SO i tried to download the RUU from HTC and while it was downloading to the device, my computer got stuck on sending img to ROM for over an hour. After I unplugged the device to try to restart it, my device says that there is no img. IDK what to do!!!! I have never rooted this device, someone help
S-ON
HBOOT - 2.10.0000
Radio - 1.12.11.0830
Choose the FASTBOOT option in the bootloader (so that the display changes to say "FASTBOOT USB") and run the RUU again from the PC.
Thankkk u!
Sent from my EVO using Tapatalk
Related
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
I'm stuck. So i have an htc one sprint latest version.So,I Moded my htc one with cyanogenmod,the mod was okay but it lagged in many ways so i decided to go back to stock rom.So i went looking for my ruu and got the 3.04.651.2 ruu.which is my version. Using the adt i "fastboot oem lock"my phone. well all was going fine until the "htc one rom update utility" says that there is a usb connection error.but the phone is connected the red led light is and it says "fastboot Usb".I already "fastboot oem lock" my device so i'm stuck on the bootloader without being able to go to recovery mode,it well just send me back to bootloader..Any ideas how to fix these.My Usb is working fine.At this point i don't care if i don't get my phone to stock rom,i would stay with the cyanogenmod i just want to use my htc one ( lol
Addiontal information:the bootloader says:
**Tampered**
**relocked**
**security warning****
s-on
os-3.04.651.2
Thanks
Juan.hdz1872 said:
I'm stuck. So i have an htc one sprint latest version.So,I Moded my htc one with cyanogenmod,the mod was okay but it lagged in many ways so i decided to go back to stock rom.So i went looking for my ruu and got the 3.04.651.2 ruu.which is my version. Using the adt i "fastboot oem lock"my phone. well all was going fine until the "htc one rom update utility" says that there is a usb connection error.but the phone is connected the red led light is and it says "fastboot Usb".I already "fastboot oem lock" my device so i'm stuck on the bootloader without being able to go to recovery mode,it well just send me back to bootloader..Any ideas how to fix these.My Usb is working fine.At this point i don't care if i don't get my phone to stock rom,i would stay with the cyanogenmod i just want to use my htc one ( lol
Addiontal information:the bootloader says:
**Tampered**
**relocked**
**security warning****
s-on
os-3.04.651.2
Thanks
Click to expand...
Click to collapse
Did you ever get a solution for this?
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
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
Here is the link to RUU 6.10.531.10 from the HTC Official Site:
RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.10_Radio_4T.28.3218.04_10.33E.1718.01L_release_405711_signed_2.exe
majmoz said:
Here is the link to RUU 6.10.531.10 from the HTC Official Site:
RUU_M7_UL_K443_SENSE60_MR_TMOUS_6.10.531.10_Radio_4T.28.3218.04_10.33E.1718.01L_release_405711_signed_2.exe
Click to expand...
Click to collapse
Thanks for the update! Downloading now..
is this available as a twrp flashable zip?
my bootloader unlocked/tampered but still s-on. so i'm worried if i just run the ruu, it will screw up everything..
chagla said:
is this available as a twrp flashable zip?
my bootloader unlocked/tampered but still s-on. so i'm worried if i just run the ruu, it will screw up everything..
Click to expand...
Click to collapse
No, it is for returning to a stock position.
Can anyone tell my I keep getting error 171 when I try to install ruu? My One gets stuck on the silver HTC logo and on my computer it says waiting for bootloader than error.
EDIT:Alright apparently I needed to lock my bootloader but after I did that it the error changes to 170.
TehAce24 said:
Can anyone tell my I keep getting error 171 when I try to install ruu? My One gets stuck on the silver HTC logo and on my computer it says waiting for bootloader than error.
EDIT:Alright apparently I needed to lock my bootloader but after I did that it the error changes to 170.
Click to expand...
Click to collapse
Try this fix: https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
Is your phone in bootloader/FASTBOOT USB when you are trying to run the RUU?
majmoz said:
Try this fix: https://sites.google.com/site/communityhelpsareebro/how-to-fix-error-170-usb-connection-error
Is your phone in bootloader/FASTBOOT USB when you are trying to run the RUU?
Click to expand...
Click to collapse
Ok I tried this but am still having some problems. Here's what I did.
1. I updated the to the HTC drivers. ( Is this the correct one?)
http://i.imgur.com/unlsTYf.png
2. I ran the ruu as admin and proceeded with the installer.
3. Here's where it just stops working. It'll just say waiting for bootloader and then error.
http://i.imgur.com/Z0XKXQ7.jpg
4. I Tried re running the ruu again like the site said but it gets stuck when it says "Verifying the information on your PDA Phone.... Please wait..."
The odd part is that when I partially plug in the USB it goes to FASTBOOT but when I plug it all the way in just goes back to the HTC logo.
http://i.imgur.com/1e8PazH.jpg
Also when my phone is in USB whilst my phone is not in fastboot/bootloader it shows up in device manager.
http://i.imgur.com/eVSL0kW.png
But when I go into fastboot/bootloader it doesn't show up.
http://i.imgur.com/UfA7kny.png
TehAce24 said:
Ok I tried this but am still having some problems. Here's what I did.
1. I updated the to the HTC drivers. ( Is this the correct one?)
http://i.imgur.com/unlsTYf.png
2. I ran the ruu as admin and proceeded with the installer.
3. Here's where it just stops working. It'll just say waiting for bootloader and then error.
http://i.imgur.com/Z0XKXQ7.jpg
4. I Tried re running the ruu again like the site said but it gets stuck when it says "Verifying the information on your PDA Phone.... Please wait..."
The odd part is that when I partially plug in the USB it goes to FASTBOOT but when I plug it all the way in just goes back to the HTC logo.
http://i.imgur.com/1e8PazH.jpg
Also when my phone is in USB whilst my phone is not in fastboot/bootloader it shows up in device manager.
http://i.imgur.com/eVSL0kW.png
But when I go into fastboot/bootloader it doesn't show up.
http://i.imgur.com/UfA7kny.png
Click to expand...
Click to collapse
Get the latest drivers from here. Uninstall the old driver through control panel then reboot the computer. Now install the new driver.
If it is saying PDA phone, then the wrong drivers are installed.
If the phone is in OS it will show up in Device Manager.
If the phone is in bootloader/FASTBOOT USB it will not show up in Device Manager
majmoz said:
Get the latest drivers from here. Uninstall the old driver through control panel then reboot the computer. Now install the new driver.
If it is saying PDA phone, then the wrong drivers are installed.
If the phone is in OS it will show up in Device Manager.
If the phone is in bootloader/FASTBOOT USB it will not show up in Device Manager
Click to expand...
Click to collapse
A thousand thanks man! This got it to work.
i have no problems with the drivers and it shows the phone is connected but when i try to run the RUU as a executable file nothing happens, it just shows to accept the conditions, i hit yes and then nothing happens. Caan anyone tell me what to do
Epiel said:
i have no problems with the drivers and it shows the phone is connected but when i try to run the RUU as a executable file nothing happens, it just shows to accept the conditions, i hit yes and then nothing happens. Caan anyone tell me what to do
Click to expand...
Click to collapse
Is your bootloader "Locked/Relocked", if you are S-ON?
Is your phone connected in bootloader/FASTBOOT USB when you double-click the RUU?
What Windows version are you running?
majmoz said:
Is your bootloader "Locked/Relocked", if you are S-ON?
Is your phone connected in bootloader/FASTBOOT USB when you double-click the RUU?
What Windows version are you running?
Click to expand...
Click to collapse
Im Relocked S-ON, I have windows 7 home premium and it's connected in bootloader/FASTBOOT USB!
so already could do it in other PC I think it's my pc, has some issue I will format and try later with another one
thanks anyway
Oh God what is this.
I decrypted the RUU with the HBOOT that was provided in the firmware zip.
Yet, flashing system.img will always fail with 51. Trying to run it in Windows will give me the "not connected" error, even though Device Manager shows that it's connected, and the phone reads "FASTBOOT USB" on the top.
S-OFF+Unlocked.