Well, today I went into settings>about phone and found the HTC update (ice cream sandwich)
I downloaded it, and went ahead and followed all instructions. Battery life, etc.
I got the black screen with the green curved arrows, and then the phone restarted.
I then got the White HTC screen and thats where it has been stuck ever since.
I noticed the grey lettering "Quietly Brilliant" never shows up under "HTC"
So I pulled the battery.. tried again. Same thing.
Pull the battery, removed the SD card, try again, same thing.
THEN I pulled the battery, did a MANUAL FACTORY RESET by holding volume down while hitting the power button, etc.
and it still gets stuck.
Took it into Tmobile store. Then did all the same stuff and then sat their glassy eyed.
I asked for an exchange, but won't bore you with the low level of service you experience in a Tmobile store.. suffice it to say if it is of any consequence, it needs to be done over the phone.
So here I am with a phone I can't get to boot. This phone has never been rooted, it was completely out-of-the-box.
I did notice on the white DOS-like screen where you select "factory reset" that at the top it says "locked" in fuschia colored text.. not sure if that has any significance.
I'm about to call customer service and start that whole fun time, but I'm posting here hoping that one of the genuii that frequent these forums can help me get the phone working so that I don't have to go days without a phone and pay god knows how much to get a new one shipped to me. (the guys at the store were of no help getting me a replacement)
I have no idea what to do to get it running at this point..
Thanks for any help!
PS: My phone has never been rooted or altered in any way.. completely stock
Try this.
Pull battery, remove sim card. Leave out for 5 minutes. Don't put sim back.
Put battery back (without sim) and hold volume and power and instead of factory reset choose recovery.
Cross fingures and hopefully it recovers into ics sense 3.6. Worked for me.
I am not rooted, fully stock out the box also. And this worked
Sent from my HTC_Amaze_4G using Tapatalk 2
tiki66 said:
Well, today I went into settings>about phone and found the HTC update (ice cream sandwich)
I downloaded it, and went ahead and followed all instructions. Battery life, etc.
I got the black screen with the green curved arrows, and then the phone restarted.
I then got the White HTC screen and thats where it has been stuck ever since.
I noticed the grey lettering "Quietly Brilliant" never shows up under "HTC"
So I pulled the battery.. tried again. Same thing.
Pull the battery, removed the SD card, try again, same thing.
THEN I pulled the battery, did a MANUAL FACTORY RESET by holding volume down while hitting the power button, etc.
and it still gets stuck.
Took it into Tmobile store. Then did all the same stuff and then sat their glassy eyed.
I asked for an exchange, but won't bore you with the low level of service you experience in a Tmobile store.. suffice it to say if it is of any consequence, it needs to be done over the phone.
So here I am with a phone I can't get to boot. This phone has never been rooted, it was completely out-of-the-box.
I did notice on the white DOS-like screen where you select "factory reset" that at the top it says "locked" in fuschia colored text.. not sure if that has any significance.
I'm about to call customer service and start that whole fun time, but I'm posting here hoping that one of the genuii that frequent these forums can help me get the phone working so that I don't have to go days without a phone and pay god knows how much to get a new one shipped to me. (the guys at the store were of no help getting me a replacement)
I have no idea what to do to get it running at this point..
Thanks for any help!
PS: My phone has never been rooted or altered in any way.. completely stock
Click to expand...
Click to collapse
Sorry to here that, just install the official leaked ics ruu through hboot/bootloader.
1. Download the ruu.
2. Place the file on external sd card but rename it PH85img.zip
3. Go into hboot by removing the battery and put it back in, then hold power and volume down.
4. Just follow the onscreen instructions and let it do its thing, (LET IT DO IT'S THING)
http://www.filefactory.com/file/5p9....17DC_30.78.550L.15_release_259626_signed.zip
Below.is the thread where you can get more info about this
http://forum.xda-developers.com/showthread.php?p=711823
Good luck
Sent from my HTC_Amaze_4G using Tapatalk 2
If you follow through with his^ instructions on installing the stock RUU, word of advice, NEVER FACTORY RESET OR BATTERY PULL ON YOUR FIRST BOOT UP AFTER INSTALLING A NEW ROM OR UPDATE, be patient, give the ROM some time to move in, organize it's desk, stock the fridge up and put the toilet paper back, it was in the process of doing so when you interrupted it multiple times and even took away it's luggage in the end, so flash the stock ruu he indicated and let it do it's thing. That seems to be your best chance since everything is stock, not sure if the phone would let you, but you can pull the update file from the post in the general forum and try flashing that since it should be the same and it's the official update.
Ouch... TMO must have used the same bad mirror I used when first trying to flash ics
Sent from my HTC_Amaze_4G using Tapatalk 2
Hey Seriously, THANKS guys.
You are more help than anything Tmobile can do thats for sure.. just got off the phone with a level 2 guy, and the best i can get out of them is to pay them $45 to get me a refurb Amaze by Thursday.
And even then, I'd still probably have to try and get ICS on it.
Forgive me for this, its been awhile since I've been twiddling with my Android phone (not since my original G1 back in the day)
..so I'm a bit rusty of the terms and where to get the files, etc. So please, if you can, walk me through these steps with URLs to files if possible:
1) "Download the ruu." - where do I get that? I assume that is a file(?)
2) "Place the file on external sd card but rename it PH85img.zip" ok self explanatory
3) "Go into hboot by removing the battery and put it back in, then hold power and volume down." - OK I've been there before
4) "Just follow the onscreen instructions and let it do its thing, (LET IT DO IT'S THING)
xxxxxxx626_signed.zip" (forum wont let me post real url)
OK is that URL above the address to get the RUU file? Just want to make sure I'm using the right thing..
ALSO- when putting that file on the External SD CARD- I am putting my SD card into a flash card reader and inserting it into a usb port on my computer (since i cant get my phone to boot)
however, the Amaze has got this weird thing where when you mount to phone as a drive, you actually get TWO removeable drives that pop up- one had the DCIM folder (photos, etc) and the other had some other stuff.
When I put my SD card into the reader on my computer, I'm only getting one of these right now- the one with the DCIM containing the photos.
Is this where I need to place the PH85img.zip file?
Thanks for your help- sorry I'm rusty
wise words
elwaxman said:
Sorry to here that, just install the official leaked ics ruu through hboot/bootloader.
1. Download the ruu.
2. Place the file on external sd card but rename it PH85img.zip
3. Go into hboot by removing the battery and put it back in, then hold power and volume down.
4. Just follow the onscreen instructions and let it do its thing, (LET IT DO IT'S THING)
http://www.filefactory.com/file/5p9....17DC_30.78.550L.15_release_259626_signed.zip
Below.is the thread where you can get more info about this
http://forum.xda-developers.com/showthread.php?p=711823
Good luck
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Dark Nightmare said:
If you follow through with his^ instructions on installing the stock RUU, word of advice, NEVER FACTORY RESET OR BATTERY PULL ON YOUR FIRST BOOT UP AFTER INSTALLING A NEW ROM OR UPDATE, be patient, give the ROM some time to move in, organize it's desk, stock the fridge up and put the toilet paper back, it was in the process of doing so when you interrupted it multiple times and even took away it's luggage in the end, so flash the stock ruu he indicated and let it do it's thing. That seems to be your best chance since everything is stock, not sure if the phone would let you, but you can pull the update file from the post in the general forum and try flashing that since it should be the same and it's the official update.
Click to expand...
Click to collapse
...and a funny
glacierguy said:
Ouch... TMO must have used the same bad mirror I used when first trying to flash ics
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Flash stock rom then take battery out for an hour.
OK here's what I did.
I downloaded the big zip file, renamed it to PH85img.zip and placed it on a NEW SD card that I formatted to FAT32 (in case my other one turned out to be corrupt)
I then put that card in the phone, and held the down vol + power and got into the white screen.
It said:
ph85diag.zip
..no image!
ph85diag.nbh
.. no image or wrong
then it found the PH85img.zip and started loading it up (blue vertical progress bar in upper right that completed)
then it started "checking" PH85img.zip (yellow progress bar in upper right that completed)
then it put me back to the main menu of the white screen.
I wasnt sure what to do there so I hit the "fast boot" opetion and got a submenu where I selected "power down"
this shut the phone down.
I then powered back on normally and got the white HTC screen, and it is now sitting on that screen doing seemingly nothing (been there for about 8 minutes now)
What did I do wrong?
Thanks for the guidance!
When it checks the ph85img.zip it should ask you whether to perform the update or not, volume up for yes, volume down for no, be sure to download the very latest leaked file and try again, yes you place the file renamed to PH85IMG on the sd, not in any folders, give it another shot, let us know how it goes.
Hmm.. i don't think it asked me to perform the update.
I will go back to that white screen again (is that the "bootloader"?)
and see what happens.
in the meantime its been sitting on this HTC screen for 25 minutes so i think its safe to assume its stuck.
Also... Don't be alarmed, but there are a couple of qwerky actions the phone does whole updating that u may not be used to.
1) it will unzip and install the system partition about 7-10 times. It looks like its looping... But its not... Let it do its thing.
2) it may flash partitions out of order. With s=off it does, because one bootloader flashes certain partitions (including new boatloader) and then it rebooted and the new bootloader flashed the rest. It may not be so qwerky with s=on, but just in case... Don't be alarmed.
One last thing... Thanks for searching before posting. For that, we all love helping people like you
Sent from my HTC_Amaze_4G using Tapatalk 2
And please do not have your usb cable plugged in while doing this, that way it'll go to fastboot instead of the bootloader. (think I'll do a video to help everyone out lol)
OK I just ran through that progress bar on the white screen again.
after it was done "checking" PH85img.zip it went back to the main menu.. it did not ask to perform the update.
i have:
HBOOT (highlighted in blue)
<vol up> to previous item
<vol down> to next item
<power> to select
FASTBOOT (highlighted in blue)
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
note: i have my sim card removed.. will try again with it back in.
I'm wondering if perhaps there is some junk in my phone internal memory/storage that is causing the issue? Is there a way to clear out whatever may be in internal memory?
Because the sd card is a new and freshly formatted card, so it cant be that..
Dark Nightmare said:
And please do not have your usb cable plugged in while doing this, that way it'll go to fastboot instead of the bootloader. (think I'll do a video to help everyone out lol)
Click to expand...
Click to collapse
Definitely a great idea if u have time and camera... Only prob is u will have to post it like 50 different threads
Sent from my HTC_Amaze_4G using Tapatalk 2
tiki66 said:
I'm wondering if perhaps there is some junk in my phone internal memory/storage that is causing the issue? Is there a way to clear out whatever may be in internal memory?
Because the sd card is a new and freshly formatted card, so it cant be that..
Click to expand...
Click to collapse
Very unlikely
Your bootloader is "LOCKED" or "RELOCKED" right? Because it has to be for it to work
Sent from my HTC_Amaze_4G using Tapatalk 2
yup it says "locked" at the top of the bootloader screen.
i just tried the whole thing again with the sim card put back in and had the same result- just brings me back to the main bootloader screen.. should I try a "factory reset"?
one note: I didnt download the zip file from filefactory, as it was going to take 3+ hours
so i googled the filename and found a page with it available at d-h.st and grabbed that one.
I assume its the same file, but perhaps not the latest version?
tiki66 said:
yup it says "locked" at the top of the bootloader screen.
i just tried the whole thing again with the sim card put back in and had the same result- just brings me back to the main bootloader screen.. should I try a "factory reset"?
one note: I didnt download the zip file from filefactory, as it was going to take 3+ hours
so i googled the filename and found a page with it available at d-h.st and grabbed that one.
I assume its the same file, but perhaps not the latest version?
Click to expand...
Click to collapse
It seems to me you got a bad download. This was happining to me when I was trying to update to ics. I would try to download the ics leak in the devolopment section posted on may 5th by football then proceed with your steps.
Place file on sd card (not in any folders)
Rename to PH85IMG
Put sd card back in phone
Pull battery and put it back in
Volume down and power button
Sent from my HTC_Amaze_4G using XDA
thinksecretly said:
It seems to me you got a bad download. This was happining to me when I was trying to update to ics. I would try to download the ics leak in the devolopment section posted on may 5th by football then proceed with your steps.
Place file on sd card (not in any folders)
Rename to PH85IMG
Put sd card back in phone
Pull battery and put it back in
Volume down and power button
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
Hi everyone im new and this is my first post.
If is gona be helpfull to someone maybe tiki66 u can use to fix your phone or some developer find a way how to root last tmob OTA update or whatever can someone find usefull i have made copy on my pc after checking and downloading OTA tmobile update
ISC 4.0.3
sense 3.6
kernal 3.0.16-ga4fb83c
baseband 1.14.550L.17DC_30.78.550L.15D
build number 2.14.531.3 CL373265
I made copy on this way duoing this steps
i check for software update on my amaze (05.21.2012) after geting message avilable update i press download on my phone after finishing download its come up INSTALL NOW or INSTALL LATER somthing like that i did not press nothing i conect phone to my comp i search my sd for files using option search files not older then 30 min i found this file OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip i made copy on my comp then i disconect fhone from comp and i fress install on my phone. Ameze start rebooting several times maybe 6-7 time after 20-30 min phone startup and i wate extra 3-4 min then i start using my phone.
I just open account on dropbox writing this i uploading last stock OTA tmobile update for htc amaze i waiting for finishing upload on dropbox and i gona post link...
waiting...
waiting...
here is MD5checkSum
1708459a5276024e097fc89211a24e6e
waiting...
here we goo
I hope i gone help someone
ok i geting this messege
The following errors occurred with your submission:
To prevent spam to the forums, ALL new users are not permitted to post outside links in their messages. After approximately eight posts, you will be able to post outside links. Thanks for understanding!
i gona tray to post link on another way
somthing like this
h t t p : / / dl.dropbox.com/u/81034574/OTA_ICS_update_Not_RootededMay21_2012.rar
remove space betven h t t p : / / dl.dropbox....
I hope i gone help someone
tiki66 said:
yup it says "locked" at the top of the bootloader screen.
i just tried the whole thing again with the sim card put back in and had the same result- just brings me back to the main bootloader screen.. should I try a "factory reset"?
one note: I didnt download the zip file from filefactory, as it was going to take 3+ hours
so i googled the filename and found a page with it available at d-h.st and grabbed that one.
I assume its the same file, but perhaps not the latest version?
Click to expand...
Click to collapse
I also used the dev-host mirror. It was from Hasoon2000 on page 3-4 of football's second thread. Maybe try redownloading
Sent from my HTC_Amaze_4G using Tapatalk 2
Related
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
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.
Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.
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!
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.