Issues with USB connectivity etc. and root / A2SD

[Guest mardox]

i know exactly when this happend to me.

everything was fine and i wanted to try out the clear notification mod so i flashed the mod. but before flashing i made a nandroid backup. the mod worked fine but i did not like it. so i booted down and went into recovery. in recory i ran the program to get to green recovery menu. when in the menu i went to nandroid restore but the green menu dissapeard and i had to run the program again to re-enter green menu, here i did a nandroid restore (without a wype inbetween, i forgot to do this) nandroid restore was succesfull so i pressed reboot. on reboot i get tons of bootloops ( at the part before qeuitly brilliant) but after a couple of loops the phone boots but without sdcard, and thats when i remember i should have wiped so i shut down phone and try to get to recovory but my computer wont detect my phone.

all this was done without a2sd , although i have had A2SD before and it has worked perfectly. the rom i was on didnt even support A2SD ( rom was evil desire 1.2.3 bare )

hope this helps

[Guest jdouce]

ARGH!!!!! i didnt have bootloops or use nandroid theres no consistency ANYWHERE

so far we got

with/without a2sd

with/without nandorid

with/witout usb-ms

with/without bootloops

have we actually ruled out ... anything

WINDOWS???

someone check the windows recovery method

i had not problem till i used windows! just realised i did all my flashes except 1 from unbuntu

Edited May 16, 2010 by jdouce

[Guest eViL D:]

It's the recovery process itself. I was pretty sure everyone understood this. This (usb bricking) has, from what I've heard (including me) happened right after flashing, obviously from recovery. But, please correct me if I'm wrong. Something happened with the scripts/files pushed to the phone during or after the reboot.

*if it means anything either, my rom was based off of Pauls r1.

Edited May 17, 2010 by eViL D:

[Guest jdouce]

r2 bricked me

i think its windows during the recovery pushing process

i did 10+ flashes in linux, all ok

first windows flash , bricked

Edited May 17, 2010 by jdouce

[Guest xhemp]

2 flashed in same fastboot rules out i flashed twice during my initial root ... instantly flashed r1 and was fine

btw the guys over at acer liquid had a similar issue .... caused by a2sd

every1 on here

go to android market

get USB Switcher

it says get pro or somthing ignore it

connect to pc

use it (its a widget u gota add it to home)

see if usb ms works ... it worked for me

now i got usb mass storage back

if this works for every1

its a HTC software issue

actually ... is every here using a non sense version?

saying that im only partiually usb bricked .. still have acess in fastboot

My device is not rooted now, I believe it is needed to run this application.

I got my device back to Stock as I'm sending it back to HTC for repair.

[Guest Carnage21]

Just spotted a couple of interesting strings in the hboot file:

usbtestmode: <value>

value=0 -> disable

value=1 -> enable

readconfig

Can somebody with a bricked device test whether that is a valid fastboot command?

no go

also fyi

flashed here using win 7 x64 , i am usb bricked , i dont remmeber doing the usb mount thing , but i did nandroidbackup , no a2sd

[Guest Carnage21]

2 flashed in same fastboot rules out i flashed twice during my initial root ... instantly flashed r1 and was fine

btw the guys over at acer liquid had a similar issue .... caused by a2sd

every1 on here

go to android market

get USB Switcher

it says get pro or somthing ignore it

connect to pc

use it (its a widget u gota add it to home)

see if usb ms works ... it worked for me

now i got usb mass storage back

if this works for every1

its a HTC software issue

actually ... is every here using a non sense version?

saying that im only partiually usb bricked .. still have acess in fastboot

no go

[Guest Biliskner]

r2 bricked me

i think its windows during the recovery pushing process

i did 10+ flashes in linux, all ok

first windows flash , bricked

You can count me out of that. ALL my flashes were in Ubuntu 9.0 non-VM.

The only Windows thingo I used was step1 in Paul's r1 method, flashing the testRUU. The rest was Linux (recovery-linux.sh).

[Guest Biliskner]

Just my 2 cents:

AFAIK the phone comes with a configuration data area most likely in NVRAM (probably connected via I²C). This configuration contains parameters such as the device serial #, the regional branding, wifi rf calibration data and the kernel command line. Having had a look at the kernel sources, it contains much more. Some of these parameters are interpreted by the kernel, some are just ignored (cf. dmesg output). The same applies to the kernel command line parameters.

IMHO, some (yet unknown) event has altered this configuration data on the affected devices. IMHO, just re-flashing will not help as this operation will almost certainly not overwrite device-specific factory settings.

I think you may be right. The ONLY thing common to ALL usb-bricks is the flashing process. It's not Windows, Linux, A2SD or anything. It's just the fact we're trying to root our phone. Why some people flashed different ROMs over 20x and then usb-bricked it on the 21st time is a mystery however....

[Guest xhemp]

Guys

This is really random.

For 2 weeks we've been trying different things with no luck.

I can't think anymore.

[Guest Biliskner]

