I installed twrp and SU. Really the only reason I did it is because I use titanium backup to back up and restore apps and such. Otherwise I really don't need root.
I have two questions.
First Question: Can I re-lock the boot loader if I have TWRP and SuperSU installed? If not how can I use Android pay? Is there a work around? It's not allowing me to because it can't verify
Second Question: The OTA 6.0.1 won't stick. I'm pretty sure I've done one other over the air update (at least I thought I did, I may be remembering incorrectly) and it worked just fine. But for some reason 6.0.1 isn't taking. Any ideas?
If you don't need root what you can do is download the 6.0.1 imag direclty from google, put it in your adb/fastboo folder and use the flash-all command and it will erase root, twrp and it will be like you just got it from the factory. The only thing that would be still there is the unlocked bootloader. Once you've performed the flash-all command, you can simple lock the bootloader again. That's if you want to get rid of Root and Twrp.. If not, you can try a Rom like Chroma that has android pay working on it.. Here's the instructions. Hope this helps: http://forum.xda-developers.com/showpost.php?p=64269166&postcount=2338
Edit: Make sure you follow the systemless root instructions from that link to get android pay to work...
So I cannot lock the boot loader if I have root and twrp installed?
I really don't want to use a Rom. I'm happy with stock, just want to be able to use titanium backup.
And are ota updates not working if you have twrp installed?
OTA updates won't flash properly if you have TWRP installed, though I heard there is a way to extract the components of the update you want to apply so you can preserve root and custom recoveries while still updating. Sorry I don't know where the instructions are though.
No you can't lock the bootloader with TWRP installed, it can result in a brick.
I would not lock the bootloader unless you are 100% stock. You open yourself up to unrecoverable bricks. As for the update if you download the image from google you can just flash the individual partitions in fastboot. This way you can preserve your data. Heisenburg has a great guide here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 You will loose root but getting it back just involves reflashing the SuperSU-v2.62-3-20151211162651.zip from this thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344/post64161125#post64161125
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..,
Hello,
I wanted to test the Engineering Mode and I followed the guide posted on twitter by fsociety (Used the adb method to enter the 'angela' code). Turning engineering mode on had no visible impact but on subsequent reboot, I lost root and Safetyet got violated (More specifically, CTS).
Setup:
OnePlus 5
OxygenOS 4.5.14
Magisk (latest)
This setup used to work fine and SafetyNet was intact. Things got bad after unlocking the engineering mode.
This is what I have done so far:
Tried *#8011# code to reset settings but I have no luck.
Re-installed the ROM (dirty flash)
Uninstalled Magisk and re-installed Magisk. (but still no root)
Installed SuperSU (systemless) but no luck rooting the phone.
Tried setting "setprop persist.sys.adb.engineermode 0" and "setprop persist.sys.adbroot 0"
Can someone tell me what I can do to fix this?
There's a debloat app in the themes and apps section. You can remove the engineering mode bloatware and see if that helps. You can also try a clean flash instead of a dirty one. If that doesn't work either you can always format your data with TWRP which will wipe everything on the phone except TWRP, use a computer to copy the ROM zip and Magisk to your phone and flash them in TWRP. If you do a clean flash or the latter I would set up the phone fresh instead of from an Android cloud backup because the cloud backup will restore some OOS settings and data and might restore your problem.
There are probably less drastic ways to solve your problem but I don't know them. Good luck.
It got fixed somehow. I ran the *#8011# code and used my computer to set the ADB properties. I flashed TWRP again and installed Magisk and bam! It worked!
Hi! I have flashed successfully a stock rom of Android 5.1.1 on this device (SM-G531M) using the latest Odin. I enabled the developer options and then OEM Unlock and USB Debugging. Flashed TWRP, everything great. Once TWRP was on my device I installed Magisk following the instructions and no problem. So having root access and TWRP on my phone, really happy that no problems came up on the way, I decide to log into my Google account to update and get some apps and here is when the problems appear. I checked that OEM Unlock is still on and reboot my phone to find that FRP is on and can't boot because of root (can't get in recovery either because TWRP is not the stock recovery), so I flash the device again with the stock rom and find out that I can't remove FRP lock to flash TWRP again. I try removing my google account and FRP is off, so I have to choose:
a) root access and TWRP recovery or
b) Google Account and get new apps or update the ones I have.
Nowhere I looked I could find any answer or anyone having this issue. Can someone tell me what am I doing wrong? I really have no idea why this happens, is a Google update that does this to everyone or what's going on?
Thanks in advance!
So I've read a bunch of stuff and everything I've read tells me to do the same thing that I've already done. Also those thread seemed pretty old so....
Anyway I need a stock backup so I can perform OTA update but I don't have one. this is what I did
I used msmtool to start over
pushed through setup
unlocked bootloader switch in developer settings
unlocked bootloader in fastboot
updated android
fastboot boot twrp.img
wiped everything
flashed magisk.zip
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
installed magisk.apk
So what step am I missing to save the stock backup so I can uninstall magisk for OTAs?
I had a Pixel for 3 years that had a broken fastboot and so I couldn't unlock the bootloader and never got to learn about the new AB partitioning until now. so I'm a little behind
Thanks
GbizzleMcGrizzle said:
(I didn't install TWRP because I am under the impression I can't pass safteynet with a custom recovery am I wrong about this?)
Click to expand...
Click to collapse
Unlocking the bootloader can make you fail safety net, much less Magisk if its not set up right. The recovery wont matter.
My guide here is for installing Lineage, however Step 5 will work for OOS too and make you pass safety net. So feel free to install TWRP.
I recommend Funk Wizards Guide on installing TWRP. Also note the section on EFS backups.
Look into TWRP backups, I dont use them, but I know its not straight forward unfortunately.
So when I'm flashing the magisk file in TWRP, does it save a copy of the image it's modifying? And where does it save that image? Also where should i put that image so I can uninstall-> Restore Images?