Related
Afternoon all,
I debranded my desire using an RUU flashing it to 1.15.405.4 but now HTC Sync isn't recognizing the phone, it is just coming up as 'Disconnected' yet it is still being recognized as a removable disk when in disk drive mode so it can't be a USB brick.
I can't get ADB working either since the phone isn't being recognized so it isn't installing the required ADB drivers for the phone. I can't go back to my stock firmware either because USB Debugging has to be installed correctly for the RUU to run. I had no problems initially, but after upgrading to this ROM I have seemed to have this problems.
I want to root, but if I can't have access to the ADB a root would not be possible? Please correct me if I'm wrong.
If anyone has any advice I would be glad to hear it. Thanks
I have the same problem with HTC Sync - just can't get it to see the phone. Hopwever to get ADB working make sure you have USB Debugging turned on in the settings under Applications / Development / USB Debugging.
sbdags said:
I have the same problem with HTC Sync - just can't get it to see the phone. Hopwever to get ADB working make sure you have USB Debugging turned on in the settings under Applications / Development / USB Debugging.
Click to expand...
Click to collapse
Thanks for the reply.
I have USB Debugging turned on in the menu, but it seems to not be recognized. I have done all the command prompts in cmd, but it doesn't list the device under ADB devices. Hmm.. :/
I had the same problem after all my updates, that worked for me, restart your pc and restart the phone, leave it plugged in by usb, it worked every time for me, hope that will help.
I restarted my computer then phone - leaving the USB plugged in, but it's still not being recognized. Am I doing the steps the wrong way round?
It's annoying because this is stopping me from rooting at the moment and I really want to get my hands on froyo!
Thanks
I'm not to sure I'm a newbie to all this, what I did was tun the phone and pc off, turn the phone back on first then turn the pc on as soon as the pc detects the phone put the phone on sync, and so far it always worked for me after a update, maybe you have a different problem maybe a proper dev can help you out.
fredhd said:
I'm not to sure I'm a newbie to all this, what I did was tun the phone and pc off, turn the phone back on first then turn the pc on as soon as the pc detects the phone put the phone on sync, and so far it always worked for me after a update, maybe you have a different problem maybe a proper dev can help you out.
Click to expand...
Click to collapse
Tried the above a couple of times, no luck. Thanks for the help though.
Hope someone knows a fix cause I'm eager to root my phone and get onto some froyo goodness! haha
Cheers
The HTC drivers are pretty damn bad with regards to Sync. I always do adb-related work in recovery for that very reason - I can almost never get Sync working.
Can you get adb working in recovery?
Ok here is what worked for me
1- Uninstall the HTC sync and the HTC drivers
2- open MSConfig and disable all non microsoft services
3- restart windows
4- install HTC sync
5- Connect the phone and it will connect
6- re enable the disabled services and restart Windows
Does it work normally every time after that, or do you have to go through that jazz every time?
Hopefully it works every time - I'll give that a shot if so.
Hi,
The ADB isn't being found in Command prompt it outputs 'list of devices' but there is no device listed. All drivers are installed as well.
I will try the above and see if that helps.
Cheers
Hi Matey, I had this exact same problem after rooting my desire last night - basically check task manager for any adb processes and kill em, if that still doesn't work re-run the htc sync install and select repair and it'll be ok again.
I had to do this on my home laptop which I used for the root, but also on my works laptop even though this was turned off and not used for rooting at all so think it's an issue with htc sync not seeing the same phone, but at the same time seeing the same phone and getting confused.....
so - reinstall using repair and reboot and all should be well matey...
Thanks for the help guys.
I had to reinstall Windows for other reasons, and after I reinstalled HTC Sync it still wouldn't recognize the phone but ADB is working so I can do all the shell commands.
Cheers for all the help.
I take my above post back. The phone is now not being recognized by ADB, it seems to have occurred after I have turned my computer back on. Windows installed some updates and I'm wondering whether they might have had an affect.
Anyone had any experiences in the same sense?
Ok Guys heres what I,e got
Firmware ver 2.1-updat 1
Baseband ver 32.36.00.28U_4.06.00.02_2
Kernal ver 2.6.29-b7e82785
Build Num 1.19.707.7 CL171460 release keys
Software num 1.19.707.7
Browser ver Webkit3.1
Ok. now I,ve spent probably about 24 hours during the past three days trying to root the thing. made a gold card after about 10 attempts, have tried and tried to root the thing, have tried 3 or 4 different methods, most fail becase either I loose USB connection to the fone when navigating to Bootloader. From there on in she all over rover. Actually I,m not sure I have the right ROM to add to the fone, but I,d really like to get to the point where it asks for the rom. I,ve aged about 10 years since embarking on this venture, and still the thing is as bought. The phone isnt branded, bought it thru ebay from Hong Knog I think, has asian english which aint no fun. Have loaded Morelocal2 on but it still aint nice.
Can someone who has rooted one of these with similar ver software email me whith there secrets please before I go totally insane or really root the thing against a brick wall.
Cheers Guys.
Try the tutorial in my sig (second link). You should have no problems rooting with that.
It provides you with the required downloads for rooting. Just download and flash your ROM of choice in place if the 'rootedupdate.zip' file.
Please state any errors you recieve while attempting root.
-------------------------------------
Sent via the XDA Tapatalk App
Rooting Desire
I,ve tried your link, now my wife has been helping me, she cant get it to install either, I,ve even got to the stage of watching in Device manager what happens when it goes into Bootloader/recovery mode. the link between the HTC and the computer breaks,SOOOOOOO as I,ve stated before I have a very good understanding on HOW to root the thing, its just that for some reason I cant keep the phone connected thru the USB . I think this is the only prob I have. Something else that also happens is I get a Customer ID failed message half way thru step 1
What ever system I try to use to root this thig thats where I end up.
Wifie is going to try one more time, this time we are going to try the fone with a default startup to look at the disc not the HTC Syn.
Please keep trying to help guys
Rooting Desire
OK Heres the wifie update,
Screen says,
Pushing update file to device
error: device not found
error: device not found
Now wipe and apply rootupdate.zip from the recovery image menu.
Error: device not found
[email protected]:/mnt/cdrom/root$
So there we go guys, thats it in a nut shell
Try using the TinyCore method, I had all sorts of issues in Windows but this worked first time...see this post...
http://forum.xda-developers.com/showpost.php?p=6710081&postcount=2
obviously download the right Live CD for your bootloader
Also if you are trying to root in windows, make sure you have HTC Sync installed.
Desire root
Yep, I,m using the tiny core app followed the instructions in the link as advised. Still loses connection at bootlader/recovery
When you get back to Bootloader, how long do you wait before trying to run? As I normally leave it 5 or so seconds and then it's fine...if you do it too quick it'll say no device found
Which TinyCore CD did you download? I'm assuming you have HBOOT 0.80 on your device before you started?
Rooting a desire
An answer to your question, I,m using the tcl_r4_desire_hb80 file. when you ask how long are you waiting , I reckon it taks me more than 5 seconds to type in sudo ./step2.sh
I could try it again and wait longer.
Desire a rooted phone
Nope sorry guys, I,ve tried god dam everything, still wont connect afetr step 1 with tcl_r4_desire_hb80.
Somehow I need to be able to force a usb connection.
hey I tried this on Vista and XP, thought XP might be better. is there a stand alone app to force USB drivers when tcl_r4_desire_hb80 boots into termial screen
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
socktug said:
If you have done step 1, is it possible after failed attempts at getting into the recovery, you have usb bricked it?
Try switching it on normally and see if you have normal usb connectivity, and the sd card mounts and works fine?
Click to expand...
Click to collapse
I too was thinking that there is a possibility of his device being bricked, especially when receiving errors indicating that the device cannot be found in recovery.
Rooting desire
OK, wondered that myself,
connected phone to PC, sync straight away with fone
reconnected it to pc in disk drive mode and connected, checked in My Computer and the disc drive was there with all my files.
Suppose that means everything there is ok to
OK if it isn't usb bricked then it's got to be a driver issue. My suggestion would be to follow the tutorial in the dev section and use tiny core linux.
Rooting desire
OK guys,,, so heres where I,m at, so far all info gained from you lovely people has been to no avail.
What I,m getting is this
In device manager I am watching what happens when the Desire goes from fastboot to bootloader. In bootloader I get "Android 1.0 with the yellow tiangle indicating it aint set up with drivers. In fastboot I get "My HTC" under Android USB Devices. now in either Bootloader or fastboot I,m only getting one or the other, and as I said, the triangle under "Android 1.0"
Now Ive gone to Android 1.0 and tried to add a driver, seemingly thers not a driver in the world that will work with Android 1.0. All driver in my Sdk dont work. The driver installer asks for a driver but wont except anything trown at it.
First, via your phone, go to Menu > Settings > Applications > Development and ensure the USB Debugging option is selected.
Try a different USB port.
I actually think you need to create a Gold Card even though you have stock rom 1.19.707.7
Try the Gold Card.
-------------------------------------
Sent via the XDA Tapatalk App
I have the exact same issue on win.7 64bit.
Try ignoring the no android 1.0 issue, continue to put your phone into recovery with the volume down and power buttons. Wait about 10 seconds after you see the black screen with red triangle, and then click on recovery windows.bat. Works for me everytime.
Windows takes it's time to see and install devices so it may be that you are trying things too quickly after connecting the usb lead.
Here's the issue for me. My computer is not recognizing my properly, or it could be the only way around. The phone only charges, and is never picked up as a usb disk drive. I have confirmed that it's a problem with my phone itself, as my friend's EVO 4G, hooked up to my computer using the same cable, connects and is recognized as a disk drive just fine. We tried swapping out microSD cards to see if it could be something with that, and his phone was still picked up fine with my microSD in it. I think my phone may be partially rooted.
I tried SimpleRoot 1.47.651.1 on my phone at my friend's house a few days ago (4-click method), and for some reason, it never completed. His computer would pick up my phone as a disk drive perfectly fine, but on the last step (reboot and scan) it would never finish, even after letting it sit for a few hours; step 3 was saying something about not being able to identify the correct cache from the browser or something like that. I'm thinking that the partial root may've flubbed up the phone?
Right now, I'm trying to look up which root method my friend tried to work on my phone. It involved PC36IMG.zip and an update named s-u-*something*. I'm still new to the EVO, not like the Droid. Anyway, that root method failed for some reason (no errors in HBOOT, but never asked if I wanted to reboot). I've tried to factory reset, and nothing. I got my phone sitting here while I'm scratching my head trying to figure out what to do. I'm well-versed in ADB, but if my computer can't pick up my phone properly, it's all for naught. Anyone have any ideas to get me on the right foot? I can still pop out the microSD and put it into the computer directly, too. Sorry for the tl;dr candidate.
Quick update/bump.
I upgraded my phone to OTA Froyo, and now USB debugging shows up, but I don't get the "Connect to PC" menu still. Is this phone fubared?
HTC Sync not recognizing phone
I was having the same problem with 2 Evos. The phone would accept a charge from the USB port and the computer would even install the driver sometimes. Then nothing. I tried again last night after I pulled the 2.2 update and it worked! I think HTC might not have had Windows 7 Starter edition covered until this update.
Here's the thing, I'm on Windows 7 Ultimate x64. I'm having this problem on 2 EVOs, also. I've updated them both to stock 2.2 OTA, and still nothing. =/
I did just read on here somewhere that a fix was to delete the drivers for the phone and sd card and reinstall them.
I've done some searches, here and on google, and I couldn't find anyone with the exact problem as mine, and non of the solutions I tried worked. Thanks ahead of time for reading.
Yesterday, I was running Sirius ROM on my SGH-T898 Galaxy SII, and for the first time running this ROM, my battery level reach below 15%, and a pop up message suggested I plug the phone in to charge. When I did this, I noticed for the first time that my desktop at work is not recognizing the device and saying that it malfunctioned. I didn't think much of it. Later in the day, I decided to restore my stock backup and update to ICS via Kies. Darkstar Superwipe ----> Restore backup. Once I plugged the phone into my laptop at home, I noticed again that windows in not recognizing my phone, and saying that it malfunctioned. I attempted re-installing the drivers via Kies multiple times with no success. I've tried 3-4 cables and 3 computers, still no success. I've used an electronic duster and lint remover, thinking perhaps some lint or something is preventing a connection - no luck. I've tried dialing *#7284#, and changing those settings - no luck. I've trying the usb debugging checkbox in applications/development - no luck. Now I am back to the ROM Malice (which i had before the ICS Sirius), still, with no luck of connecting to a computer. The phone charges, and works perfectly fine. I can access the files on the SD through the phone with no issues (i.e play music). The last time I could successfully connect to a computer was this past Saturday morning, and those files successfully transferred to my knowledge (I can listen to that particular album).
Guys, what could possibly be my issue!?
Thanks for your time!
Anyone?
Edit: I had switched to a different (charge-only) cable halfway through and not realized it. Switched back and the phone was recognized again.
Steps:
I unlocked my bootloader with Wug's toolkit.
I installed the zips that it asked me to (that it put on my SD card).
I updated SuperSU
I got a notice to update the SuperSU binary.
SuperSU binary won't install via Play.
Tried to install via TWRP and recovery isn't twrp, seems to be stock recovery (thought I installed it, maybe not)
Now the toolkit won't recognize my device. neither will windows. It gives me the USB noise but won't show the device in the folder list and defaults to USB for Charging. I can change it but it doesn't make it recognizable.
I'm trying ot back out and try again but the toolkit says it finds the device but that it's listed as "offline". When I toggle the USB debugging, it doesn't ask me to fingerprint my computer.
When I try the "soft brick" option to flash from the bootloader, the script reports a failure "data transfer failure (unknown error)", then says "rebooting into bootloader..." and does nothing else BUT my phone's bootloader still says "downloading..." When I reboot, the script throws another failure and says "waiting for device". when I bootload into it again and connect, the script throws more failures.
I've been on this for 4 hours, getting pretty fatigued (through the night on a weekend when family is visiting. yes, I'm an idiot for trying this procedure but the 5 went so smoothly I was optimistic).
try reinstalling the drivers. also the OEM-lock option in the dev-settings may help bringing you back to step one.
I was halfway through installing the drivers when I quit for sleep last night.
I'm using the LG-Mobile-Driver_v3.14.1.exe package, and the installer says it installed successfully, but windows says that MTP and PCI Simple Communications Controller had "No driver found", so the device doesn't show up in my drive list and wugfresh won't detect it.
I've removed all Google, LG, MTP, and Nexus drivers in USBDeview, but can't seem to figure this out.
I was able to get the drivers installed on my wife's system, so I'll open another thread about this if I can't get them to work.
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
oubravs2b said:
Try using @Heisenberg root instructions if you get back to stock. I've tried multiple times to use the toolkit to no avail. I've had to resort to Heisenberg's root method every time and it just works.
You may wonder why I've rooted multiple times...I was testing with Android Pay and wanted to start clean. Although I was able to use the toolkit to get back to stock easily.
Click to expand...
Click to collapse
so, the reason my computer stopped recognizing the phone was that I switched to a charge-only cable without realizing it. Switched back and the phone recognized fine.
The weird thing is, the charge-only cable worked fine for data xfer on my wife's system.