Database Develop

[Q] I9000 no longer auto rotates with unofficial BG 2.3.3

I've booted and rebooted. I've had the battery out. I've checked and unchecked the auto rotation button but,no autorotation happens. Th
anks so much, Giles.

Have you flashed another kernel for root? Mine works flawlessly

I was using Darky's Rom. Flashed from that

Do you think a different kernel might help? I've been thinking about flashing a different kernel to get voodoo control app working.

doonit said:
I've booted and rebooted. I've had the battery out. I've checked and unchecked the auto rotation button but,no autorotation happens. Th
anks so much, Giles.
Click to expand...
Click to collapse
Have you tried deleting /data/system/ms3c_yamaha.cfg
This is the config file for the accelerometer, you will need root to delete it.
I have this issue on my froyo rom quite regularly (couple of times a month)
Let me know if it works?

Or you could try simply re-calibrating in settings as I mentioned to another post on this earlier.

Tehpriest said:
Or you could try simply re-calibrating in settings as I mentioned to another post on this earlier.
Click to expand...
Click to collapse
To be honest I would have assumed that was the first thing to try before posting here?
What happens on mine is that it gets locked and you get a 0byte config file no amount of calibrating / rebooting / using the engineer test menus will fix it but deleting said config file does.

curioct said:
To be honest I would have assumed that was the first thing to try before posting here?
What happens on mine is that it gets locked and you get a 0byte config file no amount of calibrating / rebooting / using the engineer test menus will fix it but deleting said config file does.
Click to expand...
Click to collapse
The same happen to my device awhile ago,tried all the recomendations but no dice.
only a hard-reset fixed it.

curioct said:
Have you tried deleting /data/system/ms3c_yamaha.cfg
This is the config file for the accelerometer, you will need root to delete it.
I have this issue on my froyo rom quite regularly (couple of times a month)
Let me know if it works?
Click to expand...
Click to collapse
I would try deleting it, except that it's not there! Can't find it anywhere.

faria said:
The same happen to my device awhile ago,tried all the recomendations but no dice.
only a hard-reset fixed it.
Click to expand...
Click to collapse
I kind of gathered that I might need to hard reset, but I'd like to avoid that if I can. I've searched through my phone though. Can't find the .cfg file mentioned above. It's not in /data/system.

Ok. So by now I've pretty mich done everything. Even after a hard reset my phone will not aouto rotate and I'm becoming a little irritated by this whole thing.
Under /data/system THERE IS NO FILE CALLED ms3c_yamaha.cfg, so what's next? Go back to Darky's rom?
Can anyone help me here, please? My fingers are too big for typing with the portrait keyboard, besides the many other good reasons for being able to go into landscape mode
Sent from my GT-I9000 using XDA App

Recalibrate screen at settings> display place your phone at a desk and tap the option that should fix it! Good luck!
Sent from my GT-I9000 using XDA App

jpsalas said:
Recalibrate screen at settings> display place your phone at a desk and tap the option that should fix it! Good luck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No, I've tried that too. Nothing!!

its the problem with the kernel

kanasai87 said:
its the problem with the kernel
Click to expand...
Click to collapse
Ok. I'll go for that. Can anyone suggets a kernel to try?

im not sure bout kernel for 2.3.3 bcause im using miui rom
Sent from my GT-I9000 using XDA Premium App

Bionic 5.5.1_84_DBN-55 Auto_DeOdexer

For those of you that do not want to DeOdex their phone manually, here's a script I created to do it for you. I've created this same script before for the Droid X, and it's quite simple. Here's what you need.
1) Your phone must be Rooted.
2) You must install Bionic_Bootstrapper.
Below you can find these items.
COMPLETE GUIDE TO ROOT AND BOOTSTRAP
Once you have that.... download my DeOdexer and put it on your sdcard.
Bionic_AutoDeOdexer
MIRROR
Reboot into recovery. BACKUP YOUR PHONE!!!!
Once that completes, then go to install from zip. Choose file from zip... find the Bionic_DeOdexer zip file... and run it.
There is a script at the beginning that checks the build.prop file and makes sure you have the correct build. You must have 5.5.1_84_DBN-55. If you do not, I hope it fails.
Reboot.... and all should be good. Now that you are DeOdexed.... have fun theming!
As you should know, do this at your own risk. Yes, I've tested this on my phone and had no issue. This doesn't mean you won't experience a problem. I'm not responsible for what happens to your phone.
ENJOY!!!

