Issues with USB connectivity etc. and root / A2SD

[Guest ZiCoN]

Not much has been said inhere about the issue for a while.... Feels a bit like it's been given up on for now... I hope I'm wrong and people just look at it in silence...

I'm thinking about getting my Hero back and sending the Desire for repair... Just hope they will fix it... Upgraded to 1.21, but thats not official in denmark yet..

[Guest pina]

If there will be no solution, I longer don't want to have the desire since I can't live without the root-functions. Even if I would send it back to HTC and got it repaired, I don't want to root again without a solution with every risk to brick it again, just like a russion roulette.

If there will be no solution, I think no one should root their phone since it will eventually get broken. I will send my Desire back to HTC, sell it and get myself a N1

[Guest ZiCoN]

If there will be no solution, I longer don't want to have the desire since I can't live without the root-functions. Even if I would send it back to HTC and got it repaired, I don't want to root again without a solution with every risk to brick it again, just like a russion roulette.

If there will be no solution, I think no one should root their phone since it will eventually get broken. I will send my Desire back to HTC, sell it and get myself a N1

I've customized all of my qtek and htc phones, and have done it because of the fun of it. My android phones has been because I wanted app2sd and market enabled. When (if) I get my desire back in a working condition I'm not sure I'll do anything to it again (for now anyway) With froyo I get ½ of what I WANT... The rest can wait a bit.

[Guest MIYU-G]

If there will be no solution, I longer don't want to have the desire since I can't live without the root-functions. Even if I would send it back to HTC and got it repaired, I don't want to root again without a solution with every risk to brick it again, just like a russion roulette.

If there will be no solution, I think no one should root their phone since it will eventually get broken. I will send my Desire back to HTC, sell it and get myself a N1

you're more luck than me,I'm in China,there is almost no way to send it to HTC in Cina,except send to HTC,Hongkong

[Guest deeren]

I've customized all of my qtek and htc phones, and have done it because of the fun of it. My android phones has been because I wanted app2sd and market enabled. When (if) I get my desire back in a working condition I'm not sure I'll do anything to it again (for now anyway) With froyo I get ½ of what I WANT... The rest can wait a bit.

yes but you do know that we have a long wait ahead of us till we get froyo. htc announced it for the 2nd half of this year while google announced gingerbread for q4.

so my guess is that htc will release a phone with froyo in the coming weeks or mths. then wait for gingerbread to be released to give us froyo. that's th HTC's way!!!!!!

[Guest PeBo75]

yes,I feel so sad to use the phone,because no dev here to care about this issues,may be they just think "It 's all your fault,,whatever,my phone is ok now" :rolleyes:

I can't understand this. How can you say noone cares about this issue? Who told you? Is it because Paul is working instead of replying to every single post?

I wouldn't want to change with Paul. People were almost crying to get rooted phones as soon as possible, they got. Now people are crying for help with usb disbled phones, they will get. But why are some unable to realise that this will take it's time for problem identification, fixing and creation as well as proper testing the solution?

My Desire is also USB disabled this time and i have to deal with this. It's not funny to switch back to the old phone after 3 weeks with such a nice gadget. Also im checking this site more than once a day to see if something new is available. But for the time we all have to wait.

From IRC i've seen Paul working with others to find out how to flash different protected areas on the phone and most likely this will also help to fix this USB issue.

MIYU-G, please be sure that someone also cares about your phone!

[Guest ZiCoN]

Self pitty is allowed at this point :rolleyes: Frustrating to see others play like we want to.

Don't ever think I don't appreciate what people are trying to do, and I've also offered any and all the help I can provide.

But at this point.... its allowed :D

[Guest MIYU-G]

I can't understand this. How can you say noone cares about this issue? Who told you? Is it because Paul is working instead of replying to every single post?

I wouldn't want to change with Paul. People were almost crying to get rooted phones as soon as possible, they got. Now people are crying for help with usb disbled phones, they will get. But why are some unable to realise that this will take it's time for problem identification, fixing and creation as well as proper testing the solution?

My Desire is also USB disabled this time and i have to deal with this. It's not funny to switch back to the old phone after 3 weeks with such a nice gadget. Also im checking this site more than once a day to see if something new is available. But for the time we all have to wait.

From IRC i've seen Paul working with others to find out how to flash different protected areas on the phone and most likely this will also help to fix this USB issue.

MIYU-G, please be sure that someone also cares about your phone!

Could You Tell Me The Address Of The Irc?Thank You

Edited May 22, 2010 by MIYU-G

[Guest jeckyllhavok]

Could You Tell Me The Address Of Tie Irc?Thank You

irc.freenode.net room: #modaco

[Guest DougieB]

Have you flashed back to stock? Haven't heard of those issues there.

As pointed out on IRC last night and subsequently found on this forum by searching for the keyword 'proximity' the problem was with the proximity sensor ending the call.

Took the phone back to tmobile today, in for repair now.

[Guest ciairo]

I'm afraid this issue is a real tricky one.

It would be good to pack some advice for the lucky ones that still have a working phone.

As far as I have understood and with my direct (:rolleyes:) experience, here is the situation:

• The phone gets bricked when it starts looping after a reboot (for 3 times or more). This is usually due to some tampering done the bad way (e.g. caches or ext partition not wiped before reflashing)
  
• A2SD or A2SD+ might be therefore not a direct cause but they can be an indirect cause if you mess up with the flashing process
  
• I don't think that the issue is really related to low quality usb cables (afaik)
  
• When the phone is bricked, you lost access to the SD card, phone connection, USB access, bluetooth, FM radio
  
• Access to sd card and phone connections can be restored using the fastboot commands: fastboot oem enableqxdm 0 / fastboot reboot
  
