I rooted my OnePlus with TWRP recovery sometime back and current image is CM11. I need to upgrade it to CM12 however all the manuals I found require stock recovery to upgrade from CM11 to CM12
I was wondering if it's possible to upgrade to CM12 with TWRP recovery? If not, how I can get stock recovery restored?
Also, if I manage to upgrade to CM12, is there a possibility for OTA updates in future?
Dud download lollipop bootanimation and flash through TWRP
Sent from my Micromax A106 using XDA Free mobile app
yetanotherse said:
I rooted my OnePlus with TWRP recovery sometime back and current image is CM11. I need to upgrade it to CM12 however all the manuals I found require stock recovery to upgrade from CM11 to CM12
I was wondering if it's possible to upgrade to CM12 with TWRP recovery? If not, how I can get stock recovery restored?
Also, if I manage to upgrade to CM12, is there a possibility for OTA updates in future?
Click to expand...
Click to collapse
1. Download the flashable CM12s zip file.
2. Store it under the root directory.
3. Go to TWRP recovery (Please make sure you use the latest version 2.8.6.0).
4. Do factory reset (wipe dalvic cache and other memory)
5. Flash the CM12 zip.
6. Reboot and enjoy....
Also, you will get OTA if you manually flash the CM12s.
yetanotherse said:
I rooted my OnePlus with TWRP recovery sometime back and current image is CM11. I need to upgrade it to CM12 however all the manuals I found require stock recovery to upgrade from CM11 to CM12
I was wondering if it's possible to upgrade to CM12 with TWRP recovery? If not, how I can get stock recovery restored?
Also, if I manage to upgrade to CM12, is there a possibility for OTA updates in future?
Click to expand...
Click to collapse
You don't need stock recovery, just flash with TWRP.
Transmitted via Bacon
Thanks for your help. Was able to flash CM12 successfully.
But facing another issue now - As soon as phone booted with CM12, it downloaded OTA system update. When I try to install the update, phone reboots in twrp recovery and update doesn't complete. Tried numerous times (with and without 'update CM recovery' toggle) but with same result.
yetanotherse said:
Thanks for your help. Was able to flash CM12 successfully.
But facing another issue now - As soon as phone booted with CM12, it downloaded OTA system update. When I try to install the update, phone reboots in twrp recovery and update doesn't complete. Tried numerous times (with and without 'update CM recovery' toggle) but with same result.
Click to expand...
Click to collapse
What error message do you get?
Shankar9822 said:
What error message do you get?
Click to expand...
Click to collapse
Some md5 error. Was able to workaround it by flashing the OTA update via TWRP directly
yetanotherse said:
Some md5 error. Was able to workaround it by flashing the OTA update via TWRP directly
Click to expand...
Click to collapse
Good to hear that.... MD5 error occurs when the downloaded file is corrupted.
Related
I currently have 2.3.1 installed on my note. I want to update to 2.6.3 so I can install CM11.
I only have TWRP installed and my current ROM (some verzion of PA) has already been factory reset (aka I can not actually use my ROM/Phone).
In order to update to CM11 I need to use the latest TWRP.
Edit: When I try to install the .zip for 2.6 from 2.3 it gives me an "error" message
Yes, you can. But after flashing the update, you must reboot into recovery (restart TWRP) before flashing anything else.
Sent from my SCH-I605 using Tapatalk
Trying to flash 5.0 OTA from 4.4.4 without losing data on Nexus 5.
I don't know how to remove custom recovery so I can sideload the OTA zip in the stock recovery. It keeps loading into TWRP instead.
Can someone explain step by step how I flash the factory recovery.img?
That's not even possible (as far as I know)...
XDA Visitor said:
Trying to flash 5.0 OTA from 4.4.4 without losing data on Nexus 5.
I don't know how to remove custom recovery so I can sideload the OTA zip in the stock recovery. It keeps loading into TWRP instead.
Can someone explain step by step how I flash the factory recovery.img?
Click to expand...
Click to collapse
Removing a custom recovery while preserving data is not possible, you should backup all your data, remove the custom recovery, flash 5.0 and then restore your custom recovery.
Are you using the Nexus Root Toolkit? It's incredibly easy and I use it for almost all my flashing, rooting, etc.
You can't apply an OTA on a rooted phone. On Kitkat and before you could end up in a boot loop. After Lollipop the OTA changed to system-level verification, and any change to the ROM stopped the OTA - all you get is a reboot to an unchanged system.
In any case, major ROM jumps usually work best with a total wipe and clean install of the new ROM. somerandomatoms is right - back up and install the new ROM. But why go to 5? You may as well go straight to 6.0.1.
hello everyone
I have XT926 (verizon one)
my phone system version is 183.46.10
I have rooted my phone using towelroot and unlocked bootloader
now whats next?
latest firmware update (183.46.15) notification is bugging me, should i install it through ota in this condition or directly move to installing custom roms. if install this ota without unrooting, will my phone enter bootloop?
which recovery is recommended for android 5.0 on kk bootloader.
faheemakbar18 said:
hello everyone
I have XT926 (verizon one)
my phone system version is 183.46.10
I have rooted my phone using towelroot and unlocked bootloader
now whats next?
latest firmware update (183.46.15) notification is bugging me, should i install it through ota in this condition or directly move to installing custom roms. if install this ota without unrooting, will my phone enter bootloop?
which recovery is recommended for android 5.0 on kk bootloader.
Click to expand...
Click to collapse
Here ist what i have experienced:
I was on System Version: 181.46.3
Well nevertheless:
It was the most recent version i could get and i wanted to get back to Android L.
I installed CM12 the Following way, I had a lot of problems with that. So here is my experience and everything:
So you need to know, to install CM12 or other CM12 based ROMS you first need to have CM11 installed.
Newer Versions of the recovery might be having problems installing CM11, so i would recommend using PhilZ Touch Recovery. It was working for me.
1st: install PhilZ recovery
2nd: factory reset
3rd: install cm11 (Unified Build, due to no up-to-date-build for XT925)
4th: boot
5th: install latest TWRP XT925/TWRP XT926
6th: factory reset
7th: install CM12 XT925 / CM12 XT926 or other CM12 based ROM
8th: install Gapps
9th: wipe cache/dalvik cache
10: Boot
11: Have fun.
Possible problems:
"This package is for moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish, this is a xt925" ------> You got a problem with the Recovery, it is too new. Try PhilZ
CM12 Booting, inconsistent Data partition stuff error ---------> you did not install cm11 and did not wipe Data before installing CM12, when coming from Blur Rom
Bootloop ---------> no wiping or you did not install cm11 before installing CM12
I hope this might have helped you.
Greetz Esok
thanks alot @esok44 for detailed reply
which phone you hv xt925 or 926
why install cm11 from moto msm8960 and not from specific xt925,xt926 build
faheemakbar18 said:
thanks alot @esok44 for detailed reply
which phone you hv xt925 or 926
why install cm11 from moto msm8960 and not from specific xt925,xt926 build
Click to expand...
Click to collapse
Heyho
I have an XT925.
I installed the msm8960 Build.
The Reason i used the unified Build was, there is no KKBL build for the xt925.
thanks again, onto the procedure now
just last thing, which version of philz recovery you installed, download link has latest one @esok44
faheemakbar18 said:
thanks again, onto the procedure now
just last thing, which version of philz recovery you installed, download link has latest one @esok44
Click to expand...
Click to collapse
Hey Faheem,
i used the latest one, i guess
Found it here.
Link in my first Post was wrong
esok44 said:
1st: install PhilZ recovery
2nd: factory reset
3rd: install cm11 (Unified Build, due to no up-to-date-build for XT925)
4th: boot
5th: install latest TWRP XT925/TWRP XT926
6th: factory reset
7th: install CM12 XT925 / CM12 XT926 or other CM12 based ROM
8th: install Gapps
9th: wipe cache/dalvik cache
10: Boot
11: Have fun.
Possible problems:
"This package is for moto_msm8960, xt907, scorpion_mini, smq, xt926, vanquish, this is a xt925" ------> You got a problem with the Recovery, it is too new. Try PhilZ
CM12 Booting, inconsistent Data partition stuff error ---------> you did not install cm11 and did not wipe Data before installing CM12, when coming from Blur Rom
Bootloop ---------> no wiping or you did not install cm11 before installing CM12
I hope this might have helped you.
Greetz Esok
Click to expand...
Click to collapse
If you come frome OTA Kitkat 4.4.2
you have to change Step 1st: install PhilZ recovery ------ to ------ Install TWRP2710-RAZR-HD_M-KITKAT.img instead then you can flash the CM 11
If you like philz_touch_6.58.7-moto_msm8960.img recovery (it can mount external Memory Card as USB) you can flash it after all installations after Point 11. The only thing that you cannot start directly to recovery from CM 12.1
Hi, today I received Marshmallow OTA update (13.0-ZNH0EAS2JK, not yet installed), this is a great news but I also get a popup window says :
WARNING : Update Cyanogen recovery is disabled. This may cause issues with updating your device.
Please enable Update Cyanogen recovery in Developer options
Ignore / OK
1. Should I ignore the message or I have to enable Update Cyanogen recovery?
2. Right now I use TWRP, will the cyanogen recovery override the TWRP or not?
3. Just to make sure, upgrading to Marshmallow doesn't delete data and apps, right?
Btw right now I'm on CM 12.1.1-YOG7DAS2K1 (Lollipop) rooted.
this will not affect the update but your device may well not allow the update unless you re-flash CM recovery first then after updating again re-flash TWRP
For ota you should be in stock recovery not in twrP and stock rom ,Enable update cm recovery in developer's options.no data loss .
So before installing update, I need to re-flash CM Recovery or just enable it from Developer Options?
cliffflip said:
So before installing update, I need to re-flash CM Recovery or just enable it from Developer Options?
Click to expand...
Click to collapse
Toggle on the "update cyanogen recovery" from Developer menu and flash the stock recovery.
You probably need to flash the stock ROM too which includes the stock recovery.
When i switched from cm12.1 with twrp to cm13, just flashing the stock recovery didnt work for me, I had to flash the stock cm12.1 ROM
COS 13 bacon signed zip for fastboot and twrp posted in oneplus forum
https://forums.oneplus.net/threads/cos-13-full-zip.445052/
I flashed via twrp , working well.
Hi Currently I am having Honor 4c with Kitkat 4.4.2 (V100R001C636B160) version I wanted to Upgrade my android version to Marshmallow(CHM-U01C432B560) or any other custom ROM. I have unlocked my device bootloader and installed CWM recovery following the guide https://forum.xda-developers.com/honor-4c/development/honor-4c-root-cwm-recovery-inshaalmirza-t3177770 was able to install CWM but I wanted to install TWRP and followed the guide by @HassanMirza01 but wasnt success to install TWRP , if I am trying to flash Marshmallow ROM using CWM or by flashing IMG files using ADB I am not able to do it. Every Time I try to flash a ROM from CWM I am getting error and while flashing IMG files using ADB the screen is being struck at boot logo.Can anyone guide me how to replace CWM with TWRP so that I can Install Marshmallow (every time while I am trying to flash TWRP it is being struck at boot logo and had to flash stock ROM to recover the phone) and install marshmallow.
Note: Initially I upgraded to Lollipop as the version was not stable and Buggy I reverted to stock version using the official guide.
miststudent2011 said:
Hi Currently I am having Honor 4c with Kitkat 4.4.2 (V100R001C636B160) version I wanted to Upgrade my android version to Marshmallow(CHM-U01C432B560) or any other custom ROM. I have unlocked my device bootloader and installed CWM recovery following the guide https://forum.xda-developers.com/honor-4c/development/honor-4c-root-cwm-recovery-inshaalmirza-t3177770 was able to install CWM but I wanted to install TWRP and followed the guide by @HassanMirza01 but wasnt success to install TWRP , if I am trying to flash Marshmallow ROM using CWM or by flashing IMG files using ADB I am not able to do it. Every Time I try to flash a ROM from CWM I am getting error and while flashing IMG files using ADB the screen is being struck at boot logo.Can anyone guide me how to replace CWM with TWRP so that I can Install Marshmallow (every time while I am trying to flash TWRP it is being struck at boot logo and had to flash stock ROM to recover the phone) and install marshmallow.
Note: Initially I upgraded to Lollipop as the version was not stable and Buggy I reverted to stock version using the official guide.
Click to expand...
Click to collapse
You can try this TWRP https://forum.xda-developers.com/honor-4c/development/recovery-twrp-3-0-0-0-huawei-honor-4c-t3349495 or some version of TWRP for honor 4x or p8lite. And then you can try to flash stock firmare using this tutorial https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702. You might need to be in lollipop or marshmallow to use it.
Hi @keikari thanks for the reply, that is the case where I am facing the problem Neither I can install Twrp 3.0.1-0 (r1,2,3,4) variants nor lollipop or marshmallow update .I am struck with stock Rom tried more than 15 to 20 times . Can you provide any alternative solutions.
miststudent2011 said:
Hi @keikari thanks for the reply, that is the case where I am facing the problem Neither I can install Twrp 3.0.1-0 (r1,2,3,4) variants nor lollipop or marshmallow update .I am struck with stock Rom tried more than 15 to 20 times . Can you provide any alternative solutions.
Click to expand...
Click to collapse
What error did fastboot gave you when you tried to flash TWRP?
No error given but after flashing twrp device is struck at boot screen and can't move to next screen cwm flashing works fine .
Is it mandatory to have lollipop or marshmallow update to flash twrp?
miststudent2011 said:
No error given but after flashing twrp device is struck at boot screen and can't move to next screen cwm flashing works fine .
Is it mandatory to have lollipop or marshmallow update to flash twrp?
Click to expand...
Click to collapse
I don't know how things really work or why they need stuff to work. But in TWRP thread it says for android 5.1.1 - 6.0. So I guess it's important to have some of those versions.
Is there any other way to flash lollipop or marshmallow from cwm? I even extracted update.app and flashed recovery, system , boot images individually but it also doesn't work struck at boot screen. Can I fully wipe system files from phone and re-flash lollipop or marshmallow update. Similar to full format of a PC.
miststudent2011 said:
Is there any other way to flash lollipop or marshmallow from cwm? I even extracted update.app and flashed recovery, system , boot images individually but it also doesn't work struck at boot screen. Can I fully wipe system files from phone and re-flash lollipop or marshmallow update.
Click to expand...
Click to collapse
No idea will that work, but one thing that comes to mind is to flash those images you did and then put UPDATE.APP in your sd card in folder named dload and do force upgrade ( power + vol up + vol down ).
keikari said:
No idea will that work, but one thing that comes to mind is to flash those images you did and then put UPDATE.APP in your sd card in folder named dload and do force upgrade ( power + vol up + vol down ).
Click to expand...
Click to collapse
Tried that too but no success. I think the problem occurred while downgrading to kitkat from lollipop maybe it corrupted the boot system. Even that is the case while flashing and wiping cache so many times it might have showed error in any of the instances but it didn't. Can't find out what actually preventing system to update.