Related
Hey guys,
I have a very annoying and reproducible problem with my Desire. Everytime I connect the phone via USB (no matter if dock, laptop, wall) it reboots ~2 seconds after removing the USB cable from the phone.
I have had this problem for about 2 weeks now, across 4 or 5 Custom Roms (Sense and Non-Sense) and right now I am on CM6.1 Nightly 214.
It just annoys the crap out of me, for example when I got the Desire in the dock next to my desk and I receive a call, I can only accept the call handsfree, because removing it from the dock would cause a reboot and I would lose the call...
Please give me some kinda advice, I just flashed the latest radio and it worked twice without rebooting and now I'm back to square 1.
All the best,
Paul
Sounds like a faulty battery or some kind of defect at the power supply.
I suggest you try this with another battery, maybe from a friend.
You should check the usb connector on the phone too for some sort of deformation or smudge.
I thought that it could be the usb cable you are using, but since it does the same with the dock, it's not it.
The easiest and the most not likely way to fix it is with the calibration of the battery, if you have luck maybe it's just the OS that errs.
Thanks for your thoughts on my problem. Right now I am waiting for an important call but I got a spare battery from a friend of mine already and will later check and see if the problem occurs with the spare battery as well.
But the other point you mentioned was a calibration of the battery: how exactly do I do that? Just AmonRA Wipe Battery Stats or are you talking about another method?
Cheers for the advice!
this is for the calibration of your battery.
http://forum.xda-developers.com/showthread.php?t=755903
Hi, hope it works with the other battery, otherwise you'll have to send it for repair.
The battery thing I mentioned, has a minimal chance of working, but at least when I am desperate I try things that have even the smallest chance of fixing it. So in essence the process is: charge untill full when powered on; disconnect charger (which will automatically reboot your phone in your case);
don't let it boot, enter hboot for example and turn it off; then charge till full again; now boot into recovery wipe stats; and finally just boot into android.
Another thing worth checking I think is the pins where the battery connects to the phone, they should look clean (I wipe pins with rubber for a pencil) and intact.
Edit:Well seems like Marios already posted a link but mine is specific for your situation
did you solve the problem?
i have the same thing... very strange.
calibrating the battery didn't help.
No, I still haven't found a solution. Strangely though, it doesn't reboot anymore if I charge it via USB on my laptop. On my desktop and via the wall charger it still reboots every time I unplug it. Sorry I can't be of more help
my phone reboots when disconnecting from my laptop too.
even when in recovery, very strange...
have you tried to try the unbricking process with the misc.img?
Actually, I haven't tried that one. Can you give me a link to what you're talking about?
IT WORKED!
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
just flashed the update.zip and i can copy the files to/from my laptop using the usb cable.
and it doesn't reboot when unpluging too
Got the same issue, tried modaco´s workaround, same thing... it started happening after i flashed CWM3.0x wich reovery do u use?
gonna try flashing Ra again and see what happens....
Solved It
Like i said, happened after flashing cw3.x finnaly i got home, flashed RA-desire-v2.0.0-CM again, then flashed update.zip from modaco´s thread, and for now it stoped....
just gonna see what happens when the battery get fully charged....
EDIT: Fully charged 4192mV removed it, and.... nothing happened...
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
congrats
powlemann said:
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
Click to expand...
Click to collapse
NICE....
How did u solved it, u never know.....
I tried all things listed in this thread and some more, too.
But, it still reboots when removing from power supply (pc connection works now).
Perhaps you tried some things not listed here?
I am not sure when the problem started for me.
I installed cm7 nightlies with no reboot-problem, also switched from alpharev1.5 to alpharev1.8 and from cwm2 to cwm3.
All in a few days.
Somewhere along these days the problem appeared.
Btw.:
I got reboots on both kinds of usb connections (PC/power supply).
Debugging connection (adb, fastboot) worked.
Accessing the phone as usb storage device worked, too.
So this may be a little bit different from the cases described in the thread.
To solve the issue, I tried several things:
First I restored older backups (versions of cm7) with no success.
Then I restored my last backup of cm6 nightly from just before cm7, and it didn't work either.
As I was 100% sure that this worked before, I now concentrated on the remaining parts, recovery and boot loader.
So I first tried downgrading to clockworkmod2.
Then I tried updating to a newer alpharev1.8 (as it was a little bit newer than my installed version).
After finding this thread, I became a little happier again...
I applied the fastboot oem ... thingy (hmm, what does it do exactly?).
Then I calibrated my battery, which seemed to work well, as it shows 99% now, which it didn't before.
And at the end I installed the fixmisc-update.zip as linked above.
Between each step I checked if the issue disappeared.
Nothing of those steps completely solved the problem.
However, when disconnecting from PC, the reboots don't appear anymore, so at least something has changed.
So, powlemann, ferreinf and others being successful with the steps above, which configurations do you use now?
Can you tell me which change solved the issue for you?
Do you use alpharev1.5 or 1.8 (and the later from which date) or none of them?
Did you install cwm3 again after solving the problem and did the problem re-appear?
Good News for you, hg42!
I am 99% sure you can fix the problem when first flashing AmonRA recovery and then do Mocados Usb Brick rickrolled.
Do you know how to flash a different recovery?
I fixed it with modaco's zip, that was very annoying!!
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
tommo123 said:
i ask as i updated my radio last night for the 1st time in aaages and the phone turns on etc as you'd expect. since then though (this morning) i've had random reboots. i've got recovery images of different roms and both do the same.
i tried a clean install of a new rom and it reboots while installing, i try to install again and this time it gets to the "press on the droid" option when it reboots again.
Click to expand...
Click to collapse
Weird..did u try flashing a different radio?
not yet. in work for a while longer. the only other thing i can see it being, is the kernels in the rom i'm using now, using too little voltage.
might try flashing a different kernel
I have had this problem before & as has been suggested a different radio did solve the problem. Hope it turns out something as simple for you.
As a last resort try wiping and flashing an RUU, that will replace the kernel, radio and rom
yea, had a thought on doing that too. grabbed 2 of em (not sure which i need) but today it's not rebooting
ok, somethings gone real wrong now. cant do anything more than go into fastboot. recovery causes a reboot with 7 vibrations on the boot screen and it wont go past it. i can go into fastboot/fastboot usb and that's it.
how do you flash a ruu now? i found a guide but it refers to downloading .zip images and putting em on an sdcard? i could only see .exe ruus
Just run the ruu exe while your phone is connected in fastboot. Do you have the ruu that was originally on the phone?
Sent from my HTC Desire using Tapatalk
trying it now. got the ruu downloaded. tried it before but got some funky errors
phones doing some funky stuff at the mo. if this works (i hope) then i can use unrevoked and then alpharev to get root/s-off later again yea?
ta mate
Yeah, you can do that.
Sent from my HTC Desire using Tapatalk
coolio.
worked. now booted up. wonder what the hell happened though!
Dunno but I guess you're relieved
Sent from my HTC Desire using Tapatalk
i am, but tried 2 pcs and my netbook, installed usb drivers off their site but just cant get unrevoked working for my desire.
off to try the old goldcard method
odd, even the goldcard tool didnt work. did a year or so ago when i 1st rooted. had to go old school on this thing.
edit
and after several tries, alpharev doesnt work
cant make the phone reboot when it needs to. worked last time with opendesire with no probs at all. no joy with oxygen though, or the default sense rom
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
tommo123 said:
ok, thanks to the forum, i've got opendesire installed now and i think somethings up. after an install (clean) it locked. hard. 3 finger salute didn't reboot the phone and had to pull the batt out (other roms caused reboots instead). i decided to take the sim out - and nothing. no more locks/reboots at all.
i'm gonna try the sim in another phone tonight and see what happens.
something very off with this phone.
Click to expand...
Click to collapse
I had this problem after I flashed a radio. I ended up sending it back to O2 due to a corrupt radio/cpu stack on the actual device.
I just tried to flash the new radio using CLockworkmod and it took about 2 seconds and then said complete. I didn't see the typical Radio installation screen.
So it rebooted and I successfully was able to get into CM7 Nightly 87 running GodMode. However, the radio appears to be jacked up. It still says I am running the previous one from 11.19. USB attach no longer works -- It see's the connection but immediately goes away. I flashed a new kernel (Tiamat 4.0.3), but same problem. USB charging does NOT work either, and neither does USB HBOOT.
I immediately restored by backup of nandroid, but I still have the same issue. I also had the old version of the radio on this device, so I flashed that, but it did the exact same thing.. took about 2 seconds and then said complete.
Can anyone make any recommendations on how to fix this? I go from 3g to 1xrtt to nothing and rinse and repeat. I can make calls, texts take a while to go through. I can receive some calls but some just keep ringing.
I'm at a loss.
Try flashing use the PC36IMG.zip method from the bootloader.
Download this and rename it to PC36IMG.zip. Place it on the root (top level, not in a folder) of your SDCARD and reboot the phone while holding vol down to get the bootloader. It should find the zip, load it, and then ask if you want to flash it.
You can do all of this on your computer, except the flashing part of course.
Found the link to the PC36IMG.zip radios in this thread, for reference.
Thanks.
I was able to perform the above and I also tried going back to 11.19. Trying to flash that radio is clockwork really messed this phone up. The radio totally does not work, nor does USB.
Anyone else have any suggestions on what happened here? I am going to set it back to factory defaults as well to see if it makes a difference.
Took phone to sprint. Amazingly enough, the USB port detached from the circuit board, so it was completely unrelated. New phone being shipped and here next week.
wtwagon said:
Thanks.
I was able to perform the above and I also tried going back to 11.19. Trying to flash that radio is clockwork really messed this phone up. The radio totally does not work, nor does USB.
Anyone else have any suggestions on what happened here? I am going to set it back to factory defaults as well to see if it makes a difference.
Click to expand...
Click to collapse
try:
fastboot oem enableqxdm 0
I say now is as good a time as any to make the switch to Amon and make your life easier
Sent from my EVO rocking Evervolv Gingerbread
I was running Leedroid on my Desire and all was fine.
I seen these Sense 2.1+3.0 ROMS and decided to give one a go.
I tried to get into recovery before doing anything to take a NAND Backup, but it just refused to go into recovery. I finally got it in there and tried to apply to update.zip but it kept saying something could not be found, I forgot what, and failed after 10 tries.
I booted mu phone up and I'd lost all my data. It's like the phone had been wiped.
I tried reseating the SD Card and checking it was all ok, but then I got stuck in a bootloop. In the mean time, my Alienware Laptop decided to die, followed by my backup Dell laptop! lol
I messed around for ages trying to get various things to work, but couldn't do it. In the end, I downloaded the old root method and flashed Cyanomod 7 which seemed to work and I got it booted, but I couldn't mount the SD card and it would rarely pick up that the USB was connected.
I then flashed AceSMod007 which also seemed to go well minus 2 things.
The first, Text messages seem to show my contacts picture, but also it only shows their Number rather than the contact name. This is VERY annoying and I can't find a way to resolve it.
The second issue, and possibly the most worrying is that it won't pick up USB connection AT ALL. This includes when it's plugged into the Wall to charge.
I tried the USB Brick fix, but that didn't work at all.
I shutdown the phone, removed the battery, plugged in the charger, inserted the battery and booted up the phone and it started charging, but as soon as I unplugged the charger and put it in again, same problem.
I'm currently trying another ROM to see if that resolves the issue, but I suspect that it won't tbh.
Has anyone came across this before and/or knows how to fix it?
Other things I've tried:
Wiping all data, cache and Battery data.
Using different USB cables
Thanks
UPDATE:
Flashing a different ROM didn't seem to resolve it.
Quick update.
I flashed Insertcoin rom onto the phone and it's resolved my text message issue.
Also, when I plugged the phone into the PC, it didn't give me any options for mount SD or anything like that, but said it was charging. However, an hour later and the battery had only gone down.
Since charging by USB has always been slow for me, I plugged in into the wall socket for an hour but it wouldn't pick up that I'd plugged it in. I turned the phone off and I got the LED to say it's charging.
Left it, then booted it up and still has the same battery level.
I don't expect it's the battery otherwise it would pick up fine when plugging into the PC.
Could be an usb brick:
http://forum.xda-developers.com/showthread.php?t=691639
Cheers mate, but as I mentioned, I've tried the USB Brick fix a couple of times and still experiencing the same issues.
Can you switch on blue tooth? Does it stay on?
Sent from my HTC Desire using XDA Premium App
Actually, no. Its says Turning On... Then just goes back to off.
you DO have USB-Brick
you gotta fix it
if S-OFF do:
fastboot oem enable qxdm 0
fastboot oem eraseconfig
if S-ON there are a few threads on xda on how-to do it, if you still get no USB-connectivity you just didnt do it right
good luck
Ah, I did try it a few times. I'll just keep trying then.
Cheers
Are you S-Off or S-On and are you still ROOTED?
This thread for USB Brick
See for my post here
if you are S-off or tried to flash a RUU and lost ROOT!
This thread has a flasher with built in USB Brick fix
I'd already followed the USB Brick guide and it didn't help.
Now, is I were to have missed the step that says to run '/data/flash_image misc /data/mtd0.img', I'd be a bit of a tit.
So let's just say that I tried the guide again and now I have full USB functionality back
I was going to S-OFF my phone, but I'll hopefully get a Sensation soon and I don't want to fubar anything in the mean time.
Thanks for the help and pointers though guys. It's nice to be a member of some forums that aren't full of people who want to cry at you for not understanding everything 100%.
Cheers again
just use the thanks button
glad we (or at least I) could help.
Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA
Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app
Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.
These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..
All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!