Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
acemccloud1 said:
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
Click to expand...
Click to collapse
Same problem dude...
I too got same problem, but now solved. Use all in one tool box by gohel.vishal first unlock bootloader, 2] resart phone 3] now enable usb debugging 4] again use toolbox to fash custom recovery 5] after flashing remove battery and restart into recovery, thats all.
Issue fixed using this thread:- http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847
(Remember to disable "Update CM recovery" option in Developer Options)
remove battery after install recovery before restarting phone
Guide me to install HYBRID v3.4 recovery......so that i can install CM14....
currently i am using this cm13 rom(version details in the pic).
Finally, what i want is the change of recovery !!!!!!!
I had the same issue but I was able to fix it.
I flashed halogenOS: http://forum.xda-developers.com/oneplus-2/development/rom-halogenos-oneplus-2-t3377799
Then I was able to flash the latest TWRP via fastboot and it's working great.
First do all necessary backups etc.
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..,
OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..
sguy156 said:
OP2 is stuck at OP logo after the latest OTA. What do I need to do to have it restored it back ..
Click to expand...
Click to collapse
If you have twrp you can flash a full oxygen rom to restore it if you dont you need to Download latest full rom on your pc go in recovery mode connect phone to pc and put the zip in your storage and after that flash it via recovery mode
No it doesn't go into recovery mode it only goes into fastboot mode ..
sguy156 said:
No it doesn't go into recovery mode it only goes into fastboot mode ..
Click to expand...
Click to collapse
Try this zip on your pc while phone connected and on fastboot mode It auto flashes twrp on your phone so you can try to flash oxygen os via it
https://forum.xda-developers.com/devdb/project/?id=13708#downloads
that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script
sguy156 said:
that worked so do I need to flash modified SU 2.79 to root this phone or stay with the TWRP which came with the first aid script
Click to expand...
Click to collapse
If you want to root your phone use this file and Flash it via twrp
https://www.androidfilehost.com/?fid=24591000424939898
modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..
sguy156 said:
modified SU is not going to work and have to use seemless SU . Thanks for your help which version of TWRP works without any issues with the newest Oxygen OS..
Click to expand...
Click to collapse
Go to Playstore and download twrp app en flash the latest compiatble version
What is needed to re-root OOS 3.5.6 if you did like me and let the OTA update your phone.
TWRP 3.0.2-2 link
OOS3 SuperSu 2.78 link
You can get latest TWRP flashable OOS packages from here.
For future reference.
Oneplus two Rooted stuck on Boot Loop Mode
Hi Guys I need your Help Can anyone Help me as soon as possible
I was Using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery
I was using Resurrection Remix 5.8.5 Nougat 7.1.2 and in Twrp recovery apk a small mistake was done by me
I tick marked as
Allow Flashing to boot partition after that it got stuck in Boot Loop Mode How fix that guys
But Fastboot Mode only Working
Hi it's done with me but not in your way I was realising why it is not boot loading then I came to know maybe TWRP recovery is not installed so I just wanted to flash TWRP recovery in fastboot mode there are so many people trying in different different way to switch on the mobile which got stuck and boot loop mode I found a simple way with all in one tool for Android I am giving you a description or a link below just to flash TWRP recovery and don't forget to select after flash reboot you have to select tick mark it's the best way you can boot load your phone very very simple way to do that
Download Link
https://basketbuild.com/devs/mauronofrio/TOOL
Basically I currently Have TWRP and MAGISK in the first version of the stock oreo rom now i have no idea how to update via ota because i have twrp as my recovery right now.
Any thoughts on how i could remove twrp and go back to stock recovery... long story short i needed twrp before because i was stuck in a boot loop and had to flash magisk via twrp to fix the loop. Thanks in advance.
IHaveThisSlowPhone said:
Basically I currently Have TWRP and MAGISK in the first version of the stock oreo rom now i have no idea how to update via ota because i have twrp as my recovery right now.
Any thoughts on how i could remove twrp and go back to stock recovery... long story short i needed twrp before because i was stuck in a boot loop and had to flash magisk via twrp to fix the loop. Thanks in advance.
Click to expand...
Click to collapse
Follow this thread :
https://forum.xda-developers.com/showthread.php?t=3718542
It provides link to all roms (stable, beta & incremental) & Mi flash tool. Download the latest platform tools zip for windows & update your .net framework. You should also make sure you've installed your adb & fastboot drivers correctly.