Database Users

CM9 and V3 Bootloader, won't wake up

I have CM9 with the V3 bootloader and I'm loving it!
I have one issue and I was wondering if anyone else has come across this. When I lock the screen (tap the power button) then come back to it 5 minutes later I have to do a hard reset. It's like it's going to sleep and not coming back on. This isn't a CM9 issue I don't think because the official dump I flashed originally to get on ICS and the V3 bootloader had the same issue. Is it the bootloader? Is there a firmware update I missed by not using the official GEN1 update? Any help is appreciated.
EDIT: I used the Acer_AV041_A500_1.033.00_PA_CUS1 update.zip to get onto ICS and it worked beautifully except for this issue. Should I reflash with one of the other ICS leaks for the GEN1?

Search for sod (sleep of death) and you will get a zillion hits...

naviathan said:
I have CM9 with the V3 bootloader and I'm loving it!
I have one issue and I was wondering if anyone else has come across this. When I lock the screen (tap the power button) then come back to it 5 minutes later I have to do a hard reset. It's like it's going to sleep and not coming back on. This isn't a CM9 issue I don't think because the official dump I flashed originally to get on ICS and the V3 bootloader had the same issue. Is it the bootloader? Is there a firmware update I missed by not using the official GEN1 update? Any help is appreciated.
EDIT: I used the Acer_AV041_A500_1.033.00_PA_CUS1 update.zip to get onto ICS and it worked beautifully except for this issue. Should I reflash with one of the other ICS leaks for the GEN1?
Click to expand...
Click to collapse
Flash the correct ICS kernel and not a modified kernel to run on HC bootloader.

civato said:
Flash the correct ICS kernel and not a modified kernel to run on HC bootloader.
Click to expand...
Click to collapse
CM9 isn't using the correct kernel? I thought they said they would no longer be providing a HC compatible kernel in their images.

Is updated bootloader needed

Hey guys what's up sorry I'm sure there are other threads about this but I haven't been able to find one to answer me directly....is the updated ics sandwich boot loader necessary I was able to flash flexreapers and lightspeed's ics custom rooms without it? So is it really needed does it make it faster update cmw or just allow recovery boot menu and dual boot I'm at a lost on weather its neccesary or not thanks once again

It will be soon, alot of the developers, including Civato, have said they are going to stop development for the HC bootloader. It does significantly improve performance and eliminates most of the glitches on ICS.

And it will make life easier in the future - upgrading the bootloader, etc. straight from CWM among others.

strongergravity said:
And it will make life easier in the future - upgrading the bootloader, etc. straight from CWM among others.
Click to expand...
Click to collapse
cruise350 said:
It will be soon, alot of the developers, including Civato, have said they are going to stop development for the HC bootloader. It does significantly improve performance and eliminates most of the glitches on ICS.
Click to expand...
Click to collapse
Alright sweet +thanks ;-) I'll update it later then

gears177 said:
Alright sweet +thanks ;-) I'll update it later then
Click to expand...
Click to collapse
Just stick with whatever custom recovery that is provided with the package you
use...not all features in all recoveries are yet supported.
some are meant only for certain BL's for instance HC3.2 and TWRP
from v4 BL on you are able to flash a zip thru recovery and more fastboot commands are available.
You need to read the change logs for each version as things are being added with each new release.
One thing i am certain of and that is if you are having ANY weird issues, sod, wifi OFF, nvflash issues then what seems to settle everything down is a rollback to HC - I think alot of us myself included, never flashed the right thing at the right time when first upgrading to ICS (and at some future point ending up with a "freakenstein" not one thing or the other and not working all that well either) when you start running a "compatible system" i.e kernel, bootloader, recovery, rom all working as they should, then things look and work a whole heccuvalot better!!!

I will not support HC bootloader for the Overclocking kernel for ICS.
To much problems. So expect no OC support for my rom if you stay on HC bootloader.

Unlocked Bootloader v8 / ICS - SoDs

I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?

droidroidz said:
I had zero issues with SoD running HC roms and HC bootloader. I have serious issues with ICS roms and the unlocked bootloaders. Here is what i have tried:
First tried v3 unlocked bootloader with Thors recovery and CM9 alpha rom. I had many issues with SoDs everytime the screen went off it seems like it SoD. That was the original issue. I recently just tried 3 different recoveries including twrp/ezterry/thors and used all 3 to do full wipes. I installed ezterrys ICS rom. I am getting less SoD..maybe 1 per day but they still persist. Does anyone have any ideas what im doing wrong? Am i the only one with these issues? Its not an app causing this either as I have run with both roms on the base w/o installing any apps and the SoD still persists. Anyone have any experience with this and can enlighten me?
Click to expand...
Click to collapse
Had sod on any rom (and stock) with changed bootloader (and other problems). Went back to ota stock without root. No problems

