[Q] bricked tmous hd2 from freezing android? - HD2 Android Q&A, Help & Troubleshooting and Genera

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.

Related

[Q] HD2 Random Reboot Issue with Android in Nand

Hello everybody,
I came from a nrg on a leo512.
I have installed MAGLDR 1.11 in order to use Android in my NAND.
But I've some random reboot from my device and most of them are when I'm standby mode when I woke up the morning the phone asks me for the pin code...
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
That's why I'm wondering If you think my HD2 NAND is clean ?
Should I make a task29 ? I heard that tools earses all the data...
All your helps are welcome !
Regards
ditto
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Sammy88 said:
It's strange when I boot I saw in first for 1-2 sec NRG bootscreen before MAGLDR...
Click to expand...
Click to collapse
This is normal.
The custom ROM you were using has flashed a custom boot screen. As MAGLDR is installed AFTER this in the chain (Boot1->Magldr->Radio & NAND), it does not alter the screen. You can actually install a custom boot screen to replace this. Check Here for some.
As for the reboots, check the sticky link in my sig. There is a FAQ in there which may offer some help.
Also try post 2 of THIS
looks promising
Cptrucker said:
I have this problem also..
Norwegian HD2..
I have tried quite a few radios.. plowing through all the available radios as we speak.. if i get a reboot i flash a new radio in hope of figuring out the problem.. the weird thing is i dont get this while using WP7... i get reboots in all other OS.. a quick fix for the SIM lock annoyance is to disable PIN code but does not fix the problem itself.. anyone have any thoughts on what this may be?
Click to expand...
Click to collapse
Update: Ended up on 2.11.50.20 and its been 20 hours since i flashed the radio.. still no reboot... looks promising, ill update if the situation changes...
Update: 2.11.50.20 was no success, 2.15.50.04 seems to be the best radio in my case.. about 60 hours between reboots has been quite consistent
lately.. i wonder what causes this. ideas and\or sollutions are recieved with gratitude. Disabled the SIM lock so its nothing to worry about but it stil gives me headache.
Although the posts above me may be right, it seems that after I disabled over clocking on my hd2, the issue was no longer present.
As always, remember what your mommy taught you; it's proper to say "please and thank you".
The solution to this problem, can be found HERE.
Esaj2 said:
The solution to this problem, can be found HERE.
Click to expand...
Click to collapse
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
viscious said:
I tried this solution, but it didn't resolve anything. I'm using mdj's cyanogen mod 2.6 with the latest radio and magdlr 1.13. I' m not using set CPU anymore. I was using it to underclock the phone and I was still getting restarts. The phone's temperature did not seem excessive either. This is a great phone but these restarts are making it almost useless. I'm at a lost here.
Click to expand...
Click to collapse
Like I said, it works for some of us. I haven't had any rebooting issues, after I turned of the automatic network selection. Some Norwegians fixed this issue, by turning of the 3G. You could try removing the sim-card and leaving the phone at sleep mode for few hours, in order to see, if your phone is still suffering from the random reboots. If so, the problem is somewhere else and I can't help you with it, because I haven't had such issues.
I resloved the issue by sending the phone back to HTC and having the mainboard replaced. Now the phone is working exactly as it should.
Sent from my HTC HD2 using XDA Premium App

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...

[Q]Is there anyway to go from HSPL3 to HSPL2.08?

Ive been trying to get my HD2 to not freeze up on me and ive read every where that HSPL2.08 is recommended. I tried searching for a guide on how but all I get is the HSPL/HSPL2 guide
Hspl is hspl2.08 its just the actual number of the hspl
Sent from my HTC HD2
ok ive tried every guide out there but nothing is working. How can I start from scratch??? I want my HD2 to go to where I just got it out from the box. I cant get it to boot, sometimes when I finally do get it to boot android I cant do anything like browse the internet or play games cause it will freeze. I think if I had just a clean start I can get everything to work again. Ive been trying to fix this problem all weekend and today is my last day off until I go back to work. Can anybody help
Just try another build of Android?
If you do want to go back to stock, what phone do you have? The T-mobile one or the European?
I have the T-Mobile one, Its so bizarre. I finally got it to go back to winmo 6.5 but it still freezes, I thought for sure if I got it back to the original OS it wouldnt freeze. Did I do something wrong when switching OS'?
In what way does it freeze?
sometimes when it does the "123 GO GO GO" also if it happens to get past the GO GO GO it will freeze on the HTC boot screen, and I guess if I do to much within android it will freeze. I cant really use any apps or else it just freezes. Like right now I was just editing stuff on the home screen and it froze
I actually have this problem with my HD2 sort of. I dug it out today after a few weeks sitting in my drawer as I thought its time had past. I don't really think there's s fix for it. Maybe restore to stock and send it to HTC for repair? I don't have warranty so I just bought a Desire Z.
Sent from my HTC Vision using XDA App
Thats weird because I had my HD2 back when MAGLDR first came out and I had Android running on nand. I think I even used MAGLDR 1.11 and installed a ZIP MIUI Android with CWM and I never had this problem. Then my screen broke and I reverted it to stock (Turns out I had no insurance) and now I want android again and I keep freezing. Point is before I went back to stock my phone was fine
Carliz89 said:
Thats weird because I had my HD2 back when MAGLDR first came out and I had Android running on nand. I think I even used MAGLDR 1.11 and installed a ZIP MIUI Android with CWM and I never had this problem. Then my screen broke and I reverted it to stock (Turns out I had no insurance) and now I want android again and I keep freezing. Point is before I went back to stock my phone was fine
Click to expand...
Click to collapse
Mate,
Have u tried flashing via cLK? using this method can show you whether there is badblock (cluster) in the NAND. I used this method and I found why I couldnt flash/boot Android anymore. Too many badblocks in the NAND. But luckily, I still can go back to WInmo and use it without problem, sofar and I am selling it now
Cheers...
is Clk the clockwork thing or the AD Recovery? Because ive tried it using a NAND and the Zip way. I think theres something wrong with my NAND or something because it was working 100% 2 months ago
AD recovery is the clockwork mod. Clk replaces the magldr. It does the same thing except its only for Android it won't boot wp7.
Sent from my HTC HD2
Im still getting a crazy amount of freezing from my phone. I cant do anything with it, or else it will freeze. Ive tried a bunch of android builds and its all the same. It even freezes on the T-Mobile Stick Together screen. How can I start from scratch Theres no point in having a smart phone if you cant use it. Its been like this for 2 weeks and its driving me CRAZY

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!

