Issues with USB connectivity etc. and root / A2SD

[Guest afiorillo]

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!

However, "installing" A2SD is actually the same process as flashing a ROM.

Just a note: you're the second or third guy I read ended bricked after flashing something from XDA-Dev. This could be nothing, since me too did something like that flashing the "circled battery" update, that cames from XDA-Dev: but your words make me think.

[Guest r&a]

i never used a2sd it happened just after flashing r1-withadditions

i flashed 5.0.6 before and all was ok

never used mount sd or anything that was mentioned here

the only issue might be- i flashed without erasing data as it wasn't stated a must

Edited May 17, 2010 by r&a

[Guest afiorillo]

i never used a2sd it happened just after flashing r1-withadditions

i flashed 5.0.6 before and all was ok

never used mount sd or anything that was mentioned here

the only issue might be- i flashed without erasing data as it wasn't stated a must

Have you ever flashed a radio update?

[Guest r&a]

Have you ever flashed a radio update?

yes just after rooting

[Guest mosbie]

Ok, I have the same problem on a HTC Legend (And I found a couple of more Legend owners scattered around this and the XDA forum).

I succesfully rooted this device with the instructions of Paul. And after trying some custom ROMS suddenly I had this issue. The SD card was solved easily with exactly the same commands as for the Desire.

I know it's of no help but just to let everybody know that it is not a Desire only problem.

[Guest Biliskner]

I've flashed TestRUU and have SU access.

Is there anything I can try? mkdir recovery / push files that are non-bricked desires onto mine? I tried the radioupdate 4 command, gave no error but nothing seems to have changed. The usbtestmode is not a command as far as I can tell (in Terminal) or with fastboot command...

[Guest afiorillo]

yes just after rooting

OK, so let's start it again. Is there somebody out there with an usb-bricked phone still with a stock (untouched) radio ROM in?

Edited May 17, 2010 by afiorillo

[Guest mardox]

i haven't touched my radio :) just rooted and went on to flash roms, but none with the radio update

[Guest Snarkasm]

I rooted via MoDaCo help, but every ROM I've flashed afterwards has been an XDA ROM, and most of those with A2SD baked in. Still safe.

Sad to hear the Legend's looped in on this now, too. Hopefully we can figure it out.

[Guest zanshin]

r2 bricked me

i think its windows during the recovery pushing process

i did 10+ flashes in linux, all ok

first windows flash , bricked

Nope I just used linux and mine is bricked too.

[Guest Linkazoid]

Mine bricked after flashing the new radio using OSX.

But i also have a problem of the proximity sensor disabling the network service when it is enabled in a call. :)

Edited May 17, 2010 by Linkazoid

[Guest eViL D:]

Have you ever flashed a radio update?

Grasping at straws here. We know it's the recovery. Paul is a wonderful dev and a great person I'm sure (I'm not blaming him). But, let's be real. This "non standard" technique of entering recovery is the culprit (yes i understand the risks). Now there might be some other variables like rebooting versus shutting down, but again, I believe that's grasping at straws too.

I also do remember my screen flickered while in recovery at one point, but it did not do this before the "usb brick". Not that I can remember at least, but it did worry me. Here's what happened to me. I rebooted to recovery, push files, wiped everything, transfered my rom via usb mount, flash successfully and then shut down to swap memory cards. After that I powered on, it boot looped at the first htc splash, I pulled the battery and powered it back on successfully, but that's when i noticed no sdcard mounted.

Edited May 17, 2010 by eViL D:

[Guest kiokoman]

Grasping at straws here. We know it's the recovery. Paul is a wonderful dev and a great person I'm sure. But, let's be real. This "non standard" technique of entering recovery is the culprit. Now there might bee some other variables like rebooting versus shutting down, but again, I believe that's grasping at straws too.

I also do remember my screen flickered while in recovery at one point, but it did not do this before the "usb brick". Here's what happened to me. I rebooted to recovery, push files, wiped everything, transfered my rom via usb mount, flash successfully and then shut down to swap memory cards.

my screen flickered too a couple of time in recovery menu but it is still unbricked

[Guest afiorillo]

Grasping at straws here. [...]

Agree. But what else? You say it's a recovery' fault: I say that if this is the case, it should fail every time instead of killing devices randomly. So, there's another (con)cause and I'm pretty confident it's an evil sequence of flashes.

[Guest eViL D:]

my screen flickered too a couple of time in recovery menu but it is still unbricked

I didn't say it flickered then bricked, just stating that it did that. Another poster had mentioned it. It could be a warning sign, it could be nothing. I'm just saying I've seen that.

[Guest xhemp]

I called HTC today and they will collect my device tomorrow. I will let you guys know what they say.

[Guest jdouce]

argh... this is anoying

os is ruled out various os's been used

method rules out

leaves recovery and what was being flashed at the time

[Guest eViL D:]

argh... this is anoying

os is ruled out various os's been used

method rules out

leaves recovery and what was being flashed at the time

I don't think what is being flashed has anything to do with it, since bricking is occurring from updatezip to r2. If I had to guess, I would say it's the mounting and dismounting process within the recovery. And, from Pauls earlier post, I think he has an idea. And, I think we're hosed until an unlocked bootloader, like Paul had been asking for.

[Guest deeren]

sEVIL D is right. i think that the rooting technique is the culprit. i mean, is it a coincidence that users at the htc legend forum too are having these problems too?????

P.S the last time i could enter the recovery , my screen flickered a lot. each time i moved through the options with the optical trackball. i didnt pay attention at that time and flashed. it booted all right but thta was the end of it/

[Guest jdouce]

HOPEFULLY now the kernel is available they will find some vulnerability and get us a custom Recovery.

[Guest NisseGurra]

sEVIL D is right. i think that the rooting technique is the culprit. i mean, is it a coincidence that users at the htc legend forum too are having these problems too?????

P.S the last time i could enter the recovery , my screen flickered a lot. each time i moved through the options with the optical trackball. i didnt pay attention at that time and flashed. it booted all right but thta was the end of it/

Yes, the recovery is flaky, seem very sensitive for usb cable movement. I had few disconnects but luckily not during flash. Can it be a connection/data stream error that bricks the phones?

[Guest dimor]

sEVIL D is right. i think that the rooting technique is the culprit. i mean, is it a coincidence that users at the htc legend forum too are having these problems too?????

P.S the last time i could enter the recovery , my screen flickered a lot. each time i moved through the options with the optical trackball. i didnt pay attention at that time and flashed. it booted all right but thta was the end of it/

same thing with my device...

[Guest Specialist79]

Agree. But what else? You say it's a recovery' fault: I say that if this is the case, it should fail every time instead of killing devices randomly. So, there's another (con)cause and I'm pretty confident it's an evil sequence of flashes.

Not necessarily. Timing will be subtly different between different recovery sessions, which might be sufficient to explain the weird bricking pattern.

[Guest NOFX]

I don't think what is being flashed has anything to do with it, since bricking is occurring from updatezip to r2. If I had to guess, I would say it's the mounting and dismounting process within the recovery. And, from Pauls earlier post, I think he has an idea. And, I think we're hosed until an unlocked bootloader, like Paul had been asking for.

but where is Paul :)

[Guest xTc is loVe]

but where is Paul :)

Yes i would like to hear from him =( =(

Someone tested this? http://www.droidforums.net/forum/hacking-h...-using-sbf.html