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
Related
I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.
It's normal. Remove the phone, reboot it and run Revo again. It'll fail each time it tries to reboot but running it again does the stages one at a time. It'll eventually say you have root and do you want to install CWM
It happened with me many time....(NOTE: Do "DISABLE Fastboot" & "ENABLE Debuggin").
Try it again. When it boots into bootloader, you will eventually see on top "S-OFF" and the name "Revolutionary" as well. My Hboot version was totally different from the one mentioned on the "Guide to S-Off,Root,Flash CWM Recovery", But I did Root and flashed few ROM's till now. As soon as you instal CWM, install ROM Manager, Update the CWM and reboot into recovery and make a BACKUP(To be on safeside,as it was useful for me)
Good Luck.
Thanks. Ill keep trying and hopefully itll work eventually like you guys said.
First upgrade to Windows 7 But yeah, like the other 2 two guys said, just keep trying
Sent from my HTC Sensation Z710e using Tapatalk
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
HTC sync was the only way it worked for me, on the the third loss of communication it worked, s off. As others stated, keep trying, it works.
Sent from my HTC Sensation 4G using Tapatalk
Please Make Sure you have HTC Sync uninstalled and Droid Explorer uninstalled.
Did you check the Post #2 of http://forum.xda-developers.com/showthread.php?t=1192300
icepikk said:
ok ive continued trying over and over again and still nothing at all. its still stuck at the first part. i have usb debugging on and fast restart off. whats the better way to have the connection, charge only or htc sync cuz ive seen both
Click to expand...
Click to collapse
Try putting it to charge only, fastboot off and debugging on.
Try it 2-3 times.. eventually it gives s-off. Then you can install recovery by booting the phone & putting PGxx.zip on your sdcard. Then turn off the phone and boot to bootloader (Vol - and power) press vol + when it asks for update.
I had the same problem on the 3VO. When I disabled the fastboot option it worked!!
I was having this problem, USB debug on and fast boot off. No number of resets would cure it.
This is how I solved it, in case anyone is having the same problem:
The application reset the phone a second time, at which point it would get the error, I was left in the boot menu with S-On and a sad expression on my face.
During the first reboot into the boot menu, I quickly selected 'FASTBOOT USB' (I think it was vol down once, then power button). It then started processing the ZIP file before the application could reboot it a second time.
The application will still get the same error, however on your phone, you will now have S-Off.
Disclaimer: I have no idea what I'm doing, as evidenced by my post count of 1. It seems to work fine, but my phone may explode in 30 minutes time, I have no idea.
press power key
when it asks for the fastboot second time, just press the power key once and u will get the s-off
after s-off...how can we push recovery and flash su zip...for root...
sorry guys, but I just can't get this to work. I'm having the exact same issue
as, well a lot of people. "Communications with phone unexpectedly interrupted"
I got a brand spanking new Sensation. (if that could be part of the problem)
I've scowered the internet for a solution and tried just about anything I can find.
- Phone is set to USB debugging.
- fastboot is off
- set to charge only
- sync is uninstalled
- all drivers are installed
I've tried every possible combination of the above as well.
I've tried "when it asks for the fastboot second time, just press the power key once and u will get the s-off"
for the "Try it 2-3 times.. eventually it gives s-off" I just completed my 25th try,
and still no luck.
What the f**k is going on here? I'm no noble prize winner, but I've done
way trickier stuff than this.
any ideas?
Thanks guys,
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Hello Guys,
I solved this issue when I rooted my HTC desire using Unrevoked..
every time the desire rebooted, then the unrevoked said that " Communications with phone unexpectedly interrupted "
What I did is that,
- Phone is set to USB debugging.
- I couldn't find (fastboot) in my mobile, I just forgot about it.
- set the mobile to sync only when connected with usb cable.
- HTC sync is uninstalled from my computer.
- my computer recognize the device when it connected with usb cable otherwise you need to download some drivers (google it).
- then I connected my desire to the computer using the usb cable and start the unrevoked software.
- the unrevoked works and download some files then said that waiting for device to reboot. my device is rebooted.. when the logo of HTC started to appear in my mobile and just before the mobile completely works after rebooting, I have unplugged the usb cable from the desire..
- the unrevoked software still saying that "waiting for the device to reboot and it may take few mintues" !!
- when the desire is completely works and ready to use I have plugged it again to the computer and choose sync mode in very fast way before the unrevoked software detect it.
- then the unrevoked software start to download some files on the deasire and reboot it again for the second time and said that " waiting for device to reboot" .. in same way in have unplugged the usb cable after the HTC logo appears before it completely start and plug it again when the desire is completely working and ready to use and to respond.
- then the unrevoked software downloaded more files and said that " Done successfully" .
When I used this method, I have rooted and flashed my htc desire mobile and It is working fine. I just installed some custom roms on my mobile from the sd card using ClockworkMod Recovery v2.5.0.7 and it is working great..
I hope this will help somebody getting same problem.
Greeting from Saudi Arabia.
Mkman
AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
Thanks alot.I was same problem and done that way....
AussieMikey said:
I think this error message only applies to 1.17.0008 only...I did it successfully only by following this:
1. Disable Fastboot
2. Enable USB Debugging
3. Whenever the message says "waiting for..." unplug the usb fast...after the phone reboots...plug it back it...it will load a few seconds then it will say "waiting for fastboot etc." and keep repeating it (unplug USB wait for reboot before plug back in) till "waiting for fastboot (once moar)" and you will see S-OFF!!!
Click to expand...
Click to collapse
It applies to Hboot 1:18.0000 as well. However in my case, no amount of plugging and unplugging will fix the problem...
Edit: Solved by running on Win 7, outside of the VM where I usually do my phone stuff with adb installed ect... So not sure if adb was the issue or that the VM is WinXP. Anyway, seems clean install of drivers without adb installed fixed it.
try to install adb, it works
When I was rooting and s-off an htc desire on linux using revolution. It fails every time on "waiting for fastboot...", then exit with "communication with phone unexpe...".
I have adb installed with android sdk. however, i haven't started the daemon. The last time I use "adb devices" to check the connected device, this also enables the adb daemon. Then everything just goes well and i get s-off.
Remember to install adb and start it by executing "adb devices"
icepikk said:
I saw a similar issue in the EVO 3D forum, but nothing that helped my situation.
I run revolutionary on windows vista and everything seems to be working fine until it restarts and goes into bootloader, then revolutionary gives the error that "communications with phone unexpectedly interrupted. Press (almost) any key to exit." I have tried many times and still the error. I have left it at charge only, ive set it to HTC sync, and I have tried it with turning fast reboot off. Still not working. Any help would be greatly appreciated! Thank in advance.
Click to expand...
Click to collapse
i had same issue when i was using a VM windows machine, once i tried with a physical win machine it worked like a charm.
Dear forum,
I kind of hesitated to start a thread for my problem, but after a long time I still haven't found a solution. I have contacted HTC (no answer yet), but hope to resolve my problem in meanwhile instead of waiting 1 month+ for a replacement.
I got the -by now familiar- freeze, and after rebooting it would go beyond the HTC logo, then stay stuck in a backlit black screen mode. Tried removing the battery, sim card, sd card etc. Then decided to boot into recovery (vol down + power) which worked, but any option would freeze the phone, like factory reset which I tried first.
Right now, the phone already freezes at the carrier logo, and I can't even get into recovery again (vol down + power). The phone won't respond to the key presses, and eventially boot and freeze at the carrier logo. The weird thing is that before, after a lot of trying and re-inserting the battery, it would eventually boot and work just fine for about 1 in 10 tries.
Does anyone have any ideas what I could try? Any help would be greatly appreciated!
edit: Okay, after a while I finally managed to get into HBoot again! Now what should I do to get my phone resetted/fixed? I guess it's not possible for me to flash another ROM or something as i'm not rooted. Details shown are: S-OFF, HBOOT 98.0002
can you get into recovery from bootloader?
Seems like I now consistently can boot into HBOOT. When I choose recovery, it will reboot, show the carrier logo, show the green logo with circular arrows, and then switch to the phone logo with a red exclamation mark for two seconds. Then, it shuts off. Also, when I tried that just now, it buzzed for like 6 times very fast after turning off.
On the second try, exactly the same happened: red exclamation mark, screen off, +- 6 fast buzzes.
After doing that, it doesn't respond to vol down+power or power at all. After reinserting the battery, I can get back into HBOOT
edit: it didn't want to boot into HBOOT, but now it does again. Anyhow, chosing recovery is still green logo, red logo, screen off and some buzzes. The phone doesn't show up in "adb devices" neither.
Whatever you are going to do; do not root your device as it will void your warrenty.
Is there anything else i can try doing? The situation so far:
-normal boot just stays stuck into carrier logo
-hboot->recovery gives a reboot, green logo, switch to red logo, screen off and +- 6 fast buzzes, then nothing. Needs battery reinsertion to be able to respond to vol down + power again
-hboot->factory reset just freezes on the same screen, no response, needs battery removal
-noshow in adb devices (update: show in fastboot!)
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
maxxur said:
Another update: after messing arround with the drivers which didn't seem properly installed, I know have my device showing up in "fastboot devices".
Please, I feel like I'm so close to fixing this. What could I do next? Fastboot in some different recovery with more options or something? Anyone?
Could I simply run the RUU for my 3UK branded phone now?? If I get the RUU from http://forum.xda-developers.com/showthread.php?t=1002506, it seems that the RUU is "signed", which would result in S-ON? While right now my phone is S-OFF?
edit: So, I ran the proper RUU, it will find my device, propose me to downgrade from 1.47 something to 1.37 or so. Click next. Then it stays on the "rebooting the bootloader" phase indefinitely
Click to expand...
Click to collapse
Slow down maxxur, wait for this quesstion to be out there for long enough for someone to answer it.
Dont go on a battery pulling spree, coz that is the first and most tempting response on a frozen phone. But i hope you know what that can do to this phone...
Give the xda community some time to figure this out. Hold your ground till then. Need to go in to the theatre now. Will get back in the evening and try to figure this out.
Try running the RUU while in the fastboot menu (usb mode). Also my suggestion is not to make the process more complicated by downgrading - just reflash 1.47...
Thanks for the response guys
The RUU I found was 1.37. Could you point me to a 1.47 RUU for the 3UK network?
Also, running that RUU when in Fastboot USB mode is what I tried. The info on the RUU shows that it hangs indefinitely at "rebooting bootloader". That is expected, as when I try to manually reboot bootloader in my fastboot menu, my phone will also freeze.
I'm wondering if running a different recovery image could be of any help? Last night I tried running CWM recovery to see my options, by entering "fastboot boot recovery.img" but i'd get a "remote: not allow" error.
Have not noticed that you are not rooted!
Why don't you try the revolutionary tool? If you have luck it will restore your bootloader if it is broken (keep in mind that is not the best option because it will break you warranty). Then you will just need to flash an eng hboot and run the RUU, or better try some custom ROM
But in my opinion the best option for you is to go for a replacement rather to try yourself, since you dont have any custom software on it it has to be covered by your warranty (probably it is a faulty device to go like this from nothing).
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
maxxur said:
Thanks for the suggestion. Are there any other safer options for me?
Could I try extracting the rom.zip from the RUU and manually put it on the SD card, then try to flash it in CWM recovery? Since "fastboot boot recovery" doesn't work though, could I try "fastboot flash recovery" to get CWM on there? Atm the "stock recovery" seems to be dead anyway, as when I choose it in HBOOT, the phone simply freezes.
Click to expand...
Click to collapse
Of course you can if you are eager to try this. When you run the RUU, even when there is no phone connected there is a folder in your C: drive created (I assume that you are using Windows). Open your Windows Explorer and search for the rom.zip. When you have it copy it somewhere and close the RUU screen. Then if you open the RUU all the *.img files are there. You can try flashing the stock recovery or hboot or whatewer using the fastboot command. But I have to say again the best option for you is to bring the phone for a repair before you end up with something irreversible and void your warranty.
Thanks for keeping me sane on what to do with my problem Mentally, I came to the point where I'd go flash CWM recovery on my phone and try to flash that RUU rom from there, but you helped me get around that thought and now I made arrangements for HTC to come and pick it up. I'll keep you guys posted!
PS: you've got to love our desire s community, it's the best.
Cheered too early
Now HTC suddenly responds that while entering my phone in their warranty service thingy and the phone seemed to be 3G UK branded, they told me they "can't" do repairs for those.
Seriously, HTC is trying to troll me saying the inner hardware could differ between a UK and a Belgian Desire S?? Could this be true in any way?? :/
Maybe some parts are cheaper but with the same parameters...but I thought that when you have a branded phone you should seek your warrancy support from the carrier's office?!?
Sent from my HTC Desire S
Options for solution!
Option 1: Copy rom.zip (from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed) to your sd rename it to PG88IMG.zip and let m boot into hboot.
If option 1 is not ok try option 2.
Option 2: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU then after that run ruu RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.
If option 2 not OK then there is option 3.
Option 3: Boot in to fastboot connect it to your computer and on your computer open dos/terminal run fastboot oem rebootRUU after that run in dos/terminal fastboot flash zip rom.zip (extracted from RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed)
Let me know if one of these option worked for you if not I can help you with reflashing your hboot again.
NikMel,
Thank you so much for the tips. Currently I'm trying the first HBOOT + .ZIP method. It detected it, asked me to update and is now showing a pink "Updating" sign. How long should this normally take? I have a strong feeling it simply froze again, and it really turns out to be a hardware problem.
Is that updating next to radio?
If yes it will take realy long so wait!!
Please Help!!
I have an Inspire 4G and i was trying to put ENG-OFF following this steps: http://forum.xda-developers.com/showthread.php?t=855403 to run "Desire HD s easy-off.exe" gave me "Bootloader is Corrupt. DO NOT REBOOT!" (He went out alone) and I could not take him with anything, you connect to the charger and nothing, the PC and nothing, as 20 minutes after i had pressed the power button turned on the cel with the white screen and vibrating continuously approx 8min, the problem is that in the beginning it takes too ... Now every time I reboot so, and if I discharge the battery will be useless because I do not grab power when connected to the charger or the pc .....
- I can not enter the bootloader, I managed to do with the "Super Tool V3" and the recovery reinstall the ROM, I thought it would end the problem but stayed the same, takes too long to start and does not grasp the power of the charger ... .
What can i do? What is it?
If I noticed that the bootloader says "ENG-OFF" and if you step back to ENG-ON?
I greatly appreciate (and have no idea how) that can help me please .....
(sorry about my english)
You have a newer version Inspire that came preloaded with Gingerbread. I believe trying to achieve Eng-off has flashed a previous bootloader that is incompatible with your phone. Since you say you can't get to your bootloader then you will need to install the stock ATT gingerbread ROM using your PC. Get it here: http://dl4.htc.com/RUU_Ace_Gingerbr...60.25_26.10.04.03_M_release_200368_signed.exe You will then have to re-root using the Hack Kit.
rikrdoVe said:
Please Help!!
I have an Inspire 4G and i was trying to put ENG-OFF following this steps: http://forum.xda-developers.com/showthread.php?t=855403 to run "Desire HD s easy-off.exe" gave me "Bootloader is Corrupt. DO NOT REBOOT!" (He went out alone) and I could not take him with anything, you connect to the charger and nothing, the PC and nothing, as 20 minutes after i had pressed the power button turned on the cel with the white screen and vibrating continuously approx 8min, the problem is that in the beginning it takes too ... Now every time I reboot so, and if I discharge the battery will be useless because I do not grab power when connected to the charger or the pc .....
- I can not enter the bootloader, I managed to do with the "Super Tool V3" and the recovery reinstall the ROM, I thought it would end the problem but stayed the same, takes too long to start and does not grasp the power of the charger ... .
What can i do? What is it?
If I noticed that the bootloader says "ENG-OFF" and if you step back to ENG-ON?
I greatly appreciate (and have no idea how) that can help me please .....
(sorry about my english)
Click to expand...
Click to collapse
Maybe u missed the part where it said that it was not compatible with GB shipped devices. You have definetely messed your bootloader. You need to fix that first. Hit the Hack Kit IRC channel and we will lend you a hand.
http://webchat.freenode.net/?channels=#aahkSupport
Mora ntoChni
Agoattamer said:
You have a newer version Inspire that came preloaded with Gingerbread. I believe trying to achieve Eng-off has flashed a previous bootloader that is incompatible with your phone. Since you say you can't get to your bootloader then you will need to install the stock ATT gingerbread ROM using your PC. You will then have to re-root using the Hack Kit.
Click to expand...
Click to collapse
Well, i flashed via RUU with PD98IMG.zip from bootloader, i can enter to hboot only with "Super Tool V·" but Vol down + Power doesnt work..
But i'm still with the same problem, it takes 20 minutes to start...
Any other option?
Agoattamer said:
You have a newer version Inspire that came preloaded with Gingerbread. I believe trying to achieve Eng-off has flashed a previous bootloader that is incompatible with your phone. Since you say you can't get to your bootloader then you will need to install the stock ATT gingerbread ROM using your PC. You will then have to re-root using the Hack Kit.
Click to expand...
Click to collapse
Well, i flashed via RUU with PD98IMG.zip from bootloader, i can enter to hboot only with "Super Tool V·" but Vol down + Power doesnt work..
But i'm still with the same problem, it takes 20 minutes to start...
Any other option?
First of all I apologize if this has been covered, I have been trying to find a solution for 3 days straight. I have a Rogers Wireless HTC One X I managed to unlock bootloader and root as well as having access to TWRP 2.1.8. recovery.
My problem is when I tried to apply the 3 dot removal mod my phone suddenly would not boot past the first screen, and a message would appear for developers use do not distribute but just stay on that screen. I have tried numerous things to no avail. I can boot in recovery and mount sd card from there (but have not found a successful way to restore from within recovery mode) otherwise in fastboot etc. the computer does mount the phone at all. it will not mount as a device properly so I cannot run the RUU and flash to stock.
So I am left with a unmountable and unbootable phone (brick) and have no other ideas on how to fix it if possible. BTW the device does show in device mgr and the computer gives the connect and disconnect alert, but it will not mount. Also, I have read the bootloader has to be relocked to flash back to stock if I relock the phone I cannot access recovery therefore an endless nightmare. Also, within TWRP recovery I try to reboot and it gives an error saying no Android OS found, install a rom or restore from backup (which I have neither) so I have to hold the power and dwn volume button to reboot each time to switch from recovery to fastboot. I think its toast.
Thank you in advance for any responses, I have been up almost 36 hours straight trying to figure this out and the phone is not even a week old. :crying:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
gunnyman said:
There's a link in dev to unofficial twrp with usb mount support install that by following the directions in the thread. Then you'll be able to copy a rom to the phone for flashing.
Click to expand...
Click to collapse
Thank you very much I will look into that today. Fingers crossed!
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
stnguyen09 said:
Or you can install HTC Sync on your computer and that may allow you to use a RUU to flash back to stock. HTC Sync has the required drivers to make a Windows PC recognize the HOX.
Click to expand...
Click to collapse
Yes, thank you I have HTC Sync installed and it does not recognize the phone when it is connected either. I will keep searching. Thanks.
ethantarheels123 said:
i ran into a similar situation about a week ago. hard shut down the phone by holding down power button for like 10 seconds, then boot into bootloader. hit fastboot. connect your phone to computer, and fastboot oem lock bootloader. now you can ruu. Download Rogers RUU utility and follow steps. Voila! Phone is just like new! but first make sure you still have your old unlock_bin code in case you want to reunlock bootloader.
Click to expand...
Click to collapse
Yes, I have tried relocking bootloader, it did not help with the phone being recognized by the computer also when I oem lock I cannot access recovery and such. I will have some more time to poke around with it, I have downloaded the RUU utility although it sends back error with device not found. Thanks for your reply, I will keep at it I know the phone can not be bricked, well I am hoping not!
edit
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). The Switched to the Galaxy note & S3 for a while NOw Im using the HTC one S. I normally never have these problems or ever post on the forums. But Im desperate for fast help. I know how to do everything on both the htc evo 4g and design.
but The Ville is diff. without the removable battery
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
ultimul said:
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
Click to expand...
Click to collapse
I have the HTC One S Ville
I was stating how I use to have the evo
gisaac2157 said:
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). There is no development forum for that devices in XDA so I used SDX-DEV I actually started learning how to kang my own roms.
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
Click to expand...
Click to collapse
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
gisaac2157 said:
I have the HTC One S Ville
I was stating how I use to have the evo
Click to expand...
Click to collapse
can you reboot into recovery/fastboot? press the power button for 5-7 seconds until the keys start blinking;
the phone should reset after it
some RUU, you can find here:
http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Thanks so much.
AKToronto said:
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See <font color="red"> as a new member cant post links</font> for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
Click to expand...
Click to collapse
I feel really stupid for not knowing THAT. Now whats up with the energy rom? the thread says stable. How am I suppose to flash it?