Related
Hi All
Hoping someone can tell me if I've completely killed my phone. It was working absolutely fine with no problems whatsoever until earlier today when it froze. Without looking around at what to do I just held down Vol + & Vol - & power. This restarted the phone and it went through the T-Mobile logo and then just sat there. I then took out the battery, put it back in and held vol - and hit power, got into the clockworkmod menu and used the recovery option to wipe then restore an earlier backup, this all seemed to go fine and I used the power off option to restart the phone.
Nowwww though it just vibrates 7 times and stops, if I then pull the battery and replace it and hit power it vibrates 7 times again and then nothing unless I pull the battery again.
Am I screwed?
The phone is S-Off and had clockworkmod installed. Has the clockworkmod boot loader thingy some how been damaged? Anything I can do?
Appreciate any advice. Thanks
can you get into recovery? if so try wiping everything and then doing a fresh install of something
Sent from my Desire HD using XDA App
dont keep pulling the battery if you dont already have emmc failure you will soon if you continue to pull the battery!
Yea I didn't realise pulling the battery was that bad. I haven't done it since reading this forum. But no I can't get in to recovery any more since that time I wiped everything and restored a backup. Since then it just vibrates 7 times when I push the power button and that's all.
can it connext to adb? if so, id try flashing an ruu via fastboot. that will set everything back to stock. then you can reroot and flash a rom, and id get rid of that backup
Sent from my Desire HD using XDA App
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
rlzzzz said:
Is there a guide for adb anywhere? I haven't used it before, but I've tried plugging the phone in by USB and Windows doesn't say new hardware found so I assume that's a bad sign?
Click to expand...
Click to collapse
theres tons of guides but if you give me a few minutes ill upload a auto installer for you, so then you just have to add the path in
Sent from my Desire HD using XDA App
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
rlzzzz said:
I looked for adb guides and they all seem to show how to install the drivers etc but my phone doesn't even get detected as a new device in Windows so I assume it's not going to show up?
I mean it looks completely dead right now, won't turn on or even vibrate. Unless I was to pull the battery again I think it would probably then vibrate 7 times when I push the power button for the first time and that would be it again.
Do you think the clockworkmod boot loader got overwritten some how when I did the restore?
Click to expand...
Click to collapse
it could of, and its worth a shot, it might be recognized. just get adb working, and install the drivers. plug the phone into your computer, and wait a minute or 2 and the screen should turn on but be black. then just boot into the bootloader and flash the ruu via fastboot
Sent from my Desire HD using XDA App
So I installed Java JDK, then Android SDK, then downloaded the HTC adb drivers but it says to install the drivers plug in your phone and wait for Windows to detect it... which is as far as I can go because Windows doesn't detect the phone.
I don't even seem to be able to reset the phone by holding Vol + & Vol - & power at the same time. It's not looking good.
In fact you say about the phone going to a black screen, it did do this after I initially restored the image. But it was just after that that I pulled the battery and now it doesn't do that anymore.
I assume basically what has happened then is first some thing froze and corrupted my normal install, so to fix this I tried the restore and the restore image somehow overwrote clockworkmod but at this point the phone was still recoverable via adb? but then I pulled the battery and now it's definately dead?
Seems like an unfortunate string of events but at least I know now to avoid pulling the battery next time! Thanks for all your help stumpyz9 and djisgod, I don't suppose you know why pulling the battery can so easily kill the phone?
Btw if anyone would like to jump in and make my day by saying nooo everything is fine here is a quick fix please feel free
my only guess of why pulling the battery killed it is when you where restoring it and then pulled the battery, it was restoring something very essential to even turning the phone on. i dont know why windows wouldnt detect your phone, it has derected my DHD even in the worst scenarios. and were you saying the drivers wanted you to hook the phone to the computer? if so dont and try to continue installation, because if you can get it hooked up to your computer and have adb recognize it, then tyere is a very good chance you can recover it. if not, then im sorry to say you have yourself a very pretty paper weight. if it is a paper weight, id say maybe check to see if a dev could use it or basically part it out on ebay and sell the lcd, digitizer, housing, camera and you can probably make some of your money back.
Sent from my Desire HD using XDA App
The ADB HTC drivers I downloaded are not an installer file, you need to plug in the phone so Windows will recognise a new device and ask you to select the location of the drivers but I can't because it doesn't detect the phone being plugged in at all.
I've also been reading around a bit more and found a thread about a fried eMMC chip. I was actually getting the same errors they mention in that thread when I did the restore from clockworkmod.
"E:Can't open /cache/recovery/log" etc etc
dont use that, install htc sync, then plug the phone in and tell me if that works
Sent from my Desire HD using XDA App
Yea I just gave that a go after reading someones adb guide and even with HTC sync installed when I run "adb devices" it lists nothing.
It's strange I thought once I had clockworkmod installed nothing could go wrong because I would always be able to restore from an old backup. I always assumed that clockworkmod would be sat on the boot partition and never touched even when restoring a backup. I can't understand how it went so wrong lol.
Although right now the phone seems so far gone maybe I could get away with a warranty repair as they won't be able to tell it was S-OFF.
yah if all of the chip has been fried and it wont power on, i think that would be your best bet, seeing as they probably wouldnt be able to tell.
Sent from my Desire HD using XDA App
Ok well thanks for your patience I appreciate your help.
rlzzzz said:
Ok well thanks for your patience I appreciate your help.
Click to expand...
Click to collapse
no prob, alwsys like to help out when i can
Sent from my Desire HD using XDA App
I know this title comes up a lot but I can't seem to find my problem.
I wanted to go back to the stock rom and I used the proper RUU but totally forgot to use the S-ON tool before hand. It installed successfully but now I get a solid amber light and so far I got my inspire to boot once only to get stuck on the splash screen with it vibrating non-stop.
And now it just vibrated once, went to a black screen and then shut off. I really don't know what to do since I can't even get to HBOOT nor will the computer recognize it.
I've done numerous batter/sim card pulls as well as clean them out.
Any help would be greatly appreciated
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
lay012 said:
I think he was referring to the bootloader as HBOOT. I had this problem while rooting my sisters Inspire. Might be a corrupted bootloader.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
moutansos said:
Have you tried booting into the bootloader and doing a factory reset?
Sent from my Inspire 4G using XDA
Click to expand...
Click to collapse
Never do a factory reset on a S-OFF device....it will jam u up.
greggyt79 said:
Last I remember my bootloader was TWRP which I guess I had accidentally installed somehow. If you think its a corrupted bootloader how would I go about solving this, if there is a solution?
Click to expand...
Click to collapse
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
greggyt79 said:
Alright so I went to the IRC and they told me they couldn't help because it did not deal with the hack kit, fair enough.
I have been able to get the phone to boot after waiting for about 10 minutes but I cannot get to the bootloader. I tried rooting the phone again this way I can turn s-on then flash the stock rom again but the phone ends up not being detected half way through the process.
I really don't know what else to do...
Forgot to mention, now my inspire boots but then fades to a greyed out screen. My computer recognizes the phone as something occupying the usb port but is not accessible. Wish the phone had a physical reset button somewhere that i can poke with a paperclip...
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
glevitan said:
Greggyt, Hit the IRC Channel again,.....it was a rough day and we were a bit pissed. I just connected after you were gone....=0) just hit the channel again....
Click to expand...
Click to collapse
I will get back on the IRC this evening when I get home from work thanks again!!!
Does it say anything about QHUSB_DLOAD USB device being connected?
I ran into a similar problem not too long ago, immediate vibrating followed by a solid amber light and no phone activity (nothing on the screen at all). I knew I had a backup in Recovery, but I couldn't even get into recovery.
In order to work around this, I did the following steps.
1. Deleted the PD98IMG file from my SD card (so I could get to recovery once I made it to the bootloader).
2. Take out the battery, then put it back in.
3. Plug in the phone, and let it sit for a few minutes.
4. Start into bootloader (hold power + Volume Down)
Now, in my case I was just trying to get back into recovery. if you don't have a working recovery, or no ROM to flash, you'll want to grab a few RUU 's to try from the bootloader. Try stock GB first, then try a stock Froyo just for the heck of it.
Hope this helps! Good luck to anyone else that's stumbled into this problem.
side note: I've also heard of this "power problem" occurring to other people without bootloops or screwed up bootloaders: which is solved by doing steps 2 and 3, then it'll boot up normally.
help
im having same issue i have gb stock and i accidtly did froyo ruu phones power bottun does nothing i have to plug it into computer and it will get solid amber light then eventually it either brings up battery charge icon and then if i press power button or unplug it. it just shuts off the i plug it back in and wait sometimes white htc screen comes up and it vibrates for a while then boots ad works like nothing is wrong but i cant flash gb ruu when i try to do that or re root and go to recovery to reistall ics that is on my sd as soon as phone restarts during process it doesnt reboot then i have to go threw whole procss of trying to get it to boot back up
glevitan said:
Never do a factory reset on a S-OFF device....it will jam u up.
It seems that the RUU you flashed was a Froyo one and your phone was running GB so you messed the bootloader. Hit the Hack Kit IRC channel (is in the OP thread) and we will lend u a hand to fix that....
Click to expand...
Click to collapse
im new to this site but i did exactly what you said in your post and now my inspire wont reboot unless i go threw a few hour process of plugin my phone in and i get solid amber light for like 5 min then a battery charge screen comes up then i have to unplug my phone and plug it back in the last time i did this it took about 8 hours of tryin until it finally got amber light for like 5 min then started vibrating for a min or 2 then it booted up and its bin workin fine for like a week now ive tried to reflash gingerbread ruu ive tried doin upgrade from my phone and tried reroot but as soon as it shuts down to start upgrade my phone is off and wont reboot
​Atrix 2 will not charge it is stuck in recovery (Blue CWM) it has atrix 2 bootsrap installed and RAZR-CWMOnBoot-Global-J.Y.Daddy.zip file installed need help asap tried cmd line prompt to reboot phone but cpu wont recognize device also i left it on charger overnight and still nothing i will probably get another battery soon but i still need to know how to fix this if i run another battery to 0% thanks in advance dev team :crying:
Did you try to take the battery out of the phone? When you do it will boot into CWM Recovery.
thats the only thing it will boot into it wont go past CWM no matter what i do
dscott973 said:
thats the only thing it will boot into it wont go past CWM no matter what i do
Click to expand...
Click to collapse
When you try "reboot now", what happens?
Charge phone for awhile and FXZ back to stock. The phone will charge if you turn it off and plug into wall charger.
Sent from my SAMSUNG-SGH-I997 using xda premium
And if you have CWM on boot installed you need to either delete the bootstrap apk, or deny it su rights in super user. It's either one or the other, not both.
Sent from my MB865 using xda premium
pull the battery, then put it back after a few seconds and hold both volume buttons while turning it on. choose normal powerup and see if that will boot it. you can also try bp tools.
TheZeroDay said:
When you try "reboot now", what happens?
Click to expand...
Click to collapse
You have CWM on boot installed so this is what it's going to do every time you reboot.
You have to select "reboot now" to get it to boot up normally after getting to CWM.
Have you selected " reboot now" and what were the results?
I have seen people even having this type of trouble on other phones as well, If you are unable to charge your battery Get a battery only charger from ebay using which you will be able to charge your battery then use FXZ you will be fine
link for charger
http://www.ebay.com/itm/Battery-Cha...259246?pt=PDA_Accessories&hash=item4cff64042e
Maybe you should but a ROM in your SD card, get the SD card out put in another phone or MicroSD card adaptor, put a ROM in it and flash it, it should fix the issue. It's not the best idea but it should work.
JRW 28 said:
You have CWM on boot installed so this is what it's going to do every time you reboot.
You have to select "reboot now" to get it to boot up normally after getting to CWM.
Have you selected " reboot now" and what were the results?
Click to expand...
Click to collapse
Sounds as though he's just not familiar with CWM and its functions. I don't see how CWM can just hang there unless the user isn't selecting any of its functions to run...
Apex_Strider said:
Sounds as though he's just not familiar with CWM and its functions. I don't see how CWM can just hang there unless the user isn't selecting any of its functions to run...
Click to expand...
Click to collapse
Actually, if there is an issue with the boot image, it may NOT go past CWM, becuase it can't even check the boot partition if it is corrupted, so it will not even attempt it. I think there was link a few posts up that explained something similar.
I saw this a WHOLE lot with my inspire 4g, where the boot partition became corrupted on reboot, and CWM would not even attempt to boot.
I think tmease1 was right an fxz restore is the best fix at this point, just hope that the boot partition is not so borked that even that does not fail.
jimbridgman said:
Actually, if there is an issue with the boot image, it may NOT go past CWM, becuase it can't even check the boot partition if it is corrupted, so it will not even attempt it. I think there was link a few posts up that explained something similar.
I saw this a WHOLE lot with my inspire 4g, where the boot partition became corrupted on reboot, and CWM would not even attempt to boot.
I think tmease1 was right an fxz restore is the best fix at this point, just hope that the boot partition is not so borked that even that does not fail.
Click to expand...
Click to collapse
Ah, yes... indeed, if his boot image or system image is borked it WOULD NOT boot passed CWM in that case. Hard to diagnose the issue if we don't know what else has been done. Won't RSDlite flash the boot image in the unfortunate chance that his boot image is fudged?
Apex_Strider said:
Ah, yes... indeed, if his boot image or system image is borked it WOULD NOT boot passed CWM in that case. Hard to diagnose the issue if we don't know what else has been done. Won't RSDlite flash the boot image in the unfortunate chance that his boot image is fudged?
Click to expand...
Click to collapse
Yeah, but if I remember correctly, I think I saw a few users who still had issues restoring with RSDlite and even with the moto-fastboot commands, if the boot partition was deleted or so corrupted that it could not overwrite it. Now I have not done a search but just going off of what I remember, so I could be incorrect here though.
I fixed it I saw a post on another forum (forgot which one to anxious to try it) but it would only charge while connected to a computer led was white while charging unlike when connected to a wall charger (no led) it decided to reboot itself as I'd I selected reboot now from CWM I am thankful for all of you guys input. And I'm still gonna get a extended battery so this doesn't happen when I'm away for long periods of times...by the way the standard battery last about two days of moderate usage but can I use an extended battery designed for the Droid Bionic I figured I could but I'm not sure could it hurt?
Sent from my MB865 using xda premium
dscott973 said:
I fixed it I saw a post on another forum (forgot which one to anxious to try it) but it would only charge while connected to a computer led was white while charging unlike when connected to a wall charger (no led) it decided to reboot itself as I'd I selected reboot now from CWM I am thankful for all of you guys input. And I'm still gonna get a extended battery so this doesn't happen when I'm away for long periods of times...by the way the standard battery last about two days of moderate usage but can I use an extended battery designed for the Droid Bionic I figured I could but I'm not sure could it hurt?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
if it fits and i the same voltage, it should be fine from a hardware standpoint, not sure what the phone will think of it though, I don't know if it does any kind of check.
Oh and every time I was turning it off and connecting to wall charger it would auto boot back to CWM then I would try to "reboot now" and it would fail and I did that continuously for a few hours sorta a manual boot loop lol glad I fixed it though even though it wasn't too broke
Sent from my MB865 using xda premium
dscott973 said:
Oh and every time I was turning it off and connecting to wall charger it would auto boot back to CWM then I would try to "reboot now" and it would fail and I did that continuously for a few hours sorta a manual boot loop lol glad I fixed it though even though it wasn't too broke
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yeah, Moto is finicky about having the battery somewhat charged, and will not usually let you fully boot without it in, I think I read in some document on the Motorola forum that it had to do with the bootloader, and it was a "safeguard".
Good to see you're back up and running
So I just got my phone today, rooted and installed the Viper rom. Then I installed the blackout kernel. It installed fine but it wont start up anymore. The phone won't go to bootloader or anything. I tried the 10 second power +volume down, ill get the screen that says htc one s this is a development phone and thats it. it turns off after that. When i plug the phone into a charger the light doesnt come up, i tried to use fastboot from my computer but it can't find the device since its not in fastboot. what should i do?!
This is odd. Even when you try turning the phone on with the volume down button depressed you can't get into bootloader? I've always been able to get to bootloader so this one is a challenge. I would make sure you have enough battery life in your phone too. Even if you have kernel issues you should still be able to make it back to bootloader. It should pop up instantly without any other boot screens. I imagine you can't see your phone from your computer with either adb devices or fast boot devices?
Sent from my HTC One S using xda premium
Are you sure you flashed the right kernel? I know quite a few Blackout kernels.
You did flash the boot.img, right? You can try flashing it again. If nothing works, try an RUU, or let the battery drain.
Are you sure you're trying to go into the bootloader the right way? The trick for me was to hold down only the power button, then once it goes off, hold down the volume down and the power button.
I remember the time another person had a similar issue, and managed to get in after about 30 tries.
Sent from my HTC One S using Tapatalk 2
usaff22 said:
Are you sure you flashed the right kernel? I know quite a few Blackout kernels.
You did flash the boot.img, right? You can try flashing it again. If nothing works, try an RUU, or let the battery drain.
Are you sure you're trying to go into the bootloader the right way? The trick for me was to hold down only the power button, then once it goes off, hold down the volume down and the power button.
I remember the time another person had a similar issue, and managed to get in after about 30 tries.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
thank you! that worked, i didnt flash the boot.img.. i forgot that part lol im used to having s-off where its so much simpler, but luckily i had a backup i could use. i know this is a dumb question but how do i install the kernel with boot.img?
deepshah420 said:
thank you! that worked, i didnt flash the boot.img.. i forgot that part lol im used to having s-off where its so much simpler, but luckily i had a backup i could use. i know this is a dumb question but how do i install the kernel with boot.img?
Click to expand...
Click to collapse
Go into fastboot in the bootloader. Then type fastboot flash boot boot.img in your Windows command prompt.
You should be able to extract the boot.img from the relevant zip file of your custom kernel. Then put that file (assuming its named boot.img) in the same folder as fastboot.exe
Hello
I have an s-off htc sensation with cm10 and recovery etc its been running great for ages with this setup.
The phone completely ran out of battery and shut down. I left it on charge overnight and in the morning it would not switch on.
I have read a LOT of threads on here and elsewhere about this issue and have tried the fixes you guys have suggested for similer issues (usb charging, new battery, battery pulls)
I dont think that the usb debugging mode was enabled on my phone so i cant use the commands to restart it etc
When charging, the orange light blinks for about 5 seconds, then is on constantly until the phone boots all on its own to the htc logo screen, then goes black with no orange light. (it did this with the old dead battery and the new one)
any help would be greatly appreciated
thanks
Such a great problem you have :crying: well, you can try re-flashing the ROM again. If it is not working maybe it is the ROM weakness. AOKP (your ROM series) is more unstable than AOSP ROM (like Android Revolution HD, ViperS, JB MIUI, and other).
The most possible reason for your problem is your ROM, so if re-flashing the rom does not help you, you can try flash a AOSP ROM. May the force be with you
When my advice helps you, try the THANKS button
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Device : HTC Sensation XE, S-ON
ROM : ViperS 1.52
Kernel : Bricked Kernel
Recovery : 4EXT Touch Recovery
MOD : jerrytan93 mod for ViperS ROM
Body : Little scratch because my sister dropped it thanks for my case, for covering
Very strange that a new battery didn't fix this... same thing happened to me but mine died while charging some how and I didn't even have a charging light! However, in my case a brand new battery fixed my issue instantly. You can try a new rom if you can somehow flash it and see if it helps.. one question, was the other battery you tired new? Just curious? Hope you can get this issue resolved. If the battery you tired wasn't new in last effort if nothing else works, try a new battery. Like I said, it worked for me.. I wish I could be of more help. Best of luck and keep us informed. I've read of this happening when battery is ran out before and I wish I knew what causes this.. very strange. Good luck
Sent from my HTC Sensation using xda premium
realsis said:
Very strange that a new battery didn't fix this... same thing happened to me but mine died while charging some how and I didn't even have a charging light! However, in my case a brand new battery fixed my issue instantly. You can try a new rom if you can somehow flash it and see if it helps.. one question, was the other battery you tired new? Just curious? Hope you can get this issue resolved. If the battery you tired wasn't new in last effort if nothing else works, try a new battery. Like I said, it worked for me.. I wish I could be of more help. Best of luck and keep us informed. I've read of this happening when battery is ran out before and I wish I knew what causes this.. very strange. Good luck
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Yup the battery was brand new off amazon....
Any ideas of how I can flash a rom without being able to boot into recovery?
Some one else might know this answer but have you tried, pulling battery, putting battery back in, immediately press power and volume down and hold it... recovery should pop up after that. Then go to wipe and wipe data factory reset, then install rom, or you can go to backup restore and restore your nandroid back up. Try to get into recovery this way. Hope it helps let me know. Best wishes. If you did try, couldn't hurt to try again keep hold of volume down and power and see if recovery will boot. If not you might be able to do it though computer but I can't help with that. Maybe someone else can help with fast boot commands on the computer. But it would hurt to try to pull battery again. And give it a go. Good luck
Sent from my HTC Sensation using xda premium
realsis said:
Some one else might know this answer but have you tried, pulling battery, putting battery back in, immediately press power and volume down and hold it... recovery should pop up after that. Then go to wipe and wipe data factory reset, then install rom, or you can go to backup restore and restore your nandroid back up. Try to get into recovery this way. Hope it helps let me know. Best wishes. If you did try, couldn't hurt to try again keep hold of volume down and power and see if recovery will boot. If not you might be able to do it though computer but I can't help with that. Maybe someone else can help with fast boot commands on the computer. But it would hurt to try to pull battery again. And give it a go. Good luck
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Thanks for helping but this isn't working either! If anyone knows how to boot into boot loader using a pc that would be very helpful.
harleyato said:
When charging, the orange light blinks for about 5 seconds, then is on constantly until the phone boots all on its own to the htc logo screen, then goes black with no orange light.
Click to expand...
Click to collapse
i assume it stays on at least after booting
if yes then connect it to pc
go to the folder where you have adb and fastboot files and open a command window there
then do
adb
adb devices
adb reboot bootloader
see if it works
rzr86 said:
i assume it stays on at least after booting
if yes then connect it to pc
go to the folder where you have adb and fastboot files and open a command window there
then do
adb
adb devices
adb reboot bootloader
see if it works
Click to expand...
Click to collapse
No the phone screen just goes black after the HTC screen and sometimes randomly flashes grey!? So the computer cannot detect it when connected by usb .
Really need to get to recovery it seems
This happened to me the other day, I have a charger that came with the battery off amazon and I gave it a full charge on that. After I put it in fully charged my phone was fine. I was nearly fully through flashing when this happened. I got back to bootloader and flashed 4ext recover and flashed my rom.
Charlie3999 said:
This happened to me the other day, I have a charger that came with the battery off amazon and I gave it a full charge on that. After I put it in fully charged my phone was fine. I was nearly fully through flashing when this happened. I got back to bootloader and flashed 4ext recover and flashed my rom.
Click to expand...
Click to collapse
Cool could you post a link? Thanks
harleyato said:
Cool could you post a link? Thanks
Click to expand...
Click to collapse
http://www.amazon.co.uk/1900mAh-Bat...K7YS/ref=sr_1_3?ie=UTF8&qid=1356828192&sr=8-3