Issues with USB connectivity etc. and root / A2SD

[Guest Snarkasm]

I always wipe, every single time, before flashing a whole ROM. I remain unbricked. Maybe some others can corroborate.

[Guest mardox]

i am getting so sick of this especially because i have no way of unrooting my phone :S if someone could help me get my phone unrooted to generic rom i would be so gratefull! the thing that happens when i try to unroot with generic ruu ( before you ask i use the one for correct bootloader version, i run .75) is that when searching for my rom image it says FAILED too many links ( or something like that) and then the phone just freezes and i need to take out battery. i have tried almost all the usb ports on my pc and it just wont work. i boot into fastboot and connect usb then run the ruu.

anyone have a fix for the problem? btw my phone is nordic version which is unlocked so i did not use goldcard.

is it possible to extract rom out of generic ruu so i could put it on sd and flash it through the stock recovory image?( http://android.modaco.com/content/htc-desi.../recovery-menu/ ) as it is probably htc signed?

Edited May 23, 2010 by mardox

[Guest r&a]

I'd contribute a good few quid to the cause.

it's up to paul - if he needs bricked unit

as soon as he says so i'll put some money in

[Guest ZiCoN]

it's up to paul - if he needs bricked unit

as soon as he says so i'll put some money in

I actially had the thought of sending him mine, if I could get my hands on a working phone until I would get it back... That's if I was guaranteed of getting it back in working condition :rolleyes: .... and of course if he would need it :D

I would rather be without it knowing Paul could do some greater good, than sending it to my provider, who would send it to who ever repairs HTC devices here in denmark.

[Guest NOFX]

i am getting so sick of this especially because i have no way of unrooting my phone :S if someone could help me get my phone unrooted to generic rom i would be so gratefull! the thing that happens when i try to unroot with generic ruu ( before you ask i use the one for correct bootloader version, i run .75) is that when searching for my rom image it says FAILED too many links ( or something like that) and then the phone just freezes and i need to take out battery. i have tried almost all the usb ports on my pc and it just wont work. i boot into fastboot and connect usb then run the ruu.

anyone have a fix for the problem? btw my phone is nordic version which is unlocked so i did not use goldcard.

is it possible to extract rom out of generic ruu so i could put it on sd and flash it through the stock recovory image?( http://android.modaco.com/content/htc-desi.../recovery-menu/ ) as it is probably htc signed?

You're a lucky bastard - because I hade the same issue - and FINALLY solved it!!!

What you need to do is run the Generic RUU from the 'Unroot' thread' here on MoDaCo. I underline this - don't run the generic ROM - run the unroot one. It won't work at first - I had to boot it into fastboot, and tried it maybe 5 times - with no luck. But then - suddenly - it went past the first step, and stopped. After 3 or 4 more flashes, it finally went through. Try different USB-ports, and keep running the Unroot RUU - NOT the generic one.

Eventually I think you will succeed. About the 2nd time I didn't have the multiple images thing anymore - instead it wrote image version: cccccccccc or something like that. After that, I needed those 3-4 more flashes before it worked.

Good luck - I sent mine in after unrooting. And I'm still waiting for a reply on it. BTW: My phone is Danish!

[Guest afiorillo]

[...] Are you guys certain about this 3x bootloop=debugmode theory? I've had a lot of bootloops after flashing specific roms (i'm 99% certain that it's been more than 3 consecutive, at times), but still no brick here.. Still 1% uncertain though! :rolleyes:

The first bootloop I suffered (installing A2SD w/ Dalvik-cache, first version) I left my Desire rebooting for an hour or so. After that, I learned my way and I began pulling the battery out.

[Guest afiorillo]

It would be interesting to know how many of the people with bricked phones did a full wipe before they flashed? [...]

I like to do things the clean way, I don't mind reinstalling 130+ apps: i ALWAYS wipe anything is wipeable, and not only flashing a Desire (I do the same with my computers, and in many thing in real life). Never bricked.

[Guest djk314]

Sometimes Recovery script don't work on my Desire, i need to click a lot of time on the recovery.bat and the desire show-up and script copy files thrue the usb, it could take 4 or 5 times to use the usb, but i done that a lot of times, flashed more that 50 times, wiped, Sd reformat for A2sd etc... I use win764 and adb-nilezon and always wipe when i try something (nandroid backup before too)

adb-nilezon push files /

adb-nilezon shell busybox --install /sbin

adb-nilezon shell nohup recovery &

Sometimes Recovery menu lock or disapear too and i need to relaunch the script.

Edited May 23, 2010 by djk314

[Guest RiotRick]

The first bootloop I suffered (installing A2SD w/ Dalvik-cache, first version) I left my Desire rebooting for an hour or so. After that, I learned my way and I began pulling the battery out.

I've had a couple of bootloops as well. I've left some of then running for 10+ minutes so definately more than 3 cycles. The device still works perfectly fine. I've flashed about 10-15 different roms on it.

[Guest sruon]

Sometimes Recovery script don't work on my Desire, i need to click a lot of time on the recovery.bat and the desire show-up and script copy files thrue the usb, it could take 4 or 5 times to use the usb, but i done that a lot of times, flashed more that 50 times, wiped, Sd reformat for A2sd etc... I use win764 and adb-nilezon and always wipe when i try something (nandroid backup before too)

adb-nilezon push files /

adb-nilezon shell busybox --install /sbin

adb-nilezon shell nohup recovery &

Sometimes Recovery menu lock or disapear too and i need to relaunch the script.

That's most likely because adb.exe is still loaded on your computer, a quick CTRL+ALT+DEL to close all adb processes fixes this for me.

[Guest jamlam]

I've had a couple of bootloops as well. I've left some of then running for 10+ minutes so definately more than 3 cycles. The device still works perfectly fine. I've flashed about 10-15 different roms on it.

Did you always do a wipe before you flashed the roms?

[Guest djk314]

That's most likely because adb.exe is still loaded on your computer, a quick CTRL+ALT+DEL to close all adb processes fixes this for me.

Yes you are right about this, but it look like bricked ;p , forget to mention my hboot is 0.75

[Guest r&a]

plz vote if u havnt done so yet

http://android.modaco.com/content/htc-desi...ts-get-a-count/

even if u exchanged under warranty

Edited May 24, 2010 by r&a

[Guest MIYU-G]

Yesterday I sent a support mail to HTC,told them my phone' issues.Today they reply me says:here is no support center in mainland,China now,from my SN,I have to sent it to Holland,if I could pay all the postage & fix cost.And have to get it back with myself,this means I must buy a airplane ticket from China to Holland,my god,I have no way with my desire now.

Today I also went to some personal fix center for HTC in Shanghai for good luck,but falied,noone could fix it,because they even don't know these issues,and no mainboard of Desire to change for my bad one.

[Guest ZiCoN]

Yesterday I sent a support mail to HTC,told them my phone' issues.Today they reply me says:here is no support center in mainland,China now,from my SN,I have to sent it to Holland,if I could pay all the postage & fix cost.And have to get it back with myself,this means I must buy a airplane ticket from China to Holland,my god,I have no way with my desire now.

Today I also went to some personal fix center for HTC in Shanghai for good luck,but falied,noone could fix it,because they even don't know these issues,and no mainboard of Desire to change for my bad one.

That really sucks :rolleyes: But I still believe it's NOT a hardware issue. It will for sure only be a matter of time till a fix is available... But trust me.. I know how frustrating it is...

[Guest MIYU-G]

That really sucks :rolleyes: But I still believe it's NOT a hardware issue. It will for sure only be a matter of time till a fix is available... But trust me.. I know how frustrating it is...

thank you for understand.I still wait for a hope

[Guest MIYU-G]

I decide to flash Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed,b

t failed,RUU can't find my phone.any one have try it before ?

Edited May 24, 2010 by MIYU-G

[Guest r&a]

u must be in fastboot

[Guest MIYU-G]

u must be in fastboot

I have in fastboot,but it can't find my phone

[Guest MIYU-G]

u must be in fastboot

I can flash version 1.15.405.4,but can't flash version 1.21.405.2

[Guest anishnair]

I too bricked after taking extreme care with all the advice from every related posts; stable connection with pone placed on desk, run recovery with nohup option (recovery.bat modified with adb-windows.exe shell nohup /sbin/recovery &) etc. What is interesting in my case is phone bricked after entering recovery and before flashing; sequence below

1. Phone in recovery mode (red triangle screen)

2. run recovry.bat

3. recovery menu appeared on phone screen and disappeared in few secs.; this happened many times before also, but I re-run the recovery.bat command from PC to bring back the menu - but not this time :rolleyes:

4. I heard a USB disconnect sound before I could issue recovery.bat from PC again

5. I saw a failed device driver installation and Unknown Qualcom device appeared in devices list (all while still in red triangle screen)

The rest of the story is same as all other bricked USB phone, I too hope some one will find a workaround.

[Guest Aphax]

So about these bootloops, is it possible not every bootloop is the same? Maybe some are just the kernel panicking and having it automatically reboot after a few seconds (watchdog), and maybe that doesn't trigger a debug mode, while bootloops caused by bootloader failing to boot the kernel (because something fubared the boot partition or something) maybe do? Just guessing here though, I know theres people that understand this much better than I do in this thread..

[Guest antihero_]

I too bricked after taking extreme care with all the advice from every related posts; stable connection with pone placed on desk, run recovery with nohup option (recovery.bat modified with adb-windows.exe shell nohup /sbin/recovery &) etc. What is interesting in my case is phone bricked after entering recovery and before flashing; sequence below

1. Phone in recovery mode (red triangle screen)

2. run recovry.bat

3. recovery menu appeared on phone screen and disappeared in few secs.; this happened many times before also, but I re-run the recovery.bat command from PC to bring back the menu - but not this time :rolleyes:

4. I heard a USB disconnect sound before I could issue recovery.bat from PC again

5. I saw a failed device driver installation and Unknown Qualcom device appeared in devices list (all while still in red triangle screen)

The rest of the story is same as all other bricked USB phone, I too hope some one will find a workaround.

Tried linux?

I'm on linux and sometimes I have to restart adb a fair few times and the process goes a bit mental but it eventually works.

[Guest StuMcBill]

There is a new version of the recovery batch (or Mac / Linux equivalent) released today, which doesn't rely on the USB cable being connected to exit recovery. Paul says it is much safer.

I know this won't fix the problems you guys are having with your USB etc, but its useful to know for anyone following this topic who's device is still working, and still wants to flash ROMs.

Stu

[Guest deeren]

There is a new version of the recovery batch (or Mac / Linux equivalent) released today, which doesn't rely on the USB cable being connected to exit recovery. Paul says it is much safer.

I know this won't fix the problems you guys are having with your USB etc, but its useful to know for anyone following this topic who's device is still working, and still wants to flash ROMs.

Stu

well this won't prevent other bricks i guess. there are other users that reported bricks even when using the ''no hub'' thing in the script