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.
Hi Guys,
I have the TF101 tablet and anytime I try to reboot it just stays at the first boot screen with the "Eee...." screen. Forever. If I hold down power and vol-down then hit vol up, it just stays there saying its booting recovery image but never changes. If I hold down volume long enough it comes to the factory reset/cold boot screen, if I choose cold boot it will boot.
I have rooted the tablet and had no problems previously, was able to flash roms and whatever else I wanted to do. Also, when I plug the tablet into my Windows XP machine, it does not detect the tablet in any way.
Tablet info:
Android Version: 4.0.3
with 2.6.39.4 kernel
I don't remember what rom its running exactly but I know its a version of ICS
Did you use ROM manager to update your CWM version? This sounds exactly like that, you can try running the bootloop-fix in my PERI tool (link in my signature) to fix, or manually run roach2010's fix found in his latest recovery thread. You definitely need ADB working, otherwise you'll need to Nvflash. (Nvflash Wheelie link is in my signature as well)
You are probably right i very well could have done so in rom manager. Im on vacation and dont have access to a pc right now but am going to try ur tool when i get back. Thx for the info
Sent from my Transformer TF101 using xda premium
Wait. I just realized. My pc doesnt even respond when i plug my tab in. How do i run PERI?
Sent from my Transformer TF101 using xda premium
Cold boot and install the drivers.
Ok Thing o Doom, you've been great pointing me in the correct direction, however I need some more guidance.
I have installed ADB, and when I cold boot the device and run adb devices I get nothing.
HOWEVER, if I just reboot the tablet, when it's stuck on the EEE screen, I do adb devices and it shows 123456789ABCDEFG.....
My computer doesn't see the tablet when it's plugged in otherwise, nor does any other windows PC in the house. Do you have any guidance as to what I can do? Please help, I need to get this thing running right.
You just need to get to a state where adb is recognized, and 'adb shell' command works.
From that point PERI should work.
Reboot when it prompts you to if it doesn't automatically (Probably won't being stuck on logo)
I can't seem to get anywhere else. My pc recognizes the tablet at the first boot screen but adb shows it as inactive. When I cold-boot the tablet it boots and loads fine but ADB nor any PC recognizes that it's plugged in. I'm lost.
Is "Enable USB Debugging" Checked in Developer Options?
I accidently used a root-kit for ICS while having JB (Bootloader unlocked before) from:
http://theandroidrom.com/how-to-root-motorola-razr-i/
Now my device is constantly rebooting...
I can enter fastboot and already tried all options (recovery, wiping etc.), none of them working.
Then I tried to apply the firmware again from:
http://forum.xda-developers.com/showthread.php?t=1936512&nocache=1
Choosing "91.2.26001.Retail.en.EU - 4.1.2"
It stops the first time I have to push a key after being asked about installed drivers etc...
I have all drivers installled and the phone connected (do i have to shut it off or stay in fastboot? I tried while staying in fastboot so far) with my pc. But how do I enable USB Debugging from fastboot?? I did so when my phone was still working, but I cant say if its still like that.
Another possible problem: Battery is on 15% but being connected with PC gives power, doesnt it? I will let it charge up, now...Maybe you can give me some tips what else I could do?
bumping
Hi guys I recently tried to boot Linux rom as a recovery alternative, it worked fine
but I lost my stock recovery , later I flashed CM 10.2 with clockwork mod , also worked fine, I flashed with odin with erase all stuff
now everytime I boot the device it shows strange white screen with lines, and its no longer be able to connect via USB , I tired many PCs and its not the Samsung drivers thing I installed it many times
so I flashed stockrom from Samsung site but still cant lose that white screen when I boot , and still cant connect via USB
any help ?
No USB to PC and corrupt Boot and shut down screen. GT-N8000
Did you find a solution for your tablet?
If so let me know.
I have the exact same issues. Also tried CM10.2 and latter moved back to stock ROM via ODIN with the standard normal selections.
Now I have the same issue you describe.
No USB connection to PC
Strange white screen with lines on boot or shutdown. Sometimes a corrupted image of the download screen.
Else the tablet is fine. EFS and all related OKAY.
For the USB issue I found a TEMP solution.
Go to the phone dialer, type *#7284#. a PhoneUtil menu comes up.
Select "PDA" on both UART and USB. Your PC will immediately connect.
On the tablet you will also now have the USB options.
But, your tablet will still have the PhoneUtil menu OPEN.
Below the options you have a "save and reset" button. Push it.
also, i have seen prints of PhoneUtil thats contains an extra button called QUALcom.
My tablet DOES not. GT-N8000. Read other guides if you have this button.
Your tablet will reboot and you still have the USB connection to PC.
However this works only if you do not reboot your tablet. If you reboot USB is gone again.
Then again you need to do the *#7284#
At least this is the scenario on mine. I have USB connection.
I have tried several different stock ROM's via ODIN from all over the world and always the same issue.
USB issue and strange boot screen image before Samsung circle.
Tried with PIT files and even selections in ODIN that are not suppose to be used.
Tried KIES as well, but here it fails stating GT-N8000 does not support initialization. KIES 3 told me to get lost.
also tried 4.0.4 ROMs via odin, installed fine, and allowed KIES to update to 4.1.2, but issue remains.
Other strange activities are also taking place after ODIN uploads.
Tablet always goes int boot loop. No matter which stock ROM.
Need to go into standard recovery and perform factory reset.
But
Need to perform button boot into recovery option twice. always fails the 1st time after ODIN load.
Strange corrupt screen always present on performing these actions.
Cannot use CM10.2 as the USB issue remains permanent as the *#7284# does not work on that dialer.
Any help would be appreciated to return tablet back to REAL normal.
Well I did a factory reset on my H60-L04 through the Emui stock recovery with a stock room (rooted). I went through the setup wizard successfully. After I finished the wizard the phone said the setup wizard was forcefully closed. After I press ok on that message the phone constantly puts out a message saying that com.android.phone has been forcefully closed. I can't do anything with the phone anymore.
EDIT// Wtf is this ****? I tried to turn off the phone by holding the power key 10 secs now it constantly reboots and I can't do anything about it.
EDIT2// If I unlock the lockscreen I simply get a black screen with the message that com.android.phone has stopped. Maybe there are some files missing??
It's the stock 2.3 emui for the H60-L04. For some reason I also can't boot into fastboot anymore (Power button+Volume down key). Instead the honor just boots normally and shows me the error again. as thus I can't activate USB debugging as there is no UI at all. Means I can't use adb.
`
Volume Up leads me to the emui recovery. I got fastboot now by Volume down and power key. Maybe that was my fault before. Should I now flash over the russian stock rom? Or is there any other (faster) way to fix this (Assuming flashing a new rom will fix this)?
EDIT// I am in fastboot but my computer doesn't detect the phone. I guess USB debugging is deactivated. And I can't activate it because no UI. what now?
EDIT2// The Device Manager of Windows shows "Android Phone\USB Modem Phone ADB Port" so the device is definitely recognized. The problem is that ADB doesn't work (probably because of no USB debugging)
Also if you try hard enough you might be able to enable USB debug by constantly skipping the crash message
Click to expand...
Click to collapse
You mean by constantly pressing OK on the message or what? The problem is I guess that the launcher is missing somehow. I have no status bar, no softkeys etc.
pudup said:
Not sure why fastboot doesn't recognize your phone. You typed "fastboot devices" yeah?
Click to expand...
Click to collapse
Yes. As said I guess the factory reset also resetted the USB debugging. As thus USB debugging is now disabled and I cannot activate it without a interface.
Though so I rebooted the device multiple times now and for some reason the message is now gone (still no status bar nor softkeys). I guess the message is gone now because the first screen is the USB screen. I will now put the russian stock rom and flash it. Hopefully it will work.
pudup said:
Alright. Always make backups in the future.
Click to expand...
Click to collapse
I do have a nandroid backup of the clean Emui2.3 but what should I do? I can't access adb and have stock recovery. As thus there is no way to restore it.
pudup said:
I don't see why adb or fastboot should have stopped working. It worked before right?
Click to expand...
Click to collapse
Yes it did. As said I guess the factory reset also disabled the USB debugging (as obviously the developer options (including USB debugging) are normally disabled). Ok but now it works agian. Now i have the status bar and navbar back. Thanks man the answer that I really never thought of (constantly clicking away the ****ing message) really did work. And thanks to the russian stock rom.
Try this:
reboot to Recovery, goto "Mounts & Storage" and select "Format cache" followed by "Format /data and /data/media". Then reboot!
It helped on my device, while testing other roms,...