Trouble booting into custom recovery... - Galaxy Note 3 Q&A, Help & Troubleshooting

As I stated in another thread, I used to do this with other phones, but it's been years and it would appear that things are now "different!" It looks like I have the Verizon locked recovery and I'm having trouble getting the phone to boot into a custom recovery. Everything I have tried so far has just been from the phone itself - I haven't plugged it into a PC. I have tried TWRP, CWM, and Safestrap. It still boots into the stock recovery. What should I do next? Was this problem fixed a long time ago?
Thanks.

With a locked bootloader, you cannot run TWRP or CWM.

I'm figuring that out. I'm in the bootloader unlocking thread now. It appears there might be an apk that works, but I have about 50 more pages to read.

If you have Verizon phone then you want that forum not this one .

That's what I got. Thanks.

Related

Root n7100 (March '13 kernal) N00b

Yes I'm a n00b, yes I've researched both this forum and the wider net.
I have just taken delivery of a brand new n7100 as a warranty replacement. My previous n7100 was rooted with CWM (can't remember the version, sorry). That phone was rooted using the simple method described at galaxynote2root.com and I had no issues either rooting or flashing several different ROMS.
My new phone is a very different story, I've tried several different versions of ODIN and various rooting methods. The closest I've come to a success (as reported by ODIN) actually caused the phone to reboot after flashing but instead of booting back to the script (on the phone) as I would expect, it just booted back to the regular Samsung splash screen, but distorted and then froze. I was able to reboot normally but whenever I attempted to enter CWM the same distortion/freeze would happen.
So, to recap; I was able to flash successfully (according to ODIN) and when the phone booted I had supers in the app drawer. I was NOT able to enter CWM at boot. I was able to flash the stock recovery and that is how the phone is configured at the moment.
I'm anxious about choosing the wrong root now I've had this problem as I fear I'll brick the phone.
I'm addition to the concern, I've also read that CWM can cause "sudden death"...which is something is really rather avoid...I don't want my new phone to suddenly due! However, I did really enjoy using CWM to switch ROMs on-the-fly before and, as that's what I'm familiar with I'd like to continue using that method if possible.
Can anyone suggest/recommend a method of rooting which might work for me?
If you have already rooted and SuperSU in app drawer, you need not to reroot
Just flash CWM recovery, find Philz recovery or any else in tar.md5 version and flash using odin, that's it.
And next time post your queries to Q/A section, not in general.

[Q] Flashed an OTA and now I can't boot

I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
AlexRamallo said:
I got an OTA update notification a few days back, and without thinking I decided to install it. Stupid decision. I was on a custom rom AND a custom recovery (TWRP). Now, whenever I turn on my phone it will just take me to TWRP recovery. Even if I flash a rom like AOKP or CM, the install will say "successful", but it will still go to recovery instead of the actual operating system when I power on the phone.
My guess is it has something to do with the bootloader, but I'm not too familiar with the way Android devices bootup and whatnot. This is on a D801 (T-Mobile version), and I was running a stock rooted rom with TWRP recovery installed. I'm posting here instead of the T-Mobile subforum because I don't think it's an issue unique to my model.
Since I can load up TWRP just fine, I don't think it should be too catastrophic of an issue.
Any help would be greatly appreciated
Click to expand...
Click to collapse
This might help;
http://forum.xda-developers.com/showthread.php?t=2451696

Can't Get Cyanogenmod On Verizon LG G2 V2980

So I'll tell you the steps I've tried since I've read the guides etc. What I've done this far: So in the official wiki guide you're supposed to flash a custom recovery of course first like TWRP and then flash a Cyanogenmod ROM.
You're supposed to use FreeGee for this in the App store but this does NOT WORK so one of our awesome developers on here made a tool on here AutoRec APK that DOES work. I used that tool on here with a rooted phone to install TWRP. TWRP does work and I can boot into it, but when I flash the latest nightly for my phone in TWRP it says it flashes successfully but then after rebooting the phone you end up in an infinite boot loop.
Essentially the phone goes to the LG logo and keeps rebooting over and over and over again. I fixed this by just flashing BACK TO STOCK in download mode but I've tried twice to flash a Cyanogenmod ROM and both times I end up flashing back to stock because it won't work. What's the deal with this? I can't stand this Verizon crap and their ridiculous encrypted boot loader. Never again will I buy a Verizon phone/main service mind you. Next time I'm just going to get a Nexus or whatever. It looks like Verizon doesn't want you doing anything with the bootloader for YOUR OWN PHONE.
What should I do?

Axon 7 : Can't get into recovery

Hi,
I'm not sure if it's the right place to ask this, but I need help. I just got my Axon 7 in the mail today so I was eager to root it and get started. It did not go well.
The version I got was on b27, and it had an update to b29 right out the box. I did not think too much of it and did the update. I realized later that if I wanted to root, I would need to be on b20 instead. No worries, I got into recovery, flashed the b20 stock image, and all went fine. I went on and rooted using tenfar's utility, and it also went fine. I rebooted went with DrakenFX's way to update back to b29, but something went wrong in the process, and I don't remember the exact message. I told myself that it might be cause I wasn't running the latest TWRP. When I first got into recover after using tenfar's utility, I noticed that the TWRP version was not the latest (3-0-2-0? maybe). I had just downloaded the most recent TWRP image from Unjustified Dev (twrp-3.0.2-2-a2017u.img), so I decided to update right away from within TWRP...I guess this is not something you can do.
Long story short, the phone simply won't get into recovery mode now. The led flashes red for a second, then the phone simply shuts down.
The weird part is that it boots just fine, and I can get into ADB and bootloader too. However, my bootloader is locked once more, and root does not work either. I am now on b29, so I cannot use tenfar's utility.
So, am I SOL? Is there a way to restore the stock recovery image via ADB? I tried flashing TWRP again, but I get a "FAILED (remote: Partition flashing is not allowed)" in ADB, most likely because my bootloader is locked again?
The good part is that the phone is usable and everything seems to work, but having no recovery is a bit unnerving...if something goes wrong again, the phone will be a dead brick.
Thank you very much.
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
arky33 said:
OK, I just realized that I could still use tenfar's utility even though I was on b29....pheww, what a relief. Back in TWRP. Sorry, you can delete this thread (I would do it if I knew how )
Click to expand...
Click to collapse
Can you link me in the right direction? I'm having the same problem where I can get to bootloader and fastboot, but no recovery. I'm on a2017u.x.x.b29, too.
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
arky33 said:
Hi,
I am not sure anyone should follow my advice considering how I somehow managed to screw up a relatively simple process, but here's how I fixed it. I used tenfar's utility from this thread to flash TWRP again. Even though I was on B29, I used the B27 package and it worked fine. But don't flash the boot image, just the recovery! After that, I could boot into TWRP again. From there I followed this great instruction thread and got Lineage up and running in minutes.
I hope this helps you get going, but keep in mind that this might not be the proper way to do things, it's just what worked for me. Cheers.
Click to expand...
Click to collapse
Thanks, Arky!
I've been away from XDA for quite some time since I've had the S6 Edge on Verizon and there hasn't been any type of root action on it. I really appreciate the links you posted!

HELP. Phone stuck on black screen after installing SuperUser.

Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
UPDATE #2
So I did what abhi212b told me to do and flashed the stock rom. Everything is fine now.
I'll try rooting it again a bit later. Thanks for the help.
UPDATE #3
I tried rooting my phone again, and it went flawlessly this time! Rooted successfully.
What an emotional rollercoaster lol.
Push the power button for at least 2-3 minutes. Worked for me and others in the past.
SSJGod said:
Hey guys, I'm a little devastated. Hoping I didn't ruin my phone.
So, earlier today I unlocked my Moto G4 Plus's bootloader and installed TWRP recovery. I installed ElementalX and a superuser.zip file as well. After reboot, there was no superuser in my app drawer and when I checked my root status with Phh's Root Checker, it said that my phone was not rooted properly. I then found the guide here on how to root, and noticed that it had Phh's SuperUser. I changed the config.txt file like mentioned in the guide, booted into TWRP recovery and installed it and clicked on reboot. I got the usual bootloader unlocked message, but after that my screen went blackish-grey and has been that way since, which is about 15-20 minutes now. I (panicking and being a noob) tried switching it off using the power button which didn't work. I then checked to see if it showed up as connected device in android sdk/fastboot, which it didn't.
WHAT DO I DO? I can't just buy another phone since I can't afford it as I recently bought this one, so it's a really big deal for me. :crying:
PLEASE HELP ME.
Thank you.
Click to expand...
Click to collapse
Like the poster above stated, hold the power button until the screen shuts off. YOUR PHONE WILL AUTO REBOOT!!! The instant the screen turns off, begin holding the volume down button. When you see the fastboot screen pop up, begin flashing your N images again, or use a custom ROM (which are generally much faster, easier to mess with, and easier to recover from).
Ex didn't flash properly.. That is what I can estimate! If u root on stock kernel, it breaks the device.
As said above go to bootloader (works on any screen... Power and volume down) and then to twrp maybe (flash twrp from fastboot). And then restore any previous nandroid u have.. If not u will have to flash stock via fastboot and then flash ex kernel. When u flash, restart and go to about phone and see if the kernel shows elemental x.. If yes, go to twrp and root it via suoersu, phhh's superuser or magisk su.. Whichever u like.. That should be fine!
UPDATE.
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
SSJGod said:
Hey guys,
First of all, thank you for the replies. I'm sorry I couldn't reply to them.
Secondly, a few things have happened since the OP. Keep in mind I had absolutely NO internet during the following events, so I couldn't do any research.
The night my phone went black screen, I went to sleep thinking i'll let it die out of battery and work the rest out in the morning. So the next morning I put the phone on charge and went into the bootloader. I tried doing a normal reboot which didn't work (I got the same screen) so I went into into bootloader again, connected the phone to my computer (it got recognized this time) and re-flashed TWRP. I went into recovery mode on the phone and tried re-flashing ElementalX and superuser. This time I got an error when trying to flash the superuser.zip, and the error was:
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/superuser.zip'
I had another supersu.zip in my phone storage, tired installing it and got the same error.
When I tried doing a normal reboot into my system, it goes on a boot loop on the "your device is unlocked" screen and has been that way ever since.
What do I do now?
Should I try to re-flash TWRP and superuser with the right files, or should I restore stock recovery? I don't have any backup. (noob mistake)
I'd highly appreciate it anyone linked me the proper twrp and superuser or stock recovery files and if possible guided me on what to do.
PLEASE HELP ME.
thank you.
Click to expand...
Click to collapse
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Thank you, will try this now.
Only the last SuperSU Beta defaults to systemless install. Any other ones require writing of a .SuperSU file to force systemless before rooting.
https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
SSJGod said:
Thank you, will try this now.
Click to expand...
Click to collapse
If you have not done this already, you can give it a try by flashing the stock boot.img via twrp and see if that boots the device.
I am not sure that it will work since, i have not tried it.
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
just_magikkal said:
Exact same thing with the XT1625. I have also found that the systemless method of rooting with SuperSU kills my wifi and cellular network's connection abilities, which might just be a standard G4 thing but the only way I know of to fix it is reflashing the OS (data wipe not necessary).
Just thought this might be helpful to anyone who ran into similar issues to the ones I had.
also i'm still having issues with the stupid thing actually rooting but i'm gonna try again some other day.
Click to expand...
Click to collapse
I think that is the kernel issue.. you should try EX.. and then use SuperSU or maybe use Magisk SU..
abhi212b said:
That won't help!
Best is that u should flash stock rom, since the phone is bootlooping...
U can find it here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Flash it on bootloader screen via fastboot.
Do not relock the bootloader. Skip that step and also do NOT flash bootloader.img and partition. That can mess up the device.
once this is done, boot the device once... Finish the setup and then flash twrp.. Then flash ex kernel then flash any root Zip. (supersu, magisk or phhh's superuser)
Twrp can be found from here. https://forum.xda-developers.com/mo...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Click to expand...
Click to collapse
Had the same problem as OP and this fixed it, thanks a lot man!
Good to hear now the phone is alive!

Categories

Resources