Worked great. Saved me a lot of time from manually deodexing.
Sent from my DROID BIONIC using xda premium

Thanks for this...

TauntingBull said:
Thanks for this...
Click to expand...
Click to collapse
You're welcome!

Fantastic nitro.thank you so much.it was quick, clean and simple. System/app/ shows no sign of .Odex's after installing zip. Flawless victory.
Sent from my DROID BIONIC using Tapatalk

AJMetal87 said:
Fantastic nitro.thank you so much.it was quick, clean and simple. System/app/ shows no sign of .Odex's after installing zip. Flawless victory.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Not a problem. Have fun Theming!

I think this should be stickied.... lots of requests for this!

For some reason when I try to run this it says that it failed. I have downloaded a few times and tried. I'm on the same build and completely stock rooted.. weird. Any ideas?

willbur73 said:
For some reason when I try to run this it says that it failed. I have downloaded a few times and tried. I'm on the same build and completely stock rooted.. weird. Any ideas?
Click to expand...
Click to collapse
Have you removed or touched any of the system/app/ 's ?

I'm running the rooted stock rom. I haven't removed any programs or modified/renamed anything in /system/apps, however, I did freeze some of the bloat using TB. Do I need to defrost the apps first before running this script, or does it matter?

PillClinton said:
I'm running the rooted stock rom. I haven't removed any programs or modified/renamed anything in /system/apps, however, I did freeze some of the bloat using TB. Do I need to defrost the apps first before running this script, or does it matter?
Click to expand...
Click to collapse
If you modified any of the APKs, to include freezing them, I cannot guarantee it will work. Best thing is to be completely stock and rooted. At least that's the way I did this script.

Thanks for the answer! TB has a batch defrost, so if I decide to go ahead & run this script, I'll defrost everything first.

I did mine with frozen apps and it seems to be working well. Was able to install the 1% mod and use a custom battery icon too.

slvrdrgn123 said:
I did mine with frozen apps and it seems to be working well. Was able to install the 1% mod and use a custom battery icon too.
Click to expand...
Click to collapse
Good to know. I do know that depending on how the person downloads some packages, they may get corrupted during download. If it fails one time... try again. If it continues to fail, re-download and try again.

So the file isn't available any more?
Sent from my DROID BIONIC using xda premium

I just checked both file locations and they are still there. What are you referring too.
Sent from my DROID BIONIC using XDA App

Worked great here, didn't unfreeze anything before running it and no problems to report.

Kind of a goofy question, but is there any reason that deodexing the stock (rooted) rom would worsen data loss issues?
The reason I ask is that I reverted to stock yesterday after experiencing substantial data problems with UNLEASH3D 1.5. Ran well for the entire day and this morning. Then, a couple hours ago, I ran this script and have had nothing but issues since, with both WiFi and cellular data dying, and not coming back without a reboot. Reverted to stock again, and all is normal.
Any ideas?
Sent from my DROID BIONIC using Tapatalk

Underwater Mike said:
Kind of a goofy question, but is there any reason that deodexing the stock (rooted) rom would worsen data loss issues?
The reason I ask is that I reverted to stock yesterday after experiencing substantial data problems with UNLEASH3D 1.5. Ran well for the entire day and this morning. Then, a couple hours ago, I ran this script and have had nothing but issues since, with both WiFi and cellular data dying, and not coming back without a reboot. Reverted to stock again, and all is normal.
Any ideas?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I have these same issues on stock, on .892 and on any roms - I really think it is just the phone :/ - there is a known bug on the bug list about data connectivity issues.
Btw the .892 radio is complete crap.... at least on my phone it is...

