Database Users

Nexus 6p with Android 7.0 in bootloop cannot access recovery

Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA

Found this on Nexus 6p help forum. Haven't tried it though so I'm unable to confirm if it works or not.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE

@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode

ciocu said:
@sirluigi, this EXACT thing just happened to me ..
stock nougat, only bootloader unlocked ((( and since I've got no access to recovery and no Nougat image, I don't know what to do next
minicoop7, unfortunately, for that guide I need to go into recovery mode
Click to expand...
Click to collapse
Have you tried using fastboot to temp boot to recovery?

fastboot boot twrp-3.0.2-1-angler.img
downloading 'boot.img'...
OKAY [ 0.409s]
booting...
OKAY [ 0.680s]
finished. total time: 1.097s
Click to expand...
Click to collapse
same behavior, nothing but a bootloop
I'm dowloading an official MM image, just to get the stock recovery and see if I can temp boot in it
edit: not possible, I even tried to flash twrp, I tried flashing stock recovery from MTC20F.. tried to temp boot in both, all with no luck and with phone constantly alternating between the "Your device cannot be checked for corruption" screen and the white Google screen with the open lock.

sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
sirluigi said:
Hi Guys,
I'm Kinda new about making a new thread, so if anything's wrong let me know.
Just last evening my nexus 6p (on Android 7.0 official) got into a boot loop from a normal state. It just boots & right after when the white google logo transforms into 4 round object, it just reboots (it takes about 3-5 secs). I can access the boot loader but was unable to access to recovery from there as that takes it to bootloop again. I've tried flashing it, but since i had already updated to Nougat official version & the official image for 6p is yet to come, i tried with some earlier version of Marshmallow. but that failed as well. can it be that i need to select the right version of factory image as i really do not remember my old marshmallow versions anymore.
It seems i'm out of options right now. :crying:
Any advice guys??
TIA
Click to expand...
Click to collapse
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Unfortunately, this didn't work for me.

I believe you should be fine with just trying to flash an earlier recovery version using fastboot... if you're trying to save your data and then factory flash MM and then restore your data to the phone, you should be able to use fastboot pull and then copy them back once you've got a working device by simple copy from windows.

disbeyad999989 said:
Guys its very simple, flash the stock mtc20f image first. After that boot it, it wont work but don't worry. Onece it bootloops go into bootloader and fastboot flash twrp 3.0.2-0. once thats done boot into twrp recovery. Onece in twrp make a backup of the image you just flashed that don't work. Once thats done mount system in recovery. Once mounted plug phone into computer and open the twrp folder you will see on your internal wich will have the backup that you just made. Transfer an old working backup into that folder that way twrp will recognize that backup. Once the backup is in the folder you shoukd see 2 backups in there, your new one that doesn't boot and your old one that does work wich you just put into the twrp folder. Once done go to restore and restore the backup of the working rom you just put in there, make sure to check off all on restore. Once done reboot system and it should boot. This will only work if you have a backup of an old working rom.
---------- Post added at 01:13 AM ---------- Previous post was at 01:00 AM ----------
OMG I finally got mine to work
I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked
Let me know if it worked for you guys or if you need any more help
Click to expand...
Click to collapse
Can you elaborate the steps pls? also have you had an earlier back up of your phone which i don't have?

Has anyone been able to get this to work without being able to get into TWRP? I can't get into recovery whether it is a temp boot to it, or fastboot flash either version..

I have compiled a list of the 20+ methods from various users in THIS thread. It's the second post.

Stuck in a bootloop still @tr4nqui1i7y but will try your methods as well... Fingers crossed..

So I do not if this may help anyone who as run into this issue but still may want to retrieve their data before formating their data or factory resetting. While running TWRP 3.0.3 and flashing the latest 7.1.1 files for angler. I would sometimes be able to boot into the recovery like 3/10 tries ( from the bootloader menu). My data was encrypted and it woul freeze constantly when trying to decrypt soo i decided once I finally got it to boot again in the recovery menu(TWRP after hours mind you) I let the phone stay idle for a few mins should the cpu would cool down that my battery percentage would drop around 41% and the tried to decrypt data which went tru successfully. I retrieve what I Could and it froze during a process of a nandroid backup and started bootlooping again. I believe the battery percentage may be linked to the early shutdown issues that many user were reported having and the bootloop of death we are experiencing. Hopefully this info may help someone else.

OP5 bootloop with every ROM

Hey fellas,
so I rooted my phone and tried to install some Magisk modules, but after rebooting it got stuck in the TWRP bootloop. So I flashed the Nandroid backup and it got stuck in the OOS boot animation. After that I tried reflashing OOS, but it didn't change anything, so I tried Lineage OS and now it won't even get past the Oneplus logo at the beginning and keeps restarting.
Thanks in advance
EDIT: when I flash the stock ROM through TWRP it installs normally, but then when I try to reboot it says there is no OS. So I flashed the stock OS to try adb sideload, but my pc says it cannot read the zip.
I also decrypted my phone through the OP5 Decrypt App, before the bootloop it worked for some time.
Of course I wiped everything before every action.

if you can bootup into recovery, try go into advanced and format data and system.
if you can't your last chance is using adb - flash a default rom.

Is it any different than wiping everything? Because it didn't do anything. I can access both twrp and fastboot so I guess it's not that bad

sounds like you went from unencrypted to an encrypted rom and your data is encrypted, or visa versa.

yep, it's vice versa, I used the OP5 Decrypt App after rooting. Is OP5 encrypted by default?

If you've tried the Android 8.0 Rom, just go to the official OP5 support site and download stock rom, flash it via ADB sideload if you can. (Don't forget to format data etc etc..) and restart from scratch.
Unlock BL if it's relock, then flash TWRP and go for a custom ROM. That's what I did, happened to me 2 days ago.f
EDIT : Oh you just flashed Magisk.. Well, try this anyway.

I tried flashing Lineage, but I can't install Oxygen

Ok, so apparently OOS boots up only after relocking the bootloader. And I had to make adb use more RAM to get sideload to work.

Can't unroot, stuck on MI Logo.

Hello. I rooted my phone using this guide en.miui .com /thread-415853-1-1.html
Everything works good, but then I tried to move an app to system with Link2SD but it said "write error no space left on device" and system space was 100%. I moved some system apps to user apps to make space (Mi Cloud, Mail, Calendar) but the problem persisted so I decided to leave it alone and not do anything. I then proceed to unroot by uninstalling with Magisk Manager, reboot and it got stuck on Mi Logo. I even left it for several hours but nothing happened.
I found out that if I enter fastboot and then TWRP, I can flash Magisk again, reboot, and it is not stuck on MI Logo anymore, the system boots perfectly and all my files and apps are there same as before. But how can I unroot without getting stuck on MI Logo? Is there a problem with Magisk or something? What else can I try?
I'm thinking my best choice is to flash the Mi ROM again using TWRP, is that correct? Any help would be appreciated, I'm still learning about this.
Currently I have MIUI Global 8.5.5.0 Stable (MADMIED) and I just downloaded the zip file of that rom.

Ok I worked it out. I'm going to post my solution in case someone else has the same problem.
Since I was able to boot system normally if I flashed Magisk again, I did that, made a backup of my whatsapp chats and saved a backup of my files in MI Account.
Then I reboot TWRP recovery, wipe all (factory reset) and flash my ROM MIUI Global 8.5.5.0 Stable (MADMIED). Phone started, root was gone, restored my backup.
Then I reboot again TWRP, flash Magisk and Phh SU and everything else in the guide linked above. Installed Link2SD, deleted some system apps (Youtube, Google Play Movies and Music and some others), and then I was able to move the app I wanted to system.
Rebooted phone to system. Then uninstalled Magisk from Magisk Manager, reboot phone, and everything worked ok!

Thanks, im planning on flashing twrp and magisk, so this could become handy ?

Try flashing these, worked like a charm for me.
https ://android file host. com /?fid=889964283620756562
https ://android file host. com /?fid=745425885120731943
just remove the spaces and you are ready to go!

Found a better Solution!
If you are stuck on the MI logo after the unroot that's because of the verity check of the ROM. So if u could boot into the custom recovery(TWRP) then just simply flash the lazy flasher zip file and then you are good to go, the ROM will normally boot with all of your files and apps.

¡HELP! Can't update to Android Oreo (Root user)

Hi guys.
I have bought my Xiaomi Mi A1 like 4 days ago, I'm so happy with it, it's damn awesome. Afer one day of having it in my hands I decided to root it, and one day after I rooted it I saw that the Android Oreo update was avalible, so I decided to unroot the phone to update it and then root it again, so when I flash the Magisk uninstaller in TWRP it brick my phone, bootloop, and if I flash Magisk again it boot perfectly, I think that when I installed magisk for first time it didn't backup the original boot image, so when I flash the uninstaller it gimme boot loop. I figure that it didn't backup my stock image cos' when I flash the uninstaller it says me something like "no backup found". Even I have tried to flash the boot image of a rom of my actual OS but didn't work too.
I think that an option is erase ALL about the phone in TWRP, when I say all I mean ALL OF ALL (There is an option in wipe at TWRP that allows to do that) and then flash in MiFlash or in a zip file the OS but I think it's unnecesary and there are more options to do.
UPDATE WHILE I WAS WRITTING
I have bricked it, lul
I restore my backup again but this time didn't boot, but still can boot into fastboot and TWRP, seems like I'm not able to say happy year to friends this night...

Just flash the last full fastboot rom using MiFlash. You can save your userdata if you choose the option to save user data. Then do the update.

Just flash stock ROM using mi flasher tool and erase all the data...

Update
Hey another update here! I have uptaded to oreo succesfully Thanks to all, but I have a doubt... I did a backup when I had nougat, with all my apps and that stuff, Can I restore all of it to Oreo? I did backup of system and data

Do you Still Have root???

Recovery changes back to MI recovery after installing either custom recovery

Today I finally made the step of switching to a custom recovery/rom on my Xiaomi Mi 9T. The first and last time installing a custom rom (2 or 3 years ago on ZUK Z2) was quite a long time ago, so I checked several videos showing bootloader unlocking and all those steps.
one video used orangefox and I tried to flash it onto the device. The guy in the video used Yuware to flash orangefox and it successfully flashed it and I could also boot into it. For my Z2 I used a usb-c to usb-a connector and I would have gapps, rom etc on a USB drive. But I didn't have one on me so I booted into the phone to place gapps, rom and vendor (new to me) by dragging the files onto the phone storage using my PC. Once I booted into recovery the custom recovery was gone and it went to MI recovery 3.0
I tried to flash TWRP with ADB and Fastboot, and I managed to do so but still, when I wanted to go back to TWRP after booting into the phone it went back to MI recovery.
This is really annoying and there are some similar posts on forums but I haven't found a solution. I hope somebody can help me

jipderkman said:
Today I finally made the step of switching to a custom recovery/rom on my Xiaomi Mi 9T. The first and last time installing a custom rom (2 or 3 years ago on ZUK Z2) was quite a long time ago, so I checked several videos showing bootloader unlocking and all those steps.
one video used orangefox and I tried to flash it onto the device. The guy in the video used Yuware to flash orangefox and it successfully flashed it and I could also boot into it. For my Z2 I used a usb-c to usb-a connector and I would have gapps, rom etc on a USB drive. But I didn't have one on me so I booted into the phone to place gapps, rom and vendor (new to me) by dragging the files onto the phone storage using my PC. Once I booted into recovery the custom recovery was gone and it went to MI recovery 3.0
I tried to flash TWRP with ADB and Fastboot, and I managed to do so but still, when I wanted to go back to TWRP after booting into the phone it went back to MI recovery.
This is really annoying and there are some similar posts on forums but I haven't found a solution. I hope somebody can help me
Click to expand...
Click to collapse
Right after flashing TWRP from Fastboot, immediately reboot to TWRP:
>> fastboot oem reboot-recovery
You must enter your Android unlock pin for TWRP to be able to access Data (and Internal storage)
After those two steps TWRP should stay - if still not (?!) you would also need to flash lMagisk patched boot image or flash Magisk from TWRP (with that, TWRP will definitely stay, it always does ) or VBMeta ((I'm not familiar with, never used, google about)

zgfg said:
Right after flashing TWRP from Fastboot, immediately reboot to TWRP:
>> fastboot oem reboot-recovery
You must enter your Android unlock pin for TWRP to be able to access Data (and Internal storage)
After those two steps TWRP should stay - if still not (?!) you would also need to flash lMagisk patched boot image or flash Magisk from TWRP (with that, TWRP will definitely stay, it always does ) or VBMeta ((I'm not familiar with, never used, google about)
Click to expand...
Click to collapse
Really appreciate your effort, but it did not work :/. The command let TWRP boot and also asked for my pattern. But when I turned it off, and went into recovery mode it just went straight into the mi recovery again.
Magisk is actually a root right? I do not have any experience when it comes to that. If Magisk lets me keep my TWRP, I'd be happy to install it. But will it affect any other apps, causing me to get bypasses and stuff? Because I use snapchat on a daily basis but i'd find it disappointing if I have to get through several fixes if I went on to install Magisk. Or is that something I will just have to accept?

jipderkman said:
Really appreciate your effort, but it did not work :/. The command let TWRP boot and also asked for my pattern. But when I turned it off, and went into recovery mode it just went straight into the mi recovery again.
Magisk is actually a root right? I do not have any experience when it comes to that. If Magisk lets me keep my TWRP, I'd be happy to install it. But will it affect any other apps, causing me to get bypasses and stuff? Because I use snapchat on a daily basis but i'd find it disappointing if I have to get through several fixes if I went on to install Magisk. Or is that something I will just have to accept?
Click to expand...
Click to collapse
With Magisk hide you will e.g. get SafetyNet to pass, currently it should be failing for you because of detectimg that Bootloader is unlocked (if you are on stock firmware)

everytime i updated the MIUI, the recovery went to stock. then i install twrp, then reboot directly into twrp, then flashed recovery again in twrp, then rebooted...
after this, the recovery did not change to stock anymore.

Hello, I also have this problem, I have been offered several solutions, but I am still in doubt:
https://forum.xda-developers.com/mi-9t/help/unable-to-restart-twrp-1-st-installation-t4158409
https://xiaomi.eu/community/threads/twrp-restart-problem.58260/