I need some help.
I'm trying to recover a friend's Evo 3d. He tried to flash a different ROM on it, and messed it up.
I'm on Windows 7 32bit. The phone is the Sprint EVO 3D (CDMA). HBOOT is 1.50.0000 S-ON
The device is not bootlooping. I get a blank screen after the HTC logo. I don't have access to USB debugging. I can get into recovery to try to flash a different image but to no avail - I get the same screen every time. I decided to get it back to stock but I can't relock it. ADB doesn't recognize the device and the device is very much in the device manager (proper drivers and all). I would love any advice.
Thank you.
my fix method
pixel4e said:
I need some help.
I'm trying to recover a friend's Evo 3d. He tried to flash a different ROM on it, and messed it up.
I'm on Windows 7 32bit. The phone is the Sprint EVO 3D (CDMA). HBOOT is 1.50.0000 S-ON
The device is not bootlooping. I get a blank screen after the HTC logo. I don't have access to USB debugging. I can get into recovery to try to flash a different image but to no avail - I get the same screen every time. I decided to get it back to stock but I can't relock it. ADB doesn't recognize the device and the device is very much in the device manager (proper drivers and all). I would love any advice.
Thank you.
Click to expand...
Click to collapse
You can boot into fastboot by holding vol-down and power from off. Then plug in USB and run fastboot(in the same folder as adb i think) with these args
Code:
boot PATH_TO_RECOVERY.IMG
and then flash a ROM. LightsOut is a good ROM. Hope I help.
Download the RUU and get into fastboot USB. and run it. That'll reset your firmware and radios and everything.
IF it has 1.50 s-on than it's still on Gingerbread, You need to update your radios and firmware, With the 2.89 RUU
Then it'll be on ICS, and you can unlock the bootloader
Then get s-off, You shouldn't be flashing anything with s-on lol.
(You can, but get s-off it's 1 more hour of work once you get it booting)
I must have been using a faulty cable or USB port, I tried it the next day with my girlfriend's Samsung cable and "fastboot oem lock" worked immediately. Ran RUU like a champ and it is alive and working now.
pixel4e said:
I must have been using a faulty cable or USB port, I tried it the next day with my girlfriend's Samsung cable and "fastboot oem lock" worked immediately. Ran RUU like a champ and it is alive and working now.
Click to expand...
Click to collapse
good deal
Related
After attempting to S-Off the phone yesterday afternoon and failing (it is unlocked), I'm now stuck at the infamous JPbear screen with the green arrow. I've read pretty much every post I can find on recovering from it and still cannot get the phone to boot correctly.
I flashed the boot img for the rom I was running, I created my own PH98 file with the boot image and AmonRa, I've tried to flash a complete rooted Global stock rom, as well as attempting a full flash of the rom I was running. The PH files seem to process correctly but when done I get a messaging it is parsing the file but nothing happens afterwards. On reboot I get the white HTC screen then straight to the black JPBear screen. The phone also does not recognize that it is plugged into my laptop or a wall charger, there are no LED's lit. Without the USB I cannot relock the phone so I cannot flash back to a stock RUU. Fastboot\Min-ADB\Controlbear all fail as the phone is not recognized.
Are there any other things I can try before I give up. I'm not sure if the S-Off attempt may have damaged the USB or not but it definitely does not respond. I do have the extended warranty on the phone but returning it would be a last resort.
I apologize for asking the same questions as many others but I have not been able to find an answer despite searching for most of the night.
controlbear - r
Straight from the troubleshooting page: http://unlimited.io/jbtroubleshooting.htm
shrike1978 said:
controlbear - r
Does not work. I've read the troubleshooting page and tried everything I could find before posting. Controlbear returns an error it cannot find the phone and prompts me to install the drivers and reboot. Fastboot and mini-adb return similar results (phone is not detected).
Thanks for the input.
Click to expand...
Click to collapse
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
brando56894 said:
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
Click to expand...
Click to collapse
I did try a ROM but have no access to recovery. When I select it fro the hboot menu, the screen flashes for a second and then goes back to hboot. I cannot load the stock RUU because the bootloader is unlocked and I have read there is no way to relock it without working USB.
Thanks for the suggestions, I appreciate the imput.
control bear makes a back up before doing the wire trick. just restore the back up?
synisterwolf said:
control bear makes a back up before doing the wire trick. just restore the back up?
Click to expand...
Click to collapse
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
gskuse said:
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
Click to expand...
Click to collapse
Can you see hboot at all?
Sent from my iPhone...
synisterwolf said:
Can you see hboot at all?
Sent from my iPhone...
Click to expand...
Click to collapse
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
gskuse said:
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
Click to expand...
Click to collapse
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
synisterwolf said:
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
Click to expand...
Click to collapse
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
gskuse said:
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
Click to expand...
Click to collapse
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
synisterwolf said:
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
Click to expand...
Click to collapse
Nah no way to charge the battery. I have a VZW store near me and will take it there for a swap.
I really appreciate your help though.:good:
The only way to recover with the control bear program is to place all the files in its own folder and then CD to that folder and run from there.I had to recover my phone once. Took me a few minutes to wrap my mind around it. Just keep reading until it makes sense.
Alright so my issue is I flashed an ics rom on my evo LTE but accidentally with the wrong firmware. When the update was just about done, the screen went black. No charge light when plugged into a charger and the device will not power on, or do anything(tried button combinations). However when I plug it into my computer,device manager sees my phone as “My HTC”. So it seems to have a connection but it doesn’t do anything to the phone. Fix possibly?
Sorry for asking such a basic question guys. New to the forums but definitely not new to flashing roms. This problem just confuses me to death.
Can you supply as much info as possible.
QUOTE=bigdaddy619;45718286]Can you supply as much info as possible.[/QUOTE]
Yes I can my friend. Of course, I got S-OFF with moonshine. Never had a problem there. Rooted also with moonshine as well. Flashed a lot of different jelly bean roms (CM, Meanbean) to see which one best suited me. Well after awhile I decided to give one of the ics roms a shot but the firmware version on my evo was for jelly bean only, not ice cream sandwich. Just as the flash of the ics rom was about finished, the screen went black. (Battery was above 50%). I tried every button combination, but nothing worked. Tried connecting it to a charger and the orange charge light wouldn't even come on. I even left it on the charger overnight, but no dice. So the phone is totally unresponsive to everything. One thing I did notice however is that when I tried connecting the phone to the computer, my computer makes the connection noise when it finds a
Usb device. Checked my device manager on windows and my phone shows up as "My HTC". So it seems as my computer has some type of connection to the phone. With that being said, would there be some way to use some unbricking software or any other way to unbrick my phone? (From what I see, I think the bootloader may be corrupted)
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
scottspa74 said:
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you know of what commands may work for my device? Cmd is new to me, or well at least when it comes to sending commands to phones lol.
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
FinZ28 said:
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
Click to expand...
Click to collapse
Thank you much sir. Here's what I found out. When I type the command "adb devices", nothing shows up. When I type in "fastboot devices" here is what it says:C:\Users\lisa\Desktop>fastboot devices
C:\Users\lisa\Desktop>fastboot devices
t♥☻ fastboot
guessing that's not a serial number, as it should be, but it recognizes my device as a fastboot device. Is there any hope of fixing this paperweight?
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
FinZ28 said:
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
Click to expand...
Click to collapse
The only way I can get to the bootloader is by using the command prompt. Otherwise, my phone remains inoperable.
What happens when you select the recovery option in the bootloader?
Meaning that fastboot shows my device is connected but I cant access it on my phone.
rwhittaker13 said:
Meaning that fastboot shows my device is connected but I cant access it on my phone.
Click to expand...
Click to collapse
Ah.
HTC bricked
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
stasikbest said:
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
Click to expand...
Click to collapse
What did you do prior to booting into recovery? Also, when you plug your phone into your computer, what does your device show up as?
Sent from my HTC EVO 4G LTE
Bricked Phone Stuck in Fastboot
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
Use Fastboot to fastboot flash a recovery to your phone
Sent from my SPH-L710 using Tapatalk 2
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Thanks
FinZ28 said:
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Bammm! Worked like a charm. Back in business. Thanks much!
I have been following all the posts about rooting and I managed to soft-brick my phone. I was able to temp root the phone, but I could never get superCID because the modified CID would never take. I didn't get errors, it just didn't stick. Anyway, I flashed the recovery for 2.17, but my phone took an OTA update to 2.19 a few days ago, and now I am stuck on the main screen but without the sense unlock ring. The screen works, and I can access the phone's drive and sd card, and I can adb. The bootloader shows ****TAMPERED***** (been that way for a while), and Bootloader is LOCKED. FIREBALL PVT SHIP S-ON RL, HBOOT is 1.15.0000.
Any ideas to recover to a fully booted phone?
yes had the same thing happen to me. download the ruu exe. from here http://www.androidruu.com/?developer=Fireball i used 217.605.2 ruu. put phone in fastboot connect it to computer and run ruu exe. on ur computer
I followed your reply but am not having any success . . . yet.
I go through the RUU.exe screens where I verify that I want to "upgrade" from image version 2.19.605.2 to image version 2.17.605.2.
Then RUU.exe runs to the point where it tells me the process will take 10 minutes. It then gets to "waiting for bootloader........" and the phone looks like it is rebooting and a black "HTC" screen appears. Bootloader never appears. A Windows 8 Systray error message then appears saying "USB Device Not Recognized - The last USB device connected has lost communication with the computer [or something like that]" The RUU.exe program then states: "ERROR [171] USB Connection Error. Check the following: (1) phone is connected to USB cable; (2) PC is connected to USB cable" There is no further option than to EXIT the RUU.exe. (Yes, my cable is connected to a USB 2 port).
I tried to do this twice with the same error message and the same disappointing results. The phone stays locked on the black HTC screen and I need to pull the battery to change this locked state.
I have no trouble communicating with the phone with ADB and I have root (#) at ADB Shell. I JUST loose USB communications with the phone as soon as it goes tries to load bootloader. I originally tried to run RUU.exe the way you stated by putting the phone into fastboot and then running RUU.exe, but then the program would not find the phone. What am I missing here? I have HTC drivers loaded, but I keep getting the comm error. Any more ideas?
Maybe I need to flash a recovery for 2.19.605.2? Any idea where I might find that?
OK, not sure why I didn't do this sooner, but I did a factory reset from Bootloader and it seems I am back again running the 2.19.605.2. Not sure if I can root this new OTA version using the 2.17.605.2 procedures or not, but I may give this a break for a bit.
Yeah u can't downgrade to 2.17 if ur on 2.19
Sent from my XT1060 using xda app-developers app
Hello,
I was trying to convert my T-Mobile HTC One to a Developer Edition so I could receive OTA updates by following the instructions here. I made it to step 11 where I changed the CID to BS_US001 (from T-MOB010), but encountered an error trying to change the MID to PN0712000 (from PN0713000). I also tried to change the CID to 11111111 which also worked, but I was still unable to change the MID. At this point I searched around for alternate ways to change the MID and found this post which I was able to follow until step 5. When I rebooted to bootloader at step 5, the phone never turned back on and I got a message in Windows saying "USB device not recognized".
The phone doesn't turn on at all, I have tried to hold power and power + vol down for around 30 seconds and nothing happens aside from a few vibrations every 20-30 seconds. I've tried holding power + both volume buttons for over 2 minutes to no avail. The PC I'm using is Win 8.1 using the USB 2.0 ports. I left it connected to the wall charger overnight and it only gave me a flashing red light.
Am I permanently bricked? No matter what I've tried, the phone just will not turn on at all. I tried running the RUU but of course it didn't work because the phone wasn't recognized as being plugged into the PC. Any help would be greatly appreciated. I've also attached a screenshot of the command window up until the point where I tried to reboot and it never turned back on.
When you get the "unrecognized device" the phone is on. Chances are, it's running a badly modified HBOOT that is trying and failing to get into RUU. LAst tiome that happened to me, holding the power button for *exactly* 16 seconds brought it into RUU mode (did not display the HTC RUU logo). From there I was able to run the RUU.
If you can get to that point, the RUU should install so long as you are SuperCID. If it does not;
Make sure you have the latest adb/fastboot - (or search google for "Minimal ADB and Fastboot" which has always worked for me)
fastboot reboot-bootloader
Install the modified tmous hboot following the instructions here:
http://rumrunner.us/hboots/
This will enable the use of the fastboot oem writemid command allowing you to change your MID.
I use this HBOOT when doing any conversions on my device. It allows all of the commands and has yet to fail me getting RUU's to run.
I have converted from T-Mobile to Dev, GPe and Int'l (and back to T-Mobile) several times and haven't bricked.
Keep working at it. These things are hard to brick!
Thank you for the reply! I'll try what you mentioned and report back on the results. I probably should have waited until I had a windows 7 PC to work on, but mine is currently in shipment. Hopefully with those tools you mentioned I can resurrect it.
Sent from my Galaxy Nexus using xda app-developers app
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
dg32 said:
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try flashing a bright light into the proximity sensor while holding the power button + vol down buttons together.
:good:
the phone was working fine then it started to reboot by itself, but it word not go past the beanstalk 4.4 boot.
then it just stayed on the fastboot menu and or bootloader menu... the phone was s-off then i was told maybe there was a glitch and
it was not s-off and to retry to unlockit after that it became black screen asking for Qualcomm usb driver... please help.
Connect it to a pc run a ruu can you still get into the hboot menu? What exploit did you run etc. Provide more details.
Sent from my EVO using Tapatalk