good afternoon people ! I have a Lg nexus 5 Hammerhead if someone can help me thank you very much, my problem is as follows I am trying to install the lineage The 17.1 android 10 so far all right the problem is when installing the gapps because of the error 70 I have always tried almost everything and nothing works TWRP is updated all right I tried since the gapp pico to stock could someone help me please already extract the gapp and delete the size folder and even then it didn't work.
Related
Hello first of all let me tell you that you do a great job here at XDA, I need help, I installed cyanogenmod 11 ver. 7 and nothing more, but this morning I tried to install the User GAAps but I get a message saying installation has been aborted, I have not linked my e-mail to my device only installed the link2sd.apk, I really like this ROM and want to have it working at a 100%, all your help will be very much appreciated.
elsapito said:
Hello first of all let me tell you that you do a great job here at XDA, I need help, I installed cyanogenmod 11 ver. 7 and nothing more, but this morning I tried to install the User GAAps but I get a message saying installation has been aborted, I have not linked my e-mail to my device only installed the link2sd.apk, I really like this ROM and want to have it working at a 100%, all your help will be very much appreciated.
Click to expand...
Click to collapse
The system partition is too small, 190 MB, for a full ROM installation and GAPPs too. The ROM should be trimmed either before installing to the device or while on the device but before installing GAPPs. View the LG Optimus One FAQ for more information. In my signature there is also a tool designed specifically for trimming ROMs built for the O1 called OOne ROM Editor.
Hello from Regensburg, Germany. Please help! I am still a greenhorn in the field and HERE IS THE PROBLEM: I tried to install the latest CM 13 nightly on the Samsung Galaxy S5 klte. I must have tried 7 or 8 different Gapps packages (mostly from Open Gapps) without success. Everything looks good until I reboot the system. Then I get constant popup messages telling me "unfortunately Google Playstore has stopped". This happens with ALL the gapps I have tried. Maybe it is not a Gapps problem but something else??? I am desperate because I have already spent hours and hours with this. Before that I had CM 12 snapshot installed and it worked really nicely. I always did all the wipes (System, Data, Cash, Dalvik) before flashing and tried again and again (ca. 15 times so far...). I have TWRP recovery installed.
Hello and thank you for using XDA Assist,
this was a problem in the last nightly. It should be fixed in the newest Nightly from today.
Kind regards
Trafalgar Square
XDA Assist
schnoeselmeier said:
Hello from Regensburg, Germany. Please help! I am still a greenhorn in the field and HERE IS THE PROBLEM: I tried to install the latest CM 13 nightly on the Samsung Galaxy S5 klte. I must have tried 7 or 8 different Gapps packages (mostly from Open Gapps) without success. Everything looks good until I reboot the system. Then I get constant popup messages telling me "unfortunately Google Playstore has stopped". This happens with ALL the gapps I have tried. Maybe it is not a Gapps problem but something else??? I am desperate because I have already spent hours and hours with this. Before that I had CM 12 snapshot installed and it worked really nicely. I always did all the wipes (System, Data, Cash, Dalvik) before flashing and tried again and again (ca. 15 times so far...). I have TWRP recovery installed.
Click to expand...
Click to collapse
Thank you so much for your fast reply. I had actually tried again and again with two different nightlies, yesterday's and the day before yesterday's, without success. I will give it another try with today's (or tomorrow's) nightly. Do you happen to know when a CM13 stable release can be expected? Maybe I should just wait for that...
Hey,
no, I don't know when there will be a snapshot.
Todays nightly should be good.
Thanks again! Yesterday's nightly was fine and I was finally able to install CM 13. Do you suggest to always update nightlies or rather stay with one that seems to work?
It's OK, if you update every month.
But you can update weekly or daily too
Trafalgar Square said:
It's OK, if you update every month.
But you can update weekly or daily too
Click to expand...
Click to collapse
Thanks again!
BTW I found one bug in the day before yesterday's nightly: The calender did not work, so i deinstalled it and installed Google Calender from the Playsstore...
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
Gotta old Nexus 5 that I have put Linage 17.1 on. 17 being of course android 10. Went fine.
Then I tried to flash open gapps on to it and I get an error code 70.
It is telling me that I don't have enough space even through I was using pico
I'm not big on re-partitioning anything for fear of bricking my phone.
I would try mindthegapps but they only have flashes for andriod 8 and 9.
What should i do?
Try and use linage 16?
Any thoughts would be welcome.
Thanks
Ok, first of all if you had read through any threads about ROMs based on Android 9 and up, you would see that the repartitioning process is mandatory in case you want to flash any gapps package (yes, even pico). The error you get is because the stock system size of our device is around 1GB, which is not enough for the more recent Android versions ROMs + Gapps to fit. With LOS 16, you will get the same results / errors. Therefore, repartioning is the way to go.
An alternative would be to flash an an older Android version ROM which does not take as much space. In this case I would recommend razorloves's unofficial LOS 14.1 builds which are based on Nougat and ROM is still being maintained.
So long story short, up to Oreo, you are fine with stock partition. Pie and up, you need repartition!
3suns said:
Gotta old Nexus 5 that I have put Linage 17.1 on. 17 being of course android 10. Went fine.
Then I tried to flash open gapps on to it and I get an error code 70.
It is telling me that I don't have enough space even through I was using pico
I'm not big on re-partitioning anything for fear of bricking my phone.
I would try mindthegapps but they only have flashes for andriod 8 and 9.
What should i do?
Try and use linage 16?
Any thoughts would be welcome.
Thanks
Click to expand...
Click to collapse
I followed the necessary instructions to repartition here
https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
3suns said:
Gotta old Nexus 5 that I have put Linage 17.1 on. 17 being of course android 10. Went fine.
Then I tried to flash open gapps on to it and I get an error code 70.
It is telling me that I don't have enough space even through I was using pico
I'm not big on re-partitioning anything for fear of bricking my phone.
I would try mindthegapps but they only have flashes for andriod 8 and 9.
What should i do?
Try and use linage 16?
Any thoughts would be welcome.
Thanks
Click to expand...
Click to collapse
Lineage 16 also needs re-partitioning, I am running 15.1 which I build myself.
Hi. for 2 days I have been googling and looking on this forum on which rom is best for nexus 2012, but I can't find anything at all. most posts are for 2013 version or outdated with dead links.
I was able to get lineage 14.1 on it, but it was missing google play, after following some guide here and installing Gapps, it then stopped booting. it got stuck on the google logo and that's it. lineage 14.1 itself worked fine, installation of gapps succeeded, but simply won't boot. tried several times. always gets stuck on google logo (waited over 15 minutes).
before that i had some kali version on it, but out of the blue it stopped working and wouldn't boot anymore, that's where i deciced to try lineage. i dont want kali on it anymore as it was sluggish to start with.
so I thought I'll just put original rom on it and was looking for original 2012 rom download, but it seems like it comes in pieces like system.img boot.img ..etc and I don't want to overwrite my bootloader or lock the device again or cause other issues. I just want a working rom that can be sideloaded.
can someone please point out which rom is actually working with nexus 7 2012 and can be flashed using sideload or twrp loader.
I already have everything working, such as twrp, fastboot ..etc. I can easily sideload any working zip or img, but I simply can't find a working one.
I find only dead links on this forum and elsewhere, such as this one "xxxxxx" which is suppose to be for some nightly version. and some dead gapps links that point to dead domains or link just doesn't even exist.
please dont start suggesting to buy new tablet. i'm poor and i have no money and i only need this tablet to use with my smart plugs and camera. i'm not going to buy new tablet just for that. i just want to keep it on charger 24/7 so i can monitor my plugs and camera. that's all.
but for that i need working android rom and google play store so i can download and update apps.
I don't have any backups nor important data on it, however i want to keep it unlocked and keep the twrp.
any help would be appreciated. thanks.
Mod Edit: Link removed
so your question is about gapps?
aIecxs said:
so your question is about gapps?
Click to expand...
Click to collapse
uhh, no..
I quote:
mordaxify said:
can someone please point out which rom is actually working with nexus 7 2012 and can be flashed using sideload or twrp loader.
Click to expand...
Click to collapse
lineage 14.1 itself worked fine, or not?
aIecxs said:
lineage 14.1 itself worked fine, or not?
Click to expand...
Click to collapse
it was bit sluggish and got stuck couple times during boot, but it worked.
I think better question to ask is: does any of the ROMs comes with gapps?
It was like 5-6 years ago so i don't remember much, but i installed some version of kali on it and it had everything included (play store and other stuff). however as i mentioned before, for some reason it got really, really sluggish and at some point it just stopped booting completely.
so your question is about gapps. ROMs always should provided without google apps for licence violation.
use older installer. check recovery.log