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.
Related
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Wait till Asus fix the problems.
Yea dont install ICS, it would be like pouring water over your PC
It might seem fun at the time, but its really not a good idea
I would say it is a very bad idea. Avoid it. I did it and literally my tablet is unusable now because of
Slow response
Random rebooted
Random no message crash of apps like gmail.
Dead slow,app response
white screen on app loading
It is now embarrassing infront of ipad users.
Sent from my Transformer TF101 using Tapatalk
spinaldex said:
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Click to expand...
Click to collapse
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
horndroid said:
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
Click to expand...
Click to collapse
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
*Detection* said:
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
Click to expand...
Click to collapse
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
I would no say my TF is unusable under ICS.
It works fine, apart from not so random reboots, as it reboots mainly in the morning when I wake it up form the night...
maybe the Sleeping Beauty requires a kiss from the Prince ...
By the way, it used to be really better under HoneyComb, I wish i could have refused that damned firmware upgrade ...
If I were you I'd rather wait as an other poster said for a really proven Stable version from Asus
Nickola
horndroid said:
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
Click to expand...
Click to collapse
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
*Detection* said:
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
Click to expand...
Click to collapse
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
I've got issues on Stock and I did a full wipe using voldn+power method and this was before I rooted. I also lost sound randomly on Stock, and the custom kernels I still get reboots but my sound for the main part does work.
So, if the OP needs their tablet to work correctly then wait, if it's not that important to them and they don't need for day to day tasks then take a chance, you might get lucky or you might be causing yourself a headache, up to you.
horndroid said:
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
Click to expand...
Click to collapse
How is the problem me when I am doing everything the "ASUS way" ?
The problem is ASUS and their code.
If you read the OP's actual post, you will see this line
"Is it possible to upgrade to the stock ICS"
And if you want to go even further into it, your line "Probably because I do it correctly and do a full wipe including format /system before I flash anything"
I don't think you can get a cleaner flash than NVFLASH, which is how I always flash my ROMs
!!! Attention !!!
.24 seems to be even more imminent, so if you have any patience left, wait for it, otherwise keep on reading
#########
Couldn't take the infant ICS anymore, the RR & SOD, broken sound, gmail freezing etc. Waited a while for fixes but my patience ran out.
If you decide to downgrade via flashing stock images, you will quickly discover yourself in a maze of inter dependencies, missing downloads etc, conflicting & not working root methods.
Instead, flash the Revolver 3.11 (fetch one from Dev Thread) - doable via CW or NVFlash. You will get up-to-date HC distro, rooted & all, with barely any effort at all.
rashid11 said:
Instead, flash the Revolver 3.11 (fetch one from Dev Thread) - doable via CW or NVFlash. You will get up-to-date HC distro, rooted & all, with barely any effort at all.
Click to expand...
Click to collapse
If you're flashing a custom ROM, why not try one of the ICS custom ROM? I don't have RR or SOD with Megatron ROM or any of the ICS ROM I've tried
baseballfanz said:
If you're flashing a custom ROM, why not try one of the ICS custom ROM? I don't have RR or SOD with Megatron ROM or any of the ICS ROM I've tried
Click to expand...
Click to collapse
Same here, other than the latest ICS test Kernel I have seen little to no problems since upgrading to ICS.
glad to hear that ICS's been trouble-free for some folx here, and God knows I tried too, but simply had to back off and wait till 100% stable ICS is released - ASUS or custom ROMs.
I think most of us wuz caught by surprise with ICS instability, we were used so much to how rock stable HC had become around late fall of 2011, ASUS or custom ROMs.
Or save your self the pain, since it isn't going to help much, refurting back to HC. and read Gary's last update:
5/14/2012 Update -
The .24 release should go to FOTA later today or early tomorrow. Please shutdown and perform a cold boot after updating.
Click to expand...
Click to collapse
gkillerx said:
Or save your self the pain, since it isn't going to help much, refurting back to HC. and read Gary's last update:
Click to expand...
Click to collapse
Where did you get this from?
hey, if that .24 thing works (as in proven) and we have a nice pre-rooted NVFlash or CW image out, I won't hesitate going back to HC ... but for now I need something I could rely on
baseballfanz said:
If you're flashing a custom ROM, why not try one of the ICS custom ROM? I don't have RR or SOD with Megatron ROM or any of the ICS ROM I've tried
Click to expand...
Click to collapse
I Was on Megatron and had daily (sometimes multiple per day) SOD's. The problem is at the kernel level, with something that is common to *any* ICS ROM, stock or custom.
Even with guevor's kernel I still had the SOD's. I stopped trying when he was at the 17c version, I think, and nvflashed prime (I posted a quick guide somewhere).
If you want stock, there are guides to go from custom HC ROM's to stock which are simpler than going from ICS to stock HC.
I don't know what you guys are doing to have such bad luck on ICS, but my experience with Team Eos ICS has been absolutely pleasant. Absolutely every minor shortcoming that the tf101 had on HC (like video playback, stuttery transitions, "white boxing" in the browser, etc) is improved or fixed completely in ICS.
The ONLY problem I have with ICS is that the one single app I depend on every day for work is incompatible with ICS - not a fault of ICS, but the developer of that app. Thats why of my two tf101s, one of them is still running HC (Prime 2.1.1)
None of us doubt the evolutionary nature of ICS and we all will gladly upgrade to ICS when the issues are fixed. For now, some require tablets that are good enough to be relied on.
The "wait a for a full moon, have 23 ml of blood of virgin male chicken handy, face North (do account for magnetic field) at exactly 12:34, wipe 7 times, wait 50 minutes between, upgrade to 18.1, immediately downgrade to 17c ... etc" recipes are a bit more than I could handle .
Seriously, I was so used to how solid stock HC was, I was totally shocked by ICS ... should've never allowed auto-update ... wait, ASUS gave us non-rooted users no choice in the matter
rashid11 said:
None of us doubt the evolutionary nature of ICS and we all will gladly upgrade to ICS when the issues are fixed. For now, some require tablets that are good enough to be relied on.
The "wait a for a full moon, have 23 ml of blood of virgin male chicken handy, face North (do account for magnetic field) at exactly 12:34, wipe 7 times, wait 50 minutes between, upgrade to 18.1, immediately downgrade to 17c ... etc" recipes are a bit more than I could handle .
Seriously, I was so used to how solid stock HC was, I was totally shocked by ICS ... should've never allowed auto-update ... wait, ASUS gave us non-rooted users no choice in the matter
Click to expand...
Click to collapse
I haven't seen anyone post anything like that to get ICS to work. It seems like it either does or doesn't, I would call it user error but I would probably be beheaded by all the people who have these issues. All I know is that along with other people I am running ICS and can go days, if not longer, without a single SOD or RR.
If you need to go back to HC, go right ahead, but try not to be too harsh as from what I can tell, 90 % of the community isn't having major issues.
rashid11 said:
None of us doubt the evolutionary nature of ICS and we all will gladly upgrade to ICS when the issues are fixed. For now, some require tablets that are good enough to be relied on.
The "wait a for a full moon, have 23 ml of blood of virgin male chicken handy, face North (do account for magnetic field) at exactly 12:34, wipe 7 times, wait 50 minutes between, upgrade to 18.1, immediately downgrade to 17c ... etc" recipes are a bit more than I could handle .
Seriously, I was so used to how solid stock HC was, I was totally shocked by ICS ... should've never allowed auto-update ... wait, ASUS gave us non-rooted users no choice in the matter
Click to expand...
Click to collapse
I have no idea what you're talking about, dude...
ICS works fine. I didn't do any weird dance or ritual involving blood from a chicken. I simply installed Eos ICS and haven't had a single issue. Its better, faster, more stable than Honeycomb in every measurable metric. If you are having a different experience, I don't know what to tell you..
No sleep issues, no random reboots, all features work correctly. I don't know how else to put it other than saying there are ZERO problems with my tablet running ICS.
I agree, Ics is amazing IMO. I had freezing and reboot problems with HC, but I havn't really been on stock ICS, only AOKP/Megatron/ARHD with Testymehics/test kernels. No sod problems here.
Stock ICS
Sorry guys, no problems here at all and I am running stock ICS. No issues what so ever.
a.mcdear said:
I don't know what you guys are doing to have such bad luck on ICS, but my experience with Team Eos ICS has been absolutely pleasant.
Click to expand...
Click to collapse
I've no doubt whatsoever that you have a great experience with ICS on your tablet. TBH, other than the SOD's, I liked ICS better than HC: Faster, snappier, more intuitive UI, etc. This isn't about the the OS or UI in general, it's a problem with the kernel and it is very inconsistent. While maybe the majority of people with a TF don't have a problem there is still a large group who do have problems. And these are also all over the place:
- SOD
- Random Reboot
- SOD + Random Reboot
- Screen glitching (or something like that)
- other weird stuff, less critical.
Nobody is doing *anything* to have such bad luck. It's just, well, bad luck. I love ICS and have it on my SGS, which ironically, wasn't even supposed to have been running ICS in the first place. And it's rock solid, fast, dependable and I love it tons more than the iPhone 4S they gave me at the office
miketoasty said:
Where did you get this from?
Click to expand...
Click to collapse
Like i said from gary :
http://forum.xda-developers.com/showthread.php?t=1556914
Does anyone have access to NVFlash version of Revolver 3.11? (all links I've found are dead)
Apparently SOD and RR still exist in ICS .24
I downgraded using CWM .zip of 3.11 , that one was still available 2 days ago.
kermitdefroghere said:
Apparently SOD and RR still exist in ICS .24
Click to expand...
Click to collapse
How do you sure about this? Have you updated to ICS.24???
My stock ICS.21 is doing great with a little mod.. flashed guever's custom kernel and those SOD or RR are gone.. Everything else is stock with all those ICS greatness.
farsight73 said:
How do you sure about this? Have you updated to ICS.24???
My stock ICS.21 is doing great with a little mod.. flashed guever's custom kernel and those SOD or RR are gone.. Everything else is stock with all those ICS greatness.
Click to expand...
Click to collapse
Check jtroskys posts in the official ics thread (stickied).
He was a beta tester for. 21 and .24.
Though stable initially .24 has receded back to the regular sods and Reboots many of us have been struggling with.
I've officially stopped waiting and went to Revolver.
Edit: Just to be clear... that's Revolver 3.11.1 (Honeycomb) with Blades kernel 3.
Very impressed.
Funny how an overclocked 3.2.1 build can be more stable than ICS (at least so far).
VERY impressed with Revolvers 3.11.1
Enjoying my Transformer again.
Sent from my XT910 using Tapatalk 2
Hello All,
Here's my 2 cents on SODs and killing of it (even if only temporary)
I am currently on @Anti's Asylum ROM. Previous to that, I was on CM9 ver 7.
Had been plagues by SODs and had almost given up and was about to flash Samsung Stock ROM.
I was on Stunner previous to CM9. Once I was on CM9 and loving it, I came across this nasty looking creature called SOD for the first time in my life.
Threads suggested I should flash GB ROM back and do a clean install. @AndroidIndian was kind enough to walk me through all the steps and I did everything I had to. Then flashed CM9 back. Guess what, those SODDIN SODs were still there.
So, apologetically, I posted that I had to betray my brethren here and go back to Samsung Stock.
Then, @Tremorone PMed me to try @Anti's asylum, built on CM9 code. He said since I was trying to hold on to an AOSP thing, I should try it at leas once. In one last ditch effort, I did the right thing - flashed Asylum ROM over the CM9 ver 7.
Now, the interesting bit:
Initially, I was on XXLPT Modem (the latest one). Overnight, there was no SOD and I was a happy bunny. Next morning I got a long call (about 20 mins). Once the call was over, SOD !!!! Figured it HAD to be a modem.
So, I did the following:
1) I flashed LP5 Modem through Mobile Odin. SODs were less but the lockscreen froze up once.
2) Being the impatient prick that I am, after a while I flashed LB2 Modem via CWM Recovery.
SODs has drastically gone down on that. No SODs in the last 7 hours as a matter of fact.
I don't know if it's the ROM, LB2 via CWM or the combination of Steps 1 and 2 above, but seems like it has more or less solved the problem. Of course, it is still early days and I need to observe for a couple days more.
To everyone suffering at the hands of the SOD demon, I would suggest why not try Step 1, let the ROM settle, and then proceed with Step 2 (as above).
There's no harm in trying, right? And if it solves it, nothing more beautiful than it. Then you can go CM flash happy as soon as new builds start being avaialble.
Thanks to @Abhisahara for helping me keep the faith.
All the best SODding off the SOD.
Cheers.
Well, I think I'm a lucky guy. I had never one SOD since I own a note. I have nearly the same flashing history like you. Flashed also many modems . I can't imagine why the devices are so different. The same thing I noticed with my old HD2. I hope you will find the reason/way to solve this f******* SOD issue
Gesendet von meinem GT-N7000 mit Tapatalk 2
I'm the same after flashing cm9 I had one screen of death on the lb2 modem.. I flashed lp6 just because.. After that I used cm9 for a week with not one sod before flashing ics official
Sent from my superior Nokia 3210 using XDA Premium Plus Legacy Edition
My SODs stopped after I flashed .19 Stunner with LP5 kernel and LP6 modem. I haven't had one since then (**knock on wood**). I am on stock ICS now with the new modem, not CF-root kernel though. Strange how variables are always so different though.
Hmm,
I've flashed several modems since being plagued by the SODs. I'm on CM9 nightlies and am using LP6 from LB2. The SODs have gone down with the newer modem since I was getting 5 or 6 a day! But, I still get at least one or two a day now. I'll try with the latest LPT or LR1 and see if these make any improvements.
They are a bit of a mystery though since there never seems to be any consistency to what is actually causing the sleeps.
I always flashed modems through Mobile Odin and flashed every single modem available for note, but still had SODs.
So I wiped everything and reinstalled the ROM and did not restore data and I did not have SOD.
I have data backed up on Google, it restored my apps (through play store), contacts and wifi access points, so I was kind of OK, since I did not lose out much. But thats just me!
I tried LB2 ,LA4 ,LPY Modems ,and had one SOD in two weeks time while on CM9 build#3 and LA4 modem.
LB2 modem iks very good and I'm using it right now with the latest nightly with no SODs what so ever.
I've flashed modems using CWM and still get the SODs. I'm beginning to think these are not directly related to the modem. I did a clean install of GB from Imilka's CM9 (Chinese leak) then Chainfire's rooted kernal and then on to the CM9 nightly. I didn't copy any system data but I did use TB to resinstall my apps (against advice I know). I had no SODs on Imilka's rom but they appeared following install of CM9 nightly.
I guess I'll try a clean install again but I hate having reconfig my phone everytime since I change so many things via Apex, Minimalistic Text and Folder Organiser apps.
I'm hoping though that we'll get to a nice update on CM9 that will resolve the problem eventually.
I think SOD is WIFI related (not just modem). Since upgrading to ICS, different ROMs, I had many of them on all ROMs and modems, until I set my WIFI to never sleep and disabled any battery saver trying to make it sleep when screen off. That solved it for me. Then started testing battery savers, most of them brought SOD again, until I tried battery defender, which seem to work without SODs.
Had lots of SODs in the past on CM9, none for 3 days since I installed nightly 20120515 and LPT modem. Fingers crossed
i bought cheap milestone 2 and wanted to try CM on it
rooted, installed CWM
tried to flash CM 7.2 RC3 and it fails after "checking kernel version..."
so i guess my 2.2.2 is too old
went back to wiki, tried to flash their downgrade rom VRZ_A955_2.3.20_1FF_01.sbf hoping that it will get me to the right spot
no joy here as it fails (running as admin etc.) with "Phone is not compatible with multi-interface super-file."
any suggestions what to do now, as this is where i start worrying that i might do\flash something stupid and brick it
Hello!
Sorry if I'm wrong but, wouldn't be needed do update to 2.3.6 first?
Yet, this could help:
http://forum.xda-developers.com/showthread.php?t=1310641
It says that you can update from Froyo.
actually it was just me being dumb as i tried to install
update-cm-7.2.0-RC3-droid2-signed
instead of
update-cm-7.2.0-RC3-droid2we-signed
as WE in filename means that this is rom for global, gsm version (that i have)
it updated ok, but all i get now is motorola logo and then black screen, i can't even get CWM to start...
Hi, first you may know, there are two different phones Droid 2 and Milestone 2 (A953), maybe you are trying to flash wrong sbf to your phone.
pepe55 said:
Hi, first you may know, there are two different phones Droid 2 and Milestone 2 (A953), maybe you are trying to flash wrong sbf to your phone.
Click to expand...
Click to collapse
yup, just figured it out, had to flash back to 2.2.2 with
MILS2_U6_2.4.24_SIGNED_UCAMILESTONE2B1B80E100E.0R_UCXMILE20RTGB_P040_A013_HWp2a_Service1FF.sbf
and is working now...
for some reason i thought that droid 2 global = milestone 2
what should i look for if im interested in most stable rom for milestone?
Indeed, be sure of the sbf version.
Try going back to stock and do it again, cleaning data, cache and dalvik before and after update.
*didn't see that it worked hehe
Most stable roms, IMO are MIUI 2.5.25 and CM7
Now i'm trying CM9 (20120602) and i'm enjoying, still checking. Seems like it's worth the try.
Still some issues to solve, like recording, etc... but looks like good for daily use.
People say that MIUI tends to give some compatibility issues sometimes. And Cm7 fails to run some apps... like ShadowGun (well, in my Miles it fails hehe).
I'm very happy with MIUI from Will5, check it. It has very good battery life, the rom is smooth and stable and very addictive =D. I got small amount of forbidden crashes. I'm trying other roms as well but always come back to MIUI until better rom comes out, if it happen sometime. It has froyo kernel and i dont have any strange touchscreen bug, but the touch responsive is a little less then newer kernel, thats no problem for me.
trying it now, installation hints states "Flash UPDATE_2.5.25.zip from cwm 4.x.x.x or greater"
how to get cwm 4x?
all i found is 2.something in cm wiki and 3.1 in bootmenu
anyway i installed it with 3.1.0.0 and it seems to be ok
I installed it as you without any problems, I think it can be flashed from recovery from droid2bootstrap. If you dont like MIUI you can try another ROMS maybe original 2.3.4 sbf, in developer section is manual to get out the blur (and bloat) from stock roms. I test it someday but Im happy with MIUI.
pepe55 said:
I installed it as you without any problems, I think it can be flashed from recovery from droid2bootstrap. If you dont like MIUI you can try another ROMS maybe original 2.3.4 sbf, in developer section is manual to get out the blur (and bloat) from stock roms. I test it someday but Im happy with MIUI.
Click to expand...
Click to collapse
miui installed fine, it looks great, but after some basic configuration launcher start FC, as i dont have time to experiment just now i flashed latest CM7 i found (cm7-120221-1901-NIGHTLY-Milestone2.zip) and it is working perfectly, just as good as on my LG P990
Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.
If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.
dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.
A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800
You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.
as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...
The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!
Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.
First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).
Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.
What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?
Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?
You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.
and now i have blue screen.. what can i do? or have i bricked it?
Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder
basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..
Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.