I've seen a couple of threads about this but none of them have the same issues as I have or they remain unanswered.
My HTC Sensation (EU version) won't boot up at all. I can't boot it into recovery or bootloader and when charging the light doesn't turn on.
It recently started to randomly reboot and at one point it completely corrupted all files on my SD card. However, it worked ok after I bought a new SD card and the random reboots didn't bother me that much. Today when I woke up however, I saw that it wouldn't respond to me pressing the power button. I also noticed that the charging light wasn't on (it was plugged into the wall overnight).
I tried removing/reinserting the battery, I tried booting into recovery and bootloader, I tried connecting it to my PC and forcing it to boot into bootloader but nothing works. To clear things up, when I try to boot it up nothing happens. The screen stays black and doesn't power on.
The only thing that leads me to believe there's still a chance of it working is that when I plug it into the PC, my PC detects it (although it's unable to install the required drivers for it).
I'd appreciate any help I can get.
intestro said:
I've seen a couple of threads about this but none of them have the same issues as I have or they remain unanswered.
My HTC Sensation (EU version) won't boot up at all. I can't boot it into recovery or bootloader and when charging the light doesn't turn on.
It recently started to randomly reboot and at one point it completely corrupted all files on my SD card. However, it worked ok after I bought a new SD card and the random reboots didn't bother me that much. Today when I woke up however, I saw that it wouldn't respond to me pressing the power button. I also noticed that the charging light wasn't on (it was plugged into the wall overnight).
I tried removing/reinserting the battery, I tried booting into recovery and bootloader, I tried connecting it to my PC and forcing it to boot into bootloader but nothing works. To clear things up, when I try to boot it up nothing happens. The screen stays black and doesn't power on.
The only thing that leads me to believe there's still a chance of it working is that when I plug it into the PC, my PC detects it (although it's unable to install the required drivers for it).
I'd appreciate any help I can get.
Click to expand...
Click to collapse
open a cmd window in your adb and fastboot folder and try this command
adb boot bootloader
rzr86 said:
open a cmd window in your adb and fastboot folder and try this command
adb boot bootloader
Click to expand...
Click to collapse
That command didn't work for me and displayed a wall of text. After looking through it I found a similar command which I tried
adb reboot-bootloader
When I entered that it said that it was starting the daemon on port, that the daemon had started succesfully and then it gives me the error: device not found.
intestro said:
That command didn't work for me and displayed a wall of text. After looking through it I found a similar command which I tried
adb reboot-bootloader
When I entered that it said that it was starting the daemon on port, that the daemon had started succesfully and then it gives me the error: device not found.
Click to expand...
Click to collapse
opps i mean reboot
i don't know why i forgot that
previously you said that it detects it
how it detects it?
When I connect the phone to my PC I hear the sound that windows makes when you connect a USB device.
intestro said:
When I connect the phone to my PC I hear the sound that windows makes when you connect a USB device.
Click to expand...
Click to collapse
charge the device without battery,sim and sdcard for 4-5 hours
put them back and switch it on
see how it goes
if that fails then try to switch on the device with a different battery
rzr86 said:
charge the device without battery,sim and sdcard for 4-5 hours
put them back and switch it on
see how it goes
if that fails then try to switch on the device with a different battery
Click to expand...
Click to collapse
I tried the charging method but it didn't seem to do anything.
I don't have a different battery that fits in there. Can I use a smaller and lower capacity battery as well and just connect the contacts? I don't wanna shortcut anything
intestro said:
I tried the charging method but it didn't seem to do anything.
I don't have a different battery that fits in there. Can I use a smaller and lower capacity battery as well and just connect the contacts? I don't wanna shortcut anything
Click to expand...
Click to collapse
No. Don't even try connecting other battery.
Sent from my HTC Sensation Z710e
MrJukeHardbane said:
No. Don't even try connecting other battery.
Click to expand...
Click to collapse
So are there any options left for me? I've read some stuff about Jtagging but I'm not planning on getting a box or paying someone to do it for me.
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.
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
sinaisinai43 said:
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Click to expand...
Click to collapse
I'm having the same exact issue, except with SlimBean 4.3. My phone is stuck in Fastboot (and says "FASTBOOT - NO BOOT OR RECOVERY IMG") and my phone will charge but can't be detected by *any* computer. I've tried three Windows 7 PCs of different makes and an Ubuntu 13.04 box and three different USB cables that all connect my other phone and my tablet fine - none can see it. (It was connecting fine to PC including being seen by ADB prior to this)
My power button is working, but it is also automatically booting into fastboot on its own when I plug it into the computer. Any of the options (besides "Power Off", which performs as advertised) just brings it back to Fastboot.
When I say can't be detected by a computer, I mean there is no USBDeview device listed and there is no 'connect' or 'disconnect' sound on the PC. ADB can't see it.
Yeah, it's strange. Did you find a solution yet, by chance?
sinaisinai43 said:
Yeah, it's strange. Did you find a solution yet, by chance?
Click to expand...
Click to collapse
Nothing yet. Thinking of buying an phone with a busted screen or something and swapping out the internals... I think it's PROBABLY the NAND chip. What I'm suspecting is that because there are several versions of the Nexus S, we might have used the wrong images. I have no idea if this is correct, but it's the only thing I can think of.
My phone's sticker says i9020 on the inside, but D720 (or whatever) when I look up the EIN.
Just hoping somebody sees this and offers a suggestion... I'm getting ready to buy a refurb and put the 'new' body over it so at least I have a functioning, new-ish phone.
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1
gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh
lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh
Hi, I hope someone can help, because this looks like a strange one. I was not able to find something similar to it.
I attempted to unlock the boot loader and install TWRP. This worked fine. But I noticed that the fastboot icon changed from being a gray CM face to a white one. That was done using using the Toolbox v6.
I later noticed that some android apps are listed as not compatible with the device. So I thought I'll reverse the process. So I plug it in, and clicked lock boat loader, did a restart; wanting to to flash the stock-recovery. My goal was to reset it back to normal.
The issue I have now is that whenever I try to fastboot, it boots into the white CM face, and the second I connected to the computer via USB, it restart. If I try to hold power+volume up again, it just goes black and does not restart. When I unplug the USB, it restarts again.
How can I get it to reboot into fastboot and remain in fastboot after being connected to USB?
Any ideas? The tools listed in this thread:
http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
require that I fastboot, then connect to the computer. but my very issue is that when it connects to USB it just restarts.
Any ideas?
Thanks,
Maher
melkhaldi said:
Hi, I hope someone can help, because this looks like a strange one. I was not able to find something similar to it.
I attempted to unlock the boot loader and install TWRP. This worked fine. But I noticed that the fastboot icon changed from being a gray CM face to a white one. That was done using using the Toolbox v6.
I later noticed that some android apps are listed as not compatible with the device. So I thought I'll reverse the process. So I plug it in, and clicked lock boat loader, did a restart; wanting to to flash the stock-recovery. My goal was to reset it back to normal.
The issue I have now is that whenever I try to fastboot, it boots into the white CM face, and the second I connected to the computer via USB, it restart. If I try to hold power+volume up again, it just goes black and does not restart. When I unplug the USB, it restarts again.
How can I get it to reboot into fastboot and remain in fastboot after being connected to USB?
Any ideas? The tools listed in this thread:
http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
require that I fastboot, then connect to the computer. but my very issue is that when it connects to USB it just restarts.
Any ideas?
Thanks,
Maher
Click to expand...
Click to collapse
It seems to work fine now... I honestly kept tinkering around, it seems to work now. I wish I could offer a better answer. But I am not sure I am able to remember what I did exactly... it was a bunch of plugging and unplugging, restarts, and lots of prayers.
I had a same problem and similar solution
I believe i had found the solution when I change the USB port from my notebook where I had plug my the USB cable from my smartphone.
Same issue here.. I think it is because of USB 3.0. My laptop don't have USB 2.0 hence fastboot or adb wont detect my device, I was using a USB extender which works as USB hub (2.0) it worked many times before now again facing same reboot on usb connection issue.
After 8 years of tinkering with Android phones I have no clue how this happened.
PIXEL 2 (Walleye, non-xl)
Tried getting TWRP and ElementalX working but either one or both weren't doing there thing, though I could at least boot and use my phone normally. Finally ended in a situation where I couldn't boot passed fastboot with an error at the bottom "ERROR: LoadImageAndAuth Failed: Load Error". Found a fix that said to change the active partition. Set it to b and that worked and surprise it loads TWRP...so somehow TWRP was installed, but I can't actually load Android.
Grabbed the latest factory image and manually flashed all the files in the zip-within-the-zip. Everything flashed with no hiccups so I rebooted to bootloader with the intention to then reboot the system, and now this is happening:
TLDR Phone won't turn on. Holding PWR+VolDown SEEMS to do nothing, but it actually flashes a line on the screen like it's trying to load something for a milisecond, then does nothing. Holding PWR+VolUp does nothing. Holding PWR+VolUp+VolDown does the same screen flash followed by the notification LED blinking red 2 or 3 times. Please help!
EDIT: if it matters, the phone is about 50% battery and currently still on judging purely by the fact that it's been warm for about an hour.
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices? If it shows in devices, can you run platform-tools and see if it shows up via fastboot devices with an ID? If you can connect to fastboot, you could attempt to flash images that way.
djer34 said:
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices?
Click to expand...
Click to collapse
Nothing happens if I plug into the computer, no sound and not listed in devices. Plugging it in to the charger does nothing except possibly charges it, but I wouldn't know because the screen doesn't seem to be able to turn on for more than a milisecond of a flash.
I had this same problem when I flashed Elemental X kernel over top of the flash kernel and all I did was use the flash-all script that is included with the system image from google. This got me back to my OS where I flashed elemental and magisk. Do you have insurance through your provider?