Market Apps
After running this script, I noted that my normal list of around 60 or so market apps is now showing only around 13 apps. Also, the market app asked me for authorization when I started it up. So, I don't know if this script, or maybe an automatic update to the market app has caused my missing downloaded apps.
They are still on the phone, and still backed up with TB, but they are not shown in the market My Apps page.
Any thoughts or solutions?
Corey
...Argh, never mind, this phone seems to have a mind of its own. The account chosen for My apps was not my main google account but another one. Not sure how this happens, but I find little things like this all the time with Android. My favorite is that my email delivery settings (push vs. manual vs. schedule) seem to change on their own!

[Q] Help with gingervolt 2.0

Hello, I dont know where the help forums are for the lg revolution and it wont let me post for some odd reason so hopefully here, i can ask for help, and not get banned x3.
So im tring to flash gingervolt 2.0 and well, it's not working. Ive tried updating from gingervolt 1.3, adding the 2.1 version of blitzkrieg and a theme. But the problem here is. It just goes to the LG screen then turns off and vibrates again going to the same screen. When i get very lucky it boots into the boot animation and into the device. But some parts freeze if i try to do something and sometimes the boot animation freezes. If anyone knows about this problem or think they can help. Any help would be appreciated. Thanks.
Also i don't want to use stock or gingervolt 1.3, i think 2.09 is so much faster so i'm not wanting to be recommended on another version or another Rom. Thanks.

Restore your back up and try re downloading and trying again
Sent from my VS910 4G using xda premium

Ive already tried that. D:
Sent from my VS910 4G using XDA App

Did you wipe data before flashing 2.0? Just trying to cover the bases
Sent from my VS910 4G using Tapatalk

swiftriolu said:
Hello, I dont know where the help forums are for the lg revolution and it wont let me post for some odd reason so hopefully here, i can ask for help, and not get banned x3.
So im tring to flash gingervolt 2.0 and well, it's not working. Ive tried updating from gingervolt 1.3, adding the 2.1 version of blitzkrieg and a theme. But the problem here is. It just goes to the LG screen then turns off and vibrates again going to the same screen. When i get very lucky it boots into the boot animation and into the device. But some parts freeze if i try to do something and sometimes the boot animation freezes. If anyone knows about this problem or think they can help. Any help would be appreciated. Thanks.
Also i don't want to use stock or gingervolt 1.3, i think 2.09 is so much faster so i'm not wanting to be recommended on another version or another Rom. Thanks.
Click to expand...
Click to collapse
Start over from stock GB would be your best bet.
Sent from my VS910 4G using XDA App

Yes i wiped data. I followed all of the directions. Also i dont like stock at all, are you saying i should try from that. I did that to.

I agree that going back to stock GB would probably be the best solution. Then just start over from scratch
i'm running gingervolt 1.3 and didnt even realize the was a 2.0 for it....lol....
could someone post a link? or point me in the right direction?
Much Appreciated

thephelans5 said:
I agree that going back to stock GB would probably be the best solution. Then just start over from scratch
i'm running gingervolt 1.3 and didnt even realize the was a 2.0 for it....lol....
could someone post a link? or point me in the right direction?
Much Appreciated
Click to expand...
Click to collapse
Here ya go!
http://forum.xda-developers.com/showthread.php?t=1326542

KaneOfMars said:
Did you wipe data before flashing 2.0? Just trying to cover the bases
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
I didn't wipe data before flashing. But it's most likely better off to do it like Kane said and also starting from a Stock GB then flashing GV 2.0

Hi all,
I'm new here, and couldn't find any references to this specific problem, but this thread appears to be vaguely related. I'm GV 1.3 and just tired to update to 2.0. CWM makes it appear as though the update worked, but when I restart the phone, Settings --> About Phone still shows it's on GV 1.3. I tried the update twice; the first time, I chose "Reboot phone" from the CWM menu after installation, and the second time, I powered down. Same result both time.
Per the instructions, I did NOT wipe data, since I was already on GV 1.3.
Any ideas/suggestions?
Thanks!
-- Bryce

