Develop Bugs

SGH-I747 AT&T Softbricked Maybe Hard

Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.

gica69 said:
Hi guys I just bought a SGH-I747 AT&T and the issue with it is it goes into Download mode just fine, works with Odin 3.7 loads a stock rom and then it sais reset but the phone doesn't reset just goes to black screen and then Odin sais Pass. I press the power button and Samsung appers and vibrates and goes back to black. When I try Recovery mode it show the blue writing on the left upper and the Samsung and then it goes to black screen. I put two different stock roms and same story. Kies won't recognize it and I installed recovery-clockwork-touch-6.0.4.3-d2att.tar to try to get into recovery mode and of course no luck. Don't know the history on this, so if anyone could help I would really appreciate it. Thanks in advance.
Click to expand...
Click to collapse
I found out that the phone had 4.1.1 on it and the guy tried to flash 4.2.2 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help

gica69 said:
I found out that the phone had 4.11 on it and the guy tried to flash 4.22 and upon doing the odin mode flashing odin gave Firmware upgrade encountered an issue Please select recovery mode in Kies & try again So these are just some helpful facts for anyone who has gone through it. Thanks in advance for any help
Click to expand...
Click to collapse
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3
PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.

Larry2999 said:
What firmware were you trying to flash via Odin and are you sure the seller didn't previously flash (or try to flash) the 4.3 on it? If it wasn't higher than 4.3, then you may try recovery via Kies as follows ....
Install and launch Samsung Kies on your PC (not Kies 3). Open the Tools menu and select Firmware Upgrade and Initialization
Do not connect your phone to your PC yet. Remove the battery cover and record device info written in the battery compartment
In Kies, enter your phone model (SGH-I747)
Enter the phone serial number and click OK to all the security questions. Follow all the instructions on Kies
Connect the phone when prompted and follow the rest of the instructions
Wait for firmware upgrade to complete
Good luck!
If this doesn't work, then you may try flashing the 4.1.1 stock image via Odin. Look for the correct stock image via the following thread ...
http://forum.xda-developers.com/showthread.php?t=1739426
The one you want for Samsung Galaxy S3 AT&T (4.1.1) is I747UCDLK3PLEASE don't try any of the above if you were already on the 4.3 bootloader as things will only get worse.
Click to expand...
Click to collapse
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help

gica69 said:
I have already tried the I747UCDLK3 not from the link you gave me though. I did notice that the one you mentioned is a rooted stock do you think I should still do it? The rom flashes fine no errors in Odin but when it sais RESET the phone turns off the download mode and vibrates once then goes black then later Odin sais Pass but I cannot start it it just bootloops and vibrates and it stays that way As far as the Kies procedure you gave me don't I have to be in recovery mode for it to see the phone? I cannot get to that mode just download mode. Let me know thanks for your help
Click to expand...
Click to collapse
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.

Larry2999 said:
If you were successful in flashing via Odin, I would have suggested you try doing a hard wipe/reset in recovery. However, you said you can't get to recovery mode so this may not work. What happens when you try booting into recovery mode?
For Kies, you wouldn't have to be in recovery mode for the firmware restore to happen. Normally, you would have to connect your (powered-on) phone to your PC for it to be recognized by Kies. However, as you can't power on, we are forcing Kies to prepare the specific required firmware for your device by manually entering in the device information. Thus, when the phone is connected, you have firmware ready to make it work.
It may also be that the firmware you downloaded and flashed via Odin may not be the correct or full version. There are so many sources of "stock" firmware these days that one can never be too sure. You may go to Sammobile.com to download the stock firmware and compare the size of the extracted file to the one you used. The odin flashable tar.md5 file should be about 1.1Gb in size.
Click to expand...
Click to collapse
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.

