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?
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
My wife's EVO is running the Mean ICS rom from last summer and I'd like to go to JB so she stops getting the OTA notification. I tried flashing a new ROM (using TWRP 2.5) to no avail (tried 3 different ones). Then I was going to roll back to stock and can't even re-lock the bootloader. When I use the QB King video I plug in the usb on bootloader and it doesn't show "fastboot usb" until I scroll down. Any thoughts?
mfenske said:
My wife's EVO is running the Mean ICS rom from last summer and I'd like to go to JB so she stops getting the OTA notification. I tried flashing a new ROM (using TWRP 2.5) to no avail (tried 3 different ones). Then I was going to roll back to stock and can't even re-lock the bootloader. When I use the QB King video I plug in the usb on bootloader and it doesn't show "fastboot usb" until I scroll down. Any thoughts?
Click to expand...
Click to collapse
Are the USB ports you're using 2.0 or 3.0? I recently got a new laptop and found that my LTEVO didn't play nice with 3.0 ports so I had to set my BIOS to use the USB ports as 2.0 in order to be able to work with my phone.
mfenske said:
My wife's EVO is running the Mean ICS rom from last summer and I'd like to go to JB so she stops getting the OTA notification. I tried flashing a new ROM (using TWRP 2.5) to no avail (tried 3 different ones). Then I was going to roll back to stock and can't even re-lock the bootloader. When I use the QB King video I plug in the usb on bootloader and it doesn't show "fastboot usb" until I scroll down. Any thoughts?
Click to expand...
Click to collapse
You have to press the power button to select fastboot
bigdaddy619 said:
You have to press the power button to select fastboot
Click to expand...
Click to collapse
Yeah, I did that. When I enter a command it just says "Waiting for device". I've tried in fastboot, hboot, fastboot usb. Doesn't seem to matter.
If your command window says 'waiting for device' while you have already selected fastboot from bootloader menu then its most likely your fastboot drivers aren't installed. They usually don't install automatically in Windows and it may list "Android 1.0" in device manager with a yellow exclamation mark meaning the drivers weren't automatically installed. If this is the case just download HTC Sync online, install it and make sure at the top of your device manager list "My HTC" is showing. Then you can commence fastboot commands such as relock etc.
I pretty much screwed my phone so bad, and I can't seem to the find any solution anywhere...
Here's what I did in order:
-tried rooting it with this guy's guide [link taken down since im a new member, but it's on htconeroot dot com//htc-one-root/how-to-root-htc-one-windowsmaclinux/]
[keep in mind it's S-On with HBoot 1.55]
-found out TWRP wasn't updated so I replaced it with a newer one (2.6.3)
-now rooted device
-wanted to restore to normal stock settings so I downloaded the Guru Reset M7 1.26.502.15 and put it in my root folder
-went to recovery to install the guru reset ZIP
-things install, but touch screen doesn't work
problems now:
-can't turn off phone on main screen (tried holding down power, but doesn't restart phone past the 3 second mark)
-can't boot into bootloader from restart
-ruu doesn't work
can anyone provide me with help? please and thank you
EDIT: few things to keep in mind
-everytime i use RUU 3.17.502.3, it loads up black screen with HTC logo int he middle, then I can turn off the phone.
-when loading up, i can load into bootloader
-when choosing recovery/factory reset, it brings up the software update screen, but then goes to red triangle
-at red triangle screen, i can reboot system through android recovery system.
-back at square 1, touch screen doesn't work, etc.
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
hack14u said:
All I can say is that I am in the same waters, phone stuck in bootloop, or goes to triangle of death, and PC WILL NOT recognize phone at all so without driver support, I am screwed too.
Added: All I did was unlock through HTCDev, and all hell broke loose, loaded up AIO, and phone freaked upon flashing TWRP. 1.55 HBoot, 4.3 ATT update.
Click to expand...
Click to collapse
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
pztrixwsup said:
Here's a solution:
-get into bootloader mode
-fastboot
-plug usb in
-open cmd, then get to where your HTC One rooting stuff is (for example, everything was in a folder on my desktop)
-type "fastboot oem lock"
-your phone should say "relocked"
-open the latest RUU you have
-run things normally
that's how i fixed mine, lemme know if you have any more questions.
i also don't know why your phone has to be "relocked" in order to update it's software.
Click to expand...
Click to collapse
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
That's why we need to wait for the issue with Rumrunner S-off for our phones to get squared away. So we can flash other carrier or older software.
---------- Post added at 06:51 PM ---------- Previous post was at 06:40 PM ----------
Has anybody had success with Rumrunner for 3.17.502.3 yet? I have been hitting a wall and am not the only one. The phone is freezing on adb at test 2.1. We have tried flashing the RUU and doing it again, but it fails every time in the same way.
Here's what I get:
Code:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0712000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (22/120)
Test 2.1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Waiting for ADB (120/120)
ADB connection failed!!
FIX IT, yes, YOU fix it no!!!FIX IT NOW!!!!!
Reboot command failed!!
Bootloader unlock failed?
Press ENTER to exit
Specifically looking for somebody with 3.17.502.3 to chime in if they've tried it, or one of the most awesome devs that work tirelessly so we common folk may find new ways to nearly-brick our phones :silly:
hack14u said:
A thousand thanks, you are my new hero! And if you run the RUU, then go back and re-unlock the bootloader, it only says "unlocked" not tampered.
Click to expand...
Click to collapse
Yea no problem bro, i was in your position for the whole day and i stumbled upon a billion sites and eventually trial and error'd the whole way through
Check the discussion in other thread about 4.3 and s-off. We have tried quite a few different things with no luck so far. I even posted in HTC one forums in the support thread. Hoping they will release something soon for our hboot 155.
Sent from my HTC One using xda app-developers app
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
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