Database Users

[Q] Android worked fine now has stopped

Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?

TommyHD2 said:
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
Click to expand...
Click to collapse
I am getting same issue. Android was very nice, fast boot and so on. But since tomorrow, when booting to Android it stays on startup screen with green htc.

TommyHD2 said:
Have had Android working and booting fine for the week, battery went flat last night , now android wont boot, goes to the grnn HTC icon n then stops, I have waited half an hour still with nothing, as ive said its not the first time its been booted. I have searched on here but they all seem to be new installs that are having problems. Any idea ?
Click to expand...
Click to collapse
Sounds like possible data corruption if system did not shutoff gracefully. Not a good idea to let low battery shut off system... you should shut it off manually. I have had this happen on WM where the phone get into a weird state and data get corrupted.
I would backup the data.img file, let Android create a new one to see if it boots properly. Then restore the original data.img file and see if it boots with that one.

hidnface said:
I am getting same issue. Android was very nice, fast boot and so on. But since tomorrow, when booting to Android it stays on startup screen with green htc.
Click to expand...
Click to collapse
Which build are you using?

Same Here!
Battery went flat, tried booting android a few times but didnt succeed. So rebooted the phone to find..
The android boot screen repeats itself. Over and over. Was fine yesterday.
Going to try backing up the data.img and restoring it after it rebuilds as mentioned above.
UPDATE :
After backing up the data.img file, and letting it rebuild, one hour later, still not booted.. So restarted the phone, put the old data.img back, started up haret.exe, and its now stuck on the Green HTC logo.. and isnt moving.. at all.
This isnt my first boot.. usually it boots within a couple of minutes.

jmmmmm said:
Which build are you using?
Click to expand...
Click to collapse
Latest Android build. FroyoStone version3.2

Android not rebooting after flat battery
Hi TommyHD2,
I have just had the same problem, actually a couple of times. What I did was to delete all the new entries that had been made on my micro SD card and only leaving the original 8 files that are in the FroyoStone 3.2.7z Android folder and of course I did not delete the media folder that is also included in the build. Well twice now I have done this with a successful reboot of Android whilst not losing any of the settings that I had made ie. Wallpaper, shortcuts etc even apps (unless they are on the card).....Obviously this will now be a case of trial and error to establish which of the deleted files it is that cause a conflict in the reboot. I am also new to this but reading this someone may be able to idntify the problem easily. Other than that it runs superb....EVERYTHING works....well battery drain but I think that is even solved now thanks to XDA.....I will let you know in about four hours
Good luck
HTC HD2
Radio - 2.15.50
FroyoStone 3.2.7z

scirroco said:
................
FroyoStone 3.2.7z
Click to expand...
Click to collapse
.7z is the file extension (like .rar, .zip, .doc) and not the version.

Froyostone version confusion
HI Hidnface,
I don't know what sort of smile that is ....sarcastic or friendly but thanks all the same. Bit dumb of me but then I am still learning.
By the way I found that when you boot into Anroid you are left with a folder calle Android_Secure....I dont know what thois does but this is the one I delete to enable successful reboot.
Thanks mate.

have you guys tryed doing a logcat of it booting? whats it erroring at? is it looping?
search adb logcat. android is verry easy to debug since you can watch processes in a comand line...

[Q] bricked tmous hd2 from freezing android?

hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!

lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse
Please mention your RADIO, HSPL and the last Android Rom in which this happened!