As far as a fix is concerned: I'd probably disassemble the hboot code to better understand what's going on, but unfortunately my trial version of IDA Pro does not seem to come with ARM support (contrary to what the web site says). There also seems to be a factory mode built into the device, which can apparently be activated by providing the androidboot.mode=factory2 on the kernel command line. This seems to activate a kind of serial console according to the source. Use at your own risk...

Specialist79, PM kingoffail (he has posted on page 1 or 2 on this thread I think). He was in the middle of disassembling the HBOOT (not sure how far he got) - maybe you could grab the stuff he has already disassembled and go from there.. ?

[Guest deeren]

Definetely not a windows thing. I have been using linux mint all along.

hboot- .75, i have been using ap2sd on some occasions, have been using th usb mount functionality in recovery and have been flashing more than 30 times.

now that i think, i remember starting getting problems with usb recognition when entering recovery at times but it got resolved after some attempts.

when it got bricked? well, just before getting bricked i remember that in recovery , the screen starting flickering. after that .....Kaboum!!!!!

i guess i'll send it for repairs too.

[Guest Biliskner]

HTC is gonna love all these "repairs" that have stock ROM on them - they'll be like 'wtf'? happened to all these phones!' :)

[Guest andy76q]

Definetely not a windows thing. I have been using linux mint all along.

hboot- .75, i have been using ap2sd on some occasions, have been using th usb mount functionality in recovery and have been flashing more than 30 times.

now that i think, i remember starting getting problems with usb recognition when entering recovery at times but it got resolved after some attempts.

when it got bricked? well, just before getting bricked i remember that in recovery , the screen starting flickering. after that .....Kaboum!!!!!

i guess i'll send it for repairs too.

same here, only linux and i've tried the app2sd but removed it. had the same flickering in the recovery at the time it got bricked.

[Guest Specialist79]

no go

What exactly did you try? I would try myself, but my Desire is unaffected and certainly will remain so until this has been sorted out.

[Guest NOFX]

You can flash via fastboot oem rebootRUU then fastboot flash zip zipfilename (where zipfilename is a signed zip).

I have a question - did any of those having this issue use the 'USB mount' function in recovery?

P

Ok - so I just did this with the rom.zip file from the 'Unroot' guide.

What I'm getting is a lot of commands - and then in the end a 'FAILED <remote: 90 hboot pre-update! please flush image again immediately>

What dows this mean?

[Guest ZiCoN]

Just spotted a couple of interesting strings in the hboot file:

usbtestmode: <value>

value=0 -> disable

value=1 -> enable

readconfig

Can somebody with a bricked device test whether that is a valid fastboot command?

In Connectbot:

usbtestmode 0

usbtestmode: permission denied

[Guest ZiCoN]

Fastboot source code:

http://android.git.kernel.org/?p=platform/...3bc9fdc;hb=HEAD

[Guest Snarkasm]

The only time I did anything in Linux was to root the original time, using the TCL method. I've done 30 or so flashes in Windows outside of that, and I'm still unbricked. At least in my case, it's not Win7's fault.

[Guest Biliskner]

In Connectbot:

usbtestmode 0

usbtestmode: permission denied

You need to have a rooted ROM. Stock ROM will give you permission denied for most commands.

I'm going to flash TestRUU tonight and see if I can get any of these commands to work...

[Guest Specialist79]

You need to have a rooted ROM. Stock ROM will give you permission denied for most commands.

I'm going to flash TestRUU tonight and see if I can get any of these commands to work...

I was under the impression that this was a fastboot command, not a shell command (this existence of which is a lucky coincidence). So trying it via fastboot could also be an additional option.

[Guest afiorillo]

Could it be that flashing twice in the same fastboot session triggers the issue?

Nope. I did that many times without any problem.

[Guest afiorillo]

r2 bricked me

i think its windows during the recovery pushing process

i did 10+ flashes in linux, all ok

first windows flash , bricked

I rooted under Linux, flashed gazillion times under Windows, no probs. Despite my warnings to other people, I flashed even through two serialized USB hubs and a retractable ultra-cheap cable using a messed-up Windows netbook equipped with a mere Atom and 1 GB RAM running Windows 7, while iTunes was playing music. So, it's definitely not a Windows issue. :)

[Guest Biliskner]

I rooted under Linux, flashed gazillion times under Windows, no probs. Despite my warnings to other people, I flashed even through two serialized USB hubs and a retractable ultra-cheap cable using a messed-up Windows netbook equipped with a mere Atom and 1 GB RAM running Windows 7, while iTunes was playing music. So, it's definitely not a Windows issue. :)

lmfao...

[Guest NOFX]

I rooted under Linux, flashed gazillion times under Windows, no probs. Despite my warnings to other people, I flashed even through two serialized USB hubs and a retractable ultra-cheap cable using a messed-up Windows netbook equipped with a mere Atom and 1 GB RAM running Windows 7, while iTunes was playing music. So, it's definitely not a Windows issue. :)

I flashed a lot of different ones in Windows XP as well - no problems. My problems came after I installed the Apps 2 SD app from xda - and partitioned my SD-card.

It wasn't while installing a new ROM!