I was trying to install RunnyDroid on my Desire S (Where I have BeatMod BlissSense before. I wanted to try a ROM that seems to have better battery time), the installation seems to go well (I do the Wipe of system, data and cache), but when the device is rebooting it hangs itself on HTC Logo Screen. Is there something I am missing or doing wrongly? I went back to BeatMod for the time being
Cheers Anders
Related
Hello,
usually it always was fast, but recently i tried install super-d rom and android wont boot (freez on first boot picture). then i wiped everything (all 3 first sections under wipe options) and tried restore my nand backup.
and second time i try and it takes for ever (dots running and running nonstop for hour+).
any suggestions? it happened second time now...no luck...
re-wiped, booted super-fast rom and magic just works...going to try restore my old backup again...
rommark said:
re-wiped, booted super-fast rom and magic just works...going to try restore my old backup again...
Click to expand...
Click to collapse
got that one one time too.. checking logcat showed that the nandroid-script died efter some seconds but the dots kept comming.
For me It was caused by me not wiping when switching radio/spl.
Had to do it immediatly after radio/spl/rec, not in the newly flashed recovery afterwards
Hi!
I upgraded from Cyanogenmod7 to CM 7.01 using ROM Manager premium on my HTC Desire (GSM).
It asked me which cache's to clear, and I let it go with the default it suggested. The Dalvik cache
After the upgrade the phone booted fine, but where I usually have around 20Mb free on the phone, it was running very low at only 1.34Mb free on the phone.
I tried to clear the app cache, but that didn't help as there was no cache used.
So I tried to reboot the phone, and now it just hangs at the animation with the blue cyanogen android and won't start . I tried removing the SD card, but it still hangs.
Where do I go from here?
It's all sorted now.
I held down the volumekey while turning it on, and in the boot menu I found an option to do a 'factory reset'.
Thanks to Titanium Back it was all a question of restoring my apps, and I know have my phone looking and working exactly as it did before!
Delete.
I have the same problem except that if i were restarting, it had been continuing the same boot loop.
Meh, back to insert coin 2.2.5
mandroid25 said:
I've installed the Revolution 3.5.2 ROM for my phone (upgrade to 3.6.0 possible, but experienced the problem also with previous versions):
http://forum.xda-developers.com/showthread.php?t=1098849
My problem is, after charging the phone for some hours (usually in docking station) or after using the phone for an hour or so, my phone suddenly crashed in a boot animation loop (meaning HTC logo), freezes - nothing happens anymore. I need to remove the battery and put it back in, can continue using my phone afterwards.
As I'm quite new to Android development (not even allowed to post in forums there), I'm interested what's causing it (too much CPU adjustments) and how can I fix my problem. (Actually I suppose there might be the solution somewhere here, but I couldn't find it - so even a link to a solution might help me).
Click to expand...
Click to collapse
Hi,
The most common cause of bootloops and freezes are incompatible mods.
Have you installed anything other than the ROM?
Did you wipe data,cache partition and dalvik before ROM installation?
Did you reinsatall titanium backup "SYSTEM" data?
More info needed,please
I am also having the same problem. Random reboots, but just hanging at the bootscreen.
It happens very often if i am running Gameboid (a gameboy emulator).
I still have ARHD 3.0.1 with Thyparency Theme.
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.
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