I was helping a friend fix their mytouch 4g because it was stuck on the first boot screen that says "Mytouch 4g" I tried flashing a stock rom through bootloader and after that it reached the mytouch logo screen and kept looping there then I tried a factory reset then the phone bricked itself. Now I cannot turn it on but when I connect it to my computer it shows QHSUSB_DLOAD in device manager. I have been trying to find the RUU exe to fix it but I cannot find it anywhere. What else can I do unless someone has the ruu?
No RUU will help you.
Google the name of the device you're getting, and you'll see the complexity of what needs to be done. This procedure was only finalized for Sensation. If you think you have enough technical knowledge to attempt it - good luck.
Otherwise - you have a true brick that you can't recover without JTAG.
So I have to use unbuntu and following this guide should fix it?
http://unlimited.io/qhsusbdload.htm
I do remember seeing guides that use unbuntu to fix this problem when I searched the name of the device as it is now. I will try that and hopefully it will fix it.
Yes, you should - but not blindly following. Remember that the guide deals with Sensation, so you have to adapt it for MT4G along the way, if possible at all.
well this will be interesting, hopefully I can find a similar guide but for the MT4G but how would I adapt to the MT4G with that guide?
You won't find a similar guide for MT4G, because nobody ever made one.
If you don't know what to adapt (if it's possible at all - I didn't check) - then look into JTAG repairs.
I just contacted a member of the brick movement that made the ubuntu guides for a few HTC phones and the mytouch 4g slide and he said that method won't work for this mytouch 4g. It seems to be a bad eMMC chip from what I have gathered because originally it was stuck on the white Mytouch4g screen and after a factory reset it just bricked which doesn't make sense why it would do that.
Related
I have the Android Dev Phone 1 and I had just gotten through rooting it following the wiki's instructions, I wanted to try to install Hero with the Rosie UI so I was following these directions to then flash it:
http://forum.xda-developers.com/showpost.php?p=3816278&postcount=3
But I was in the process of doing that, I had two micro SD cards with the proper updates on each, and when it came time to switch the cards(I didn't hit any buttons or anything by accident) I switched them, hit Alt +X, nothing happened. Nothing. I tried it a few more times and still nothing. All other combos of letters and trying to get it to respond in any way did nothing. So I pulled the battery out and now I cannot get past the G1 screen. It won't do the boot where you hit the camera button and power or the home + power boot. It just sits at the black screen with the G1.
I tried getting the ADB devices to recognize it and no dice. I can't get it to do anything other than go to the black screen. I tried searching the forum and I scoured google but all the things I could find were where you could get some kind of input beyond the screen.
I'm kinda mad as I just got this phone and paid $450 some bucks for it, can someone help me out? I'm on Vista X64 and Ubuntu X64. Thanks in advance to anyone who can help me unbrick my $450 paperweight.
you need to update the from the original recovery, which im guessing you still have to swithch to one of these. http://forum.xda-developers.com/showthread.php?t=455860 then you can update to the SPL H
Hard SPL is the recommended one. Which in turn will give you the list feature Alt-x
Truculent said:
I have the Android Dev Phone 1 and I had just gotten through rooting it following the wiki's instructions, I wanted to try to install Hero with the Rosie UI so I was following these directions to then flash it:
Click to expand...
Click to collapse
So is your phone a "PVT" or "DVT"? If it's a DVT and you tried to install Haykuro's SPL 1.33.2005, then you are almost certain to have a paperweight. I believe it's mostly consensus that the DVT phones brick if you go to that SPL. There are a bunch of threads here on it.
Truculent said:
I have the Android Dev Phone 1 and I had just gotten through rooting it
Click to expand...
Click to collapse
Aren't ADPs rooted out of the box?!
You have to install the new SPL and JF's recovery image before you to to Hero/Rosie.
ADP's certainly do provide root out of the box, so no need to go to the trouble.
@Truculent:
Sounds like this is what happened;
1) installed rc29 for tmobile branded dream (mistake),
2) rooted that and probably installed some older radio image (or left original radio),
At this point, though you wasted time and risked screwing it up, you were probably still OK. The fact that you would even attempt the previous steps says something though...
3) reversed the sdcards and accidentally installed SPL before radio upgrade.
Its bricked and nothing you can do for now. Most likely this will require a physical disassembly and reprogramming to repair.
Honestly, anybody who could make a bonehead move like rooting a prerooted device by installing a root-locked firmware shouldn't be messing with SPLs. In other words, you deserve what you got. Particularly since you DONT NEED the modified SPL for what you were attempting! There's a system/apps to SD approach to fitting it with the standard disk layout.... which you could have stepped to *directly* from a stock ADP1 without ANY risk of bricking.
lbcoder said:
ADP's certainly do provide root out of the box, so no need to go to the trouble.
@Truculent:
Sounds like this is what happened;
1) installed rc29 for tmobile branded dream (mistake),
2) rooted that and probably installed some older radio image (or left original radio),
At this point, though you wasted time and risked screwing it up, you were probably still OK. The fact that you would even attempt the previous steps says something though...
3) reversed the sdcards and accidentally installed SPL before radio upgrade.
Its bricked and nothing you can do for now. Most likely this will require a physical disassembly and reprogramming to repair.
Honestly, anybody who could make a bonehead move like rooting a prerooted device by installing a root-locked firmware shouldn't be messing with SPLs. In other words, you deserve what you got. Particularly since you DONT NEED the modified SPL for what you were attempting! There's a system/apps to SD approach to fitting it with the standard disk layout.... which you could have stepped to *directly* from a stock ADP1 without ANY risk of bricking.
Click to expand...
Click to collapse
I thought it was rooted when I bought it, but I was not able to install programs that needed root. They told me I needed root. I'm kicking myself right now. But yes, that sounds like what I did. This is my first time of doing anything with cell phones, I'm trying to learn. I didn't see anything regarding the ADP's so I figured the T-mobile G-1's were the same, my fault. I spent hours reading this forum and the wiki and didn't see anything concerning this kind of thing.
Is there any way I can do the disassembly and reprogramming? I did DD-WRT stuff on my routers, is there a way to JTAG or something similar to these phones? Oh, and this is a PVT phone.
Root is hidden from programs for security reasons (keep programs from going nuts and messing up your system), but a little bit of "adb shell" would show it to you.
I really doubt that PVT or DVT matters. The distinction was guessed at by trying to follow the pattern of bricking BEFORE it was determined that the radio version was the common factor. Even then, there was really no conclusive info showing that DVT boards were more prone to bricking, I think there was a sample of about 14 devices bricked back then, of them 6 were PVT and 8 were DVT.... you see how weak the evidence is? It would make a statistician cringe. See this: http://forum.xda-developers.com/poll.php?do=showresults&pollid=1523 - only the number of PVT bricks has increased because everyone got scared of trying to write the bootloader to DVTs, but you can see that there are some DVTs that flashed fine. 2 at least.
As for hooking up a jtag... there was someone looking into that, but I haven't heard of any repair procedures yet. Note that though it hasn't been done yet, there is no question that it is possible since the chips must have been programmed by some means initially.
I got my magic and bricked it today.Any thoughts to unbrick i am crying please somebody help. i cant face my parents or any person at my place.
advise on what u did before it got rooted..
step by step
I followed the mytouch guide and saw my device was 32b and went ahead for 32b (dont know if it was necesarry) and applied radio as update and i am fked up. fk me
charnsingh_online said:
I followed the mytouch guide and saw my device was 32b and went ahead for 32b (dont know if it was necesarry) and applied radio as update and i am fked up. fk me
Click to expand...
Click to collapse
The same thing happened to me. I completely bricked it. Couldn't get into fastboot. Phone wouldn't even turn on, computer wouldn't recognize it, LED's would not come on when plugged into charger or phone. It was that bad. I just went to the T-Mobile store and said that it got like that over night when I left it charging. They sent me a new one under buyer's remorse. It worked out great for me. As for how it did it, I did it the same exact way you did. When applying the 32B radio I didn't flash the radio right. Idk if you read Amon_Ra's guide on how to root it. He didn't specify at first how to flash the radio so when guessing I broke it. Then a few hours later he then posted how to flash it. Just my luck! But I now have a new mytouch and when I followed his directions exactly for the 32B, it went off like a charm. 32B is necessary if you are going to run Hero roms because it is expecting the extra RAM to push it harder. Not so sure about Non-Hero Roms but I believe it might be the same thing. If your phone is as bad as mine, just use the same excuse. They will think it is a defective handset and send you a brand new one, not a refurb. I tried everything to get back into fastboot but I couldn't get the damn thing to start up. It was a sad day. We now have 3 rooted myTouch's that are working great. Hope this helps.
try removing battery for 1 hr and power it up again
You should PM that bloke who's got "have a problem with Android? PM me" in his sigfile. I'm sure he'll fix you right up.
(sorry mate, I couldn't resist! )
Loccy said:
You should PM that bloke who's got "have a problem with Android? PM me" in his sigfile. I'm sure he'll fix you right up.
(sorry mate, I couldn't resist! )
Click to expand...
Click to collapse
haha how ironic
if you have insurance on the phone...smash it and send it back. make sure the mobo is broken though and not just the screen. if not, well...sorry to hear about your new paper weight.
trying my hardest not to flame here, but.....
specify the guide you followed... a link to it would be a good start
state exactly what steps you did
state what conditions have occured (eg. stuck on logo, wont even power, etc)
state the actions you have taken to try to repair (sometimes you can make things worse but at least we'd know what you've done)
it's rather inconsiderate to not take the time to post these essential points.
you are expecting us to spend more time thinking and explaining your problem then you have bothered. not cool.
i concur..i try my best not to flame people, but in some situations, such as this one, a flame is appropriate....
i have bricked my HTC Magic while i was trying to flash this ROM (http://forum.xda-developers.com/showthread.php?t=549591)
but i guess i missed/skipped and had the wrong radio, so then after that all i get is a HTC Magic boot up screen and nothing else.
non of the button combinations work, i cant get to fastboot or recovery using the buttons.
is there anything i can do? any suggestions?!
P.S I DO have a Nandroid Backup (if that can help)
zidane said:
i have bricked my HTC Magic while i was trying to flash this ROM (http://forum.xda-developers.com/showthread.php?t=549591)
but i guess i missed/skipped and had the wrong radio, so then after that all i get is a HTC Magic boot up screen and nothing else.
non of the button combinations work, i cant get to fastboot or recovery using the buttons.
is there anything i can do? any suggestions?!
P.S I DO have a Nandroid Backup (if that can help)
Click to expand...
Click to collapse
Nandroid backups are useless unless you can get into recovery, or perhaps fastboot through a PC. But if you're bricked like these guys...then that's not possible.
korndub said:
i concur..i try my best not to flame people, but in some situations, such as this one, a flame is appropriate....
Click to expand...
Click to collapse
I don't think a flame is necessarily appropriate... Obviously the guy is distraught and doesn't know what else to do and is looking for support - not the time to get on him for not following the right protocol.
I understand your frustration, but try to understand his as well... if you don't want to help, then just let it go - somone else most likely will.
I bricked in the first hour, just think how i feel looking at the phone. $600 for a phonedummy
you gonna tell us what you did to brick it? what radio you applied? What methods you used?
ok now that you say my nandroid is useless
is there anything else i can do to get my phone working again?
if you replaced battery you cant relsoved becoz phone bricked is bricked
farbird said:
try removing battery for 1 hr and power it up again
Click to expand...
Click to collapse
if you replaced battery you cant relsoved becoz phone bricked is bricked
Hey all,
First of all, I would like to thank everyone for the work they did rooting the htc dream. I couldnt get it to work and would like to revert to the original state. My phone keeps getting stuck at the rogers screen.
I can however, load the phone up in fastboot mode. I tried flashing it with the original radio and recovery image, but it still gets stuck at the rogers logo.
Thanks
Rohit
After reading my post I think I should provide more info on my situation.
I was following the rooting guide (http://forum.xda-developers.com/showthread.php?p=4280573#post4280573) perfectly till step 15. Instead of finding another ROM to install, i think I reapplied update.zip from step 10. When it asked me to restart it would just get stuck at the rogers logo.
I can still get into Fastboost mode (from what i've read means I have not bricked my phone).
I was just hoping to replace the rogers branded android with the stock android.
If i manage to fix my phone, I promise to be nice to my phone and will make a donation to this forum.
Thanks in advance.
Rohit
Did you ever manage to fix your phone?
I have a HTC magic with HTC Hero ROM it was running fine. Until I tried to update redio using this http://android.modaco.com/content/h.../03-09-hero-roms-radios-in-update-zip-format/. After I download and update the radio. I can not boot the phone all its display is an icon with an box and arrow pointing to a phone. I attached my icon image. Please maybe somebody give me an idea. How to boot it back. Thanks in advance.
Chris
ccfiel said:
I have a HTC magic with HTC Hero ROM it was running fine. Until I tried to update redio using this http://android.modaco.com/content/h.../03-09-hero-roms-radios-in-update-zip-format/. After I download and update the radio. I can not boot the phone all its display is an icon with an box and arrow pointing to a phone. I attached my icon image. Please maybe somebody give me an idea. How to boot it back. Thanks in advance.
Chris
Click to expand...
Click to collapse
The radio images at modaco are for the HTC Hero. I was wondering whether or not this radio update would work on my Magic... Try looking in the development section for the newest original magic firmware RUU (it's the official HTC method of updating). This update contains a correct magic radio image (amongst other things). The RUU package should include a readme on how to apply the update. The screen you are seeing on your phone is the original recovery screen so at least we know that your device is not bricked!
Hi,
I'm on the same situation .... my HTC magic not boot. But on my case is impossible run the update menu.
how can I install the original Radio for saphire?
thanks for your suggestions,
This is interesting.
I was considering flashing that EUROPEAN radio to my spare phone (HTC Dream) to basically take the 50/50 chance to see whether or not it would actually register and comply with the device.
So, it's confirmed that this method DOES NOT WORK...correct?
Which radio did you flash again? I'll double-check the link. And which update did you attempt to apply? The 2.1 Hero version of the build...? As in the "enhanced" port. That won't be available for the Sapphire (32B) for a few days. Paul @ Modaco-ANDROID said he is working the kinks out, then fashioning an enhanced version for the Sapphire and apparently the Dream as well.
Hi,
thanks for your reply ... but now, my problem is recover the htc.
I try to entry on the Recovery tool and run fastboot, etc ... and nothing work's ....
thanks for your help
Hmph. That's not a good sign.
jimi01 said:
Hi,
thanks for your reply ... but now, my problem is recover the htc.
I try to entry on the Recovery tool and run fastboot, etc ... and nothing work's ....
thanks for your help
Click to expand...
Click to collapse
Not to say you shouldn't be on the optimistic side of this...but from what you've stated; sounds like you have just created a $300 paper weight! I'm sorry.
If you cannot boot into recovery, cannot run fastboot, and from what I understand you cannot power on your device into a normal loading...that's a serious set of problems. Potentially permanent ones.
NOW, all things considered...have you tried ADB? Can your computer detect the device to run ADB? If so, you might have some luck in that department to uninstall whatever you've done or possibly re-flash the appropriate radio and SPL.
Search tutorials. I cannot offer further assistance for your particular situation. It's in your hands now.
I'm in the same boat.
I'd be interested to find out what this screen actually is. I thought it might be a recovery image but adb devices does not return any information.
None of the usual key combinations to get to hboot or fastboot or recovery will work.
I have the latest rogers update ruu and will try to run that and see if it works.
Wasn't able to use the rogers updater as it wouldn't see the phone.
Spoke to HTC support who seemed not to know what the box with the arrow pointing to a phone screen meant.
They are collecting tomorrow and will re flash it for me.
Whether someone will be able to tell that I was flashing a new, apparently incorrect, radio we'll just have to wait and see.
radio
i have the same thing i tried to install a different radio on the cyn 10.1.1 rom and i had teh same recovery logo. i tried everything. i thing our phone is bricked. i called rogers and they will send me a new phone as i told them i used the rogers update tool. next month ill see if they will charge me for the damage or not.
My phone is back with HTC for repair. Initially they said they would re flash it, but now I understand that they are replacing the main board. It looks like the problem is pretty terminal!
I have same problem, is there any solution for this?
same situation here,any help?
For now there is no solution, maybe serial cable in blue led mode or jtag can help,
read about it in G1 section:
http://forum.xda-developers.com/showthread.php?t=591048
This problem is caused by failed radio rom update, I think JTAG will help, but problem is we dont have pinouts for magic. So if anyone have magic with water damage can help us finding pinouts for jtag.
jimi01 said:
Hi,
I'm on the same situation .... my HTC magic not boot. But on my case is impossible run the update menu.
how can I install the original Radio for saphire?
thanks for your suggestions,
Click to expand...
Click to collapse
Same problem , but you should go back and download your same SPL & Radio that came with your and go into fastboot and flash theme to your phone , then flash the correct recovery img for your phone model , and hopefully you are good to go , hope this helps .
PS : should be done through your PC , good luck
Magic with box.arrow problem cant go into fastboot mode!
Hello
Same problem, not posible solution?or i have to sent to Repair in warranty?
Thanks
Nicolas
Hi all,
First of all i wanted to say that i'm completely new with android and the htc thing.
But i have basic in computing and programming.
Yesterday i bought an htc dream smartphone and i really loved it. Because i'm an exploring-type of person, i wanted to try to upgrade my android version to 2.2. Im following instructions from the Cyanogen website on installing Cyanogen mod 6.0 with android 2.2. However, it did say that it requires the dangerSPL. So i googled around and found the direct link to the dangerSPL patch. But, i am so stupid that i didn't read the instruction on flashing the SPL.
So, i did flashed the dangerSPL without updating the radio and those required. Now, my htc won't boot. It turned on and just stayed at the "T-Mobile G1" screen. And no, i couldn't even get into fastboot or the recovery mode. Is this means my phone was bricked? (i do believe so)
Sadly, yes. JTAG it if you're brave enough, I doubt there's another way.
Do i have chance to repair it using JTAG? If so, would you direct me to a tutorial or anything that could tell me how to do it. I am willing to do anything to save this htc.
Wait, before i proceed to JTAG method,
I did some research about "Blue Light Mode" and try to do it by powering my htc with the trackball pressed, it did light up the blue light. Does this means anything useful?