If your phone is booting, it's not bricked. Did you try another SD card? Have you tried doing a low level format on your SD card? If it were me I'd Format the SD card with an adapter on my PC, low level. Then I would put it back in the phone then run Task29. Then flash MAGLDR 1.1. Then Flash the CMY 1.4n Desire HD Nand build in the HD2 Nand Android Development forum. It's the most stable Nand build up there right now.
I would use the 2.15 radio that comes with the newest Tmobile ROM. You might have to download the 3.14 ROM from Tmobile and flash it first to get the Radio in there. Then Task29 after that. MAGLDR, Then the NAND build. Make sure you find the Task29.exe that doesn't have a radio paired with it. it's on this site somewhere.
lewy255 said:
hi all, long time viewer first time poster, i have been reading many post on the net trying to find a definite answer on my tmous hd2 but with no luck. My problem started when i was running android (sandisk mirco sd, yes i know the incompatibility issues, it came with the phone). I was playing music through headphones while charging and suddenly the phone froze with a buzzing sound until i battery flipped, first thing it did when i started it back up again is vibrate approximately 5 times at boot flash screen (indicating excessive heat?), so i battery flipped again and waited 10 mins then i tried to start again and it just froze at boot screen, it would keep doing this and every now and then it will boot to wm, but sooner or later it will freeze in wm and then have booting problems, its still doing this today after doing all the following: 1.flash another custom rom. 2.flashed another radio. 3.task 29. 4. flashed stock rom & radio. 5. flashed nandroid 6.tried different capacity and brand sd cards & none at all.
I now have a hd7 because I couldnt fix it and didnt want to shed the cash they are still asking for a hd2, but i do want to fix the phone to play around more with it, i did look at the possible solution unbrick with jtag thread but im thinking the phone is perma bricked, when it was working it has had alot of custom rom flashes so i dont know if that makes much a difference but i would greatly appreciate some advice, THANKYOU XDA FOR ALL YOUR HELP!
Click to expand...
Click to collapse

hd2 running MIUI freezing up too
I'm a complete noob here so bare with me. I'm currently experiencing the same probs as lewy255 with the hd2 freezing up. It happens every now and then when I'm accessing certain apps. When the hd2 does freeze up, i have to take the battery out, wait, then boot up again. Once it tries to boot up it freezes on magldr, then i got to take out the battery again, wait, then power it on again. It seemed to happen when i first rooted my hd2. The first ROM i flashed after rooting was typhoon CM7. Currently have:
HSPL 2.08
radio 2.15.50.14
MIUI version: 1.5.27
I hope this isnt a hardware issue cause i bought this phone from one of my friends and he didn't have the receipt. Please advise on what i can do to fix this freezing issue.
Thanks

Sounds like cpu overheat freeze. When you were playing music and charging it the first time it froze, was the phone and/or battery hot?
It's very possible that it got too hot once, and now the cpu its self gets too hot much easier now that it has already happened once.
Sent from my HTC HD2 using XDA App

Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App

germotlp said:
Cpu overheat freeze? So its a hardware issue? What if I ran task29, and reinstalled magldr, clockworkMod, and then MIUI, do u think that would fix the freezing issue?
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.

T-Macgnolia said:
No I do not think that will help your situation. I think your HD2 is starting to show signs of hardware break down. More specifically a breakdown in the connection of the processor and the main board. The only permanent if this is the case is to replace the main board.
Click to expand...
Click to collapse
t-mac
I tried installing setCPU and adjusted the temperature setting so if got too hot then the speed of the phone would be reduced, but still no luck.
What if i unrooted the phone and put everything back to stock? I think that way i will know for sure that its a hardware issue. I dont know much about phones but your probably right. I'll try running task29 and reinstall everything and see if that works, if not then i will un-root and put everything back to stock and test.

Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.

Kailkti said:
Is it an undervolted kernel? Might cause problems, but I'm with mac here on it being a hardware problem, since you flashed back to winmo stock and you still had problems.
Click to expand...
Click to collapse
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App

i have same problem with miui roms. I think this problem is about Miui Roms. Miui developers must solve this issue, there is no way..
When i try other Roms, there is no problem like this issue..

germotlp said:
I'm a newbie here. Not sure what u mean by undervolted kernel. Could u explain to me? Btw I have not flashed back to winMo yet.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
in my opinion and its just my opinion, but you should flash a winmo 6.5 build than boot android from sd its safer because theres no need to worry about battery dying in magldr. and if theres a nand rom you want to try out i suggest using port a droid. im using now with the new nexus 2.8 with a 1gb data.img and it runs great plus i have 3 other builds on there also.

