im on green clockwork recovery and no matter what i try to flash it says bad zip. Also i have wipe everything and formattted sd card. Can i just unroot and fastboot usb mode? please need help
I personally never had good luck with CWM for Eris. I have been using Amon Ra recovery with no problems. I would give that one a shot.
There is one application on the Market called 'HTC Eris One Click Root', it installs a custom recovery and at the same time you it gives a zip so you can root the Eris. This might not be relevant to your situation, however, if you delete your current recovery mode and you can try this; this is just a suggestion.
Hope this helped
I second the Amon Ra recovery for the eris.
I can fix cars but I might have jacked my Eris
So i have ClockworkMod, And was using CyogenMod 7, no problems, Even tried a few other Roms, well I was switching Roms one day with the battery low. Stupid me. It died in the middle of it (F..k me). I now have the problem of- assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Errorn /sdcard/update-cm-7.2.0-RC1-desirec-signed.zip
(status7)
installation aborted.
This happens or similar no matter the ROM!!
And my nandroid backup- Well its now missing!!!
What can I do? I can boot into hboot and go to usbbootlogger and into clockworkmod recovery so it aint bricked yet! Might as well be though cause I am using a old NON ANDROID hoopdee till I fix this one. Its like my Cadiliac is broke and Im driving a VW bug till I fix it! Ugh!!!! This was a Verizion Flashed(reprogramed by me with no problems) for months. I guess I know enough to fix it if some one holds my hand through the steps! Or enough to get myself in trouble!!! Anyway, any suggestions! And yes please talk to me like im 5 explaining all the steps in detail or It just might be bricked! If you live in Denver Colorado I will fix some Cars for some phone help! That is a great deal as cars are way more expensive as the tools and schooling are Very expensive! A scanner will buy you 50 new phones!!! But hey, I just want my phone back! And ya might get your car fixed for it!
jayram1408 said:
well I was switching Roms one day with the battery low. Stupid me. It died in the middle of it (F..k me). I now have the problem of- assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Errorn /sdcard/update-cm-7.2.0-RC1-desirec-signed.zip
(status7)
installation aborted.
Click to expand...
Click to collapse
jayram1408 said:
What can I do? I can boot into hboot and go to usbbootlogger and into clockworkmod recovery
Click to expand...
Click to collapse
You should be able to flash ErisMTDNuke_v0.9.zip from within ClockworkMod recovery. Get it here.
Note that this procedure will completely wipe out the "boot", "system", and "data" partitions, so you should also either:
(a) have a ROM on your SD card ready to install OR
(b) figure out what you did to your nandroid backups and restore one of those.
You can do the flashing of the ROM or nandroid restore in the same session of ClockworkMod after flashing the ErisMTDNuke_v0.9.zip repair.
As you've learned, do this stuff with a 100% charged phone.
Let us know how it works.
bftb0
I really messed up now
Now it wont even light up, turn on, charge, NADA. Does this mean its toast? Nothing.
jayram1408 said:
Now it wont even light up, turn on, charge, NADA. Does this mean its toast? Nothing.
Click to expand...
Click to collapse
What exactly was it that you attempted? Did you charge it before you did anything?
You might try pulling the battery, wait a couple seconds, press each of the mechanical buttons (vol-up/down, send, trackball, end) once, and re-insert the battery, and put it on the charger. (This is a very long shot, probably will do nothing.)
Note that if you left the phone sitting in HBOOT, FASTBOOT, RUU mode, or a bootloop the battery can discharge even if you have it plugged into a USB hub. IIRC Li-Ion battery packs have a safety circuit that prevents charging if the battery charge (voltage) level drops too low.
It is possible that you simply have a dead battery that can not be recharged. Not easy to tell if that is the case, though - if you plug an Eris in to a charger without its battery, it won't start up in any mode even though there is (in principle) sufficient voltage/current (I just tried it on a working Eris). About the only way to know for sure is to see whether it's the phone or the battery is if it will go into any mode with a known-good battery.
I just measured the open-terminal voltage on a charged Eris battery - 4.11 V
bftb0
Battery reads 3.89 volts
I don't know what happened? I did'nt get a chance to do anything. I tried to boot into recovery and that was the last time it did anything. No lights, beeps, backlights, even no charge indicator. I cleaned the contacts with alcohol, still nothing. Its like its fried. I am wondering if it has lost all programing and that prevents buttons and charging from working?
jayram1408 said:
I don't know what happened? I did'nt get a chance to do anything. I tried to boot into recovery and that was the last time it did anything. No lights, beeps, backlights, even no charge indicator. I cleaned the contacts with alcohol, still nothing. Its like its fried. I am wondering if it has lost all programing and that prevents buttons and charging from working?
Click to expand...
Click to collapse
That sounds like a hardware problem other than the battery - I think that the discharged voltage for a low Li-Ion battery is close to 3.0v or below, so a discharged battery is probably not your problem.
100% of all "software" - even the bootloader itself - is stored on the single NAND flash chip in the phone. So, it could be that the bootloader code got corrupted, but it could also be any number of other hardware defects that prevents the phone from getting to the point where it loads and runs the bootloader code. It could even be something trivially simple like a problem in the battery charging circuit - it seems hard to imagine that the microprocessor needs to be awake and running (maybe in deep power down mode) for the battery charging to be operational.
Ok cooked eris.
I liked it so much I found a near new one on Craigs List for 30. And im back up and good again. Flashed Amon RA Recovery this time.
Related
Hello,
Yes, I am a noob, and after searching and looking through a lot of threads, I decided to make this post, knowing full well how annoying it must seem to those of you who actually know even a little about phones.
Someone special to me got the HTC HD2, and it was a bargain. But she hated windows, so I offered to help. She's had it for ages by now.
I believe I did everything correctly, blindly following guides (which I know is a bad idea from reading threads similar to this one).
The thing that makes my problem somewhat special is:
- Everything went smoothly, the android build is amazing
- I was a hero for a few hours
- She's playing some game when it suddenly freezes.
- Buttons not responding, afraid the battery has to go.
- Boots up, android guy stares at us for more than five minutes, battery has to go again.
- Nothing, NOTHING, happens after. Can't boot, screen is black.
So obviously I'm suspecting the battery is completely dead. It won't charge either from the computer or by plugging it to the wall. It was connected when it crashed, and there must have been power left. Now, I have the HTC desire HD, so I can't test my battery with the other phone.
Before I try to buy a new one, I need to know, being completely oblivious with regards to anything more complicated than rocks, if it's possible that I have installed any kind of software that can permanently mess up a battery. Feel free to laugh if this is the dumbest question ever. It's weird how it booted a little before permantently shutting down.
To make matters a lot worse, she's going abroad for five months possibly only equipped with a really old nokia phone until I can get things fixed and sent off to her (which will be quite expensive and perhaps risky.)
Have I messed up good, or is it just chance that the battery should fry hours after getting the android rom? Should I get a new one? Her phone was actually smoother than mine until the crash.
Sorry to make yet another "dumb noob ruins phone" but I really need to redeem myself, and fast.
Edit: Remembered the course of events was a bit different.
well, if I tell you that the phone wont charge when off when magldr is installed, would that change your opinion of whether the battery is at fault?
id suspect the crash broke something preventing rebooting (had this myself once or twice with nand android ) followed by teh battery being flat so wouldnt come back on. (And of course magldr wont let it charge when off....)
get an old usb cable, any type, cut end off, bare red and black wires, plug into wall charger and then hold red to + black to - on the battery for about a minute, this should let the phone start, , put it into bootloader (coloured stripey screen, not magldr) and let it sit there for a hour or three with usb plugged in, should now be charged enough to see if you can get into magldr, from there into cwm, and from there id do a backup, and then perform 'wipe data/factory reset', , if it boots to the clean rom, you can try (again in cwm) selectively restore the data and/or sd-ext partitions, which should bring back teh data and the installed apps. if the restore doesnt work, just do another wipe data/factory reset and start from scratch.
also, check the battery pins very carefully, they bend easily, especially when you pull teh battery whilst panicking!
samsamuel said:
well, if I tell you that the phone wont charge when off when magldr is installed, would that change your opinion of whether the battery is at fault?
id suspect the crash broke something preventing rebooting (had this myself once or twice with nand android ) followed by teh battery being flat so wouldnt come back on. (And of course magldr wont let it charge when off....)
get an old usb cable, any type, cut end off, bare red and black wires, plug into wall charger and then hold red to + black to - on the battery for about a minute, this should let the phone start, , put it into bootloader (coloured stripey screen, not magldr) and let it sit there for a hour or three with usb plugged in, should now be charged enough to see if you can get into magldr, from there into cwm, and from there id do a backup, and then perform 'wipe data/factory reset', , if it boots to the clean rom, you can try (again in cwm) selectively restore the data and/or sd-ext partitions, which should bring back teh data and the installed apps. if the restore doesnt work, just do another wipe data/factory reset and start from scratch.
also, check the battery pins very carefully, they bend easily, especially when you pull teh battery whilst panicking!
Click to expand...
Click to collapse
What ARE you?
It started. Honestly, when I was crossing wires I half suspected someone was pulling my leg. I can't thank you enough. Maybe I will be able to get this thing running again before I leave in the morning. I'll visit the link in your signature at a later point, too, as you may have saved me some money here.
The only real problem is that with no prior experience, I didn't even really get into what the different programs I installed actually do, so I'm not even sure where to go from magldr. I took a backup of what was essential before flashing, so I guess I'll just try to navigate to wiping and resetting. So relieved.
e: Progress, thanks again, fantastic.
Multiplum said:
e: Progress, thanks again, fantastic.
Click to expand...
Click to collapse
youre welcome.
As per feralicious' suggestion I've created a poll to collect data. Information on the issue below. Sorry about the long poll.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I'm on Rezound #2 right now. Both of the phones had the same exact problem when the battery died ie. they simply wouldn't charge. Now I thought the problem was hardware (which is why i got the replacement), but after being able to boot up my replacement phone with my girlfriend's battery, I relocked and RUU'd back to stock. I then threw in my dead battery and VOILA it began charging. I let the battery die again just to see if i can recreate the problem, and havent had the issue since.
Now i really want to unlock my phone again but my girlfriend isn't here all the time for me to test out if this was an issue with either the unlocked bootloader, a kernel issue, ROM issue, or if I'm actually having hardware issues. I'm hoping someone here with an extra battery or external charger here can recreate the problem and hopefully we can pinpoint this. Just for reference the ROM I was using was CleanROM GBE 1.6.5 *SP1* - Base: OTA 2.01.605.11 and whatever kernel that came with it. If this is a ROM and/or Kernel issue, we need to get a hold of scrosler and let him know.
Any help would be much appreciated guys thanks!
EDIT: Just to let you guys know. I did do all the OTA updates prior to unlocking the bootloader in the first place.
UPDATE: So I've been sitting with my phone literally all day trying to pinpoint what could be the cause of this. Clockworkmod seems to be the culprit. I'm going to be testing more right now so I'll keep you guys updated.
UPDATE #2: Success! The battery not charging while dead and powered off issue was resolved on my end. ClockworkMod definitely was to blame. I noticed it stopped charging while powered off/dead as soon as I flashed ClockwordMod and shut down my phone while it was connected to my PC (This was after my 5th go around with the bootloader unlock). I then flashed over Amon Ra to see if it really was ClockworkMod or if it was the recovery in general, and what do you know Amon Ra allows me to charge while powered down and dead. If you guys are having this very problem with your phone and you're running any version of ClockworkMod I suggest you try flashing Amon Ra 3.13 and posting your results so we can see if this is universal.
Instructions to flash recovery with adb and fastboot for Windows below:
Note you only need to do this if for some reason you can't boot into the bootloader using Vol. Down + Power. I am not responsible for bricked phones.
Prerequisites:
1. ADB & Fastboot (found with the Android SDK)
2. Amon Ra IMG (Use ver. 3.15 if you've flashed ICS RUU)
3. Battery with a charge.
Instructions:
1. Pull out battery, and unplug from charger/computer
2. Reinsert battery
3. Plug in your USB cable to computer and phone (your charge indicator light should go on for 1-3 seconds and shut off, then your drivers should load afterwards.)
4. Place the Amon Ra img file in the folder where ADB and Fastboot reside.
5. Once drivers have loaded open up Command Prompt, and find your way to where you set up ADB and Fastboot. Type cd <folder path>
6. Now type the command adb reboot bootloader (Note: if you get some sort of error try again a few more times. if it keeps giving you error try redoing steps 1-3 before doing 5 again)
7. Your phone should have now loaded directly into Fastboot. When in Fastboot go back to the command prompt and type in fastboot flash recovery <amon_ra_file.img>
8. When the process is done shutdown your phone and test the charging.
**ADDED** If you can run ADB commands while the phone is off, dead, and not charging, type adb reboot. The OS should boot up and begin charging. I would say let it charge till 40% before you flash an alternate recovery. If you're unsuccessful in rebooting with adb try leaving your phone plugged into the charger for 2-5 hours (this seems to have worked for some people to get a charge). If that doesn't work I recommend you get another battery or use an external charger. (Thanks excellentnuke)
If you are coming from a dead battery the charge light indicator should turn on for a few seconds then turn off for a few seconds then begin flashing continuously. When the light becomes solid you should be able to boot. When coming from a charged battery the same thing should happen, except instead of the charge indicator flashing continuously it should come back solid.
UPDATE #3: I've also discovered this problem isn't relegated to having a dead battery. Simply disabling Fast Boot and shutting off your phone can recreate the problem with CWM.
UPDATE #4: I can say that I think I've gotten enough feedback to determine that this issue was solved by what I've written above. I would highly advise people to switch over to Amon Ra until we get a bug fix/update for CWM to address this issue.
Thanks to everyone that was involved in this thread to help determine the cause of this; I appreciate it.
You should set up a poll and change the thread title to indicate that.
I am on Ineffabilis GB and accidentally let the battery die yesterday and it charged no problem. I was ready for a problem, thankfully it went straight to charging. I had also let it die once before unlocking and no problem then either.
feralicious said:
You should set up a poll and change the thread title to indicate that.
Click to expand...
Click to collapse
Good idea. Done!
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
I have been running different ROMs and had it die a few times...
When I plug it in the LED comes on and starts blinking, after a few minutes of the blinking, I unplug then re-plug in the phone to the charger and the light comes on and stays on. I never let it sit there long enough to stop blinking on its own. I get impatient LOL.
UgXvibe said:
My phone shut off last night due to battery death, when I woke up I plugged it in and the charge indicator came on after about 10 minutes of charging.
Click to expand...
Click to collapse
I take it you're running stock still? or a custom rom? It seems odd that the charge indicator would take that long to start. I left mine on the charger for about 30 minutes when it was unlocked without any progress.
This happened to me, I took my phone to verizon and they just gave me a new battery... it took a little while, them trying different batteries, looking for a 'test' rezound battery before pulling a packaged battery to try and finally they were satisfied then swapped it out... all my boot logos and screens were stock but my launcher was not... they never went as far as checking phone specs or asking about root/unlock... they did check the phone settings to check on charge at one point... I was just thankful it wasn't a bad micro connector because I didn't want to have to wait for a new phone
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
andybones said:
Before I knew about this issue I actually had my phone die when I had my 3.8v battery, I had no issues what-so-ever plugging it in to charge. I've been afraid ever since, I also have the 3.7v battery now.
I bought my phone from a trade of my GNEX, so I do not have the 1 year manufacturer warranty, so no refurbs for me, and I had to buy the 3.7v battery
I'm getting rare blue screen flickers like the ones from ICS ROMS on GB ROMS too. no fun!
Click to expand...
Click to collapse
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
drinkhere said:
I'm having the same problem once my phone dies i can't get it to charge. it starts charging for two sec and it stop charging and i does that with both of my batteries i have a 3.8v that came with the phone and a 3.7v that verizon sent me because my phone was over heating. I'm unlock and running CleanROM GBE 1.6.5 *SP1*
Click to expand...
Click to collapse
I would highly suggest you relock and go back to stock. It seems to have made the issue subside. Since you have 2 batteries if you wanna do further testing with other roms and configs that would help out a lot. No pressure though i understand if you dont want to do it.
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
joel4832 said:
I've also had the problem with it not charging after it's died and thus had Verizon send me a new 3.7v battery. And now Ive had the same problem with the 3.7v.
This is how i've fix both the 3.7v and 3.8v when they wont charge.
Battery pull and replace. Then plug in. Dont hit power or touch the phone. Just leave alone. Orange light will come on for a few seconds then off. Still leave it alone. I swear it took an hour but it finally booted on it's own. Weirdly it had 40% battery when it was finally on.
I'm on stock OTA rooted and running chad's beta 4 but i've had the problem with beta 3-1 as well. I did have Force fast charge enabled in incrediControl. Most of the reason the phone died was because it bootlooped for hours(?) while i was sleeping and it wasnt plugged in.
I did have a similar problem when i first got my incredible... dunno what i was running at the time could have been stock.
What i'm guessing happens is that you drain the battery so much it takes forever for it to get a strong enough charge to boot on it's own.
Click to expand...
Click to collapse
Hmmm... I'm beginning to suspect its either an unlocked bootloader issue or a kernel issue and not a ROM issue.
Now thats cool that your phone was able to boot up after an hour on the charger without the charge indicator light telling you it was charging (my phone was probably doing the same thing) but it still shouldnt take that long to be able to boot up the device.
When stock my charge indicator blinks continuously until it's ready to boot up, then it becomes solid. This only takes about 4-5 minutes. When running custom ROM/Kernel it would give me the same thing it gave yours ie. charge indicator turns on for 1-3 seconds and turns off and nothing else.
afmracer6 said:
I had this happen for the first time today. Phone wouldn't start,battery wouldn't charge. My fix.... Open command prompt. Plug phone in to computer. Type " adb reboot recovery" when recovery opens the battery starts charging. Push reboot and Pooooof! A charging phone!
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I'm definitely going to take this into account and try it when i unlock my phone again. Thanks man!
IrvChynaman said:
What's interesting is that I keep reading about issues with the 3.8v battery but nobody talking about the 3.7v's. I'm on a 3.7v and this issue is occuring, but i'm beginning to think it has something to do with either an unlocked bootloader or ROM issue.
Click to expand...
Click to collapse
Update in OP!
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
edit: i would also like to note, when putting the battery [my 3.7v] into my girlfriends device. It showed about 80% battery.
krstnsn said:
Im unlocked and on the senselessICS.
Ive had this issue happen to me several times. However today it was bad. I had it plugged in for 6+ hours with out it being able to turn on.
I had the 3.7v battery in the device.
i messed with it a bit with in that 6hour time frame. Pressing buttons pulling battery, etc. About 4 hours into this whole ordeal... it turned on, on its own. But stayed on the white HTC screen for about 45mins before i pulled the battery and tried to turn it on again. However, it would not turn on. Infact it never turned on....
Heres where it gets interesting. I had the 3.7v. My girlfriend comes home and has the 3.8v. I pop hers out, put it in my device. Fires right up... still sticks on the white HTC screen. While im impatiently waiting, i stick my 3.7v that my phone wouldnt boot with in her device. Fires right up.
I wasnt able to fully boot. Recovery/computer wouldnt mount my SDcard. Though... reformatting it from within recovery allowed it to be mountable again. I also had to wipe and reflash my rom in order to get the POS to boot.
Click to expand...
Click to collapse
are you running clockworkmod recovery? Your issue sounds identical to mine and I MAY have a solution. I'm testing right now on my own phone right now.
IrvChynaman said:
are you running clockworkmod recovery?
Click to expand...
Click to collapse
yes. the touch one. However i had this issue prior with the unofficial clockwork.
krstnsn said:
yes. the touch one. However i had this issue prior with the unofficial clockwork.
Click to expand...
Click to collapse
Ok try flashing Amon Ra 3.13. Clockwork mod seems to be the culprit from my end. what was weird is when the phone was shut down I was able to run adb commands and every time i ran "adb devices" it showed my phone as recovery. It seems like clockwork mod recovery was trying to load before anything else preventing the phone from charging and booting up
Hello Everyone,
I may have done the stupidest thing ever. I was attempting to partition my sd card using an app I found in the play store (don't remember which at the moment), Well i believe that i may have messed up and accidentally deleted the HBOOT partition. the phone continued to run fine but then when i restarted the phone never came back on. the phone does absolutely nothing, no lights no vibrations no charging indicator nothing. I have been at this for 3 days now and i think i am about to give up. Any one out there have any advice. I have found the unbricking thread but they all specify its for S-ON only and i am S-OFF when i plug it into the computer is is recognized as QHSUSB_DLOAD although the drivers dont load. I found some drivers online but that did nothing.
I too might have this problem. I'm not sure because it has been well over a year since the incident and I have moved on. My evo, when connected to a charger, flashes a red light for about a minute and then does nothing. It will not pull up a charging logo and will not boot. The battery is completely dead. I know I used to be able to access recovery on the device but the original sd card is gone. Would this mean if I got the battery charged somehow that the phone would still be bricked? When I plug it into a computer is says htc_shooter. The phone is s-off and i dont remember the hboot it had or firmware version. If anyone has advice for me that would be wonderful, however if my phone is forever a brick then no big deal.
Mr_JacobClutch said:
I too might have this problem. I'm not sure because it has been well over a year since the incident and I have moved on. My evo, when connected to a charger, flashes a red light for about a minute and then does nothing. It will not pull up a charging logo and will not boot. The battery is completely dead. I know I used to be able to access recovery on the device but the original sd card is gone. Would this mean if I got the battery charged somehow that the phone would still be bricked? When I plug it into a computer is says htc_shooter. The phone is s-off and i dont remember the hboot it had or firmware version. If anyone has advice for me that would be wonderful, however if my phone is forever a brick then no big deal.
Click to expand...
Click to collapse
When I had this problem it was due to my battery having run down so much and not being able to draw a charge. If you have a spare battery try swapping that in and see if it makes a difference.
If you don't have a spare you can try what I did which is to take out your battery and put it in airtight bag and place it in the freezer overnight. Put the battery back in and try to power it back on in the morning.
When I first read this I thought it was crazy but I thought what the hell and incredibly it worked. Something to do with the low temp allowing the battery to draw enough to charge. Of course you could have an altogether different issue and I would only try it if you have nothing to lose.
Hey guys,
So I've had my DNA for almost 1 1/2 years, and just recently decided to root and flash CM 11 and CWM recovery onto it. Now, everything went fine, except a month later, I was listing to music on Pandora, and my phone crashed (it has a few times before since it wasn't a stable release, but always boots back up in like 5 mins), but this time it never booted back up. I let it sit in the charger over night, but got nothing, not even an orange light. So I decided that, since it was broken anyways, to go ahead and take the entire phone apart and reassemble it. And after the second time, it turned back on (by plugging it into my computer at the same time of holing down the power button). But an hour later, the battery died, and I couldn't get to the charger in time, so it shut off. Now, I've tried everything that I have before, and also took it to a repair shop, but never got any life out of it again. Does anyone have any ideas about whats wrong? Is it fixable? I've also herd of a type of USB jig for Samsung phones that can put an unresponsive phone into 'download mode', is there some kind of equivalent of that for the DNA? Any help is appreciated!
Thanks!
Cman1468 said:
Hey guys,
So I've had my DNA for almost 1 1/2 years, and just recently decided to root and flash CM 11 and CWM recovery onto it. Now, everything went fine, except a month later, I was listing to music on Pandora, and my phone crashed (it has a few times before since it wasn't a stable release, but always boots back up in like 5 mins), but this time it never booted back up. I let it sit in the charger over night, but got nothing, not even an orange light. So I decided that, since it was broken anyways, to go ahead and take the entire phone apart and reassemble it. And after the second time, it turned back on (by plugging it into my computer at the same time of holing down the power button). But an hour later, the battery died, and I couldn't get to the charger in time, so it shut off. Now, I've tried everything that I have before, and also took it to a repair shop, but never got any life out of it again. Does anyone have any ideas about whats wrong? Is it fixable? I've also herd of a type of USB jig for Samsung phones that can put an unresponsive phone into 'download mode', is there some kind of equivalent of that for the DNA? Any help is appreciated!
Thanks!
Click to expand...
Click to collapse
It's your recovery. Try the most recent twrp instead. I've had this issue with my rezound and DNA and it's scary for sure. If you find a way to power on your device immediately change recoveries. Some are touchy on charging a dead phone.
iHateWebOS said:
It's your recovery. Try the most recent twrp instead. I've had this issue with my rezound and DNA and it's scary for sure. If you find a way to power on your device immediately change recoveries. Some are touchy on charging a dead phone.
Click to expand...
Click to collapse
Would maybe trying to charge the battery outside of the phone work? If so, how would I go about that? A friend of mine has a Lipo charger for RC cars, could I make some kind of jig to charge the DNA's battery with that?
EDIT: Found out he has a supper high end lipo charger that is programmable, so could I charge it with that if I can get the battery hooked up right?
Cman1468 said:
Would maybe trying to charge the battery outside of the phone work? If so, how would I go about that? A friend of mine has a Lipo charger for RC cars, could I make some kind of jig to charge the DNA's battery with that?
EDIT: Found out he has a supper high end lipo charger that is programmable, so could I charge it with that if I can get the battery hooked up right?
Click to expand...
Click to collapse
You could to irreversible damage to the battery if you do the settings wrong, or hook it up incorrectly. You can get a replacement battery online for pretty cheap. I suggest that than possibly having a small explosion from charging a battery in a way not suggested. After you get the phone back on, immediately fastboot flash a different recovery as @iHateWebOS said.
New batteries come half charged (40-60%) out of the box as that is the suggested storage capacity for batteries to ensure long shelf life.
Sent from my HTC6500LVWBLU using XDA Free mobile app
Okay, just ordered a new battery, should be here between the 10th and the 20th. Hopefully this works
HOLY ****, IT WORKED!!!!!! My DNA booted!!! Thanks so much guys!!!! Which recovery would you guys recommend?
EDIT: So I flashed on twrp, and it won't charge with the original battery in it, so does that mean if the new battery dies, my phone won't boot again? If so, which recovery should I flash to prevent that?
Okay, update. So I tried updating my DNA to the latest snapshot of Cyanogen mod (was at m6, going to m11), and the recovery failed, so now I'm soft-bricked... I'm trying to flash on the old m6 snapshot I have on it, but it keeps failing. Also, the recovery won' t support external storage, so I can't flash on m11 from my flash drive... What should I do?
EDIT: Okay, just found out that I was running the 2.4 beta of twrp, so I'm trying the latest 2.8.0.2, Ima see if that does anything
EDIT: YAY, flashing the latest recovery worked!! so now everything is working properly, except the digitizer, since I ripped the ribbon cable a little, but I already ordered a new one
Okay, so I accidentally let the battery drain, and now I'm at square 1 again. Does anyone have the pin-out schematics for the battery on the DNA so I can make a jig to charge it?
Thanks!
I got this old phone out of the cupboard because I needed some old photos from iT, and figured I'd better backup before it died. So I turned it on, the phone crashed and started boot looping. Great. I try to enter recovery and it won't work, only thing that works is download mode.
So I do some reading and see that reflashing the stock firmware might work, so I try that in Odin and it just hangs on factoryfs for an hour. So I disconnect and try again 10 times with different computers, cables and ports. Also tried alternative firmware. Same result each time
So now I find info on installing twrp and backing up the needed user data from there.
So I install hemidall and it recognises the phone, sweet. I find an isorec boot.img and a twrp recovery image bang them in and hemidall starts. I think I'm onto a winner.
But Noooo, hemidall says beginning session, sits there for maybe 20 seconds then moves to releasing device interface.
Any idea what else I can try? I must have spent 12 hours doing this. I just need the photos I could care less about the phone.
Thanks
Are you sure you have a fully operational battery?
You know, sometimes the battery can be fully charged, but still cause resets.
Do you see a charging animation on the screen when connected to the charger?
ze7zez said:
Are you sure you have a fully operational battery?
You know, sometimes the battery can be fully charged, but still cause resets.
Do you see a charging animation on the screen when connected to the charger?
Click to expand...
Click to collapse
Hi Thanks for the reply.
The battery seems okay, but its not charging in the phone currently, when i plug it in it comes up with this weird like grey frozen charging logo. Ive been charging it externally to make sure it keeps a decent charge during all these flashes. But as i can't enter any kind of environment the only way i know the batterys charge is using a multimeter.
Also wanted to add, the phone didnt have adb enabled so thats off the table. I also dont even know what firmware version it was running. all these things seem to be working against me.
Since I tried to use odin to upgrade the firmware i dont even get a boot logo or it trying to boot anymore, i get the yelllow triangle with phone and pc logo, so im assuming the original firmware is toast. just need some way to reinstall the firmware, or install twrp and grab a backup, then this thing is going in the bin because its ruined my last 24 hours.
Thanks again
If you don't want to waste time, and you have the money, then turn to a local service that has a data recovery service using JTAG. Usually you pay when it is possible to recover the data. However, if the NAND memory has damage, this could be a problem.
ze7zez said:
If you don't want to waste time, and you have the money, then turn to a local service that has a data recovery service using JTAG. Usually you pay when it is possible to recover the data. However, if the NAND memory has damage, this could be a problem.
Click to expand...
Click to collapse
thanks. I live in a small country town in Australia. Closest place for something like that would be 4 hours away.
I'm already wasting plenty of time haha but i reallllly need this data, so i will try whatever anyone can suggest. thanks