Related
I have been trying out a couple Ics roms, all of which claim have no SOD, but I'm still having problems. I have tried
Lightspeed 4.2
Latest icylicious
Tabooney 3.0.1
I guess to be sure, what I'm experiencing is every seems to work fine, but if the screen goes off for more than a couple seconds, it won't come back on. I have to hold the power button for a few seconds, then let go, the hold down the button again it turns on again fine.
What bootloader did you flash?
FloatingFatMan said:
What bootloader did you flash?
Click to expand...
Click to collapse
I guessed that I still have the boot loader that I installed back when I got my a500 last summer. I thought the ICS boot loader was unstable or something. Should I try the other bootloader that is posted?
Edit: I checked in thee Acer Recovery Installer app and it says I have bootloader 3.01
The SoD is usually caused by the bootloader, but it's possible you didn't wipe something when you flashed one of the ROMs. Personally, I'm running the version of AmonRA we have (though that's not fully compatible with Acer Recovery Installer), and on top of that I have Vache's ICS leak, complete with his 3.0.1 patch. I have no SoD issues at all with this configuration.
You DID do a full wipe, right?
veidt_industries said:
I have been trying out a couple Ics roms, all of which claim have no SOD, but I'm still having problems. I have tried
Lightspeed 4.2
Latest icylicious
Tabooney 3.0.1
I guess to be sure, what I'm experiencing is every seems to work fine, but if the screen goes off for more than a couple seconds, it won't come back on. I have to hold the power button for a few seconds, then let go, the hold down the button again it turns on again fine.
Click to expand...
Click to collapse
I tried both icylicious and flexreaper and could not get rid of the SOD either. I have the 3.01 bootloader and have wiped and formatted and wiped some more. Everyone keeps saying the SOD is because I didn't do a full wipe. I'm back on 3.2.1 now.
Did you check if an ICS incompatible app might be the reason?
Best regards, maris
maris__ said:
Did you check if an ICS incompatible app might be the reason?
Best regards, maris
Click to expand...
Click to collapse
I thought an app might have been at fault so I did fresh formats/wipes and didn't restore any apps to be sure but still got SOD. The screen goes to sleep normally then after a short time reboots and gets stuck until I press power to turn off, then power back on.
Thanks everybody, it was the bootloader. Just for closure, here is what I did.
Install leaked ICS from here
Fix the bootloader and recovery from this thread
Install ROMs like normal
Thanks again
Had SOD all the time with flexreapper, installed newest thor's and all SODs gone. I guess the issue is specific to ICS' ROMs based on the leak.
Whats the newest version of thor clockworkmod recovery for Iconia a500?
veer01_42 said:
Whats the newest version of thor clockworkmod recovery for Iconia a500?
Click to expand...
Click to collapse
NEXT time, Google should become a resource for you..... But this time, V1.7.1 I believe is latest 'touch' version.
SOD ain't there on LEAK version...
ROOT can be done on LEAK version...
the problem for sure is from CUSTOM
There's no SOD in the custom ROM's built from the leaks, either; as long as you followed the instructions properly.
Try this out. Finally worked for me.
Hey a little late here, but I have had SoD for months. I have tried everything (new bootloader, several roms), but nothing seemed to work. I finally tried flashing a custom kernel separately after I flash the rom and it seems to be working now.
Here is the ezterry A500 rom, http://forum.xda-developers.com/showthread.php?t=1703590 and its a zip so you flash just like a rom. Good luck everyone who has the same problem.
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
fayettec said:
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
Click to expand...
Click to collapse
Did you install the Flexreeper new bootloader? This is probably why you still have SOD. If I am not mistaken, Flexreeper has 2 or 3 different versions of bootloader that you need to use. Depending on which version of the rom you want to install.
Scary Bootloader
Moscow Desire said:
Did you install the Flexreeper new bootloader? This is probably why you still have SOD. If I am not mistaken, Flexreeper has 2 or 3 different versions of bootloader that you need to use. Depending on which version of the rom you want to install.
Click to expand...
Click to collapse
Thanks for the reply.
I thought that the img file was for people with ICS bootloaders, I thought that I had HC3.0.1
I'm afraid if i flash the ICS img file that I won't beable to get back to HC or that because I have 3.0.1 bootloader that the ICS bootimage file they have there will brick my a500
If you formatted and wiped everything as you were instructed . I am wondering if when you get to the google setup screen something is being restored from the old system.. When it gets to where you setup your google account. Uncheck the backup and restore boxes .
Do not restore any apps or settings from say TI BACKUP. Install only a few apps that you MUST HAVE and know work with google ics. run for a few days and see what happens.
if you still have a issue go back to 3.2 for a week and see if it works. it could be just coincidence that hardware fail-or at the same time as you flashed your tab. ..
just a though thou unlikey
Thanks
I went ahead and tried the ICS Boot.img file after reading some new post in the thread. It worked! Interesting side note, be fore the flash at boot up the display showed:
ACER.
After it was:
ACER ACER
Thanks again!
fayettec said:
I went ahead and tried the ICS Boot.img file after reading some new post in the thread. It worked! Interesting side note, be fore the flash at boot up the display showed:
ACER.
After it was:
ACER ACER
Thanks again!
Click to expand...
Click to collapse
You running an a500 or an a501?
Last time I saw the double Acer, was when the leak first came out. The 500 had issues, but not the 501 (except for double acer).
The double Acer is normal. Be glad you don't get the AFU screen like the rest. It's a BETA release, and it has..... issues. Hopefully Acer will release an official build that will do away with a lot of the issues in the near future.
fayettec said:
I, Not at 10 post yet so Here I post,
Can any one help me with SOD on the new Flexreaper 11 ROM. Acer Recovery tool indicates i have 3.01 bootloader. I Had a 3.2 Rom before that worked fine. I Wiped everything and formatted Flexrom and system. First time it went to sleep it would not wake up.
Thanks!
Click to expand...
Click to collapse
I came from ezterry's acer7.014.14_CUST_ROOT_BBv4_S. I just flashed Flexreaper R11 this morning. I've noticed SOD at least three times today. My bootloader version is 3.01 like in the OP. I noticed he ended up flashing the ICS bootloader. Is this the only known fix? And if so, will ICS bootloaders prevent me from restoring a HC NAND? Thanks.
How do we find our boot loader version? When I do, what does that mean for ROMs I can flash? I have flexreaper r11 and it is consistently SOD badly. :'(
Sent from my SGH-I777 using xda premium
bigwilly90210 said:
How do we find our boot loader version? When I do, what does that mean for ROMs I can flash? I have flexreaper r11 and it is consistently SOD badly. :'(
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
To me a favor and flash the kernel for ICS boot loader users.
Its in the thread , section kernels.
The rom got a auto script for installing the correct boot.img but even for some the ICS boot.img is needed.
Worst that can happen is stuck on Acer logo, if you got that just reboot into recovery and flash the boot.img or kernel for HC boot loader users.
The thing is that even for some people that got HC bootloadr they still need to flash the Kernel for ICS boot loader users, strange yes but no harm in trying.
I'm wondering if something in the cmdline for the LP0 changed in the latest leak causing the kernels packed for the old bootloader to have SoD again.
Also, some of you guys, please don't confuse bootloader with boot.img. They are not the same thing. FLEXREAPER does not contain any bootloaders. It contains 2 different boot.img's and trys to install the correct one based on the bootloader you have.
The bootloader only gets changed if you flash it via nvflash (or flash a stock leak but then it would be locked).
@someone who asked above. if you flash the ICS bootloader(0.03.11-ICS), you would not be able to run HC ROMs, unless you went back to the HC bootloader (3.01).
But apparently, the ICS boot.img is working for some on the old HC bootloader and resolving the SoD issue for them.
Hey guys,
this is my first post and my problem is as follows:
I had ICS 4.0.x on my galaxy tab 10,1 P7500, I then installed CWM 5.5.0.4. but had a rolling window. I then continued to install a bootloader (here: http://forum.xda-developers.com/showpost.php?p=27830023&postcount=41) with the appropriate bootloader for the p4. This fixed the rolling recovery and allowed me to install CM10 using CWM.
But my current problem is when the device goes on sleep mode and I wake the device up the screen is scrambled, can anyone tell me how to fix this?
Thank you in advance
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
Edit:
I fixed the rolling screen issue after screen unlock with pershoot's help, thanks again pershoot!
Maybe it will also work for you , here we go:
If you have installed the latest cm10 build, there is only one issue for the p4wifi , you must be on the US ICS Bootloader .
So download the recovery.tar.md5 from here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/recovery.tar.md5
Than go into download mode and flash this recovery using ODIN, (select pda and look for this file where you safed it, than click start)
Than, download the right US ICS Bootloader here:
http://droidbasement.com/galaxy/roms/cm10/p4wifi/US_LPL_4.0.4_bootloader.zip
Flash this also via ODIN in the PDA section, this may take a little longer, don't panic...
After that, the tablet will reboot and it should work... don't blame me if it didn't, but i had this rolling screen on almost every rom, and everything is fixed now...
I wish you good luck because i know it IS very annoying..
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
DefQoN_BE said:
I have EXACT the same issue, i'm running the latest cm10 build from droidbasement.com, if anyone can please help us???
The only fix i found is for HC
http://forum.xda-developers.com/showthread.php?t=1680738
I wish you good luck because i know it IS very annoying..
Click to expand...
Click to collapse
I have tried this method and works perfectly!
Thank you sooo much!!!
I am afraid to put a rom on my 10.1, i love it though!
blacks10 said:
I am afraid to put a rom on my 10.1, i love it though!
Click to expand...
Click to collapse
There's nothing you should be afraid of there is a fix for everything, and if you can't find it? There are nice poeple out there who wants to solve your problrm on xda developers forum
@drefcom: you're welcome
Please help - When turning off the Screen Android 4.1.1 will not come back on
I have the following problem.
When I install one of the latest rom e.g.
[ROM] [JB] [P4--P4WIFI--P4VZW]
4.1.2 AOKP for the Galaxy Tab 10.1
or
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview
then I have this problem:
When I turn off with the "Power"-Hardbutton, then it turns off, but it does not turn back on. The screen stays black.
With the Rom ...
[ROM][JB][CM10] Android 4.1.1 - CyanogenMod 10 Preview "cm-10-20120814-EXPERIMENTAL-p4.zip" from August everything works fine.
Since I had this flickering problem I flashed the bootloader before I installed all these Roms.
But one works and all new ones don't.
Anyone has a idea what to do?
thx
drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Hi guys.
speersie said:
:good:
Thanks this helped me fix a mates Galaxy Tab 10.1
I was starting to pull my hair out and this worked so well.
Takes no time to do and no need to reflash the rom.
Click to expand...
Click to collapse
i tried this method, but at second flashing (bootloader.zip) i get "0 succeed/0 failed" and still i get that scramble, and have to reboot all the time.
Any ideas?
Thanks in advance.
Cheers!:good:
Problems solved
I solved my problems. I installed the "custom" bootloader for each Rom and the "black screen" problem is now gone.
Thanx anyway.
drefcom said:
Thanks for the reply DefQon, I agree I think this is most annoying errors I have ever gotten.
I also searched high and low and could only find the fix for HC.
I have tried this method and works perfectly!
Thank you sooo much!!!
Click to expand...
Click to collapse
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
drefcom said:
I have tested the fix for weeks now and it worked great.
Except, this afternoon my tablet randomly restarted and now won't go past CM 10 boot screen.
Any idea whether reflashing the ROM without wyping, purely just installing (as is) CM10 M2 from CWM? Or any other ideas?
I have tried clearing the cache and the dalvik cache. I then tried doing a factory reset but it doesn't seem to proress. I thought if I can do a factory reset then reinstall the ROM I might get it to work but I can't install the ROM as it says "Error (Status 7)?
I have tried formatting the /data in attempt to get the factory reset to work but this also freezes.
Currently, my tablet is in an infinite loop cycle and I cannot change the ROM or do a factory reset.
Thanks, you guys have really been helpful!
Click to expand...
Click to collapse
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
drefcom said:
After hours of trying I have found a solution.
I previously had done backups. I tried each one until one started restoring. It completed quite a lot till it froze and I restarted into recovery.
I did a cache wipe and dalvik cache wipe and could then complete a factory reset.
It has now booted completely into ICS where I can now flash CM10 again.
The tablet works normally as you would expect on ICS. I booted into recovery and tried to flash CM10 M2 for the GT-P7500 but I still get a error, status 7.
Anyone experienced this?
Click to expand...
Click to collapse
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
DefQoN_BE said:
Status 7 usually indicates the wrong update file, are you sure you are flashing the right ROM for the 7500?
Perhaps try to flash the recovery and bootloader first and then the right ROM and see what happens?
Click to expand...
Click to collapse
The thing is it is the exact same file I used to flash the previous time.. I first updated my recovery and bootloader before flashing and still get the error. Thanx for the thought though.
Hi guys, hoping someone could help me out here.
I was running my tablet on ICS before with the HC bootloader (I believe it was Tablooney) and of course I was stupid and didn't make a backup.
long story short I flashed the bootloader and started experiencing random issues where the tablet would not wake up, thought ok maybe I missed a wipe of cache, battery stats, or dalvik-cache, or something. did the wipes that wouldn't kill my rom and still had the same problem.
did a full wipe and used a JB rom, still same issue
had some weird issue, restored to HC BL and rom, tried to do OTA to ICS (used EUU to go back) Tablet would not see the OTA ICS update.
so tried a third rom, still same problem. does anyone have any suggestions or insight as to why this is happening?
Thanks!
BlueWyvern said:
Hi guys, hoping someone could help me out here.
I was running my tablet on ICS before with the HC bootloader (I believe it was Tablooney) and of course I was stupid and didn't make a backup.
long story short I flashed the bootloader and started experiencing random issues where the tablet would not wake up, thought ok maybe I missed a wipe of cache, battery stats, or dalvik-cache, or something. did the wipes that wouldn't kill my rom and still had the same problem.
did a full wipe and used a JB rom, still same issue
had some weird issue, restored to HC BL and rom, tried to do OTA to ICS (used EUU to go back) Tablet would not see the OTA ICS update.
so tried a third rom, still same problem. does anyone have any suggestions or insight as to why this is happening?
Thanks!
Click to expand...
Click to collapse
Maybe I have an answer.
1. After returning to stock, you should have installed Acer Update Enhancer from the Play Store. Without it, you won't get OTA.
2. Early release of the ICS had some SOD issues kernel related. The current ICS roms shouldn't have this anymore. However they require the V8 unlocked bootloader. Also, they use modified kernels.
Make sure you have V8 installed, An appropriate CWM recovery like Thor 1.7.2 or .3. Do your wipes, then install one of Civato's Roms. His are current builds. And, Do ALL your wipes in CWM as per the OP instructions.
MD
Moscow Desire said:
Maybe I have an answer.
1. After returning to stock, you should have installed Acer Update Enhancer from the Play Store. Without it, you won't get OTA.
2. Early release of the ICS had some SOD issues kernel related. The current ICS roms shouldn't have this anymore. However they require the V8 unlocked bootloader. Also, they use modified kernels.
Make sure you have V8 installed, An appropriate CWM recovery like Thor 1.7.2 or .3. Do your wipes, then install one of Civato's Roms. His are current builds. And, Do ALL your wipes in CWM as per the OP instructions.
MD
Click to expand...
Click to collapse
That Update enhancer did the trick to take me to ICS. Then I used afterota to get rooted (which also flashed my boot loader) and now I have ICS, root, and the v8 BL!
Thanks MD!
I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Kesh09 said:
I'm running an S4 and have this very weird issue where after installing a custom rom, the phone would reboot and load the rom successfully, but if I ever reboot it, it never wants to go past the Samsung logo.
If I try entering TWRP and fixing permissions or factory reset, it just comes up with errors and fails. The only way around it is to format data, then reflash the rom.
But now I have a nandroid backup so everytime I reboot, I basically have to reflash the rom.. It's happened on at least 2 roms!
I've used the search function on the forums and found a thread was inconclusive so I've made this thread.
Thanks in advance
(This is my first Android phone too, so I'm not 100% familiar with all the different software and techniques, but I can definitely learn!)
Click to expand...
Click to collapse
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Gotcher said:
Try flashing the ROM with the latest stock CWM. TWRP can cause issues.
Click to expand...
Click to collapse
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
scottyf79 said:
go into the wipe options on twrp - go to advanced and select - cache, dalvik, system, data - swipe
then do a normal full wipe
reflash the chosen rom
power off rather than reboot
then power up
something gets fracked with the wipes somewhere and thats how i fixed it.
either that or flash philz recovery through odin and do a "new rom" wipe
Click to expand...
Click to collapse
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Kesh09 said:
For some reason, whenever I install CWM, it keeps getting stuck at "recovery booting" and once in maybe 30 times it works, haven't got it to work in a while.. Not sure what's happening, but if I flash TWRP again, it boots up fine. Am I doing anything wrong? Using Philz touch..
This hasn't worked for me, and yeah, I can't seem to get CWM to like my phone..
Click to expand...
Click to collapse
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
scottyf79 said:
try flashing the rom twice in succession. it will stick eventually but its just getting the right combo. these S4's are a right pain in the ass just now.
also another option would be downloading a rom with Aroma installer onto a micro sd and see if that gets you out of the problem. ive found on other devices ive had that a rom with Aroma can sometimes get you moving (id suggest Omega rom as a good solid base)
Click to expand...
Click to collapse
The rom I'm flashing (twice) now is Omega actually!
I'll see how this goes! Hoping it's okay!
..
try to install another rom clean & stable and do full wipe or trust me the best to turn the phone to default firmware.
Kesh09 said:
The rom I'm flashing (twice) now is Omega actually!
So are you suggesting I install Omega, get it run, then install Aroma installer and reinstall it?
Click to expand...
Click to collapse
no i just meant flash the rom twice IF it didnt have Aroma.
try GoldenEye rom from micro sd (obviously downloaded and placed on the card through a pc and put back in the phone).
Or as above - you might have to start from scratch and use Odin to revert back to stock and re-root etc again.
Although i said Aroma sometimes helps, being honest it was a rom with Aroma that started causing me a similar issue in the first place (Not Omega or Foxhound though)
No luck guys... I think I'd rather start from a stock rom too. When I created my stock rom backup, it was through nandroid and an CWM format, but CWM did work, it froze when it was checking for MD5 or something...
But now I'm trying to find the right firmware for my phone, is there any thing I need to look out for? Gt-i9505 from Australia?
http://forum.xda-developers.com/showthread.php?t=2265477
In that thread, there's two of them, I'm downloading the one closest to when I bought it which was June