[Q] HD2 randomly crashing, may bricked?

Hi
So I've tried several things the past days and nothing seem to work properly.
I found several threads with same topic, however this is really random crashing.
My EU HD2 is pretty much unusable:
- Sometimes it won't boot, just vibrates constantly 5 times or so
- Loads into MAGLDR, but gets FATAL HIT when attempting to boot.
- Crashes randomly when used, either android or wp7.
I first experienced these issued with NAND android, using skinks clean desire v1.2
Then i reformatted, using task29, installed MAGLDR again, and then wp7 nodo (stable). But the issues kept on going, and now I'm not really sure if it boots. The battery pins look okay to me, and i have tried several different batteries.
Anyone experienced this before, is it gone or is it possible to fix?
all help greatly appreciated!!
rubikum said:
Hi
So I've tried several things the past days and nothing seem to work properly.
I found several threads with same topic, however this is really random crashing.
My EU HD2 is pretty much unusable:
- Sometimes it won't boot, just vibrates constantly 5 times or so
- Loads into MAGLDR, but gets FATAL HIT when attempting to boot.
- Crashes randomly when used, either android or wp7.
I first experienced these issued with NAND android, using skinks clean desire v1.2
Then i reformatted, using task29, installed MAGLDR again, and then wp7 nodo (stable). But the issues kept on going, and now I'm not really sure if it boots. The battery pins look okay to me, and i have tried several different batteries.
Anyone experienced this before, is it gone or is it possible to fix?
all help greatly appreciated!!
Click to expand...
Click to collapse
main board is fubar. Warranty or sell for parts
Too bad, guess ill have it in on warranty then.
Thanks for quick answer!
rubikum said:
Too bad, guess ill have it in on warranty then.
Thanks for quick answer!
Click to expand...
Click to collapse
np, make sure you flash stock via SD card before you send in for warranty.
SD card flash didn't work for me so I flashed stock rom and then reset spl.
Phone won't boot now anyway so..
rubikum said:
SD card flash didn't work for me so I flashed stock rom and then reset spl.
Phone won't boot now anyway so..
Click to expand...
Click to collapse
I would try the fridge flash from SD just to be sure.
Guess ill try once more then
Does the card need to be formatted in order to do so?
When I tried last time i just put the leoimg.nbh onto are the card but nothing happened.
rubikum said:
Guess ill try once more then
Does the card need to be formatted in order to do so?
When I tried last time i just put the leoimg.nbh onto are the card but nothing happened.
Click to expand...
Click to collapse
Format fat32 and make sure the card.is 8gb or less. Also make sure the file is called leoimg.nbh
Sent from my HTC HD2 using XDA App
Maybe you have bad blocks
orangekid said:
main board is fubar. Warranty or sell for parts
Click to expand...
Click to collapse
what is fubar?
im sorry my english isn't good
khaled1994 said:
what is fubar?
im sorry my english isn't good
Click to expand...
Click to collapse
Fubar means F'ed Up
Serious_Beans said:
Maybe you have bad blocks
Click to expand...
Click to collapse
I think you should stop pointing random problems on bad blocks.
I understand that these are the symptoms observed by people with high number of bad blocks, but i'm running sense 3 roms with 8 bad blocks and no problem/random freeze/reboots till now.
Also, this guy is not running android/WP7 which are believed to be unable to manage bad blocks (assuming as he posts in HD2 General).
most probably hardware problem. i've had bad experience about this too. send it for warranty at the end

Categories

Resources