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!)
First of all sorry for my english not good.
Start : with my HD2 have brick after task29 and not success to flash new ROM I'm take USB. cable out and try to open my HD2 in to boot loader by put volum down + power bottom but screen not show any image or 3 color my phone it only long vibration pull battery out waiting 30 minute and put battery in and try to open my phone to boot loader but is same only long vibration.
Now : can not do any think with it when try to plug power in my phone is auto startup and long vibration.
I'm search on google and in this forum not have some one face problem same as me please help me to fix this.
Any body please help me, I'm love it because now we can run both WM. and Android
Upppp waiting for your help
Did you try a long press of the reset-button?
You could try to put the original Stock Image from HTC onto the root-folder of your SD-Card, rename it to LEOIMG.nbh and Push Vol up + Vol down during start and follow the on-screen instructions if it works.
Otherwise use Search-Function in the forum.
ı have jtag HTC for samsung and HTC devices if u want send for repair to me..
www.sevgigsm.net/forum
admin..
I use ORT
Did you check to make sure your radio version was correct before flashing? This is probably the number one reason for bricking.
Check this thread it may help you if you did the flash properly:
http://forum.xda-developers.com/showthread.php?t=668347
i got same problem now...
no screen, no boot, vol down+ power oso same
no screen just a long vibration
anybody help?
I am using the correct radio so don't tell me I am using a wrong radio or something, I have been flashing for 4 months so I know EXACTLY how to flash.
now i can neither get into tri-color or hard reset so don't tell me to flash or smth like that, just tell me how to recover properly
Don't tell us to use search or something because seems like only 2 of us is encountering this problem in the internet
I'm exactly the same problem as TS coz it juz auto go vibrate when plug in battery
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
at the long vibrate, when i plug in to my pc, it will keep on got usb connected and disconnected sound
and dont know what device is connected as not shown in found new hardware and device manager
I also have been searching all possible keywords about what me and TS encountered but all linked to completely UNRELATED results(like search for long vibrations only link to people asking how to make vibration long and 1st result is this thread)
bountygiver said:
This problem actually started when I flash ROM halfway, it stucked and failed...
the device is already HSPL-ed!!!!
but why the F it cannot get into tri-color bootscreen now?
Also, I have to state that my device already got several problems before, my device was very hard to bootup as it will always stuck at HTC screen w/o red version number at bottom left corner, must keep on removing and reinstall battery and reboot until it can boot, not an issue with rom/radio/sim/sd as I tried flash proper rom and radio and remove sd and SIM.
my device also seems like got problem at the gps chip, because when using it for a few minutes, it will lost signal and never reconnects unless i soft reset, after use gps the device will also use battery VERY FAST(-100mA in standby, from -4mA).
now i cannot flash to stock completely, how do I get warranty it?
Click to expand...
Click to collapse
Silly question, but are you holding (and keep on holding) the Volume-Down button while you press the power button?
of course YES
i told you i have been flashing for so long
Leo from T-Mobile. Hi! I've got same problem. After flashing new (next) rom phone definetely died. Phohe is currently simfree and with HSPL. Only one reaction is short vibration after press power button. I searched everywhere. My phone has no bootloader but system see him as Qualcom CDMA Technologies MSM. Thats all, any ideas? Please and thanks for advice.
czaruch said:
Thats all, any ideas?
Click to expand...
Click to collapse
Yes, you flashed a non tmous stock rom that included a ..51.. radio and it destroyed your phone.
What rom? exact filename please.
thank you so much.
I bricked a Leo with the .51 radio. I think I read that is a European or otherwise foreign radio. Since your ROM has Euro in the name.......
czaruch said:
ROM_Leo_HTC_WWE_EastEurope_1-66.
Click to expand...
Click to collapse
The full filename for that rom is
RUU_Leo_HTC_WWE_EastEurope_1.66.479.2_Radio_CRC_Si gned_15.32.50.07U_2.07.51.22_2_Ship.exe
it comes with a version x.xx.51.x radio, and they do Not work on tmous (t mobile us) phones. They kill them
Your phone is dead, sorry. No known fix.
warranty or repair (or JTAG if you are brave and have the money)
a friend of mine bricked his phone. he then tried to microwave it, but that didn't work after that he took a power wire from an old computer, cut it and connected it directly to the phone's parts where the battery would go...this completely f-ed his phone up (he also used a lighter to fake a powersurge of the battery). Then he called htc and a few weeks later he got a new hd2!
GOOD LUCK
lol, he doesnt need to do any of that, its allready as dead as it can be. Loads of epople have had them replaced under warranty with this kind of brick. It wont start, so htc/tmo cant see that its been hacked.
Hi! I understand and realy sad. Somebody know where could I fix it in UK? And how much for this pleasure. Thanks.
i would contact htc, see what they have to say. (dont say you flashed it, it just stopped working")
i bought an used hd2..this hd2 wont boot up to windows it just stuck at htc logo..i was thinking theres must be something wrong with the os..so i think reflashing rom will be just fine..
first i check the spl and radio..spl is 2.08 and radio is little bit strange cos its 2.07.51.x i believe .51 is t mob hd2 version, but by looking its phisic i believe this is not t mob version..
so then.. i flash cottula hspl3, the flashing went fine..100% complete, after that i reboot to bootloader then do task29, task29 complete 100% , then i flash Omega sense rom, this rom flashing went fine too, complete at 100%.. but when it reboot it just stuck at htc logo, theres no radio information text at the bottom like use to be..
i wait for a couple minute, still no progress.. then i take off the battery, put it back, try to turn it on but it wont turn on anymore, i can't turn on to enter bootloader too..
so it is now completly dead, i make sure the battery still has power..i have another hd2 too..i use it battery but still no luck..i tried to plug it to charger..no red led, plug usb cable to pc no detected hardware..
i'm so curious what is the cause so my hd2 brick? .51 radio? should i flash .50 radio firts then winmo rom?
btw i'm planning doing Riff JTAG but it cost $150..+ $30 for shipping to my country
Sent from my HTC HD2 using XDA App
lesjaw said:
but by looking its phisic i believe this is not t mob version..
Click to expand...
Click to collapse
if the send key is greenm its tmous, if its white its regular.
However, if you say it came with a ..51.. radio and it worked, then it IS deffinately a regular, and not a tmous.
so then.. i flash cottula hspl3, the flashing went fine..100% complete, after that i reboot to bootloader then do task29, task29 complete 100% , then i flash Omega sense rom, this rom flashing went fine too, complete at 100%.. but when it reboot it just stuck at htc logo, theres no radio information text at the bottom like use to be..
Click to expand...
Click to collapse
correct, the omega rom requires a ..50.. radio. Enter bootloader and flash a ..50.. radio and then omega will boot.
i wait for a couple minute, still no progress.. then i take off the battery, put it back, try to turn it on but it wont turn on anymore, i can't turn on to enter bootloader too..
Click to expand...
Click to collapse
bent battery pin (probably)
so it is now completly dead, i make sure the battery still has power..i have another hd2 too..i use it battery but still no luck..i tried to plug it to charger..no red led, plug usb cable to pc no detected hardware..
Click to expand...
Click to collapse
bent battery pin (probably)
should i flash .50 radio firts then winmo rom?
Click to expand...
Click to collapse
roms that use a tmous rom as their base (that means they unlock the 576ram,) require a tmous radio, , meaning one that it version 2.06.50.x or higher, otherwise they do not boot. It is not a problem, it is just waiting for teh correct radio. Enter bootloader and flash a radio. (exactly teh same as flashing a rom)
It doesnt matter if you flash teh rom first or the radio, it just scares you when you flash teh rom first and it doesnt boot. But its not a problem.
btw i'm planning doing Riff JTAG but it cost $150..+ $30 for shipping to my country
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
thanks for ur reply..
i can make sure the pint not bent..seems very normal..
i'm sure its brick already, but i wonder why?
Sent from my HTC HD2 using XDA App
Hello guys i have a problem with my HTC HD2.
I have searched a lot on this site before posting my problem.
This is what happens and what i did:
The phone doesn't pass the white HTC screen with the RGD letters below.
What i have tried:
HSPL 2.08.HSPL, 1.66, 1.42, 2.08.000
Radio: Leo_RADIO_2.08.50.05, Leo_RADIO_2.15.50.14
Roms: Stock Vodafone (Dutch) rom, Energy rom
Hard reset (vol up +down on startup).
Tried task 29 and started everything all over again
I went to the a phone store, they couldnt help me. Afterwards i went to the official store but i don't have my receipt anymore so i don't have a warranty..
So i think i have tried everything i could find on this forum. Tried most of the HSPL versions with diferent roms. But all of them stay on the startup screen (white htc start screen)
If someone can help me please, this is really my last chance
Thanks,
Issam
ps. i hope this is the good section to post this problem.
Well the phone starts up now (it actually works for a few minutes!). I haven't changed anything, the only thing i did is leave the battery out for like 1 hour. But everytime i start up the phone it freezes and / or turns of after 1 min or something. Sometimes it doesn't even boot up like the usual problem, but then i remove the battery for 10 minutes and it boots normal again.
So i really don't have a clue
i was experimenting all day again with my htc.
What i found out was, the longer i keep my battery out of the phone the longer i can use it.
For example: I had the battery out of the phone for about 2 hours, when I put it back in i could use it for like 10 minutes.
But when i keep the battery out for 10 minutes it freezes within 1 minute.
Maybe this will help me get the solution to this problem.
I would format the sd card just in case, also make sure you have the correct versions of what you need, rom raido ect, because theres two types of HD2s, hope this helps!!
Thanks for the reply, i tried formatting the SD card and i succeeded doing it 5 times i think. I think i have the correct version of rom and radio, how do i know?
IssamRazza said:
Thanks for the reply, i tried formatting the SD card and i succeeded doing it 5 times i think. I think i have the correct version of rom and radio, how do i know?
Click to expand...
Click to collapse
You should remove hspl , and after that install the latest rom available on htc site for your device (download the rom from htc site, with your serial number ) . Official roms have included radio inside of them. If HSPL is removed and you have again problems with your device with an official rom installed, then you have a hardware problem. You could try to boot up without sd card installed, to see if the card is the problem.
Thank you,
I will try removing HSPL and install the original ROM from the HTC site. I'll let you guys know.
IssamRazza said:
Thank you,
I will try removing HSPL and install the original ROM from the HTC site. I'll let you guys know.
Click to expand...
Click to collapse
I see that you are on t-mobile network , so you should download your rom from here: http://www.t-mobile.com/wmupgrade/ . Just enter your imei and download the update. Remove HSPL and then install the official rom. Perform a hard reset after that , and see if is all ok . Keep us informed pls.
Hi, yes i have a T-mobile contract, but my phone is Vodafone branden so i'll have to download the Vodafone version I think.
But what i just did is this:
I had HSPL 2.08.HSPL and a Custom ROM on it. So I was planning on maybe sending it back. Thats why I performed a task 29 to delete all the previous (parts of the) Roms. After that i changed my HSPL to 1.66.000, the original spl I had on it.
But now the phone does vibrate when i hold the power butten (with vol down), but there is no picture, so i cant get into the phone or the Red green blue screen. So i think the phone will not boot because I deleted the Rom on the phone and also returned the spl to original.
Is there a solution for this problem? omg this phone just doesn't seem to be working for me (maybe it's me that is not working for the phone).
It is normal since you did a task29. Verify if you did it correctly here http://forum.xda-developers.com/showthread.php?t=644781
Yes i have read that thread thank you, but the question is:
How can i get the phone to connect with my PC, so I can install original ROM. Because the Boatloader screen won't start up, to make connection with my Computer. I press the power button and vol down butten at the same time. Tried it at least 20 times
Thanks you all. But i sent this phone back to HTC. The board was replaced and they sent it back, so it works again! finally my phone back
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.