Related
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 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.
I am having a really weird problem with my HTC Desire
It wont charge although sometimes it does.
if I plug it into the mains it may charge but only up to a maximum of 21% and then whilst still plugged into the mains it will discharge (while it is discharging the orange led is on solid as if it is charging)
If the battery reaches 0% the phone stays on when plugged into the mains.
I have the original battery and a new one i bought off ebay about 3 months ago. I dont think its the batteries as the exact same fault is happening on both.
I have also tried 2 different mains charges and usb charging,
This all seemed to start after i s-offed the phone and installed the lastest ICS Sanvold 0.7 ROM (which i found a bit too unstable) so I installed CyanogenMod CM7 Official (this is when i noticed the battery charging problem). Thinking it might be ROM related i installed the Oxygen 2.3.2 ROM which is one i used to use a while ago but I am still getting the charging problem, so i guess its not that.
Anyone got any idea? i still like my desire but i cant go on much longer like this and might just have to splash the cash and get a new phone.
I think the only way i can get it to charge is just to leave it charging for hours or switch the phone off and charge it upm but again it never goes above 21%
I have done the reset battery stats in ClockworkMod
Im running
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
and
Revolutionary CWM v4.0.1.4
Any ideas?
Can you try a different usb cable? I had a similar problem with a damaged one where the connector was broken.
Get back to S-ON and install the official RUU for your phone. See if the issue persists.
That test would demonstrate whether it's a hardware or software issue, and from then on, you can make your own conclusion.
powercat_ said:
Get back to S-ON and install the official RUU for your phone. See if the issue persists.
That test would demonstrate whether it's a hardware or software issue, and from then on, you can make your own conclusion.
Click to expand...
Click to collapse
Do i need to go back to s-on before i can reload an offical RUU?
I just tried to run the official ruu there but it told me i need 30% battery but unfortunately i can only power the battery to 21%
You don't need to S ON, but that would be the most efficient way to get it back to "Default"
The RUU from within windows gives a battery error? Try extracting the rom.zip from it and do the PM99IMG.zip flashing. Don't quote me on this, but it may bypass that error.
http://forum.xda-developers.com/showthread.php?t=1275632
Section "[7]: RUU WITHOUT USB CONNECTION"
cheers
I managed to do what you mentioned above but all it did was downgrade the bootloader to s-on hboot 0.80.0000 , it failed on the rest ie downgrading to stock rom files etc
It wouldn't boot either but i did manage to get into recovery and flash a CM7 rom zip file i still had on the SD card, so i managed to get that on and the phone booted.
Is there anyway i can go back to stock using Recovery?
In the RUU Stock Rom.zip file there are loads of .img files, can i manually flash these somehow?
My phone is now up to 24% but wont go any higher
Yeah those .img files can be loaded with fastboot
"fastboot flash system system.img"
then do a delete user data from the recovery..
did you try another battery by the way?
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!
So last night I unlocked the bootloader for my HTC One X. I wanted to get CM10.1 Nightly builds onto my phone, and was able to get all the way to where I have CWM 5.8.4.0 and even installed CM10.1 Nightly release. The problem at the time was that when I rebooted the phone it would become stuck at the bootscreen with the "Quietly Brilliant" quote. I tried everything from there to get CM10.1 working based on what I found around other threads and forums.
At one point the battery started running low and the phone stated that the battery was too low to perform fastboot commands. I thought I was in the clear as forums stated that as long as you have CWM on your phone then you can charge it back to full. I turned off my phone and plug in the wall charger and the red indicator light turned on a solid red.
This morning when I woke up, the red indicator wasn't on so I tried turning it on and nothing happened. I held down the volume button and pressed it, held down power for a minute...nothing seemed to work. I tried plugging my phone into my pc and it made that sound where the computer recognizes a new device and then made the sound that a device has been disconnected shortly after. This time though, the red indicator turned on but was blinking. I check other forums on how to fix this and all of them say to either:
1. Let the phone charge until the red light is solid
2. Hold down the volume button and then click power to boot into recovery.
The problem with that was the first option didn't happen, at a certain point the red light will just turn off. The 2nd option yielded nothing as I can't turn my phone on...
I'm seriously hoping I didn't just brick my phone and am hoping someone out there has a solution to the problem I'm facing.
Please and thank you!
***UPDATE***::: I got it to charge just enough to power on back to the bootloader using a Duracell external battery pack. Stupid me decided to relock the phone and go for the RUU when I clearly didn't have 30% battery life. I ended up looking around forums until I found a fix for that located here: (http://forum.xda-developers.com/showthread.php?t=1658084)
Using that method my battery maxed at 3665mV and I had just enough power to unlock the phone again and then reflash cwm 5.8.4.0 just for safety measures. Now I have the phone booted into the recovery main screen and plugged it into my ac charger. However, there's no LED indicator and I'm not sure if the phone is even charging at this point. Unless someone can help assure me that it is actually charging then I will wait about 2 hours before plugging it back into my pc and checking the power variable. Hopefully this all works out...
***UPDATE 2***::: This is just leading to more frustration. I proceeded with the following tutorial http://forum.xda-developers.com/showthread.php?t=1859714 and got to where I start the RUU exe. Unfortunately for me I ran into a "155: Unknown Error" and I tried the following RUU's: (3.14.707.24), (3.14.401.31) first. My phone code is (3.14.707.24) so I wasn't sure why it wasn't working. I read another thread http://forum.xda-developers.com/showthread.php?t=1660642 that said to try either (1.29.401.11) or (1.29.401.7). Both of these RUU's gave me either a "USB connectivity error" or a "Main battery is below 30%"
Now I wasn't sure if my phone had actually lowered that much since I started working on it, but I checked the mV value and it gave me 4030 which I thought was more than 30%. I don't believe it's the USB cause I can still get to the 155 error for the former RUU's. I just went ahead and started charging the phone again and will try again soon. This is really ticking me off...
***UPDATE 3***::: NOPE! I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.
***FINAL UPDATE***::: Mission Accomplished!!! I'm glad to say that I got my phone running back on stock and am not holding a brick in my hands. How I fixed it? This morning I came across this thread here http://forum.xda-developers.com/wiki/HTC_One_X#Disaster_Recovery_-_what_to_do_in_the_event_of_a_bad_flash and I noticed something new in the instructions. It said to run fastboot when executing the RUU, and interestingly enough when I got to the 2nd to the last step the version said "updating from 3.14.707.24 to 3.14.707.24" Before, I ran the RUU while on the "Quietly Brilliant" splash screen since the tutorial I was following never mentioned having to run the RUU while in fastboot. This would probably also explain why, when I ran the RUU in the splash screen, it gave me the (3.14.401.31) version number instead of the correct (3.14.707.24) version.
Well, it's been a messed up roller coaster of a ride and I will try my luck with flashing another rom later this week. I hope I never have to revisit another HOX troubleshooting thread for the remainder of the time that I use this phone. Thanks to all that assisted in my endeavors.
Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
http://d-h.st/487
Sent from my HTC One X using xda app-developers app
davidk-il said:
Hey,
Try to boot into recovery when charger is plugged in hold power + vol up buttons and wait.
If that doesn't work, there is a script that charges the phone by looping ot on fastboot.
After you manage tocharge the phone boot into recovery and install cm 10.1 vendor installer :
Click to expand...
Click to collapse
I already tried the method you mentioned and that didn't work. The problem with the script is that I assume I would need to have the phone charged somehow and then turn it on. I can't charge the phone at this point so I'm lost...
Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app
The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.
davidk-il said:
Did yoy actually try to boot into boot loader? Power + vol down
As far as i remember, charge script works whe on bootloader(please correct me if im wrong guys)
Im using twrp recovery and it charges just fine for me.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, I have tried that too...it didn't work =(
At this point the phone just won't charge properly.
TToivanen said:
The one and only solution to this is to plug it in to an AC charger and let it charge over night. It doesn't matter if the led is enabled or not.
Click to expand...
Click to collapse
I plugged it into the AC charger last night and this morning is when the problem started. I'm starting to think I should have left the phone on in the recovery screen and charged it that way.
When I try plugging the phone into the AC charger now there's no red led indicator, but there's one when I plug it into the pc (even though the flashing light disappears after 5 minutes or so).
Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app
davidk-il said:
Hey,
Did you manage to get the phone charged?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
So last night I checked the millivolt of my battery after charging it through recovery for about 2 hours and it was at roughly 3810mV. I'm not sure what the max mV for HOX is but I let it charge overnight again. This morning I checked and it was at around 4180mV. I'm not very knowledgable on how to convert the 1800mah value over to how many mV it would equal to. I wasn't sure if this was the max so I left it charging and will get back to it once I get home.
~4200mV is equal to 100% charge.
TToivanen said:
~4200mV is equal to 100% charge.
Click to expand...
Click to collapse
Good to know! I'll give the RUU a try when I get the chance later today and post an update. Thanks!
I flashed TWRP in replacement of clockwork just cause another thread said it's supported rather than just a port like CWM. Anyways, I've tried several other RUU's and they all give me the 30% Low Battery nonsense. I have tried: (1.28.728.9), (1.29.728.12), (1.29.707.11) but I didn't expect these to work since the previous thread menioned how I can't go backwards. Right now I'm completely lost on what I should do. RUU was supposed to be the last resort, but even this is failing me. FYI: My device's CID: HTC_044 and version as mentioned before: 3.14.707.24 Don't know if that will help but if someone out there can tell me my next steps then it would be much appreciated.
Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights
Mr Hofs said:
Here is your ruu
http://bugsylawson.com/index.php/fi...24-radio-5120416229-release-296434-signedexe/
Relock the bootloader
Fastboot oem lock
Then run the ruu WITH admin rights
Click to expand...
Click to collapse
If I'm not mistaken, that's the first one I used last night along with the same steps. It gave me the "155 Unknown Error" and I proceeded to trying other RUU's. I will try again when I get home, where I can only hope it works for some odd reason. Stay tuned.
Well its the only one that should work. A newer one in not out. And this one matches the main version 100%
Mr Hofs said:
Well its the only one that should work. A newer one in not out. And this one matches the main version 100%
Click to expand...
Click to collapse
I think what I forgot to mention in the updates was that I found something strange. During the RUU steps, after I clicked update, it said:
Upgrading from 3.14.401.31 to 3.14.707.24 which I thought was really strange since 401 indicates Europe version. Is this something to note?
It was the next steps that lead me to the 155 Unknown Error
The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here
Mr Hofs said:
The outcome of
Fastboot getvar version-main
That is the number that must match the ruu ....if its 3.14.401 then you have the wrong ruu. Do the command first and check the number/post the outcome here
Click to expand...
Click to collapse
Here's the thing, when I run the command to get the version I receive: (3.14.707.24)
However, when I run the 3.14.707.24 RUU it leads me to a page where it says I'm going from 3.14.401.31 to image: 3.14.707.24
That seemed very odd to me. Can you help explain why this is?
Hmm no i can't ! That's very strange.....try the 707 ruu again. Otherwise try the 401 ruu ?
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Don't exactly know what to think about that
Is there a solution for Droid DNA?
I tried rooting it last night. It was successful. The last step was to reboot according to JCase's method. It hasnt restarted since then. No battery indicator as if its not at all plugged in. "YES IT WAS ON CHARGING THE WHOLE NIGHT". It wont even show me the boot screen. "YES, I PRESSED THE POWER AND VOL BUTTON FOR MORE THAN A MIN".
Any help would be appreciated.
Thank You