gica69 said:
When I go in recovery it shows blue writing in left upper corner and Samsung logo and then black screen. I think I did use the Sammobile firmware at 1.1. My clock in download mode shows 6. I don't think that would affect it though. Could it be that Odin doesn't really write the firmware that's why flashing doesn't change anything? I don't think the jig would do anything maybe sending it for a jtag reflash is the trick.
I am lost for now. If you guys can think of anything new let me know and thanks again.
Click to expand...
Click to collapse
You didn't mention if you tried the Kies option. I had a similar problem once when upgrade to 4.1.1 via Kies failed during the process and that was how I was able to recover. However, since you bought this from the secondary market, there is no way of telling for certain what the previous owner did wrong which would have been useful for recovery options.
One of the nice things about Odin is that you usually know the results immediately. If it says Pass, therefore, that's likely what it means. So Odin did flash something. But what did it flash? The counter you saw in download mode shows how many custom system installations there have been and 6 does show there has been some previous heavy tinkering with the phone. As you are still able to get into download modes, I would suggest you try flashing custom recovery (TWRP or CWM) via Odin. If this works and you are able to get into recovery mode, you may then try doing a hard wipe/reset via recovery. You may also try flashing the other (rooted) 4.1.1 file via Odin. At this stage, you really have nothing to lose in trying all options. I guess if you can get into recovery mode, the problem is almost solved as this leaves plenty of options.
A jig wouldn't help as that only gets you to download mode which, for now, you don't have a problem with. JTag should always be a last resort option only. Let me know how far it goes and good luck!

When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.

audit13 said:
When flashing in Odin, did you check auto reboot? If you did, try flashing again but uncheck auto-reboot. When you see Reset in the status windows, disconnect the USB cable, pull out the battery, wait a few seconds until the phone completely shuts down, put back in the battery, get into recovery, wipe cache, do a factory reset, and reboot.
Click to expand...
Click to collapse
This damn phone is starting to annoy me. I can still get into download mode but my phone gets usb device not recognized now. I have access to another I747 phone so my question is if I have access to the pit file from that phone can anything be done with the Debrick utility and a SD card with only download mode access? Thanks in advance.

Go into download and let us know what is shown on the screen.

audit13 said:
Go into download and let us know what is shown on the screen.
Click to expand...
Click to collapse
Odin Mode
Product Name: SGH-I747
Custom Binary Downloads: Yes (6 Counts)
Current Binary: Samsung Official
System Status: Official
Qualcomm Secure Boot: Enable
Green Android Icon Downloading...
Do not turn off target!!!

OK I plugged the USB in and out a few times and it allows to write every few tries. Back to my question can I do something in download mode if I have another i747 that I can copy stuff from? I also tried the suggestion to uncheck auto-reset pull the usb cable then the battery and try to go to recovery but it doesn't.Any suggestions are welcomed.

Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.

audit13 said:
Try flashing a stock 4.1.1 rom from sammobile using Odin. Do not check auto reboot. When you see reset in the status window, disconnect the usb cable, pull the battery, replace the battery, boot into recovery, and wipe. I have done this numerous times on my i747m after flashing custom ROMs.
Click to expand...
Click to collapse
I will try it again I think I already did but when I put the battery back and click the Vol+ Home Power I get the blue writing and then black screen. Should I wait like 10 min on the black screen or it should be quick. Thanks

Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.

audit13 said:
Keep holding the buttons until the blue writing disappears and the green android appears with the green progress bar.
Click to expand...
Click to collapse
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.

If u can get it into download mode u are never ever hard bricked my friend...take it from a guy who had to dust off his old galaxy sll last weekend & still can't get into d/l mode on my s3 after a week & even with a jig lol
Sent from my SGH-T989 using xda app-developers app

gica69 said:
Is there an unbrick.img for 4.1.1 or 4.1.2 I noticed that there are files for 4.3 that allow you to go in recovery and erase stuff reinstall. Let me know cause I sure couldn't find it.
Click to expand...
Click to collapse
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.

