I tried installing a custom ROM and rooting my Tab A 10.1 2019 and now it is stuck in a bootloop and will not turn off. What happens:
1. I get the Galaxy Tab A screen
2. Get a message about boot loader unlocked
3. Tablet starts showing the Samsung logo loading screen
4. Tablet restarts
I can't get it to break this loop, it won't even turn off., just keeps looping. Any advice?
When you see the boot-up logo quickly use adb to reboot into recovery and re-flash
Hi. How did manage the problem.? I have mine at the same behavior. Cable was dettached while flashing with Odin.
Can you still boot-up at all? i.e. does any boot screen show up? If the screen turns on make sure its plugged in and then use ADB reboot recovery to get back into recovery if it hasn't been overwritten. From there you can mount storage if its TWRP and push files to your device for the ROM, and then flash from recovery. Also you could try to find an app that can fully restore your device to factory, I know there are apps that can do that. Good luck bro. Try drfone?
Related
My out of the box Nexus 6 is now stuck looping on and off at the Google boot screen after it tried to install the system update.
I've used the toolkit 1.9.8 to go back to stock. It goes thru the steps appearing to show OKAY and finished at each step. It never reboots the phone at the end. I try to force reboot after waiting for several minutes and it still boot loops. I try again the process again and sometimes it loops and a few times it actually starts up to the welcome screen. However, if I try to root or update recovery (using the toolkit), I get the boot looping again.
Did google bork my phone during a failed update? Is there anything else I can do to completely restore the phone? I've also downloaded the images on google and flashed---same boot loop.
Ultimately, my phone is now booting up to the welcome screen as expected and shows LRX21O. BUT, if I try to do anything (root or recovery), boot loop results again.
(I was able to unlock the phone and know about the usb debug and OEM unlock settings in dev menu, fyi).
I have a Note (GT-N7000) which has decided to no longer boot up completely. It is unrooted stock ROM. It manages to get bast the initial boot screen, but gets stuck on the SAMSUNG splash screen.
I can:
Boot into Recovery
Boot into Download Mode
Use ADB
see it in device manager as aMTP Device (although I can't see the actual device contents)
I have data (appdata, and files/documents)on it I need to get off, is there any hope?
It's my wifes phone, so some of you probably know how important this is!
Any help appreciated.
dartho said:
I have a Note (GT-N7000) which has decided to no longer boot up completely. It is unrooted stock ROM. It manages to get bast the initial boot screen, but gets stuck on the SAMSUNG splash screen.
I can:
Boot into Recovery
Boot into Download Mode
Use ADB
see it in device manager as aMTP Device (although I can't see the actual device contents)
I have data (appdata, and files/documents)on it I need to get off, is there any hope?
It's my wifes phone, so some of you probably know how important this is!
Any help appreciated.
Click to expand...
Click to collapse
From what I've read, I guessed I'm screwed, but was hoping there was something I missed. Look slike the phone will be relegated to a drawer in the hope that one day I can get data back. Look out Note 3! (or 4 if the budget can stretch)
Solved!
So, I ended up installing PhilZ-cwm6 - Safe Stock Based Kernel (http://forum.xda-developers.com/showthread.php?t=1901191) and could then boot into a custom recovery, mount USB and copy all the data off.
All good. Now to factory reset and see if phone comes back to us. Already got a new Note 4 to replace the old girl, so not a issue anymore.
Hello,
I have a GT-N7000 which I am only able to access via download mode. Recovery mode does not work at all.
Odin 3.09 runs the following successfully:
1. Flashing a stock rom: N7000JPLSB_N7000OJPLSB_N7000XXLSO_HOME.tar.md5
2. Flashing a pit file: Q1_20110914_16GB.pit
3. Flashing a safe kernel: PhilZ-cwm6-JPLSB-UAE-4.89.4.tar.md5
These steps however have not solved the problem.
I have read that I need to flash a bootloader, but I don't know how to do that.
Any help would be highly appreciated.
GT2020 said:
Hello,
I have a GT-N7000 which I am only able to access via download mode. Recovery mode does not work at all.
Odin 3.09 runs the following successfully:
1. Flashing a stock rom: N7000JPLSB_N7000OJPLSB_N7000XXLSO_HOME.tar.md5
2. Flashing a pit file: Q1_20110914_16GB.pit
3. Flashing a safe kernel: PhilZ-cwm6-JPLSB-UAE-4.89.4.tar.md5
These steps however have not solved the problem.
I have read that I need to flash a bootloader, but I don't know how to do that.
Any help would be highly appreciated.
Click to expand...
Click to collapse
On a successful kernel flash, enter into recovery mode and flash raw kernel and its corresponding rom.
Unfortunately recovery does not work at all. The phone reboots when I attempt to enter recovery.
GT2020 said:
Unfortunately recovery does not work at all. The phone reboots when I attempt to enter recovery.
Click to expand...
Click to collapse
My phone has this thing where upon pressing the buttons for recovery, it will show the Samsung Galaxy Note screen twice before entering recovery. That means pressing the buttons until it finishes showing twice, or it will just reboots normally. Did you try it?
What I tried now was flashing the stock rom again. After Odin successfully flashed the rom, it went into a boot loop that lasted approximately 20 minutes, but I just let it loop without disturbing it. Eventually it stopped and switched itself off.
I tried to enter recovery and and it rebooted a few times as you mentioned, but eventually I now see the stock Recovery screen, but the Android is on his back with the red triangle on his chest.
I then performed a factory reset.
Phone reboots, I see the Samsung logo, I hear the jingle and then the phone switches off.
Edit:
Switch phone on: See message Android is upgrading. Reaches 33 of 73 apps and phone switches off.
Switch on again: Android is upgrading 1 of 41. Completes. Switches off.
Switch on again: See setup screen. Switches off.
Switch on again: Same thing.
Recovery still broken and can't setup phone as it switches itself off.
GT2020 said:
What I tried now was flashing the stock rom again. After Odin successfully flashed the rom, it went into a boot loop that lasted approximately 20 minutes, but I just let it loop without disturbing it. Eventually it stopped and switched itself off.
I tried to enter recovery and and it rebooted a few times as you mentioned, but eventually I now see the stock Recovery screen, but the Android is on his back with the red triangle on his chest.
I then performed a factory reset.
Phone reboots, I see the Samsung logo, I hear the jingle and then the phone switches off.
Edit:
Switch phone on: See message Android is upgrading. Reaches 33 of 73 apps and phone switches off.
Switch on again: Android is upgrading 1 of 41. Completes. Switches off.
Switch on again: See setup screen. Switches off.
Switch on again: Same thing.
Recovery still broken and can't setup phone as it switches itself off.
Click to expand...
Click to collapse
You need the stock recovery. Flash your rom in, reboot to stock recovery, then update with the corresponding Philz for your phone. If it works you should reboot and see philz recovery and your rom is unusable. Just flash raw kernel and any other rom after that
So all the random reboots were caused by a faulty battery.
I bought a new battery, followed steps 1,2 and 3 in my original post and my phone is working perfectly again.
My dad dropped and cracked his Note 4. I need to boot it up to get the data off it.
For some reason it wont boot to recovery, it gives me the blue text but it just boot loops after. I cannot get it to boot to the OS either.
I can get to download mode, i already tried flashing the firmware through odin. After doing so, it goes to recovery to install the system update, but then freezes 1/4th the way through and boot loops again.
I cant flash a custom recovery because the FRP lock stops me.
The only thing i have access to without a problem is Download mode. Can anyone please help me get this thing booted so i can recover the data?
Thank you!
Hello,
I'm trying to load LineageOS onto my Galaxy Tab S2. I'm using Oden to flash TWRP, but the issue is that after successfully flashing, I'm unable to boot into twrp. I tried to turn off auto-reboot in Oden, but when I then exit download mode on the tablet, it starts to boot again directly into the default os. Unlike a phone, I'm not able to remove the battery to force a power off and then a recovery boot. Anyone also run into this?
Thanks.
xd21 said:
Hello,
I'm trying to load LineageOS onto my Galaxy Tab S2. I'm using Oden to flash TWRP, but the issue is that after successfully flashing, I'm unable to boot into twrp. I tried to turn off auto-reboot in Oden, but when I then exit download mode on the tablet, it starts to boot again directly into the default os. Unlike a phone, I'm not able to remove the battery to force a power off and then a recovery boot. Anyone also run into this?
Thanks.
Click to expand...
Click to collapse
I had the same problem on my T810 and bypassed it holding button combo while it was rebooting.
Wasn't always successful so I had to flash TWRP several times until it worked.