I have SoD since going from thors rom back to taboonay and then to V8 bootloader, still trying to solve the issue but no luck. I can't even connect to pc to root it again as I've lost that too

Any of you running a 501?
If so, it's an issue with the kernel.
MD

a500 here

Moscow Desire said:
Any of you running a 501?
If so, it's an issue with the kernel.
MD
Click to expand...
Click to collapse
Using A500
I see so many others with success which is why its killing me that this is not more common issue. There must be something we are doing slightly wrong or forgot to do causing this.

Ok, here is the real deal.
1. ICS Bootloader. Mandatory. Check it when you boot, it should say in the left corner.
2. Recovery version has no effect on SOD. However, you should have the correct one for ICS. Currently I use 1.7.3.
3. The kernel. Now, most of the ICS Roms in the forum for the 500 have a "tweaked kernel". These are the ones you want to use. MAKE SURE the rom you are using is for the patched ICS Bootloader. This includes EZTerry's and Civatos. You have to pay attention with Civ's as he may still have some designed for HC bootloader. YOU DO NOT WANT THESE. I believe Smaury's and Vache's are ok also, but check first.
4. This is probably where the problem is. Wipes and Formats. Sometimes, leftover code from a previous kernel or modules could still possibly be in the tab. This can cause strange issues.
Wipe
Data/factory reset
Cache
Dalvik Cache
(depending on recovery version)
Format System
Format Flexrom
Do this 2 or 3 times, then install the rom.
I use CWM 1.7.3 recovery (too lazy now to change but will in the future)
Also, if you have any doubt which bootloader you currently have, download AcerRecoveryInstaller and it should tell you. After OTA in the Dev forum will also tell you. You don't have to do anything with the app, just start it to get information.
This should get you going.
MD

I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?

riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011

riot1031 said:
I have two A500's, both with V8 bootloader and the latest flexreaper rom. One doesn't SOD, the other has constant SOD's. I'm beginning to think it's the hardware. Mine were purchased about 6 months apart, maybe different hardware revisions?
Click to expand...
Click to collapse
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD

Moscow Desire said:
You know, you just added some insight into a theory I've been tossing in my head. Although I thought this was only a51x and a70x based. I didn't know it might be effecting the 50x as well.
Let me run this at you. With the 51x and 70x, the bootloaders seem to be matched to the specific version of ICS installed from factory. (COMGen, version number, etc). We know this, as the bootloaders on several tabs have different naming conventions. It's why certain root methods will not work on some tabs. Currently we have 3 methods, but 1 requires CWM (and our current version will brick the tab if you use the restore option..../data is what bricks).
It's possible, that with ICS, certain kernels are required to function properly on the 500 also. We all know with ICS, the kernel communicated a lot with the bootloader. This "may" be associated with some obscure part of the hardware as well. This I don't know. But with the newer tabs, it definately seems to be hardware software related. Some Roms just WILL NOT run on some tabs.
Now for you guys, here is what I might try. Different kernels. Try running a stock kernel for that specific build number. Or if you haven't tried it yet, try running EZ_Terry's OC kernel built form source. See if you still get SOD.
Just something to try.
MD
Click to expand...
Click to collapse
This is an interesting theory and makes sense. In my case with CM9 and Ezterry's rom I have tried the stock kernel for each and ezterry's OC kernel on both...and still SoDs although ezterrys rom/kernel seems to be far less frequest SoDs. We don't have much options for kernels around here.