Larry2999 said:
The unbricking image only helps you get into download mode from where you can work your way up the rest of the food chain. As you can already get into download mode without difficulties, I doubt if that's what you really need. You are also able to flash ROMs successfully in download mode via Odin so you've gone far up on the food chain already. Perhaps you are not doing the recovery thing correctly enough. Like Audit said, you need to continue holding down the Volume Up and Menu buttons whilst releasing the Power button after you see the first flash until the recovery menu appears and then do a hard wipe/reset.
Perhaps you could also try flashing TWRP via Odin if CWM isn't working.
Click to expand...
Click to collapse
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.

gica69 said:
I already tried holding the Home and Volume up buttons for 4-5 minutes at which point my fingers got a bit tired. The reason I wanted the unbrick.img is that I am now having issues with the computer recognizing the device in usb. I plugged and unplugged so many times that it no longer works that way so I wanted to do it via sd card. The unbrick.img gets you in recovery mode and download mode as it allows you to boot from the card not from the internal HD. But the only ones I have seen are for the 4.3 issues. And I tried It but did not put my device in recovery.
Click to expand...
Click to collapse
I couldn't find one either although you may be able to create yours using the command line posted in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
You may also try using a jig to get back into download mode. Have you, however, considered exercising any buyer protection options you have on the phone since, it would appear, the guy sold you a lemon?

Nokia N1, wiped system, stuck on splash screen (Powered by Android) (Update!)

Dear Xda,
This is my situation, i had a bootloop so i ran the temporary recovery method explained in the thread "Nokia N1 Rooted with Google Play!" in the general forum of the Nokia N1
But i accidentaly removed the system partition (which boots the system and shows the boot animation etc, after the splash screen)
I can however boot into the bootloader with volume down+power as well as going into the temporary recovery to wipe and flash stuff.
I figured a way to fix this, this is to push or copy a update.zip from my pc (with the original nokia n1 files) to my nokia n1,
but the problem is adb does not recognize this device in the cmd with the command adb devices, and the hardware id is having ???? in device manager (Windows).
Does anyone maybe know a way to push files to this device in either bootloader mode or temporary recovery or maybe another way, as i am stuck with this.
If something is not clear or if i need to post images of my situation of more information please say so,
also i have the taiwanese version not the chinese and i have also all the zip files for android 5.0.1 and 5.1.1 (latest) which 1 of the 2 i need to push to my device to restore the system partition.

Ok, so far i have not gotten an answer from someone,
so i went to look around other forums and identical devices, the closest being the zenphone 2, as they use the same intel processor the intel atom z3580.
I have also looked around alot in the nokia n1 forums on search for the original taiwenese firmware as i have found a way to custom flash the device if it is hard bricked (as in no adb, system or recovery)
I found out that the new intel phone flash tool required a flash.xml file to (re)flash firmwares in order to restore it, so i have been googling around for older phone flash tool programs as i have stumbled upon a nokia n1 thread somewhere where it showed a picture of a custom flash (without the flash.xml file)
I have managed to get a fastboot connection with an old intel phone flash tool program and been trying to flash chinese firmwares to it, but so far it keeps on failing for some reason
I have a feeling that it might be possible to resurrect a broken nokia n1 with the right firmware when you only have access to the fastboot (power up+volume down), we might as well use this method if succesfull to fix bootloops if no recovery is available (as it was with my taiwanese version for some odd reason)
I will attach screenshots of what i have so far, if anyone is interesting in helping me or have an idea please say so.
p.s. i keep on trying to do more research and fiddle more with it, as it cant be more broken than it is now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sadly, i can not go on any further, i have tried and flashed to much files and the nokia bootloader has locked itself, neither does oem unlock commands work with a fastboot flash file, i feel like i was very close to recover the nokia n1, but now it will forever be paperweight, as i have no recovery, no system, no adb, and a locked bootloader so no fastboot anymore.
If anyone have a solution or advise i'm open for this, but until then i can not proceed to test further for people who have like me bricked their device and turned it into useless paperweight (and i feel like the nokia was really vulnerable for bricking) i kinda regret buying the nokia now though.

