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
Hi All,
I just recently got my samsung galaxy tab 2 5110 with CM10 10.1.3 RC2, yesterday, i updated it with the latest nightly version of CM11 something like that cm-11.20141111_nighlty.zip and also with latest Gapps for CM11 found on cyanogenmod website. I used the latest recovery Philz touch CWM recovery (6.0.5.1).
Aftering upgrading the tab frequently shows the different gapps stop errors and sometime android process stop errors and getting stuck & restart frequently whenever i use it for some time.
Please anyone help me in this as im the newbie and its my first android device.
Maybe you should have had a stock tab for a while, and figured out all the do's & don'ts before you got involved with CM.
Full wipe.
Flash complete CM11 and gapps, that should clear up the problem.
Pp.
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
JJEgan said:
KK 4.4.2 is the last release from Samsung .
Android then see your models custom rom section .
Click to expand...
Click to collapse
I've just picked up a used 10.1 (first edition) and am hoping to get it onto 5.1.1 or 6.01.
I see a custom CM ROM from Cyanogen, that states it's 6.0 official, but when I go to the site the release is really old for the 8013, and I'm not sure if it's been grouped in with the more recent beta group that is linked in the thread or if it's not.
I also see an older Cyanogen thread for 12, but that's pre 6.0 and appears to be somewhat abandoned.
My Note 3 is on phronesis 6.0.1, and I would like to get the Note 10.1 to as close to that as possible, without dealing with any major bugs.
Thank you for your assistance.
Some progress.
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Basil Rathbone said:
I managed to update mine to Marshmallow 6.0.1 (cm-13.0-20160523-UNOFFICIAL-n8013.zip) via CWM v6.0.3.6 but Google Apps keeps crashing.
I've tried both open_gapps-arm-6.0-nano-20160721.zip (Open GApps) and gapps-600-base-20151107-1-signed.zip. Both take hours to install and just keep crashing whenever you try to do anything.
Anyone have any luck getting cm-13.0-20160523-UNOFFICIAL-n8013.zip / and GApps.zip working?
Click to expand...
Click to collapse
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Still no joy
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
bladebarrier said:
I had it crashing initially too, with CM-13.
I reinstalled the ROM, root, twrp, everything. I also made sure to install the latest "Stock" Gapps, before rebooting once the ROM was in place. Since then I have not had any issues.
I did however have some issues using the nano package. Hope that helps.
Click to expand...
Click to collapse
Basil Rathbone said:
I still can't get CM-13 to work. I use CWM. I made sure I was using the latest CWM 6.0.4.6.
I booted into CWM, factory reset and cleared cache. Flashed cm-13.0-20160523-UNOFFICIAL-n8013.zip.
I then factory reset and cleared cache again and flashed gapps-600-base-20151107-1-signed.zip.
I then factory reset and cleared cache again and rebooted.
No joy.
What actual gApps and CM-13 did you use? Maybe I need to use the same version of TWRP as you used?
I'm stumped.
--------------------------------------------------------------------------------
Click to expand...
Click to collapse
I used the ARM 6.0 Stock version for CM 13. http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
I ended up swapping to the 2014 model because I got a good deal on a Verizon version (which is locked but oh well), so I don't recall the TWRP that I ran. It sounds like that sometimes gives people issues.
I do recall that using the nano version of gapps was not working for me. Could be a coincidence, but I had constant crashes when I tried using it.
This is the thread I used to grab the ROM and TWRP: http://forum.xda-developers.com/galaxy-note-10-1/development/rom-lollipop-t3269375
It helps to read the installation notes properly
The problem(s) I was having were resolved by using twrp-2.8.7.0-gt-n8013 instead of N8013-CWM-Touch-6.04.6. I also used open_gapps-arm-6.0-stock-20160803 instead of nano but I really think it was TWRP that made everything work.
I'm now running cm-13.0-20160523-UNOFFICIAL-n8013 without any problems.
I consider this thread closed.
Basil Rathbone said:
If the following table is correct then I have a GT-N8013. I'm running KitKat 4.4.2 on it: (N8010XXUDNE4_N8010BTUDNF1_BTU_N8013.tar.md5).
How close can one get to the latest version of Android and still have a working GT-N8013?
GT-N8000 - Wifi+3G+calling
GT-N8005 - Wifi+3G
GT-N8010 - Wifi (Except USA)
GT-N8013 - Wifi (Only USA)
GT-N8020 - Wifi+LTE
Click to expand...
Click to collapse
How did you get KitKat on n8013. It was never released and no one successfully flashed 4.4 n8010 to n8013. Odin keeps giving an error. Please I've been trying for years now since it's been 2 years since update was released and doesn't look like it'll ever release (**** yoi Samsung with your update **** and regions)
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
MrAwesome75 said:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Well official only kitkat if you are international (Samsung decided not to release a lot of device updates in the us for kit kat including the s3, galaxy light, and this one). However I think you can get CM 13.1, idk about anything more recent but there is a (slightly) active community for it still left. Its a shame that this flagship tablet was neglected. I hope it doesn't happen with future Samsung ones but I've avoided buying any. I still use mine on jellybean for basic internet browsing and games
zMrAwesome75 said:
Quote:
Anyone have any luck? I've had this tablet since 2013 and I stopped using it because it has always been such a laggy sluggish experience. I thought I would try putting an AOSP ROM on it to see if that helped. Everything is so old for this device that it's nearly impossible to find the old files, ROMs, recoverys, etc. I can't even get TWRP or CWM to work on it. Maybe it's not worth the trouble anymore.
Click to expand...
Click to collapse
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
7.1.2 on GT-N80013
I am currently running an unoffical build I picked up here on xda it is an unofficial Lineage OS build. I haven't currently found any bugs... camera works, bluetooth works, wifi works... at least for me. The build number is 14.1-20170810-unnofficial-n8013
Hannover2k said:
Not sure if you're still looking but I just installed Android Nougat v7.1.2 using the instructions provided here:
https://forum.xda-developers.com/showthread.php?t=2185119
I have a N8010 that topped out at 4.1.2. I flashed to a N8013 kernel/rom about 2 years ago which maxed out at 4.2.2 . I just recently found that link to the LineageOS build (Formerly Cyanogenmod) when I was contemplating buying a new tablet. The tablet was getting a bit sluggish so I decided to go ahead and blast it out and see what happened. I was VERY pleasantly surprised! Had some issues getting the Recovery flashed but once I did, it was pretty smooth from there. I had backed up all the apps so once I got it booted and restored all the apps, I was surprised how responsive it is. Oh, and you can say goodbye to all those SD card issues that the Note 10.1 had since this version of Android integrates the external SD with the internal SD so everything gets installed on the external card. No need for apps like folder mount, etc.
I highly recommend it. The only issue is that you lose the integrated S-Pen functionality but you can reinstall some of those apps from the play store and bring back a lot of those features. Some 3rd party apps actually work better.
Good luck!
Click to expand...
Click to collapse
I'd appreciate a link to the rom you installed. Thx.
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
cloves said:
I'm interested as well I'm still running original os. Also wondering if the rom update works well on these tablets since they are older. As Android matures the os gets bigger which can impact performance on older CPUs.
Click to expand...
Click to collapse
I recently installed Lineage OS 14 and it is working great.
Tablet is stable, everything works, great battery life.
All devices work gps, etc...
The s-pen will not work like it did stock but there are apps you can get that seem to work better
Squid and Sketch for drawing....squid seems cool if you write with stylus
Install Magisk instead of supersu.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
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