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!!
Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.
I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.
Try reinstall usb drivers, rsdlite, different usb port, and different pc.
@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.
If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.
im having the same issue, did you solve it?
im having the same issue, did you solve it?
try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...
You have tried the McGyver-trick?
I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.
Ok. At least you have the time now to enjoy your sunny weather in Brazil...
RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help
First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx
Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again
i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan
hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..
I just rooted my HTC Desire and installed CM7 on it (loved it on my HTC Legend). But suddenly today, after I turned Wifi on, it started rebooting all the time, couldn't do anything to stop it. I thought "Hey, there was the radio flash thing in the tutorial that I didn't do yet, I'll try that out" so I flashed the radio. Then I chose reboot system, but it just booted to a logo with an android coming out of a trash can, and looked kinda stuck there. So I took out the battery and plugged back in. Now if I try to turn it on, it'll just vibrate 7 times - no picture or anything. Also there's no LED when I plug it to the charger.
I had those 7 vibrates too.
Happened after i flashed the cm7 hboot over my stock hboot while trying to enter recovery. After i re-flashed my recovery using fastboot, everything worked again. What happens if you try to power up while holding down vol- ? Did you use fastboot or your phones recovery mode to install the radio?
I am not able to start in recovery or anything. I tried vol. down + power and back + power and no matter what I try, it just vibrates 7 times. I used the recovery mode to install the radio.
You could try to connect your phone via usb and check if fastboot discovers your device. If yes, flash hboot and recovery using fastboot. If not, well... i dont have a clue. Sorry :/
Computer discovers nothing when I plug in the phone.
Bad news when u pulled battery u interrupt the process n u now have a bricked device I would b very surprised if u managed to do anything
Pulling battery when doin a radio update is a BIG NO NO I'm sorry but ur stuck with a 400+ mirror now
Please look at this link
http://www.google.co.uk/m/search?site=images&client=ms-android-htc&hl=en&gl=uk&source=mog&aq=&oq=&aqi=&fkt=&fsdt=&cqt=&rst=&htf=&his=&maction=&q=android+radio+update#i=95
If that the image u saw when u pulled battery ur defo screwed
The Best Things Come To Those Who Wait
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
U need to copy the link for some reason its not showing up
Pm the link u have
The Best Things Come To Those Who Wait
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
inrego
yes the image u just sent me is correct
the image showing would of ment it was installing the radio and because u pulled battery u have corrupt the flash and unfortuntly bricked ur device
i will look for a solution on the net but im not sure if ill find anythink sorrry
Inrego said:
Your link doesn't work.. I found a picture of what was showing when I unplugged the battery, but I'm not allowed to post links to other sites on these forums yet.
Click to expand...
Click to collapse
heres a few thread about some pulling battery on radio flash
http://android.modaco.com/content/g...m/304368/can-the-nexus-one-be-bricked/#entry0
http://android.modaco.com/content/h...50/help-cannot-turn-on-after-flash-new-radio/
i cant find anythink about fixin the issue sorry
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
all depends on if ur on warranty if u have receipt and warranty then all is ok with out them u stuck basically
sorry couldn't help more hopefully lesson learnt playing with radio is risky business
Yea got warranty and reciept and all that, so np there
Inrego said:
Yea got warranty and reciept and all that, so np there
Click to expand...
Click to collapse
nice one then just make up a bull**** reason ok well hope u get a replacement
Wait a minute...
Inrego said:
Well thanks alot for trying. At least it seems like it shouldn't be too hard to get a replacement unit..
Click to expand...
Click to collapse
For the record to help some of you out who ended up here Googling: I had a similar issue. My HTC Desire SV did not boot, and when charging, only had an orange flashing light, and the phone vibrated 7 times. I did 2 things that got it back up:
1) left the phone off for say 10 minutes (I read about overheating issues in general, although the phone did not feel hot).
2) removed the battery for a couple of minutes.
VERY IMPORTANT: for step 2: make sure to have the battery removed long enough to drain internal charge. I removed and installed the battery in a second or so at first, and still the phone did not boot. After leaving out the battery long enough, it booted again. It appears to me that the issue in my case was a rather big internal charge capacity which kept internal state (memory and/or CPU?) from booting. Hope this helps...
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
WasifSal said:
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
Click to expand...
Click to collapse
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Kevin Ma said:
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I Re-Locked the phone
Will that flash the Recovery?
WasifSal said:
I Re-Locked the phone
Will that flash the Recovery?
Click to expand...
Click to collapse
unlock the phone again. flash the latest recovery. then go into fastboot. fastboot erase cache , then flash the kernel, go into recovery flash superwipe, flash rom and reboot and job done..
before you do all that though backup your current rom
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
WasifSal said:
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
Click to expand...
Click to collapse
well then leave it overnight to charge..see what happens in the morning then
Goku80 said:
well then leave it overnight to charge..see what happens in the morning then
Click to expand...
Click to collapse
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
WasifSal said:
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
Click to expand...
Click to collapse
man i am sorry then i wish i had more knowledge to give you help. hopefully someone else with more experience and knowledge can come and advise you different. just never had that issue you see.
if you say you can not go into bootloader or recovery then it does not sound right...maybe take it back to retailer or something might be the best option if no one can help out
have you tried the power button with the volume button down for ten seconds to see if the phone reboots?
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
WasifSal said:
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
Click to expand...
Click to collapse
try what i said to you in my last sentence mate
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
PatsFan1286 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
OK so I managed to get the phone UNLOCKED (Finally)
Now when I flash the 5.8.4.0 recovery it says
"unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'"
So i booted the phone into the recovery mode instead of flashing.
I am finally getting somewhere but how do i know it's charging there? I don't see the red LED turn ON :/
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
WasifSal said:
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
Click to expand...
Click to collapse
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
rayford85 said:
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Woah! That's spot on... I was surely gonna mess up my phone if i had done the RUU.
Its charging while the screen is off as we speak. But I think there is a problem with the charge thingy.
Its off and charging.. but sooner or later it turns off due to low battery (IM SUCH A NOOB I DNT KNW IF THE LOW BATTERY IS CAUSING THE PROBLEM)
I'll wait for it to charge again though and connect to the PC again
In the meanwhile can u answer me something regarding this
1. Does the red light turns on while charging in CWM 5.8.4.0
2. Does the mount USB Drive works? :'( Cuz when the phone was working fine. The mount USB Drive failed and gave an error of having a "lunfile missing" :/
Both of your questions can be found :
http://forum.xda-developers.com/showthread.php?t=1594819
i flashed the boot.img like ray said. then i turned the phone to recovery mode it went there and then mounted the usb it worked etc.
but I didnt flashed just yet.. i wanted it to be charged so i turned it off.. I am again getting that "not turning off" habit again
OH God what am i doing wrong here
PLEASE!! Someone help me! It's got that nasty thing that gets HTC Queitly Brilliant thing again.. It's charging but won't go into the recovery mode now!!!!!!!!!!!!!!!
How can I charge my phone while on Relocked Bootloader. I need help u guys!
Hello there,
I have noticed a strange thing with the HTC One X, when i charge my phone although i turn it off before i plug it into the power outlet it always turns back on. Am i doing something wrong? I can't find a way to charge my phone in a turned off status and it's the first time i have come across with such a problem. Could you please help me out? I use the factory charger that came with the phone device.(I am on a stock ROM, never used a custom ROM before and i have smart screen pro for notifications)
Thank you in advance,
Dinos
dinothenino said:
Hello there,
I have noticed a strange thing with the HTC One X, when i charge my phone although i turn it off before i plug it into the power outlet it always turns back on. Am i doing something wrong? I can't find a way to charge my phone in a turned off status and it's the first time i have come across with such a problem. Could you please help me out? I use the factory charger that came with the phone device.(I am on a stock ROM, never used a custom ROM before and i have smart screen pro for notifications)
Thank you in advance,
Dinos
Click to expand...
Click to collapse
settings developer tools untick stay awake whilst charging done
withymanq said:
settings developer tools untick stay awake whilst charging done
Click to expand...
Click to collapse
I have already done that but still no change,any ideas?
Okay finally found it, thanks to the xda search capability, the problem was the clockwork mod, after i flashed another recovery, the TWRP to be exact, the problem is solved. Now there is another issue, the phone still turns on but this time it boots to recovery mode. After some search, there is also a bug in TWRP which turns the phone on although previously it was turned off. I am using TWRP 2.2.2.0 and as for the CWM recovery i was using 5.8.4.0. I hope the guys at TWRP who did a great job by the way will try to fix this problem. I hope this info will help some people in the future if they happen to have the same problem as i did.