bnewall1 said:
Hi all,
I'm new here, and couldn't find any references to this specific problem, but this thread appears to be vaguely related. I'm GV 1.3 and just tired to update to 2.0. CWM makes it appear as though the update worked, but when I restart the phone, Settings --> About Phone still shows it's on GV 1.3. I tried the update twice; the first time, I chose "Reboot phone" from the CWM menu after installation, and the second time, I powered down. Same result both time.
Per the instructions, I did NOT wipe data, since I was already on GV 1.3.
Any ideas/suggestions?
Thanks!
-- Bryce
Click to expand...
Click to collapse
Mtmichaelson forgot to change the build number I believe. You should be good.
Sent from my AXI0M ICS RAZR using tapatalk.

Thanks
spc_hicks09 said:
Mtmichaelson forgot to change the build number I believe. You should be good.
Sent from my AXI0M ICS RAZR using tapatalk.
Click to expand...
Click to collapse
Thanks spc hicks09
after reading previous posts I was suddenly curious why my revo said 1.3 when it should have said 2.0

bnewall1 said:
Hi all,
I'm new here, and couldn't find any references to this specific problem, but this thread appears to be vaguely related. I'm GV 1.3 and just tired to update to 2.0. CWM makes it appear as though the update worked, but when I restart the phone, Settings --> About Phone still shows it's on GV 1.3. I tried the update twice; the first time, I chose "Reboot phone" from the CWM menu after installation, and the second time, I powered down. Same result both time.
Per the instructions, I did NOT wipe data, since I was already on GV 1.3.
Any ideas/suggestions?
Thanks!
-- Bryce
Click to expand...
Click to collapse
You should be fine. The name was not changed in the file. There are many posts about in the gv 2.0 thread.
Sent from my VS910 4G using xda premium

spc_hicks09 said:
Mtmichaelson forgot to change the build number I believe. You should be good.
Click to expand...
Click to collapse
Oh, that might explain a lot then. Other than the build number, is there any indication that I'm on 2.0 now? The animated startup graphic is the same as it was before.

bnewall1 said:
Oh, that might explain a lot then. Other than the build number, is there any indication that I'm on 2.0 now? The animated startup graphic is the same as it was before.
Click to expand...
Click to collapse
If you can overclock without flashing the kernel then you're good. 1.3 didn't have the kernel implemented.
Sent from my AXI0M ICS RAZR using tapatalk.

spc_hicks09 said:
If you can overclock without flashing the kernel then you're good. 1.3 didn't have the kernel implemented.
Click to expand...
Click to collapse
I wouldn't know how to overclock my phone if it smacked me in the face...
I was having some trouble with Bluetooth, so I went back to GV 1.3 and checked the build number. When that didn't help and I ended up having to factory reset my phone to get BT working again, I went back to GV 2.0 again, and noticed a different kernel build number. I guess that's one way to tell that I'm on 2.0. I can't tell any difference in how it works otherwise, though.
-- Bryce

Battery problems
Has anyone else had any problems with the battery dying fast after switching to gingervolt 2.0? Since updating from gingervolt 1.3 to 2.0 my battery has been dying significantly faster (from 100% at 7:30am to 20% at 9:30pm with hardly any use and yes I have the extended battery). I am using rom toolbox and have the cpu set to Max: 1305Mhz and Min: 576Mhz with the governor set on smoothass (this was also set on 1.3 with no issues). My phone also will occasionally freeze and reboot at random times. I also noticed that it seems to lag when opening certain apps. Verizon tried to push an update to my phone which thankfully did not go through but i was able to go into the system files and change the system/lib/libme_main.so and change it to system/lib/libme_main.so.bak. That seemed to stop the update from trying to install. I also went to etc/security/otacerts.zip and added .bak to the end. Doing this accomplished nothing and now it wont allow me to remove the .bak from the end of the file. I love gingervolt 2.0 when it is working properly and hope I can get it to run smoothly. If anyone has any suggestions please share.

[Q] My X8 got laggy after failed overclock

