Bootloop after root on Nougat 7.0.0 NBD90Z - Nexus 6 Q&A, Help & Troubleshooting

Hello there!
I’m currently the newest Nougat image (7.0.0 NBD90Z). Before flashing to this version I was on the latest marshmallow image (6.0.1 MOB31H). Initially I dirty-flashed the image, keeping the data partition intact.
However, after I tried to root the phone with SuperSU 3.78 SR1 via TWRP recovery I got into a bootloop. After restoring stock again, I backed up my data partition (nandroid backup) and did a clean flash. On the clean ROM rooting works just fine - when I tried restoring my data partition after root was up the phone got into a bootloop again.
I repeated my experiments with SuperSU 3.78 (non-SR) and 3.76 - same results.
It seems the phone gets stuck quite late into the booting process since it is detected by my PC and listed under adb (as offline, mind you).
I don't even know how to begin to analyze or debug this problem since rooting and even dirty-flashing between major versions has been working for me since Nexus 4 / KiteKat times.
Letting go of all my userdata (at least entirely) is not an option.
Any ideas or directions how I could proceed into tracking down the problem?

Related

[Solved] Official Oxygen OS 5.0 boot loop problem for rooted users

Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.

absolute cluster**** after attempting to move from 4.5.0 to 5.0

So... was tired of some miscellaneous issues with 4.5.0 (rooted w/ Magisk, TWRP recovery) and decided to finally jump to 5.0. Failed initially in TWRP (was using stock 3.1.xx), moved to the OOS internal upgrade option, and actually managed to boot into 5.0 (albeit stock recovery and no root) after that succeeded.
Powered off, connected to PC, fastboot flashed TWRP 3.1.1 blu spark, rebooted into recovery, reflashed blue spark img, flashed OnePlus3TOxygen_28_OTA_060_all_1711160447.zip (went fine AFAIK, "script succeeded, 1.0000"). Cleared Dalvik/cache, flashed SuperSU v2.82... and this is where things got weird. First, flashing SuperSU failed once at the point of compressing the ramdisk. rebooted into TWRP, tried again, and it finished without error messages. Wiped Dalvik/cache once more and rebooted. This time, I got a permanent boot where my OP3T appeared to freeze at the first OP logo on a black background and would go no further even after 10+ minutes. Swapped out my SuperSU zip with a download straight from their website, same frozen boot. Redownloaded OTA_060_all, same thing. Wiped dalvik/cache/system before each attempt, no luck.
Gave up, fastboot -w, reflashed TWRP blu spark, and now even just drying to flash the plain OTA_060 zip results in a "no OS installed" when I try to reboot. When I try to flash either Magisk v15 or SuperSU 2.82, TWRP freezes entirely in the first steps, crashes to a white notification icon, and requires a long power button hold to reboot. I am lost at this point. AFAIK, my OP3T is basically a blank, wiped slate, and I've never experienced full-on TWRP freezes while flashing before blu spark.
In the meantime, I've installed OTA_057 (4.5.1) instead, thankfully without a bootloop, but fully wiped any suggestions?
I've jumped from Nougat to Oreo too. These are my steps: while on nougat open the TWRP recovery (stock TWRP); MAKE A COMPLETE BACKUP; updated it to the latest version (3.2.1.0.- if you have it installed then there's no need for this step); complete wipe; install the OTA using USB OTG; boot to system; run the first setup; (now TWRP might got overwritten just reboot to recovery, if it reboots to TWRP great, move on, if not then reboot to system and install TWRP using ADB); reboot to TWRP recovery; flash Magisk 15 (or SuperSU, but I don't use it so I can't say if it works); flash kernel if you want; reboot to system; check if Magisk/SuperSU works and that's it. At this point I've made another complete backup just in case I skrew up something in the future. Hope I helped! Good luck!
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Tagtag123 said:
Are you using supersu 2.82 SR5.
I had same problem with my 3T going from nougat to oreo.
Click to expand...
Click to collapse
Yep, I believe that's exactly the version I tried I eventually just gave up after doing the complete device wipe through fastboot commands, am now running 5.0 with no problems but have the stock recovery and am not rooted :/ Now I just need to make a backup and then I can mess around and try and find a root method that doesn't basically soft brick my phone...
Even I am running OOS 5.0
The way I rooted is:
Flashed oos 5.0 using TWRP (https://forum.xda-developers.com/devdb/project/dl/?id=27381&task=get)
Boot normally
Reboot to TWRP, flash TWRP using fastboot if you find stock recovery. Then boot to TWRP.
After you in the TWRP recovery, flash superSU 2.82 SR5
Then flash suhide (it helps you hide root from apps which are a bit finicky about root).
This works for me.
SuperSU v2.82-SR5 flashable ZIP:
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
suhide v1.09 flashable ZIP:
http://download.chainfire.eu/1219/suhide/UPDATE-suhide-v1.09-20171001222116.zip
I just followed these steps coming from rooted 4.5.1 and worked perfectly.
https://forums.oneplus.net/threads/guide-how-to-install-oos-5-0-over-rooted-4-5-1.684519/
Unleashed by my rooted OP3T in 8.0

[RESOLVED] TWRP 3.2.3.1 bootloop?

The newest TWRP 3.2.3.-1 does not let me boot into ROM, just brings me back to TWRP again. I have to restore a backed up boot image (with 3.2.3-0) to boot normally. Even flashing TWRP 3.2.3-0 in TWRP does not bring me back.
Anyone else having experiencing this? I have attached my recovery logs.
I was on stock ...and just install los16 without problem... So i dont have problems with TWRP.
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
jhedfors said:
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
Click to expand...
Click to collapse
There is always a risk when flashing your device. One of the reasons why I prefer to flash using Linux was that Windows would have so much going on in the background that I risked the data transfer being corrupt. That said, if you're using Windows, I'd close all programs and especially disable any anti-virus running in the background. Sure, Linux may have a few things running, but I have always found it did a better job multitasking resources than Microsoft Windows with a fewer chance of data loss.
It is probably because after installing Google Apps, your /data partition gets corrupted.
So after installing Google Apps, go to TWRP > Wipe > "Format Data" & reboot.
I've the same problem & this resolves the issue for me.
For me, this did not help. I had to reflash everything from bootloader.
Funny thing is: it just has downloaded and installed an OTA update. With open bootloader.
I ran into this issue yesterday when a bad flash caused the infamous "no bootable A/B" error. After I resolved it and install TWRP I kept being rebooted back into TWRP. The 3.2.3-0 version resolved everything. I really do believe 3.2.3-1 is a bit buggy. I mean it works, but once you really start to use it more than the average user, you start to notice little things.
I too had this same issue. Eventually realized that updating TWRP by flashing zip from TWRP caused it. I had to flash stock boot partition, then follow the process for flashing TWRP as if you are flashing it for the first time (first boot into TWRP and then flash the corresponding zip). This resolved the issue.

Can't install anything - TWRP crash, bootloops after installation and so on

Hello to all.
So, I have the N950F (international Exynos) which generally works fine, but It started being weird for some reason. I installed TWRP on day one, used IronMan ROM since day one and everything worked. I still use IronMan 2.0 (Oreo) since I don't really like the One UI, and I debloated the ROM piece by piece until I overdid it and the Contacts app stopped working properly. When I tried reinstalling (with a full wipe), TWRP crashed and the device would bootloop, so, as usual, I redownloaded the zip (and verified checksums), and the exact same thing happened. As it turns out I can't install anything on the device, TWRP crashes on installation every time and the ROMs bootloop.
Observed hint: the installation always crashes on steps related to the boot image, regardless of bootloader version installed.
Steps taken: tried every available TWRP version (including unofficial ones), tried different bootloaders, tried different ROMs (Oreo and Pie), tried flashing with full wipe and dirty. The problem persists.
After the installation crash I sometimes get "E:Legacy property environment did not initialize successfully. Properties will not be detected.". Subsequent attempt results in Aroma claiming the ROM is for greatlte and current device is "" and stopping immediately.
backup/restore in TWRP works fine which turned out to be my saving grace.
Enclosed are TWRP logs including a large last_log from /cache/recovery and a screenshot of current system version (but the problem persists on every bootloader/system configuration). I went through them, but couldn't find anything relevant, so any help will be greatly appreciated. I might be just dim and missing something obvious.
TalkingChicken said:
Hello to all.
So, I have the N950F (international Exynos) which generally works fine, but It started being weird for some reason. I installed TWRP on day one, used IronMan ROM since day one and everything worked. I still use IronMan 2.0 (Oreo) since I don't really like the One UI, and I debloated the ROM piece by piece until I overdid it and the Contacts app stopped working properly. When I tried reinstalling (with a full wipe), TWRP crashed and the device would bootloop, so, as usual, I redownloaded the zip (and verified checksums), and the exact same thing happened. As it turns out I can't install anything on the device, TWRP crashes on installation every time and the ROMs bootloop.
Observed hint: the installation always crashes on steps related to the boot image, regardless of bootloader version installed.
Steps taken: tried every available TWRP version (including unofficial ones), tried different bootloaders, tried different ROMs (Oreo and Pie), tried flashing with full wipe and dirty. The problem persists.
After the installation crash I sometimes get "E:Legacy property environment did not initialize successfully. Properties will not be detected.". Subsequent attempt results in Aroma claiming the ROM is for greatlte and current device is "" and stopping immediately.
backup/restore in TWRP works fine which turned out to be my saving grace.
Enclosed are TWRP logs including a large last_log from /cache/recovery and a screenshot of current system version (but the problem persists on every bootloader/system configuration). I went through them, but couldn't find anything relevant, so any help will be greatly appreciated. I might be just dim and missing something obvious.
Click to expand...
Click to collapse
Some solutions:
> Firmware reset via Odin. There's a few guides on how to do that, it should fix your issues.
> If you get into TWRP, wipe your directories, mainly ones like /data, and reboot back to TWRP. Not system.
> Try a different rom/zip.
> Try older versions of TWRP if you can. TWRP is recovery.img, not boot.img, so it shouldn't be crashing unless you bonked up recovery.img. You could try flashing the stock one, or flash stock via odin again.

Recover data from soft-bricked (bootloop) phone

Background:
Went to update Magisk via TWRP, phone now bootloops (and gets really hot when charging).
Before I go ahead with flashing an older firmware, to try and get it running again, I was wondering if there was any way of retrieving data from the phone?
I can still boot into TWRP without issue, although I did notice if i go to Install and select source, Internal Storage shows as empty, while External is fine.
Failing data recovery, any suggestions for unbricking it without wiping anything? I've tried un/reinstalling Magisk via TWRP, wiping data/cache/dalvik, but no luck so far.
Thanks
I know where i ****ed up now. By flashing Magisk directly from TWRP.
Tried reflashing it via the guide on page one:
"Instructions for Root Access"
A) Workaround for flashing Magisk with TWRP – for Advanced Users:
Now getting past the warning screen, but not past the Huawei logo.
Going to try remove Magisk altogether, and see if it boots up. If so, will install Magisk again.
Flashed original ramdisk.img and it now shows the boot animation, but doesn't get past there....progress i guess.

Categories

Resources