do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it

2111002640 said:
do you have any ROM for CN version ????? my tablet is stuck in logo, i don't know how to fix it
Click to expand...
Click to collapse
Yes i do have, do you perhaps know which CN version you had? if not i can attach/link you a CN version.

It is possible to install the same or newer Version of the Firmware, which was installed on your N1
You need a full Firmware package for your tablet (CN or TW Version).
Sent from my N1 using Tapatalk

do you have full ROM for N1 tw or cn, if you have this can you share for me plêas

i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke

2111002640 said:
i have a solution to fix this error, anybody want to fix this error may be contact me
my fb: https://www.facebook.com/hjxhjx.huhu
i had fix 2 devices to live every oke
Click to expand...
Click to collapse
I don't have a Facebook account. Could you post your solution on here please? Thank you

Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.

srsface said:
Hello there! I think I had a similar problem but I managed to unbrick my device after good 24 hours of stress and facepalming after getting it stuck in splash screen late last night. I found your thread and a few others that suggested trying Intel's Phone Flash Tool, but it didn't work for me. I thought I had no fastboot, but suddenly I managed to get it to fastboot with Power + Vol Down (releasing power shortly after pressing while holding vol down a tad longer). Turns out my device was locked, so I couldn't flash anything. I had previously flashed the recovery file of A5FMB19, but I thought it hadn't worked. Alas, again I was wrong and from fastboot I was able to get to recovery mode! From there I was able to factory reset, adb sideload the full version of A5FMB19 and now my N1 is happily running with Google Play.
So if somebody still has the same problem I guess what I'm trying to say is that even if it first seems that recovery mode is not reachable, it might still be there since the device seems to be very picky about the button presses. It was that in my case, and it suddenly worked tonight while earlier it did not... This is the post that I mainly followed https://forum.xda-developers.com/no...1-chinese-version-5-1-1-update-t3183529/page6 I guess the important thing is to find a matching ROM to your recovery image.
Click to expand...
Click to collapse
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?

defendos said:
How did you manage to enter recovery after entering fastboot, i can enter fastboot just fine, but my device is in a locked bootloader state after to many flash attempts, and when i try to enter recovery in fastboot it just reboots the device back into fastboot, any suggestions or ideas?
Click to expand...
Click to collapse
It's been a week and it was the first time I ever tried to flash anything, but I think that in fastboot I just selected recovery mode with the volume buttons and then pressed the power button to confirm the selection. Since I had previously managed to flash in a recovery image of the Taiwan version, it worked. My saviour was that the recovery image wasn't corrupted even though my Android itself was, so I guess there was no magic trick - I just managed to do the right things finally after wrong physical button presses. If you can't get to recovery then maybe you are truly bricked. Would these suggestions be of any help? forums.oneplus.net/threads/solved-stuck-in-fastboot-bootloader-is-locked-need-help.435522/

same boat bump!
accidently wipe data cant boot stuck on android logo
i can access fastboot but no adb (unauthorize)
on 5.0.2

Bricked LG G3 [D855], cannot enter download mode

Hi, I was trying to flash a kdz to my LG G3 in order to downgrade the phone to 5.0. However, while the program start flashing and the progress bar on the phone reach 5%, the program shows " cannot reach the sever". The flashing process then stopped, no matter I keep clicking "retry".
As a result, I took out the battery and put it back attempt to get back to download mode.
However, the LG G3 do have a starting up screen as usual, but the phone didnt go in download mode, but get into black screen. The notification light is repetitively flashing blue and red color for couple second.
THe computer cannot detect the phone.
Any idea how I can save the phone ~_~?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana

Bananaphone64 said:
Can you still Enter Recovery or the normal OS (guess not because the flashing process was interrupted)
Banana
Click to expand...
Click to collapse
It can go into the recovery mode but not the normal OS. But what I can do in the recovery

