so I keep getting stuck at Waiting for fastboot on the revolutionary .exe on the computer....
the phone is on a white screen that at the top says locked. has hboot, down below has fastboot, bootloader, reboot..
now what?
Edit: the above is on a windows vista computer
im now tring on a windows xp computer and Revolutionary software wont even recognize the waiting for device....
so i cant get either to work.....
it is closer on the first one where i am stuck at Waiting for Fastboot on revolutionary and the phone is on the locked bootloader white screen.
plase help me out
kboater said:
so I keep getting stuck at Waiting for fastboot on the revolutionary .exe on the computer....
the phone is on a white screen that at the top says locked. has hboot, down below has fastboot, bootloader, reboot..
now what?
Edit: the above is on a windows vista computer
im now tring on a windows xp computer and Revolutionary software wont even recognize the waiting for device....
so i cant get either to work.....
it is closer on the first one where i am stuck at Waiting for Fastboot on revolutionary and the phone is on the locked bootloader white screen.
plase help me out
Click to expand...
Click to collapse
go into the phone settings, then power and uncheck fast boot. you might have to close the program first I think, and then repeat the procedure.
I have done it, I am still stuck in the same place...
more help is greatly appreciated
if it's <... waiting for fastboot > or something similar , UNCHECK fastboot from the power settings, turn off the phone, turn on while holding vol down. That will boot the phone into fastboot and your computer should recognize it.
ok, trying now. should i do that to the phone while the Revolutionary program is at the Waiting for fastboot?
Same thing. when i get into fastboot, Windows pops up the found new hardware and wants to install drivers. I thought I had installed all the drivers.....
so still same thing....
EDIT: same thing again. so i was thinking maybe for some reason even though i installed the drivers with HTC sync, maybe i needed to do it again. so i installed htc sync again, made sure drivers were installed. then deleted htc sync. then opened Revolutionary, entered code... bascially gets to same place and says waiting for fastboot; and the device looks like it is booting into fastboot (assuming fastboot is the white screen with options). then it just stays there and i get a window popping up asking me to install drivers. If i ignore that window, Revolutionary and phone stay in same place. if i try to install drivers, it just says it cant and I still just sit there....
damn this is frustrating.
Same freaking thing. Program says waiting for fastboot. widows pops up a found new hardware needs to install drivers (which i have done about 5 times) and phone looks like it is booting into fastboot (white screen)
and all just stay there.....what am i doing wrong? how long should i let it sit like this?
FINALLY!!!!
got it to say S-Off, now to the rest of it....
had to switch computers for a third time
Im having the same problems, but don't have access to another computer. I am running windows 7 on a mac, is this the problem?
Guys make sure that you have USB Debugging enabled under development options and run revolutionary.exe as admin... (right click-> run as admin)
I just came across this problem while trying to permanently root using revolutionary 0.4pre4. Android version was 2.3.5, hboot was 1.3 and with no OTA installed ever.
Apparently it was driver problem on Win7x64. I had HTC Sync installed(all processes were ended with task manager(this worked when I rooted my 4G on XP) and PDAnet installed. I came across and followed the "Pre-Installation" section at the rootzwiki Revolutionary section(can't post links yet).
While in recovery on my phone and "waiting for fastboot", I went to device manager and manually updated the drivers from my C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 directory. At that moment revolutionary continued, rebooted several times and finally said it failed. My phone booted into recovery and it showed S-off and revolutionary at the top!
After rebooting the phone, it gave me the activation and profile/prl update prompts, but all my data and apps were still there. I only had to sign back into google, but from here I can flash a recovery and install a zip to gain root.
kboater said:
so I keep getting stuck at Waiting for fastboot on the revolutionary .exe on the computer....
the phone is on a white screen that at the top says locked. has hboot, down below has fastboot, bootloader, reboot..
now what?
Edit: the above is on a windows vista computer
im now tring on a windows xp computer and Revolutionary software wont even recognize the waiting for device....
so i cant get either to work.....
it is closer on the first one where i am stuck at Waiting for Fastboot on revolutionary and the phone is on the locked bootloader white screen.
plase help me out
Click to expand...
Click to collapse
where did you get your phone?
Works
P-Dub said:
I just came across this problem while trying to permanently root using revolutionary 0.4pre4. Android version was 2.3.5, hboot was 1.3 and with no OTA installed ever.
Apparently it was driver problem on Win7x64. I had HTC Sync installed(all processes were ended with task manager(this worked when I rooted my 4G on XP) and PDAnet installed. I came across and followed the "Pre-Installation" section at the rootzwiki Revolutionary section(can't post links yet).
While in recovery on my phone and "waiting for fastboot", I went to device manager and manually updated the drivers from my C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 directory. At that moment revolutionary continued, rebooted several times and finally said it failed. My phone booted into recovery and it showed S-off and revolutionary at the top!
After rebooting the phone, it gave me the activation and profile/prl update prompts, but all my data and apps were still there. I only had to sign back into google, but from here I can flash a recovery and install a zip to gain root.
Click to expand...
Click to collapse
Cheers for that, final step I was stuck on. Revolutionary then reset hboot 4 times and during one it changed to s-off then after the last -Revolutionary- at top. Then clockwork mod installed also.
P-Dub said:
I just came across this problem while trying to permanently root using revolutionary 0.4pre4. Android version was 2.3.5, hboot was 1.3 and with no OTA installed ever.
Apparently it was driver problem on Win7x64. I had HTC Sync installed(all processes were ended with task manager(this worked when I rooted my 4G on XP) and PDAnet installed. I came across and followed the "Pre-Installation" section at the rootzwiki Revolutionary section(can't post links yet).
While in recovery on my phone and "waiting for fastboot", I went to device manager and manually updated the drivers from my C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 directory. At that moment revolutionary continued, rebooted several times and finally said it failed. My phone booted into recovery and it showed S-off and revolutionary at the top!
After rebooting the phone, it gave me the activation and profile/prl update prompts, but all my data and apps were still there. I only had to sign back into google, but from here I can flash a recovery and install a zip to gain root.
Click to expand...
Click to collapse
OMG, THANK YOU!
I usually don't bother to thank in forums, because I consider it a littering. But this time I couldn't resist. After 7 hours of trying all the fancy ways of installing the drivers, I tried the directory you mentioned and volia!
Simi-larly
P-Dub said:
I just came across this problem while trying to permanently root using revolutionary 0.4pre4. Android version was 2.3.5, hboot was 1.3 and with no OTA installed ever.
Apparently it was driver problem on Win7x64. I had HTC Sync installed(all processes were ended with task manager(this worked when I rooted my 4G on XP) and PDAnet installed. I came across and followed the "Pre-Installation" section at the rootzwiki Revolutionary section(can't post links yet).
While in recovery on my phone and "waiting for fastboot", I went to device manager and manually updated the drivers from my C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 directory. At that moment revolutionary continued, rebooted several times and finally said it failed. My phone booted into recovery and it showed S-off and revolutionary at the top!
After rebooting the phone, it gave me the activation and profile/prl update prompts, but all my data and apps were still there. I only had to sign back into google, but from here I can flash a recovery and install a zip to gain root.
Click to expand...
Click to collapse
OK, same shinola here, but also got mine done without downloading HTC Sync for Aria, at same point, by just right-clicking the 'Revolutionary' Android ADB driver from 'Device Manager', then clicking 'Scan for Hardware Changes' and letting Windows re-install the LAST driver I'd (just) tried (which was either the one automatically installed via 'Windows Update', or--much less likely--the one I'd found while trying to use the 'Unrevoked' method).
Regardless, all I'm saying is there turns out to be more than one way to skin this ruthlessly messy cat. I'd almost forgotten how difficult the Aria was (while definitely remembering how unrewarding it could be).
Anyway, at this point, 'Revolutionary' finished up immediately, after sticking at that spot for more than 15 minutes...and just took one reboot to come up saying 'Revolutionary' in red up top, as well as 'S-OFF', so...I'm on my way.
Actually, by the time I finished typing this, I've already used it to install CM7.2 (I know--that's all!) and gapps for it (while also ALMOST forgetting the silly speed-bump about 'up-arrowing' through those recovery menus to make the 2nd pages of menus actually show up!).
Overall, I'm here to say 'thanks' guys...and as always, 'thanks again' to XDA for being the ultimate grouping of resources for all things Android!
Related
In case you've experiencing the frustration of your inquiries being met with "search for blah blah blah" here is the direct link to avoid frustration.
ftp://xda:[email protected]_Hero_C_Sprint_1.29.651.1_signed_release.exe
If anyone can help me get this installed I'd appreciate it. It times out at the waiting for booatloader screen. I have the recovery ROM installed.
Try this:
Pull your battery
Put it back in
Hold down the Volume down arrow and press power
Press Volume Up, screen should say FASTBOOT USB in red
Start your RUU
If I'm in Fastboot USB Mode when I run the RUU, it fails at Verifying. If I boot into Fastboot while it's waiting to boot into recovery, it still times out.
Hmm, do you have the correct driver installed? Check your device manager under Android devices and see if the ADB driver is installed. If it is, install the driver from HTC Sync. Its called My HTC when it is installed
Yup, I definitely have the driver installed. I can use ADB just fine foe shell and push and so forth.
It connects initially to verify the info on the phone, but the RUU process reboots the phone and seems to expect it to boot into a certain bootloader. But it doesn't. I imagine the recovery ROM I flashed doesn't work with the RUU.
Does anyone have the original recovery ROM?
Had the same situation. I was able to get it to work by messing with the volume keys right after the reboot (pressed up and down a couple times.)
Gah, Windows. =/
Gonna see if I can do it in Parallels.
Having the same problem. It restarts the phone waiting for bootloader and then errors out.
Not sure what's going on. 100% positive I've got the adb driver. I've got HTC Sync working.
Using Win 7 64bit.
So it errors out and says a connection could not be made error 170.
I then disconnect the usb cable and the screen shows RUU but of course it's already disconnected.
No idea what to do.
Not sure why it is not working for you guys. My RUU would not update using the adb driver. I put it into fastboot usb mode. My pc then detected the phone. I went into device manager and checked under android devices. Make sure it says something like 'My HTC' and not 'HTC Dream' or something like that.
Hmm, worked fine for me under Vista. Installed HTC Sync update from the HTC site and all was good afterwards. Updating now.
I installed HTC Sync and now it works (that's with the custom recovery ROM).
Cool.
Yeah, the damned thing wouldn't work unless I installed HTC Sync. Back in business.
what OS are you guys using? I'm using w7 and i'm having absolutely no luck, i think i've tried everything possible...
I'm on Win7. You installed HTC Sync?
There's really no reason to flash the stock ROM anyway,,,
yes i have sync installed.
basically what happened was I lost my recovery backup image, i dunno how where i can get another one and how to apply it to my phone...this RUU thing is not working either, i tried fastboot and reinstalled all the phone drivers
Where is it getting hung up?
By the way, Byggun posted his recovery backup image:
http://rapidshare.com/files/308999685/recovery-backup.img.html
the RUU just says that my phone is not connected, i've checked the drivers and all are up to date.
i dont know exactly what to do to use the recovery image, i've never had to use one before, only had to create one.
it connects to my phone then waits for boot loader, then it says that its not connected anymore
Downloaded Advanced ACE Hack Kit (30042012)
Disabled apple drivers, shutdown extraneous applications, disabled firewall and antivirus, and did all the other prep steps recommended in the Effen manual.
Yes, I read the Effen manual
Never had HTC drivers installed or sync software. Installed drivers bundled with AAHK.
Plugged phone into laptop USB port - device was detected, drivers installed. Launched AAHK, selected 1 for the automated flash process.
Things seemed to go fine, however I saw a few errors (a few of which seemed to be anticipated by the script and were reported as expected and normal), and the phone rebooted a number of times.
Ended up on a white screen, with the phone totally locked up and unresponsive. Pulled the battery and rebooted holding power and volume down to boot into CMR (white screen with old school pixelated text?).
All appears not to be well though. I can't get the phone to boot and have yet to try installing any kind of ROM. Have tried to repeat the process, but the laptop will not install the drivers for the device this time when I plug it in - Android 1.0 device shows up, but the machine can't find the right drivers (maybe the device ID changed during flash?). Device manager lists the device as not working (missing a driver)
Device Instance ID: USB\VID_0BB4&PID_0C94\HT11NT206202
In looking at the summary screen on the phone, I see the following:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Apr 12 2011,00:55:45
After trying a few different options, my current status is:
HBOOT USB PLUG
I downloaded Ubuntu 12.04 LTS and tried re-running the flash, but the AAHK doesn't see the phone - says 'waiting for the phone to be connected' or something similar.
Given that I REALLY don't want to brick the phone, I am cautious about trying to work out the next step myself. Had wondered about:
1. Trying to get the (Win XP Pro SP3) drivers installed correctly for that device - then I could try re-running the flash process again.
2. Why did the flash process fail. I didn't have anything in the PD98IMG folder as I understood that was optional, yet the hack kit complained about the file being missing when it started running - red herring?
3. Do I need to put a rom on the SD card and use CMR to load that? If so, I am not sure I have a microSD to SD adapter handy right now?
Am on IRC looking for assistance - this post is to summarize my circumstances and hopefully help anyone in the same position later on.
Thank you in advance!
Solved
Thanks to @PaxtonCamaro91 on IRC for this:
Booted to livecd
- tried to run AAHK, but it errored saying it could not find the device
- rebooted phone in fastboot mode, still did not work
- booted to white HTC screen (not bootloader)
- AAHK then detected phone - selected T from AAHK menu selected fastboot RUU
- selected 1 to reflash.
The flash succeeded this time, but only took about 45 seconds to complete.
Rebooted phone, saw AT$T Rethink possible screen, which didn't appear before, and eventually came all the way to the desktop.
Confirmed adb reboot recovery and adb reboot bootloader worked from a terminal window
Confirmed S-OFF now showing under bootloader screen.
Carried out factory reset and am now moving on to AOSPX ICS 4.0.4 !!
Thanks to all who made this possible - awesome tool, awesome support!
im having the same issue, constantly fails downgrade and now doesnt even aknowledge attempts in bootloader.
im stuck here and have even tried onther pc, with the same outcome
jw2k_fr said:
Thanks to @PaxtonCamaro91 on IRC for this:
Booted to livecd
- tried to run AAHK, but it errored saying it could not find the device
- rebooted phone in fastboot mode, still did not work
- booted to white HTC screen (not bootloader)
- AAHK then detected phone - selected T from AAHK menu selected fastboot RUU
- selected 1 to reflash.
The flash succeeded this time, but only took about 45 seconds to complete.
Rebooted phone, saw AT$T Rethink possible screen, which didn't appear before, and eventually came all the way to the desktop.
Confirmed adb reboot recovery and adb reboot bootloader worked from a terminal window
Confirmed S-OFF now showing under bootloader screen.
Carried out factory reset and am now moving on to AOSPX ICS 4.0.4 !!
Thanks to all who made this possible - awesome tool, awesome support!
Click to expand...
Click to collapse
THANK YOU!!! My phone is back from the dead! , oh btw I was running AAHK on Windows 7 Home Premium 64bit
This is why I have been advocating using the Ubuntu Live CD method for many months. I've never seen anyone have problems going that route.
Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2
As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436
What we're your steps exactly? Did you relock your bootloader
a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Does anybody else have some more ideas?
Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?
kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.
Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you
Hi everyone. Thanks for your attention
I have a HTC Mini. Today I wasn't able to connect my phone into the wifi. Then, I restarted and afterwards the phone didn't boot at all. It goes only to the bootloader menu. Last two days I was looking for the solution. In the HBOOT menu when I tried to the factory reset it only jumps into the fastboot menu, same thing for the recovery. When I am in the fastboot menu, if I click on reboot, or reboot bootloader it just reboot and the HBOOT menu comes again.
However, my HBOOT menu is locked and when I wanted to try unlock it. following problem happen :
- when I connect the phone to a Mac, Fastboot Devices detect (but only fastboot, ADB devices return nothing) the phone and I could get the token for unlocking procedure, but when I load the the unlock token which sent to me by mail from HTCDEV, nothing happen. it just say everything was successful on Terminal, but nothing shows up on the phone to Confirm unlocking procedure and sometimes it hangs and if I try pushing the token again (the bin file), I receive an error, fail to splash the screen (something like this). However, I already installed the HTC Sync Manager and every other possible driver I could find on the internet.
When I use windows, after installing HTC Sync and all of the drivers several time, still the command for Fastboot devices or ADB Devices return nothing. I don't care about the phone data or anything. I just want to like Flash the whole operating system and everything . thats fine. But nothing is working properly.
Please guide me if you have any idea about this problem.:crying::crying:
It happened to me too. Same sh1t. Camera didn't worked so i decided to restart the phone...from that time same story like yours.
same here, but i have an idea
when i do fastboot getvar all my baseband says N/A indicating corrupt or missing radio rom
the correct radio should be Radio_1.29.40g on mine based on the RUU i have on hand (used before)
RUU attempts to get into different mode and fails
i have been unable to extract the files from the RUU