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
Related
//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
I am stuck in a boot loop and the only I think I will fix this is taking it to the Verizon store. I flashed the stock ROM, but cannot take it back yet until I turn S-ON.
I am unable to do this on my Thunderbolt or at least this method (http://forum.xda-developers.com/showthread.php?t=1310014) because it says bypassed when I attempt to update under bootloader.
I cannot remove root through the Thunderbolt USB utility or ADB because my phone cannot connect to the computer through USB when in USB debugging. When in USB debugging and attempt to mount as disk drive it says unrecognized, and does not do this when not in debugging. When I connect without debugging and press debugging the phone instantly shuts off and goes back into boot loop. I am not sure what is causing debugging to malfunction, maybe a corruption or revolutionary?
On Thunderbolt Forum they say "You have rooted using the Revolutionary root method and have the protected S-OFF bootloader installed that prevents you from accidentally flashing an S-ON bootloader. You need to unroot using this method:[RS Guide] How Return to Stock from Revolutionary Root", and as stated prior that method requires ADB and I cannot turn on debugging.
My theory is either something physically broke or h-boot is somehow corrupted and causing the splash screen to restart. Here is what another forum said:
Problem: I flashed the unsigned RUU above named "PG05IMG_MR1_upgrade.zip", but my phone still won't start. It just displays the white HTC screen and then briefly shows the second splash or animation screen and then immediately restarts. I've tried getting into Clockwork Recovery through HBOOT, but again, I just see Recovery briefly and then the phone reboots again.
Answer: It is possibly this may be a true brick caused by a hardware failure in your phone. The ongoing theory is that some phones have a defective emmc chip.
I am able to turn my phone after 3 or 4 battery pulls and restarts, but it takes a while. Can anyone help me remove revolutionary and S-OFF?
P.S. Here is the info under Revolution hboot screen:
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Feb 23 2011,20: 42:55
It seems all that was needed to be done was update the firmware, now I was able to plug in and remove root, thanks to everyone that helped me in previous posts. It only took 24 hours... lol
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 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
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.