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
Related
I've tried to also find the tbauto root downloads but my browsers never find the page no matter who's link i try I'm a massive noob but i have rooted my nexus s 4g and last night i put ics onto my friend touch pad so I thought i was able to follow directions but i guess not.
steps i took:
downloaded all files needed to run revolutionary
downgraded
ran revolutionary
got correct code from serial number
reboots into bootloader (on phone ) says waiting for fastboot on revolutionary
help out a noob!
screen shot
View attachment 928832
loook
colbatronbmw said:
I've tried to also find the tbauto root downloads but my browsers never find the page no matter who's link i try I'm a massive noob but i have rooted my nexus s 4g and last night i put ics onto my friend touch pad so I thought i was able to follow directions but i guess not.
steps i took:
downloaded all files needed to run revolutionary
downgraded
ran revolutionary
got correct code from serial number
reboots into bootloader (on phone ) says waiting for fastboot on revolutionary
help out a noob!
Click to expand...
Click to collapse
once the phone boots into the bootloader you have to press the power button to select fastboot from the menu (vol +/- are used to scroll). this will put the phone in fastboot. if your usb connection is detected it should display "fastboot usb" on your phone after a few seconds.
what software version do you have? If it is 2.11.605.9 then there are extra steps need to get it.
---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------
If you are on the system version stated above use this http://www.cd-net.net/dev/Joomla/index.php/projects/htc-thunderbolt-hacking to root.
Thanks I'll try it
Sent from my Nexus S 4G using Tapatalk
Another option disconnect the phone from the USB and reconnect it after a few seconds. Might have to power cycle the phone also.
Solution to "waiting for fastboot"
I just ran into this same problem, nothing I could find would work. I was using the thunderbolt all-in-one solution to root my phone and was stuck on the revolutionary step. If I power cycled and booted into recovery and selected fastboot, the phone would say "fastboot usb" for a moment, but then it would just say "fastboot". Finally, I found a solution. With Revolutionary stuck at "waiting for fastboot...." I did the following:
* uninstalled the HTC drivers
* reinstalled the drivers
* power cycle phone and boot into recovery
* select fastboot
again it said "fastboot usb", then toggled to "fastboot", but then windows gave me a message telling me that a device driver was installed, and it togged back to "fastboot usb". revolutionary was then able to find my phone and go to the next step which was... booting into fast boot (once moar). again it hung here, and I had to repeat all of the above steps.
after this I was able to install CWM successfully, and use the all-in-one tool to install the super user program.
What version of windows are u on?
Sent from my Liquidsmooth Rezound using xda app-developers app
tburns said:
What version of windows are u on?
Sent from my Liquidsmooth Rezound using xda app-developers app
Click to expand...
Click to collapse
I am on Windows 7
Try running the tool on administrator. Also when you connect the device before you start the process and you get the prompt to run HTC sync don't touch it. Don't close or allow the dialog just leave it be until the tool is run.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Try running the tool on administrator. Also when you connect the device before you start the process and you get the prompt to run HTC sync don't touch it. Don't close or allow the dialog just leave it be until the tool is run.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Great idea, thanks. If I root another tbolt I'll try this out.
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
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
Hello,
I was trying to convert my T-Mobile HTC One to a Developer Edition so I could receive OTA updates by following the instructions here. I made it to step 11 where I changed the CID to BS_US001 (from T-MOB010), but encountered an error trying to change the MID to PN0712000 (from PN0713000). I also tried to change the CID to 11111111 which also worked, but I was still unable to change the MID. At this point I searched around for alternate ways to change the MID and found this post which I was able to follow until step 5. When I rebooted to bootloader at step 5, the phone never turned back on and I got a message in Windows saying "USB device not recognized".
The phone doesn't turn on at all, I have tried to hold power and power + vol down for around 30 seconds and nothing happens aside from a few vibrations every 20-30 seconds. I've tried holding power + both volume buttons for over 2 minutes to no avail. The PC I'm using is Win 8.1 using the USB 2.0 ports. I left it connected to the wall charger overnight and it only gave me a flashing red light.
Am I permanently bricked? No matter what I've tried, the phone just will not turn on at all. I tried running the RUU but of course it didn't work because the phone wasn't recognized as being plugged into the PC. Any help would be greatly appreciated. I've also attached a screenshot of the command window up until the point where I tried to reboot and it never turned back on.
When you get the "unrecognized device" the phone is on. Chances are, it's running a badly modified HBOOT that is trying and failing to get into RUU. LAst tiome that happened to me, holding the power button for *exactly* 16 seconds brought it into RUU mode (did not display the HTC RUU logo). From there I was able to run the RUU.
If you can get to that point, the RUU should install so long as you are SuperCID. If it does not;
Make sure you have the latest adb/fastboot - (or search google for "Minimal ADB and Fastboot" which has always worked for me)
fastboot reboot-bootloader
Install the modified tmous hboot following the instructions here:
http://rumrunner.us/hboots/
This will enable the use of the fastboot oem writemid command allowing you to change your MID.
I use this HBOOT when doing any conversions on my device. It allows all of the commands and has yet to fail me getting RUU's to run.
I have converted from T-Mobile to Dev, GPe and Int'l (and back to T-Mobile) several times and haven't bricked.
Keep working at it. These things are hard to brick!
Thank you for the reply! I'll try what you mentioned and report back on the results. I probably should have waited until I had a windows 7 PC to work on, but mine is currently in shipment. Hopefully with those tools you mentioned I can resurrect it.
Sent from my Galaxy Nexus using xda app-developers app
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
dg32 said:
Well, I was able to get it working again. I actually tried plugging it into the usb 3.0 port on win 8.1 and it didn't give the unrecognized device message so I went from there. I did have to install some 8.1 fastboot drivers for usb 3.0 which was easy. I tried to run the t mobile ruu which didn't work because I had changed the CID but after that the device just booted normally.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Try flashing a bright light into the proximity sensor while holding the power button + vol down buttons together.
:good: