Database Info

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.

After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?

audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.

Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.

audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!

I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.

TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?

I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...

download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck

hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...

kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda

audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.

kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/

Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...

[HELP] Stuck on Recovery Bootloop after OTA Update (CM14.1) , can't access Fastboot

Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.

I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.

[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date

Same thing happened to me! Where did you get a copy of the stock recovery? Link?

resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.

Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.

corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse

resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!

First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.

Boots to OS but immediately shuts down and reboots to recovery

I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?

toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.

mjp93 said:
Share this with OnePlus team on Twitter too until someone help you here too.
If MTP supported by your TWRP then copy the data? If TWRP is still there.
Click to expand...
Click to collapse
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:

toyanucci said:
I was on 5.1.8 and updated to 5.1.9 but for some reason the phone boots, goes to the OS but immediately shows the shutting down dialog box and reboots the phone to recovery.
I tried reinstalling 5.1.9 with and without root but have the same result. I have tried with and without permanent twrp. The only thing I haven't tried is a factory reset as I am abroad and cannot afford to lose all my info (especially whatsapp as I won't be able to set it back up until 2 weeks when I return home).
Has anyone encountered anything like this or know how to fix it?
Click to expand...
Click to collapse
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.

mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
I'm travelling and the hotel wifi is super slow. I have the full 5.1.9 and I've tried dirty flashing and clean flashing (I did a nandroid backup first). With a dirty flash the phone boots to the lockscreen but immediately says shutting down and reboots, after the reboot it goes to recovery (stock or twrp whichever is installed). After a clean flash it seems to try to boot then just shuts off and reboots to whichever recovery is installed.
I've set 5.1.8 to download which will take HOURS so I'll report back with any update. I pray this fixes it...

toyanucci said:
MTP doesn't work but adb works. I have reinstalled 5.1.9 after doing a full wipe and still the phone reboots to recovery after trying to boot normally.
Can anyone help me please :crying::crying::crying::crying:
Click to expand...
Click to collapse
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.

Pat123 said:
In thw worst case, since ADB works, you can backup your entire internal storage to your computer and factory reset. Use adb-sync for this.
Click to expand...
Click to collapse
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery

mikex8593 said:
Just dirty flash 5.1.8 system update in TWRP, reflash TWRP, reboot recovery, flash magisk. You shouldn't have to wipe data if there were no problems in previous OS and forcing a shutdown shouldn't be due to data anyway. You could also try to dirty flash 5.1.9 again with those steps. Has to be the full ROM.
Click to expand...
Click to collapse
5.1.8 should be flashed again over current 5.1.8?

Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?

MrSteelX said:
Why not just tell twrp to switch back to other slot with working oos. I am missing something that this was not tried yet?
Click to expand...
Click to collapse
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.