• the USB connection will stay broken, the phone cannot be accessed any longer by connecting to the pc. Bluetooth and FM radio will be lost too
  
• Access in recovery mode (via adb commands) will be lost too, undepending on the operating system you use
  
• As an extra gift the battery will drain very quickly (don't know if that is happens to me only)
  
• The only possible access to the phone with an usb cable is using the fastboot mode.. with it we are still able to flash a stock rom, unfortunately this won't fix the problem.
  

The way out would be flashing a patched kernel or a kernel module with fastboot. Unfortunately, while modifying the kernel is definitely feasible, creating a fastboot image seems really hard as it would require signing it with an HTC key.

Therefore, for anyone playing with mods, roms, or kernel, the minimun advice is that you keep the phone case open when patching, and as soon as you end up in a boot cycle you immediately remove the battery from the phone. You can enter fastboot then to wipe the caches, storage, etc or to reflash a stock rom.

Anyone able to confirm that? I'd like to see that as a visible as part of the advice in the root and mod posts.

Too bad that this topic is not getting enough perticipation from the experts depite of the background work that is happening.

[Guest chrmrt]

http://forum.xda-developers.com/showthread.php?t=686698

Just incase you didn't see it :rolleyes: might be useful?

[Guest adi90]

http://forum.xda-developers.com/showthread.php?t=686698

Just incase you didn't see it :rolleyes: might be useful?

post on modaco FIRST ! :D

[Guest pina]

let me quote him here:

Hold Vol Down + Power and goto recovery.

When you get the red triangle push Vol Up and Power and you get a blue recovery menu that looks like this

(I didn't have an update.zip on my sdcard...)

I tried to flash the update.zip, but got received the same error as on the attached screenshot.

[Guest MIYU-G]

let me quote him here:

I tried to flash the update.zip, but got received the same error as on the attached screenshot.

It Is Not Work, :rolleyes:

[Guest r&a]

wonder if paul has a bricked unit at hand to try

if it can help maybe we can send him one

i.e. someone living in the uk so no taxes or shippin delays

and we can raise the funds to get that guy a new one

just my 2c(p)

[Guest MIYU-G]

wonder if paul has a bricked unit at hand to try

if it can help maybe we can send him one

i.e. someone living in the uk so no taxes or shippin delays

and we can raise the funds to get that guy a new one

just my 2c(p)

really hope someone could send a bricked phone to paul,I'm in China,if I sent it,it's a long way :rolleyes:

[Guest zw4mp]

What I ran into in the start of rooting / flashing my Desire was breaking the recovery menu by using "adb". Since I'm on windows, the adb for getting into recovery is called "adb-windows" or "adb-nilezon". If you then run "adb shell" from another cmd prompt it will kill the adb-windows or adb-nilezon's connection with a message like "adb server out of date.. killing" making recovery menu hang. The right way would be to use "adb-nilezon shell", the same exe thats used for the recovery.

I read over at XDA that it's "believed" to be caused by an unstable usb connection when the shell session is running, so this is just something that came to my mind.

and no I don't have a bricked device :rolleyes:

[Guest phunkycow]

My recovery has crashed a few times. Seemed unresponsive, i couldn't use the trackball to move through the recovery options so i just kept killing adb and rerunning recovery-windows.bat - no bricks there. And I've done this numerous times.

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:

[Guest m2te]

wonder if paul has a bricked unit at hand to try

if it can help maybe we can send him one

i.e. someone living in the uk so no taxes or shippin delays

and we can raise the funds to get that guy a new one

just my 2c(p)

Alternatively get Paul a fully working phone then he could try every bad trick in the book to brick it. It may give a definative reason for the problem - and the answer fingers crossed.

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

[Guest pina]

Alternatively get Paul a fully working phone then he could try every bad trick in the book to brick it. It may give a definative reason for the problem - and the answer fingers crossed.

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

I will send mine if you all raise funds for to buy me a new unbricked one for in meantime! :rolleyes:

[Guest Pyr0x64]

My recovery has crashed a few times. Seemed unresponsive, i couldn't use the trackball to move through the recovery options so i just kept killing adb and rerunning recovery-windows.bat - no bricks there. And I've done this numerous times.

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:

i've had a dodgy recovery too, screen flickering, menus messed up and cursor movement somehow being imprecise

i just restarted and loaded the recovery again

i've also had way more than 3 bootloops too, but no brick

[Guest xTc is loVe]

My recovery has crashed a few times. Seemed unresponsive, i couldn't use the trackball to move through the recovery options so i just kept killing adb and rerunning recovery-windows.bat - no bricks there. And I've done this numerous times.

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:

I think its not the Bootloop theory...its is the Rooting Method i think.

And u will be bricked too :D:P:P:P

[Guest jamlam]

I think its not the Bootloop theory...its is the Rooting Method i think.

And u will be bricked too :rolleyes::P:P:P

It would be interesting to know how many of the people with bricked phones did a full wipe before they flashed? I know that I didn't before the flash that bricked mine, and I also saw a message on the phone screen saying no space left on device during the flash. I'm just wondering if something is not getting erased properly by the rooting process causing the phone to run out of space when the new ROM is flashed. A full wipe prior to flashing would avoid this.

[Guest ZiCoN]

It would be interesting to know how many of the people with bricked phones did a full wipe before they flashed? I know that I didn't before the flash that bricked mine, and I also saw a message on the phone screen saying no space left on device during the flash. I'm just wondering if something is not getting erased properly by the rooting process causing the phone to run out of space when the new ROM is flashed. A full wipe prior to flashing would avoid this.

I didn't wipe either...