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?
So here are a few things I have been through in the past 48 hours:
I flashed a custom ROM (FreedomOS) for the 3T. Could not get OK Google to work and it is essential to me especially when driving. Other people had mentioned every custom ROM was like this at the moment so I made the switch back to factory. This is where the hell begins. I wanted to try out Magisk so I could play Pokemon GO and use Android Pay, and I thought "oh what a perfect time to do just that". 4 hours of work and the SafetyNet was still tripping, only to find out I needed Magisk 13.0, which is incompatible with the OP3T boot image. Now, that could have been because I installed SuperSU prior and that patches the boot image but I had been through enough to the point of just going stock with SuperSU only. So about 10 dirty flashes later and a few hours of waiting for TWRP to load (F2FS can suck my @#$*), I find out that if you don't want to lost your data partition, there is only one very specific way to install SuperSU.
1) Wipe system and caches
2)Install OOS full rom
3)Boot into OS
4)Reflash TWRP (because OOS removes it)
5)Flash SuperSU
6)Boot into OS again
7)THEN, and only THEN can you install additional things such as ARISE or custom fonts
It appears after you flash the factory ROM through TWRP, TWRP loses all commands. So anything flashed after that doesn't actually do anything. I thought maybe it was because the new recovery is there and so maybe TWRP just needed to be reflashed before the OS was even booted, that however, resulted in a beautiful slew of corrupted fonts, no root access and broken hardware keys (even the power button). So please, learn from this XDA users, as I have the hard way. Now I'm off to go change F2FS to EXT4, fun stuff.
EDIT: On top of everything I just said, it seems none of the SuperSU zips are working now. Does not affect my phone whatsoever. It's almost like it isn't mounting /system...
EDIT 2: Great. Rooting now bootloops me and the logcat is saying AtCmdFwd service errors and BindNDK sensor server unavailable. I'm going back to FreedomOS and will just suffer from never having OK Google again.
EDIT 3: FreedomOS no longer even starts booting. Stuck at bootloader logo. Guess I'm flashing stock OOS unrooted for now. Going to have to deal with ugly default fonts and crappy audio
Try blusparks twrp for OnePlus 3t.. that fixed a lot of my issues with flashing, instead of supersu try magisk instead.
Install twrp - OOS - Magisk - Kernel - what ever else.. but see if it boots. If not, try holding the power button for 12-15 seconds until the screen goes black but the notification led turn red.. plug your phone into the computer and do a unbrick from there with the msm tool.. once it all boots, flash a custom rom over the stock rom and then factory reset from there, I'm just throwing ideas out there.
1. Factory reset.
2. Install official OOS.
3. Reboot to recovery.
4. Install TWRP.
5. Install Magisk, custom kernel, debloater etc.
6. Reboot to OOS.
When upgrading to newer OOS version, skip factory reset. I never wipe caches and everything works. If safety net fails, check that hide is enabled on Magisk settings. If still failing, use Universal SafetyNet Fix.
Forget SuperSu, Magisk does same thing. And with Magisk you can play PoGo. Forget EXT4, it doesn't give you anything, it's going to be history.
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Solved
xKroniK13x said:
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Click to expand...
Click to collapse
Ok, I will eventually try blu_sparks TWRP (that was the plan anyways), but I am back in working order. So Magisk did not bootloop my device, and v13 works on OOS. It wasn't working on FreedomOS but it even passes SafetyNet on OOS. I have ARISE and Dolby installed and couldn't be more satisfied. Did not have to wipe /data, it's like the whole thing never even happened. I will likely change to EXT4 as soon as I get the chance to backup my data partition, I haven't seen any benefit to F2FS whatsoever. Appreciate the tips, XDA rocks!
EDIT: Still takes forever to boot blu_spark TWRP but eh, I'll keep it. Will update when switch to EXT4, only reason to switch
I do the flashing in a rude way
1. Flash OOS from TWRP.
2. Flash magisk, arise, etc..
3. Reboot
4. Boot into recovery, flash any custom kernel etc..
Changing to ext4 is not required, if you are on OOS. f2fs is way better in performance over ext4 for the stock/freedom.
Sent from my OnePlus 3T using Tapatalk
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.
Here's what's happening:
I'm currently on stock V11.0.14 on both slots, magisk rooted and data is encrypted.
Both slots are bootable, and PBRP (recovery) successfully detect and decrypt data partition.
Not sure why, but if I try the usual process to update, uninstall magisk and apply System Update, it always fail, I've reflashed the stock ROM on both partitions and got the same result.
Then I tried to manually flash the full rom (any version greater then V11.0.14) to the inactive slot but it always fails to boot.
Something that I've noticed is that if I boot PBRP with the updated partition active, it fails to detect that the data partition is encrypted and I think that Android is facing the same problem, the updated version isn't detecting the encryption as well.
If I flash V11.0.14 back, it boot.
Any suggestions/solutions rather than full data wipe?
Cheers!
Just today I wrote comment on problems with updates to versions >= 11.0.15.0 :
December 2020 Security Update now available
Hy, December Update out now. Greets
forum.xda-developers.com
As for TWRP - I regard as working 2 versions only:
https://forum.xda-developers.com/t/recovery-unofficial-teamwin-recovery-project.4209151 by @Nebrassy
and older https://forum.xda-developers.com/t/...-mi-a2-jasmine_sprout-by-d4e8ede8f1f2.3941096 by @d4e8ede8f1f2
I got this weird non-Tmobile XT1965-T phone that was discussed elsewhere (XT1965-T non-Tmobile). I only rooted boot.img, kept stock recovery & /data encryption, as in this link. But then I flashed a program into /system (my bad!) by accident. So now I cannot revert back to stock boot.img, and apply the new OTA because the checksum is messed up for /system.
My current version is QPWS30.61-21-18-7-3. I tried to do A/B switch, and boot the prior version of the system (which should be full stock - QPW30.61-21-18-7), but no go. Does anybody know why the prior version in the other set (A/B) would not boot? Would it boot if I fully wiped /data?
I thought I could boot QPW30.61-21-18-7 from the older partition, and let it update a couple of times, then root again. But seems that is not possible? What is blocking the boot?
P.S.
It seems like I could get the same stock ROM here which currently sits in my unbootable other A/B partition (LAKE_QPW30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip):
MOTO G7 PLUS NO SERVICE
I just bought a G7 Plus on amazon for $122 which is produced in 11/05/2020 with the latest version of rom. Model XT1965-T Currentlly, I already unlock the bootloader. I have installed the mokee rom and lineage os for more than 15 times. The...
forum.xda-developers.com