Issues with USB connectivity etc. and root / A2SD

[Guest NisseGurra]

Yeah, if you re-read the first page, YOU took the risk. I think it says that at least twice on the front page (and about a more thousand times in that crazy 90+ page thread)

Sure, but this root have is way to flaky, should not been released..

[Guest Biliskner]

Sure, but this root have is way to flaky, should not been released..

Rooting is always flaky.... (yes, pun) :)

[Guest pina]

there's no use to blame someone for this. It's more important that we try to find a solution for the bug... because I don't dare to root again until there's a new rooting method

[Guest NOFX]

Sure, but this root have is way to flaky, should not been released..

I agree with both of you. Flashing is always a risk - and should be done at own risk.

However - I think there should definitely be a 'stop flashing' warning on both MoDaCo and XDA. I wouldn't want anyone else having these same issues...

[Guest xhemp]

Let's not blame anyone but ourselves, I'm pretty sure that people that didn't touch their devices since they bought, don't have this issue, so...

But as NOFX said and I completely agree <quote below> :)

However - I think there should definitely be a 'stop flashing' warning on both MoDaCo and XDA. I wouldn't want anyone else having these same issues...

Edited May 19, 2010 by xhemp

[Guest NOFX]

Let's not blame anyone but ourselves, I'm pretty sure that people that didn't touch their devices since they bought, don't have this issue, so...

But as NOFX said and I completely agree <quote below> :)

Done - I just posted a thread on XDA regarding this ;)

[Guest deeren]

I totally agree that we are the ones responsible for our phones. i do not put the blame on anyone. however i should state that all these quotes on each dev thread '' do at your own risk ...i am not responsible if you've bricked your device.....'' is a quote that everyone takes lightly. i mean it is usually interpreted as '' if u do not follow the instructions carefully and u brick your phone, i am not responsible''; and also, if somebody gets an issue , it would be at the moment of the flash!!!!

But here we have a different scenario, even with proper instructions and all, we are getting problems. some immediate, some after weeks..... and surprisingly enough, our comrades at the htc legend section seem to have the same problems too.

so imo, this is clearly a problem in the root method.

once again, i am not blamimg paul here. He has done tremendous work on the android platform. and i am sure that he had put a lot of effort in this root but i am just stating the facts.

Edited May 19, 2010 by deeren

[Guest ZiCoN]

I'm neither a coder or a developer... But instead of thinking about who to blame or not, we need a fix.... Does anyone have the know-how to make the patch suggested earlier in the thread? Could we, as non-coders, do something to speed this process up somehow?

If I can do something, please let me know... I think this goes for anyone with this issue...

[Guest StuMcBill]

Trying again to narrow down causes, did the pricked people have their USB cables attached while entering recovery, or did they attach it after it loaded?

I have no experience with these things, its just that mine is still ok (touch wood), and I have always let recovery load, then attach the USB cable, let Windows recognise it, then run the bat file.

[Guest deeren]

Trying again to narrow down causes, did the pricked people have their USB cables attached while entering recovery, or did they attach it after it loaded?

I have no experience with these things, its just that mine is still ok (touch wood), and I have always let recovery load, then attach the USB cable, let Windows recognise it, then run the bat file.

so far from what i know, you cannot access recovery without the usb connected.

i mean, you have to attach usb to load recovery!!!

[Guest StuMcBill]

so far from what i know, you cannot access recovery without the usb connected.

i mean, you have to attach usb to load recovery!!!

No, what I mean is do you have your usb attached when you press "recovery" in the bootloader? Or do you wait to see the red triangle and then attach it?

[Guest ciairo]

I'm neither a coder or a developer... But instead of thinking about who to blame or not, we need a fix.... Does anyone have the know-how to make the patch suggested earlier in the thread? Could we, as non-coders, do something to speed this process up somehow?

If I can do something, please let me know... I think this goes for anyone with this issue...

I fully agree.

I don't care about where to put the blame, I care about fixing a bricked device :)

Considering the great work done for the rooting process, I would feel more confortable if I knew that Paul and the other guys are currently attacking this problem to find a fix.

Otherwise mates it's gonna be time to think to a strategy with the HTC support service.. that I would rather avoid. It's about paying other extra money for a software fix (unless we lie and they trust us), and losing every will to root/mod again.

Well, and I also agree in being of help if I can. Images and fastboot commands are well accepted!

[Guest ciairo]

No, what I mean is do you have your usb attached when you press "recovery" in the bootloader? Or do you wait to see the red triangle and then attach it?

To me it used to work in both ways.. and now that is bricked it doesn't work in either way

[Guest ZiCoN]

I found this while trying to port the kernel to a more forward version:

#define ULPI_VERIFY_MAX_LOOP_COUNT  3

static int msm_hsusb_phy_verify_access(void __iomem *usb_base)

{

        int temp;


        for (temp = 0; temp < ULPI_VERIFY_MAX_LOOP_COUNT; temp++) {

                if (ulpi_read(usb_base, ULPI_DEBUG) != (unsigned)-1)

                        break;

                msm_hsusb_apps_reset_phy();

        }

        if (temp == ULPI_VERIFY_MAX_LOOP_COUNT) {

                pr_err("%s: ulpi read failed for %d times\n",

                                __func__, ULPI_VERIFY_MAX_LOOP_COUNT);

                return -1;

        }

}


[/codebox]

