Guest Raivis R. Posted May 21, 2010 Report Posted May 21, 2010 my USB connectivity problems started even before I got to rooting the device and guess what, HTC have included extremely crappy USB cable. Switched that cable for one that came with wife's nokia and voila, everithing works just perfect.
Guest yabolek Posted May 21, 2010 Report Posted May 21, 2010 (edited) tried 5 cables - not the issue I suspect that actually a crappy cable/connection might have been the cause of all this. Given that we cannot find a common software scenario (except being in recovery) before the brick it would be a good explanation. Edited May 21, 2010 by yabolek
Guest NisseGurra Posted May 21, 2010 Report Posted May 21, 2010 I suspect that actually a crappy cable/connection might have been the cause of all this. Given that we cannot find a common software scenario (except being in recovery) before the brick it would be a good explanation. I agree, the recovery is run "online" from computer and this makes it very sensitive for connection errors. So make sure not to move your phone during flashing.
Guest Richard Trip Posted May 21, 2010 Report Posted May 21, 2010 I agree, the recovery is run "online" from computer and this makes it very sensitive for connection errors. So make sure not to move your phone during flashing. There is also no sdcard availability from hboot? If there is you could rename an origin rom.zip (from RUU) to PB99IMG.zip and put it in the root of your sdcard. After that start the phone with vol-down + power.
Guest r&a Posted May 21, 2010 Report Posted May 21, 2010 There is also no sdcard availability from hboot? If there is you could rename an origin rom.zip (from RUU) to PB99IMG.zip and put it in the root of your sdcard. After that start the phone with vol-down + power. it will only take signed rom
Guest jeckyllhavok Posted May 21, 2010 Report Posted May 21, 2010 it will only take signed rom are we able to sign with test keys?
Guest geek78 Posted May 21, 2010 Report Posted May 21, 2010 are we able to sign with test keys? sign yes but with test keys and we need HTC keys so no for this use ..
Guest andy76q Posted May 21, 2010 Report Posted May 21, 2010 i returned my desire today for this issue, so now i hope i will get some good news in a few days.
Guest Richard Trip Posted May 21, 2010 Report Posted May 21, 2010 it will only take signed rom Yes, but the RUU's are signed. Maybe this way you could revert to a stock RUU and have your usb/sdcard working again? And start the rooting process again.
Guest Snarkasm Posted May 21, 2010 Report Posted May 21, 2010 You can revert back to stock, but it doesn't restore the USB function. That's the correct way to put your Desire back before you send it back to HTC, though - that way there aren't traces of root.
Guest IEFtm Posted May 21, 2010 Report Posted May 21, 2010 I see some people saying that recovery is running from the 'pc', obviously, it does get written to RAM. However, I did notice that when USB is not connected properly during recovery, it might end the /sbin/recovery program running from ADB. It might be a better idea to start recovery by doing 'nohup /sbin/recovery &' That way it won't get killed when USB is disconnected (you can even take out the usb cable when recovery is booted properly).
Guest mardox Posted May 21, 2010 Report Posted May 21, 2010 if the usb connection loosing connection is the triggering factor (even though it may not be the underlying factor) it would probbly help to get a better cable, am i right? if so what cables have the best fitt and dont loose connection?
Guest IEFtm Posted May 21, 2010 Report Posted May 21, 2010 not really. You don't need the usb connection anymore after all the recovery files are written, and the recovery binary is running/daemonized. It would seem to me the usb connector for the Desire isn't all that great. Also, I have 4 other microusb cables , they all exhibit the same problem, you just shouldn't move the usb connection too much or it will loose connection for a second. Which in the case of recovery / flashing is extremely detrimental, as you could see.
Guest mardox Posted May 21, 2010 Report Posted May 21, 2010 sure you dont need usb cable after files are written? because recovery stops workng when usb is unplugged
Guest NisseGurra Posted May 21, 2010 Report Posted May 21, 2010 I see some people saying that recovery is running from the 'pc', obviously, it does get written to RAM. However, I did notice that when USB is not connected properly during recovery, it might end the /sbin/recovery program running from ADB. It might be a better idea to start recovery by doing 'nohup /sbin/recovery &' That way it won't get killed when USB is disconnected (you can even take out the usb cable when recovery is booted properly). Easy to see that the recovery runs from com: disconnect usb during recovery session and it stops directly
Guest PeBo75 Posted May 21, 2010 Report Posted May 21, 2010 Easy to see that the recovery runs from com: disconnect usb during recovery session and it stops directly Maybe because the parent process is terminated then? It is the terminal session initiated by "adb shell", isn't it?
Guest Aphax Posted May 21, 2010 Report Posted May 21, 2010 Well, I just logged in through adb shell on my (not bricked) desire, and did some extreme fiddling with the usb cable/connector, and nothing really seemed to happen, i had log cat running and a dmesg afterwards showed no usb related messages either, but I guess that doesn't really say anything about other desires.
Guest IEFtm Posted May 21, 2010 Report Posted May 21, 2010 (edited) sure you dont need usb cable after files are written? because recovery stops workng when usb is unplugged If you run recovery with 'nohup', then no, you don't need the USB cable. Easy to see that the recovery runs from com: disconnect usb during recovery session and it stops directly It doesn't run FROM the adb connection. But ADB is the tty/shell over which it was launched, so without nohup it will terminate on disconnect. Maybe because the parent process is terminated then? It is the terminal session initiated by "adb shell", isn't it? Exactly. All the more reason to run it by doing 'nohup' in front of it. At least then it will stay active. Tested it a few times myself, works brilliantly. Edited May 21, 2010 by IEFtm
Guest xhemp Posted May 21, 2010 Report Posted May 21, 2010 Hi guys, Just as an update: I've called HTC and I've been informed that my phone is repaired but she couldn't tell me what has been done (maybe a motherboard swap?). Phone is currently in testing and will be shipped to me soon. Let's see. Cheers.
Guest pina Posted May 21, 2010 Report Posted May 21, 2010 Hi guys, Just as an update: I've called HTC and I've been informed that my phone is repaired but she couldn't tell me what has been done (maybe a motherboard swap?). Phone is currently in testing and will be shipped to me soon. Let's see. Cheers. huh? That's really fast! I went to the shop yesterday and they told me that it would take AT LEAST 3 weeks if they have to send it back to HTC to repair it...
Guest cbgb Posted May 21, 2010 Report Posted May 21, 2010 (edited) I'm just wondering if fastboot oem enableqxdm 0 is the same option that you can find in the service menu (#*#*4636*#*#) ==> Phone Info ==> enable QXDM-SD Protocol I have a german phone, so this is just my bad translation, in german it says: Telefoninformation => "QXDM-SD-Protokoll aktivieren" Edited May 21, 2010 by cbgb
Guest pina Posted May 21, 2010 Report Posted May 21, 2010 I'm just wondering if fastboot oem enableqxdm 0 is the same option that you can find in the service menu (#*#*4636*#*#) ==> Phone Info ==> enable QXDM-SD Protocol I have a german phone, so this is just my bad translation, in german it says: Telefoninformation => "QXDM-SD-Protokoll aktivieren" hmm that's strange, I can't even run the code...i could before, but now not... maybe because of bootlaoder 0.8 or the bricked phone?
Guest MIYU-G Posted May 21, 2010 Report Posted May 21, 2010 My desire is parallel import,there is no HTC support in China,this means I have to wait when the builtin recovery or the open spl is annouce?that's too sad to wait for it :rolleyes:
Guest nilezon Posted May 21, 2010 Report Posted May 21, 2010 hmm that's strange, I can't even run the code...i could before, but now not... maybe because of bootlaoder 0.8 or the bricked phone? It's: *#*#4636#*#*
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now