voot566 said:
But what I can do in the recovery
Click to expand...
Click to collapse
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana

Bananaphone64 said:
You can Flash the stock rom via Recovery (i assume you have TWRP or some other custom Recovery installed?)
https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012
You also can try to repair the Download Mode via ADB & Fastboot. I dont know if you can use ADB via Recovery.
https://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Do this in Order to erase the Download Mode to get access to fastboot Mode. In Fastboot you can flash the stock recovery, boot etc. images to repair the download mode.
Just did this 1 day ago
Banana
Click to expand...
Click to collapse
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"

voot566 said:
That is exactly the problem, where I am in stock recovery now, and all adb command from computer end up with "no device is connected"
Click to expand...
Click to collapse
drivers installed?

Bananaphone64 said:
drivers installed?
Click to expand...
Click to collapse
Yes, driver is installed :crying:
but windows doesnt seems to have detected my phone

Hm... i recently havent the stock recovery installed. I allways hat the possibility to use TWRP.

Thx so much, Bananaphone64.
I think what the real problem now is, the computer cannot recognize the phone. Anyone else have an idea?

In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana

Bananaphone64 said:
In a Tread about recovering LGs i read that you have to uninstall all drivers from different Phones. I had Samsung Drivers installed. Maybe this helps.
Can you give a SS of the original recovery. From my old s2 recovery i know that you can apply an update.zip from the Android Recovery. But you have to get a signed (bumped) Original Rom to make it work.
This is what comes to my mind.
Banana
Click to expand...
Click to collapse
I have attempted on another computer, but the other computer also doesnt recognize the phone.
What is a SS?

A Screenshot or Picture from the Recovery Menu

Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS

I have seen that screen! 3 days before!
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!

yosmz1112 said:
hello
I got the same screen on my G3.
Is it not possible to enter the download mode even if you turn off the power and connect to the computer while holding down the volume button?
My G3 is in download mode in that way.:good:
Using the LG flash tool 2014, after writing the corresponding kdz, it recovered.
good luck!
Click to expand...
Click to collapse
Yes. it was completely not able to enter into the download mode...........

Wh0CaREs said:
Hello,
I am not sure do you have custom recovery?
I had same problem and only way to fix it it was to follow this tutorial because I hadn't had custom recovery..
I unbricked my phone and installed stock rom and then I installed LineageOS
Click to expand...
Click to collapse
It is factory recovery. let me check the link, thx so much

deleted

Question Bricked Pixel 6 Pro Help needed

My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.

There's another software on here called pixel flasher try that if they don't work see of more knowledgeable people message
might have to speak to Google and also were you bought it from
I had the 6 pro put on charge then turned on did restore from back up and it was like 5 to 100 of apps and then it did the march update and it boot looped that was on Saturday
I got into the safeboot mode or whatever it restated as that what I clicked then got into mode again then from there it's froze
I didn't get a replacement till Tuesday lol that was ee had no problems with new one

How about using the android flash tool to reflash the latest beta that you were on?

Also...flashing without a bootloader unlock is like Android No-No ...no.1 ...

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).

TLS993 said:
My pixel 6 pro is stuck in fastboot mode, and for some reason wont boot into android at all. It was running the android 13 beta 2, the device is not rooted, or anything. I have spent the best part of 2 hours navigating through the various bootloader/recovery menus on the phone, but not really getting anywhere. all I was trying to do was unenroll the phone from the beta updates, and return back to stock. it was downloading the latest public build after unenrolling the phone when something happened, and now it doesn't boot.
I am really stuck as I cant use the android flash tool to flash back to the public build of android 12, as I don't have OEM unlocking activated in developer settings on the phone, and obviously not being able to boot into android, means that I cant just restart to enable, like all the guides i have read tell you to do.
Is there a way to flash the phone back to stock android 12 through terminal some how without having OEM unlocking enabled? any help is appreciated, as I am currently looking at a £1000 paperweight at the moment.
Click to expand...
Click to collapse
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.