Can someone with a usb-bricked device thoroughly check the kernel log for messages containing [b]ulpi read failed[/b] or similar?

If I am right the only thing one needs to do to revert this is call one of this functions from kernel space.

[codebox]
if (reset)
ret = msm_proc_comm(PCOM_CLK_REGIME_SEC_RESET_ASSERT,
&usb_id, NULL);
else
ret = msm_proc_comm(PCOM_CLK_REGIME_SEC_RESET_DEASSERT,
&usb_id, NULL);

This would need to be done in a module, I am not sure if we can easily insert modules now. I am not able to test this because my device is working correctly but I thought it might be useful for some.

Allright..... How do you make a module? What needs to be done?

It could be that this is what needs to be done... It would make absolutely sense, since all of us had boot loops when it happend (correct me if I'm wrong)

[Guest jeckyllhavok]

Allright..... How do you make a module? What needs to be done?

It could be that this is what needs to be done... It would make absolutely sense, since all of us had boot loops when it happend (correct me if I'm wrong)

does it mean that at 3 boot loops the debug mode is activated?

man, that woulb be real sad, which idiot programmed that at HTC?

[Guest DougieB]

does it mean that at 3 boot loops the debug mode is activated?

man, that woulb be real sad, which idiot programmed that at HTC?

Any brave soul willing to boot-loop their working desire a few times to test? :)

[Guest eViL D:]

Any brave soul willing to boot-loop their working desire a few times to test? :)

are you serious?

[Guest DougieB]

are you serious?

Nope. I certainly wouldn't do it....

Seriously though, thinking about what others have said ... I did know this was at my own risk, and I have no complaints really with anyone except HTC. I do think we should have a temporary sticky warning people though, as is on XDA... I just figured the problem was with A2SD. Never used A2SD, but did have boot-loop and now USB-bricked.

A note to HTC if they're reading - the reason I opted for an android phone is because android is so open, I had an iPhone and will never own another apple product again due to their closed nature. Stop locking down our phones ... they're not your phones, they're ours. Next time I come to buy a phone, I'll be more cautious of how rootable they are. If you lock down the phone too much, I'll vote by not giving you my cash....

Edited May 19, 2010 by DougieB

[Guest lmb__]

what if you just peel out the battery if you see the phone just looping? could that be a step of preventing it from happening? if i saw my phone rebooting i Definitely would have done that

[Guest xTc is loVe]

Next time I come to buy a phone, I'll be more cautious of how rootable they are. If you lock down the phone too much, I'll vote by not giving you my cash....

WORD man!

Im so a idiot that i dont bought the Nexus One ..... This phone is much better because it has full root sh*t off this few mb ram! Next time only a Google or another Dev Phone!

BTT:

Is anyone serious like paul working on this issue? Or should i better send my Phone back because i unrootet it?

[Guest SonicArt77]

what if you just peel out the battery if you see the phone just looping? could that be a step of preventing it from happening? if i saw my phone rebooting i Definitely would have done that

Only if we had known before HTC released the kernel...

[Guest lmb__]

Only if we had known before HTC released the kernel...

yea, but maybe a tip so not more phones get bricked? i know it wont unbrick already bricked phones...

[Guest Heppieboeddah]

Just to let you all know and maybe it might be of any help. As we all know on the phone usb-debugging shouldt be on when flashing.

This morning I wanted to try the rom 1.2.1 WWE as was posted on XDA. That went without any problems. As i didn't think it was worth keeping it on my phone, i started to root my phone again and apply apps2sd as was described in the first post publiced on 28-04 by Paul.

TestRUU, rootupdate.zip, apps2sd...just the oldschool way. After flashing apps2sd i came in the first boot and after doing the settings, I noticed that on the notification-bar there was a small triangle that says ' USB-debugging is enabled. Tick here to disable'?! So i disabled usb-debugging and wanted to transfer the backup i had made from my pc to the sdcard. And yes, the sdcard wasn't recognized and usb was not working.! I thought my phone was bricked as well.

I started the process all over again, and again by first boot and after the setting there was that notification . Turned usb-debugging off and again no sdcard and usb. Then i rebooted the phone with usb-debugging unticked and after the startup i saw that my sdcard was initialized and plugging my phone in the pc as diskdrive everything was up and running again.

To get to the point, maybe the guys with the usb-failure might try to restart the phone with usb-debugging unticked, and see what happens.

It might just be that simple.

Edited May 19, 2010 by Heppieboeddah

[Guest afiorillo]

[...]

To get to the point, maybe the guys with the usb-failure might try to restart the phone with usb-debugging unticked, and see what happens.

It might just be that simple.

We're calling it "usb brick", but it involves much more than the USB port: SD card, FM radio, missing filesystem portions, odd behaviours, 3G and BT issues and so on.

No, I don't think it's a mere checkbox problem. Life is never so easy.

[Guest Heppieboeddah]

We're calling it "usb brick", but it involves much more than the USB port: SD card, FM radio, missing filesystem portions, odd behaviours, 3G and BT issues and so on.

No, I don't think it's a mere checkbox problem. Life is never so easy.

Just wanted to share my observations. And it might be disappointing for you...but live is easy

Anyway in holland they have a saying that goes like:

"Niet geschoten is altijd mis"!

"

Free translated that is in english

"If you dont shoot, you'll never hit"

justmy2cents

Edited May 19, 2010 by Heppieboeddah