Related
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!
Hey guys,
Got a bit of a weird situation here and have spent 3 days pondering this and surfing the web with no success -
I noticed my friends HTC Desire S had a crack in the screen so offered to repair it for her, free of charge - say for my cost. I didn't get a chance to do it before holiday so went to pick it up when I got back and she explained that since then the phone has developed a fault and now won't turn on past the boot logo. I have no idea if this is related to her dropping it - I'm assuming it was a bad app download or something?
I followed various guides on YouTube, XDA forums and other external sources but am getting stuck at a particular stage which is what I think I need help with - I may just be chasing my tail but don't have the background to know otherwise. I have download Fastboot drivers, Revolutionary etc. with the intention of S-OFFing the phone and re-flashing the software - doesn't technically need to be custom but it seems easier to get hold of. I do not know if Fastboot or debugging mode are turned on/off due to the inability to turn the phone on.
Revolution sticks 'Waiting for Device...' - Here's what I've tried:
- Factory resetting the device from the bootloader menu but it freezes. (It also freezes if I select 'reboot bootloader')
- I have tried multiple USB cables in 3 laptops (with the drivers installed) but have had no success.
- Using Fastboot.exe to test if the laptops can see the device - which they can.
Eventually I got frustrated with this so moved on to the screen - no problems replacing that. No internal damage that I can see.
All the buttons work, it still vibrates etc. I can't test the sound - I'm running out of troubleshooting ideas and trying not to be too invasive where I'm unsure of what I'm doing to save bricking the phone.
Here is the Bootloader Info:
""SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011,17:29:31""
Does anyone have any suggestions of a path to follow or any step by steps to eradicate my problem?
I will post back my triumph (if possible) so others can hopefully overcome it!
Also, any advice on which RUU to use? I don't know the network the phone is on but can find it out.
Thanks alot for reading!
Josh
If it is not a hardware fault using a RUU should make the phone running again.
You do not need additional modification, just start the RUU while connected to a PC is FASTBOOT USB mode.
How to know the proper RUU version see here
P.S.: this will work only if you have not tried any other RUU so far.
Revolutionary uses adb not fastboot, this is the reason it cannot find the device. It will work only when fully booted in the OS or in a custom recovery.
Sent from my HTC Desire S
Thanks for the quick reply mate, I started downloading a Vodaphone RUU straightaway.
I am now having an issue with this - the phone is plugged in and sat waiting in Fastboot USB (on the bootloader,) I run the RUU on the computer, run through all the menu's and when it attempts to apply the Radio Update it sticks at 'Rebooting the Bootloader' and seemingly freezes the phone. As mentioned above, if I try this manually it does the same thing.
Any Ideas?
If it is the right RUU then most probably it is some kind of hardware problem. Sorry but this was the only software fix that I can suggest.
You can try to revive it with JTAG if you have such service in your area.
Sent from my HTC Desire S
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Scuba_Luv said:
I bought a HTC One S for T-Mobile USA. Has been working flawlessly. Today I got an OTA and my world is now upside down. I have spent 5 hours trying countless things to get my phone back up to no avail.
my phone stats:
hboot 1.09.0000
radio 0.16.31501s.16_2
open dsp-v28.1.0.32.0504
emmc-boot apr 2 2012,21:08:24
UNLOCKED
TAMPERED
How do I get back to square one and turn this phone back into something usable?
It has something called TWRP 2.1.7 installed on it and I have tried fastboot and a host of other things to remove it. I have even tried the thread on sending your phone back to stock but I can't access RUU because it won't load the driver. I have never rooted this phone nor do I believe USB Debugging was turned on before I accepted the OTA. I can communicate via fastboot in the command shell via a usb cable. The PC wont mound the SD card so I can't copy a new image and reboot this thing on a different rom and then send it back to stock.
I am about ready to throw it away because i can't seem to get a .zip file to it so it will run again (for putting a working build on it). There are no images to boot to. Somehow that got wiped and no backup was done. I don't give a poop if the data is whiped. Its all backed up via dropbox and exchange. I just want it up and running so i can use RUU and send it back to stock.
Any help would be appreciated.
Click to expand...
Click to collapse
I hate to tell you this but if you never unlocked or rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Behold_this said:
I hate to tell you this but if you never unlocked and rooted your phone, somebody did. Your device is unlocked and running a custom recovery therefore you cannot accept over the air updates and that is your problem. You did not buy your phone that way from T-Mobile so what did you really do to get to this point?
Click to expand...
Click to collapse
I never said I bought it as OEM. I also never thought to ask the guy I got it from if he rooted it or unlocked it.
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
beats4x said:
Relocking the boot loader then running an RUU should fix the issue. Once you do that enter the recovery and wipe everything/factory reset.
Then if you are trying to run a custom ROM you should be able to mount your SD card and push one to the phone.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Great reply however I am short on knowledge on how to do what you have recommended. I don't know how to relock the boot loader nor can I run RUU because I can't get the driver installed. Any help would be awesome. Thank in advance. Sorry I'm a noob at this.
In the dev section there is an all in one toolkit that will execute the correct scripts for you. Download it, then run it. You may also need the HTC sync drivers installed on your computer.
Once you see that the bootloader is locked run the ruu.
And don't apologize for being a noob, I am too lol. We all need help to get started.
Sent from my HTC One S using xda premium
If you install HTC sync to your pc it should install the driver's you need. Then install the one s tool kit in developers section to relock. Then run ruu.
Also, anything you see in blue text is what you'll need to type, or copy/paste, to avoid any quote confusion.
Files You Need:
T-Mobile USA RUU file (mirror) - it's about 563 mb, and worth saving once you download it.
Extremely Important: If you're on another carrier you'll need a different RUU file - DO NOT try and run this RUU file, it could really screw you up. Go to this link to find the right RUU file.
HTC Drivers (mirror) - You probably already have the drivers installed if you're needing this thread, but just in case...
ADB / Fastboot (mirror) - same as the drivers, but again, just in case...
Initial Setup:
Again, some of this might be redundant as you might already have this setup if you rooted/unlocked.
Install the HTC drivers if you haven't already
Unzip the adbfastboot.zip file to your desktop (anywhere, but I find it easiest to get to it on the desktop for my habits)
Getting into the bootloader (hboot):
If you're stuck in a boot loop, pull the batt... oh wait, we can't do that here. To perform a hard reset, hold down the power button for 10 seconds - in the process you'll see the softkeys start blinking, then it should reset. As soon as it starts to reset, release power, and hold down the volume-down button - hold it until hboot pops up (white screen, colored text).
If you're phone is fully powered off (make sure "fastboot" is disabled - settings > power), hold the volume-down key and while holding it, press and hold power for a few seconds. You can probably release the power button, just make sure you keep holding volume-down - after probably 3-5 seconds (maybe a bit more), hboot should come up.
If the phone is on and you're plugged in to your computer, make sure "usb debugging is enabled" (settings > developer options), shift+right-click the adbfastboot directory on your desktop (or wherever you put it), choose "open command window here", and in the prompt that comes up, input adb reboot bootloader.
Restoring:
Once you're in hboot, make sure you select Fastboot (if you don't see it, you're in Fastboot already). In the command prompt referenced above, input fastboot oem lock. This will relock your bootloader in order to allow the RUU to run. Historically this has been necessary for an RUU to run, but I haven't actually tested it without relocking on the One S, and assumed based on previous HTC devices that this would continue to be the case. Edit: thanks rbrookstx for confirming that re-locking is necessary
Your phone will reboot when it relocks - follow the steps above to get back into hboot.
Once you're back in hboot, make sure you're in Fastboot, and open / run the RUU file. It'll go through some initial prompts, then it should start. It takes about 10-15 minutes, maybe less, depending on your computer.
Once it's done, it'll simply go back into hboot - reboot, and you're good to go.
A couple of notes:
When you unlocked and flashed a custom recovery (if you did that), hboot probably said "tampered with" and when it booted up, it probably had a red message under the "HTC" logo about being a developer only device. That should be gone now. It should boot up clean, and hboot should simply say "relocked", with no tampered message.
Until a better solution comes out, once you unlock the bootloader with HTC's official method, it can never be locked the way it was from the factory. "Relocked" is the best you can do.
Click to expand...
Click to collapse
This is what worked. I had to search the internet for this stuff but the HTC driver, the fast boot and the RUU with a matching or higher radio number all made it work out.
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
I was updating my inspire 4g from the HTC's update sense 3.0. I got it directly from their site. My micro-usb cable apparently wiggled loose during the "Installing Bootloader" phase of the installation. Now my phone will turn on after about 20 minutes. It does not respond to me pressing the power button and I can not get it into recovery mode. It hangs at either a Black HTC screen or a White HTC screen. It's different each time it boots. When it boots into the white HTC screen it vibrates for a good 5 minutes then eventually boots up. My phone is not rooted. Is there anything that I can do to fix this?
EDIT: I just booted into recovery after holding the volume down and power button for like 5 minutes. Although, my volume and power buttons do not work in recovery mode :/
fix
235tylerlee said:
I was updating my inspire 4g from the HTC's update sense 3.0. I got it directly from their site. My micro-usb cable apparently wiggled loose during the "Installing Bootloader" phase of the installation. Now my phone will turn on after about 20 minutes. It does not respond to me pressing the power button and I can not get it into recovery mode. It hangs at either a Black HTC screen or a White HTC screen. It's different each time it boots. When it boots into the white HTC screen it vibrates for a good 5 minutes then eventually boots up. My phone is not rooted. Is there anything that I can do to fix this?
EDIT: I just booted into recovery after holding the volume down and power button for like 5 minutes. Although, my volume and power buttons do not work in recovery mode :/
Click to expand...
Click to collapse
I've same problem here
I'm searching for fix about 5-6 hours
If your phone boots up, it's more easy to fix it.
All you need now is to turn you phone fully to android desktop and follow this thread
tau.shadowchild.nl/attn1/?p=188
(I'm new here, i can't use "insert link" option, copy and paste link in browser)
or try this http://forum.xda-developers.com/showthread.php?t=1875134&page=2
Mine even doesn't boot up after 2 hours
Takes up to 20 minutes to enter in hboot, then up to 40 minutes to enter in fastboot
and then another 40 minute for fastboot usb
But still adb doesn't recognize device :/
Any help would be greatly appreciated
uNdea said:
I've same problem here
I'm searching for fix about 5-6 hours
If your phone boots up, it's more easy to fix it.
All you need now is to turn you phone fully to android desktop and follow this thread
tau.shadowchild.nl/attn1/?p=188
(I'm new here, i can't use "insert link" option, copy and paste link in browser)
or try this http://forum.xda-developers.com/showthread.php?t=1875134&page=2
Mine even doesn't boot up after 2 hours
Takes up to 20 minutes to enter in hboot, then up to 40 minutes to enter in fastboot
and then another 40 minute for fastboot usb
But still adb doesn't recognize device :/
Any help would be greatly appreciated
Click to expand...
Click to collapse
It sucks man! but I have finally booted my phone this morning. In order for my phone to boot it must be plugged into my computer for some reason?
is there a way to fix the bootloader while the phone is on and plugged into the pc? Or is there a way to boot into recovery without turning the phone off? BTW my device is not rooted.
EDIT: I attempted to redo the AT&T update and it failed because it took to long for my device to boot. So now, I'm attempting to root it again threw Ace Advanced Hack Kit. I know that this kit is no longer supported but I did use it in the past and it worked flawlessly. So now, AAHK is waiting for my device to boot. AAHK aparently doesnt care how long it takes so I guess thats a plus. My phone will eventually turn on. I'll post the results when/if it finishes
EDIT 2: AAHK aparently did not work. AAHK still says waiting for device after the device booted normally.
235tylerlee said:
It sucks man! but I have finally booted my phone this morning. In order for my phone to boot it must be plugged into my computer for some reason?
is there a way to fix the bootloader while the phone is on and plugged into the pc? Or is there a way to boot into recovery without turning the phone off? BTW my device is not rooted.
EDIT: I attempted to redo the AT&T update and it failed because it took to long for my device to boot. So now, I'm attempting to root it again threw Ace Advanced Hack Kit. I know that this kit is no longer supported but I did use it in the past and it worked flawlessly. So now, AAHK is waiting for my device to boot. AAHK aparently doesnt care how long it takes so I guess thats a plus. My phone will eventually turn on. I'll post the results when/if it finishes
EDIT 2: AAHK aparently did not work. AAHK still says waiting for device after the device booted normally.
Click to expand...
Click to collapse
If you try to run a RUU your device will probably end up bricked. You need to fix that using this:
http://tau.shadowchild.nl/attn1/?p=188
Any other method might leave you with a dead $200 device.
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
How to fix Corrupted bootloader with RUU
glevitan said:
If you try to run a RUU your device will probably end up bricked. You need to fix that using this:
Any other method might leave you with a dead $200 device.
Click to expand...
Click to collapse
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
bananagranola said:
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
Click to expand...
Click to collapse
Well, thank you guys. I'm in the process of reading everything. I messed my bootloader up by updating my phone btw not trying to root it. BUT thank you guys for the links. I'll post back with my results after I finish doing everything that the articles insist that I try.
uNdea said:
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
Click to expand...
Click to collapse
Your english is pretty good
BUT what you suggested is almost exactly what the above said link suggested. only he did not inform you about the Device manager things.
Thanks for the update
235tylerlee said:
Your english is pretty good
BUT what you suggested is almost exactly what the above said link suggested. only he did not inform you about the Device manager things.
Thanks for the update
Click to expand...
Click to collapse
I don't know, when i researched i didn't find bootloader fix with RUU, everyone warned about brick, so i was little confused when tried that.
It was my last hope to fix, because PD98IMG.zip way doesn't worked for me, neither "boot up and ADB" method. Some thread was about making goldcard and then flashing hboot like pd98img, but i hadn't goldcard. Also, i had S-ON and i think there was no way for S-Off
Anyway, thanks to xda and google :good:
Hope this would help you too ))
bananagranola said:
AAHK is not only not supported. The server hosting the files it needs has been taken down.
In any case, you both sound like you have messed bootloaders. In the link in my signature, post #7 has a PDF guide that has, among other things, instructions on how to fix that. Make sure you read carefully.
Click to expand...
Click to collapse
I have attempted what this PDF guide has insisted that I do and I get an error. The cmd prompt says the following
"C:\Users\mine\Desktop\help\tools>fastboot flash zip PD98IMG-HBFX.zip
< waiting for device >
send 'zip' (262 KB)...OKAY [ 0.080s]
writing 'zip'...FAILED(status read failed(Too many links))
finished. total time:1911.686s
C:Users\mine\Desktop\help\tools>'
EDIT: now it booted into something..idk. It says the following
ACE PVT SHIP S-OFF RL
HBOOT-0.85.0019
NUCRIO-0437
RADIO-26.06.04.06_M
eMMC-boot
Dec 27 2010 14:47:30
RUU
NEVERMIND Aparently the article was true..I am a dumbass..I fixed it thank you guys
HElp
uNdea said:
I've fixed my bootloader with RUU
It was S-ON, so i went to RUU and it worked flawlessly.
AAHK wasn't recognized phone, even when it was connected with Fastboot USB.
I corrupted bootloader when i was trying to manually downgrade from 2.3.5 (Because AAHK don't worked, file server was down)
Phone was unable to boot up (I've waited about 2 hours and it was still stuck on htc logo)
so was adb, when in Device Manager "my htc" was shown, command "adb devices" had no result
I'll tell my way (Full process takes about 3-4 hours, cross your fingers and drink some coffee, let's go..) :
I'm not developer. I tried and fixed my device with this, because other known methods don't worked for me. So read carefully every step and use it at own risk!
First, you need to remove sd card to skip PD98IMG check and make entire process faster
1) remove sd card
2) remove battery (make sure it's charged at least 50-60%)
3) insert battery and go to hboot screen (Press volume down and Power button same time, be patient and keep holding buttons, it will take about 5-10 minutes to show up hboot)
4) Wait until hboot loads fully (takes about 10-20 minute) and when you can go down or up with volume buttons, go to Fastboot
5) Wait there to load fastboot (10-20 minutes or little more) and then connect USB cable
6) Wait there for 15-30 minutes, untill PC recognizes device (Go to Device Manager and check it out if there's "Android USB devices" and "my htc" are shown) for me, it was connected and disconnected 2-3 times, Windows said to check the device and etc, but at least it was shown correctly
7) Make sure that hboot says "Fastboot USB" and run the RUU (I'm new here and can't use "insert link" function, so paste this link in browser and download, --> 4shared.com/file/XORxHMZx/RUU_Ace_Gingerbread_S_Cingular.html )
8) RUU would detect device this time and ask to update system image or radio or hboot (I don't remember what it was exactly) to 2.x.x..,
accept and click next, It would say that device will be rebooted into recovery (black screen with HTC logo)
9) Wait till the device is fully loaded in recovery mode (about 20-30 minutes, check if it's available in Device Manager again)
in 10 minutes RUU would say device isn't recongized or something like that and exit. Don't worry about it
10) When device is recongized in device manager, run the RUU again. It will ask to update to 2.x.x.., like it asked in step 8, click next. This time it wouldn't reboot, because you're already in recovery mode. It will start the update process. Be patient, it would take about 2-3 hours to fully restore. Don't think that it's stuck and don't cancel process, just wait..
Yeaaah, take deep breathe, you have done it
When it finishes, phone would restart and boot up normally with new hboot, it would be android 2.3.3, so you can run AAHK and root&unlock your device without problems
( Sorry for my English )
Click to expand...
Click to collapse
My Bootloader hangs up when booted...and i have the same problem as u guyz mentioned! So plz help me
waleedbutt256 said:
My Bootloader hangs up when booted...and i have the same problem as u guyz mentioned! So plz help me
Click to expand...
Click to collapse
write detailed information, how u corrupted bootloader, what u tried to fix it and etc. If u tried my method, on which state it hangs up?
uNdea said:
write detailed information, how u corrupted bootloader, what u tried to fix it and etc. If u tried my method, on which state it hangs up?
Click to expand...
Click to collapse
flashed a froyo hboot on your HTC Inspire/DHD shipped with gingerbread. Phone takes forever to turn on, then it buzzes like cheap vibrator got hit by lightning for two or three minutes – then it finally begins to boot. I tried Using IAMADUMBASS FIX by attn1..which is specifically for this problem but my DHD hangs up in bootloader + when flashing unknown error occurs!
waleedbutt256 said:
flashed a froyo hboot on your HTC Inspire/DHD shipped with gingerbread. Phone takes forever to turn on, then it buzzes like cheap vibrator got hit by lightning for two or three minutes – then it finally begins to boot. I tried Using IAMADUMBASS FIX by attn1..which is specifically for this problem but my DHD hangs up in bootloader + when flashing unknown error occurs!
Click to expand...
Click to collapse
So was my phone too, and attn1 fix doesn't worked. Try that method that I've described above step by step and let me know result))
I've checked RUU download link and it's still working