Related
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
vipimg said:
Any one rooted after updating to CM12 (Official)
I have updated my so far i have noticed some lags & network issues
PLS share your problems
THX
Click to expand...
Click to collapse
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
hrishi21007 said:
If you wanna root it....Just install a custom Recovery & flash SuperSu.zip
Click to expand...
Click to collapse
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ??
Mine's bricked.
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
aakarshak said:
i also update to lollipop, unlocked the bootloader and flashed 64bit twrp but my phone is bricked. can u please help?
thanks in advance.
Click to expand...
Click to collapse
This is what I was trying to say i was not sure about it i didnt do it yet just waiting for a solid one
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
vipimg said:
Mr aakarshak
May i ask if your phone now in boot loop ...? or something else
Click to expand...
Click to collapse
I jst flashed the cwm recovery and its working fine
Yes i was about to tell u to flash CWM recovery
aakarshak said:
I jst flashed the cwm recovery and its working fine
Click to expand...
Click to collapse
which one... is it 64 bit or the old one ????
rahulsingh616 said:
Yup its same!
But u need to install 64bit custom recovery!
There is 64bit twrp recovery thread in Yureka android development!.
I rooted my phoe successfully and works great ����
Click to expand...
Click to collapse
i am also trying to flash the same thru fastboot but every time i am booting to recovery it shown cynogen's recovery.
update cm recovery is already unchecked in Dev option.?
any help
Rooted my phone, bricked it, and now went back to default Lollypop
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
After flashing dont start ua phone
Go to recovery mode directly!
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
I hv updated my yureka yesterday manually to cm12 and device is running very smoothly..bt I faced an issue while charging the phone..it was taking around 4hrs of time and phn heating a lot .. I was thinking to revert back to kitkat which was also working f9 for me without any heating issue bt I came to know it is not passible to go back.. I was bit tensed regarding heating issue bt suddenly I see my lumia 520 charger and I charged yureka with that charger and u won't believe charging speed is increased and phn was nt heating up at all.. I don't knw what is issue with charning in lollipop bt nw I am very relaxed ...
original 12S zip links
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can u post links to original CM12S zip u mentioned above...?
vipimg said:
I am just asking if its the same procedure as CM11 ....?(Dont wat to brick it)
Click to expand...
Click to collapse
I bricked mine... So i dont recommend rooting after upgrading to cm 12
kailashnj said:
What is the proper procedure to install the fast boot version as I am facing issues after installing the OTA and probably they can be resolved with the fastboot option. Kindly help.
Click to expand...
Click to collapse
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
Are you sure this worked for you,cause basically you are just saying that you did the normal rooting procedure that we did when we had kitkat,just that you used a 64 bit recovery this time
Stock recovery for CM 12
abeyhere said:
-> I flashed the official CMD 12S, and flashed supersu alongwith, the first time when it was released, i.e. Thursday evening.
-> I was rooted to begin with, setup everything, everything worked.
-> Out of curiosity, rebooted to recovery to check the recovery, what it is. I was on clock work mod recovery, when I was on kit kat.
-> That's when my device would go to YU screen, and never go beyond that.
-> Luckily, I could still go into adb shell and fastboot. I flashed, the default boot and recovery from the original 12S zip, and logged into recovery again. Then used the update process in default recovery, to install 12S again.
-> So far so good. I can go to recovery as well.
-> What different I did this time, well did not root my device using supersu. So whoever have rooted your device using older supersu, would suggest to reboot to recovery, and if it breaks, you can still get your device back, by the process I mentioned, but that would confirm that old supersu could break recovery.
Click to expand...
Click to collapse
Can you tell you you flashed the cm12 recovery ???
i cannot find it inside the cm12 update zip file.
abeyhere said:
Kailas proper procedure, I won't know, as there may be a better way . However I'd tell you what worked for me.
-> I downloaded the zips (fastboot, and signed one, from http://forum.xda-developers.com/yureka/general/discussion-yu-yureka-cm-12s-lollipop-t3084461).
-> I moved the signed zip(cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip) version to External SD card.
-> I extracted the fastboot zip file to folder in laptop, and flashed boot.img from it, using fastboot. Not sure if there would be any difference if I use the boot.img from usual signed zip file.
-> Then I rebooted to fastboot again, and flashed the recovery.img.
-> Thats when I booted to recovery, and updated the zip(I already moved earlier to sd in step 2) through default yureka recovery.
-> Once installation was completed, I cleared the catche again, as suggested by others.
Let me know if you need fastboot commands. The fastboot works using the verdor id as fastboot -i 0x1ebf. For ex.
fastboot -i 0x1ebf flash boot boot.img
And you can almost always login in fastboot, by
-> connecting USB to computer, and pressing power button, and volume down key together.
And on windows 8 the fastboot drivers are named as YunOS phone.
Zips link Signed http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_14294725084389&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...ato-signed.zip
Fastboot: http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_142947255030510&key=f0a7f91912ae2b52e0700f73990eb321&libId=i8ov035t01000n4o000DL15p41qflr64vu&loc=http%3A%2F%2Fforum.xda-developers.com%2Fyureka%2Fgeneral%2Fdiscussion-yu-yureka-cm-12s-lollipop-t3084461&v=1&out=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2Ftomato%2F12.0-YNG1TAS0W0-tomato%2F56deeca328%2Fcm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip&title=DISCUSSION%3A%20YU%20Yureka%20CM%2012(S)%20Lollipop%20Upda%E2%80%A6%20%7C%20YU%20Yureka%20%7C%20XDA%20Forums&txt=http%3A%2F%2Fbuilds.cyngn.com%2Fcyanogen-os%2F...d-fastboot.zip
Let me know if you have any questions. Cheers.
Click to expand...
Click to collapse
I did install the rom from the fastboot method still it did not work. I am fed up of the CM12 rom.
How to remove twrp and put stock recovery
Hi guys, can you please help me with this problem?
Yesterday i went for CM 12.1 but didn't like it at all, I installed it via twrp...
So now i flashed asus rom 2.20.40.59, but i want to put OTA and i can't do it with TWRP.How can i put stock recovery and remove twrp? I tried several methods, but none of them worked for me...
Thanks in advance!
I couldnt put stock recovery either.
Please take a look at this thread:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
the method of flashing stock recovery is the same as flashing the twrp.
Here's a link to the stock recovery collection from the same thread:
http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
You can flash any recovery without PC by using [ROOT] Rashr - Flash Tool.
Search at play store.
thezibrail said:
Please take a look at this thread:
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
the method of flashing stock recovery is the same as flashing the twrp.
Here's a link to the stock recovery collection from the same thread:
http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Click to expand...
Click to collapse
I try to flash stock recovery with adb (fastboot flash recovery recovery.img) but when I try to enter in recovery I got an Error screen.
I also noticed in the bootloader screen that the product_name is Z008, but I have Z00A with 4Gb ram..
Any solution?
edit: do you know if are there other link for recovery stock files?
Yco.giusti said:
I try to flash stock recovery with adb (fastboot flash recovery recovery.img) but when I try to enter in recovery I got an Error screen.
I also noticed in the bootloader screen that the product_name is Z008, but I have Z00A with 4Gb ram..
Any solution?
edit: do you know if are there other link for recovery stock files?
Click to expand...
Click to collapse
Thats so strange about ur phone model!!
I've got zenfone ze550ml, model is z008, 2 GB ram . for recovery I downloaded this one: http://www.mediafire.com/folder/setyy42t2cymy#ma3w61exgyy06
and perhaps u have already converted into stock recovery.
When u get an error screen while trying to go to recovery mode (probablu u saw a dead android bot with an error) press and hold power button, then (while holding power button) quickly press Vol up and release and then also release power button..
hope this helps. i had the same error screen
thezibrail said:
Thats so strange about ur phone model!!
I've got zenfone ze550ml, model is z008, 2 GB ram . for recovery I downloaded this one: http://www.mediafire.com/folder/setyy42t2cymy#ma3w61exgyy06
and perhaps u have already converted into stock recovery.
When u get an error screen while trying to go to recovery mode (probablu u saw a dead android bot with an error) press and hold power button, then (while holding power button) quickly press Vol up and release and then also release power button..
hope this helps. i had the same error screen
Click to expand...
Click to collapse
I tried to use your method but no result then I tried to flash stock rom with twrp and I don't know why, this time work(maybe because I wipe data and cache first, or maybe I was on cyanogen rom and not paranoid). Then i flash the stock recovery and apply ota. Now the model on bootloader is z00A again.
OT: Anyway every rom, with his bugs, is better than asus stock. Damn!
how to flash stock rom using twrp (ZE550ML/Z008)
i saw ur post and u mentioned that u again installed asus stock rom using twrp.
as far as i know, for installing stock rom, u must use the stock recovery.
it will be very helpful if u kindly post the stapes to flash stock recovery via twrp
i am now in cm12.1 but i could not roll back to stock rom inspite i flashed the original stock recovery
i am desparate to roll back in stock recovery and rom and get ota update for the upcoming periods
peace (Y)
---------- Post added at 05:09 AM ---------- Previous post was at 05:06 AM ----------
Yco.giusti said:
I tried to use your method but no result then I tried to flash stock rom with twrp and I don't know why, this time work(maybe because I wipe data and cache first, or maybe I was on cyanogen rom and not paranoid). Then i flash the stock recovery and apply ota. Now the model on bootloader is z00A again.
OT: Anyway every rom, with his bugs, is better than asus stock. Damn!
Click to expand...
Click to collapse
i am on also unofficiam cm12.1 nightly
i also want to get back to stock rom
will u plz tell me the stages u followed to port stock rom in ur device via twrp
i am using (ZE550 ML /Z008)
Yco.giusti said:
I tried to use your method but no result then I tried to flash stock rom with twrp and I don't know why, this time work(maybe because I wipe data and cache first, or maybe I was on cyanogen rom and not paranoid). Then i flash the stock recovery and apply ota. Now the model on bootloader is z00A again.
OT: Anyway every rom, with his bugs, is better than asus stock. Damn!
Click to expand...
Click to collapse
Asus stock would have been good without the bloat wares.
I tried to flash stock rom in my asus zenfone 2, but it said that, "the package is for Z008 but this is Z00A" but my phone is ZE550ML (Z008). I dun know why I can't get back to stock rom using twrp. I also tried to side load "update.zip" from ADB sideload using stock recovery but it also shows error. this time it says "This package is older than the Build"
Sent from my ASUS_Z008 using Tapatalk
update rom stock with twrp
Hello,
I have only install twrp recovery (no root) but now how do I update ota with TWRP ?
if not possible, Can i update the rom stock with twrp?
I try with "file.zip" from asus site but don't work.
I read some threads but I could not understand...
thanks for help me
Just "fastboot flash" recovery and splashscreen from YOUR model.
RealYoti said:
Just "fastboot flash" recovery and splashscreen from YOUR model.
Click to expand...
Click to collapse
thanks for answer...
where can i found the recovery?
I don't understand much, sorry...
can you write me a small and quick guide?
very grateful
All recoveries are here: http://www.mediafire.com/folder/setyy42t2cymy
From fastboot/bootloader mode:
Code:
fastboot flash recovery recovery.img
fastboot flash splashscreen splashscreen.img
Fastboot is a program in Android SDK tools.
Now I understand...thank you very much....
Can I use this command line:
adb sideload file.zip (file.zip is the file of firmware zip that I download of asus - for exemple: UL-Z00A-WW-2.18.40.12-user.zip.)
this command line has some effect on the bootloader or recovey?
sorry for my many questions...I'm learning...
bozzy_guzz said:
Can I use this command line:
adb sideload file.zip (file.zip is the file of firmware zip that I download of asus - for exemple: UL-Z00A-WW-2.18.40.12-user.zip.)
Click to expand...
Click to collapse
Yes, from/in recovery. And better use shortest command (e.g. "adb sideload d:\adb\update.zip") or you'll get an error.
bozzy_guzz said:
this command line has some effect on the bootloader or recovey?
sorry for my many questions...I'm learning...
Click to expand...
Click to collapse
Your bootloader will be untouched, recovery will be updated (if you flash newer zip) or untouched (for same version).
RealYoti said:
Yes, from/in recovery. And better use shortest command (e.g. "adb sideload d:\adb\update.zip") or you'll get an error.
Your bootloader will be untouched, recovery will be updated (if you flash newer zip) or untouched (for same version).
Click to expand...
Click to collapse
thanks for your time...
Last question...
I use the command line "adb sideload d:\adb\update.zip" and I have installed TWRP recovery
I think that twrp becomes a recovery stock...Is it correct?
bozzy_guzz said:
I use the command line "adb sideload d:\adb\update.zip" and I have installed TWRP recovery
Click to expand...
Click to collapse
"ADB sideload" work with stock recovery only, as I know. Just reinstall TWRP after.
RealYoti said:
"ADB sideload" work with stock recovery only, as I know. Just reinstall TWRP after.
Click to expand...
Click to collapse
done everything ok, thanks
I read that twrp support "adb sideload".
1.entry in twrp
2.select advanced
3.select adb sideload
4.lunch the command line:
- adb devices (for device is recognized)
if this is correct lunch the command line:
- adb sideload name_Zip_Rom.zip
I have not tried it yet...when I will install a new update will try it.
bozzy_guzz said:
done everything ok, thanks
I read that twrp support "adb sideload".
1.entry in twrp
2.select advanced
3.select adb sideload
4.lunch the command line:
- adb devices (for device is recognized)
if this is correct lunch the command line:
- adb sideload name_Zip_Rom.zip
I have not tried it yet...when I will install a new update will try it.
Click to expand...
Click to collapse
don't work it...
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Could you share your twrp? Thanks!
Thetpcguy said:
Hi, I manually updated my honor 7x (BND AL10 INDIAN) to EMUI 8 following the other post in this forum and after that I went on to flash TWRP recovery again from another post "complete_twrp_ramdisk.img" so that I could take full Nand backups and what not. But Here's the problem, When I try to flash the stock recovery back "BND_RECOVERY_NOcheck" which I flashed during upgrading to EMUI 8, it says "size of image is large than target device"
I tried this using boot fastboot command "fastboot flash recovery_ramdisk recovery.img" and also using the TWRP. It doesn't work either way. So I'm basically stuck with TWRP. The reason I want stock recovery is because
1. I can install OTA UPDATES on EMUI 8 (I actually got one)
2. I may want to just be on complete stock like locked bootloader, sock recovery etc...
Could any one help?? Maybe I need the right stock recovery file ?
BTW It's my first post ever so please go easy if I did any mistakes.
Click to expand...
Click to collapse
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
holds said:
Could you share your twrp? Thanks!
Click to expand...
Click to collapse
It's here https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
"BND_RECOVERY_NOcheck" is nouget stock recovery.
Oreo update replaces all the partitions, including the recovery that you flashed in order to install the update.
The stock recovery can be extracted from "update.app" , the one inside the oreo "updateL22.zip"
Click to expand...
Click to collapse
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Thetpcguy said:
Hi, I'm downloading that UPDATEL22.ZIP right now and Can I extract this with any unzip/unrar program? What will be the name of that recovery? is it going to be "recovery"? The thing is I've never extracted anything from a ROM so I have not idea.
Click to expand...
Click to collapse
Hi, so I figured Huawei update extractor app is the way to do it but I have a Mac and there doesn't seem to be a Mac version? is there a way to do it on android or Mac?
mrmazak said:
you should already have the update.zip.
use same one you "manualy" installed.
winrar did not work for me but 7-zip did.
there is also rom extractor built into "multi-tool" and stand alone extractor around here some where.
I found it here
the name is just like the twrp you flashed and just like the partition that you flashed. (recovery_ramdisk.img)
Click to expand...
Click to collapse
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Thetpcguy said:
Hi, Thanks for all your replies. After doing a bit of search, I managed to get it extracted on my android using zarchiver app and I copied the recovery_ramdisk.img from that BNDL22.ZIP and when I tried flashing it using the fastboot command "fastboot flash recovery_ramdisk recovery.img" It went ok and It got installed but when I tried to boot into recovery, I got this screen "ERROR MODE" ATTENTION ETC.. I don't know where I'm going wrong?
Click to expand...
Click to collapse
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
i am wipeiing my data it always show faild plss help my device is dead
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Which perticular file should i flash for stock recovery please. There are 4-5 files. Pl help. I am on RR and want to flash system.img to go back to oreo beta. But i think i do not have stock recovery as i had tried to flash twrp. Pl help
Thetpcguy said:
Hi Dude, Great man. Your recovery worked like charm. But I did extract it properly from BNDL22.ZIP and I still don't know why it failed but thanks a ton. I hope this helps out other people reading
Click to expand...
Click to collapse
Hey bro thefe are too many files there will it flash through fastboot or twrp and how to flash one by one pls help me
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
mrmazak said:
I dont know.
The new way to boot to recovery was written in other thread as "hold both volume buttons & power button"
not sure if it was a problem with extraction or not, but attached is the recovery I extracted. do not have it installed. I dont even have oreo installed., I'm still pulling files together and reading the update-scripts and trying to convince myself if it is worth trying it.
https://www.androidfilehost.com/?w=files&flid=262391
I have now jumped on board and did oreo conversion on L24, then flashed RR. I went and installed the oreo recovery, then back to this stock recovery. It worked fine for me.
Click to expand...
Click to collapse
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
kingd421 said:
Can I flash just the stock recovery to my phone and if so is it the recover_ramdis.img, or do I need to flash them all. I'm on mostly stock bnd-l24. Unlocked bootloader TWRP and magisk for root. There's a new update and i wanted to flash stock recovery so I could update.
Click to expand...
Click to collapse
Yes that is the recovery.
But if you have root, update not going to work
mrmazak said:
Yes that is the recovery.
But if you have root, update not going to work
Click to expand...
Click to collapse
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
kingd421 said:
Will uninstalling magisk fix that or does the boot image have to be reflashed. Thank you for the quick response
Click to expand...
Click to collapse
From magisk manager app should be a restore images option
mrmazak said:
From magisk manager app should be a restore images option
Click to expand...
Click to collapse
Sounds good. I appreciate it.
aibiman said:
Hello all,
thanks for all the info in this thread.
I bricked my Honox 7x (BND-LC21) by trying to go Oreo.
The installation went halfway through, but now I can't complete (missing info howto flash bootloader / kernel) and I also can't go back as the partition layout has already changed to oreo style.
Steps done so far:
- unlocked boot loader
- installed twrp
- extract system image and recovery image from oreo update zip
getting the phone in fastboot mode i can successfully run
fastboot flash recovery_ramdisk recovery_ramdisk.img (i can also flash old recoveries this way, but none of them will successfully boot into recovery mode)
fastboot flash system system.img
either way, the system will not boot afterwards.
how do I manually flash bootloader / kernel on the oreo partition layout?
erecovery and hisuite won't recover my phone either...
Any hints appreciated
Aibiman
Click to expand...
Click to collapse
can you in to TWRP?
Hello. Just moved from iPhone to a OP3 and I am fairly new to the whole ROMing and rooting thing. My OP3 is currently in LineageOS 15.1 and I want to update to the Open Pie beta that OnePlus recently released..
What steps would I have to go through to do this? I have read that Bootloader needs to be locked back again but I do not know how to accomplish that. I have twrp as the recovery and rooted with magisk.
Any help will be very appreciated.
How to guide
INSTRUCTIONS - DOWNLOAD FILES
Go to https://eu.dl.twrp.me/oneplus3 and download TWRP recovery (.img file).
Go to https://www.oneplus.com/global/support/softwareupgrade > select your phone (OP3/OP3T).
2.1 Download stock 8.1 firmware (.zip file).
2.2 Download stock recovery (.img file).
Go to https://www.xda-developers.com/oneplus-3-oneplus-3ts-oxygenos-beta-android-9-pie/ and download your stock 9 firmware (.zip file). I see you mentioned this download link instead - well, if it's zip file, it's OK!
INSTRUCTIONS - PROCEDURE
Go to bootloader (AKA download mode) and flash TWRP recovery: fastboot flash recovery twrp_recovery.img
Go to your flashed TWRP recovery > Wipe > Advanced Wipe > Select everything ("USB OTG" might throw error - ignore) > Swipe to wipe. Screenshot on the web.
Copy stock 8.1 firmware to your phone (while in the same TWRP recovery) to /sdcard/ directory and flash it.
Go to bootloader and flash stock recovery: fastboot flash recovery recovery.img
While in bootloader, lock bootloader: fastboot oem lock. On the phone using volume buttons select "Yes" to lock bootloader. Your phone should show you some sort of wiping procedure on the screen and reboot to Oxygen OS with Android 8.1.
Move/Copy your stock 9 firmware to your phone internal storage (simply, while in Android), go to Settings > System updates > Click on top-right gear icon > Local upgrade > Select your stock 9 firmware zip file.
Once update is applied and phone rebooted, I STRONGLY suggest going into stock recovery and performing full factory reset ("wipe EVERYTHING").
QA
Q: Why Do I need to flash 8.1 if I can flash 9.0 in the first place?
A: Well, you can, but I tested it and only possible way to lock bootloader while being on stock 8.1 oxygenOS and recovery. If you flash stock recovery and oxygenos 9 - nothing happens when you lock bootloader.
Q: Any easier (or other) way?
A: Restoring to older version (don't remember if android 6 or 7 or 8) by following this guide. Then just simply apply upgrade via local upgrade. Not sure if bootloader will be locked afterwards. This also useful if you messed with partition sizes/partitions on your phone. Example.
SIDE NOTES
Battery life seem to be worse compared to SkyDragonOS. Not talking about missing customization options, but it's fine to me.
Google camera ports are still better option than stock camera on OxygenOS 9.
You rock my man. I will give it a shot. Thank you very much
javiwankenobi said:
You rock my man. I will give it a shot. Thank you very much
Click to expand...
Click to collapse
Just a word of caution. Wiping everything will wipe all your photos, videos etc. So backup everything beforehand.
I don't know where you read about bootloader having to be locked. For your information, I am running that ROM with bootloader unlocked. It is your call.
tnsmani said:
I don't know where you read about bootloader having to be locked. For your information, I am running that ROM with bootloader unlocked. It is your call.
Click to expand...
Click to collapse
Read it somewhere on reddit. But you're the third person to tell me it doesnt have to be unlcked, so I will go ahead and skip that.
I do have to install OOS 8.1 first tho right? or can I just flash the open beta update on TWRP after I do a factory reset?
javiwankenobi said:
Read it somewhere on reddit. But you're the third person to tell me it doesnt have to be unlcked, so I will go ahead and skip that.
I do have to install OOS 8.1 first tho right? or can I just flash the open beta update on TWRP after I do a factory reset?
Click to expand...
Click to collapse
I don't know. I happened to be on OOS 5.0.8 with bootloader unlocked when I flashed the Closed Beta Pie. When the Open Beta became available, I flashed it. On both occasions, I wiped all and my bootloader remains unlocked. In fact, I make it a point to remain unlocked always so that I don't face issues while flashing.
Flashable firmware / modem / baseband / RIL only (no full ROM).
Basically, it's a set of firmware/modem/baseband/RIL extracted from the OxygenOS Full ROM update payload and packed into a custom recovery flashable ZIP. Useful for users of a custom ROM, since the firmware/modem/baseband/RIL is never updated on most custom ROMs and thus becomes outdated. Those who use OxygenOS don't need this, since the firmware/modem/baseband/RIL is also updated with OTAs.
Important
If you have a OnePlus Nord (avicii) AC01AA, AC01BA or AC01DA and a custom ROM installed, feel free to proceed. However, I recommend making a backup before and get the unbrick tool from here, just in case.
Flash it with any (custom) recovery. It's not necessary to delete, wipe or format anything before or after installation.
Note: Packages are not signed.
Check the baseband version with: Settings → About phone → Android version → Baseband version
For OnePlus Nord - avicii - Android 12 based ROMs:
VersionModelDownload link11 F.20 AC01AAGlobalOnePlus_Nord_11-F-20-AC01AA_global_firmware.zip11 F.20 AC01BAEuropeOnePlus_Nord_11-F-20-AC01BA_europe_firmware.zip11 F.20 AC01DAIndiaOnePlus_Nord_11-F-20-AC01DA_india_firmware.zip
Baseband version after update: Q_V1_P14 or: MPSS.HI.2.5-01081-SAIPAN_GEN_PACK-1.7761.62_VENDOR
For OnePlus Nord - avicii - Android 10 and 11 based ROMs:
VersionModelDownload link11.1.10.10 AC01AAGlobalOnePlus_Nord_11-1-10-10-AC01AA_global_firmware.zip11.1.11.11 AC01BAEuropeOnePlus_Nord_11-1-11-11-AC01BA_europe_firmware.zip11.1.10.10 AC01DAIndiaOnePlus_Nord_11-1-10-10-AC01DA_india_firmware.zip
Baseband version after update: MPSS.HI.2.0.c9-00023-SAIPAN_GEN_PACK-1.422164.2.446371.2
Last Updated: 2023-06-04
Reserved 1
Reserved 2
Reserved 3
Great work! Thanks for the contribution.
can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance
Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".
hermesjconrad said:
Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".
Click to expand...
Click to collapse
I have included a safeguard so that these files cannot be accidentally installed on a device other than the Nord. But for some reason the LOS developers decided to name the device differently in LOS 17 recovery. In LOS 18 (or alternatively Orange Fox) recovery everything should work fine.
So I have removed this protection for now until an official LOS 18 or 19 is released. Download the appropriate package again and try to flash it again, it should now be able to be flashed with adb sideload.
Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?
vikd007 said:
can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance
Click to expand...
Click to collapse
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.
hermesjconrad said:
Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?
Click to expand...
Click to collapse
LOS recovery is totally OK if you only want to perform updates. But if you want to make backups and restore or want to get to the data partition, then it is no longer sufficient. Unfortunately there is still no official TWRP, so I use Orange Fox and it works great with the unofficial LOS 18, but you have to look in the Orange Fox thread there is a link to a newer version than the one in the opening post (see post 81 on page 5).
sniperle said:
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.
Click to expand...
Click to collapse
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".
Doc Sniper said:
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".
Click to expand...
Click to collapse
problem was there is no recovery for oos beta 12 as of now and no latest boot image
Managed to bork my phone by trying to upgrade magisk, managed to unbork by changing boot slots with fastboot, really neat.
Wanted to say thank you for providing the latest update file. Didn't need it in particular, but cool to have it and know it is available!
vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
I faced the same issue.. want to move on to a custom ROM but have 2 questions:
1. Does the phone loose Widevine L1 upon bootloader unlock on OOS12? I know i have to stop the phone from booting up after bootloader unlock and directly install the custom ROM, but i got stuck due to the recovery problem.
2. Does the custom ROM work good after this?
Hi,
Thank you for your work.
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
I have Magisk installed if it means anything in this case.
blorkraider said:
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
Click to expand...
Click to collapse
The ZIP files are not signed hence the message. But as far as I know, LOS-Recovery can also flash unsigned ZIPs. When the message appears, you can switch to yes with the volume buttons and then confirm with the power button. Then the ZIP should be installed.
Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.
mythos_ said:
Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.
Click to expand...
Click to collapse
According to the official Oneplus site, version 11 is still the current release version. Can you send me a download link to the release version of OOS 12? Thanks.