WARNING: I'm pretty much a noob at this stuff, so please bear with me.
Okay, first of all, and I'm not sure if this is relevant, a few days ago I hard-bricked my phone trying to unlock the bootloader. I got it repaired (I think they changed the motherboard or something) and after that I installed GingerDX (for stock kernel) and everything was working fine and smooth. Then, I tried to overclock it with a module for overclocking (not sure what it was called) and SetCPU.
When I inserted the module, everything was working fine. But then I installed SetCPU and tried something with it. I think I tried setting it to a higher frequency, but not much. And after that, it rebooted itself. And it kept rebooting all the time. It would turn on for less than a minute and then it would reboot.
I wasn't exactly sure what to do, and since I didn't have much time and I needed my phone, I just went into CWM, made a full wipe and just installed GingerDX again. But when I turned it on, it was lagging quite a lot. Not THAT much, but it was quite visible and irritating.
I tried to change the governor from ONDEMAND to PERFORMANCE, and it showed that the CPU frequency had changed from 600MHz to about 700MHz I think, but it still felt the same. Then I switched it back to ONDEMAND, and it's still the same.
Does anyone have any idea on how to fix this? Any help is greatly appreciated.

Did you full wipe system before installing
Sent from my LG GT540 Swift using Tapatalk

edinchez said:
WARNING: I'm pretty much a noob at this stuff, so please bear with me.
Okay, first of all, and I'm not sure if this is relevant, a few days ago I hard-bricked my phone trying to unlock the bootloader. I got it repaired (I think they changed the motherboard or something) and after that I installed GingerDX (for stock kernel) and everything was working fine and smooth. Then, I tried to overclock it with a module for overclocking (not sure what it was called) and SetCPU.
When I inserted the module, everything was working fine. But then I installed SetCPU and tried something with it. I think I tried setting it to a higher frequency, but not much. And after that, it rebooted itself. And it kept rebooting all the time. It would turn on for less than a minute and then it would reboot.
I wasn't exactly sure what to do, and since I didn't have much time and I needed my phone, I just went into CWM, made a full wipe and just installed GingerDX again. But when I turned it on, it was lagging quite a lot. Not THAT much, but it was quite visible and irritating.
I tried to change the governor from ONDEMAND to PERFORMANCE, and it showed that the CPU frequency had changed from 600MHz to about 700MHz I think, but it still felt the same. Then I switched it back to ONDEMAND, and it's still the same.
Does anyone have any idea on how to fix this? Any help is greatly appreciated.
Click to expand...
Click to collapse
Redownload rom , full wipe twice , wipe battery stats , system and flash rom.
Or try another rom for stock
Sent from my HTC Desire using xda app-developers app

SmashDrill said:
Did you full wipe system before installing
Sent from my LG GT540 Swift using Tapatalk
Click to expand...
Click to collapse
Yeah, I did. I mentioned it in the first post as well.
vanillaLVL said:
Redownload rom , full wipe twice , wipe battery stats , system and flash rom.
Or try another rom for stock
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Are you sure this will fix it? Because I don't want to lose all my installed apps just for trying something out. It takes a lot of time to re-install all of them.

edinchez said:
Yeah, I did. I mentioned it in the first post as well.
Are you sure this will fix it? Because I don't want to lose all my installed apps just for trying something out. It takes a lot of time to re-install all of them.
Click to expand...
Click to collapse
Use Titanium backup to backup , and then restore

On stock kernel , the more the frequence the laggier the device will become.
Sent from my E15i using xda app-developers app

Just did a double full wipe and flashed the ROM again and it's fixed now. Thanks a lot for your help guys!

For me, the overclock never work on froyobread and gingerdx on stock kernel. When I install the module, the phone just stay unstable, and without a overclock (at 600 mhz with module installed), the performance is sh!t. So, if u need overclock, install a rom with include the module, like cm7 v7 (i dont know). The best is unclock bootloader, but i dont do this.

jucazastrow said:
For me, the overclock never work on froyobread and gingerdx on stock kernel. When I install the module, the phone just stay unstable, and without a overclock (at 600 mhz with module installed), the performance is sh!t. So, if u need overclock, install a rom with include the module, like cm7 v7 (i dont know). The best is unclock bootloader, but i dont do this.
Click to expand...
Click to collapse
install app for overclocking then...many available.

I dont need overclock and I test many apps for these, but just test in froyobread and gingerdx. The overclock works for me on cm7 v6, but again, I dont need this. Its just a sugestion.
sorry for my bad english

[Q] Do I have an un-android-able Touchpad?

