Related
I have read and read and read. I have "bricked" my phone in the past and fixed it. I have used, tested, and flashed many roms from this site (Thanks to all cooks for their work!) but I still consider myself somewhat 'new' to troubleshooting.
I woke up this morning to make some important phone calls today and as luck would have it, my phone was stalled again. It's been doing that for a few weeks now. My last flash was Open Touch 5.0 UL I believe (either that or 5.2 biggy) and it has been working great except for the occasional freeze.
EDIT: Forgot to add, the actual problem is now it won't boot up after it froze this morning. Just sits at the boot screen
So I've tried my other methods of fixing it... /edit
Except this morning nothing is working. I have tried flashing with Orig. T-mobile ruu, tried SD flashing with the RUU_signed.nbh, tried restarting the computer, phone, removing battery and sim... NOTHING! When trying the sd flash (which I've never done before today, it reads and tells me to push the down button but then goes to bootloader screen and just sits there. With the RUU I'm getting err 300 but I'm using the SAME RUU (4.10...) that I've used in the past to reflash my phone AND tried the new one (4.26...)
Possible problem: Does it matter what kind of usb cable you use? I don't have the normal one I use as I am not home but I figured usb is usb...
I've read about it being a motherboard issue, how common is this?
I've read somethings about MTTY, would this apply to me??
Please help, anyone who has any suggestion, I'll try it!!
Stats:
IPL 4.10.0002
SPL 4.10.0000
NOT hard-spl'd
Wing w/ Open Touch Project 5.0 or 5.2
actualy the sd method needs hard spl thats all i can really provide
I appretiate it, that I did not know... I could barely find anything on how to do it even.
im having the same problem bt instead of freezing da screen jus goes different colors or jus goes gray and stays der
Thats basically what mine did. The colors would get messed up and no matter what button i pressed it would not do anything. My advice to you edrift, is BACK UP YOUR STUFF NOW and reflash it asap if you can still reboot. I can get into my phone at all now.
yea i tink i might jus throw my phone away.dis is jus gettin rediculous
I hope if anyone can help me as am really desperate right now, i think i bricked my htc magic or i dont know what i did exactly.
one of my friends rooted the phone for me to V2.1 i didnt like it has a shorter battery life than the cupcake so i tried to get back to cupcake 1.5, and am not an expert at all am just doing what i can see at the forums. i faced the problem E/can't open/sdcard/update.zip (bad)
was told to try another zip rom files. all was the same problem. then i found a file, but unfortunately it was something called SPL wasnt a rom. after i flashed it my phone now is switching on and freeze on the vodafone logo forever.
i tried like i saw on the forums to press on back+power but nothin home+power neither vol. down+power.
the same as well i can see the blue led light if i pressed on the trackball and the power but thats its.
i saw a lot of forums talking about the same exact problem, but didnt find any clear solution, the only one was pressing on back + power but i did that a lot of time but it didnt work at all,it keeps showing the vodafone logo and thats it, anyone has an idea how can we fix it or its unfixable or what ?!
any help will be much appreciated
Thank you
Moved to General
Ouch...
ooka_22 said:
I hope if anyone can help me as am really desperate right now, i think i bricked my htc magic or i dont know what i did exactly.
one of my friends rooted the phone for me to V2.1 i didnt like it has a shorter battery life than the cupcake so i tried to get back to cupcake 1.5, and am not an expert at all am just doing what i can see at the forums. i faced the problem E/can't open/sdcard/update.zip (bad)
was told to try another zip rom files. all was the same problem. then i found a file, but unfortunately it was something called SPL wasnt a rom. after i flashed it my phone now is switching on and freeze on the vodafone logo forever.
i tried like i saw on the forums to press on back+power but nothin home+power neither vol. down+power.
the same as well i can see the blue led light if i pressed on the trackball and the power but thats its.
i saw a lot of forums talking about the same exact problem, but didnt find any clear solution, the only one was pressing on back + power but i did that a lot of time but it didnt work at all,it keeps showing the vodafone logo and thats it, anyone has an idea how can we fix it or its unfixable or what ?!
any help will be much appreciated
Thank you
Click to expand...
Click to collapse
I'm not much of an expert myself. I've got the basics down of rooting and flashing, but try looking up a how to unroot guide for your phone. theunlockr.com has pretty good step-by-step video and text guides. I'm assuming you have the MT3G so try this page:
theunlockr .com/2009/08/22/how-to-unroot-your-mytouch-3g
After you unroot follow their rooting guide. Its very simple to do and only takes about a half hour to do.
ooka_22 said:
I hope if anyone can help me as am really desperate right now, i think i bricked my htc magic or i dont know what i did exactly.
one of my friends rooted the phone for me to V2.1 i didnt like it has a shorter battery life than the cupcake so i tried to get back to cupcake 1.5, and am not an expert at all am just doing what i can see at the forums. i faced the problem E/can't open/sdcard/update.zip (bad)
was told to try another zip rom files. all was the same problem. then i found a file, but unfortunately it was something called SPL wasnt a rom. after i flashed it my phone now is switching on and freeze on the vodafone logo forever.
i tried like i saw on the forums to press on back+power but nothin home+power neither vol. down+power.
the same as well i can see the blue led light if i pressed on the trackball and the power but thats its.
i saw a lot of forums talking about the same exact problem, but didnt find any clear solution, the only one was pressing on back + power but i did that a lot of time but it didnt work at all,it keeps showing the vodafone logo and thats it, anyone has an idea how can we fix it or its unfixable or what ?!
any help will be much appreciated
Thank you
Click to expand...
Click to collapse
Yup. Sounds like a brick. If you update the SPL you better damn know which SPL you're flashing and if it's compatible with your device. I've said it before and I'll say it again.
Right SPL + Right Radio = Good device (99% of the time)
Wrong SPL + Right Radio = brick (60% of the time)
Wrong SPL + Wrong Radio = brick (99% of the time)
Right SPL + Wrong Radio = brick (60% of the time)
Do you see the pattern here?
In other words you NEED to make sure that you are flashing the appropriate SPL for your device and make sure that you have the right radio before flashing ANYTHING.
Now since it would appear that in your case you don't even have a clue of what SPL/Radio you had to begin with and you just blindly flash a random SPL, we don't even have a way of telling if you have a 32a or a 32b device. Not that it matters because if you cannot get into the bootloader or recovery then the only chance that I think that you have is looking up JTAG, tearing your device apart, soldering the test points and running the program. This would allow you to reflash your spl. However I suggest you try to do a warranty exchange because I wouldn't even waste my money on JTAG technique.
This is for the G1 so it would probably be a little different than the MT3G, but the concept should be the same.
http://forum.xda-developers.com/showthread.php?t=591048&highlight=jtag
but not everybody is so unlucky. take a look at this post
http://forum.xda-developers.com/showthread.php?t=571457
so you never know.
Thank you
Really many many thanks for your reply, i really do appreciate it. i know that am a noob with what i did with my phone, i was just trying to get back to the cupcake. i never imagined that i could ruin everything just like that.
anyway u r right when u said that i know nothin about the radio and the SPL i started with, but i just noticed that the SPL named (Sapphire-signed), and my device is HTC Magic with vodafone 32a. but i dont know what sapphire is.
so i will give it a try with lookin for someone here who can help with tha Jtag thing, if not i will try to send it to be repaired. however i guess that the warranty doesnt cover such faults.
sorry for posting my thread at the wrong place.
Thanks for your time
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
SS and HX in the bootloader screen just means Samsung or Hynix, , two chip providers HTC uses. They do the same thing, and you can forget about that for now, you have much bigger issues than one chipset being slightly better than the other.
The pink on black screen is a splashscreen, anyone recognise it? winmo? android?
The HTC website started dropping support pages for the HD2 a month or two ago, , looks like its ancient history as far as HTC are concerned.
Qualcomm MSM,,, this is a bad sign, , it is what the bare chipset presents itself to the usb connection as when there is no controlling bootloader. (This is what tmous users get when they radio brick their phones). Quite an odd symptom to see in a phone that powers on.
From the various power / boot symptoms, it sounds likely that one or more of the following are true
1 - the battery may be low on charge, and if magldr is installed the battery wont charge until android is running (which of course it cant) so you NEED to get magldr off ASAP (if in fact it flashed)
2 - the radio may be corrupted, which usually manifests itself as flashes failing at 8 - 10%, or radio flashes never completing.
3 - The phone may be one of the unlucky ones that has/is cooked/cooking itself. have a read on the 'freezer trick' where you cool the phone down for a while in a bag in the freezer, then quickly flash from sd as soon as you take it out, so the chips don't overheat before its done. If this turns out to work, then the phone has hardware issues.
4 - The bootloader itself may be corrupt, but only slightly (just theorising now) or the NAND memory where the bootloader is stored could be starting to degrade.
Recommended way forward.
Assuming you have access to a card reader,,,
send me your IMEI and an email address, and ill generate you a Goldcard.img,
follow THIS to make teh goldcard and place on that goldcard the RUU_Signed.nbh (renamed to leoimg.nbh) extracted from, , lets go for the WWE 3.14 rom from HERE (Lotta junk in that folder, scroll way down towards the bottom, look for filename as below)
id go for
RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.zip
down towards the bottom.
(Thats assuming you want english? theres probably a DE one if you prefer)
SO, id try flash that from the goldcard, and report back.
(Note i'll be on and off all day, so don't expect an immediate response to your IMEI, cheers, oh and the .img when i send it will most likely get spam foldered, so dont miss it!)
I created a goldcard myself and tried the image inside "RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship.zip".
While flashing it showed me "RSA Fail" on "Radio_v2".
Any ideas? I'll try other ROMs till someone answers
Thanks,
iCEQB
EDIT1:
Trying "GER" Roms:
1 test) HTC_HD2_RUU_Leo_HTC_GER_1.66.407.1_Radio_Signed_15.30.50.07U_2.06.51.07_Ship.exe - "RSA-Fail" on "Radio_v2"
Ahh radio fail, bad news. I've seen it cured once or twice, by flashing the phones original rom, but I suspect those were exceptions.
I've also seen failed flashes take when you well chill in the freezer (card sim and battery out while it chills) and quickly flash on removal.
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
samsamuel said:
Also, just confirm you made a hd2 winmo goldcard, the free goldcard page at revskills is for wp7 and android phones.
Click to expand...
Click to collapse
Yeah I used the wp7 config. Is it bad? I mean, the goldcard works right?
test 2) RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe - "RSA-Fail" on "Radio_v2"
I'm out of ideas guys ... will wait for you to create me a winmo goldcard image and try them again.
Last resort is the freezer trick. Or any other ideas on how to progress from here?
Regards,
iCEQB
EDIT: BTW, does HSPL need to be deinstalled for these goldcard actions?
Ohhh hang on, that img i sent wont work, silly me, its not the imei I need, its the Cid (unique serial, uid, goes by a few names) of the SD card. See the howto I linked ya for how to find it.(really easy if you have access to any other winmo phone, not so easy otherwise.)
Just shows how long its been since I thought about goldcards.
Sorry.
Which branded phone is this?
Brother even I have same type of logo when phone starts (pink colour circle)
Even my phone is bricked but I can install wp7 or android (only no network problem)
Can u guide me how did u solve this issue pls
Thanks & Regards
SE_iCEQB said:
Hi all,
yesterday a friend of mine gave me his HD2 for repair, he bought it from eBay with a ROM failure.
I never tried to fix / flash any HTC, so I read trough a lot of flashing guides and other peoples problems etc.
So I'll tell you whats working / what I tried / what I can do / what I can't do, in the hope someone can make sense out of this and help me
1) The phone has a strange behaviour in terms of the battery. It only turns on if I'm lucky. This means if I pull the battery out and back it and try to power it on, I get a light / weak vibration (and if I'm lucky) it boots into the states mentioned in point 2) and 3). If I'm unlucky on the other hand, it just stays at a black screen, but still gives me this light / weak vibration. Windows recognises the phone in this back-screen-state, but doesn't like it that much, since it wants drivers for a "Qualcomm MSM .... something" device.
The best way to get the phone back to book (in the possible states mentioned in point 2) and 3).) is to let the battery rest fro a little while and plug it back in ... or I spam the phone like quickly plugging the battery out and in and prey that it somehow boots.
2) The "booting" I was talking about in point 1) doesn't mean it boots into any OS. I attached a picture which shows the state of the phone when I try to boot it normally via the power button. It just freezes there at this pink circle and does nothing. If I'm not wrong it should show the radio version etc. in red in the bottom left corner, but we'll get to that
Things I can do:
3) I can get into bootloader mode.
4) I can flash HSPL 2.08 and 3.03 ... or it's stock versions however I like.
5) I can execute "task29.exe" which finishes its job successfully.
Things I tried (and noticed):
6) I tried to flash "MAGLDR" which also finishes successfully (according to the install tool at least), but does nothing on the phone, same screen as in the attachment.
7) I tried to flash the latest radio ROM (v.2.15.50.14 afaik) via "CustomRUU.exe", which get stuck on 96%. "CustomRUU.exe" later on tells me that the communication betweeen the host and phone failed.
8) The phone doesn't seem to be branded, yet I tried to flash both T-Mobile and unbraded roms and 2 different versions:
Code:
RUU_Leo_HTC_WWE_1.48.405.2_Radio_Signed_15.28.50.07U_2.05.51.05_2_Ship.exe
RUU_Leo_S_HTC_GER_3.14.407.2_Radio_15.42.50.11U_2.15.50.14_LEO_S_Ship.exe
RUU_Leo_1_5_TMOUS_2.10.531.0_Radio_Signed_15.34.50.07U_2.08.50.08_2_Ship.exe
ruu_leo_s_tmo_de_3.14.111.1_radio_15.42.50.11u_2.15.50.14_leo_s_ship.exe
If I flash those with HSPL and the installer it came with it stays at 0% forever.
If I flash them without HSPL and the installer they came with they get stuck at different point somewhere between 8% and 10% and if I wait for 10 seconds, the progress bar turns red and a "!" appears at the end of the progress bar, the installer later on tells me, that this version is not for my phone or something.
If I flash them with HSPL and "CustomRUU.exe" the progress bar also get stuck at the above mentioned %-marks, but the progress bar stays green and does nothing for 10 minutes, after that the "CustomRUU.exe" tells me that the communication with the phone failed.
Some things I noticed:
9) While I was spamming the phone with battery I once got to a point where the charging LED light up for the first time in this whole process I went trough with this phone.
10) After point 9) I plugged the battery out and back in and powered it on via the power button. I got to the screen I attached below, but it didn't got stuck there, the screen just faded to black and the phone shut itself off. I managed to do this 2 times in a row, after the third try it froze again and I was back there where I was before (points 1-8 ).
This is it As you can see I tried a lot of stuff, yet I think I've overseen something and I hope you can help me there or got some other ideas apart from the JTAG'ing method, which shouldn't be an option for now, as getting into the bootloader mode is worth gold afaik, so we should be able to do something via this mode right?
Best regards,
SE_iCEQB
BTW: I can also get into the hard reset mode, but of course this gains nothing on this phone
EDIT1: Another thing I noticed, is that in the bootloader mode it says "SS-BC" in the top line, where on every other picture I saw of this phone in its bootlaoder mode, it says "HX-BC" or something, dunno if this is important.
The phone came with a german packaging, so I only tried the "DE" roms mentioned in point 8).
While I was searching for roms, some people said that I can check the S/N of this phone on the HTC website which I couldn't find ... is it gone or am I blind already?
Click to expand...
Click to collapse
Do a jtag on it it will fix everything i think
Sent from my Nexus 7 using xda premium
Hello, and sorry for the post asking for assistance!
been driving me nuts for 2 days now, it seems i'm having a major case of melting HD2
it started with the phone freezing often, reboot solved it.
then, it went to having to unplug battery for a few, and, reboot fixed it.
now i'm at a constant white screen (no htc logo)
was running in Android but tryign to just get anything working for now.
i made the sd card leoimg.nbh with a custom rom to recover it, but i can't get it to finish
in red : Radio_V2 Fail
in blue : all the rest
tried to flash radio update, failed
tried to update the HSPL version (2.8one now) but no go, it shows "success" but in bootloader shows the same old version.
what can be the cause of this, exept memory nand being screwed?
greug said:
what can be the cause of this, exept memory nand being screwed?
Click to expand...
Click to collapse
CPU and its BGA balls!
Not alot to be done i think...
Keeps coming up on white screen.
Tries to flash HSPL (newer version) finishes but it still shows the same version when powering +volume MIN.
Tried to flash a Radio, comes up with an error Radio V2 error
Tried to push a ROM on there, gives a "image file is corrupted"
Tried what i found here on the different forum threads but....seems my HD2 gave up on me...or at least it's beyond my repair skills.
Thanks for those before me who gave suggestions on what to try, it's a damn sad day i loved that phone..
wts : one slightly bricked phone
Try to do a Task29. Use the HD2 Toolkit for that.
You have to JTAG it in order to recover it. RADIO_V2 means it's radio, and it's officially bricked. There's nothing you can do other than JTAG to recover it
Well, in a way i'm glad i have the answer now about the V2 being the radio ...
Thanks for the input guys, not sure i'm going to bother with the JTAG story, already ordered a replacement for my HD2 as it is, can't spend too much time without my phone.
Anyone knows if people are interested for the "bricked" HD2's? or how to reach people?
Hello XDA.
Huge problem over here.
I can't flash anything on my device (HD2, Europe) anymore.
Newest Radio-Rom, SPL-2.08.HSPL.
Tried everything listed in the forums, event tried to flash stock leoimg.nbh from sd. nothing.
Whenever I try to flash via USB, the screen is stuck at 0 % (independent from what I try to flash).
HSPL won't let me reflash it, get an error msg.
When flashing from sd, stuck at "loading..."
Hardreset (VolUp+VolDown+Power) works, but doesn't change anything.
I really tried E-VERY-THING, nothing seems to work.
Bootloader is starting up, even the white screen with the green HTC logo is showing up, but then: nothing.
Worked my ass of through hundreds of threads in dozens of forums.
This is my last chance.
Anybody? Thank you!
schousta said:
Hello XDA.
Huge problem over here.
I can't flash anything on my device (HD2, Europe) anymore.
Newest Radio-Rom, SPL-2.08.HSPL.
Tried everything listed in the forums, event tried to flash stock leoimg.nbh from sd. nothing.
Whenever I try to flash via USB, the screen is stuck at 0 % (independent from what I try to flash).
HSPL won't let me reflash it, get an error msg.
When flashing from sd, stuck at "loading..."
Hardreset (VolUp+VolDown+Power) works, but doesn't change anything.
I really tried E-VERY-THING, nothing seems to work.
Bootloader is starting up, even the white screen with the green HTC logo is showing up, but then: nothing.
Worked my ass of through hundreds of threads in dozens of forums.
This is my last chance.
Anybody? Thank you!
Click to expand...
Click to collapse
If you've tried literally everything as you claim, then nobody can possibly help you. Have you tried flashing a stock ROM via the SD card?
schousta said:
SPL-2.08.HSPL.
.......
the screen is stuck at 0 %
Click to expand...
Click to collapse
are you 100% sure its 2.08.hspl and not 2.08.0000?
also, tried different usb ports? different PC even, if possible? (not 64 bit either, if you can manage it, , , an xp machine is perfect)
Probarly your phone is bricked yes.
You say you tried everything and nothing worked, then i think there is no option left. Maybe put it in the fridge or something for like 10 minutes?
To all:
I'm sure, its hspl 2.08, pic of bootloader on its way.
I tried Stock ROM from sd. Stock oben AND provider one.
Tried 2 different PCs. Will try XP 32bit when possible.
Please tell mehr, that here's a german Euthanasie a jtag device... or pleeeeease name another option...
Thanks...
Oh my god, Not "Euthanasie" i'm so sorry...
Damn autocorrect... meant "with"...
Have you tried this version: http://forum.xda-developers.com/showpost.php?p=5279236&postcount=4
to reflash HSPL2.08
Please fill in the blank(s):
Your device was working fine, and you could flash anything. But recently you _________________ and now you can't flash anything.
Dblfstr said:
Have you tried this version: http://forum.xda-developers.com/showpost.php?p=5279236&postcount=4
to reflash HSPL2.08
Click to expand...
Click to collapse
Tried it. Outcome:
:/
Marvlesz said:
Please fill in the blank(s):
Your device was working fine, and you could flash anything. But recently you _________________ and now you can't flash anything.
Click to expand...
Click to collapse
... recently I tried to flash a whole new ROM. RadioROM was ok.Task29 went good, MAGLDR had problems. First time stuck at 4 % (Connection Error 262 (?)), second time at 96 % (also connection error), third time I held the data cable in the port, not too strong, but it worked this time. MAGLDR booted, but didn't show any options, just the header. So i did another Task29. From this time on, nothing worked anymore. :/
Anyone?
Thanks in advance!
EDIT: Also trying another sd-card atm, doesn't seem to work...
Sorry for double-posting,
but i was able to re-flash radiorom via sd. maybe this helps.
Drowzz said:
Probarly your phone is bricked yes.
You say you tried everything and nothing worked, then i think there is no option left. Maybe put it in the fridge or something for like 10 minutes?
Click to expand...
Click to collapse
This is the most stupid bit of dangerous "advice" I've ever heard. Not only is a phone not "bricked" as long as the bootloader is working, but more importantly, "put it in a fridge" has never done anything good. It's an urban legend. If you feel like it you can try it on a broken harddisk right before getting out the black candles and the chicken blood, but it's completely useless.
schousta said:
but i was able to re-flash radiorom via sd. maybe this helps.
Click to expand...
Click to collapse
Have you tried a different USB cable? Everything points to the connection, maybe your phone's USB port is shot.
Wouldn't this have been solved when flashing over sd-card?
RadioROM worked this way, whole stock package does not.
Tried different usb cables, different pcs. and different stock roms over sd.
so chances are good it's not bricked, if the bootloader works? I mean, it even boots to the green htc logo on white bg....
thanks
EDIT: Also, usb-port worked fine before flashing, it also works now, bootloader recognizes "USB".
EDIT2:
MTTY changed nothing. Task29 was succesfull (it seems), tried task 2a (that should format the WHOLE thing, like i unterstood) and 28, too, seemed succesfull, too, but my problem remains.
and why the hell can i flash a radio from sd but not a full stock rom? sd card is formatted in fat32 and 2 gig sized... tried all official roms...
and hspl still throws this error....
EDIT3:
Set up a VM with Win XP 32 bit. HSPL doesn't throw an error now, but it seems to take forever to install. Almost 10 Minutes and counting.
is this normal?
Didn't work.
Dont know what else to try, if nobody answers...
Think about sending it in to get JTAGed (Bootloader rewritten...)
Dr_Grip said:
This is the most stupid bit of dangerous "advice" I've ever heard. Not only is a phone not "bricked" as long as the bootloader is working, but more importantly, "put it in a fridge" has never done anything good. It's an urban legend. If you feel like it you can try it on a broken harddisk right before getting out the black candles and the chicken blood, but it's completely useless.
Click to expand...
Click to collapse
Why? I've seen it working. A friend bought a broken HD2, the seller said he couldn't flash anything and he had problems with camera and games before. So after dozens of tries, he put it into the fridge for half an hour and managed to flash magldr and a new rom. Well, the motherboard was faulty and he couldn't do almost anything because the phone suffered constant freezes and restarts when doing anything else than looking at the homescreen, but well, the fridge helped him a bit.
USB Port on the phone, USB Port on the computer, USB Cable, Drivers in the computer, Firewall or similar host security software on the computer - these are some of the things I'd double-check.
But a ROM in nbh format should still flash from SD- what exactly happens, does it not find it or not complete the flash? Does it throw any error code?
And did you see any bad blocks while on mtty?
ph03n!x said:
USB Port on the phone, USB Port on the computer, USB Cable, Drivers in the computer, Firewall or similar host security software on the computer - these are some of the things I'd double-check.
But a ROM in nbh format should still flash from SD- what exactly happens, does it not find it or not complete the flash? Does it throw any error code?
And did you see any bad blocks while on mtty?
Click to expand...
Click to collapse
No bad blocks, will check it again.
As said, USB-Port on phone seems ok to me, used 2 different drivers on 2 different pcs with 2 different data cables and 2 different OS. Firewall and Antivir disabled.
When flashing from SD leoimg.nbh seems to be found but it gets stuck at the grey screen with the blue "loading...". forever. no error code, not even an option to confirm or cancel the flash. cancelling the loading process with voldown failed. tried three different sd cards and all official stockroms that could possibly come in question for my phone.
But why was I able to flash the latest radiorom again?
schousta said:
No bad blocks, will check it again.
As said, USB-Port on phone seems ok to me, used 2 different drivers on 2 different pcs with 2 different data cables and 2 different OS. Firewall and Antivir disabled.
When flashing from SD leoimg.nbh seems to be found but it gets stuck at the grey screen with the blue "loading...". forever. no error code, not even an option to confirm or cancel the flash. cancelling the loading process with voldown failed. tried three different sd cards and all official stockroms that could possibly come in question for my phone.
But why was I able to flash the latest radiorom again?
Click to expand...
Click to collapse
Beats me. How long it you wait for the full ROM to flash though? I know you have tried a bunch, and am sure you would have waited long enough, but asking just in case. It might take as much as 10 minutes or more.
But ya, at the moment JTAG seems to be your best bet.
waited for almost 1,5 h now for an sd flash...
jtag seems more and more acceptable...
If tag is available, go for it.
There are a few variants of this problem, that I think of under the umbrella name of "stuck radio"
Usually its the radio that gets stuck, but sometimes the spl gets stuck too, or sometimes just the spl. Either way, some types of flash work whilst others don't (radio works hspl doesn't for example, or custom roms flash stock rooms dont ), or a flash seem to work but nothing changes, (hspl gives hacked it but spl doesn't change,or the flash hangs...
My guess is two causes, some being corruption of the software, some actual hardware...bad blocks at a critical area of memory perhaps.
There are one or two success threads with this family of problem, but hundreds with no successful outcome. Sometimes just flashing the oldest correct rom from SD does it, sometimes freezer trick works, (not an urban myth), sometimes just trying again and again works. Often though, nothing does, so if jtag is an easy option I'd take it.
Be warned though, it could be hardware, in which case it may not work.
schousta said:
... recently I tried to flash a whole new ROM. RadioROM was ok.Task29 went good, MAGLDR had problems. First time stuck at 4 % (Connection Error 262 (?)), second time at 96 % (also connection error), third time I held the data cable in the port, not too strong, but it worked this time. MAGLDR booted, but didn't show any options, just the header. So i did another Task29. From this time on, nothing worked anymore. :/
Anyone?
Thanks in advance!
EDIT: Also trying another sd-card atm, doesn't seem to work...
Click to expand...
Click to collapse
^This.................. with that v
samsamuel said:
If tag is available, go for it.
There are a few variants of this problem, that I think of under the umbrella name of "stuck radio"
Usually its the radio that gets stuck, but sometimes the spl gets stuck too, or sometimes just the spl. Either way, some types of flash work whilst others don't (radio works hspl doesn't for example, or custom roms flash stock rooms dont ), or a flash seem to work but nothing changes, (hspl gives hacked it but spl doesn't change,or the flash hangs...
My guess is two causes, some being corruption of the software, some actual hardware...bad blocks at a critical area of memory perhaps.
There are one or two success threads with this family of problem, but hundreds with no successful outcome. Sometimes just flashing the oldest correct rom from SD does it, sometimes freezer trick works, (not an urban myth), sometimes just trying again and again works. Often though, nothing does, so if jtag is an easy option I'd take it.
Be warned though, it could be hardware, in which case it may not work.
Click to expand...
Click to collapse
Looks like we have a winner ....
You said "flashing a Radio was OK" .. so we shouldn't be having a problem there. Also, a task29 went good, too.
You started having those problems during MAGLDR, but after you held the cable, everything went fine.
So in other words, during attempt 1 & 2 of MAGLDR flashing, you pulled the cable.
I know that pulling the cable midst a radio flash will 99% cause a brick.
Same with ROM with a Radio (but less chance).
But MAGLDR, I don't really know, maybe sam will help ?