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
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.
God help me.
While I was trying to sim unlock the phone, I accidentally changed permissions on the system folder to read-only (using root explorer). The phone will not go past the splash screen since. So I tried a factory reset with no avail. I decided to load a Stock ROM using the Sprint ROM but it wouldn't load; fails at verifying file. I tried different ROMs and none of them will take. I'm unable to get the PC or Mac to recognize the USB mode. The phone is on, but in Windows it says no emulation and Mac doesn't even pop up anything. I did install the ADB and fastboot drivers on both the PC and Mac but they still don't recognize it. I'm showing
T6-WHL XA Ship S-Off
CID- 11111111
Hboot 2.46.0000
on the boot screen.
Any help is greatly appreciated.
Update: Installed Cyanogen Mod 12 via SD Card. Went smooth.
Hi,I tried upgrading my M8 from 4.16 to 4.28 manually through windows but process hanged after 28%.When i unplugged and reboot my phone will only show android system recovery screen.i have sdk toolkit downloaded in my laptop and ruu 4.28 at&t file too.please help.
Im using Ubuntu 18.04.3. All was fine until the point it said success. Ive then unplugged the phone to see if it boots and it didnt respond to the power button until several minutes later. Now it does attempt to boot but ive left it for like 15 minutes and nothing - stuck on the xperia animation. Ive attempted to reboot into win10 and use the companion app to fix my phone but it says that the bootloader is unlocked.
Ive considered using fastboot to flash TWRP or relocking the bootloader and move from there, but literally every command i give it returns 'FAILED (command write failed (Success))'
Attempts to use windows to do that also went nowhere: Im unable to install the drivers. Ive downloaded the sdk studio, installed the google drivers plugin, located the folder with them, but when i connect my device it doesnt show in the device manager. If i connect it in fastboot mode, it shows as 'Android', but windows refuses to install the drivers claiming that they are incompatible.
EDIT: nvm, managed to install the drivers on windows, sucessfully flash TWRP and fix it from there
I guess a lesson was learned today: dont use linux for this kind of stuff