Hello All,
I'm not that new to the XDA scene as I've been rooting for a couple of years now (HTC Aria, HTC One XL), however I am completely stumped as to why my HP Touchpad keeps randomly rebooting while in android. Here's the TL;DR
1. Installed moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly using ACMEInstaller2.
2. Everything installed fine, except device randomly reboots within 5 min of starting up, sometimes immediately (before I can even unlock the display), sometimes even while loading the cyanogenmod splash screen.
3. I have read everything on the XDA's about this problem and scoured Google for hours to no avail. Tried clearing cache, Dalvik cache, then fix permissions. Still randomly reboots. Tried turning off beats audio in webOS. Still randomly reboots. Used ACMEUninstaller, erased webOS completely, re-rooted using ACMEInstaller3, moboot 0.3.5, CWM 1012, and CM9 20121212 Nightly. Still Randomly Reboots.
I am at the end of my ropes here, about to give up and just accept that my device is not compatible with android, even though countless others are running android with little problem. I'm just not understanding what I am doing wrong, if anything. Any comments / advice would be very much appreciated.
Peace and Love

That's odd. Maybe try a different ROM?

bananagranola said:
That's odd. Maybe try a different ROM?
Click to expand...
Click to collapse
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.

leetpcguy said:
I've tried CM7 Alpha 3.5, CM9 Nightlys, and CM9 Fat and Creamy by SGA. CM7 was the most stable, but still I had many FC's and random reboots, though not as many as CM9.
Click to expand...
Click to collapse
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.

bananagranola said:
I would try wiping cache and dalvik-cache. Aside from that, I'm out of ideas.
Click to expand...
Click to collapse
Just tried that and it rebooted before I could even navigate to No-Frills CPU Control :/ I appreciate the input though.
It seems that once it boots, if i don't touch anything, it will not reboot while at the lock screen. I've had it charging for the past 4 hours or so while booted in CM9 and haven't ventured past the lock screen and it hasn't rebooted yet.

When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium

rrrrrrredbelly said:
When you unlock it, see if you can find out what the min cpu speed. If it's @ 192, try 384 or even 432 and see if that makes a difference
Sent from my ThunderBolt using xda premium
Click to expand...
Click to collapse
I have tried both of those as well as setting both the min and max frequency to 1.2 GHz. It still reboots; seems to be independent of CPU clock speed.
I've also tried disabling all haptic feedback as well as turning the sound all the way down and turning off the keypress sounds. Still reboots.

i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.

Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.

It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.

slicetwo said:
i had the same issue. i used acmeuninstaller and removed android completely. downloaded the latest CM9 nightly and CWM and such. used acmeinstaller to install CWM, then I installed CM9 and gapps manually via CWM. check out jscullins latest CWM build. it may help.
Click to expand...
Click to collapse
The only thing I did different than what you suggested here is let the ACMEInstaller3 install CM9 for me. I have not tried jscullins build of CWM though, I will give that a shot and also try installing the ROM manually after ACME has installed CWM.
jsgraphicart said:
Are you using the right Gapps zip? If you flash CM9 and are using Jelly Bean Gapps, it may have problems trying to run the Google setup at start since its meant for Jelly Bean. Just a thought.
Click to expand...
Click to collapse
I'm 99% sure I was using the right apps, and usually I can make it through the setup portion of the initial boot without a restart. Doesn't last too much longer than that though...
dmarchant said:
It may be a block of bad Nand memory. Similar problems have been seen / noted in some of the other tablet forums (I hang out a lot in the Advent Vega forum) and this is not totally unknown, although not that common. It may just be an area that hasn't been used or is avoided by Webos, but comes into play with Android and the extra partitions.
Only suggestion from me would be to try AcmeInstaller3 if you haven't already as that sets different partitions to AcmeInstaller2 to allow for the space needed for CM10, but will work fine with CM9.
Click to expand...
Click to collapse
I've used ACMEInstaller3 the last two times I reverted everything to stock, erased and reset webOS, and started over. Still had the same problems as when I used ACMEInstaller2.

youre doing something wrong,, probly something simple..
have you looked @ youtube?
roland has some good vids.
so does reverendkjr