opz187 said:
Go back to 13 beta 2 for now. Download the ota onto cpu. Go into fastboot, boot into recovery. Factory wipe in recovery. Then in recovery, go to sideload via adb. Adb sideload the beta zip. You're welcome . Of course you'll have to know how to use adb and all that but hopefully you do.
Click to expand...
Click to collapse
Thanks for this, I will give it a go. I have used ADB before, so should be fine with that

Alekos said:
Since you are able to boot into fastboot, your device isn't bricked and should be recoverable. The first thing you will want to try is booting into Safe Mode to enable OEM unlocking:
1. Press your phone's power button.
2. When the animation starts, press and hold your phone's volume down button. Keep holding it until the animation ends and your phone starts in safe mode.
3. You'll see "Safe mode" at the bottom of your screen.
If that doesn't work, you can also try to flashing the OTA in recovery mode. Lots of videos on YouTube on how to update via OTA in recovery mode. Here's the Android OTA download page - you won't lose your data with this method. Chose the right image.
Next option would be to try wipe or reset by using the Recovery Mode (this will wipe your phone): While in Fastboot/Bootloader, choose Recovery Mode with the Volume buttons. On your screen, “No command” is displayed. Press and hold the Power button. While you hold Power, press the Volume Up button and let go of both buttons quickly. Choose factory reset option (this will wipe your device so be sure to try safe mode and OTA update methods before this option if you are trying not to wipe the phone).
If you just want to get your phone back without trying to save data, try Google's Official Flash Tool. I know most will say it's a waste of time if your BL is locked - but there have been many reports of users fixing issues just like yours even with a locked Bootloader.
Android Flash Tool
flash.android.com
You'll need a Chrome browser.
Because you're on 13 Beta, you could try just reinstalling the Core OS with the web flash Tool. Uncheck all the boxes (don't wipe or re-lock etc).
Click to expand...
Click to collapse
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
You mention power button but you never said you held the volume down button as you were powering on. you must hold the volume down button.

TLS993 said:
Thankyou for the suggestion, my phone however will not boot into any form of android. It just boots straight to the fast boot screen every time. Pressing the power button, you see the Google logo, but it then boots straight to fastboot. It's as if there is no os on the device at all
Click to expand...
Click to collapse
I understand it won't boot into Android. Your phone is fine. If you want help, dm me, I will get you sorted. You just need to re-flash Android using the above Flash tool.

Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
That's good to hear - it's hard to brick a Pixel.
Best options to resolve issues is the Flash Tool, OTA Update or cli image. The OTA can be tricky when using platforms tools (adb/fastboot).

Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?

anasmhds said:
Hi
I ordered my phone from US, but did not realize that its Verizon OEM locked.
Any Idea how to unlock the bootloader? any way even paid method i am ready.
Now I am on A13 beta which is fine, can I flash a full rom using ADB update without any issues?
Click to expand...
Click to collapse
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such as Android 13 Beta 3, 4, and final release.

roirraW edor ehT said:
No Verizon device can ever have its bootloader unlocked. Sorry, you're just out of luck. With a locked bootloader, you can only ever upgrade to other official ROMs, such and Android 13 Beta 3, 4, and final release.
Click to expand...
Click to collapse
Thanks for your feedback.... just bad luck

TLS993 said:
Thanks everyone, After a bit of struggling to get the system image flashed, I finally managed to get it done using ADB sideload.
Took me around 15 attempts to get there, but I'm now up and running again. Thanks to everyone who replied, and assisted with the issue!
Click to expand...
Click to collapse
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

radioxmen said:
Please how did you do for ADB sideload, because I now have the same problem as you and I'm still stuck on fastboot modeView attachment 5618033
Click to expand...
Click to collapse
Select recovery mode.
When you see No Command, press power and volume up at the same time (quickly). Then try factory reset. If that doesn't work, choose ota update and follow the links above.

