For solution see this
Hi guys...I've got Problem...
This is What it is and what I've Tried so far...
I've posted this Problem at may places but didn't got results..
That's why I am ceating a new Thread..Also there is no Q & A Thread for this..which have good info
Here is What i tried.. and still the NOT CHARGING/LATE CHARGING and HEAVY BATTERY DRAIN PROBLEM..
1. Firstly I had runnymede from seb15 AiOv2.2 installed..Working Perfectly..
(See my signature for my phone's every single detail)
2. I used 4ext recovery..(before cwm).. I go to the recovery.. took backup..done perfectly..
Than rebooted.."STUCKED ON BOOTSCREEN"
"I pulled out the battery ..
Restarted with power+volume down button..
4ext recovery started after long delay..
msg:
"Error mounting your sdcard
Please check your sdcard's fat32 partition for errors"
"Error mounting your sdcard
Please check your sdcard's fat32 partition for errors"
2times...
at the table it is showing as
sacard fat32(fs) null(size) B(Free)....
I removed sd card..
repartitioned by gpartedlive..
my sdcard is 8gb sandisk..partition are 1gb ext4...remaining fat32(Both Primary)
Reinserted sd card..
again rebooted in recovery..
again same message"
This was the starting of the problem..
Now Waht i did is
1.connected to PC and in cmd typed this
adb devices
fastboot flash recovery recoveryCWM.img
fastboot reboot-bootloader
fastboot erase cache
fastboot oem enableqxdm 0
and sussefully done..
2. In fastboot
again first step and added
fastboot eraseconfig
rebooted..
3. got SD card mounted
4. Flashed CynogenMod7.1.0(Worked perfectly..even the battery was charging good...everything Normal)
5. I rewiped everything and flashed runnymede AiOv2.2 again..
Here the problem started of Battery Drain and Not Charging.
6. The Battery was NOT charging firstly...Than started charging 5mins after plugged in..
7. Charging is 1% per 15mins..(Which was almost10% per 15mins)
8. Battery Drain almost 10% in just 15mins..
Now to solve this I searched xda and googled.. foind something and did following..
reflsahed the hboot.
By first downgrading and than upgrading to cm7r2..
3.In fastboot Reflashed recovery CWM 2.5.0.7 than upgraded to 4.xxxx(ext4 and 3 supportable)
Again installed runnymede AiOv2.2 again..SAME RESULTS..
Tried Revolution v2.0 ... SAME RESULTS(the Battery thing..explained above)
Now what you guys suggest me to do NOW... to get my desire in NORMAL CONDITIONS
Huge Thanks for "ckpv5" for the guidence for solving "ERROR IN MOUNTING SDCARD"
and lot more people on xda which i searched threads..
I again NEED HELP!!!
One more thing ...
The time I was re flashing the hboot.... I pulled out the battery..the phone was connected with USB... Kit was still on...by the power from USB only...means the power was not going through battery but directly....
Can this be the cause of late charging problem....and the battery drain...
it happened with your phone???? That you forgot to pull out the USB simultaneously pulled the battery out....
By the way I've tried changing kennels... No luck stool the same problem
Thanks for your kind help
tried a different battery? only logical explanation...
have you tried charging the phone while switched off? what happens then?
also if this is a software issue did you make sure to do a full wipe before you flashed a new ROM? (from mounts 7 storage)
bortak said:
tried a different battery? only logical explanation...
have you tried charging the phone while switched off? what happens then?
also if this is a software issue did you make sure to do a full wipe before you flashed a new ROM? (from mounts 7 storage)
Click to expand...
Click to collapse
I've tried it charging in switch off mode..but.. same result..
Try changing the ROM.. same Result... as u can see above I've tried almost everything....
dont expect any1 to help of you write post the way you just did.
well what happens seems to me like:
-you had USB brick (batt drain, charging issues, no USB connectivity)
-you fixed it with 'fastboot oem enable qxdm 0' and 'fastboot oem eraseconfig'
-you flashed a (corrupted?) rom file again, and got USB bricked once again.
so just do fastboot cmds once again and you should be good.
however if i didnt understand you correctly, blame yourself for it, cause i dont feel like reading the 1st post ever again.
over and out.
dzumagos said:
over and out.
Click to expand...
Click to collapse
What this means is "call me back and don't call me" LOL
Does Bluetooth work (ie. stay on)? If not then it's a USB brick. And I'm with dzumardgos, I almost didn't bother spending some of my hard earned time on you.
Note also that loss of access and repair of the SD card issue is something completely different to charging and PC connectivity issues (USB brick).
Will see you soon with the solution.
Sent from my HTC Desire using XDA App
What are the possibilities that a ROM can be corrupted..Please mention..
By the way I was using this ROM(the v2.2) from i think 10 days..
Is it possible that a ROM which is corrupted would do this after that much time period..
Related
Im Not sure exactly what happened here, I've been flashing for nearly a year now a variety of ROMs, and this last time seems to have been fatal.
I went from a custom ROM, did the routine task29 before loading a new ROM; the task29 completed, I returned to bootloader to load the new ROM, and it wouldnt load past 0%. I tried to task29 again, and then that wouldnt load past 0%.
I've since tried mtty and doing set 14 0, task 29, task 8, which restarts it, but now I can no longer manually power it on by pressing hardware keys anymore.. I have to leave it plugged into USB and wait for it to auto-turn itself on after about 5 mins, it loads to "Touch Pro 2" screen, then I can press the little reset button and hold down vol key to get to bootloader. However, it only lasts there about 10 second before turning itself off again, showing the orange light like it's charging. Sometimes I am quick enough to get any ROM or manual HardSPL to try and load at bootloader, but it still sits at 0%.
I have also tried to load a ROM from the SD card, which seems maybe the only option how; however, I have heard you need at least 50% battery, and I have no way to see how much battery I have left, or whether its even charging.
I tried to install from SD yesterday, and got to the gray "Loading" screen, and it just sat there.. I wasnt sure how long it normally takes at that screen, so i powered it off, checked my SD card and now that shows as corrupt and cannot even be formatted... pretty much burnt out as well now, it seems.
Did I do the SD card installation right, using my RHODIMG.nbh file at the root? How long does it normally sit at the Loading screen? I have an 8GB mini-sd I could load from, but I dont want it to burn out as well..
Are there any other options?? I cant even send back to warranty, I dont think, because I cant even load back on the stock ROM or relock it...
Moved to Rhodium General forum because not a cooking problem.
Someone please help... I just tried again to load stock ROM from SD card, as well as custom, it just sits on "Loading..." on the gray screen...
Just for the record, I can get into bootloader, but as of now nothing will load past 0%.
I tried mtty set 14 0, task 29 and task 8, no luck...
I'm certainly not an expert, but just thought I'd throw out a few ideas.
Have you tried charging the phone on the wall charger (not USB) for several hours (like overnight). The fact the phone is powering off by itself suggests that you may be low on battery. USB won't charge the battery sufficiently in some cases of extreme low battery. Try another battery or charge if possible.
Having the RHODIMG.nbh file in the root of your micro-SD card is the correct way to boot from the card. Normally, it doesn't matter if there are other files on the card. But formatting it can't hurt at this point.
Only other thing I can think of, is try to re-flash the radio first, and see it that helps. That's all I can offer up at this point. I was going to suggest trying to flash the stock ROM, but you've already thought of that in your latest post.
Good luck!
redpoint73 said:
I'm certainly not an expert, but just thought I'd throw out a few ideas.
Have you tried charging the phone on the wall charger (not USB) for several hours (like overnight). The fact the phone is powering off by itself suggests that you may be low on battery. USB won't charge the battery sufficiently in some cases of extreme low battery. Try another battery or charge if possible.
Having the RHODIMG.nbh file in the root of your micro-SD card is the correct way to boot from the card. Normally, it doesn't matter if there are other files on the card. But formatting it can't hurt at this point.
Only other thing I can think of, is try to re-flash the radio first, and see it that helps. That's all I can offer up at this point. I was going to suggest trying to flash the stock ROM, but you've already thought of that in your latest post.
Good luck!
Click to expand...
Click to collapse
Thanks for the response; I just tried that (flashing the radio) and it didnt work. Ive also tried flashing a variety of ROMs and nbh files over SD;
It always seems to freeze at the gray "Loading..." screen and get no further.
venomshot629 said:
Thanks for the response; I just tried that (flashing the radio) and it didnt work. Ive also tried flashing a variety of ROMs and nbh files over SD;
It always seems to freeze at the gray "Loading..." screen and get no further.
Click to expand...
Click to collapse
Try using a different USB cable to flash via the PC. If you try the SD route again, some users report that using a NON-SDHC card solves the flashing problem. Give that a shot and then report back. I can't really think of anything else offhand.
cajunflavoredbob said:
Try using a different USB cable to flash via the PC. If you try the SD route again, some users report that using a NON-SDHC card solves the flashing problem. Give that a shot and then report back. I can't really think of anything else offhand.
Click to expand...
Click to collapse
I have tried again using a 512 MB SD card and it still hangs at the "Loading..." screen.
Also, when flashing with any USB cable, I am still stuck at just 0%.. I can get into the bootloader, etc, but it just refuses to flash any image..
Yes, this is one n00b 1st. post... but bare with me, as I (think) I have done all the right things.
The Issue:
I flashed the LeeDrOiD HD V3.3.3-Port-R5 A2SD++ to a HTC Desire (Bravo, Root, S-off, Full Wipe).
It is fast and seems to work really well, but there is one major problem: The phone do not recognized USB connection.
I plug the AC charger in, and it takes 2-5 min for the phone to start charging, and the phone seems to think of it as USB charging, not AC...
Plucking the phone to the PC gives error form windows about "unknown USB device", and the phone newer seems to register the PC: It just go to USB charging, after 2-5 min.
The first flashing of the LeeDroid rom caused a USB Brick, that FastBoot "rebootRUU" and "enableqxdm 0" fixed.
Don't know if that have anything to say.
Yes, I guess n00b problem, and I guess all is explained 117 times.
But please... point me to the right threads.
You have what's known as a USB brick. Basically, you had two problems. Your first was that your phone did not recognise that there was an SD card inserted, you have now fixed that. Unfortunately however you do now have a USB brick, which gives exactly the problems you describe. Do some searching on the forum, there's several threads explaining how to fix this.
try this thread
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
Thanks a bunch!
I vent to that same thread earlier, when the SD card did not work, but did not find a fix fore it there.
It is all starting to make sense now.
I'l try flowing the guide and, and see if I can make it on my own again.
Thanks Again.
Both SD and USB Un-Bricked now.
Happy Happy!
Thanks.
I've been there and done it. I had EXACTLY the same issues as yourself and on fixing the SD card issue I thought brilliant, "I am legend".... It was only after trying to connect the phone to the PC that I discovered I was not. I was only half way to fixing my problems. I did however make a text file detailing what I did in case it ever happened again and here it is (you will need an image file however which can be got from the thread linked above) :-
============================================
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
Before trying the stuff below, try to run this command first - fastboot oem eraseconfig
I had already done the below which didn't work then running that it suddenly did work so try it first, if no joy do the below and if still no joy then try the command again.
ALSO FOUND THIS TO TRY -
So I download the HTC hboot stock partition, flashing through fastboot command, and do 'fastboot flash misc mtd0.img' reboot... and ta...da ... my USB connection fix, Bluetooth is working too, testing with some other rom, and all fine ...
AND -
1.download recovery *.img file.
2.put it in androidsdk\tools folder.
3.boot in to fastboot by pressing back button and power button together.
4.run :-
fastboot flash recovery *.img
===================================================
EDIT: Ah you fixed it whilst I was replying (was on a phone call). Nice one fella.
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Hi! Have you tried to leave the phone without the battery for 1-2 minutes and tried a reboot?
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
bortak said:
Take the battery out, unplug it, hold power for 30 secs to get any remaining juice out.
Leave the phone for 24 hours (with battery out etc.)
Stick the battery back in, try again.
Click to expand...
Click to collapse
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Ryther said:
What would be the cause for such a behaviour? I'm a little curious (and relatively new to the android scene)!
OT: I've took a look to your troubleshooting guide, good job indeed!
Click to expand...
Click to collapse
Really no idea, and what I told you to do is not guarantee'd to work, it may help though.
And thanks, it sure has cut down repeat posts about repeat problems by about 90% here.
Thank you all for your replies.
I did leave the phone without battery for several days - same problem.
But I did not try to press the pwr for 30 secs without battery. I will try when I get home.
I tried following:
- take battery out and reset it. then hold vol dwn + pwr -> Nothing
- take battery out and reset it. then hold back + pwr -> Nothing
By the way, if I press pwr to turn phone on, it does not come up, but leaving it for a while it gets warmer.
It looks like the CPU is trapped in a loop and running at full speed!
Could a riff box repair it?
do a battery pull then hold back & power. That usually boots into fastboot mode, see if the phone is recognised with
Code:
fastboot devices
if it is run the 2.3 RUU.
Dear bortak
I have tried. It does not enter fastboot.
command "fastboot devices" returns blank.
command "adb devices" returns empty list
command "adb reboot-bootloader" givers "device not found error"
RUU gives usb error.
have you installed the proper drivers on your pc for it to connect with the phone?
If so, when you attempt boot into fastboot and connect your phone through USB do you get the "device connected to windows" sound, like when plugging in and external driver or usb?
Because if not even that sound gets played it most likely means that your phone isn't even able to get into fastboot or hboot...
windows does NOT play any "device connected to windows" sound at all.
I have all drivers installed correct on my windows 7. My other HTC devices (desire s, wildfire, wildfire s) connects correctly to the PC and I can get the serial numbers of them using "fastboot devices" command.
Now on work, I tried a windows XP - same problem no connection - no sound.
This desire does NOT get into hboot nor fastboot. I think taht the "bootsector" is correpted.
I even used a Goldcard (made thru wildfire) - not working either.
So fixing it thru USB the normal way is not working.
Is there any way to force the device to boot up from SD card??
I have several backups of the phone system on my 8GB SD card.
You have to find a way to re-flash the hboot. That causes the blank screen display. May be a bad hboot install or something :0 Unless you have S-off and can be detected in fastboot, you can reflash hboot, otherwise you will have to try the blind flash method using PB.IMG. Best I could think of.
Sent from my PB99400 using XDA
@Jonicraw, thank you for your suggestion.
Where to get the HBOOT PBxxxx.IMG for this desire?
And how to flash it blindly, since I have black screen and no connection to PC.
AbuTarboosh said:
Hi All
First thanks for a very good and informative forum.
======================
This was my first post/question and was placed in wrong section. Now it replaced. - Sorry for that!
======================
Information:
HTC Desire
rooted
S-OFF
EXT4 recovery
rom: runnymix...
sd-card partioned(by EXT4 recovery)
AMOLED
Motherboard and ribboncable was changed one month ago on warranty.
Symtpoms:
- Charges normally: orange charging/green full charge. Flashing orange/green without battery
- Cant NOT boot at all
- cant get into bootloader vol down + pwr
- can not be detected buy PC
- Battery inserted and charging: When pressing power to turn on => charge light goes off - and nothing happens. Leaving it in this condition for a while: the phone(mainboard) gets warm.
The phone was functioning perfectly before my son installed bootmanager app. He uninstalled the bootmanager app again without making any changes to the phone. It took long time (like freezing), so he did pull the battery out!!
Any help? Tried a lot of searches, none of them was as my problem.
Thank you
Click to expand...
Click to collapse
im also same problem wont to solution
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Had the same problem. Mine could not charge at all and could not enter fastboot/recovery. Send the phone to HTC. I got back the phone with a new battery.
asad_sah said:
im also same problem wont to solution
Click to expand...
Click to collapse
Same s**t for me ... I tried everything you try and no results !
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
AbuTarboosh said:
Come on experts ... somebody must have knowledge to fix this common problem.
What about an "Unbrick Jig" like the one for samsulng galaxy:
MICRO USB JIG DOWNLOAD MODE DONGLE FOR SAMSUNG GALAXY S2/I9100/I9000
This device may force the cpu to boot from usb, getting it in "boot flashing" condition.
Click to expand...
Click to collapse
No such things exists for the Desire.
Tell me what state the phone is currently in now?
Yet no solution for this problem...
STATUS for my device is:
Problem solved by changing the motherboard.
I hoped we could find a good solution for this.
I have the same problem but my phone is already on it's 3rd motherboard. I suspect the battery might be the problem but cannot get any answer as to what the voltages should be. I have already submitted a post headed Battery Voltage but it hasn't attracted a reply.
Hi there,
I got the same problem.
Can I send the phone to HTC even if I have rooted it? I also opened it a few weeks ago to replace the broken touchscreen. Do I still have warranty?
Greetings
Mika
hey there!
Ok so I got this problem. My phone felt to the floor like 2 weeks ago and the screen got crashed, everything else works normally, touch is ok, screen is ok, just glass is broken, after 2 days I downloaded some dota apps and it suddenly started rebooting and crashing:
By this I mean, apps stopped working and lots of pop-up messages appeared, after some reboots It stopped turning on, so I decided to root it and installed a custom ROM the one from mike, Android Revolution, this was last week, this weekend it worked fine until sunday when it got bricked because of an outdated recovery from clockwork. I managed to solve this with some help from you guys, but now again.
I flashed the android monday again with same version, it was working well until yesterday at night, it started showing some whatsapp stopped working stuff again, i rebooted it and now a bunch of window errors... reboot it again and well... no luck it stayed in the Android loading window.
After this I was trying to install the stock version ROM from mike also, and that's when it got worse.
Flashed boot and recovery OK, then rebooted and when I tried to install the ROM it just won't let me, failed unknown error, failed remote : 00030000, and other messages, now when I try to flash the recovery again it says low battery, and when I try the script to charge it it won't work, FAILED remote: unknown reason.
What can I do guys? =S (Sorry for the long post, I just don't know what could it be, and I wish by giving that much information someone can find out the reason, contacted HTC and they said it has no guarantee since I rooted and the glass is broken)
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
faiz02 said:
can you still access fastboot??
if you can.. then flash the latest CWM 5.8.4.0
It will allow the phone to charge.
Click to expand...
Click to collapse
I can but there is some weird reason that won't let me do any flash, either low battery and when it gets charged a bit (because it may charge enough sometimes) it says FAILED remote:00030000 or unknown reason.
Don't know what it could be.
I ran into the exact same problem, the charger script does not help me too (low power on usb port of pc).
Thats how I fix this:
1) disconnect original charger, let's phone die. or use shutdown in fastboot.
2) connect original charger, and wait while phone powered up (He himself off as he does not have enough battery power.). disconnect charger.
3) vol.down and hold power,choose fastboot
4) connect charger
5) choose reboot bootloader (phone will reboot in fastboot)
6) choose reboot bootloader (phone will reboot in fastboot)
7) choose reboot bootloader (phone will reboot in fastboot)
....(do it fast)
249) choose reboot bootloader (phone will reboot in fastboot)
250) choose reboot bootloader (phone will reboot in fastboot)
251) disconnect charger, choose shutdown.
252) go to PC
253) vol down, power up
254) choose fastboot
255) flash the custom recovery with power supply support
256) flash custom kernel
257) don't disconnect USB!
258) fastboot / reboot bootloader / hboot
259) recovery
260) mount USB storage
261) drop zip of custom flash to the phone
262) unmount
263) advanced / restart recovery
264) flash the zip of rom
265) restart phone and dont disturb it, at 30 minute, let hi charge.
266) disconnect USB and connect original charger (1A)
267) Have fun!
It worked but bad news... now as always I am getting the message windows, with some weird apps.
First it was htc.com.bgp or something which I found it was the weather, then whatsapp, then Personalize, pretty much everything I open stops working after a while, what can I do? This was the exact reason that brought me here in the first place. It started showing these messages and I decided to install a custom ROM, it was first stock and locked and happened, now with this Android HD ROM it is still the same.
Thanks man... i was scared like hell when i realised that by script my battery voltage didnt raise up... even worse... it became less... i was reboting bootloader for 1h, but finally it worked... now im charging it to max... then ill flash stock rom
Thanks again.
Hi had all different roms on my DHD and settled on Ice cold sandwich which it has been running for a few months now, earlier on today I noticed that it had gone off and only the backlight was on, So I restarted it and it started loading the screen up but then just went into a loop.
So i pulled the battery and went into recovery and reloaded the ICS rom, but know it just vibrates 5 times and shows the splash screen and goes off with just the backlight on again.
I can get into fastboot but when i press the button for recovery it does the same I've tried every pd98img I could find and it says wrong image after I try and load them.
And when I connect it to the pc it can't be recognised by htcsync or thru any adb commands, and windows tried to load a driver called Q_USB-DLOAD or something similar then loads a qualcom usb driver but adb commands still won't recognise it, been looking all bnight for an answer getting desperate.
Thanx in advance Michael
1. Remove your sd card and try to boot up again if it boots up then there might be something corrupted on your sd. (Possible sd may have gone bad)
2. Try to enter hboot with power button and volume down at same time to see if you can get into hboot. If it dont your boot img may be damaged and you may need to push it again thru ADB.
3. If you can get into recovery try full wipe and reflashing rom. (You may have to use an adapter to get rom on to sd since computer dont see phone then place sd back in phone)
These are just a few ideas you can try hope it helps.
EDIT: Also there is no need to create a double post of the same issue. This is what causes clutter among the forum. When you post a question you need to wait for an answer not ask again when there is no reply on your first post. Thank you