toyanucci said:
I did a factory reset (didn't wipe internal storage) after doing the nandroid backup and it had the same issue where it tried to boot then screen went black and it rebooted to recovery
Click to expand...
Click to collapse
I meant take backup through ADB, format everything including data, internal storage, then fastboot flash full ROM zip.

I am having the same exact issue.
Can't restore a nandroid backup. All I get is light blue notification LED. I tried 5.1.8 and 5.1.9. With TWRP right after and without it. Without even magisk. It just bootloops forever. If I install 5.1.9/5.1.8 full zips, twrp, reboot recovery, magisk. It just reboots into twrp. I can't even install any of the full ota zips. It wont get past the android boot animation when I just want to flash the ota zip only. Can't get out of twrp. Luckily I was able to backup everything, but don't know how to proceed further allowing me to regain usage of my phone.

To me, this is sounding like something did not flash right with vendor partition.
if a full wipe of System, data, internal storage, the whole 9 yards doesn't work. The only option I see that should work is the mega unbrick thread. https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

MrSteelX said:
To me, this is sounding like something did not flash right with vendor partition.
Click to expand...
Click to collapse
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.

garz said:
Any suggestions how to fix this. I am hoping I dont have to use the MSM tool and start all the way from scratch.
Click to expand...
Click to collapse
Did you make sure the download was not corrupt before flashing? OnePlus6Oxygen_22_OTA_013_all_1807130145_92ea1c670c0fae.zip MD5 61EAE0DA48C6B3914F48F3E6EA99A74B

Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/

garz said:
Yes, everything matched up. I guess I need to start from scratch.
---------- Post added at 10:25 AM ---------- Previous post was at 10:08 AM ----------
This guy's tool worked like a champ for me. Didn't have to delete everything in storage.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/
Click to expand...
Click to collapse
Funny, I was about post that link but i see you found it first. It is also good that it fixed it for you.

As far as TWRP backups, you only need to backup data. You can just install the full ROM zip file and restore data to get everything back if you have issues with nandroid restore. Just don't forget to flash TWRP before rebooting or you will need to fastboot it again.

Maybe an issue with battery calibration. Try checking the battery when the phone just boots. If it says low battery and because of that its shutting down then its just a software error and just try to turn in the phone with charger connected to check if tgats the problem. If that dosent work try the oneplus 6 mega unbrick guide and return to stock oos 5.1.5 using snapdragon msm recovery tool. For detailed info see tge OP6 unbrick guide on xda. Tell me if it works

toyanucci said:
I tried changing slots in twrp. Slot A boots to lockscreen then powers off and boots to recovery. Slot B doesn't boot at all and just shows a light blue notification LED.
Click to expand...
Click to collapse
One question, when you manually change to slot B, you're in a black screen with blue notification LED right? If that doesn't even go fastboot, how do you get out of that slot into the other one again to the boot-recovery loop?

phone boots into bootloader mode, even with a fresh rom flash??

Hi. i need some help.
I have a huge problem regarding getting my one plus 6 back up and running.
Here is what i did.
Downloaded a rom, gapps and magisk.
wipe in twrp, install, rom, gapps. worked fine, booted up rom.
when i flashed the lastest version of magisk, it boots into bootloader.
Then i did a DATA wipe. start a fresh boot.
*booted twrp via adb.
* pushed, rom, gapps, twrp into sdcard.
* installed, rom, twrp, gapps. reboot.
goes directly into boot loader.
WHAT DO I DO? my phone is screwed.
EDIT: Room bug. nothing wrong with phone or recovery. just bug in the rom.

saitek1911 said:
Hi. i need some help.
I have a huge problem regarding getting my one plus 6 back up and running.
Here is what i did.
Downloaded a rom, gapps and magisk.
wipe in twrp, install, rom, gapps. worked fine, booted up rom.
when i flashed the lastest version of magisk, it boots into bootloader.
Then i did a DATA wipe. start a fresh boot.
*booted twrp via adb.
* pushed, rom, gapps, twrp into sdcard.
* installed, rom, twrp, gapps. reboot.
goes directly into boot loader.
WHAT DO I DO? my phone is screwed.
Click to expand...
Click to collapse
Wipe all.
Boot to twrp
flash ROM
Reboot twrp
For flash gapps
Boot to ROM
Setup and enjoy

DaveHTC200 said:
Wipe all.
Boot to twrp
flash ROM
Reboot twrp
For flash gapps
Boot to ROM
Setup and enjoy
Click to expand...
Click to collapse
already done this. twice. still goes into bootloader on every boot.

saitek1911 said:
already done this. twice. still goes into bootloader on every boot.
Click to expand...
Click to collapse
Save everything from SD card to PC and try with:
fastboot -w
Then just try installing ROM
And rebooting to it.
Worry about gapps etc after,.
Possibly bad download too

Did you try booting into the other partition. A/B?

Use magisk 16.4 and then you can update thro the app. 16.7 has a flash bug

From seeing him in another thread I think he got it

saitek1911 said:
already done this. twice. still goes into bootloader on every boot.
Click to expand...
Click to collapse
when a wipe does not get it working, then ( sadly ) go to the next step of "format data", but "BACKUP" stuff you want to keep ( ie. /storage/emulated/0/Download ) to pc first . . .
( it's what I had to do )

Same issue here...
Tried to fromat data but still boot into fastboot.
Rom: Havoc

saitek1911 said:
Hi. i need some help.
I have a huge problem regarding getting my one plus 6 back up and running.
Here is what i did.
Downloaded a rom, gapps and magisk.
wipe in twrp, install, rom, gapps. worked fine, booted up rom.
when i flashed the lastest version of magisk, it boots into bootloader.
Then i did a DATA wipe. start a fresh boot.
*booted twrp via adb.
* pushed, rom, gapps, twrp into sdcard.
* installed, rom, twrp, gapps. reboot.
goes directly into boot loader.
WHAT DO I DO? my phone is screwed.
EDIT: Room bug. nothing wrong with phone or recovery. just bug in the rom.
Click to expand...
Click to collapse
Had the same problem, boot to temporary TWRP with the fastboot command "fastboot boot <twrp img>", wipe /system and then try flashing stock ROM via fastboot, it worked for me, hope it helps. Good luck! :good:

i accidentally flashed a custom rom over oxygenos lol help (really though help)

Hi.
So this was pretty stupid of me. I was trying to flash LiquidRemix onto my OP6, but I forgot to wipe the system partition. Flashed the rom, then blu_spark twrp, and rebooted into recovery to flash gapps and all. Got a black screen with a static LED. Didn't think that was a big issue cause this has happened before with normal TWRP on OB6 or OB7. Tried hard resetting to see if I could get into system, same result. Tried fastboot flashing 9.0.2, no help. And finally tried flashing OB9 via fastboot, and also no help.
I've reverted back to my tiny S6 and have sent repair request to OP. I haven't gotten anything back yet, so I thought in the mean time, I'd look for help on XDA and try to fix it before having the chance to send it in.
Any help/advice would be greatly appreciated.
Cheers
// EDIT
Figured out how to fix it. Used the MSMDownloadTool to unbrick my device. Worked wonders. Thanks to r/oneplus Discord

I did something like that I had to format data after I flashed the stock rom

mightyblazer said:
I did something like that I had to format data after I flashed the stock rom
Click to expand...
Click to collapse
How did you get to format? I really can't get into the OS or recovery at all

I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again

mightyblazer said:
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
Click to expand...
Click to collapse
I'm able to get into fastboot, but even if I fastboot boot [insert twrp file name here], it'd still result in the blank screen and static LED

Hmm I don't know then sorry

Try
fastboot flash boot twrp.zip
Then
fastboot reboot
You will need to use full stock rom first before doing anything else though.

I was in the same boat as you the other day. I flashed different versions of twrp until i managed to boot one because some twrp isn't compatible with pie.

Lol I never wipe system...

Might sound like a "hard-bricking" issue since you cant boot into the OS nor recovery. There 's a hard brick recovery guide, but it'll put you down to oreo OOS: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
As long as you can boot into fastboot, you can follow the guide's process with no problem.