Ok, I've looked and looked but I seem to be missing my clues.
I bought an Amaze from a friend who told me the battery just died on him one day. I'm not sure what all he did, but I have been unable to get it to boot, it just boot loops at the white HTC screen.
I have installed all the drivers to get the phone to work, running Windows 7 Home Premium 64, and neither adb or fastboot detects the device. I'm using the stock cable, a stock battery, basically it looks like this phone is as plain as the day it was updated by a light user. I have experience with rooting and unlocking bootloaders, but I can't make anything happen when I am unable to detect the device with my tools. Since the device has been bootlooping since I got it, I have been unable to see if USB debugging is enabled or not, but I am certain this behavior indicates that it is disabled. I need a way around this.
I am able to get into HBOOT, and the information for the device is as follows:
***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-v02.6.0.2226.00.0202
eMMC-boot
Mar 15 2012, 21:46:51
HBOOT USB PLUG
<VOL UP....
...select item
FASTBOOT (switches into FASTBOOT mode, but is unable to recognize the device)
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
Do I need to update the HBOOT? Am I missing something with my software?
I am trying a new machine in the meantime.
Just download the stock ruu(not to sure if it matters if you use the ics or gb one) and place it on the external sd in the root directory. Rename it to PH85IMG.zip and flash from the bootloader. Might as well do it since the boot loader is locked.
Sent from my HTC_Amaze_4G using xda app-developers app
ce3jay said:
Just download the stock ruu(not to sure if it matters if you use the ics or gb one) and place it on the external sd in the root directory. Rename it to PH85IMG.zip and flash from the bootloader. Might as well do it since the boot loader is locked.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Ok, trying that now, I'll let you know in about an hour how it goes
hoey2011 said:
Ok, trying that now, I'll let you know in about an hour how it goes
Click to expand...
Click to collapse
same issue tryed installing ruu not sure if i did it right but wont boot past htc screen
The last HTC device I owned was the G1, and there was no RUU flashing.
Sadly, I have become rusty, I work too damn many hours to keep up anymore.
How would I go about flashing the file I need to get out of this bootloop? I am having a lot of trouble getting the phone to the bootloader once I tried whatever I thought it was that would flash the first .zip I tried (an ICS .zip that was identified as a stock image, and I selected the "RECOVERY" option in the bootloader.
I'm way to exhausted to figure this out tonight.
hoey2011 said:
The last HTC device I owned was the G1, and there was no RUU flashing.
Sadly, I have become rusty, I work too damn many hours to keep up anymore.
How would I go about flashing the file I need to get out of this bootloop? I am having a lot of trouble getting the phone to the bootloader once I tried whatever I thought it was that would flash the first .zip I tried (an ICS .zip that was identified as a stock image, and I selected the "RECOVERY" option in the bootloader.
I'm way to exhausted to figure this out tonight.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1679486
You can't flash the RUU in recovery. After you have downloaded the RUU, renamed it, and placed it on the ext-sd card...press and hold VOL DN + Power to get into the bootloader. It will then search for the specified file, when it is done searching it will ask you to continue the operation, and it will begin to flash the file.
You'll want to make sure that you have "hide known file extentions" disabled/unchecked in windows, to ensure that the file is not named "PH85IMG.ZIP.ZIP".
ce3jay said:
You can't flash the RUU in recovery. After you have downloaded the RUU, renamed it, and placed it on the ext-sd card...press and hold VOL DN + Power to get into the bootloader. It will then search for the specified file, when it is done searching it will ask you to continue the operation, and it will begin to flash the file.
You'll want to make sure that you have "hide known file extentions" disabled/unchecked in windows, to ensure that the file is not named "PH85IMG.ZIP.ZIP".
Click to expand...
Click to collapse
Just rename it PH85IMG, the extension isn't relevant since it's automatically there to begin with, all files are done with required format so as to make it simpler.
hoey2011 said:
The last HTC device I owned was the G1, and there was no RUU flashing.
Sadly, I have become rusty, I work too damn many hours to keep up anymore.
How would I go about flashing the file I need to get out of this bootloop? I am having a lot of trouble getting the phone to the bootloader once I tried whatever I thought it was that would flash the first .zip I tried (an ICS .zip that was identified as a stock image, and I selected the "RECOVERY" option in the bootloader.
I'm way to exhausted to figure this out tonight.
Click to expand...
Click to collapse
Just think of this as flashing a DREAIMG.nbh file on your G1. The RUU is exactly the same as NBH files. Boot into fastboot and let the phone find the PH85IMG.zip file
Ok, so I'm finally home from work. This was my shortest week since I started in late June, and it was 48 hours. Eesh. Anyways, here's the update.
When I first got the phone, I urgently ordered two anker 1900mah batteries and put a Saturday rush delivery on it
The batteries arrived today while I was at work. My girlfriend opened them for me and didn't wanna break the included charger because it's a little tricky so I told her to try and charge it in the phone. She plugged it in, and it did it's usual few blinks of the orange led and then solid orange for a while before the led turned off completely. I was telling her what the phone was doing while it was happening, over the phone lol Needless to say, this phone has old SW on it. I was able to guide her to successfully booting into the bootloader, the only accessible function of the phone ATM. I was rather impressed because we are totally opposite, left brained me and right brained her, and she caught on to the process quickly, given the special modifications needed because the phone is a bootloop mess.
I told her to leave it on the bootloader, and allow the phone to "charge", or so I thought. At least the unit will power on with a charged battery, and I know the device isn't a lemon, DOA. I am currently loading the oldest available ruu for the phone, the PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip from here. I am also charging a battery in the provided charger from Anker.
I have previously been able to boot into the bootloader, but given my exhaustion, I didn't realize that the bootloops I encountered after the successful bootloader attempt were happening even though I had placed the RUU on a blank sdcard, and I didn't think about putting the card in while the device was on, instead of starting it up with the card already in it. Duh
I am giving it another go. Right.... meow.
I received the
Code:
Main Version is older!
[COLOR="Red"]Update Fail!
Press <POWER> to reboot.[/COLOR]
error I've been hearing about.
Referring back to the OP, and the information I provided there, which version ruu do I need to look for to match this HBOOT version?
EDIT:
I decided to try the latest one from the thread I linked before, and it is currently updating. Furthest progress I've made so far!
Ok, so I started the update, and got the list of 18 stages.
I pressed <VOL UP> to start update, then watched very closely and my result is this:
[1] BOOTLOADER - OK
[2] BOOT - FAIL -PU
[3] SBL1 - UPDATING (STAYS HERE)
[4] nfc
[5]....
.
.
.
.
.
.
[18] RADIO_CUST
This is where I am stuck.
I will do some reading into what the Fail-PU means, but if anyone feels gracious enough to hook me up with an answer I'd be much obliged
hoey2011 said:
Ok, so I started the update, and got the list of 18 stages.
I pressed <VOL UP> to start update, then watched very closely and my result is this:
[1] BOOTLOADER - OK
[2] BOOT - FAIL -PU
[3] SBL1 - UPDATING (STAYS HERE)
[4] nfc
[5]....
.
.
.
.
.
.
[18] RADIO_CUST
This is where I am stuck.
I will do some reading into what the Fail-PU means, but if anyone feels gracious enough to hook me up with an answer I'd be much obliged
Click to expand...
Click to collapse
Usually, a Fail-PU error means your internal memory is borked. There is no way to recover from that in general. It is essentially bricked, but not a true brick in a sense though. There are some things you can try, but they have low chances of succeeding.
EDIT: Seeing as it is a Locked, S-ON device, you'd be better off claiming warranty on the device.
hoey2011 said:
Ok, so I started the update, and got the list of 18 stages.
I pressed <VOL UP> to start update, then watched very closely and my result is this:
[1] BOOTLOADER - OK
[2] BOOT - FAIL -PU
[3] SBL1 - UPDATING (STAYS HERE)
[4] nfc
[5]....
.
.
.
.
.
.
[18] RADIO_CUST
This is where I am stuck.
I will do some reading into what the Fail-PU means, but if anyone feels gracious enough to hook me up with an answer I'd be much obliged
Click to expand...
Click to collapse
i was having the same roblem what i did was unlocked it using the devtool and then using cmd i relocked it and then flashed the ruu. file the one that worked for me was the third one down i just fixed my phone kid u not like 2 min ago
heres where i downloaded it
http://forum.xda-developers.com/showthread.php?t=1617644
make sure u are locked/re locked with s on
Ok, instead of continuing this mission, I instead decided to get really drunk with my girlfriend and my brother and his girlfriend last night. Soon, off to the flea market for some native american cultural festival. But for now, I'm going to give it another shot.
I'm using PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
Which is the 3rd one down on the list. I'll go down the whole list, hell even download files from Russia to get this phone to boot. There is no warranty in this case, so my choices are:
1. Boot it and get it functional again so that I can use it
2. Sell it for parts
hoey2011 said:
Ok, instead of continuing this mission, I instead decided to get really drunk with my girlfriend and my brother and his girlfriend last night. Soon, off to the flea market for some native american cultural festival. But for now, I'm going to give it another shot.
I'm using PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
Which is the 3rd one down on the list. I'll go down the whole list, hell even download files from Russia to get this phone to boot. There is no warranty in this case, so my choices are:
1. Boot it and get it functional again so that I can use it
2. Sell it for parts
Click to expand...
Click to collapse
There may be no T-Mobile warranty, but there is a HTC warranty on the device, provided that it isn't longer than a year old.
I think the eMMC chip failed.
OK so the eMMC is out. Is this soldered to the board or can it be solved by cracking it open and throwing in a replacement ?
Sent from my LG-P999 using xda app-developers app
hoey2011 said:
OK so the eMMC is out. Is this soldered to the board or can it be solved by cracking it open and throwing in a replacement ?
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Did you read my last post? Most likely, HTC will replace your device if it's still in warranty.
Ok, I called HTC, and the device is still under warranty from them. I will either have the failed component replaced, or a replacement device sent. In the disclaimer they mention that some things could void the warranty, but I swear to you, the phone looks like it was just peeled out of the plastic.
So, I will continue to use my own cracked screen G2X until this device gets fixed/replaced and returned. I ship it out tomorrow. I want to expedite the shipping and whatnot, but I already know that it might take it's sweet time anyways. I do warranty/insurance computer repair for a living for companies like Best Buy, Walmart, Circuit City, etc. If you've ever heard of device insurance, then you know the name Asurion. Well, the volume of the laptop repair business we get is enough to keep me from staying up to date on methods for the various devices I am interested in. The rabbit hole is so deep in technology everywhere you look, you have to be able to properly ask the community for an answer to a problem from time to time.
Thank you everyone!
Related
First off, I must apologize and say. Yes, I know there are all ready two other posts just this week on 'Did I kill my phone, Is it dead etc.'
So, to make a long story short.
After much research, I started at the ppcgeeks.com forums, then ppckitchen.org and finally made my way over here. I decided it was time to start working on updating my phone.
First off; I downloaded the wrong link and flashed the Olipro 1.20 boot loader on the phone, instead of the 2.4x version that is being used now. No big deal, I then got into boot loader mode and went to flash a stock rom to fix the issue. The rom had an error in the middle and reset. Then my phone reset. It went back into boot loader mode and then after using titan_exitbl.exe it booted to the standard HTC screen. After a moment now at this screen it will display the HTC logo and No Radio in red. After much reading I found that I could simply flash my 512mb MicroSD card, and did. And I placed the TITAIMG.nbh file on the root. (that is the only thing on the card) to upgrade the radio. But now when I try to restart into boot loader mode (power, camera, reset) it only resets and does not go into boot loader mode. I can perform a hard reset and go through the prompts there, but after it completes it simply brings me back to the HTC logo, and No Radio.
There is no connection via Active sync, nor through the USB, so I can not use mtty to edit anything on the boot loader end.
I have done quite a bit of reading and I figure this probably has been asked before, but is there a way to get my phone to get back to boot loader mode so I can load at least a stock rom onto it?
I don't know a whole lot about troubleshooting phones considering I have only had mine for a few weeks. However I have worked for Geek Squad for 3 years so troubleshooting is kind of in my nature.
Have you tried putting it in bootloader mode without your SD card in there? If there is something wrong with the .nbh you have on it and it keeps trying to load it when in bootloader, that could be your problem. I would remove the SD card and try bootloader, at which point you should be able to flash via usb.
Worth a shot at least.
Flash a new bootloader like 2.47 via sd. Then start loading radio and rom from there.
flipzmode said:
I don't know a whole lot about troubleshooting phones considering I have only had mine for a few weeks. However I have worked for Geek Squad for 3 years so troubleshooting is kind of in my nature.
Have you tried putting it in bootloader mode without your SD card in there? If there is something wrong with the .nbh you have on it and it keeps trying to load it when in bootloader, that could be your problem. I would remove the SD card and try bootloader, at which point you should be able to flash via usb.
Worth a shot at least.
Click to expand...
Click to collapse
Yes I have tried with and without the SD card in the phone. I have also tried with and without the phone connected to a USB cable.
I cannot flash anything to the phone because i cannot establish a connection to the phone via ActiveSync.
Did you try what I suggested? Can you get to just the bootloader screen? Hold power and camera then push reset at same time for bootloader.
drewcam888 said:
Did you try what I suggested? Can you get to just the bootloader screen? Hold power and camera then push reset at same time for bootloader.
Click to expand...
Click to collapse
That is the problem. I have tried that. power, camera, and reset. And any combination of other button, SD card in/out, USB in/out, and anything else i can think of...
The bootloader screen will Not come up.
What can the phone do? Kinda sounds like it might be bricked.
drewcam888 said:
What can the phone do? Kinda sounds like it might be bricked.
Click to expand...
Click to collapse
I know, I hope it is not. This is my phone for work, and my boss is pretty pissed that I might have just bricked a phone he just paid for.
It will turn on from the power button, i can reset it normally with the reset push switch. (it then returns to the HTC logo, and No Radio in red). I can also do the 'bootloader' reset, but this does not bring it to the bootloader, it simply acts as a standard reset. I can also do a 'hard' reset, both of the select keys, and the reset switch. It will then boot into the 'do you want to hard reset your phone' prompt, and it will let me go through those steps that would normally hard reset the phone. After the reboot when that is finished it again goes to the HTC logo and No Radio. So, with that, I sure hope that some part of the bootloader is in tack.
Thank you for your help so far.
Are you sure you are holding both the camera and power button at the same time and then pushing reset button while still holding?
psycopyro182 said:
Yes I have tried with and without the SD card in the phone. I have also tried with and without the phone connected to a USB cable.
I cannot flash anything to the phone because i cannot establish a connection to the phone via ActiveSync.
Click to expand...
Click to collapse
From what it sounds like, you're trying to run the bootloader with and without the SD card in. The problem is, it sounds like you don't have a working file actually on the SD card. It also seems that since you cannot make an ActiveSync connection, you aren't able to transfer files to and from the card.
Do you have a microSD card reader?
Check this out: http://wiki.xda-developers.com/index.php?pagename=TitanRecentHome
Particularly Section II.2.A. That may fix your problem.
Hope this helps!
Oh and if it doesn't something you said about your boss having 'just' paid for your phone. If its new enough... w-a-r-r-a-n-t-y!
He can't follow those suggestions on the wiki exactly because he cant get a usb connection. But I agree he needs to load the 2.47 on his card using a adapter then try bootloader again.
Did you try EnterBL.exe?
DustinEarnhardt said:
From what it sounds like, you're trying to run the bootloader with and without the SD card in.
Oh and if it doesn't something you said about your boss having 'just' paid for your phone. If its new enough... w-a-r-r-a-n-t-y!
Click to expand...
Click to collapse
I cannot even get the bootloader to come up. Yes I know that I am pressing both buttons and hitting Reset.
And as for Warranty, Will they warranty a phone that has the updated bootloader on it? I know there is a utility to Re-flash your phone to stock, but well, i cant even get mine to do anything at this point. I dont want sprint to tell me that they will not warranty it because I have 'tampered' with it, or 'voided the warranty'.
bitserve said:
Did you try EnterBL.exe?
Click to expand...
Click to collapse
I did not know there was such a tool.
A direct link would be great. That sound like what i need to get out of this mess.
Heres the deal, if you can't get it to go to bootloader, the carrier probably can't either....
I think the enter_BL only works if active sync works, but I could be wrong.
I've never seen a phone yet, or heard of one for that matter that boots as far as yours does yet doesn't go to a bootloader screen when reset properly. It does sound pretty messed up.
More than likely, if you go into the store and say "Hey this is messed up because I tried to update the bootloader on it" you'll get some pretty quizzical looks. They'll more than likely take your phone in the back, not do a thing with it, and then issue you a replacement (if they have one in stock) or mail you one as soon as possible.
It does sound like you may have created a brick, but luckily this one is replaceable. Consider it a "lesson learned" for the next one.
(My apologies if I offend any VZW store employees. I sure there is a rare breed of highly competent and capable technicians out there, but I have yet to meet one in my area.)
Boots Up?
Does your phone boot all the way up where you can explore your SD card on your phone? If you can PM me and I may have a solution for you if your bootloader allows you to flash by SD card.
Brick = New Phone
DustinEarnhardt said:
More than likely, if you go into the store and say "Hey this is messed up because I tried to update the bootloader on it" you'll get some pretty quizzical looks. They'll more than likely take your phone in the back, not do a thing with it, and then issue you a replacement (if they have one in stock) or mail you one as soon as possible.
It does sound like you may have created a brick, but luckily this one is replaceable. Consider it a "lesson learned" for the next one.
one in my area.)
Click to expand...
Click to collapse
So, I walked into the store, and simply said. "I have insurance, what do I need to tell you in order to get the phone fixed." "what do you mean?" "Well i have my phone here, it is totally bricked, the bootloader is toast, and there is no radio or rom, and it will not connect to activesync. So, if i need to come back and tell you my phone is stolen i can."
"Um ok? bricked? bootloader?... Here, let me see it"
(Lucky for me my company had just purchased about a dozen phones from this store, and the techs were happy to work with me)
The tech took the phone in back, and he and another tech looked at it, tried to hard reset, tried the enter bootloader key press. tried to plug it in. Then they both scratched their heads with a completly dumbfounded look on their faces. One of them walked to the closet, grabbed a new phone and brought it to me and said. "Congrats, this is the most screwed up phone I have seen come in here. Here is a brand new one, We will have to send this one back to corporate."
So, now shiny new phone in hand.
I can say simply "Lesson Learned"
Thanks for all of your help guys.
Think you've broken your phone? Read this to return it back to normal.
I've seen a lot of questions about people accidentally screwing up their phones or doing something similar around here and on the OG Evo forums. This thread is for those of you who want to return it back to normal. This is also useful to redirect people to if they have those questions.
If your phone won't start up at all and the LED won't light up at all when it is plugged in:
-Take out battery and put it back in
-If that doesn't work, swap out a battery with one you know works
-If that doesn't work, take out the SD card and try again
*If taking out the SD card fixed it, your SD card is bad and you need a new one.
-If that doesn't work or you know it isn't the battery or SD card, your phone is probably bricked.
If your phone doesn't start up but a red LED blinks when you plug it in:
*Download Android ADB Files if you don't already have them
-Plug your phone in to your computer. With a terminal/cmd, navigate to /android-sdk-(OS You're Using)/platform-tools and type "adb reboot"
-If that doesn't start up your phone, try the steps before except this charge your battery or replace with a working battery
*If your phone doesn't get get past the HTC splash screen, use "adb reboot bootloader" instead of "adb reboot" so you reboot into bootloader.
If your phone starts up but gets stuck at the HTC splash:
-Go into bootloader with vol-down+power and go to recovery. Wipe everything and then flash a ROM or backup from there that you know has worked before
-If that doesn't work, flash this from bootloader: http://forum.xda-developers.com/showthread.php?t=1193540
-If you can't access your SD card, replace it with a working one
If your phone won't go into recovery:
-Flash the TWRP PG86IMG through bootloader again:
http://forum.xda-developers.com/showthread.php?t=1192077
-If that doesn't work, try the S-OFF tool again and reflash the recovery
-If that doesn't work, try putting back S-on (download fastboot and type "fastboot oem writesecureflag 3" or "fastboot oem lock" into cmd/terminal) and then flashing PG86IMG. Then try S-offing again and flashing the recovery.
If your phone won't get past the boot animation:
-Go into bootloader with vol-down+power and go to recovery. Wipe everything and then flash a ROM or backup from there that you know has worked before
If your phone gets bootloops:
-Pull the phones battery and put it back in, then:
Go into bootloader with vol-down+power and go to recovery. Wipe everything and then flash a ROM or backup from there that you know has worked before
-If that doesn't work, flash this from bootloader: http://forum.xda-developers.com/showthread.php?t=1193540
If anything else strange is happening to your phone:
-Reboot phone
-If that doesn't work, wipe data and go back to a working ROM/Recovery
-If that doesn't work, flash the PG86IMG RUU:
http://forum.xda-developers.com/showthread.php?t=1193540
If you want more accurate instructions on how to fix a problem, ask in this thread.
It's nice that you're trying to help people out, but I'm sure that everyone does all this anyway when they have seemingly unfixable problems lol
freeza said:
It's nice that you're trying to help people out, but I'm sure that everyone does all this anyway when they have seemingly unfixable problems lol
Click to expand...
Click to collapse
Ure right, but this could help some noobs. Should be sticky imo.
- Coz i just saw it in 3D with the Shooter -
dashrink said:
Ure right, but this could help some noobs. Should be sticky imo.
- Coz i just saw it in 3D with the Shooter -
Click to expand...
Click to collapse
Yeah it should definitely be a sticky. Surprising even with all this information all the n00bs still ask the same damn questions about stuff that has been posted here time and time again
I have HBOOT 1.5 and suffering from stucking at splash screen. In fact, before stuck at splash screen, I did not tried to s-off, rooted, and flash any roms. Just a fully reboot result in stuck at splash screen. I have tried every method you mentioned above, just stuck at the splash screen:-(
I googled all the world, and someone said maybe eMMC chip damaged? It is happened on EVO 4G, but maybe also on EVO 3D? I hope it is not true, I always hope my situation is just a soft brick, anyone can tell me if it is possible brick the phone( stuck at the splash screen) due to eMMC chip damaged? Thanks in advance!
freeza said:
It's nice that you're trying to help people out, but I'm sure that everyone does all this anyway when they have seemingly unfixable problems lol
Click to expand...
Click to collapse
Heh, you'd be surprised with all the threads about people asking how to fix their phone after 'x' happened.
subaochen said:
I have HBOOT 1.5 and suffering from stucking at splash screen. In fact, before stuck at splash screen, I did not tried to s-off, rooted, and flash any roms. Just a fully reboot result in stuck at splash screen. I have tried every method you mentioned above, just stuck at the splash screen:-(
I googled all the world, and someone said maybe eMMC chip damaged? It is happened on EVO 4G, but maybe also on EVO 3D? I hope it is not true, I always hope my situation is just a soft brick, anyone can tell me if it is possible brick the phone( stuck at the splash screen) due to eMMC chip damaged? Thanks in advance!
Click to expand...
Click to collapse
I guess something hardware related could only be the case then. If you've tried everything you could, that is probably the case. Go to sprint and tell them something happened during an OTA. (IK it is hardware related, but that will still get you a better chance of them replacing it)
If you want to have S-On for when you take it back to sprint, open up a terminal and type "fastboot oem writesecureflag 3" and it will remove -revolutionary- and change s-off to s-on.
Although I have figured this out through other posts, etc.....
+1 for sticky
would of been great to be reassured there is a light at the end of tunnel if
I messed up before I jumped into rooting/flashing. And a good place to calm the nerves when you bootloop for the first time....
Sent from my clean sharp shooter
HBoot 1.50 Softbrick
My phone is bricked!
But yay for fixability, (and your optimism: I vote for stickying your post!)
It WON'T:
Go into Recovery (and it's HBoot 1.50)
Let me touch the screen, or buttons.
Bring up the start-up unlock screen.
It CAN:
Recognize when charging / when the battery is in;
Recognize the power button to turn the screen on/off.
Boot up to the main page where icons come up (But only the status bar is seen)
And Shake to take pictures! I accidentally took my first, being the screen I can get to.
Probable Causes:
I think I froze something I shouldn't have (Settings widget?), with Ti Backup.
Or that senseless Rom I put in... Now it doesn't sense me! All the thing wants to do is take pictures of its selfish self.
Solutions?
Thanks!
You're responses are much appreciated!
RUU
/10char
I vote for sticky, too.
I am no noob. I didn't do anything to my phone prior to bricking. I had my phone fully charged in the evening and woke up to a brick. The phone worked great from the time I bought it ... great the whole time it was rooted ... great with each iteration of SteelH's ROM. Then I woke up to a brick.
Even though I knew all of the steps to take (and did each one to no avail) I still felt helpless and started a thread in Q&A praying there was something to make it come back to life.
Now I'm just sad.
RemWhale said:
My phone is bricked!
But yay for fixability, (and your optimism: I vote for stickying your post!)
It WON'T:
Go into Recovery (and it's HBoot 1.50)
Let me touch the screen, or buttons.
Bring up the start-up unlock screen.
It CAN:
Recognize when charging / when the battery is in;
Recognize the power button to turn the screen on/off.
Boot up to the main page where icons come up (But only the status bar is seen)
And Shake to take pictures! I accidentally took my first, being the screen I can get to.
Probable Causes:
I think I froze something I shouldn't have (Settings widget?), with Ti Backup.
Or that senseless Rom I put in... Now it doesn't sense me! All the thing wants to do is take pictures of its selfish self.
Solutions?
Thanks!
You're responses are much appreciated!
Click to expand...
Click to collapse
Can you get into the boot loader at all? I've always heard that if it powers on it can be fixed. Also see if ADB works and look up a list of commands. A full data wipe should get you back up and running.
An RUU sounds like something I should put on my SD card; What is /10char?
Where do I find them?
@ Drewmungus:
I can get into boatloader, and fastboot, but the recovery is shot; it just restarts the phone. When I reboot the phone, should I try to adb/push something?
Many Thanks for you responses!
RemWhale,
Here is the fix (which was also above):
Download TWRP 1.0 and read the instructions on installing it on your phone. Once it is installed, recovery should work. If it doesn't,
Boot into bootloader with vol+power down. Then hit fastboot and connect your phone to your computer. Download the PG86IMG in the OP, and flash it how you would on hboot 1.5.
Problem from bad freezing or Recent ROM
yousefak said:
RemWhale,
Here is the fix (which was also above):
Download TWRP 1.0 and read the instructions on installing it on your phone. Once it is installed, recovery should work. If it doesn't,
Boot into bootloader with vol+power down. Then hit fastboot and connect your phone to your computer. Download the PG86IMG in the OP, and flash it how you would on hboot 1.5.
Click to expand...
Click to collapse
After all this, my battery shorted or something, but I did get a new one from Sprint today. I tried it out these solutions! My report:
Recovery through SD Card:
For newest versions: teamw.in/project/twrp/67
Successfully put PG86IMG.zip and recovery-twrp-shooter-1.1.1.img onto my SD card, and went to Bootloader; it said "Updated succesfully.";
when I restarted my phone, I still could ONLY see the background pic and status bar, but nothing else. It was the same.
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU failed - Error 155 - Unknown Image Error:
One of these error messages will appear when you'd use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, It means I need to download the correct RUU version and try again. But where?
Factory Reset
Nothing. I still get MY emails, which you can see in the attached picture of the screen I get to below.
Re-Unlock Bootloader...
Take out SD Card; Cmd: "fastboot oem lock" - Cmd: "fastboot flash unlocktoken Unlock_code.bin"
(No icons on home page at all? How strange...) Hey! I'm back in!
Made a Phone call! Installed some widgets! Restored contacts!!!!
The day is saved; All is well.
Not able to tell if I have any ROMs on it at the moment...
It appears I had the wrong RUU and/or PMG86.zip; I have HBoot 1.50; is there one for my newer version? Should I start a new post for my resolved situation? BTW, thanks for trying! Please add "Re-Unlock Bootloader" as a resolution.
Please, Thank me if his helps you too! Others will find be more hopeful.
meatgel said:
I vote for sticky, too.
I am no noob. I didn't do anything to my phone prior to bricking. I had my phone fully charged in the evening and woke up to a brick. The phone worked great from the time I bought it ... great the whole time it was rooted ... great with each iteration of SteelH's ROM. Then I woke up to a brick.
Even though I knew all of the steps to take (and did each one to no avail) I still felt helpless and started a thread in Q&A praying there was something to make it come back to life.
Now I'm just sad.
Click to expand...
Click to collapse
Try Re unlocking the Bootloader -That was the only thing that could solve my problem! It erased the problem, whatever it was - Let me know if it works!
RemWhale said:
Try Re unlocking the Bootloader -That was the only thing that could solve my problem! It erased the problem, whatever it was - Let me know if it works!
Click to expand...
Click to collapse
It was a brick. I couldn't power it on and the charge light wouldn't come on. I changed batteries, changed power cords ... the guys at the Sprint store did the same stuff and then took it apart to see if it was water damage (LOL). They said they'd never seen one that wouldn't even show the charge light for a second.
I got a replacement in the mail. Hboot 1.50.
RemWhale said:
After all this, my battery shorted or something, but I did get a new one from Sprint today. I tried it out these solutions! My report:
Recovery through SD Card:
For newest versions: teamw.in/project/twrp/67
Successfully put PG86IMG.zip and recovery-twrp-shooter-1.1.1.img onto my SD card, and went to Bootloader; it said "Updated succesfully.";
when I restarted my phone, I still could ONLY see the background pic and status bar, but nothing else. It was the same.
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU failed - Error 155 - Unknown Image Error:
One of these error messages will appear when you'd use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, It means I need to download the correct RUU version and try again. But where?
Factory Reset
Nothing. I still get MY emails, which you can see in the attached picture of the screen I get to below.
Re-Unlock Bootloader...
Take out SD Card; Cmd: "fastboot oem lock" - Cmd: "fastboot flash unlocktoken Unlock_code.bin"
(No icons on home page at all? How strange...) Hey! I'm back in!
Made a Phone call! Installed some widgets! Restored contacts!!!!
The day is saved; All is well.
Not able to tell if I have any ROMs on it at the moment...
It appears I had the wrong RUU and/or PMG86.zip; I have HBoot 1.50; is there one for my newer version? Should I start a new post for my resolved situation? BTW, thanks for trying! Please add "Re-Unlock Bootloader" as a resolution.
Please, Thank me if his helps you too! Others will find be more hopeful.
Click to expand...
Click to collapse
Well, did you try going into recovery at all? I should have included that you should have reflashed the ROM and the kernel to fix it. That probably would have gotten you fixed after the first step.
usb does not work
i flashed the miui rom and now my phone has no usb so i cant do any commands i cant use the rom i had to restore a back up of an old rom and still no usb no usb in fastboot nothing and im not sure what to do its not the cables
babybear293 said:
i flashed the miui rom and now my phone has no usb so i cant do any commands i cant use the rom i had to restore a back up of an old rom and still no usb no usb in fastboot nothing and im not sure what to do its not the cables
Click to expand...
Click to collapse
Did you try another cable? Are you sure its not the cable?
Plug in the USB while the phone is off and tell me if you can do 'adb restart'. If your phone starts, that means the USB works it should be fixable by flashing the PG86IMG.
If it doesn't work when the phone is off, there is something wrong with your USB port or the cable you are using. There could also be something wrong with your comp/usb power source.
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
phermes1 said:
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
Click to expand...
Click to collapse
Well, not sure about the installation issues...but the reason the phone died is because you have CM recovery. Known issue .. probably a hundred threads just not recently because people have either switched or don't let their phone run down. Phone can't charge from CM recovery and you need to switch back to Amon Ra recovery. http://forum.xda-developers.com/showthread.php?t=1434532
Basically, pull battery and then replace and hold volume down and power at the same time to boot into bootloader. Plug phone into computer . Put Amon recovery img into the same folder containing fastboot. Then make sure phone is in fastbootUSB . http://forum.xda-developers.com/showthread.php?t=1339679&highlight=amon+ra
Latest is 3.15 .. so once it is placed in the right folder type fastboot flash recovery recovery-ra-vigor-3.15-gnm.img ... this will flash amon ra recovery.. then you can charge. Once charged then you can attempt to recover your rom.
Sounds like you need an external charger to get the battery a little juice. I never thought that it was possible for a battery to not be able to charge because it was super dead unit I saw it happen on a Thunderbolt. You could take the battery to Verizon and have them give it a quick charge, just to get you back on your feet or got to an electronics store and buy a charger (can always take it back). Get it to boot again then work it from there maybe flash the Stock or Leaked PH98IMG just to get back to working so you can breath again..
Getting yourself out of a jam is part of the learning curve in flashing phones.
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Great, thank you for the good info! I was about ready to toss the thing in the trash, but it sounds like there may be hope yet!
EmerikL said:
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Click to expand...
Click to collapse
I'll have to get back to you on all of that - I'm not entirely sure right now, and everything is at home. Pretty sure it was a Venasaur ROM.
I wish the mods would delete any and all links to CWM. These threads keep cropping up.
its possible you need to flash the ICS firmware patch as well and thats why its not booting
Sorry to hassle you guys with what has probably already been answered a few times. I did some searching – yes, I should have done a little more - and the results I found were all folks that had phones that would still power on to some degree. I didn’t find many where the phone was completely dead, and if I did the responses were generally, “You’re screwed, throw it out.” Issues with cwm really didn’t cross my mind, so I didn’t think to search on that.
Anyway, I appreciate the help. I’ll sit down tonight and see if I can’t figure this thing out.
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Easiest way to brick it is to take out battery while flashing a hboot haha.
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Now you will at least be able to charge your phone!! From the phone, you can select 'Bootloader' then 'Recovery' and you will boot into recovery, which will allow you to charge your battery. You can check the charge status of the battery while in recovery in one of the menus, can't remember which one. (Fun tip: you can use 'Home'/'Menu' to scroll up/down, 'Back' to go back and 'Search' to select, since the hardware buttons are so difficult to press)
Once you get the phone charged, you have a couple of options. Since you stated you wanted to go to stock, I'll explain the steps to get back to the state the phone shipped with.
Once you get a good charge, you will also need to re-lock the bootloader to go back to stock, which is also done in fastboot by typing:
Code:
fastboot oem lock
(Get to fastboot by Battery Pull>Battery Put Back>Power + Volume Down, all while connected to a computer, just like when doing the Recovery flash)
BACK TO STOCK::
You can do this one of two ways, either run the revert using a .zip, or as a .exe connected to your computer. Personally, (and I know I'll probably lose credibility here lol) I prefer the .zip method, although many swear by the 'True RUU' .exe method.
**Here's a little aside to get you so you can get all of these files onto your phone. There's an option in Amon RA that mounts as removable storage to your computer so you can transfer files. Select 'USB-MS toggle' and then select 'USB-MS Toggle SDCard'. Then you can transfer all the files you need before continuing.
First, download the stock "ruu" zip from here:
http://goo.im/stock/vigor/ruu/RUU_V..._1.12_9k_1.83_V_APT_release_221502_signed.zip
and you will need to rename it to PH98IMG.zip and it will need to be placed on the root of your SDCard, not in any folder. Then download the MainVer.zip from here:
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
which can be placed anywhere on the SDCard, but I would place it in the same place as the PH98IMG file for ease.
Once you have the PH98IMG file on the root of the SDCard, and have the MainVerLow zip there also, continue on.
To flash, go to the 'Flash zip' menu in recovery, and locate the setMainVerLow.zip. All this does is set the Main Version low, so hboot (or whatever) doesn't kick it back saying you can't downgrade. This flash will only take a second, and when complete, go back to the main Recovery menu.
It probably doesn't matter, but I would wipe data/factory reset again just to be safe. Do this by selecting 'Wipe' then 'Wipe ALL data/factory reset'. Once done, go back to the main Recovery screen.
Now you will want to reboot into bootloader, which I believe is under either 'Other' or 'Developer Options'
The phone will reboot, and book back into a screen similar to what you saw in fastboot. Some purple text will scroll saying stuff about looking for some file, and will find the one you just put on there and ask if you want to update now. Click the power button to confirm the update. It will show a progress bar on the side, as well as list the parts it has updated for you. It will get around halfway done or so and reboot itself, but DON'T TOUCH ANYTHING OR REMOVE THE BATTERY!!! lol it will reboot and finish the second half of the install. Once it's done, I think you need to hit 'Power' one more time to reboot, but once it does you will be rebooted and load up the completely stock ROM that originally shipped with the Rezound. Of course, from here you can go to the system update menu and update to the latest released OTA.
EDIT:: Just wanted to add, none of what I have written was developed/discovered/first-posted by me, it is the work of other, MUCH more intelligent people other than myself. So don't thank me for anything other than putting them all here lol
con247 said:
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Click to expand...
Click to collapse
Will try to do that tonight.
I need to get it to power up first. I've had it plugged in at my desk all day and no luck so far. Let me get that taken care of and I'll go from there.
See if you can borrow a friends battery. A thunderbolt or my touch 4g slide battery will work too. You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
good luck.. if you figure all this out you might like being rooted. i had several issues coming from an htc incredible to rezound the cwm was one.
Definitely get Amon Ra.
Sent from my ADR6425LVW
con247 said:
You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
Click to expand...
Click to collapse
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
phermes1 said:
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
Click to expand...
Click to collapse
might be worth your while:
http://www.amazon.com/HTC-Thunderbo...ords=htc+thunderbolt+external+battery+charger
It doesn't charge very fast, but nice to have around.
Hopefully im not too late, but click my name and look at the threads that i have started. I used a ghetto IMO method to charge a dead droid x battery. You njeed a useless usb cable and a little time. Basically you strip the red and black wires and respectively touch them to the + and - leads on your battery. This will charge it relatively fast, you only need to hold it on the battery for a minute or so, just long enough.
But use this as a last plan method, i dont know how safe this is because the voltages may go in wrong or damage the battery, but to this day my droid x still works and i got it on the release week so its relatively old.
If you can, you should get a legit charger instead but if you want it done fast, give this a try or find another way. hope i helped but just make sure that if the battery heats up if you try this, you stop immediately. That could mean that the battery is about to explode or its breaking.
hope i helped, but if you want more help there is bound to be youtube videos on how to do this.
If you try this and something goes wrong its not my problem, but i have done this before and it should work.
Here is the link to the forum i made:
http://forum.xda-developers.com/showthread.php?t=1656547
Yakuzagang5 said:
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Click to expand...
Click to collapse
Update on my efforts. The steps above are where I'm currently at - so I haven't gotten far.
I got the $5 charger as suggested, so my phone will power on and I can at least get to the bootloader screen.
For whatever reason, it will NOT power on if I follow the steps above. It won't power up when I have it plugged into the PC. I can only power it on with it unplugged. So, when I run through the command prompt to install Amon Ra, it seems to be unable to connect to the phone. It displays 'Waiting for device' and nothing ever happens. At this point, it looks like I have everything I need on the PC side, but the phone is too boogered up to communicate with it.
I'm trying the options to clear out the memory right now. The problem there is that it goes to the screen with the top hat and orange circular arrow, and just sits there forever. It never acknowledges that it's done clearing memory.
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
sethandian said:
Here is where I was at, ready to throw away the phone I ruined. I was rooted and S-ON and unlocked via HTC unlock bootloader web page. I was happily trying new things here when my phone went to all white background with green HTC letters. Wouldnt do anything. While trying to fix that I erased my backup and the software on the phone. I let the phone sit all day hoping the white backgound would go away but no. It wouldnt even power off. But I able to get into bootloader by doing this: Hold down power and volume up for 10 seconds, as soon as the screen goes blank slide finger down to volume down and hold. This got me into boot loader. I tried all the things outlined here to recover (using abd commands, fastboot *.img files nandroid backups, sideloading etc. My CID shows CWS_001 and next to the OS field is blank. Pulled the SIM and SD card to erase cache, no help. Wipe delvick, data, etc all failed with the E: unable to mount message. 2 Days gone by with not even a glimmer of recovering phone
So I went to HTC support download news (sorry cant post a link until 10 posts) and downloaded the RUU that contains the 4.4.3 update. This is an exe file that updates your phone. It failed on the first go. So I relocked the phone using wonders_never_cease M8 all in one kit, then double clicked on the RUU app again. It took off and ran. It is menu driven so I answered all the acknowledgements and got to the update screen. On that screen "current version field was blank and update to field reflected the new RUU version. The instructions tell you to put your phone into recovery mode and select fastboot. My Windows PC already had the HTC drivers loaded. I was shocked when the app began loading modules without failing. I didnt have to do anything except put attach usb cable to phone from PC and put the phone in fastboot. 10 mins later, the phone rebooted and my hated ATT logo and tune showed. Am up and running on 4.4.3 and new firmware.
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else. Thought I post this up for any other semi-noob that got into trouble and just wants a working phone. I am not sure a phone that is S-OFF would work but it doesnt hurt to try. I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. Am just happy to have a working phone. Now will make a backup in TWRP immediately. Over and out....Michael
Click to expand...
Click to collapse
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
t5620 said:
congratulations that you restore your device. the link for the RUU its already posted in the General Forum http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
also a bootable no pc version of it http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
as well as the OTA http://forum.xda-developers.com/att-htc-one-m8/general/htc-m8-4-4-3-official-ota-t2860139
Click to expand...
Click to collapse
Thanks for posting up the links.
sethandian said:
Here is where I was at, ready to throw away the phone I ruined.
Click to expand...
Click to collapse
As long as the screen comes on for this phone, its virtually always recoverable. There was never any reason to think you had to throw away the phone. Next time you are stuck, just ask for help here; as we are happy to help. You did the right thing in trying to find existing solutions. But it sounds like you did your due diligence searching and reading; and would have been justified starting a new thread and asking for help.
sethandian said:
Everything works fine on the phone (no modules missing). So it appears the "upgrade" will wipe partition and reload all the software on the phone without doing much of anything else.
Click to expand...
Click to collapse
That is precisely what the RUU does. Its a complete image, and handy for recovery purposes.
sethandian said:
I do understand HTC stopped the OTA update due to battery draining issues but the download is still available for fastboot. l
Click to expand...
Click to collapse
While the OTA has had some reports of causing battery issues, the RUU has not had any reports of such issue, and seems to be free of it.
sethandian said:
I am not sure a phone that is S-OFF would work but it doesnt hurt to try.
Click to expand...
Click to collapse
S-off does not affect whether or not the RUU will work, I don't know why folks keep saying or asking this. RUU will work whether S-on or S-off. The only difference, is that with S-on, you need to either have a LOCKED bootloader, or RELOCKED (relock it manually if you unlocked it).
Also, in general, S-off does not limit anything. It means "all security off" and enables more access, not the opposite. If anything, S-off enables more things than S-on.
Thanks for the all the info. The experience was a valuable teaching moment. Now back to playing around with the M8.
when i open into recovery and go into twmp and i go to reboot>recovery it says no os installed. my recovery is completely gone. what do?
Ok so I was searching, a lot, and found that I can turn the phone back to OEM. unfortunately every guide I have read says it needs to be s-off using firewater. When i do the "adb reboot" function it gets stuck at the htc boot screen and I cannot perform the second step in making the phone s-off. what do I do? Is my phone legitimately bricked? Like hard bricked forever?
I also ran the RUU. It goes through and when it gets to step 1 of 7 it stops and says "unknown error occurred" I go through the error recovery steps and it still does not work. Just trying to keep all the info here so you understand the situation I'm in. It also boots into recovery mode, obviously, with the power button and volume down button.
got it. could go ahead and delete post.
Don't have the thread deleted, but instead explain how you finally solved the problem so others may learn from your experiences...
-Sent from a payphone...
tttomdemaria said:
Ok so I was searching, a lot, and found that I can turn the phone back to OEM. unfortunately every guide I have read says it needs to be s-off using firewater. When i do the "adb reboot" function it gets stuck at the htc boot screen and I cannot perform the second step in making the phone s-off. what do I do? Is my phone legitimately bricked? Like hard bricked forever?
Click to expand...
Click to collapse
I know you've already sorted it out. But first, this phone is not bricked if the screen comes on. Recovering is usually not hard at all, just a matter of knowing how to do it.
Second, were you referring to a warranty claim for a phone being not bootable due to mods that you did? That isn't covered under warranty, and is immoral. Take responsibility for your actions; and don't jump the gun and think you have to get a new phone after just a couple hours of unsuccessful attempts to get the phone running. If you want to root and mod these devices, you are going to have to learn to be patient and work through little quirks like this.
Lastly, the phone needs to be bootable to perform firewater s-off.
Thanks. yea my only two friends that do this kind of **** are like seriously the most pessimistic, negative assholes I have seriously ever met in my life. They kinda just scared me into thinking it was easy to brick a phone and totally mess it up. After some research i just found all I had to do was run an RUU and make sure the phone was relocked.
seriously. they are real negative nancies.
Ok for those of you who may ever be in the situation I was in I will write up how i fixed it. very simple and took probably about 20 minutes start of download of tools to finish. This was done on windows 7 but i'm sure it is pretty similar on windows 8 as well.
In order to do this you will need to know that holding the power button AND the volume up button simultaneously emulate a battery pull and that holding the power button AND the volume down button enter recovery mode. If you are stuck in a boot screen or splash screen like I was you will need to emulate a battery pull and them immediately switch to enter recovery without actually removing your finger from the power button.
Then you need to make sure you have the right tools. you can find them at these locations.
RUU- http://forum.xda-developers.com/showthread.php?t=2757462
ADB- http://www.mediafire.com/download/5s2nfws9wkj9gyq/adb-fastboot.zip
Now you need to make sure your phone is either "***LOCKED*** or ***RELOCKED*** when you enter the recovery mode.
You can do this very easily. Plug your phone into your computer and enter recovery mode. Make sure the phone is in Fastboot USB mode and not Hboot. Open the folder titled "Android" in the adb kit you downloaded from the link above. Shift + right click anywhere on that folder(not on a file) and choose "Open command window here" type in the command window "fastboot oem lock". It will show as "relocked" after you do this and it reboots. This will allow you to run the RUU without any issues. Always make sure the phone is in "Fastboot USB" mode.
Now run the RUU executable and it will automatically pick up your phone assuming all of your drivers are in order. Just hit yes to everything and it will run through what it needs to. If you do not have a progress bar on your phone's screen as well as your computer then you messed up somewhere. start over.
If you try to do this on the At&T htc one (m8) without actually relocking it first the RUU will fail at step 1 of 7.
Good luck.
tttomdemaria said:
Thanks. yea my only two friends that do this kind of **** are like seriously the most pessimistic, negative assholes I have seriously ever met in my life. They kinda just scared me into thinking it was easy to brick a phone and totally mess it up. After some research i just found all I had to do was run an RUU and make sure the phone was relocked.
seriously. they are real negative nancies.
Click to expand...
Click to collapse
Then stay away from those guys! Sounds like they don't really know that much, wrong attitude, and you are probably already on your way to knowing what they know, if not more.
This phone is pretty hard to brick. As long as you aren't flashing hboot or radio, and don't flash anything intended for another device, its pretty difficult to brick this phone by modding it. The condition you were in was not a brick, and not even close. Some call this a "soft brick" but in my opinion, there is no such thing, its either bricked (requires opening the phone to recovery, such as JTAG or replacing motherboard) or its not. What I call it is "something is wrong with the phone and you just need to do the right steps to get running again".
---------- Post added at 11:22 AM ---------- Previous post was at 11:16 AM ----------
tttomdemaria said:
Ok for those of you who may ever be in the situation I was in I will write up how i fixed it. very simple and took probably about 20 minutes start of download of tools to finish.
Click to expand...
Click to collapse
Glad you sorted it out, so nice job.
Although RUU was probably a little overkill. RUU is a useful recovery tool, although a bit of a nuclear option. But good last resort. Since you RUU'ed, you will need to unlock the bootloader again, and flash custom recovery to get back to where you were originally (phone setup for mods) if that is the intention. If the intent was to go back to stock and stay there, RUU is a great way to do that.
You probably could have just gotten back up and running by using adb to wipe cache, re-install custom recovery and flash a ROM.