Related
Ok, so I tried to flash my G4 wizard to wm6, went all the way through the flash, got to 99% and stopped, giving me a comm error. I did the recovery and im in an endless flash to 99% loop. When I turn it on, I get the bootloader (3 stripe) screen, with the following:
RUU upper right corner
IPL 2.25.0001
SPL 2.25.0001
USB lower left corner.
I have spent the last 4 hours reading posts and cannot fix this thing. Any help would be greatly appreciated.
did u flash it back to carrier rom?
Flash it back to the original carrier ROM (should be available on the website) and then use ShellTool to flash the ROM. make sure that you follow the instructions exactly, otherwise, you will end up with a bricked rom.
-Nstefanelli-
The only rom I can find on Cingular's web site, once downloaded says its corupted, and I cant find one on XDA at all. Anybody know where else I might find one?
Wizard Love rom is another one you could try.
Wizard Love got me goin again, I love me some wizard.
Thanks for the help guys!!!
Same Problem I Have Faced.... And Also Solved.
u have Radio Rom problem....
search the latest radio rom and upload to your rom... and restart your pda...
reply me..... sooon because same problem i had faced and solved also.
Same problem
I was having the same problem yesterday. Eventually i got it to work again. It was a little confusing though because i used the rom from the HTC website to get it up and running again with wm5 and then used ShellTool from the sticky in this forum to flash it with a wm6 rom. From what i gather it's because my phone was CID locked, something that none of the roms include in their instructions to watch out for. Maybe a sticky in the forum for newbs like me containing things to watch out for while flashing roms?
A side note:
I had to download the rom from the HTC site twice in order for it to flash back to the original OS. The first time i downloaded the rom i kept getting an error. I guess it was a bad download or something but the second one worked in the first shot.
think i bricked my wizard
oops !!!!
think i flashed a g3 rom onto my g4 wizard and for a while it stayed in bootloader screen (tricolour) now the wizard is dead with no charging light when plugged in and performing hard reset does nothing
please help !!!!!!!!!!!!!!!!!!!!!!
gripper said:
oops !!!!
think i flashed a g3 rom onto my g4 wizard and for a while it stayed in bootloader screen (tricolour) now the wizard is dead with no charging light when plugged in and performing hard reset does nothing
please help !!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
There is no help for you if you did flash a non-official G3 rom onto your phone.
Recent Official carrier releases are the only roms that contain bootloaders that are safe to flash into a G4. (Note older carrier releases could possibly fry your phone as well as they may not contain G4 bootloaders)
If you flashed a custom rom with IPL/SPL your device is done for good.
Though you said it went to the bootloader prior to going dark so you may just have a dead battery and a bad flash. Get a battery from a friend or buy one and then see if the device will power on. If you can't get it to power on with a known good battery then it is most likely fried. If it does boot at least to bootloader then you should be able to recover your device. Most chargers will not charge the battery of your phone unless the phone is fully booted into windows. So it is very important to have a contingency plan in case of a bad flash with these phones as playing/troubleshooting while trying to recover from a bad flash will drain your battery possibly leaving you with not enough juice to complete a flash.
hi zzan
thanks for the reply, i think your right about the battery it actually turns on for about 10 seconds now into bootloader but then the battery dies again so i gonna source a battery.
gripper said:
oops !!!!
think i flashed a g3 rom onto my g4 wizard and for a while it stayed in bootloader screen (tricolour) now the wizard is dead with no charging light when plugged in and performing hard reset does nothing
please help !!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Remove the battery for about 5 minutes, then put it back in.. then try booting in bootloader mode <tri color screen> .. then flash with an OFFICIAL Carrier ROM ..
I flashed my hermes yesterday <changing the spl and stuff> and it was dead for a little bit, until I took the battery out and put it back in.. <for some reason it was like a de-fibrilator..>
Try that.
hi madcap,
not looking good i toook it to a phone engineer and he says it is corrupt ? he has tried flashing it, apparently there is a guy who will put in a new chip ? i am such a fool i bricked my phone just to get rid of o2 stuff !!!!!
gripper said:
hi madcap,
not looking good i toook it to a phone engineer and he says it is corrupt ? he has tried flashing it, apparently there is a guy who will put in a new chip ? i am such a fool i bricked my phone just to get rid of o2 stuff !!!!!
Click to expand...
Click to collapse
A new chip?!?!??
The problem is the in the IPL area which can now be flashed only via JTAG (cable system that doesn't require booting files since it operates directly on the chip)
Take it to an official repair.
Hi,
I have almost the same problem. I tried to flash to WM6.1 for wizzard, it got to 99% and failed (connection lost). I then tried the recovery process but that didnt work.
Now I can boot to the booloader, and see the IPL/SPL versions (2.25.0001) and can see USB on the lower left. But , it is not making a connection to my PC. None of the RUU, ROMS, HardSPL, or SoftSPL apps can connect to it.
They all report some connection error, "Device not found", or "Connection Error 264"...
I have read a bunch on this forum, and tried alot of stuff but nothing worked.
I started up my own thread on my issue, but hope someone could help me, help someone else in the process here..
How can I get this thing flashable again?
Thanks
Madcap180 said:
Remove the battery for about 5 minutes, then put it back in.. then try booting in bootloader mode <tri color screen> .. then flash with an OFFICIAL Carrier ROM ..
I flashed my hermes yesterday <changing the spl and stuff> and it was dead for a little bit, until I took the battery out and put it back in.. <for some reason it was like a de-fibrilator..>
Try that.
Click to expand...
Click to collapse
This worked for me and now I can connect the apps to the phone again. But after I try to install the default rom, everytime at 80% it looses the connection again.. .
Anyone know a good WM6.1 rom that works with 8125 G4
end123 said:
This worked for me and now I can connect the apps to the phone again. But after I try to install the default rom, everytime at 80% it looses the connection again.. .
Anyone know a good WM6.1 rom that works with 8125 G4
Click to expand...
Click to collapse
Fully recharge your battery, then try to flash again. Low/dead/misreporting battery will kill a flash as surely as disconnecting the cable in mid-flash. Oh, and try WizFlo...really cool! (I had to fiddle with the Opera Browser install to get the Internet connection to work correctly, but who cares, it was worth it!)
i just bought my hd2 fromt-mobile and naturally couldn't resist but to modify it
So i installed and flashed the HSPL2 with no problem it worked perfect and very fast and easy....and i installed Mesus Rom and love it did my registry tweeks got the phone running awesome!!!
Now i woke up early was browsing on htcpedia and glanced at the new DOPOD version radio.... well..... it installed fine no errors but when it got to 100% to reboot BLACK SCREEN. I've tried getting the phone into bootloader mode nothing, tried a master reset holding down the volume up and down at the sometime and press power nothing, i've tried to plug it in the computer it recognizes it my computer makes the connected to a device noise but when it goes to initialize the hd2 i get this driver error:
Qualcomm CDMA Technologies MSM failed.
i've also read once u have hspl or hspl2 installed it can not be bricked can someone please help me on some step by step and some links
the radio i flashed that caused this was 2.051.03(DOPOD)
poulosjr said:
i've also read once u have hspl or hspl2 installed it can not be bricked can someone please help me on some step by step and some links
Click to expand...
Click to collapse
I hope so for your sake, however... When you say you have a HD2(T-Mobile), do you mean the US one?
Flashing guide for TMOUS HD2 states:
mskip said:
PLEASE READ ALL THE INFORMATION IN THIS GUIDE BEFORE INSTALLING HARDSPL OR FLASHING A ROM/RADIO. IF YOU FLASH AN INCOMPATABLE ROM OR RADIO ON THE 1024LEO THEN THERE IS A POSSIBILITY OF BRICKING YOUR DEVICE SO PLEASE BE VERY CAREFUL!!
Click to expand...
Click to collapse
poulosjr said:
the radio i flashed that caused this was 2.051.03(DOPOD)
Click to expand...
Click to collapse
Is that this one (2.09.51.03)?
Says in the post there it doesn't support 576MB RAM. That would probably mean it's not compatible with the TMOUS HD2. I vaguely remember that being the case for any version with 51 in it.
Sorry to be completely unhelpful here, but I wouldn't have a clue on how to revive your HD2.
Perhaps people in the TMOUS HD2 Flashing guide thread might know something?
----
meptik
chalk another non-starter up to a ..51.. radio on a tmous phone.
still not seen a fix
is the tmobile us hd2 recoverable or is it bricked out?
sorry, not sure. see other threads HERE (post three) and HERE , , it's also mentioned in the mtty and the HSPL (regular HSPL and tmous HSPL) threads.
As far as i can gather so far, roms below 2.10 cause not to boot, but can recover from bootloader, radios with a ..51.. in them cause it not to start at all. (because ..51.. radios don't support the 576mb, presumeably)
Best of luck.
I am having the same problem...I can boot in to bootloader mode and in to restore mode but there is no display on the screen the computer detects it and everything and I can flash the phone, but nothing ever comes up not the tmobile screen or anything...I had this problem when I first got the phone only the backlight would come on, but I took the battery out for a few minutes and then it worked fine until the battery died then the problems started again, then I flashed it with the with the latest tmobile us official rom I could find and it worked until I turned it off and then I could not get it to turn on again. I somehow through some voodoo or something after trying the restore feature like 20 times got it to come on, the I had to take the battery out to put in the sim card and now nothing...The thing I can't understand is why windows recongizes the phone and I can flash it but nothing changes nothing just a blank screen with the backlight on I can attach to it with mtty and everything I ran a task 28 and task 29 and reflashed it nothing I have tried cooked roms and everything still no display...Someone please help...I plan on returning it for a new one except there are none in my entire state, I have called every tmobile store in the phone book and none know when they will get more in...
brandon2004 said:
I am having the same problem...I can boot in to bootloader mode and in to restore mode but there is no display on the screen the computer detects it and everything and I can flash the phone, but nothing ever comes up not the tmobile screen or anything...I had this problem when I first got the phone only the backlight would come on, but I took the battery out for a few minutes and then it worked fine until the battery died then the problems started again, then I flashed it with the with the latest tmobile us official rom I could find and it worked until I turned it off and then I could not get it to turn on again. I somehow through some voodoo or something after trying the restore feature like 20 times got it to come on, the I had to take the battery out to put in the sim card and now nothing...The thing I can't understand is why windows recongizes the phone and I can flash it but nothing changes nothing just a blank screen with the backlight on I can attach to it with mtty and everything I ran a task 28 and task 29 and reflashed it nothing I have tried cooked roms and everything still no display...Someone please help...I plan on returning it for a new one except there are none in my entire state, I have called every tmobile store in the phone book and none know when they will get more in...
Click to expand...
Click to collapse
sounds more like a dodgy phone than a bad flash. wait for stock and get it exchanged.
bricked
I have the same problem. I just wanted to go back to stock rom and i downloaded this bull crap rom
RUU_Leo_HTC_WWE_1.43.405.1_Radio_Signed_15.26.50.07U_2.04.50_22_2_Ship.exe
BRICKED MY TMOBILE USA HD2!!! DO NOT LOAD THIS ROM!!!!
took it to the tmobile and i now have to wait till tomorrow for them to get more in stock... im pissed!!!
sk8er982 said:
im pissed!!!
Click to expand...
Click to collapse
i really hope you mean pissed at yourself, that rom is about as far away from compatible as they get for the tmous.
Cannot believe we don't have a sticky warning about xx.51.xx radios and TMOUS HD2s yet!
i am...
samsamuel said:
i really hope you mean pissed at yourself, that rom is about as far away from compatible as they get for the tmous.
Click to expand...
Click to collapse
i am pissed at myself. anyway i got a new phone now.
how do i go back to original firmware if i flash a cooked rom?
they need to remove the .51 versions, i just bricked mine and all i saw really was to not install it, not that it would completely brick it. I'm really upset.
donalgodon said:
Cannot believe we don't have a sticky warning about xx.51.xx radios and TMOUS HD2s yet!
Click to expand...
Click to collapse
I hope that was sarcasm LOL
sk8er982 said:
i am pissed at myself. anyway i got a new phone now.
how do i go back to original firmware if i flash a cooked rom?
Click to expand...
Click to collapse
That info is still in the same thread that y'all should have read before bricking your HD2's. Many (and I mean many) of us flash our HD2's all the time, run ROM's custom built to even let us run the latest and greatest Android builds available.
When you and the OP (iirc) get some fresh HD2's, read the info and links in the stickies here. There's enough info in those to get you well on your way to mastering your HD2's destiny.
Best of luck.
So true. ALL chefs always warn ab NOT flashing .51 radios on TMOUS HD2 or they posting links to HOW TO FLASH TMOUS HD2.
Dont rush with first flashing! Thats the best way to brick ur phone!
Always read the forum! Thats the bast way to make ur phone happy
htc hd2 after installing andriod
hey everybody.... I have a big problem with my phone which is when the fixer tried to install android on it it become freezing (black screen and just vibert)
so he told me that he has no idea and my phone will not fix ...so please help me out..
sherko_bax said:
hey everybody.... I have a big problem with my phone which is when the fixer tried to install android on it it become freezing (black screen and just vibert)
so he told me that he has no idea and my phone will not fix ...so please help me out..
Click to expand...
Click to collapse
it is tmous yes? it sounds like he flashed a bad radio,
If that is the case, i would be MAD AS HELL and demand they pay for the replacement of teh motherboard.
Yesterday i put my hd2 in my pocket without locking the screen. when i heard it surfing around the menues i took it back up and tried to take it back to homescreen. As many times before the phone refused to respond so i took out the battery. But when powering it back on the **** wont pass the htc startup-screen!
I have read around this forum quite alot now and i have done hard reset a million times, i have installed an original updated rom from htc`s site. When this didn`t work i installed hspl3, Artemis v270 NOR and RADIO_2.07.51.22_2. And it still wont start!
Im getting quite sick of experimenting, so i`d be really happy if any of you smartguys could help me
Pelle-pirk said:
Yesterday i put my hd2 in my pocket without locking the screen. when i heard it surfing around the menues i took it back up and tried to take it back to homescreen. As many times before the phone refused to respond so i took out the battery. But when powering it back on the **** wont pass the htc startup-screen!
I have read around this forum quite alot now and i have done hard reset a million times, i have installed an original updated rom from htc`s site. When this didn`t work i installed hspl3, Artemis v270 NOR and RADIO_2.07.51.22_2. And it still wont start!
Im getting quite sick of experimenting, so i`d be really happy if any of you smartguys could help me
Click to expand...
Click to collapse
Flash a radio that does not have ".51" in the name. Flash a radio that has ".50" instead. ***Make sure the ".50" radio is 2.06+ (don't flash anything below 2.06.50.xx).
Okay, thanks for your reply But i still cant make it work, are you sure its the radio causing this problem? I`ve now tried RADIO_2.10.50.28_2 (this is the only one with "50" in it among the recomended radios in the artemis thread...) , RADIO_2.12.50.02_2 and the mentioned above RADIO_2.07.51.22_2.7z.
Should i just keep going?
One more thing. When 2.12 and 2.10 was installed, the phone restarted by its self after about 30-60 sec on htc bootscreen. if that means anything?
Pelle-pirk said:
Okay, thanks for your reply But i still cant make it work, are you sure its the radio causing this problem? I`ve now tried RADIO_2.10.50.28_2 (this is the only one with "50" in it among the recomended radios in the artemis thread...) , RADIO_2.12.50.02_2 and the mentioned above RADIO_2.07.51.22_2.7z.
Should i just keep going?
One more thing. When 2.12 and 2.10 was installed, the phone restarted by its self after about 30-60 sec on htc bootscreen. if that means anything?
Click to expand...
Click to collapse
It's usually the radio that's the problem -- if your phone gets stuck on the bootscreen.
I'm not sure what else might be the problem.
Just in case, try this: Task 29, flash a .50 radio, flash a stock ROM (via USB), hard-reset.
If that fails, I don't know what else to say...
i tried the task 29 witout luck A couple more weird things though.. when i try to install a rom from the memory card, the bootloader doesn`t start the installation. I just says "serial". And Yes its formated with fat32 and im sure im doing it right. The other thing is that the phone starts by itself about 60sec after plugging in the charger.. i`m guessing this have to be a hardware problem. might be the usb connector as many seem to have problems with.
I`ve now put in a stock spl and will send it back for repair tomorrow.
Dammit, hspl i still there. Is the only way to remvoe it by using the sd-card? then i might be fu..ed regarding the warranty :S
Pelle-pirk said:
Dammit, hspl i still there. Is the only way to remvoe it by using the sd-card? then i might be fu..ed regarding the warranty :S
Click to expand...
Click to collapse
I think so. Someone with more experience might be able to provide a more confident answer.
Are you sure you're renaming the ROM as "LEOIMG.nbh" (no quotes) and putting it in the root of the SD-card?
Pelle-pirk said:
i tried the task 29 witout luck A couple more weird things though.. when i try to install a rom from the memory card, the bootloader doesn`t start the installation. I just says "serial". And Yes its formated with fat32 and im sure im doing it right. The other thing is that the phone starts by itself about 60sec after plugging in the charger.. i`m guessing this have to be a hardware problem. might be the usb connector as many seem to have problems with.
I`ve now put in a stock spl and will send it back for repair tomorrow.
Click to expand...
Click to collapse
Hello dude!
Try using a microSD smaller than 8gb and formated with FAT32 (it's a known fact that 16gb microSD does not work for flashing.....).
If you want to remove the HSPL there is 2 ways:
1 - Flash a stockROM via SDcard, like you are trying to do.
OR
2 - Use the HSPL2 program to revert to the original SPL state.
If you could enter the bootloader, probably your phone does not need any special repairs.. Anyway.......
Try using a smaller SDcard to flash the radio and the ROM again. You could also try flashing via USB/PC.....
Do not forget to redownload the ROM, it could be a "bad download".
For more info take a look here:
http://forum.xda-developers.com/showthread.php?t=609477 --> Flashing guide for noobs
http://forum.xda-developers.com/showthread.php?t=611433 --> HSPL thread
Good luck!!
maybe a fix
Pelle-pirk said:
Yesterday i put my hd2 in my pocket without locking the screen. when i heard it surfing around the menues i took it back up and tried to take it back to homescreen. As many times before the phone refused to respond so i took out the battery. But when powering it back on the **** wont pass the htc startup-screen!
I have read around this forum quite alot now and i have done hard reset a million times, i have installed an original updated rom from htc`s site. When this didn`t work i installed hspl3, Artemis v270 NOR and RADIO_2.07.51.22_2. And it still wont start!
Im getting quite sick of experimenting, so i`d be really happy if any of you smartguys could help me
Click to expand...
Click to collapse
hello guys,
someone at htcedia posted this fixes:
1) Install you HSPL.
2) Install your cooked rom.
3) Upgrade your radio. (Leo_RADIO_2.10.50.26)
4) Do Hard reset. (Hold Vol up and down also end call button) then press (Red reset button under back cover next to battery)
Fixes Freezing on HTC bootup screen.
and for me, when i remove the micro sd card the phone bootup but when the micro sd card is in the phone it wont.
so try to remove the micro sd card then reset a hard or soft reset ur device, keep ur micro sd out until ur r completely loaded, then put ur sd card back in the phone.
I don't know where to begin so I'll just list the problems I have been encountering why trying to flash a stock ROM into my TMO HD2.
Preloaded with Android Gingerbread 2.3+HSPL 2.08+Magldr 1.11
Stuck at 123456 Go Go Go
Digitizer cracked & removed
Tried flashing stock TMO 3.14 ROM to ascertain if it is lack of digitizer causing problem
Was able to perform Task 29 normally initially
Could not run 3.14 RUU successfully nor via SD card method with HSPL 2.08 intact. RUU stuck at 8% & SD method stuck at Radio forever
Upgraded HSPL to 3.03 successfully using HSPL 4
Still could not run 3.14 RUU; same as above
Rolled back to SPL 2.08.000 using HSPL 4
Started having problems with Task 29; could not complete properly
Tried MTTY (v.1.42) but could not format NAND
Upgraded to HSPL 2.08 using HSPL3
Still could not perform Task 29 successfully. Sometimes successful & other times not. Mostly met with limited success using SD card method & CustomRUU Task 29 met with numerous connection error (262, 266, 284)
.....
Now, managed to roll back to HSPL 2.08 after redoing SPL 2.08.0000 even though 'We hacked it' screen stayed on with HSPL3 tool 'Critical error'
Trying to flash stock 3.14 RUU met with Error 284
Tried flashing from SD card, screen displayed 'Loading...' perpetually
After pulling battery for about 10 mins, powering up to 'Stick Together' splash screen without any red letters
Now when trying to flash using RUU, it would fail with Error 284/266 & the driver would spontaneously change from HTC USB Sync to Qualcomm Diagnostic Interface 3197 (COM17)??!!
Question:
I think my phone is not bricked but can it be salvaged?
Will the lack of a digitizer prevent it from being flashed?
Can it be salvaged with JTAG?
I cannot charge the battery in the phone now even with power off. Would the remaining battery power prevent or negatively influence the flashing?
Anyone who have met with success in recovering from something like this...or anyone who has dealt with similar symptoms, please advise me what to do from here.
I really need help.
Thanks!
Konker
RUU stuck at 8% & SD method stuck at Radio forever
Click to expand...
Click to collapse
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
Can it be salvaged with JTAG?
Click to expand...
Click to collapse
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
samsamuel said:
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
Click to expand...
Click to collapse
Thanks for the response!
Am I suppose to see the R... at the bottom of the splash screen if the radio is working normally despite having completed Task 29?
I know the OS is wiped but the radio is still there....I think.
Does JTAG restore the radio?
The phone does not get anywhere near hot or very warm when I'm doing all these steps so will putting it in the freezer make a difference? I was under the impression that this works when the device has been exposed to heat or is hot for an extended period of time.
Task 29 doesnt touch the radio, only the rom. You may be able to flash cooked roms, and maybe magldr, just not anything with a radio included. Fridge probbly won't help if you're happy that it isn't heat related.
samsamuel said:
Task 29 doesnt touch the radio, only the rom. You may be able to flash cooked roms, and maybe magldr, just not anything with a radio included. Fridge probbly won't help if you're happy that it isn't heat related.
Click to expand...
Click to collapse
I'm not seeing the R... at the bottom of the splash screen now so does that mean that my radio is fried?
Also, can you comment if not having a digitizer installed would prevent WM6.5 from flashing properly? I've read in the Android thread that it will prevent Android from booting, which is why I decided to flash a WM ROM first to ascertain the hardware condition.
I'll give the 'cold treatment' a try & see how it goes & am in the process of downloading a custom ROM to try. The current HSPL is 2.08 but I'm not sure if it is working properly since the last HSPL attempt ended with the 'We hacked it' stuck on the screen without a reboot & a critical error for the HSPL tool.
Lastly, any idea why it would switch from standard driver to diagnostics driver? It's weird & I can't explain it.
konker said:
i'm not seeing the r... at the bottom of the splash screen now so does that mean that my radio is fried?
Samsamuel... it's a bad sign, but there are situations where that info doesn't show, however combined with it sticking at 8%, which is about when the radio gets flashed.....
Also, can you comment if not having a digitizer installed would prevent wm6.5 from flashing properly? I've read in the android thread that it will prevent android from booting, which is why i decided to flash a wm rom first to ascertain the hardware condition.
Samsamuel........ No, people have flashed successfully with broken digitizers, shouldn't affect winmo, up until it requires input after initial boot.
I'll give the 'cold treatment' a try & see how it goes & am in the process of downloading a custom rom to try. The current hspl is 2.08 but i'm not sure if it is working properly since the last hspl attempt ended with the 'we hacked it' stuck on the screen without a reboot & a critical error for the hspl tool.
Samsamuel....... Id try a different pc if at all posible, though i have had to pull battery myself at the hacked it screen, (not even sure it does reboot itself, from memory, hehe)
lastly, any idea why it would switch from standard driver to diagnostics driver? It's weird & i can't explain it.
Click to expand...
Click to collapse
that's worrying, too, because that's what happens when tmous gets radio bricked,,,phone becomes utterly unresponsive and pc searches for qualomm diagnostic drivers.
I too in similar situation. I can't get NAND android to boot up get stuck on 123456 GO GO GO! Try flashing the stock rom and get stuck on 8% Task 29 still work for me. If I flash Task29 you think I'm able to flash a custom rom that doesn't touch the radio? The only problem is that i was able to flash the radio with no problem.
itzstevo said:
I too in similar situation. I can't get NAND android to boot up get stuck on 123456 GO GO GO! Try flashing the stock rom and get stuck on 8% Task 29 still work for me. If I flash Task29 you think I'm able to flash a custom rom that doesn't touch the radio? The only problem is that i was able to flash the radio with no problem.
Click to expand...
Click to collapse
Do you still have magldr on the phone?
If not, do you see the R...when the default splash screen shows up after powering up the phone?
If not, you might be in a similar situation as me.
I cannot ascertain if my radio is really bricked as there's no way to see or detect that & as samsamuel indicated, having the PC detect a diagnostic port might suggest that my radio is bricked.
I did try to flash a compatible radio to my phone but it failed everytime.
Magldr is still on the phone. I am able to flash new radio with no problem. are you able to flash just a rom and not a a rom & radio?
samsamuel said:
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
Click to expand...
Click to collapse
yes you are right my bro ... had same problem ... after cooling phone in fridge for 5-10 min it will go perfect BUT still it wouldnt boot into winm so i decided to try android in nand , flashing went ok but after that it wouldnt boot Fatal hit ( magdlr) so i put phone in fridge again for 5-10 min and Yes it booted in android - tried same with WP7 ... But after using a while it will get hot and will stock or restart
konker said:
[*]Can it be salvaged with JTAG?
Click to expand...
Click to collapse
No my bro... jtag only writes boot - repair files
itzstevo said:
Magldr is still on the phone. I am able to flash new radio with no problem. are you able to flash just a rom and not a a rom & radio?
Click to expand...
Click to collapse
I think your HD2 is in a lot better shape than mine.
At least you can flash your radio...I can't flash either ROM or radio.
But I suspect your problems might be due to corrupted NAND.
Have you tried Task 29 with mtty?
At least you can see error messages with mtty when doing Task 29.
ubejd said:
yes you are right my bro ... had same problem ... after cooling phone in fridge for 5-10 min it will go perfect BUT still it wouldnt boot into winm so i decided to try android in nand , flashing went ok but after that it wouldnt boot Fatal hit ( magdlr) so i put phone in fridge again for 5-10 min and Yes it booted in android - tried same with WP7 ... But after using a while it will get hot and will stock or restart
Click to expand...
Click to collapse
ubejd, you gave your HD2 the 'cold treatment' after it turned warm & refused to boot or rebooted automatically am I right?
Would it do my HD2 any good to put it in the freezer when it is cool as room temperature? It has been sitting there unplugged & unpowered for at least 8 hours. I have not tried the 'cold treatment' but flashing custom ROMs with HSPL 2.08 also failed.
Seems like a combination of radio brick & NAND failure...
konker said:
ubejd, you gave your HD2 the 'cold treatment' after it turned warm & refused to boot or rebooted automatically am I right?
Would it do my HD2 any good to put it in the freezer when it is cool as room temperature? It has been sitting there unplugged & unpowered for at least 8 hours. I have not tried the 'cold treatment' but flashing custom ROMs with HSPL 2.08 also failed.
Seems like a combination of radio brick & NAND failure...
Click to expand...
Click to collapse
yes you are right my Bro
you can try, it wouldnt do any harm but just put in isolated place - bag before putting in the fridge - to keep safe phone from getting wet and dont let more then 5-10 min maximum... but as i told it will not boot again in win mob - i hope it does but i doubt ... if it fails to boot than consider to go with android or winp7
i have one question how it began to act like this... did it fall or you bought like that
i hope you success
best regards from me
Gave it a go with the freezer test. I was surprise that i was able to boot up into CWM, & load up Android. Now I can only use the phone for maybe 20 min or so before it get hot again and I have to put it back in the freezer. Is there a way to tell which HD2 is bad batch?
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
itzstevo said:
Gave it a go with the freezer test. I was surprise that i was able to boot up into CWM, & load up Android. Now I can only use the phone for maybe 20 min or so before it get hot again and I have to put it back in the freezer. Is there a way to tell which HD2 is bad batch?
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
Click to expand...
Click to collapse
I gave my HD2 the 'cold treatment' & I was mildly surprised that it reached the 2/3 mark when using the SD card method to flash a custom ROM but that was it. Back to square 1...
itzstevo said:
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
Click to expand...
Click to collapse
if you have both of them take motherboard from the one who has bad screen and put in one who has heating issues this way you will have at last one working hd2...
I had the same problem too. I knew I wasn't the only one with this problem.
Now I'm sure, MAGLDR makes the NAND corrupted (over 8%). My phone won't charge too, gets stuck at 8%, get stuck on splash screen and doesn't show any red lines...
PasSlert said:
I had the same problem too. I knew I wasn't the only one with this problem.
Now I'm sure, MAGLDR makes the NAND corrupted (over 8%). My phone won't charge too, gets stuck at 8%, get stuck on splash screen and doesn't show any red lines...
Click to expand...
Click to collapse
Flash failing at 8/9% has been happening long before magldr, , and seems to be connected to the radio being corrupted.
But I can flash a radio via RUU... if my radio were corrupted, flashing a radio should not be possible. Am I right ?
With RUU : I'm stuck about 1 minute on 8% then the process resume up to 100% without any error, but whatever the ROM I flash, no one reach splash screen.
With SD : No problem.
Like the OP, my phone is acting weird when I plug on charge.
With cable to PC : autoboot (MAGLDR 1.13 issue)
With cable to AC : red led but when I plug off the cable, the red led is still on (until I remove the battery).
It's clear that in any way, MAGLDR is not completly removed of my HD2 (yeah, I flashed some stock ROM with SD card).
I think I'll send it to repair, I'll leave feedback if I send it.
I have tried everything on this forum and everything people have contributed to me. Now I'm in an endless circle of downloading this and flashing that. Nothing seems to work anymore. My damn phone gets stuck on the boot screen and vibrates a few times and just stays there. I'll give it one more shot before I'll run over it with my car or attach some fireworks to it, something in that nature.
I tried using task29.exe, but it always results in Error 290. I'm pretty sure I'm using 2.08 HPSL and Radio Leo 2.15.50.14.
I faced that you discribing... when I bricked my OMNIA i900!
There're nothing wrong with Leo - it's STILL one of the VERY best smartphone on the market!
And, I never had problems with flashing, except that moment with my old OMNIA, when I was hurry to flash one rom and I f*cked up big time... and bricked my phone.
Don't know what happen to you - you don't writting DETAILS.
But, I'm strongly recomending you to try and re-DOWNLOAD every file/app you need to flashing roms, re-install everything in your PC, try again the task29.exe (if your phones has nothing wrong, the task29.exe SHOULD be working, by all means) and re-try to flash a rom - I'm strongly recomending, to try "ENERGY" roms. The "Yank" lad (chef) rocks!
Flash through SD card stock ROM.
art0605 said:
My damn phone gets stuck on the boot screen and vibrates a few times and just stays there.
Click to expand...
Click to collapse
I think your phone cpu is getting loose from its socket, have a read here http://forum.xda-developers.com/showthread.php?t=982454
Its not easy to fix tho.
Did you use Android ROMs with MAGLDR? Chances are that your device is bricked.
hi
i would suggest to download and install this toolkit found here
http://forum.xda-developers.com/showthread.php?t=1090783
this will allow you to task 29, install hspl, as well as install windows ruu.exe roms
it also alows you to download the drivers needed for your phone which is what i expect is your issue without having any real details
hope this helps
Have you tried flashing a rom through the bootloader by holding down volume down then turning the phone on? Barring a hardware fault, as long as you still have HSPL and can get to the tricolored boot screen your phone should be recoverable.
i think it might be hardware probleme ...not all phones are compatible with android ...mine works perfect on wm but ...when using android and no matter what's the rom i installed ...i always have a hight battery drain ...and i have always to wait 2 mn after turning off the phone if i want to turn it on ...otherwise i stuch on android logo and i cant boot android from sd card...i tried everything ...without success ...
the boot probleme and the hight battery drain doesnt exist on wm ...so i guess not all phones r made to work with android ...since htc make phones by lots ...so might buy one with hardware probleme like mine ...
i'm sure if u tried to install android in another phone u wont have any probleme.
i wrote this reply using wm ...i install it back to sell it tomorrow ...just do like me
instead of destroying it, give it away to some developer. sometimes things starts disliking you. than nothing works. so give it away. where do u stay?
I have the same problem. I finally found an easy fix. Take out the battery for 2-3 hours and put it back in. It almost always comes back to life with no loss of data. Good Luck.