many issues after dead battery on nand droid

the phone is freezing often
slow touch responce
programs force closing
yahoo mail doesnt work anymore
its shutting down on its own randomly
and some other problems i cant remember.
its a nand CMYLXGO stock desire HD v1.1.3
is this a common problem, if so where can i find info aout it i searched for dead battery and didnt show much.

Maybe some data got corrupted. So you should reflash or flash another build. Maybe even your radio to be sure.

why does it happen? i thought we wouldnt have this problem with nand builds.

fuzzysig said:
why does it happen? i thought we wouldnt have this problem with nand builds.
Click to expand...
Click to collapse
well, lot of roms use the data2sd method for storing data on SD, for me its pure nonsense (app2sd is fine). With data2sd the risk is very high that you get data corruption and then all the weird force close madness begins. Now if you run out of battery your device doesnt shut down properly/cleanly, its the same as you would just pull a cable to shut down a pc. So running out of battery is the same as pulling the battery.

wow
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off

kiki_tt said:
I'm using CMYLXGO's BlueTopia (NAND) and the battery widget got to 0% i think... i was worried since charging MADGLR 1.3 requires me to activate the screen / turn on the phone....luckily it did the GO GO GO thing and started to boot .... i plugged in the charger and now all is well.... lucky me I guess...
PS .. I guess the battery widget is a showing a percentage or two off
Click to expand...
Click to collapse
That's what it does for everybody.

the phone also started to have SOD.
i plug it in at night to charge, in the morning it would not wake up.
the alarm would go off but the screen is blank.

now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?

fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Been there. The only solution that worked for was to flash it from scratch once again.
Dunno why the phone is acting this way but now I always charge or turn off my phone when my battery is down on 10 %. Better to be safe than sorry.
I'm using MDJ's CM7 v. 2.6 so I think this is an issue on many builds if not on everyone.

fuzzysig said:
now the phone just freezes randomly.
can anyone suggest any fix or troublehsooting tips.
yes im well aware that i can reinstall it again but id like to try and find the problem first before wiping it all clean AGAIN.
why would a dead battery cause this on a custom build and not on a factory installed rom?
Click to expand...
Click to collapse
Since u are aware u can reinstall it again then simply do so...Yeah its a real pain but just tk time out n do it...I've been using CMY's builds for so long and have never encountered such an issue..but dats just me...
i see u r still using V 1.1.3, CMY has released a much more better build (but then u already know that), so go download dat...perform a Task 29 ,install MAGLDR ( u know d works) etc...
As 4 y a dead battery will cause this on a custom build and not on a factory installed ROM? ...Me thinks u already know d answer (stick 2 stock WinMo if u think its better)..
P.S. Remember charging ur battery to 100% b4 starting..gives u a fairly calibrated battery.

you could also try to wipe the battery information via magldr?
you choose recovery in magldr > clockworkmod recovery > advanced > wipe battery stats.

tried that didnt work
isnt there another way besides reinstalling everything over and over?

wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?

fuzzysig said:
wow i mean we went so far as to have it working on the phone but nobody knows why a dead battery causes corrupted system on a custom rom but not on the original?
Click to expand...
Click to collapse
?! it has been answered in this thread...

sense rebooting, slow ROM

everytime i go back to mainscreen, htc sense keeps rebooting. i dont know why! its so annoying! have to wait 1-3 minutes for it to reboot sense.
i have the incredible rom, and would like to upgrade it to 1.1 but dont know how to set CMW to 130mb insted of 150mb as its today.
flashing rom used to be easier before - now its CWM, cyan, partitioning and so on. im not against it, but developers are skipping the installations guide as they hade befor. they all assuming that everyone knows to work with CWM and so on.

plus, the battery drain is *#¤!% high! just charged it too 100%, then 3-4 hr later, with low usage, its on 30%!
is the sense rebooting taking all that battery? but it drains battery even on idle.
how to fix?

