I'm wondering about the CM7.2.0 nightly KANG builds, unlike some of the prebuilt versions of CM7 for this device, do these builds have access to setting up google accounts?
I had tried a build before, but could not use the market because I did not have an account set up, yet under the settings menu, there was no way to set up a google account.
The build(s) I am referring to are found here.
Thanks,
FlyingIsFun1217
did you install gapps
You need to install GAPPS.
The link it right underneath the latest build.
You flash GAPPS after you flash CM7.
That brings up another strange problem I've never had before (that I've only see occur when I had flashed a previous version of this rom).
When I boot into recovery (at least in the previous build posted) and attempted to install the .zip like any other one I would, it would not be listed. CWM Recovery acted like it was not there at all, it completely ignored it. Is this something anyone else has dealt with?
Thanks again
FlyingIsFun1217
--EDIT--
And just so we're on the same page, that was after an initial download, and a re-download of the GAPPS file, so it wasn't a corrupt download (unless the file indeed was corrupt and hosted as such).
Alright, to adress the semi-old message, I did flash the newer version of the ROM, and it seemed to work, must have had a bad flash before.
Anyway, new problem that I'm not going to bother dealing with (I've already gone to the ZEUS ROM), is that every version of CM I try for the Infuse, seems to go to a crawl with web browsing. And yes, I've tried the APN fix. I think it's something to do with whatever version of a wifi driver the phone uses on CM.
FlyingIsFun1217
Since I can not post here:
[rom] Unofficial CyanogenMod 10 for many AllWinner A10 tablets
because no matter I'm in IT over 15 years I have no 10 posts here, which is quite uncool from XDA, I have to ask here:
I have an Elf, started to hack from with the latest factory firmware (updated with LiveSuit).
Then I decided to have Christian Troy's JellyBean.
I had trouble to get ClockWorkMod running, for example Novotools_v1.0.apk said not enough Internal storage. Finally I managed with
Terminal Emulator_1.0.41.apk and a10_recovery.zip 3 files with these two commands:
su install-recovery.sh
su reboot-recovery.sh
After rebooting to CWM I made a full wipe, than installed these in order:
cm10_a10_20120913.zip
gapps-jb-20120726-signed.zip
elf_compatibility_1.2.0.zip
After rebooting I see the animated CyanogenMod 10 logo, than I should choose language onscreen.
Though hardware keys work (power, volume), touch screen is not responding!
Actuall I dropped it as well after the last reboot, so now I'm not sure if this touch problem is related to CM10 or the drop.
Do you have any ideas what to do?
Flash back to stock to verify if your touchscreen is working. If yes, make sure you don't need to flash a different kernel for your device.
Also, try flashing like you did before, but without gapps. Possibly, your /system partition gets full, so the elf_compatibility thing fails.
-- Sent from my TouchPad using Communities
post-mortem said:
Flash back to stock to verify if your touchscreen is working. If yes, make sure you don't need to flash a different kernel for your device.
Also, try flashing like you did before, but without gapps. Possibly, your /system partition gets full, so the elf_compatibility thing fails.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
I am in the no touch screen boat too. I'm running an elf, but thought I'd try the aurora compatibility files too. Unfortunately, no dice. Flashing back to 4.0.4 stock firmware brings the touchscreen back. More installs of the cm10 for a10 don't help...
Anyone that successfully flashed Christian troy's cm10 build into Ainol Elf 1 care to say which rom they upgraded from? That would be awesome...
Same problem here with Aurora 1 with nightly CM10: no touch
Success!
jan99 said:
Same problem here with Aurora 1 with nightly CM10: no touch
Click to expand...
Click to collapse
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
post-mortem said:
Flash back to stock to verify if your touchscreen is working. If yes, make sure you don't need to flash a different kernel for your device.
Also, try flashing like you did before, but without gapps. Possibly, your /system partition gets full, so the elf_compatibility thing fails.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
Seems like HW problem, went back to Elvish 0.4, still no touchscreen...
DoubleDroz said:
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
Click to expand...
Click to collapse
I am facing same problem with Elf1, touch not working after installing CM10. Mouse works just fine. ^^Was this on ELF1 or Aurora?
DoubleDroz said:
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
Click to expand...
Click to collapse
Would appreciate if you could share those image files that you used...
nevermind
vipulpradhan said:
I am facing same problem with Elf1, touch not working after installing CM10. Mouse works just fine. ^^Was this on ELF1 or Aurora?
Click to expand...
Click to collapse
It was the Elf 1
---------- Post added at 02:47 AM ---------- Previous post was at 02:08 AM ----------
vipulpradhan said:
Would appreciate if you could share those image files that you used...
Click to expand...
Click to collapse
The files can be found at *double u, double u, double u dot* ainol-forum.de *slash* ainol-novo-7-aurora-1-i-2-ii *slash* roms-novo-7-aurora-1-i *slash* 302-rom-aurora-v1-feiyu-mod-0429 *slash*
Don't download from the 115 links - they're all locked up. The mirrors work, however.
If you have an Elf, get the Aurora v1 rom. Get the Livesuit Version, and install using... Livesuit.
If you have an Elf, you must also download the Elf Patch, which you install using CWM once you've installed 0429 through LiveSuit.
Give it a shot.
Sorry for the delay - been doing other things!
PS I can't directly put in a link because XDA won't let me - I don't have enough posts - but I've changed it so you can pretty obviously work out the url. Okie dokes?
Same problem? anyone found solution
hi,
i am also lost touch screen.
Has anyone found solution??
DoubleDroz said:
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
Click to expand...
Click to collapse
Please can you explain how you managed to boot it recovery? i am not able to reboot in recovery. it starts the new rom & stuck as no touch screen.
Hi there, wondering if anyone can help me with this. I bit the bullet and ran the Bigpart process so I could try OmniROM, but on first boot I keep getting "Unfortunately the process com.android.phone has stopped".
I've scoured the OmniROM Xoom thread in the Dev section, but can't seem to find any mention of this (I also can't post in there yet).
I thought that maybe the Bigpart process didn't work correctly, but after doing some research, it sounds like it wouldn't boot at all if that was the case. The Xoom is a UK (I don't think that matters) Wingray, and I'm flashing omni-4.4.2-20131227-wingray-HOMEMADE_2122.zip with pa_gapps-modular-mini-4.4.2-20131215-signed.zip straight afterwards using Bigpart TWRP. I've tried flashing with no Gapps and Banks' Core Gapps too, just in case that had anything to do with it, but the same issue exists. The error just keeps popping up and I can't get any further into the ROM.
As a further test, I flashed CM 10.1 with the Bigpart CM Kernel and it worked perfectly, so I'm pretty sure my Bigpart is fine. Does anybody have any idea's or suggestions for what else I could try ?
Schoolboy Error
Scratch that, I made a rookie mistake. Just md5summed the zip I was flashing and it was bad. Re-downloaded, verified the MD5 hash, flashed again and it's working much better now. Apologies, feel free to beat me around the head with your Xoom's
Hi, I have a big issue installing all but one build of the PAC-Man ROM not installing on my Droid Razr Maxx HD. I've tried installing multiple nightly & Dev builds of them ROM but they all boot loop at the Motorola logo. No one seems to care about this issue either. I've posted on almost all social media the Pac-Man ROM community has bit it seems to not be getting any attention. (Excuse me for getting a little off track) I always do a factory reset with twrp twice before attempting to install this ROM, I've also tried repairing the data partition (which is this fix found on Droidrzr forum) I've tried flashing back to stock KitKat, I would try side loading a build but twrp's side load feature doesn't work. Could some one guide me to sending a Dev a boot log so whatever bug is causing this is squashed? I really want to run this ROM. Or, could someone who has had this ROM installed guide on getting it up and running?
http://www.droidrzr.com/index.php/t...8960unofficialodex444baked-08-01-14/?p=451296 is the fix I tried
These are all the builds I've tried installing, only 1 worked.
https://www.dropbox.com/s/0nsoyd5zh8yb3ww/screenshot.jpg
Playb3yond said:
Hi, I have a big issue installing all but one build of the PAC-Man ROM not installing on my Droid Razr Maxx HD. I've tried installing multiple nightly & Dev builds of them ROM but they all boot loop at the Motorola logo. No one seems to care about this issue either. I've posted on almost all social media the Pac-Man ROM community has bit it seems to not be getting any attention. (Excuse me for getting a little off track) I always do a factory reset with twrp twice before attempting to install this ROM, I've also tried repairing the data partition (which is this fix found on Droidrzr forum) I've tried flashing back to stock KitKat, I would try side loading a build but twrp's side load feature doesn't work. Could some one guide me to sending a Dev a boot log so whatever bug is causing this is squashed? I really want to run this ROM. Or, could someone who has had this ROM installed guide on getting it up and running?
http://www.droidrzr.com/index.php/t...8960unofficialodex444baked-08-01-14/?p=451296 is the fix I tried
These are all the builds I've tried installing, only 1 worked.
https://www.dropbox.com/s/0nsoyd5zh8yb3ww/screenshot.jpg
Click to expand...
Click to collapse
i dont know the answer, so ill just throw out a question.
do you know that the pac rom has been updated to kk source?
bweN diorD said:
i dont know the answer, so ill just throw out a question.
do you know that the pac rom has been updated to kk source?
Click to expand...
Click to collapse
I've known, I've tried the updater to kitkat as well, still no luck
Playb3yond said:
I've known, I've tried the updater to kitkat as well, still no luck
Click to expand...
Click to collapse
i only asked because i didnt know.
so i just went and read this entire post (is this the one we are talking about?), and it has not been updated to kk base yet as far as i can see.
if you bootloop at the boot animation then its most likely because your data partition isnt formatted to ext4
I tried that as well, still no luck
Sent from my DROID RAZR HD using Tapatalk
OK,
I have posted this within another thread but have decided to start anew as other threads seem to be resolved after Rom has flashed because of changes made in the update script dealing with bootloader version. My issue is after the Rom has flashed and apologize if I missed it but have not at least seen another thread with the same issue or complaint so will once again apologize if I am not correct but my issue is or do not beleive is related to the update.
e script bootloader insertion.
Also a bit lazy in that although I will do research have come to trust advice from xda members who may reply so all and all like knowing that whatever I may find may be backed up here as opposed to spending and wasting limited time searching down the wrong rabbit hole looking for resolutions so with that said below is what I wrote on another thread whose creators issue seemed resolved after moving past the errors received in the process of flashing.
I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0 "LMY47I" for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
One last tidbit is I have tried booting into cm after flashing both with gapps and without in the case maybe something in the gapps packages I have is screwing with things preventing from booting past the "Google" Logo