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
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'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
Hey everyone, so I woke up Saturday morning to a wonderful surprise, and am just getting around to letting everyone know and maybe throw their suggestions my way!
Device: Tmo LG V10, H901
Recovery: [TWRP] Recovery: V10_H901_pplus [V3.0.2-0] [08/16/2016]
ROM: [ROM] [STOCK] [H901] V10_H901_V20J_Stock_Custom_2e [08/15/2016]; V10_H901_V20J_Stock_Custom_2e-signed
Root: Systemless Instructions - How to - 08/08/2016
Xposed: Systemless Xposed, see root guide above
Friday night, I was using my T-Mobile V10 like normal. No recent modifications, no new apps, adjustments, etc... Plug it into the charger and go to bed for the night. No issues right?
I wake up Saturday and the screen is blank. The phone isn't responding to the power button, so I hold the Vol-Down+Vol-Up+Power down to reboot it.
The phone won't reboot. So I pull the battery, and throw it back in.
Phone hits the LG logo, yey!
But it never moves from the LG logo
So at this point, I try booting into Recovery (TWRP) and the phone seems to not be responding to my button commands. It hits the boot logo and never does anything else.
I tried to boot into Download mode, nothing, just sitting on the logo.
After messing with the phone, with and without a USB cable attached to my laptop, I finally get the device into Fastboot.
In fastboot, I can run commands, but since I am on V20J, I am unable to flash or boot TWRP
I was also able to get into download mode when plugged into my PC only.
So down below, I will go over all the stuff I have tried.
Modes I can enter-
Fastboot
Download Mode (USB)
Stuff I tried-
LG Bridge Update
Update says it succeeds
Still does not boot
When I reconnect LG Bridge again, it says an error occurred and wants to update again
Direct .img flash via Fastboot
Using the steps from this post
Unable to flash, FAILED (remote:unknown command) due to V20J I believe
Flash V20J .tot via LGUP
It seems to flash successfully, but the phone still doesn't boot
So I left for the T-Mobile store Saturday, phone not booting, just stuck on the logo.
They are Warrantying the phone, so I am just waiting on a back-ordered replacement now.
EDIT: The Plot Thickens....
So I thought I would fire up the phone this morning, maybe try some other updates/flashes again, maybe something will happen.
Now I cant even get into Download Mode (USB) anymore.
It shows Download Mode on the screen, then the phone just reboots.
Additionally, on first boot I received some sort of error on the screen, but it went away so fast I couldn't read it.
Now I can't get that error to come back for the life of me...
I am just so confused now. The phone has a mind of its own.
My brother had 2 V10's that did that. Replaced under warranty.
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Yikes. Making me scared once this warranty is up.... Would hate to just lose a phone randomly for no reason!
Swizzle82 said:
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Click to expand...
Click to collapse
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Waxim1 said:
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Click to expand...
Click to collapse
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Fenopy said:
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Click to expand...
Click to collapse
Thnks I jav read these but need to know if i should b on stock rom before locking or what? And any known issue while trying relocking it?