Jump to content

Issues with USB connectivity etc. and root / A2SD


Recommended Posts

Guest xhemp
Posted
Do you think it's a software issue, or a hardware issue? Because if it's a software issue or bug, it should be possible to fix it... but if it's hardware related, then I think it's broken...

I can't believe this is hardware related as it works on Fastboot/Hboot and also, it charges the device when in OS mode.

Guest ZiCoN
Posted

Don't know 'bout you guys... but I'm just about ready for that module patch... Next thing is to throw in the towel, and send it in for repair :)

Guest pina
Posted
the issue for me is in the step2 with this line "sudo ./adb-mac shell /sbin/recovery &"

so I suggest to do only the 1st step, you will have the testrom rooted and play with it by doing the 2nd step except the list line of the shell. You will be able to do what you want with adb. I did it last night with my new desire (1st one bricked).

And sorry, but for me the only solution for the bricked desire is to send it back to htc...

how could you send it back to htc since you have rooted it? Don't they notice that you have rooted the device, even if you unrooted before returning it?

Guest Specialist79
Posted

Is there anyone who did NOT perform a nandroid restore before bricking USB?

Guest kecal01
Posted
Is there anyone who did NOT perform a nandroid restore before bricking USB?

i didnt perform nandroid restore, and have bricked usb , i had done only wipe from pushed recovery.

Guest pina
Posted

I just performed a full wipe (except the ext3-partition, which I never do) and was ready to get into recovery mode and flash my custom rom.

Guest eViL D:
Posted
Is there anyone who did NOT perform a nandroid restore before bricking USB?

Yeah, why?

Guest geek78
Posted
how could you send it back to htc since you have rooted it? Don't they notice that you have rooted the device, even if you unrooted before returning it?
It was an orange one : they have sent me first the new one and then I have sent the bricked one :)
Guest pina
Posted
It was an orange one : they have sent me first the new one and then I have sent the bricked one :)

lucky you... I could bring it back, but the store needs to perform a checklist first, and I'm afraid they will see that I rooted the phone...

Guest xhemp
Posted
lucky you... I could bring it back, but the store needs to perform a checklist first, and I'm afraid they will see that I rooted the phone...

Unroot your device following the thread on Modaco and you will be fine.

Maybe I'm wrong, but I can't think of a way they notice you rooted your device if you flash it with a stock rom.

Guest PeBo75
Posted

+1

Hi Guys, sorry for this being my first post.

My Desire was doing quite good up to MCR r2 out of the kitchen. Yesterday when r3 became the "official" release i got one from kitchen, in recovery in did a nandroid backup and after this completed OK i flashed the new r3. Reboot was stuck for at least 30min on "quietly brilliant", the i did a restart by pressing vol- + power + trackball. Thereafter it booted fine but reached at lockscreen without SD & USB. Sense and some apps crashed instantly what must be because of A2SD+ which isn't working without SD.

MCR r3 was not the time to introduce A2SD+ to my Desire. Also my r2 build had it already and it was working fine.

Now i restored SD with the fastboot commands and it was working more or less ok.

If only i could go back to custom recovery once more to restore my nandroid backup :) but i think this is what some more of you wish to do... So i line up with you, waiting for some new input. For the time i went back to fastboot mode and reapplied the official RUU to be able to return the Device. Got it from a local dealer and will try it later.

PeBo

Guest Biliskner
Posted

this is insane... #users reading these posts / #users bricked Desires / #pages in this thread!

btw, if your battery is being chewed up 100% -> 0% in 6 hours of whatever (whether you're using it or not), I've found that turning ON pattern-lock makes your battery life 100% BETTER. I'm running TestRUU ROM and I've still got 50% charge in my phone (all day at work, WiFi on, FB/Twit update 2hours, Email 1hour, approx. 1 hour of 3G surfing on train today, random SMSs, random phone calls - only used 50% battery) :)

Guest pina
Posted
Unroot your device following the thread on Modaco and you will be fine.

Maybe I'm wrong, but I can't think of a way they notice you rooted your device if you flash it with a stock rom.

It's just that maybe HTC could link the bug of my phone with the rooting process, since the bug only occurs to people who tried to root/flash the phone...

Guest xhemp
Posted
It's just that maybe HTC could link the bug of my phone with the rooting process, since the bug only occurs to people who tried to root/flash the phone...

I understand but I don't know if they can do something about that, we will see.

Well, I sent mine yesterday, they received it today.

As I said earlier, I will tell you guys what they say :)

Guest Biliskner
Posted
I understand but I don't know if they can do something about that, we will see.

Well, I sent mine yesterday, they received it today.

As I said earlier, I will tell you guys what they say :)

thanks xhemp ;)

Guest NOFX
Posted
thanks xhemp :)

Sent mine today - in Denmark - I'll also let you guys know...

Guest ciairo
Posted
Very interesting... we are able to insert modules, so this could be worth a try?

P

Paul (or anyone else of the gurus),

did you manage to make any progress with this approach?

I still think that trying to revert it would be anyway better than sending it..

Guest pina
Posted

since HTC released the kernel, I would think that developers has complete access to the phone, so the usb-lock could be fixed?

Guest NisseGurra
Posted
OK, I think that's enough: it's time to issue a STOP FLASHING for everyone until this glitch is sorted out. Paul?

Agree, seems that this root was rushed out without proper testing, and now there seem to be none help to solve the issues

Posted
Agree, seems that this root was rushed out without proper testing, and now there seem to be none help to solve the issues

common we all knew the risks just couldn't wait

probably because there's always this fallback - return to htc (i hope)

our problem is in a way what this and xda community are about

making out devices better

i for one will wait as long as i can for a fix

unless the gurus throw the towel in...

Guest Biliskner
Posted (edited)
Agree, seems that this root was rushed out without proper testing, and now there seem to be none help to solve the issues

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)

Edited by Biliskner
Guest pina
Posted
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)

I think it will get sorted out when there's a new rooting and flashing procedure. To get into the recovery without the need of adb, just like on the Hero

Guest afiorillo
Posted (edited)
[...] in that crazy 90+ page thread [...]

[OT] I do LOVE threads like these, it means lots of passion (meaning literally) in it! :)

Edited by afiorillo

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.