loni90 said:
everytime i go back to mainscreen, htc sense keeps rebooting. i dont know why! its so annoying! have to wait 1-3 minutes for it to reboot sense.
i have the incredible rom, and would like to upgrade it to 1.1 but dont know how to set CMW to 130mb insted of 150mb as its today.
flashing rom used to be easier before - now its CWM, cyan, partitioning and so on. im not against it, but developers are skipping the installations guide as they hade befor. they all assuming that everyone knows to work with CWM and so on.
Click to expand...
Click to collapse
hi.
Go to:
http://forum.xda-developers.com/showthread.php?t=898913
Thats probably the best explanation you will get.
Flashed from my fingers to your face

Just flash the Rom again and see if it works....
If it doesn't then you got to reflash cwm with 130 partition...
Sent from my HTC HD2 using XDA App

Girlfriends kills android roms everytime!

Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)

joostnl said:
Dear xda users,
My Girlfriend got a HD2 and I installed Android on it.
She used SD versions but she kills them everytime.
After a month the phone got stock on boot screen.
Then i tried to install NAND Roms but after 2 months of smooth running the same problem again... (example: Coredroid, and sense roms)
I think that the problem is that when the phone freeze she pull the battery out and after a few times the phone won't boot anymore.
Followed all the noob friendly guides.
Followed all the instructions in the post of every rom.
Installed the recommed radio, MAGDLR, CMW, data partions that were in the instructions
Common problem on sense roms?
Should i try to install no sense rom?
(Got experience with Desire HD flashing and Touch pro 2)
Click to expand...
Click to collapse
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.

Buy her an iphone, then she can't pull the battery! :-D
Sent from my HD2 using XDA App

malybru said:
Hi,
It could be that with all the battery pulling, that the pins could be bent.
Make sure they are all straight.
Click to expand...
Click to collapse
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)

Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again

lol, hahaha

joostnl said:
I don't think it's hardware related.. Because i can boot in the MAGLDR without any problems.. But when i wan't to boot android it hangs on the coredroid boot logo
(This happends with all roms (sense) i tried so far)
Click to expand...
Click to collapse
ive seen a few posts where people have struggled with getting past boot logo, think it was fine after using a different partition in recovery but as your device is for the sd build am not quite sure how that works as Ive never had sd android or if having sd requires clockwork mod recovery? if so try different partition as i said earlier if not hang on till someone has the answer
johnerz said:
Boot into magldr and re run the rom from there,cleare the caches firsr ot course
Then glue the battery in - buy a tazer and promise her a double dose if she pulls the battery again
Click to expand...
Click to collapse
haha great answer, my girlfriend doesn't touch my hd2 or she gets alot more than a double dose with the tazer method, HD2 is not the solution for a women... you take the hd2 of her and buy her a iphone surly they are women material.

Ignore Post

Problems almost always occur after a few weeks or months of use for me, just reflash the ROM, and you'll good to go.
removing the battery is not recommended, it can corrupt files on the sd-card. Try to boot without sd-card and see if it helps. If your ROM does boot, it means the SD card is corrupted, you can try to backup the SD card and restore it after completely wiping the sd-card.
If your rom doesn't boot, than it meant there's something else going on, maybe corrupted flash, so reflash and try again. This will delete all your data, so be careful

if your girlfriend is not an daily flasher also might i suggest using a daf build. All the configuration is done for you. if you are using a sd build from magldr than make sure you change the name of the build than edit the startup txt like this "rel_path=whatever you name the build(example: "rel_path=MIUIROM nand_boot=1") the 1 for magldr 0 for windows 6.5. the reason for me saying this is all android builds create a folder android when they boot up with all your info like data and cache is in there. So its best to separate the two just in case you want to boot up more than two builds from sd.

Same here.
could be a bad block in your NAND memory. you can check this with cLK and fastboot.
see this post: http://forum.xda-developers.com/showpost.php?p=13600733&postcount=9
i checked mine and there was a bad block in the userdata. i think that is wy my phone was freezing.
now i have flashed cLK and untill now its working great!