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!
Hey, I have a somewhat major issue. I'd absolutely LOVE to be referred to any thread that exists to solve my issue. I just feel my problem is so bifurcated that no one resolution I've found quite fits the needs of my idiocy.
5 Days ago I got the HTC ONE with the Sense UI. Needless to say, I wasn't a fan of being stuck with the Blinkfeed, and lack of 4.2, so I went over to the lighter side of Android and put the Google Play Edition on my HTC ONE (AT&T).
This went well! I was running the GPE and had a blast, but I decided I wanted to return the phone and get the black one. Problem is...I needed it to look as it did out of the box, all unadulterated and such.
I attempt to restore it, accidentally delete OS, accidentally screw myself out TWRP, ontop of having NO nandroid backups.
My phone will either A. Boot to the HTC loader screen with the red disclaimer at the bottom, or B. Boot into the HBOOT screen by holding Power / Down Volume where it says ***TAMPERED*** / ***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013, etc. <-- Lol what?
Anyways, I'm stumped as to how I go about fixing this and loading stock AT&T sense. I've tried to ADB push command ROMS on, but instead when I type ADB push I get a long list of commands, rather than any kind of success / lag of loading the ROM as other guides have pointed out.
When I FASTBOOT USB nothing pops up mounted. Upon going to USB mounted items, the Android device is recognized as a CD-ROM, not as a mass media device. When I launch recovery it goes into the screen where the phone is displayed with a green arrow circle. I've tried the ADB push command (with and without caps) and nothing occurs, both at the regular HTC boot logo and the short-lived recovery screen, only to display a red triangle with an ! mark in it's center (indicating no recovery loaded, I'm guessing).
HTC device manager doesn't recognize the device either, and suggests it's locked. This is highly frustrating and I'm sure the resolution is simple, but the problem is finding the right one(s) and subsequent steps needed.
I appreciate any and all help.
Try following this see what happens.... https://www.youtube.com/watch?v=n_KBYx0xuAs&feature=youtube_gdata_player
Sent from my HTC One using xda premium
tylerdurdin said:
Try following this see what happens.... YOUTUBE
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
It didn't work initially, I had tried that video a couple of days ago. I did however get it to work.
I was running Windows 8, so first I needed to install drivers for Windows 8, by deleting the HTC from Device Manager and disabling driver verification. Doing this made the phone recognize in RUU.exe
The next step was an error code 155, suggesting my RUU was for the wrong model. Seeing as how the device was unlocked, I had to change directory to my android sdk and type "fastboot oem lock"
This fixed the error code 155, and the rest is history. Back on stock AT&T Sense 5.
Thank you for the link, had you not suggest it (and me attempt it a second time) I would have completely written off the method.
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.
Hello all! I know this is an old issue and the phone that I have is as old as life it's self but I hope that I can find some help here! I know there are sever threads covering this issue but I have not found any that covers the ENITRE issue that I am having.
Okay, now for my problem....
Of course my phone died (battery). I put it on the charger and powered it up. The phone stuck on Sprint screen for several days. This is the second time this has happened. The first time I was unable to use recovery but I was able to do a factory reset. THIS TIME I am unable to do anything. On factory reset, the phone goes to green icon and then it turns into the red exclamation. Same thing with recovery. I have tried the wipe/factory reset...I get an error there "E:can't open /cache/recovery/command" and I get that on all options in Sys recovery menu. I have read several threads on using fastboot but I have learned that there is more to it that plugging in the USB and recovering the phone.
To help answer some of the questions here are the details on the HBoot menu:
****Locked****
Shooter XC Ship S-On RL
HBoot - 1.58.0000
Radio - 1.09.00.0108
OpenADSP - v02.6.0226.00.0217
eMMC-boot
The phone has never been rooted and everything is stock.
I have seen that it can be recovered through Hboot menu but I'm not deep into this side of things so I will need detailed instructions if possible. I have an HTC Evo 3d and my PC is Mac OSX.
Same problem
I was about to post about my problem, but yours is very similar and like any good forum go-er I checked to see if there were any recent problems like mine.
I am running
**locked** shooter s-on hboot v 1.58 eMMC -boot from may 17, 2012.
I have never rooted the device or tampered with it in any way. I thought about it, but got a newer phone.
I recently got into computer programming and wanted to see what can be done with this old tech with still relevant hardware.
after starting the device it got into the OS , took me to my homescreen like normal then failed horribly after 10 seconds, once i slid the ring up.
it then got stuck at HTC screen, so i tried the bootloader, which works, so i went for a factory recovery. get the red triangle, so i look into rooting.
turns out that if i hadnt checked usb debugging and unlocked already, i cant get in to do anything. is this a soft-brick hard-brick case?
i feel there is hope, but the lack of response to OP after this time leaves me disappointed. I've spent many hours trying to find a solution to this problem, but it is way beyond me.
i tried finding signed copies of PG86IMG.zip for hboot 1.58 to no avail, only option is RUU which won't find the phone on windows 10. drivers are out of date, perhaps.
Installing linux now to hopefully get access to that file system.
Would really appreciate the help, devs. this is a great device would be a shame that NOT tampering with it would leave me and OP with a brick.
thanks for reading and thanks in advance for consideration and advice.
dunno, maybe try this
http://forum.xda-developers.com/showthread.php?t=1653777
virgin evo 3d has no downloadable current ruu to flash, and you guys are s on which won't let you flash older ruu to reset your system. which makes it difficult to fix.