Related
Hi guys.
So i was on the latest version of CM11s, rooted with supersu and with the latest version of TWRP recovery installed.
I got the ota update for CM12 and proceeded to install it with the option to update recovery unchecked as i did many times before.
To my surprise after the update i've noticed that i have now the stock recovery. So i fastboot flashed TWRP again but it seems to not work. Of course it says that the file transfer and the flashing is done while on fastboot mode.
Any clues? Thanks
I managed to find my answer. Thank you guys for your unlimited support <3
DuckMcQUack said:
I managed to find my answer. Thank you guys for your unlimited support <3
Click to expand...
Click to collapse
Hey can you post the solution here? I'm having the same problem and on top
of it, my MTP storage won't mount
Cheshire88 said:
Hey can you post the solution here? I'm having the same problem and on top
of it, my MTP storage won't mount
Click to expand...
Click to collapse
Hey,
the problem is that starting from Cyanogen OS 12 the system always overrides the custom recovery. TWRP has a feature for patching the system not doing that. All you have to do is to flash TWRP via fastboot and then immediately boot into recovery! If TWRP shows up, it'll automatically patch the system
TheCrazyLex said:
Hey,
the problem is that starting from Cyanogen OS 12 the system always overrides the custom recovery. TWRP has a feature for patching the system not doing that. All you have to do is to flash TWRP via fastboot and then immediately boot into recovery! If TWRP shows up, it'll automatically patch the system
Click to expand...
Click to collapse
Or just untick update cyanogen recovery in developer options
darsh1994 said:
Or just untick update cyanogen recovery in developer options
Click to expand...
Click to collapse
No, read OP Post
TheCrazyLex said:
No, read OP Post
Click to expand...
Click to collapse
Didn't read carefully! My bad!
This is all covered in the FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
Can't figure out why people don't read the stickies...
Transmitted via Bacon
So today I saw that the 12.1 update is downloaded and asking me to install it. But, when I do try installing it the screen is stuck at the Cyanogen Recovery.
The usual options in recovery screen are displayed, why isn't the OS updating?
FYI - My OPO is rooted and also has TWRP recovery installed. I also tried disabling the Update Cyanogen Recovery option but the same option.
Any assistance would be great
SagarRox said:
So today I saw that the 12.1 update is downloaded and asking me to install it. But, when I do try installing it the screen is stuck at the Cyanogen Recovery.
The usual options in recovery screen are displayed, why isn't the OS updating?
FYI - My OPO is rooted and also has TWRP recovery installed. I also tried disabling the Update Cyanogen Recovery option but the same option.
Any assistance would be great
Click to expand...
Click to collapse
You can't flash the OTA with TWRP recovery. You can either flash the stock recovery and then install the OTA, or you can download the full ROM zip and flash that with TWRP.
Heisenberg said:
You can't flash the OTA with TWRP recovery. You can either flash the stock recovery and then install the OTA, or you can download the full ROM zip and flash that with TWRP.
Click to expand...
Click to collapse
Heisen
Sorry, a little question (and sorry to the OP)
Ive try to install the ota manually (i was rooted with twrp) flashing back the cm recovery, but it doesnt work still.
So ive flash the twrp 2.8.6 (for the baseband not installing prolems) and downloaded the full rom file, flashed in twrp without any wipes... Its all ok now, should i have problems with this method?
The baseband is 241,is correct?
Thx for helping
L.
lollaz said:
Heisen
Sorry, a little question (and sorry to the OP)
Ive try to install the ota manually (i was rooted with twrp) flashing back the cm recovery, but it doesnt work still.
So ive flash the twrp 2.8.6 (for the baseband not installing prolems) and downloaded the full rom file, flashed in twrp without any wipes... Its all ok now, should i have problems with this method?
The baseband is 241,is correct?
Thx for helping
L.
Click to expand...
Click to collapse
You shouldn't have any issues.
Heisenberg said:
You shouldn't have any issues.
Click to expand...
Click to collapse
Hi,
I am facing the same issue while updating the official update. I tried updating using the Cyanogen recovery but it is giving a failed error: "Unable to open the zip file" something like this. i have downloaded the 305 Mb update again manually but of no use.
Please help on this.
TIA
Nav07 said:
Hi,
I am facing the same issue while updating the official update. I tried updating using the Cyanogen recovery but it is giving a failed error: "Unable to open the zip file" something like this. i have downloaded the 305 Mb update again manually but of no use.
Please help on this.
TIA
Click to expand...
Click to collapse
Are you currently on the build directly before this one?
Heisenberg said:
Are you currently on the build directly before this one?
Click to expand...
Click to collapse
Dear, i am frankly not a techie. I am using the stock (default) RAM only. Would be great if you can help on this
Nav07 said:
Dear, i am frankly not a techie. I am using the stock (default) RAM only. Would be great if you can help on this
Click to expand...
Click to collapse
You don't need to be a techie to know that the updates must be taken in order. Go to Settings>About Phone, take screenshots of the info there and post here so I can see please.
Heisenberg said:
You don't need to be a techie to know that the updates must be taken in order. Go to Settings>About Phone, take screenshots of the info there and post here so I can see please.
Click to expand...
Click to collapse
Currently the Cyanogen version is 12.0-YNG1TAS2I3, OS version is 5.0.2, Build number is LRX22G
Nav07 said:
Currently the Cyanogen version is 12.0-YNG1TAS2I3, OS version is 5.0.2, Build number is LRX22G
Click to expand...
Click to collapse
You're on the right version. The zip must be getting corrupt during the download or something.
Heisenberg said:
You're on the right version. The zip must be getting corrupt during the download or something.
Click to expand...
Click to collapse
I have manually downloaded the zip file again apart from the Official update but it is still not getting through
Can anything else be done on this?
Nav07 said:
I have manually downloaded the zip file again apart from the Official update but it is still not getting through
Can anything else be done on this?
Click to expand...
Click to collapse
Try downloading the full zip from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that with recovery.
Hi, there is an update available for CM13 and I don't know how to install it. I've heard I need to flash it using a custom recovery (I use TWRP) but do I also need to clear the dalvik and cache? Will this uninstall my apps?
The first thing that you need to do is download latest build and Gapps then for optimal performance wipe everything (caches, system, data).
After that put these files in your sdcard then boot into TWRP and then install it zip as usual.
Paradox♀ said:
The first thing that you need to do is download latest build and Gapps then for optimal performance wipe everything (caches, system, data).
After that put these files in your sdcard then boot into TWRP and then install it zip as usual.
Click to expand...
Click to collapse
will that uninstall my apps? What if I don't wipe everything, will I need to still flash gapps?
harut2K said:
will that uninstall my apps? What if I don't wipe everything, will I need to still flash gapps?
Click to expand...
Click to collapse
U can also do a dirty update (apps and data remain).
Andus1988 said:
U can also do a dirty update (apps and data remain).
Click to expand...
Click to collapse
How do I do that? (P.S. is doing a dirty update dangerous? Like, is there a chance of bricking my device?)
harut2K said:
How do I do that? (P.S. is doing a dirty update dangerous? Like, is there a chance of bricking my device?)
Click to expand...
Click to collapse
U have to download latest ROM via CM updater and click "apply update" or something like that (my phone is on german so I don't know how it's named on other languages). Then your phone automatically restarts into recovery, performs all the steps automatically and also reboots automatically.
I always do dirty updates and never faced any issues!
Andus1988 said:
U have to download latest ROM via CM updater and click "apply update" or something like that (my phone is on german so I don't know how it's named on other languages). Then your phone automatically restarts into recovery, performs all the steps automatically and also reboots automatically.
I always do dirty updates and never faced any issues!
Click to expand...
Click to collapse
Mine is unofficial, my phone is a Moto G first gen (falcon) and i don't have that "apply update" thing, so I have to do it manually.
harut2K said:
Mine is unofficial, my phone is a Moto G first gen (falcon) and i don't have that "apply update" thing, so I have to do it manually.
Click to expand...
Click to collapse
I thought we're talking about the official CM 13 The update procedure surely is described in the startpost of your ROM!
Andus1988 said:
I thought we're talking about the official CM 13 The update procedure surely is described in the startpost of your ROM!
Click to expand...
Click to collapse
No, its just how to install CM13 on Android 5 and how to upgrade from CM12.1 (http://forum.xda-developers.com/mot...fiicial-cyanogenmod-13-moto-g-t3229272/page56) and the thread is closed so I can't ask him.
harut2K said:
No, its just how to install CM13 on Android 5 and how to upgrade from CM12.1 (http://forum.xda-developers.com/mot...fiicial-cyanogenmod-13-moto-g-t3229272/page56) and the thread is closed so I can't ask him.
Click to expand...
Click to collapse
Which ROM do u use at the moment? The thread u linked was an unofficial CM 13 (=Android 6.0)!
Andus1988 said:
Which ROM do u use at the moment? The thread u linked was an unofficial CM 13 (=Android 6.0)!
Click to expand...
Click to collapse
Yes its that unofficial ROM! I'm running CM13 unofficial
harut2K said:
Yes its that unofficial ROM! I'm running CM13 unofficial
Click to expand...
Click to collapse
I would prefer a clean install (download ROM and GAPPS; reboot into recovery; wipe data, system, cache and dalvik cache; flash ROM and GAPPS; reboot)! On this way u will "lose" your apps but userdata (e. g. photos) is still there!
Andus1988 said:
I would prefer a clean install (download ROM and GAPPS; reboot into recovery; wipe data, system, cache and dalvik cache; flash ROM and GAPPS; reboot)! On this way u will "lose" your apps but userdata (e. g. photos) is still there!
Click to expand...
Click to collapse
I really want to avoid uninstalling my apps, is there any other way without removing my apps?
harut2K said:
I really want to avoid uninstalling my apps, is there any other way without removing my apps?
Click to expand...
Click to collapse
Do the described above without wiping data (but that could fail). But remember: You're coming from another ROM so wiping data is recommended!
The Screenshot is below. I got stuck in the H2OS 2.0 so I flash the cos12 to save it from bricking. Then I flash the TWRP. When I wanted to flash a CM13,the problem in the screenshot occurred. Need some Help here.
Help,PLZ
I don't have another phone.I gotta fix this as soon as possible in case I don't miss any important phone calls. plz. Somebody gives me a hand.
The problem is that you're not installing the TWRP flashable rom.
See that the zip file of the CM13 build you tried to install is called cm13......bacon-signed-fastboot......zip. So you're trying to install a fastboot rom with a custom recovery, instead of trying to install a custom rom for a custom recovery. That's why TWRP doesn't found any meta-inf folder.
When downloading the rom in the official web be sure to download the one compatible with custom recoveries.
mustang_ssc said:
The problem is that you're not installing the TWRP flashable rom.
See that the zip file of the CM13 build you tried to install is called cm13......bacon-signed-fastboot......zip. So you're trying to install a fastboot rom with a custom recovery, instead of trying to install a custom rom for a custom recovery. That's why TWRP doesn't found any meta-inf folder.
When downloading the rom in the official web be sure to download the one compatible with custom recoveries.
Click to expand...
Click to collapse
Okay,Thanks. But when I tried another ROM (NucleaRom-V2.1.4-BETA[7.0]-bacon-20161011-0245.zip) ,I failed again. It occurred error 7. The TWRP is universal in many ROMs,right?I used to installed many with it successfully.However, I failed again and again this time.
SimonYJB said:
Okay,Thanks. But when I tried another ROM (NucleaRom-V2.1.4-BETA[7.0]-bacon-20161011-0245.zip) ,I failed again. It occurred error 7. The TWRP is universal in many ROMs,right?I used to installed many with it successfully.However, I failed again and again this time.
Click to expand...
Click to collapse
The 7 error use to happen when you get a bad download and there is missing data. You can compare the md5 of the rom to check if there are missing data or simply download it again, or try another rom.
Also i suggest you to use the latest TugaPower TWRP.
mustang_ssc said:
The 7 error use to happen when you get a bad download and there is missing data. You can compare the md5 of the rom to check if there are missing data or simply download it again, or try another rom.
Also i suggest you to use the latest TugaPower TWRP.
Click to expand...
Click to collapse
Actually,I'm using the latest TeamWin - TWRP. Here is the screenshot. I downloaded the cm13 official but it didn't work too. Could you give a guide to get a Tugapower TWRP? Maybe it will work with the TugaPower TWRP.
SimonYJB said:
Actually,I'm using the latest TeamWin - TWRP. Here is the screenshot. I downloaded the cm13 official but it didn't work too. Could you give a guide to get a Tugapower TWRP? Maybe it will work with the TugaPower TWRP.
Click to expand...
Click to collapse
Did you do wipes (system, data, cache and dalvik cache) before flashing the roms?
mustang_ssc said:
Did you do wipes (system, data, cache and dalvik cache) before flashing the roms?
Click to expand...
Click to collapse
yea,of course. This problem began at my last ROM(H2OS V2.0.1). Is it the main reason? Before that ROM ,everything goes well.
SimonYJB said:
yea,of course. This problem began at my last ROM(H2OS V2.0.1). Is it the main reason? Before that ROM ,everything goes well.
Click to expand...
Click to collapse
Well, honestly i don't know.
I would suggest you to check if the files you have downloaded are not corrupted in case the computer where you're downloading the roms is corrupt them, i experienced that case. So you can check md5 following this guide: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/113984-what-md5-how-use-verify-your-download.html
And the TWRP i suggested you is here: http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366. You can install it though fastboot or try with the current recovery you have.
mustang_ssc said:
Well, honestly i don't know.
I would suggest you to check if the files you have downloaded are not corrupted in case the computer where you're downloading the roms is corrupt them, i experienced that case. So you can check md5 following this guide: http://forums.androidcentral.com/optimus-v-rooting-roms-hacks/113984-what-md5-how-use-verify-your-download.html
And the TWRP i suggested you is here: http://forum.xda-developers.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366. You can install it though fastboot or try with the current recovery you have.
Click to expand...
Click to collapse
Thank you very much. I really appreciate it. I'll try as you say.Hope the issues can be solved.:good:
Hello Guys i recently i found an official supported rom for hima ul on mokee webiste would like to share it here.The rom is based on android 7.1.2 It is fully stable and can be used as a daily driver
UPDATE: 2017-5-1
Rom has been updated to nougat
Download
IF YOU HAVE STATUS 6 OR 7 ERROR IN TWRP NOTE: open the downloaded rom zip and open the following file located in
x.zip/META-INF/com/google/android/update-script
and remove the following line to avoid errors in TWRP
"Assert(hima.verify_sbl1("1.2.50.1.36") == "1");"
happy flashing :good:
I tried this rom and loved it. But after some weeks my phone only show black screen and does not reboot. Don't know if mokee causes the failure. Or if it was a hardware issue. I think the second.
I got a brandnew m9 phone and use another nougat rom.
And yes. Mokee 60.1 is Android 6 and cam works.
mega_man said:
Hello Guys i recently i found an official supported rom for hima ul on mokee webiste would like to share it here.The rom is based on android 6.0 source so i guess the camera is working
Download
Please test it out and share screenshots of it thanks
Click to expand...
Click to collapse
MoKee is one great rom,i was using it and it is sooo stable and u can always count on updates regulary,when i get born of sense,i use this rom.
Nice that here on XDA is a mokee thread in m9 section. The rom deserves its own thread.
please share some screenshots of the rom so i can update the thread @dsg2003 @Boskoel03
So it's marshmallow?
rjcreations said:
So it's marshmallow?
Click to expand...
Click to collapse
yes marshmallow full stable with working camera
dsg2003 said:
Nice that here on XDA is a mokee thread in m9 section. The rom deserves its own thread.
Click to expand...
Click to collapse
I was using it,not now,so i can not help u at the momment... U have it all,and all the rest info about the rom on their G+ page...
Same here. I used it some time ago. So I cannot show screenshots.
Give it a try. Make a nandroid backup before, so you can switch back easily, if you don't like mokee.
Advice for you: I had to make changes in updater script before flashing. Without that, twrp gets error by me. Look in Slim7 Rom thread. There is described how to change updater script. You have to delete some words in it.
dsg2003 said:
Same here. I used it some time ago. So I cannot show screenshots.
Give it a try. Make a nandroid backup before, so you can switch back easily, if you don't like mokee.
Advice for you: I had to make changes in updater script before flashing. Without that, twrp gets error by me. Look in Slim7 Rom thread. There is described how to change updater script. You have to delete some words in it.
Click to expand...
Click to collapse
please tell in detail which changes you made so i can update OP
You have to try. Perhaps you must not change anything.
Some users have to make changes.
The updater-script is located in /META-INF/com/google/android/updater-script. Look at Slim7 Thread here on xda. There are posting to that.
I did not had to add or remove anything to flash this rom,think it is not for all phone models like that,do some research about it before u post to op...
can anybody share the screenshots of this rom ??
Alright so I tried flashing this ROM without modifying the zip and got the ERROR 7 message. I removed the line mentioned in the first post and still cannot get the ROM to install, same error. Any ideas? My model is himauhl
calikevin said:
Alright so I tried flashing this ROM without modifying the zip and got the ERROR 7 message. I removed the line mentioned in the first post and still cannot get the ROM to install, same error. Any ideas? My model is himauhl
Click to expand...
Click to collapse
U must if comming from sense based rom from twrp delete everything,not internal but data cashe dalvik and system,then install this one...
Boskoel03 said:
U must if comming from sense based rom from twrp delete everything,not internal but data cashe dalvik and system,then install this one...
Click to expand...
Click to collapse
I did that, cache, dalvik cache, and system, even wiped twice then rebooted back into recovery and still got the same error.
calikevin said:
I did that, cache, dalvik cache, and system, even wiped twice then rebooted back into recovery and still got the same error.
Click to expand...
Click to collapse
U did than,then rebooted to recovery!? Idk from where u did that,but wipe must be done from recovery,no just factory reset,but wipe from advanced wipe option in recovery...
Boskoel03 said:
U did than,then rebooted to recovery!? Idk from where u did that,but wipe must be done from recovery,no just factory reset,but wipe from advanced wipe option in recovery...
Click to expand...
Click to collapse
I was in recovery when I wiped everything, tried flashing the ROM which didn't work, then rebooted back into recovery. I thought that was self explanatory
calikevin said:
I was in recovery when I wiped everything, tried flashing the ROM which didn't work, then rebooted back into recovery. I thought that was self explanatory
Click to expand...
Click to collapse
which frimware version are you running and which rom you were on previously
mega_man said:
which frimware version are you running and which rom you were on previously
Click to expand...
Click to collapse
I'm running the LeeDroid Marshmallow ROM, the exact firmware version I'm not sure of but I can probably find out from the ROM thread if necessary. Android version is 6.0