Progress?
Has anyone made any progress with figuring this out?
My tablet was running fine on a stock, rooted ICS. Then I installed custom recovery, different kernel, and bootloader when I tried JellyBean (ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]) from the Developers forum on here. I started getting SoDs and some of my games weren't running, so I went back to the ICS rom, but the SoDs are still happening. At that point, I was pretty sure it was related to the kernel or the bootloader.
On the "ROM | WIP | CM10 JellyBean 4.1.2 Unofficial for acer a500 [Build 3]" thread in the developers section they are questioning if the SoD is related to CyanogenMod (which I don't believe it is). I wanted to post there about what this thread is hypothesizing, but am unable to post to that thread (too new to XDA).

Update
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...

Waleslie said:
I went ahead and went back to full stock ICS (bootloader, kernel, etc). Then rooted it again.
The disappearing icon issues have gone away.
Now I'm not sure if I should just stick with it like that or venture out into Jelly Bean land again...
Click to expand...
Click to collapse
Venturing out to JB land is a choice.
Although CM does a pretty good job of doing things, I always have to remember, they lean toward mainstream devices.
We 50x owners, have some pretty good guys. But, we only have a few, compared to the mainstream devices, which have a whole lot more. Welcome to the tablet world.
If it were a samsung or Asus, would probably have a ton more.
But, my ICS on my 501 runs pretty darn good. And I'm thankful to each and every dev and cook who strive to make it better. It's a pity there are not more for our device.
SOD will always plague us it seems. A lot seems to depend on the revision hardware. Seems the earlier versions don't get it much.
MD

droidroidz said:
This is some good info! I am pulling my hair our here! As far as what MD suggested I have done all those steps...multiple times with 3 different recoveries wiping everything i can. Do you happen to remember when you purchased them? I bought mine from newegg 8.16.2011
Click to expand...
Click to collapse
same problem as you and 8/10/2011 is when I got mine. I have had some version of hc to work with no sod, but tried everthing and every combination out there (with the mod bootloader) and still have sod, so just went back to stock.

[Q] out of practice and need jelly bean advice

Hi xda
I am totally out of practice but really want a jelly bean update. I am running the last Taboonay vache did before he had to stop development, so i already have cwm running (version 1.3.4)
Is this just like usual? Grab a rom, boot cwm, wipe data dalvik and cache, flash new rom? Do i need to update cwm first?
And finally, what jelly bean rom (if any) should i go with? Looking for something nice and stable.
Thanks in advance for your help and advice!

entropy.of.avarice said:
Hi xda
I am totally out of practice but really want a jelly bean update. I am running the last Taboonay vache did before he had to stop development, so i already have cwm running (version 1.3.4)
Is this just like usual? Grab a rom, boot cwm, wipe data dalvik and cache, flash new rom? Do i need to update cwm first?
And finally, what jelly bean rom (if any) should i go with? Looking for something nice and stable.
Thanks in advance for your help and advice!
Click to expand...
Click to collapse
noooooo lol you have to update your bootloader if your still on honeycomb i got the ota then got an unlocked bootloader after that install your recovery and your good honeycomb roms wont work ics bootloader though so beware

This thread has a guide on how to get from stock to a custom ROM, it also details how to unlock the bootloader.
In one of their updates, Acer updated the Iconia's bootloader (the part that starts up Android) and it is now necessary to install a patched version in order to install ICS/Jelly Bean ROMS. Feel free to ask more questions in that thread if you get stuck.

TastyPi said:
This thread has a guide on how to get from stock to a custom ROM, it also details how to unlock the bootloader.
In one of their updates, Acer updated the Iconia's bootloader (the part that starts up Android) and it is now necessary to install a patched version in order to install ICS/Jelly Bean ROMS. Feel free to ask more questions in that thread if you get stuck.
Click to expand...
Click to collapse
Thanks, both of you! I finally figured it out, now got unlocked boot loader - light speed ROM (the jb rooms seem a little too soon to use), custom kernel, and overclocking enabled with the Lulzactive governor. I am *very* happy!

entropy.of.avarice said:
Thanks, both of you! I finally figured it out, now got unlocked boot loader - light speed ROM (the jb rooms seem a little too soon to use), custom kernel, and overclocking enabled with the Lulzactive governor. I am *very* happy!
Click to expand...
Click to collapse
Glad I could help, I'd appreciate it if you clicked the "Thanks" button under my post

TastyPi said:
Glad I could help, I'd appreciate it if you clicked the "Thanks" button under my post
Click to expand...
Click to collapse
Done!

What am I doing wrong - Kernel help

I cannot figure this out for the life of me. I am running the Lightspeed ROM, but I have the same issue on other roms - I cannot install a kernel for the life of me! Even on a fresh data/dalvik/battery stats, and a fresh never used ROM.
Things go fine in CWM install wise - I reboot after installng kernel (tried 3 diff ones so far) and I get stuck on the ACER bootup screen.
I need the kernel to do overclocking, Would be very grateful for some help here!

entropy.of.avarice said:
I cannot figure this out for the life of me. I am running the Lightspeed ROM, but I have the same issue on other roms - I cannot install a kernel for the life of me! Even on a fresh data/dalvik/battery stats, and a fresh never used ROM.
Things go fine in CWM install wise - I reboot after installng kernel (tried 3 diff ones so far) and I get stuck on the ACER bootup screen.
I need the kernel to do overclocking, Would be very grateful for some help here!
Click to expand...
Click to collapse
ICS overclocking kernels that are available here on xda need the unlocked boot loader.
If I'm correct the light speed rom runs on old HC boot loader 3.01.
You need boot loader V8 see my sig for the v8 guide.

civato said:
ICS overclocking kernels that are available here on xda need the unlocked boot loader.
If I'm correct the light speed rom runs on old HC boot loader 3.01.
You need boot loader V8 see my sig for the v8 guide.
Click to expand...
Click to collapse
Thanks much for pointing me in the right direction! Working on bootloader now

epic win
Thank you so much! Got athe proper boot loader going with TeamWin, eZterry's kernel installed, light speed rom - I am a happy camper!