I decided to fastboot flash the rpm.img file from the OTA update, and now the phone will no longer boot. When its plugged in, the red light on the trackpad lights up.
What can i do?
Remove battery, keep unplugged, hold volume down and power and see if you can get into hboot
what was the command you entered into fastboot?
Blue6IX said:
what was the command you entered into fastboot?
Click to expand...
Click to collapse
fastboot flash rpm rpm.img
Connecting it to the PC it displayed as a Qualcom COM port, and I installed the driver from another site. The Qualcom QDLoader 9008.
Are there any manufacturer tools used to communicate via this port to perhaps reformat the entire nand chip to correct partition errors like this?
I think you are in a situation similar to this. I did not have the guts to try flashing something on my phone. There might be something possible but you are on the wild unexplored area right now.
The good thing here: lol my phone won't boot up today, wtf happen? Tmo proceeds to replace your phone
Sent from my RubiX ICS Infused using Tapatalk
leoilios said:
The good thing here: lol my phone won't boot up today, wtf happen? Tmo proceeds to replace your phone
Sent from my RubiX ICS Infused using Tapatalk
Click to expand...
Click to collapse
Lol, best advice of the day xD
Adding more to the conversation. "This isn't the first time this has happened. can you offer any other phones?"
Well I ordered a replacement. I was hesitant in asking for another phone. And to be honest there aren't any I'd really want for T-Mobile other than the MT4GS.
First I love having a physical keyboard, I use it often.
Also Sensation has had a lot of problems, the Amaze probably wouldn't qualify for an equal exchange due to a higher price, it would be nice, but the Roms on that seem even slower.
I'm not as lucky since I'm on a second-hand no-contract phone, so no easy freebie replacement option.
I tried flashing what turned out to be a bad PG59IMG.zip (looks like maybe a corrupt upload or download, but I didn't figure that out until too late).
Phone now shows (almost) no signs of life. Looks completely dead and silent, and pressing and holding the power button does nothing. I said almost because I got the orange charging light to come on once by clicking the track pad, but the experiment did not hold up to a second try.
Any ideas, besides the usual jokes about doorstops and target practice?
wjcarpenter said:
I'm not as lucky since I'm on a second-hand no-contract phone, so no easy freebie replacement option.
I tried flashing what turned out to be a bad PG59IMG.zip (looks like maybe a corrupt upload or download, but I didn't figure that out until too late).
Phone now shows (almost) no signs of life. Looks completely dead and silent, and pressing and holding the power button does nothing. I said almost because I got the orange charging light to come on once by clicking the track pad, but the experiment did not hold up to a second try.
Any ideas, besides the usual jokes about doorstops and target practice?
Click to expand...
Click to collapse
Next time your best bet would be to check an md5 sum of a zip before its flashed. Also i think its situations like this that forces us to use the HTC Unlock tool, so we dont have the power to brick our phones when we dont know what we are flashing or dont follow simple steps to insure your not bricked. There are unbricking projects out there
Maybe this http://forum.xda-developers.com/showthread.php?t=1627881 will help, i dunno i dont read that thread because i HOPE to never end up in bricktown
Sent from my myTouch_4G_Slide using Tapatalk 2
wjcarpenter said:
I tried flashing what turned out to be a bad PG59IMG.zip (looks like maybe a corrupt upload or download, but I didn't figure that out until too late).
Click to expand...
Click to collapse
FWIW, I'm now pretty convinced that it was not a bad PG59IMG.zip. I later DL'd from the same place and did check the MD5. I thought it was corrupt because it wouldn't open in WinZip, but 7Zip handled it fine. It flashed fine on a different MT4GS.
So, I think my MT4GS just decided to die as part of that flashing process. I may give the JTAG folks a try when I run out of patience for staring at it.
wjcarpenter said:
FWIW, I'm now pretty convinced that it was not a bad PG59IMG.zip. I later DL'd from the same place and did check the MD5. I thought it was corrupt because it wouldn't open in WinZip, but 7Zip handled it fine. It flashed fine on a different MT4GS.
So, I think my MT4GS just decided to die as part of that flashing process. I may give the JTAG folks a try when I run out of patience for staring at it.
Click to expand...
Click to collapse
Well because a new download had a good md5 does not mean the first one was a good download. Which still leaves you wondering if you bricked due to not checking the md5 of a potentially dangerous zip.
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Well because a new download had a good md5 does not mean the first one was a good download. Which still leaves you wondering if you bricked due to not checking the md5 of a potentially dangerous zip.
Click to expand...
Click to collapse
In general you are right, but in this specific case I disagree. The vast majority of "bad downloads" are actually OK downloads of something pooched on the server, either a bad upload or bit rot while it was up there. A TCP download on reliable hardware is a pretty reliable thing. Since I refetched it from the same server location, it is IMHO overwhelmingly more likely to be some other problem than a bad DL.
I agree, it's still possible the first DL was bad. I'm just not inclined to think it probable.
wjcarpenter said:
In general you are right, but in this specific case I disagree. The vast majority of "bad downloads" are actually OK downloads of something pooched on the server, either a bad upload or bit rot while it was up there. A TCP download on reliable hardware is a pretty reliable thing. Since I refetched it from the same server location, it is IMHO overwhelmingly more likely to be some other problem than a bad DL.
I agree, it's still possible the first DL was bad. I'm just not inclined to think it probable.
Click to expand...
Click to collapse
You bricked your phone lol so you might want to start blaming yourself. I mean you are the careless one that wants to blame the brick on everything but the obvious. A bad download. You yourself said winzip told you it was corrupt.
Sent from my myTouch_4G_Slide using Tapatalk 2
wjcarpenter said:
FWIW, I'm now pretty convinced that it was not a bad PG59IMG.zip. I later DL'd from the same place and did check the MD5. I thought it was corrupt because it wouldn't open in WinZip, but 7Zip handled it fine. It flashed fine on a different MT4GS.
So, I think my MT4GS just decided to die as part of that flashing process. I may give the JTAG folks a try when I run out of patience for staring at it.
Click to expand...
Click to collapse
Just because you can't open the zip doesn't mean its corrupted. HTC signs there PGZIPs in a way that in most cases only bootloaders can open them.
xmc wildchild22 said:
Just because you can't open the zip doesn't mean its corrupted. HTC signs there PGZIPs in a way that in most cases only bootloaders can open them.
Click to expand...
Click to collapse
Right. That was the point I was making. I concluded the ZIP was corrupt simply because WinZip couldn't handle it. It was an HTC-signed ROM, so the WinZip failure is not meaningful.
(7Zip opens those ZIPs with no problem, but I also checked the MD5 the second time I downloaded it.)
Maybe it's due to the Alan Turing centennial stuff, but last night I witnessed some kind of Android phone religious miracle or something. Without (much) warning, my formerly dead phone sprang back to life!
CAUTION: This is a tale of uninformed adventure. If you try the same stuff, instead of the miracle of life, you might witness the miracle of smoke or other calamites.
So, there is hope. I wish I could tell you precisely how I did it, but I was just fooling around with this boat anchor, trying various desperate measures, when it suddenly greeted me with an hboot screen. In case others are in a similar "no harm in trying" state, here is the sort of stuff I was fiddling with last night.
I've tried the HTC Unbricking Project for MT4GS literally dozens separate times: http://forum.xda-developers.com/showthread.php?t=1627881 I've tried lots of variations of ways of getting the phone to be recognized (battery in, battery out; go fast, wait a while; push various buttons, push no buttons; full moon, new moon; ...). All dismal failures, so I've concluded -- rightly or wrongly -- that I don't have the kind of bricking that that stuff can cure.
Just on a whim, I thought there would probably be something I could do if I got the phone into Qualcomm download mode. That goes by various names (which is very confusing), but the phone gets recognized over USB as "QHSUSB_DLOAD". You can read a bit about that here: http://forum.xda-developers.com/showthread.php?t=1464711 I had tried this in the past without success (don't remember what techniques I tried), but I thought I would give the "wire trick" a shot. (On reflection, it might be just a mis-remembering on my part thinking that the wire trick would get me into download mode.)
You can read about the "wire trick" here: http://unlimited.io/ I only did the physical part of the wire trick, the timed shorting of the contact. I didn't run any of the software mentioned on that site. (The reason is simple: I wasn't really sure what I was trying to do. I was just trying to get the danged phone to come to life somehow. In fact, last night, I didn't even go to that site. I just remembered how to do the wire trick from reading about it some time ago. I figured that if I got any interesting result, I would study up at that point.)
Well, lo and behold, when I did the wire trick (the timing is tricky, for sure), my Windows PC made that noise like it had noticed a new USB thing. Huh? What? Totally unexpected (by me). Sure enough, Windows device manager showed it with the messed-up-device icon, and properties showed the magical QHUSB_DLOAD.
(At that point, I took a little side excursion and did the same thing with a Linux PC. I could see the phone recognized in dmesg, but no new storage devices showed up, and nothing in dmesg would match the strings that the HTC Unbricking Project script is looking for. So, I went back to Windows. I'm skipping over the frustrating part where I would sometimes go 10-15 minutes without doing the wire trick correctly.)
What Windows wanted was drivers, and it didn't know how to find them. I found and tried these: http://forum.xda-developers.com/showpost.php?p=14386994&postcount=14 (It's really sort of taking a chance installing random stuff on my PC, but you know ... adventure!) After I installed the drivers, Windows recognized my phone as a working Qualcomm something-or-other (failed to make a note of it). It also showed up as a pseudo-serial device on port COM19:.
I was getting pretty excited and started researching the many zillions of threads about what you can do once you have access to a phone in the Qualcomm download mode. Unfortunately, it turns out you can't do much unless you have some secret mumbo jumbo that is likely only had by the hardware vendors. I trolled non-stop through the waters of "maybe someone found some magical binary that does ... something", but no joy. As far as I can tell, there is no known way for us outsiders to do anything productive through this interface on MT4GS or most other HTC phones. Most advice is that if this is all you can get, your next step is JTAG.
Along the way, though, I saw many mentions of a program called QPST (Qualcomm Product Support Tool). If you search around, you can find copies of this tool, though the most recent I found was from 4-5 years ago and runs on Windows. (I didn't look very hard because I wasn't too sure what it did, and I figured I'd look harder for a newer copy if it seemed promising.) With only a little fooling around, I got the tool to recognize my phone on COM19:. There are lots of mysterious subcommands to try. However, pretty much everything I tried failed with a message to the effect that whatever-it-was wouldn't work while the phone was in "download mode". The tool comes with some hex files that might be suitable for downloading to a phone, but nothing for MT4GS (not surprising considering the age of the software). Subcommands included a couple of things with names like "reset device" and "shutdown port". I tried them; they said no-go.
When I was done with all that fooling around, I unplugged the USB from the phone, popped a battery in, and ... as I had done maybe 50-60 times since the Great Calamity ... I tried to bring up hboot. I wasn't expecting it to work, but it did! I quickly put an HTC-signed image on my SD card and popped it in. hboot recognized it and went to work on it. (I was sweating a little bit since I had no idea how much juice was in the battery. I was careless because I didn't expect anything useful to be happening.)
So, I hope someone has enjoyed this tale of adventure. I don't know if any of the assorted things I did actually led to the hboot deciding to show itself, or if it was just random. Whatever, the phone is now re-animated, and I can get back to the original hardware problem I was trying to figure out for this phone: http://forum.xda-developers.com/showthread.php?t=1664506
wjcarpenter said:
Maybe it's due to the Alan Turing centennial stuff, but last night I witnessed some kind of Android phone religious miracle or something. Without (much) warning, my formerly dead phone sprang back to life!
CAUTION: This is a tale of uninformed adventure. If you try the same stuff, instead of the miracle of life, you might witness the miracle of smoke or other calamites.
So, there is hope. I wish I could tell you precisely how I did it, but I was just fooling around with this boat anchor, trying various desperate measures, when it suddenly greeted me with an hboot screen. In case others are in a similar "no harm in trying" state, here is the sort of stuff I was fiddling with last night.
I've tried the HTC Unbricking Project for MT4GS literally dozens separate times: http://forum.xda-developers.com/showthread.php?t=1627881 I've tried lots of variations of ways of getting the phone to be recognized (battery in, battery out; go fast, wait a while; push various buttons, push no buttons; full moon, new moon; ...). All dismal failures, so I've concluded -- rightly or wrongly -- that I don't have the kind of bricking that that stuff can cure.
Just on a whim, I thought there would probably be something I could do if I got the phone into Qualcomm download mode. That goes by various names (which is very confusing), but the phone gets recognized over USB as "QHSUSB_DLOAD". You can read a bit about that here: http://forum.xda-developers.com/showthread.php?t=1464711 I had tried this in the past without success (don't remember what techniques I tried), but I thought I would give the "wire trick" a shot. (On reflection, it might be just a mis-remembering on my part thinking that the wire trick would get me into download mode.)
You can read about the "wire trick" here: http://unlimited.io/ I only did the physical part of the wire trick, the timed shorting of the contact. I didn't run any of the software mentioned on that site. (The reason is simple: I wasn't really sure what I was trying to do. I was just trying to get the danged phone to come to life somehow. In fact, last night, I didn't even go to that site. I just remembered how to do the wire trick from reading about it some time ago. I figured that if I got any interesting result, I would study up at that point.)
Well, lo and behold, when I did the wire trick (the timing is tricky, for sure), my Windows PC made that noise like it had noticed a new USB thing. Huh? What? Totally unexpected (by me). Sure enough, Windows device manager showed it with the messed-up-device icon, and properties showed the magical QHUSB_DLOAD.
(At that point, I took a little side excursion and did the same thing with a Linux PC. I could see the phone recognized in dmesg, but no new storage devices showed up, and nothing in dmesg would match the strings that the HTC Unbricking Project script is looking for. So, I went back to Windows. I'm skipping over the frustrating part where I would sometimes go 10-15 minutes without doing the wire trick correctly.)
What Windows wanted was drivers, and it didn't know how to find them. I found and tried these: http://forum.xda-developers.com/showpost.php?p=14386994&postcount=14 (It's really sort of taking a chance installing random stuff on my PC, but you know ... adventure!) After I installed the drivers, Windows recognized my phone as a working Qualcomm something-or-other (failed to make a note of it). It also showed up as a pseudo-serial device on port COM19:.
I was getting pretty excited and started researching the many zillions of threads about what you can do once you have access to a phone in the Qualcomm download mode. Unfortunately, it turns out you can't do much unless you have some secret mumbo jumbo that is likely only had by the hardware vendors. I trolled non-stop through the waters of "maybe someone found some magical binary that does ... something", but no joy. As far as I can tell, there is no known way for us outsiders to do anything productive through this interface on MT4GS or most other HTC phones. Most advice is that if this is all you can get, your next step is JTAG.
Along the way, though, I saw many mentions of a program called QPST (Qualcomm Product Support Tool). If you search around, you can find copies of this tool, though the most recent I found was from 4-5 years ago and runs on Windows. (I didn't look very hard because I wasn't too sure what it did, and I figured I'd look harder for a newer copy if it seemed promising.) With only a little fooling around, I got the tool to recognize my phone on COM19:. There are lots of mysterious subcommands to try. However, pretty much everything I tried failed with a message to the effect that whatever-it-was wouldn't work while the phone was in "download mode". The tool comes with some hex files that might be suitable for downloading to a phone, but nothing for MT4GS (not surprising considering the age of the software). Subcommands included a couple of things with names like "reset device" and "shutdown port". I tried them; they said no-go.
When I was done with all that fooling around, I unplugged the USB from the phone, popped a battery in, and ... as I had done maybe 50-60 times since the Great Calamity ... I tried to bring up hboot. I wasn't expecting it to work, but it did! I quickly put an HTC-signed image on my SD card and popped it in. hboot recognized it and went to work on it. (I was sweating a little bit since I had no idea how much juice was in the battery. I was careless because I didn't expect anything useful to be happening.)
So, I hope someone has enjoyed this tale of adventure. I don't know if any of the assorted things I did actually led to the hboot deciding to show itself, or if it was just random. Whatever, the phone is now re-animated, and I can get back to the original hardware problem I was trying to figure out for this phone: http://forum.xda-developers.com/showthread.php?t=1664506
Click to expand...
Click to collapse
I really wish I can replicate these results because I am in the exact same situation as you were, except that QPST is not registering my phone via any COM listing. I was using Uniflash, and I was trying to flash a custom ROM. A separate process was created, and boom. Download mode.
mrbubs3 said:
I really wish I can replicate these results because I am in the exact same situation as you were, except that QPST is not registering my phone via any COM listing. I was using Uniflash, and I was trying to flash a custom ROM. A separate process was created, and boom. Download mode.
Click to expand...
Click to collapse
So a quick update: I was not able to restore this bricking via the Unbricking Project. However, I did send the phone off to Mobiletechvideos, and the dude performed a JTAG. And now, IT'S ALIVE!! I had to unlock the bootloader, and get S-Off again, but hey: I got my doubleshot back.
Moral of the story: when all else fails, JTAG.
Me and my friend are currently in an argument in what the term "bricked" really means.
I am saying that a bricked device is one that is no longer functioning, like one stuck in a boot loop, BUT it is able to be fixed in many cases.
Example: When I bricked my Droid 2, I flashed a working SBF.
He is saying that when a device is "bricked" it is unable to be fixed, and is far beyond repair.
Example: When my friends mom stomped on his Evo Shift, the phone wouldn't turn on, and the device was bricked.
I understand that both of those examples are bricked (one more extreme than the other) but a device doesn't need to be beyond repair to be technically "bricked">
I would love to hear your opinion on how you view this term.
Bricked means unflashable, and you need jtag or other device to be able to fix, or not flashable or repairable through usb cable or sdcard, also a brick is when you drop it in water and it short circuits and destroys the ics, lcd etc.
Edit: brick also means if you dropped it and it now malfunctions, like lcd cracked and other crazy things happen when your using it.
Soft brick is when its stuck in a bootloop or whatever software problem that can be fixed
Hard brick is when you mess with the bootloader or something and it won't turn on BUT BECAUSE THE SOFTWARE
When its been smashed or physically damaged (ie water damage) I simply call the device "broken"
Sent from my DROID2 using xda premium
http://forum.xda-developers.com/showthread.php?t=1483113
There are two types of bricks: hard bricks are serious and can't be fixed 99% of the time (the phone is useless and might as well be a brick) and soft bricks can be. If you have a hard brick you're probably sol but if you have a soft brick there's no need to panic.
Chancee said:
http://forum.xda-developers.com/showthread.php?t=1483113
There are two types of bricks: hard bricks are serious and can't be fixed 99% of the time (the phone is useless and might as well be a brick) and soft bricks can be. If you have a hard brick you're probably sol but if you have a soft brick there's no need to panic.
Click to expand...
Click to collapse
That's not what he was asking... read the OP again...
Sent from my DROID2 using xda premium