I have a htc sensation 4g with hboot 1.27.1100 I've unlocked the bootloader flashed recovery, and rooted the phone.
I'm trying to gain s-off by running controlbear, and using the paper clip trick, but after controlbear reboots the phone it gives me this message : Connect device and install drivers.
I'm assuming it's referring to the device drivers for the phone which are already installed. If it's referring to some other driver I don't know what one it's talking about.
I noticed while using adb it also would not recognize the device, though I was still able to use it to communicate with the phone. Was thinking that might have something to do with it.
Any help would be appreciated.
HTC's 4.0 update really screwed my phone up...Just bumping, don't know what proper etiquette is on this forum for bumps, if it was to early i'm sure i'll hear about it, and will reserve myself for future post.
make sure you have usb debugging on i had the same issue and i didnt have it on so give that a try good luck
contractedkill said:
make sure you have usb debugging on i had the same issue and i didnt have it on so give that a try good luck
Click to expand...
Click to collapse
i have a problem. i have a htc evo 3d cdma rooted unlocked and my computer is windows 7 with the htc driver.... i want to be s off i finally got controlbear to work untill i get to the arrow screen then it says resetting connecting 1 2 open device manager and check adb and fastboot drivers. so i opened device manager and looked and windows sees it as a portable device and i tried to install the htc driver but i dont know where it is on the computer and it doesnt show up when i pick from a list of drivers. please help i cant find a solution
I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it
Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.
Ok, Ill give a try.
I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?
I found the best way to get the driver installed is to install HTC sync
Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?
Is there battery actually low? Just shut down the phone and charge it up.
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
fnstGoliath said:
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
Click to expand...
Click to collapse
Hi,
Go HERE
Install 4 EXT recovery,using one of the 3 methods available.(probably third)
Then,try to install ARHD ROM.(same guide)
No need to change the firmware.
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
fnstGoliath said:
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
Click to expand...
Click to collapse
Hi,
Maybe you should run a RUU.
Look HERE
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
fnstGoliath said:
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
Click to expand...
Click to collapse
Hi,
Try installing these windows 7 & 8 drivers (assuming you have a windows 7 or 8 machine)
Reboot your PC and see if your phone is recognized in ADB.
You are s-off,so you do not have to match it 100%
Just get a RUU that is close to your region or carrier.
If you get the wrong one,it is not a problem.
It will just give you an error.
Then,just try another.
)
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
fnstGoliath said:
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
Click to expand...
Click to collapse
Hi,
Not sure what is happening with your ADB.
Look HERE for help.
In order to run a RUU ,you need to put the bootloader into fastboot,and plug in the USB.
It should show what yours is showing.
So, it should work.
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
fnstGoliath said:
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
Click to expand...
Click to collapse
Hi,
Just run the RUU.
It will only show error if it does not work.
No big deal,and no damage done.
Just try another one.
if you enable usb debugging might help too
Well.. I just started "RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed" and everything went fine until installation, no errors at all. Now the installer is stuck at "restarting bootloader" (or something equal, the installation is german) and the phone didnt do anything at all. It's now 15 minutes since the installation started so I probably will try another one but isn't it weird that ther is no error at all?
What should I do if the next RUU does exactly the same?
*edit:
just seeing page 2. How should I enable usb debugging without booting the phone?
*edit2:
second RUU: Same thing, no error but it didnt go further then "Restarting bootloader".
What to do now?
Any further Ideas what I could try?
Puuuush
fnstGoliath said:
Any further Ideas what I could try?
Puuuush
Click to expand...
Click to collapse
Put phone into bootloader then connect to pc and run the RUU
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
The phone was in fastboot usb while running the ruu for sure ..
fnstGoliath said:
The phone was in fastboot usb while running the ruu for sure ..
Click to expand...
Click to collapse
Hi,
Try running a RUU with the same radio (11.22) that you have installed.
You will not damage the phone.
It is not always an exact science with RUU.
Sometimes it is just trial and error.
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
fnstGoliath said:
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
Click to expand...
Click to collapse
Hi,
Probably ,the only thing that will fix your problem is a RUU.
So,keep trying different ones until it works.
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
fnstGoliath said:
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
Click to expand...
Click to collapse
Hi,
Plug your phone into the PC.
Go to device manager,and where it says MyHTC,right click and update driver.
Browse to the windows 7 & 8 drivers I gave you earlier.
Update,unplug phone ,and reboot PC.
Get a RUU that shows 3.32 or 3.33 in the title,and matches your region
Pull your battery.
Put it back in,and hold volume down and power button together.
Scroll to fastboot.
Plug in usb and run RUU from the PC
Ok. I need some help. Have an at&t htc inspire, bootloader screen and when i plug it in my computer to run an ruu exe file, my windows 8 computer will not recognize the device? I have tried installing the newest drivers, other usb ports, etc. Please Help, thank you
ok, got past that. NOw whenever my phone is plugged in and i reboot to the bootloader, it comes up with an error message saying the usb device is not recognized and i can't do anything? Now what?
dmartin1972 said:
ok, got past that. NOw whenever my phone is plugged in and i reboot to the bootloader, it comes up with an error message saying the usb device is not recognized and i can't do anything? Now what?
Click to expand...
Click to collapse
If you're connecting from bootloader, use fastboot not ADB.
When I have the phone on and connect the usb it recognizes it. But when I run the ruu update,and the phone boots into the bootloader, it says usb device us not recognized. I have HTC sync installed on my computer. Windows 8 64 bit.
What I really need us a pd98img.zip file for an at&t HTC inspire 4g with 2.3.5 gingerbread. Anyone have that?
dmartin1972 said:
What I really need us a pd98img.zip file for an at&t HTC inspire 4g with 2.3.5 gingerbread. Anyone have that?
Click to expand...
Click to collapse
You can get the stock images from htcdev dot com.
You will need to create an account but it's free. Also, is your bootloader locked or unlocked?
If it is unlocked, you will need to relock it before flashing a signed stock rom.
I got it back to stock AT&T 2.3.5 by pulling the img file out of the downloaded ruu. I still cant get the phone to be recognized by my computer in the bootloader screen though? So I can't get it rooted or unlocked on the htc developer site. What am I doing wrong??? Also what should I use to root it. I have tried easy ace root tool. and will not work
dmartin1972 said:
I got it back to stock AT&T 2.3.5 by pulling the img file out of the downloaded ruu. I still cant get the phone to be recognized by my computer in the bootloader screen though? So I can't get it rooted or unlocked on the htc developer site. What am I doing wrong??? Also what should I use to root it. I have tried easy ace root tool. and will not work
Click to expand...
Click to collapse
Are you using fastboot or ADB? What is the error message from the Easy Ace Root Tool?
Ok. I don't know what I did but i got it to work. Now, what is the newest root tool that works? Also do I need s-off for roms? Not sure how to proceed??
dmartin1972 said:
Ok. I don't know what I did but i got it to work. Now, what is the newest root tool that works? Also do I need s-off for roms? Not sure how to proceed??
Click to expand...
Click to collapse
Here is the link to what you need http://forum.xda-developers.com/showthread.php?t=2169518
Does that ace root tool still supposedly work? I've been at this for weeks, hours of searching forums under my belt and nada.
caseymac91 said:
Does that ace root tool still supposedly work? I've been at this for weeks, hours of searching forums under my belt and nada.
Click to expand...
Click to collapse
I had this same exact issue. I have a Lonovo Yoga with 3.0 USB ports and Windows 8.1 and no matter what I did I couldn't get my phone to work on my computer. I ended up having to switch computers just to have my phone recognized. I switched to a Windows 7 computer with 2.0USB ports and my phone was recognized in Bootload Mode. After I installed CWM I was able to have my phone recognized on my Yoga after going into CWM recovery and mounting my SD card.
Hope this helped!:good:
My post that died.. please read also
http://forum.xda-developers.com/showthread.php?p=48646053#post48646053
Hello guys, long story short.. a little while ago I tried upgrading my ROM to 4.4.4 and found out that i have to turn S-off and install the RUU 3.18 i think it was. Upon doing this I came to find out that my phone isn't being listed when I type adb devices. I have debugging mode on and install the latest HTC drivers and uninstalled HTC sync, but yet it wont list my device.
I did some research and found out it could be the current rom I have installed causing it not being listed and that I may have to use another ROM to get windows to see my phone. But I dont think I can flash another rom because I cant get into TWRP now. I can get in bootloader but now recovery doesnt work and i cant get into TWRP anymore,I think I also have to update Hboot too.
My question is how do I go about getting my phone listed in adb and how can install twrp again.. Its been soo long since I did this I may need some help. If i can get ADB to list my phone I should be able to do the upgrading myself.
I'm taking a break atm as this is giving me a huge headache. I know Its not hard to flash if you have ADB working. Or TWRP but I dont have either of them. Can anyone shed some light for me please..
This is whats on my bootloader page
EVITA PVT SHIP S-ON RL
HBOOT- 1.09.0000
RADIO- 0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
rootbox jb evita if that matters
Thx for reading.
Any help would be greatly appreciated.
So to make sure I understand your situation:
1. You CAN boot into your rom
2. You CANNOT boot into your Recovery (I'm assuming bootloop)
3. You CANNOT see your device in adb OR fastboot (please confirm)
So here's the best case scenario. You are NOT running Windows 8.1 and you can see your device in fastboot while in the bootloader. In this case, S-OFF again and flash recovery as usual. If your ARE running Win 8.1 .... well we'll cross that bridge when we get to it.
To debug your adb problem plug your phone into your computer. Does your phone respond in any way? Do you see the device show up on your computer for file transfer? If any of these things is true, rejoice! For there is hope! This is just for assurance, but you do have developer settings turned on and adb enabled right? Have you tried other usb ports? I forget if there is authentication in 4.2.2 but if there is, did you add you trust your computer? Try revoking all trusted computers and try again. Have you tried the newest version of ADB? Have you tried a different cord? If you have tried ALL of these, open up device manager. This can be done by simply typing into the search in start on both Win7/8. Now look at the top of the list. Do you see anything like ADB Interface or Android Device? If not, do you see any unrecognized devices or any device with an exclamation mark under Other Devices or Universal Serial Bus Controller? If any of these is true, right click the device and select properties. It'll be best to post a screen shot at this point. But if you're an intrepid risk seeker, go to the driver tab and hit uninstall. Next unplug your device, wait a few moments and plug it back in. You should see a driver installation progress. I've also attached the generic Google drivers that I know for sure works should you need it. Now try adb again and hopefully your device shows up:highfive:
If all is wrong with the world, and you do not see anything when you connect your phone, try on different computer with a different cord.