I have had this problem for two roms and its really annoying. After flashing firmware 3.32.401.x for Vorbeths ics rom, I keep getting frozen out of my phone every time I lock it. It won't turn back on and I have to do a battery pull to get it on again. After having trouble with this i went to Mike's stock ICS rom for the Sensation and i restarted fresh (factory reset, reinstalled 3.32.401.x firmware and wiped dalvik). This time it would freeze after a couple minutes after I locked phone. Can anyone help?
Did you just do a full wipe from the recovery, or did you use the SuperWipe script by Mike...?
Didnt use superwipe
was i supposed to use superwipe? The problem is that it has been happening on any rom with 3.32 software. Does my phone not want to play nice?
Related
I'm by no means and Android n00b. I've been using it since the HTC Magic came out and rooting and flashing ever since.
However, I've been stuck at the Google screen every time I try flashing a different rom other than the one that roots my phone using the Ubuntu script
It works and is rooted after this method, however flashing anything like a rom from TeamWhiskey, et al or a Kernel, just leaves me hanging. Literally.
Any ideas on what I must be doing wrong?
PS
I have clockwork 3.0.x.x flashed and installed already
I'm going to assume that you remembered to wipe system, data, cache, dalvik, etc. prior to trying to flash anything, yar?
Yep. It's a habit at this point. I've gone and wiped everything.
New to flashing roms on the sensation, but not new to flashing roms in general. (Had a Desire before) and i just flashed Virtuous Sensation as it seemed the most stable from what i could see but an hour after i have done so, it has frozen twice. Why is that? do I need to flash a new kernel??
Matty Matt said:
New to flashing roms on the sensation, but not new to flashing roms in general. (Had a Desire before) and i just flashed Virtuous Sensation as it seemed the most stable from what i could see but an hour after i have done so, it has frozen twice. Why is that? do I need to flash a new kernel??
Click to expand...
Click to collapse
Did you do a clean install? Superwipe? Try wipeing cache and dalvik then re-install Rom and reboot immediately after. Meaning don't flash any other mods before rebooting.
Let me know if you are beyond these steps.
i have just played arround whit my rom an it didt the same found out that it was some tweak script there didt the freez
after removing the script it hasnt done it again
All AOSP or CM ROMs are bootlooping. It gets to a certain stage in the boot animation, and then freezes for about 20-25 secs, then reboots and does the whole process again.
This only happens on AOSP or CM based ROMs. Doesn't happen on Sense based ROMs.
Anyone have any suggestions on how to solve this? I'm going to pull a logcat as soon as I can.
Thanks,
Phil
Probably wrong firmware.
Sent from my HTC Pyramid using xda premium
stonew5082 said:
Probably wrong firmware.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
So what firmware would I need for AOSP/CM based ROMs?
Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.
sshede said:
Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.
Click to expand...
Click to collapse
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels
redbullcat said:
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels
Click to expand...
Click to collapse
MAKE SURE MAKE SURE MAKE SURE your MD5s match. Flashing a firmware can brick your phone extremely easily so make sure your md5s match and that you have sufficient battery life left.
Also you will not be able to go back into bootloader without it asking if you want to flash the firmware if its still on your sd. If it asks you can say no but it will just reboot you into your system so if you have no system to boot into youll be stuck and will have to pull your sd card out and then reinsert it when in recovery.
It worked! Thanks guys, I owe you one
Hi all
I just installed the new ARHD ICS rom from mike1986
All worked fine untill I reinstalled the battery logo (zip file name UOT-3.5-blue)
I wiped battery cache and dalvik cache, installed from sd card and now the phone wont go past the beats audio screen after powering on
Any ideas?
Have I bricked my phone?
Are you 100% sure you installed the correct firmware? I seem to recall that happening with my first ICS rom that I put on. If you used the latest ARHD you need the latest firmware, applicable to your phone if you did not SuperCID.
Double check the battery mod is compatible with the rom - this happened to me once.
To recover, just restore your last backup from recovery.
Sent from my Pyramid-T using xda premium
maf-few said:
Hi all
I just installed the new ARHD ICS rom from mike1986
All worked fine untill I reinstalled the battery logo (zip file name UOT-3.5-blue)
I wiped battery cache and dalvik cache, installed from sd card and now the phone wont go past the beats audio screen after powering on
Any ideas?
Have I bricked my phone?
Click to expand...
Click to collapse
No bricked implies no power, just a plain paperweight (looks like it can be unbricked). But that's another thread.
Your issue is to just get the ARHD rom on your sd card if you don't have it on already and just reflash the rom without wiping data. But I prefer to wipe the cache and dalvik cache.
OR you can take out your battery, reinsert, and press power and volume down at the same time to access your recovery. Then restore your nandroid back up. You DID do a backup right?
Yes the firmware was correct
The battery logo mod may have not been compatile
Im going to restore to my last backup and try it again
Ok I installed the last backup, went back into reboot and now the phone is just going round in circles
It comes up with the HTC quietly brilliant logo and just powers off and the repeats that move continuously
The reason I reinstalled the battery logo mod was because it was compatible with ARHD 4.1.13 which I had on the phone before. I thought it would be ok with this new version too
That battery mod is not compatible with ARHD 6.5.1. You can see all compatible mods listed here http://forum.xda-developers.com/showpost.php?p=14191947&postcount=2
Is your backup made from ICS or GB? I think You need an older firmware for GB backup.
I have been trying the new ICS ROMS and have an interesting observation to share. I have had many weird problems like the shutdown reboot issue, touch key lights staying on, force closes etc. The only time I had a clean install (without even the shutdown issue) was when I first used CWM to wipe everything and then used the stock (gingerbread) 3e recovery to perform another wipe before flashing a ROM. Anyone willing to try and confirm?
when u say another wipe using stock recovery, u mean just a factory reset, before reflashing cwm and then ics? becuz if so, ive tried that, and it was still hit and miss
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
rushi.1986 said:
CWM - wipe data, cache and system, Darkside superwipe, ODIN 3e, wipe cache and factory reset, ODIN CWM and flash. Works every time for me.
Click to expand...
Click to collapse
It seems like there isn't an easy fix that works for everyone (for the shutdown freeze bug anyways--this was the one problem I just couldn't get rid of until just a couple days ago). I had a theory that Darkside superwipe was screwing it up for me (the method you use as I've quoted was basically my method for wiping prior to flashing any roms, with the exception of using 3e recovery).
Seanzscreams new Sky ICS rom claims to have fixed the shutdown issue for good. I don't know if this is true for everyone but it seems to have worked for me.
What I do is:
Flash darkside x1
factory reset x5
wipe cache x5
wipe dalvik x5
format system x5
Flash radio
wait 1 minute
flash rom
wait 1 minute
reboot and don't touch phone for at least 10 minutes
I've noticed that some people go to the extreme when it comes to wiping....... Super extreme.
I've always in my YEARS of flashing roms (I got G1 on day one), I've always done just a simple format of data and cache. Normally don't get any unexplained errors or bad flashes.
LOT of the problems rise from users. Either installing something that is buggy or just not following directions.
Restoring backups is probably the BIGGEST CULPRIT OF ALL. Often times, people just restore files that they shouldn't. Adding themes, adding animations, boot animations blah blah blah...then blaming devs because so and so is not working.
I use restore but I'm selective about my restores. I don't just restore everything that I just backed up. Has NEVER caused me any problems.