Being new to custom ROMs, I finally installed ARHD last week.
Twice, I have the issue where I can't get my screen to turn on. In the last incident: I received a text, saw the blinking LED, and pressed the power button -- the phone doesn't respond at all, except the LED keeps blinking. I have to pull my battery out and restart the phone.
This isn't related to the camera issue. (I'm not using my camera at all.)
This occured once on each kernel, faux 0.2.4 and 0.2.3.
Any help is appreciated. (Did my best to search!)
DEVICE : HTC Sensation
ROM : Android Revolution HD™ 3.6.5 XE
KERNEL : faux123 v0.2.4r
RADIO : 10.58.9035.00U_10.15.9035.02_2
terchie said:
Being new to custom ROMs, I finally installed ARHD last week.
Twice, I have the issue where I can't get my screen to turn on. In the last incident: I received a text, saw the blinking LED, and pressed the power button -- the phone doesn't respond at all, except the LED keeps blinking. I have to pull my battery out and restart the phone.
This isn't related to the camera issue. (I'm not using my camera at all.)
This occured once on each kernel, faux 0.2.4 and 0.2.3.
Any help is appreciated. (Did my best to search!)
DEVICE : HTC Sensation
ROM : Android Revolution HD™ 3.6.5 XE
KERNEL : faux123 v0.2.4r
RADIO : 10.58.9035.00U_10.15.9035.02_2
Click to expand...
Click to collapse
Hi,
I am running 0.2.4.r as well ,but I have never encountered any such problem.
Nor have read about any such problem for 3.6.5.
Can I ask if you wiped your cache partition and dalvik ,before your kernel installation?
Also, was your 3.6.5 installation a clean install i.e. did you super wipe?
Also,if it does lock up,you can just press volume up and down + power button.
That saves having to pull the battery.
malybru said:
Hi,
I am running 0.2.4.r as well ,but I have never encountered any such problem.
Nor have read about any such problem for 3.6.5.
Can I ask if you wiped your cache partition and dalvik ,before your kernel installation?
Also, was your 3.6.5 installation a clean install i.e. did you super wipe?
Also,if it does lock up,you can just press volume up and down + power button.
That saves having to pull the battery.
Click to expand...
Click to collapse
Yes, I wiped cache and dalvik prior and after the kernel installation.
Yes, I ran the super wipe script prior to the ROM installation.
Tried to follow everything to the letter.
Thanks for the tip. I will try that if it occurs again!
A little off topic, but what exactly is stored in the cache/dalvik? When should we wipe it, whenever we install something via recovery? (e.g. Kernels, APM, CRT Animation, etc.)
terchie said:
Yes, I wiped cache and dalvik prior and after the kernel installation.
Yes, I ran the super wipe script prior to the ROM installation.
Tried to follow everything to the letter.
Thanks for the tip. I will try that if it occurs again!
A little off topic, but what exactly is stored in the cache/dalvik? When should we wipe it, whenever we install something via recovery? (e.g. Kernels, APM, CRT Animation, etc.)
Click to expand...
Click to collapse
Hi,
Dalvik cache is a program cache area for the program dalvik. Dalvik is a java based virtual machine that is the basis for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. Sounds confusing. It's similar to the prefetch files in Windows.
Yes,wipe it before installing Kernels, APM, CRT Animation, etc.
Related
Currently running CyberGR v3 ICS rom and noticed a weird behavior on my phone.
Search button keeps flickering by itself opening the 'Complete actions with' option on the screen. It keeps happening until screen is completely unresponsive and I have to lock/unlock the phone for it to work. Eventually it would happen again.
I have cleared cache, dalvik, factory reset, fixing permissions, re-applied rom from scratch (full format of system, data, cache, boot) and even changed the kernel from original GLADOS 2.7 to Matrix 14.0 (have not tried the latest ones).
Any ideas on why this happens? Hopefully I can resolve this since I really like this ROM.....heeeelp
Update: I got the issue resolved by flashing the lastest Radio I9020AUCKF1.
Im really hoping someone can help me please...
ever since viper 1.6.x sometimes my phone will shut down, or if my phone battery runs completely dead of battery, and then when i try and turn the phone on again it will go into a boot loop where is gets stuck on the senasation splash screen...
can someone tell me why this is happening and how i can turn my phone back on after this happens...?
info
i am on vipers had this problem since 1.5.x - 1.6.x with multiple kernels, but the last kernel i was on when this happen was faux 10b9
this most often happens when the battery run completely dead, but has occasionally happened on a random reboot swell
things i have tried...
pulled battery...
clearing dalvik and cache - this will get me past the splash screen once, to the android is upgrading page (as i have cleared dalvik and cache) only to reboot at the end and finally get stuck on the htc sensation splash screen again
formated system
installed the rom again with the restore option (the last of the 3 options stating to use it if you have a corrupt operating system)
reflash the kernel
install same rom without wiping
the only thing i know i can do and that ail work is going back and restore an old backup via 4EXT but i no longer have any back ups (dont ask why i did this! i thought it was working now!)
is my only option a full format?
why is this happening?
anyone know a way around it?
does this mean i can never go back to ViperS as i will always have this problem or is the problem from somewhere else??
thanks so much in advance...
i suggest to format all partitions except sdcard
flash viperS rom
see then if your issue exists
otherwise try different rom
also if you are S-ON enable smartflash from 4ext before flashing the rom
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
Hi there!
Iam having a strange problem with all sense roms viper 2.2, trickdroid, etc. and a can't fix it and i really need some help!
the sound of the phone stops working, i have the original viper kernel, never changed, the sound does not work every where!!! the mp3 player, games, notification, and the keyboard tones when dialing a number... and this time it only took about 2h after a new clean install of the rom..... ? ? ? (iam lost)
i don'd now why it appends, but when it does, i have do restore a back up that works or re install the rom.
this as happened before, and i made a clean install i have tried wipe the phone app, wipe the caches, fix permissions,.....
please does some one have a clue?
EDIT 1:
what can i do? i always used venom rom, and all ok, now since my phone came form htc support, because of the home button problem (they changed the screen, battery and the chassis, and they fixed)
now i cant use the venom i have done 3 clean install and nothing(( ..... iam going to try the TrickDroid_9.1.0 and see, if it happens again iam screed
EDIT 2:
i notice that if i clean caches and install the bulletproof kernel it stays ok, for about 5m, then the sound goes way... ?!? there must be something that is interfering with the sound services?
just found out in other foruns, that if you press volume all down, and them volume up, the sound starts working again, but some minutes later, the same no sound
http://forums.androidcentral.com/htc...d-speaker.html now iam going to remove every app and see if theres one making the problem ... it will take some time . if anyone as a clue please help!
just removed all apps , the problem precisest.... goig to try trickdroid and see what appends, does anyone have a clue!?!?!??!
EDIT 3:
i tried the stock kernel and the bulletproff, removed all apps, tried 4 clean viperone s installs with multiples recovery's, tried a factory reset from the bootloader with the original recovery, tried with the trickdoid. and nothing works!!
what can i do please some one!?
no sound, after 5m of fresh install ? tried all roms, recovery, etc
some one please help! my problem is not with this rom, it is prefect., after-all my problem is bigger .
i have tried aosp roms and sense roms, i have tried different recovery's, and kernels, removed all apps, with all i have the problem...
a minutes after a clean install the sound suddenly stops working, especially if go to the dialer
i have to install a new rom or a restore, but +/- 5m after fresh install, the problem starts again
when i relock the booloader, with a twrp backup of the original rom untouched it shows a "security warning error" ? and wallways reboots to the bootloade
don't now what else to do ?
some one please!
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
bweN diorD said:
thats defiantly not normal. you should wipe everything 100% clean and start over, also updating your recovery to the latest version. during the wipe process make sure you wipe "data-media-/sdcard" too (NOT external sd, unless you want to and have things backed up).
also, its extremely bad for the battery to let it run down to the point where it shuts off. its only a matter of time, repeatedly doing that, before you plug it in and it will not charge no matter how long you leave it on for.
Click to expand...
Click to collapse
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
SELind01 said:
Over the summer I rooted my Droid Razr HD phone and recently have been trying different roms to use and finally found one I liked (Liquid JB official). After being out late one night my phone died because it ran out of battery. Once I got home I tried plugging it in and letting it charge for awhile before turning it back on. When I finally tried turning it on my phone got stuck on the red Motorola "M" symbol. I let it sit for almost 30 min thinking it was just trying to load everything but this never changed. Is this usual for a rooted phone not to be able to turn on? It seems to me like my phone is not able to find the boot up file for the rom? Any help would be great I really would like to go back to using a different rom.
This problem has also happened to me using other roms to like Beanstalk and Eclipse and happens whether my phone dies or I shut it off or just reboot it.
Click to expand...
Click to collapse
In all likelihood, this is not a LiquidSmooth issue. I would suggest a clean install as the previous posters suggested. The latest stable version of LS is now at v2.10 for Android 4.3
LS 2.10 must be installed as follows, according to the devs:
New Flashing Instructions
wipe data/factory reset
wipe cache partition
wipe dalvik cache
format /system
Install ROM, NOT GAPPS YET!!
Reboot system, first boot may take a few minutes, don't panic ;-D
Setup your phones settings, anything that isn't Google related
or let your phone sit for 5 minutes
reboot back into recovery
wipe cache and dalvik
then flash gapps
reboot and enjoy
Click to expand...
Click to collapse
For the xt926, the download page for LS 2.10 is here: http://d-h.st/users/jsnweitzel/?fld_id=15202#files
gapps 8/13 or newer are supposed to be used with this ROM. dl from here: http://d-h.st/users/jsnweitzel/?fld_id=21058#files
The official ROM page is over at G+ https://plus.google.com/u/0/communities/117452480298315341829, if you have any additional questions.
Give it a whirl, and let us know what happens. Good luck.
SELind01 said:
When I am installing a new rom I wipe Dalvik Cache, System, Data, and Cache each three times and then I also Format Data Three times. Is this what you mean my wipe everything 100%?
Also I am currently running TWRP v2.5.0.0, I have found a newer version on twrps website but when I go into Rom Manager and check for updates my phone does not come up as a possible clockworkmod Recovery?
Click to expand...
Click to collapse
you are wiping very well, i was just confirming you wipe everything possible short of the external sd.
the wipe im talking about in twrp is wiped when you wipe "data", the one where you have to type "yes" before it will wipe. in cwm, in the formatting section (i forget what its called), there is an option that specifically says "data-media /internal sd" or something close to that.
as for the latest recoveries, here is a tool by Tucstwo that i have been updating lately http://www.mediafire.com/download/2o061zcmzlaycb5/Razr_HD_Recovery_Flasher_V8.rar
also, twrp 2.5 doesnt have all the selinux bugs worked out, you need 2.6.3.0, which is in the above utility.