When Android Keep Booting Into TWRP Recovery - Google Pixel Guides, News, & Discussion

Thousands of android users having this problem, when you install custom ROM and then you try to reset your phone; it keep rebooting into TWRP recovery (not system), even after you flash your ROM again.
So here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE
Mod edit:
Thread closed. Link is dead.

link is dead...

I'm already rooted and I tried to install twrp and it keeps doing the same. Even after flashjng boot.img to both slots before hand.and rerooting after installing twrp
Sent from my Pixel using XDA-Developers Legacy app

Somebody please repost the answer.

I dont know if it has changed but whenever this happened to me I just fastboot flashed the boot.img and then it booted up fine
oneders65 said:
Somebody please repost the answer.
Click to expand...
Click to collapse

oneders65 said:
Somebody please repost the answer.
Click to expand...
Click to collapse
The answer for me when I had this happen in September was to simply flash the Magisk zip file from the TWRP recovery after one of the many loops that it had done
(and I had tried everything else - reflashed TWRP from both fastboot and recovery many times, re-flashed the Google Pixel full image via the flash-all.bat file a few times, etc).

Related

[Q] Problem with TWRP in rooted and unlocked nexus 10

Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.

Need Help Stock Recovery Marshmallow ZE500KL

Hello, i accidentally flash twrp on to my phone (should just boot it). Now i dont have stock recovery anymore. i have tried flash my phone using stock recovery i got from here, here and here. but still no luck. anyone can help?
my phone firmware is latest marsmallow. Unlocked Bootloader and Rooted using miaulightouch method.
Thanks,
FRezING
FRezING said:
Hello, i accidentally flash twrp on to my phone (should just boot it). Now i dont have stock recovery anymore. i have tried flash my phone using stock recovery i got from here, here and here. but still no luck. anyone can help?
my phone firmware is latest marsmallow. Unlocked Bootloader and Rooted using miaulightouch method.
Thanks,
FRezING
Click to expand...
Click to collapse
The links you give mostly for L.. I don't know if that will work on M though
Try to extract boot.img from your Asus zip and flash it, root might lost (?)
#sfmbe
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
The links you give mostly for L.. I don't know if that will work on M though
Try to extract boot.img from your Asus zip and flash it, root might lost (?)
#sfmbe
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
Thanks for reply, ya all of them for Lollipop because i have tried to flash boot.img from stock Marshmallow but still no recovery so i tried using Lollipop still no luck. Yesterday i tried back2stock method the rom flashed sucessfully but still no stock recovery.
Thanks,
FRezING
FRezING said:
Thanks for reply, ya all of them for Lollipop because i have tried to flash boot.img from stock Marshmallow but still no recovery so i tried using Lollipop still no luck. Yesterday i tried back2stock method the rom flashed sucessfully but still no stock recovery.
Thanks,
FRezING
Click to expand...
Click to collapse
So, I'm curious about it, and flash twrp myself just awhile ago...
And got bootloop, really... wait, seriously?
I'm like
How did the other day I'm able to survive this? It boot normally,
After 1st successful boot, flashing root, (I don't remember but just say I'm booting twrp this time), xposed, aware that root lost after reboot, I did my backup here,
Then deciding to start from scratch, installing official Asus, boot normally, flash twrp, rooting,rebooting few times and somehow root intact, install xposed, root lost...
Restart again, install Asus official (I'm not restoring my backup, really, the only thing I know how to install stock is by stock recovery itself) , boot twrp, install root by system, reboot, root intact, xposed, root intact, surfing net, registering xda yesterday, just now replying to your thread, then you can read from above again...
Just few minutes ago, restore recovery from backup (still bootloop though), installing Asus again, and make this reply...
Sorry can't help you, even I'm confused right now
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
So, I'm curious about it, and flash twrp myself just awhile ago...
And got bootloop, really... wait, seriously?
I'm like
How did the other day I'm able to survive this? It boot normally,
After 1st successful boot, flashing root, (I don't remember but just say I'm booting twrp this time), xposed, aware that root lost after reboot, I did my backup here,
Then deciding to start from scratch, installing official Asus, boot normally, flash twrp, rooting,rebooting few times and somehow root intact, install xposed, root lost...
Restart again, install Asus official (I'm not restoring my backup, really, the only thing I know how to install stock is by stock recovery itself) , boot twrp, install root by system, reboot, root intact, xposed, root intact, surfing net, registering xda yesterday, just now replying to your thread, then you can read from above again...
Just few minutes ago, restore recovery from backup (still bootloop though), installing Asus again, and make this reply...
Sorry can't help you, even I'm confused right now
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
It's ok thanks for your help tho, my phone still usable im just curious why the stock recovery still missing after flashing it via fastboot. u can use back2stock method if bootloop that method really handy no need to wipe anything i use it before when bootloop and my data still there.
FRezING said:
It's ok thanks for your help tho, my phone still usable im just curious why the stock recovery still missing after flashing it via fastboot. u can use back2stock method if bootloop that method really handy no need to wipe anything i use it before when bootloop and my data still there.
Click to expand...
Click to collapse
My phone already recovered by the time I'm replied above, and somehow.. systemless work.. duh
back to topic
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
My phone already recovered by the time I'm replied above, and somehow.. systemless work.. duh
back to topic
Sent from my ASUS_Z00RD using XDA Labs
Click to expand...
Click to collapse
How did u fix dat issue? no recovery here and on booting logo it shows invalid boot.img
Plz help
arunperul said:
How did u fix dat issue? no recovery here and on booting logo it shows invalid boot.img
Plz help
Click to expand...
Click to collapse
Sorry, which part?
If about how I got my recovery back then, I don't really understand, let's assume I have my backup that time. now I have my backup, for real.
From what I understand, invalid boot mean either you got broken boot images or locked bootloader, so which one is familiar to you?
Anyway, you can try to flash back stock boot (grab from asus zip) and stock recovery (if you have them, or find on this forum?).
I don't know if locked bootloader can flash boot/recovery, never tried it myself. So, good luck!
Sent from my ASUS_Z00RD using XDA Labs

[HELP] Moto G PLus 4 booting only in recovery, not system

Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
EDIT: I forgot to mention, I'm not getting the boot animation as well. I press the power key and nothing at all happens.
d1nesh said:
Hi,
I just unlocked the bootloader of my Moto G Plus 4 via adb, and after that I switched it on, it worked fine and I transferred SuperUser.zip into my phone's internal memory, and then tried to flash it through recovery, (following the sleps I read somewhere), since then my phone is not rebooting - it is rebooting into bootloader and I can enter recovery as well, but Im not able to reboot my phone. The device is being detected via adb when it is in recovery mode, but not in bootloader. Is this issue fixable? Please help me fix this.
Click to expand...
Click to collapse
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
You got into bootloop, just download the stock ROM and then flash it again, follow any guide over XDA or see YouTube for more help. Flash ROM without locking bootloader will be good.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
d1nesh said:
I forgot to mention, I'm not getting the bootanimation as well, I press the power button and nothing at all happens.
Click to expand...
Click to collapse
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
avirk said:
Yes that is what happen after unlocking Boot loader, just flash the stock ROM using any tutorial over XDA without locking the boot loader and then follow the proper instructions to root your mobile. Rooting is very easy on Android N. So I will say flash android N and then proceed.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
==vj== said:
First thing, your query doesn't belong to the development thread. It should had been created in "Questions and Answers"
Second thing, if you flash supersu on stock rom it won't boot due some security measures of Moto. Instead flash ElementalX kernel first and then flash supersu.
Click to expand...
Click to collapse
i'm really sorry about posting in wrong thread.
While trying to flash ElementalX kernel through memory card, I'm getting error: Zip signature verification failed, (in red).
nazim7 said:
All information that you will need can be found here. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
For the latest stock nougat firmware for XT1643 check this link https://mega.nz/#!ystC2ZSL!ql6cyC5v5RgLQfo7G44mhi7Ng-AQBvtsouKxKinbHi8
If you have some confusion about flashing, be sure to check it out before going on. I believe you have some knowledge about fastboot and using it.
Click to expand...
Click to collapse
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
d1nesh said:
DO you mind posting the link to the proper article, since phone is not being detected via adb as well.
Click to expand...
Click to collapse
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
d1nesh said:
Last time I used fastboot was more than one year ago. Also, my device is not being detected by adb when in bootloader.
Click to expand...
Click to collapse
What did you mean by your device not being detected in bootloader mode. Did you install the right drivers. Did you install minimal adb and fastboot. Can you do the below steps and tell me the result.
1. Download the drivers from here.
For Windows: http://www.devfiles.co/download/5eEx...ager_2.5.4.exe
2. Download the Minimal ADB and Fastboot = https://www.androidfilehost.com/?fid=745425885120698566
3. Install Minimal ADB and Fastboot = https://forum.xda-developers.com/sho....php?t=2317790
4. Restart the Moto G4 in fastboot mode. (Bootloader mode)
5. Connect the Phone to the computer.
6. In adb fastboot folder shift+right click and then in the pop up click "open command window here"
7. In the command line type: "fastboot devices"
Seeing your serial number means we know all is good and your phone is connected and you can go on flash the stock firmware. If the serial number is not showing, the drivers are not properly installed.
---------- Post added at 01:33 PM ---------- Previous post was at 01:25 PM ----------
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I thought he don't have TWRP installed. If TWRP is installed, then go on with what he said. That is the best solution for you. :good:
avirk said:
You can try one thing if you have twrp and your phone is booting into recovery then do this.
Download any custom rom based on Android N, don't go with RR for now as it is not for newbie cause new build has some issue while flashing.
Download the gapps recommend the opengapps Nano package from the opengapps.org.
Place both zip on your sd card and boot into recovery and then wipe everything like, system, dalvik cache, cache, system and then install the both zip, first rom and then install gapps. Then reboot. I hope it will fix the bootloop issue.
Click to expand...
Click to collapse
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
d1nesh said:
I tried the same, but the flashing process is stuck on "Patching system image unconditionally..." I tried two different ROMs, and in both cases, it is stuck in the same step
Click to expand...
Click to collapse
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
avirk said:
Try with wiping everything, wipe system and internal storage as well, I know your important data will be gone but it will be worth a try. If anything comes up let us know, also what have you tried so far tell us in details so we don't repeat it over and over, also in above post some links are provided try them.
Click to expand...
Click to collapse
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
Try with other pc or change the port for data cable. It seems your system partition got corrupted, also you can mount system partition under twrp and then try to format it.
d1nesh said:
I had tried wiping everything already, still I'm getting this error.
Also i'm getting one more error: Unable to load "/system".
Click to expand...
Click to collapse
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
nazim7 said:
When in TWRP, go to Mount and see if system is ticked or not. If not, mount the system and wipe it. Then flash the rom again. BTW which TWRP version are you using. From where you get it.
Click to expand...
Click to collapse
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
d1nesh said:
System is not ticked when i go to Mount, neither am I able to tick it. BTW, I have twrp-3.0.2-0-athene.img.
Click to expand...
Click to collapse
As @nazim7 suggested you to flash the latest TWRP and then try to flash the rom again, also you can try to resize the partition and try to format it from twrp from the option in twrp. Just let us know what the result come back.
nazim7 said:
So that is the problem. You have to install TWRP latest version. Version 3.0.2 r4 or higher by shreps will work for you. You can find it here. https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
The latest version is 3.0.3 n4. Flash it, mount the system and everything will be good for you
Click to expand...
Click to collapse
There's one more problem like I've mentioned previously. I have the latest drivers even then the device is not being detected via adb when in bootloader, but as soon as I boot into recovery, the device shows up on adb after command. How do I flash the recovery if the device doesn't show up in bootloader on adb?

How do I fix this problem with booting to system?

Hi,
I have the issue that my g4 plus won't boot at from boot loader. I have flashed the 8.1.0 stock ROM, but am unable to boot into the system. It just boots to the dead android no command screen. I have tried the other methods in other threads to no avail. I also tried ADB side loading but it didn't work either as it did not recognize the .zip. Does anyone have any solutions?
Derpsherpa said:
Hi,
I have the issue that my g4 plus won't boot at from boot loader. I have flashed the 8.1.0 stock ROM, but am unable to boot into the system. It just boots to the dead android no command screen. I have tried the other methods in other threads to no avail. I also tried ADB side loading but it didn't work either as it did not recognize the .zip. Does anyone have any solutions?
Click to expand...
Click to collapse
If you try to flash the 8.1.0 stock rom it needs to be extract from the zip. You cannot flash the zip like a custom rom. But that's explained in the instructions in the first post.
Please make this sure.
strongst said:
If you try to flash the 8.1.0 stock rom it needs to be extract from the zip. You cannot flash the zip like a custom rom. But that's explained in the instructions in the first post.
Please make this sure.
Click to expand...
Click to collapse
Oh I fixed it nvm. I just forgot to boot my bad. I guess the thread is useless now.

Bootloop after flashing twrp

Hi xda,
I'm new into the world of flashing so any help would be nice.
I used this tuto:
https://rootmydevice.com/tutorials/root-samsung-galaxy-a40/
and downloaded twrp image from this post:
https://forum.xda-developers.com/galaxy-a40/development/recovery-twrp-galaxy-a40-t3968586
After flash phone restarted as intented but it keeps booting, I tried also some methods how to enter recovery mode while bootlooping but they didn't work out. I also want to flash pixel experience rom.
Thanks for any help provided.
Use the TWRP from this thread.
Your TWRP is not working anymore with actual firmware.
ruffyrisco said:
Use the TWRP from this thread.
Your TWRP is not working anymore with actual firmware.
Click to expand...
Click to collapse
Thanks I'll check that tomorrow
Ok, thanks for help, my ROM is currently booting
flash vbmeta

Categories

Resources