Have same exact issue here.
When I try to sideload, I constantly get "cannot read" error.
I tried Large Address Awareness but even that didn't work.
Any help is appreciated

So this tool cant fix your problems?
Android Flash Tool
flash.android.com

No, I keep getting error that OEM is not unlocked

Found my old note 10.1 and did something stupid... need help...

I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Why don't you try flashing stock firmware?
Check for drivers issue.

mvikrant97 said:
Why don't you try flashing stock firmware?
Check for drivers issue.
Click to expand...
Click to collapse
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
Your device should show up like this in device manager
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing like this

erkme73 said:
Thanks for the quick reply. I guess that's where I need a bit of hand holding. It's been so many years since I dabbled with rooting my devices, that I've forgotten more than I remember, and I'm hitting all sorts of dead ends.
I'm willing to learn so I'll take whatever advice you're willing to offer. I've installed the samsung USB drivers, but with too many variables to nail down, I'm not sure where to start.
I have Odin, and I THINK it's the p600 (without the cell radio), but odin or adb is not seen any device connected.
Click to expand...
Click to collapse
It is P605. And from this post looks like you are not the only one https://forum.xda-developers.com/t/q-galaxy-note-10-1-2014-not-recognized-in-download-mode.2494886/

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Also watch this video

erkme73 said:
I haven't used it in many years. It powered up just fine. I apparently rooted it when I first got it, and forgot. So I tried to update using the system update - it failed because of the root, which is expected.
I opened the superuser root app and told it to permanently unroot. I mindlessly accepted the following prompts, and after rebooting, it's now stuck on the main samsung note 10.1 2014 edition logo for about 3 seconds, then repeats in a loop.
I am able to get to the recovery screen where I have options:
Reboot
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to boot loader
power down
view recovery log
I attempted the wipe data/factory and cache. Same results.
If I attempt to do the bootloader (either through the recovery or with the power/vol+ button) I get the prompt to enter the download mode by pressing the up button. However, it then immediately returns to the bootloop.
I screwed the pooch because I don't recall any details on what version of ROM I had on there, or any other details.
Is there a way to get me back to a point where I can install something like lineage? All of the steps I'm finding presume I can get to a working OS.
Any help would be appreciated. I really don't want to toss this tablet. It was working just fine before I decided to "fix" it.
ETA: Connecting it to a PC provides no recognition at the device manager at all. I tried different cables, different ports, different PCs.
Click to expand...
Click to collapse
Please try to get into download mode for odin to recognize your tablet

Ok, so using another PC and yet another cable, I was finally able to see this pop up on the device manager when in the "update with adb" option:
Unfortunately, I cannot get the tablet to stay in download mode. As soon as I confirm to go to download with the vol+ button, it immediately starts to boot loop.
On the other hand, when in the adb mode, the PC does recognize the device when it's attached and I can see it with "adb devices" command.
But unless there's a way to get it to go to download mode, I'm screwed, right?

mvikrant97 said:
Also watch this video
Click to expand...
Click to collapse
Yes, but that is my problem. I cannot get to the download screen. I can press up to select it, but then poof, it goes to cycle again. Unlike the guy in the video:

OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!

erkme73 said:
OMG!!! Pressing volume DOWN (cancel) actually put it into download mode!!
Click to expand...
Click to collapse
Now you are good to go. Odin will detect and you can flash it.

Thanks... doing it now. I'll let you know how great you are as soon as it starts working! Thanks...

Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
That's great to see your device is working now.

erkme73 said:
Works perfectly. On "latest" 5.11 stock. No I remember why I rooted back in 2014... Now hunting for a simple root.
Click to expand...
Click to collapse
If you really wanna stay on stock you can use Chainfires Autoroot for this device.
Anyway, my P605 is on LOS17.1 running stable.