Database Users

OP2 cannot upgrade from Oxygen OS 2.2.1/Cannot flash TWRP versions newer than 3.0.2-0

So.... Pokemon Go has a lot to answer for......
I have run into a really strange problem when trying to install an OTA on my *unrooted* Oneplus 2. I have been trying to fix this for days but I have completely run out of ideas.
I originally had a working stock Oxygen 3 (Marshmallow) rom with TWRP recovery on my device (not sure of the version). The device was rooted and apart from not being able to install OTAs, I was fairly happy with the setup. Then along came the Pokemon GO update that banned rooted devices. Ok, "big deal" I thought. I was quite content playing Ingress instead (a far better game by the way that doesn't rely on a "pay to win" structure). I really wasn't too worried but then I found out about "systemless root" and "Magisk". I thought that if I installed this correctly I could still play a bit of Pokemon GO when I wanted to and could toggle a root button in Magisk Manager to install OTAs when they became available.
This is where the problems started.
I followed a guide on how to unroot and install Magisk and "Phh's Superuser". The problem was that the Phh Superuser was being denied permissions for Magisk Manager, there were no pop up notifications prompting me to give it access, just toast notifications. I couldn't for the life of me figure out how to give it permission so the "enable root" slider button kept sliding back, not allowing root. This is when I used SuperSU ver 2.76 (Magisk version) and it seemed to work fine. I now had a stock Marshmallow rom with TWRP and Magisk Manager all working exactly how they should be. I could toggle root and play Pokemon GO, then return to a rooted state when I needed to.
"Awesome, mission accomplished." I thought. Now I just need to toggle root off, download the latest OTA and install it through Flashfire.
First I made a complete nandroid backup (as I've done with other devices many times before) through TWRP. I even copied the backup folder to my PC in case something went wrong.
Well, this is when the nightmare started.
The first mistake I made was to use Flashfire when it clearly stated that Oneplus devices were currently untested. Not sure if it was a big issue or not, but it was a mistake none the less. The second mistake I made was to not stop the stock recovery being replaced when prompted before the reboot. I assumed (and it even states in the app) that the custom recovery should be reverted back to the stock recovery when attempting to apply OTA updates.
So I went ahead and rebooted, waiting for the OTA to install. I'm fairly sure from memory that it went into the stock recovery, flashed the OTA and restarted.
This is when the phone soft bricked.
"Oh well, that is why I made the backup." I thought.
I reflashed TWRP in fastboot mode and attempted to restore my backup. No dice, the phone was still soft bricked.
(And by "soft bricked" and "boot looping" I mean the Oneplus logo was in the middle of the screen, "Powered by Android" was at the bottom and the two blue LEDs for the buttons either side of the fingerprint scanner/home button remained on. This for me was the tell tale sign of the soft brick because these two light go off after a few seconds after rebooting usually.
So from here I have tried EVERYTHING. All I really want now is a working stock (rooted) Marshmallow rom with TWRP. I have downloaded many different full rom zips and attempted to flash them through TWRP with no success, I have returned to stock recovery and tried flashing signed roms with no success, I've even tried flashing the official CM13 rom for Oneplus 2 (with the correct GAPPs and kernel) through TWRP with no luck.
But here is where it gets interesting......
There are a few things that are really weird...
1. I have always been able to get into Fastboot mode and ADB and Fastboot commands "work".
* Operations succeed but don't stick (for example trying to flash TWRP versions 3.0.2-1 and 3.0.2-2 through Fastboot mode result in no recovery being there at all.
2. I can flash TWRP recovery though Fastboot mode but ONLY VERSIONS 3.0.2-0 and lower. I can also successfully flash the stock recovery.
3. I can flash OxygenOS 2.2.1 but NOT ANY VERSION RELEASED AFTER THAT. Doing so results in the soft brick "bootloop" I mentioned earlier.
4. Attempting to flash the official CM13 rom for Oneplus 2 doesn't work either. Originally I got the error 7 message, but after editing "Updater-script" in the rom and re-zipping, the process seemed to work fine in TWRP but the reboot gave me... you guessed it... a softbrick.
I have flashed custom roms on a few different devices before so I'm not a COMPLETE newbie when it comes to this stuff, but I am by no means a developer or even anything close to one. I have bricked this phone in the past (long story, involved getting it without an invite and it being shipped to me with spyware on it) but I used a guide very similar to this and it worked a treat.
www(dot)androidbrick(dot)com/unbrick-oneplus-one-two-3-qualcomm-hs-usb-qdloader-9008
So, thinking that this process would format all partitions and start me from scatch I tried it. It worked fine but I was still unable to upgrade from Oxygen OS 2.2.1 or install TWRP versions 3.0.2-1 or 3.0.2-2.
I have tried all sorts of things. I have wiped, flashed and wiped again. Factory resets, dirty flashes, clean flashes.... everything. All sorts of different sources for the TWRP images and Oxygen roms... nothing seems to work.
It's just so weird considering it's not a hard brick... just a soft brick.
So I really need my phone so I am sitting on this current build because it is the only one that works.
Here are some details of the current build I am using. (using CPU-Z app)
Model: Oneplus 2 (ONE A2001)
Android version: 5.1.1
Oxygen OS version: 2.2.1
Bootloader: Unknown
Build ID: ONE A2001_14_160226
Java VM: ART 2.1.0
OpenGL ES: 3.1
Kernel Architecture: aarch64
Kernel version: 3.10.49-perf+ (56)
Root access: Yes
Super user app: SuperSU Free v2.46 (Chainfire)
OEM unlocking: Enabled
USB debugging: Enabled
And these are some of the ZIPs and IMGs that refuse to be flashed to my device.
TWRP-3.0.2-1-oneplus2
TWRP-3.0.2-2-oneplus2
Grarak's TWRP recovery IMG for Oneplus2 (modified to install CM13) according to this guide:
missingtricks(dot)net/oneplus-2-official-cyanogenmod-13
cm-13.0-20160924-NIGHTLY-oneplus2
OnePlus2Oxygen_14_OTA_019_all_1606041303_bd42fc5cc5cc4ab2
And also my TWRP backup named 2016-09-16--09-44-09
I am really at a loss as to what to do next. ANY help ANYONE could give me would be greatly appreciated. I have been all over the net looking for ways around this bt have had no luck.
As I've said, I'm not a huge tech head, but I'm not a newbie either. The only thing I can think of is that somehow one of the partitions (maybe boot? ) may have been corrupted somehow when messing around with systemless root. But I don't know how considering it's "systemless". If anyone knows how to check for corrupted partitions on the Oneplus 2 please let me know and I'll try it. Maybe formatting these partitions might help (????), but I don't want to permanently brick my phone.
But I don't know how I've got this particular build working if one of the partitions has been corrupted. And the corrupted partition thing is just a guess.....
Please, anyone, someone point me in the right direction. Again, any and all feddback is welcomed and would be very much appreciated.
This is all Pikachu's fault.

Kamakiriash said:
A very long post...
Click to expand...
Click to collapse
The normal way too update from OOS 2 to OOS 3 is:
Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
Reboot recovery via TWRP so that you now have a recovery that's compatible with the new bootloader
Wipe data, cache & dalvik-cache (but not internal storage)
Flash the OOS 3 signed flashable zip again to update the system
Flash one of the modified SuperSU zips if you want root
Reboot system
All the files you need are in post #1 of this thread.

Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:

Kamakiriash said:
Thank you so much Spannaa!
I was clearly missing a vital step here and let it be a lesson to anyone else in this situation....
As Spannaa said......
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
4. Wipe data, cache & dalvik-cache (but not internal storage)
5. Flash the OOS 3 signed flashable zip AGAIN to update the system.
Again, thankyou Spanna for your quick and accurate response.
The order in which you flash zips and imgs is very important it seems.
You really saved me.
I restored the TWRP backup and I am back to where I started.
Is it now possible to apply OTAs when I toggle the root off in Magisk manager and install using the stock recovery? What do you think would be the best way to do this?
And would it be worth moving to the official build of CM13 for Oneplus 2?
Thanks again, Spannaa. :victory:
Click to expand...
Click to collapse
Glad you're sorted.
Not sure about Magisk as I've never used it.
CM13 is OK but whether it's worth you moving to it is your choice. Personally, I prefer TipsyOS!

Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
1. Flash the OOS 3 signed flashable zip via TWRP to update the bootloader and firmware
Click to expand...
Click to collapse
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
2. Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option
3. Reboot recovery via TWRP SO THAT YOU NOW HAVE A RECOVERY THAT'S COMPATIBLE WITH THE NEW BOOTLOADER!
Click to expand...
Click to collapse
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?

Aood said:
Hi,
I face the exact issue with same Oxygen OS and TWRP versions mentioned, I have tried the above steps but there are some problems:
when I checked the option (Zip signature verification) in TWRP, the installation failed with error "Zip signature verification failed! Error installing zip file '/sdcard/oneplus.zip'", but it's successfully installed when I unchecked (Zip signature verification) option.
second problem is that after installing the TWRP 3.0.2-2 (or above), then reboot recovery, I can't access the recovery again and the phone stuck on bootloop.
any idea ?
Click to expand...
Click to collapse
I don't have a OP2 anymore but that post was seven months ago and the instructions worked for numerous users.
Don't enable zip signature verification in TWRP - it's unnecessary.
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.

thanx for replay Spannaa,
Flash TWRP 3.0.2-2 via your current TWRP's recovery image flashing option and then reboot recovery directly from TWRP.
Click to expand...
Click to collapse
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.

Aood said:
thanx for replay Spannaa,
I have already did that, but same issue once I reboot "directly from TWRP" , the TWRP doesn't show up and bootloop start again.
Click to expand...
Click to collapse
Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?

Last chance and then I'll leave this for someone that has the OP2.
Are you rebooting recovery "directly from TWRP" or rebooting system?
Is your bootloader still unlocked?
Click to expand...
Click to collapse
Yes, rebooting recovery "directly from TWRP"
and bootloader loader is unlocked,..
anyway it's not important to fix the phone, it's almost one year since last time I use it, yesterday I saw it in the drawer and try to figure out the issue..,

Having Problems Trying to Root / Flash TWRP

Hey all, I've spent my entire night trying to get root on my new OnePlus 5 so that I can transfer all of my data from my Nexus 6p over through TitaniumBackup, but for some reason I am having weird issues.
I've followed Funk Wizard's guide on unlocking the bootloader and getting a custom recovery to root, but that's when weird things began to happen. I flawlessly was able to get TWRP running the first time through since it was similar setup to how I got everything working on my Nexus 6p. Once I tried booting back into the ROM though after flashing Magisk, the boot failed and rebooted back into recovery. This kept happening no matter what I tried to do. TWRP also was failing to flash the full Oxygen OS zips as well. I tried flashing stock recovery over TWRP to see if that would let me flash the zip, but then it stuck me back in TWRP afterwards despite overwriting it. I updated the TWRP to the "last latest build" which allowed me to flash the zip and boot back into my ROM successfully. However, then I tried going back into the recovery, it defaulted to the stock one again rather than the TWRP I had before. I reflashed TWRP but it keeps getting the stock OnePlus 5 recovery consistently. I am unsure of what to do. :\ I have to switch back to my old battery-failing phone for the time being. I'm not sure what I'm doing wrong.
Drivers work; manually forced the ADB driver for fastboot. Device just OTA'd to 4.5.3 a few moments ago; I am still getting the same issue. I also tried the latest TWRP but it still achieved no results whatsoever. All of my flashing is done through fastboot.

Hi I red your problem tho I am new here I successfuly rooted my OnePlus 5.
I think that the problem is either not using proper rooting zip's or bad drivers so I will tell you how I rooted mine.
I reccomend using this tool so you will be sure 100% that you have the ADB, Fastboot and necessary Drivers.
https://forum.xda-developers.com/showthread.php?t=2588979
Those are the files that I used(The Magisk zip file and the recovery):
https://mega.nz/#!AA8FGLZR!63Q4HGrAoIlNlwR_NVj8Rbq4RKoPKaEnHLtHuEW3o94
I do not remember from where I downloaded them, neither I can find them from my messy history cuz I searched a lot for them around the internet, so I upload them for you!
Magisk link:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
So basically I went to my phone's settings unlocked Developer options by spamming the build number so I can get there and enable OEM unlocking and USB debugging. After that I rebooted my phone into fastboot mode like I just normally turned it off and hold the power button and VOL+ key. after that I connected my OnePlus to the PC using the DASH cable. You should download beforehand the TRWP and latest Magisk.zip so you can root it using Magisk I have not tried using SuperSU. So you basucally flash the TWRP using the "fastboot flash recovery twrp-3.1.1-0-oneplus5.img" command in my case and you transfer the Magisk Manager and zip file on the phone later so you can root. Then you just flash Magisk's latest zip file or use mine. I do not remember if I manually installed the Magisk Manager APK file tho I have it downloaded on my PC gonna zip them real quick with the recovery and uploade them.

(US996) Any way to get root on the newest update (US99610n)?

As the title states, is there any way to achieve root on the newest build for the US996 unlocked version? I have the bootloader already unlocked, but unfortunately it had already been updated to the latest software, I can get TWRP to install just fine but when I try to install Magisk after wiping data in twrp, I keep getting the same problem on bootup where it says "Encryption unsuccessful" and the only way I can get around that is by flashing back to 100% stock and factory resetting. Am I missing something? Is there any way to get around that problem? I also tried installing a custom rom based on stock (alpha rom) but that didn't work either, any help is appreciated.

well for anyone wondering, I was able to get root and a custom ROM installed. Instead of wiping data like so many guides say to do, I put magisk and the alpha ROM file on an external SD card, skipped decryption in TWRP, mounted the SD card, and installed the ROM and magisk. Didn't have to bother with encryption or anything weird. I made sure to do it after a clean install to minimize any problems that may arise from not wiping. I haven't found a way to do it without an external SD card sadly.

@rusty815, thanks for following up on your own thread with the solution. I just cancelled a purchase for an H918 after reading too late that it won't take the dirtycow root exploit after H91810j, and just bought a US996 instead. I don't know what update the US996 will be on, so if I do end up with US99610n, your post will be very helpful.

Need Help!! LG V20 US99610n
rusty815 said:
well for anyone wondering, I was able to get root and a custom ROM installed. Instead of wiping data like so many guides say to do, I put magisk and the alpha ROM file on an external SD card, skipped decryption in TWRP, mounted the SD card, and installed the ROM and magisk. Didn't have to bother with encryption or anything weird. I made sure to do it after a clean install to minimize any problems that may arise from not wiping. I haven't found a way to do it without an external SD card sadly.
Click to expand...
Click to collapse
I have that same phone and same firmware. Could you please submit the links for what you used to root your phone?

Please OP be our savior and post how to root the vs996 and install twrp on 10n

How to setup official MIUI without breeaking OTA updates or fingerprint sensor

Due to the use of encryption by the official MIUI ROM we cannot use a custom recovery. Only the MIUI stock recovery knows the encryption password so only it can install OTA updates. If you are also having issues related to the fingerprint scanner data disappearing after each reboot, they will be fix by this.
So the actual solution... This might not be obvious to everyone but due the encryption password being unknown we actually need to keep the stock recovery. That's it. Just install the stock recovery. Now you might ask how you flash things like Magisk since the stock recovery doesn't support that kind of thing. It's simple too, just you a ciustom recovery. You don't actually need to have a recovery flashed to use it, you can just boot a image via fastboot(1). This is a bit annoying but still way less annoying than not being able to install updated or the fingerprint data resetting every reboot.
(1) Boot to custom recovery without replacing the stock recovery
Code:
fastboot boot custom-recovery.img

hmmm, I am not really sure what you wanted to explain, however, not only the miui stock recovery knows to handle encryption, as the ATG's twrp with certain version does it fine, as well.

They do but only the stock one knows the password used to encrypt MIUI.

PBRP handles OTA updates without issue. Have had two updates since installing it and haven't had any problems.

HELP! S8 won't boot up!

I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!

Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...

tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!

cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage

I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).