Hi guys, a few days ago I posted something about a CM12 update here http://forum.xda-developers.com/oneplus-one/help/update-to-ota-recovery-issue-t3143078 and as somebody pointed out the cause of the problem might be the fact that the TWRP error that I get when I try to install the update says that I have android 4.4.4 whereas I have CM12 (hence the new post). Let's have a look at this, here is the screenshot of the error message http://s28.postimg.org/zb06wtcpp/OTA_error.jpg
As you can see here instead http://s17.postimg.org/mvd5vekjz/settings.png I have CM12 5.0.2 (which is stock as the phone came shipped with CM).
Now, is there any way we can get what TWRP says to match the version of android I have?
thanks
Related
Hello guys
I have an HTC One Mini 601E, and today I've try to install Android Kitkat 4.4.2 via CyanogenMod ( by following the procedure on ibtimes, update-htc-one-mini-android-4-4-2-kitkat-via-cyanogenmod-11-rom-1433685 [sorry it seams I cannot post any link as new member...]) so I rooted the phone, installed SuperSU and installed a recovery mod and everything necessary but after trying to install the zip "Android 4.4.2 KitKat Cyanogenmod 11 ROM" few time and with first ClockworkMod and then also TWRP recovery tools I still get the same error : set_metadata_recursive: some changes failed" (Status 7). (even using recovery base Phil..)
I've try few things to try to solve it lbut still get the same error. So I'm wondering why and how I could resolve this. I'm thinking also that this phone is 601E and not 601S. I mean, this phone come from Taiwan, my girlfriend bought it for me but I'm in Australia actally. I know there is just a little difference about the baseband between these two model (601E and 601S). So I was wondering that maybe I need a different version of the Android 4.4.2 KitKat for my phone that come from Taiwan ? I don't know.. but actually I cannot do anything with my phone, when I turn it on I can see the logo HTC and then it reboot again. I can only access the fastboot menu and the recovery mod.
So my questions are :
- How could I successfully install this Android 4.4.2 KitKat Cyanogenmod 11 ROM on my phone ?
- And if it is just not possible or just not working, how can I come back to the previous Android OS that was installed before (Jelly bean) ?
I think to understand that I need a RUU m4 for my phone, I've found some on the website androidruu.com in the M4 RUU category) but I'm not sure if it is the right RUU file for my phone version.
I hope my phone is not broken and hope also to find some help here also sorry for my english is not perfect I hope it is enough clear
Thank you very much for any help.
Jona
I successfully installed another mod but based on Android 4.3, not 4.4 Kitkat.So it's ok
But if somebody know or have an idea about how I could install Android 4.4, I still interesting
Thank you
Hello all
I have XT1032 (GPE), and I had CM11 on it (nightly from 1106, I believe).
Today I downloaded the latest CM12 nightly (0115), and tried installing it from TWRP. The installation failed (I keep getting "Error executing updater-binary"), and I remained with no system partition.
I tried many guides and tips (the most promising one was this), but nothing seemed to work.
If I understand correctly, there is some problem in installing CM12 over 4.4.4 (from CM11).
I somehow managed to get to stock 4.4.4, but I'd much prefer to get back to CM11. However, all the download links on CM website don't seem to work over a week back, or something. Is there some other mirror with CM11 I can use, in the meantime? Maybe someone in here has a relatively recent CM11 zip file he can send me?
And what about a real solution to the problem? Is there a way to install CM12 on my stock 4.4.4? Am I the only one who got this error?
Thank you for your help.
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2
Good morning guys, sorry about the english. So, a while back I installed the 12.1 cm in my GT I9515L (Galaxy S4 VE), the rom was running normally, but i had some problems in some applications that were not compatible with the version BOJ1 (Lollipop). I performed the downgrade of the same for AJN1 (KitKat) to reinstall the CyanogenMod above, the problem is that whenever I go into recovery mode, time to flash the GAPPS, one error appears saying that the version isn't compatible. I performed the test of reset the machine without installing any version of gapps, and the cell was automatically updated to version Lollipop. I would like to ask for your help because I am unable to keep KitKat version in Cyano. I think that it's a litte mine mistake on wipes or in version of cyano, but I googled a lot and found nothing. Thank you guys.
I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/samsung-a-series/orig-development/rom-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entry/-Firmware-Download-Samsung-Galaxy-A3-SM-A300FU-Official-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
XDA Visitor said:
I have been running Cryogenmod 12.1 for my Samsung SM-A300FU but its UNOFFICIAL and a preview the webpage i got it off says 'Wifi and Camera NOT WORKING'. I guess thats what i get for following my mates advice.
Because of this, i looked at CM13 (Android 6) which i got off the XDA site and i have made sure it is for my phone and model, the SM-A300FU. Of course, being my luck it didnt work. I get the error of 'Executing updater binary in zip' and i have wiped my phone then tried to install it and i have also tried to completly remove all OS and files then install it which apparently fixed it for people, but not me of course. In a desperate measure i even bluetoothed the ROM to another phone then back into my SM-A300FU to get it onto the internal storage but that obviously didnt change anything.
Finally, i gave up and tried to downgrade back to Android 5.0.2 although this isnt a CM zip. Once again, this ROM doesnt work. It just gives me an error saying it failed, no reason in particular.
I have a few issues for a whole range of files. Any help in fixing any or all of these would be much appreciated.
Links to the files I sites i downloaded the files from:
CM 12.1 UNOFFICIAL (Not meant to work fully) - https://forum.xda-developers.com/sa...m-cyanogenmod-12-1-samsung-galaxy-a3-t3273323
CM 13 (Doesnt install) - https://forum.xda-developers.com/sa...-cyanogenmod-13-0-unofficial-samsung-t3326297
Android 5.0.2 ROM (Doesnt install) - http://www.youmobile.org/blogs/entr...ial-Android-5-0-2-Lollipop-update-Rolling-out
So to reitterate: I installed the CM 12.1 ROM without issues but it turns out to be a mod that doesnt work fully meaning its unsuitable for me. I downloaded CM 13 but this gets an error. I downloaded a Android 5.0.2 ROM which has an error it doesnt even tell me about.
Click to expand...
Click to collapse
Greetings and welcome to assist. Which recovery are you using ? Have you tried to update to the latest ? Also if that doesn't work try using odin to go back to latest stock then reflashing custom recovery
Why not make an account and let the experts here
https://forum.xda-developers.com/samsung-a-series
guide you
Good Luck
Sawdoctor