Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed johnance17's unbrick guide on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
The phone is unbricked and operational if the charger is plughed in, when I unplugh the charger, the phone says, that the battery is empty, and turn itself off, and will not charge.
So, can someone help me what went wrong, why won't any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
See my post in the other thread.
Sent from my LG-P920 using XDA Premium App
hefonthefjords said:
See my post in the other thread.
Sent from my LG-P920 using XDA Premium App
Click to expand...
Click to collapse
I've tried, but no luck, unfortunately..
I was able to flash 10b without brick, but but had battery issues like you described. I thinks its a flaw in the build. I just installed King_3d_rom_v1.2 ROM which is in the developer section of these forums and it works well and has apparently solved my battery issues. ...probably worth a shot! (Good Luck!)
I tried to flash King_3d_rom_v1.2 ROM but still, battery is still at zero(0) level.
@freez76, What ROM were you using before resolving your battery issue?
Did you do a full wipe before flashing (cache, data, dalvik)? I was on 10b when I was having battery problems. I am now on 10d with King and not only its my battery working again, but its better than it was on the May version of the stock ROM. ...I should also point out that I am on a developer version of the phone.
Sent from my LG-P920 using XDA App
I have same problem to you. My first rom is LGP920-V08i-APR25-2011. I upgraded it with V10b_00.kdz. However the O3D turned off after booting. If I connect with USB cable, it is working well. but battery level is zero. Do you have same firmware at the first time???
Yepp, I've unbricked it by installing the v10b fw.
Tried the kingdom rom with wipeing everything, but still the same. :S
Have you backed up original rom??? I didn't..... So I didn't use o3d until now... If anyone has the old rom,. pls post it... Thanks.
@freez76
Is the 10b fw you had with battery problem the one from Fabio's post? When you flashed it, did you wait for the O3D to restart itself after reaching Param 100 in kdz_updater?Would it be possible for you to upload a backup copy of your currently working ROM (King) and share it with us who are having battery problem?...Thanks in advance.
@freez76
I hope so.... Pls Help us freez76... Thanks
@dnardz
Yes, it was the 10b update from fabio's thread, but the update was from gpx. From what I remember the update took awhile, but eventually completed normally. However, the battery seemed completely messed up after the first discharge.
I am attaching a link to my wiped fresh backup (which will need to be unzipped) of my o3d with KingROMv1.2 installed. Its the same restore backup method that gpx used. Just a note, I am using CWM 4.0.0.9. Please check your version and update if its not the same. I hope this helps....Good luck!
http://www.megaupload.com/?d=14NUM2GD
Many thanks Freez76...I'll give it a try now...
Thanks Freez76. However it is not working at my O3D.... How about dnardz and Zirowe????
Sad to say,it didn't work also on mine.. i think i'll try to flash 10b again,..then apply the June update as Freez76 did, and then update using King's rom.otherwise we'l have to wait for an official flashing program ang maybe a gingerbread rom to come out.by the way im also using prototype model.
dnardz said:
Sad to say,it didn't work also on mine.. i think i'll try to flash 10b again,..then apply the June update as Freez76 did, and then update using King's rom.otherwise we'l have to wait for an official flashing program ang maybe a gingerbread rom to come out.by the way im also using prototype model.
Click to expand...
Click to collapse
I am using prototype model too, and I got the same problem, I was stuck in cmv, after unbrink i am having problems with battery, but in my case, the problem is worse, i can't use the phone even with usb or using the charger, i will try other ways to solve this problem, i will post results later, if anyone has a suggestion, please, help us!!!!
modernbruce said:
Thanks Freez76. However it is not working at my O3D.... How about dnardz and Zirowe????
Click to expand...
Click to collapse
Well, I'm still stuck, I'm out of town now, will give it another try on tuesday.
Not ideal I know but at least you will be able to charge the batteries again as well as having 2 spares. I use one of these and they work very well.
http://www.ebay.co.uk/itm/Q590-2X-B...328?pt=LH_DefaultDomain_3&hash=item35b1e4f6e0
Pete
mad_sunday said:
Not ideal I know but at least you will be able to charge the batteries again as well as having 2 spares. I use one of these and they work very well.
http://www.ebay.co.uk/itm/Q590-2X-B...328?pt=LH_DefaultDomain_3&hash=item35b1e4f6e0
Pete
Click to expand...
Click to collapse
I've already tried two other batteries with the same result, so it's not a solution for me.. :S
The idea is that you can charge the batteries with the stand alone charger, not that you get other batteries to charge in the phone.
Sent from my LG-P920 using XDA App
Related
Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?
iglu said:
Recently my Nexus s started bootlooping.
First it was happening if the phone was powered off due to finished battery, now it happens every time i power it off.
What happens is, it bootloop on the google logo. In order to over come that i pull the battery out and turn it back on. After a few time (3-10) it would start up normally and not bootlooping.
I run stock 4.0.3, not rooted.
Anyone has a clue ?
Click to expand...
Click to collapse
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
You think it might be a result of ICS upgrade ?
iglu said:
What is lost on factory reset ? only the OS and installed apps, no SD data right ?
You think it might be a result of ICS upgrade ?
Click to expand...
Click to collapse
Yes factory data reset only deletes all data on your phone not the SD card.
Sent from my Galaxy Nexus using xda premium
simms22 said:
my only suggestion is maybe a factory reset, you might have some corrupted files somewhere. but, my fear/concern is that your internal sd storage card might be going.
Click to expand...
Click to collapse
TheMatrix246 said:
And if a factory reset didn't work, I think you'll have to use ODIN to flash stock 2.3.6 ...
Click to expand...
Click to collapse
Okay, so i did factory reset and i'm still stuck on the bootloop. Need to remove the battery and turn back on until it doesn't bootloop.
Actually what happens is the google logo appear, then for a moment it turned off and comes back again.
simms22, why do you think it's internal sd damage ?
TheMatrix246, what's ODIN ?
Guys, you think if i root and switch ROM it could be fixed ?
I would appreciate some help here a bit lost.
One last thing before you contact Samsung:
Download Nexus S [i9020T/i9023] 4.0.3 Full ROM and copy to sdcard as update.zip
Go into bootloader
Recovery
Data/factory reset
Install update.zip (reflash all files of ICS)
Reboot and hope it works out fine
If this doesn't work for you i highly doubt rooting and changing ROMs will. This will reinstall the entire OS (format and install /system), bootloader, radio, kernel and recovery.
Do i need to be root user in order to do that ?
And just to make sure, this Full ROM is for i9020T ? correct ?
(mine says only GT-i9020 on the back, bought in Carphone Warehouse in England).
Yes, i9020T. If you get 3G with Orange, and you have the SAMOLED screen, you have the i9020T (and to my knowledge, 9020 on the back signifies i9020T).
Also, i don't believe you need to be root to do that. I'm pretty sure you can flash the same version ROM from stock recovery as long as it is signed, just not older versions.
First, thanks guys for the help.
After first doing the factory reset, it seemed the bootloop happens less often. At first i tought it was solved but then it rarely (1 to 5 reboots) yet happened.
Today i installed the Full ROM Harbb suggested and so far i have no reboot issues.
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?
iglu said:
First, thanks guys for the help.
...
...
...
But i after the installation i saw OS wasn't reset. Does it suppose to (not) happen ?
Click to expand...
Click to collapse
You're welcome. Also, all that file does is replace everything in the /system partition (OS). All apps besides the defaults that come from the factory are not in that partition so are not affected. Hopefully your problem is fixed permanently
But it's generally recommended to do a full wipe when switching ROMs. It could be that you encounter other problems because of the ROM change without wipe. But you could also be lucky to have no problems. Just to remind you, when you encounter something wierd.
Problem is still there ....
Hi guys,
First thanks for all the help, but the problem still there.
I did the upgrade using the Full ROM as Harbb suggested. For the first 10-12 times i rebooted (i rebooted again and again) it was alright, booting successfully ... but then it stated occasionally to bootloop and now it does it almost everytime. usually takes up to 10 times i remove the battery and start the phone so it will start up and not bootloop.
Also, I'm sorry the taking so long to respond, the nature of the problem compelling me to test it for a few days so i will know if it works or not.
Should i root the device ?
If so , how do i replace / rewrite the boot program ?
I would much appreciate any suggestion.
I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.
BlatDinger said:
I had a similar problem, bootlooping, stuck on Google logo when running 4.0.3 in the end I took it back to carphone warehouse who repaired it and now it's ok. I found that heating it with a hair-dryer made it stop bootlooping (but that's what worked for me). However the repair seems to have fixed any issues and its all OK now.
Click to expand...
Click to collapse
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?
iglu said:
My problem is i bought the device also in carphone warehouse in the UK, but i live in Israel. Meaning i will have to send it to them by air-mail.
By any chance they mentioned what was the problem ?
also did they give you a refurbished device or a new one ?
Click to expand...
Click to collapse
Most likely its a refurbished one, as is the way of sending devices for warranty
Sent from my ice cream powered Nexus S
Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium
BlatDinger said:
Sorry for slow reply - they said they 'flashed it' and it came back unlocked but I believe its still the same handset and I've no idea how they did it soz.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Hey, thanks for the replay.
What does is mean to flash it ?
How do i do that ?
You noted it was returned unrooted, was it rooted before ?
Again thank you all for the help.
To be honest I'm a novice to these terms but know that they unlocked it(it was not unlocked when sent off) and reinstalled os 2.3.3 after a complete wipe. Details of how to unlock and flash (install a different os) are on the forums. If you follow the forum advice precisely the instructions work. I am now running a CyberGR rom of ics 4.0.3 that runs smoother than stock ics . Again found on these forums. Hope this helps.
Sent from my Nexus S using xda premium
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
renehd2 said:
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
Hi... I once had a similar problem late last year. My phone kept rebooting randomly, sometimes as soon I switch the phone on, or data like yourself. What I did was.... Installed the official RUU that came on my phone (O2) and the rebooting stopped. But I felt the need to send it back anyway, so I did and just as well, because HTC replaced the mainboard and a few other things. I hadn't overclocked or anything either so it was a strange one.
This way worked for me, so give it a go.
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
MANTI5 said:
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
Click to expand...
Click to collapse
When you say rooted and unrooted what exactly did you do?? Meaning did you HTC unlock or use revolutionary to s-off? And what recovery did you use? Because in actuality all root is, is the su binaries and the su app, not the process of gaining the access. There are inherent problems with the htcdev unlock and using cwm as your recovery. Even if you delete su the remnants of either process could possibly cause problems. Did you return to s-on again?? Because that will cause serious issues if you don't have the correct ruu. Did you flash any newer firmwares??? The few before .32 did cause loops without the correct rom.
Also in your case it sounds like a rogue app causing loops because it boots up after a battery pull. Have you tried to factory reset and wipe your data to see if that helps??
Sent from my Sensation using xda premium
renehd2 said:
guys I have a serious problem..!!
I was in 5.1.8 everything was fine non a problem and when 5.5 came out I installed it, super wipe script, and install the Rom; I was getting a lot of boot loops. Reinstall the ROM again full wiping, ans still the same. I came back to 5.1.8 and I'm still having boot loops but not that often like it was in 5.5, now I have boot loops when turn on the data or when I try to make a call... I really don't know what could be the problem because I have installed hundreds of roms with the same steps and everything was fine,.I don't know what could be the problem...
I hope someone could help me thanks a lot
from my HTC Sensation XE with Beats Audio using xda premium
Click to expand...
Click to collapse
it's maybe hardware failure in first place but after doing battery thing it was fine
go here and try battery fix thread plzzz post back and vote in first thread
MANTI5 said:
I rooted my phone, then unrooted without ever installing a custom rom. I have gotten boot loops ever since and seemingly random shut downs that require me to take out the battery and put it back in before the phone will boot up again. Happens every day, several times a day.
Click to expand...
Click to collapse
it's a battery thing go here and try battery fix thread plzzz post back and vote in first thread
Used Revolutionary, not sure what I used to put it back as it's been a while but I followed a guide from here. I'm trying the card piece trick so we'll see if it does anything.
Pm me if your soff I can help easy
Sent from my Sensation using xda premium
Thanks but not s-off anymore and just got another reboot so I doubt it's the battery. I guess I'll try to deal with it until ICS and see if that fixes anything. If not then I guess I'll try something more drastic.
Well get soff you can't fix with out it
Sent from my Sensation using xda premium
Ok, got s-off again.
It seems to have something to do with going in and out of service or switching between wifi and cell service. But that could just be a coincidence.
Anyone have ideas on how to fix this? I got the OTA ICS and I'm still getting reboots.
MANTI5 said:
Anyone have ideas on how to fix this? I got the OTA ICS and I'm still getting reboots.
Click to expand...
Click to collapse
it's a battery thing go here and try battery fix thread plzzz post back and vote in first thread
it won't hurt ur phone u must stick a tape to close the gap between batt pins and connectors do it and see it easy but worth allot
Tried that earlier in this thread and it didn't help.
Anyone else?
Well guys after reading I fixed my problem cleaning the little panels in the battery, and also installing another rom, seems like the htc sense roms have some problems with that because since I install a senseless rom (not aosp) the problem is gone
Sent from my HTC Sensation using xda premium
I think you did not unroot properly. Can you please describe the process you used for unrooting?
Don't remember what guide I used to unroot as it was a while back. It definitely seems to have something to do with the signal. It will lose signal, reboot, get pretty warm and repeat while sometimes just shutting off and needing the battery pulled and put back before it will turn back on. My wife will have a signal just fine in the same areas mine loses them.
Very frustrating because I'm missing a lot of calls and txts because it'll just shut down.
MANTI5 said:
Don't remember what guide I used to unroot as it was a while back. It definitely seems to have something to do with the signal. It will lose signal, reboot, get pretty warm and repeat while sometimes just shutting off and needing the battery pulled and put back before it will turn back on. My wife will have a signal just fine in the same areas mine loses them.
Very frustrating because I'm missing a lot of calls and txts because it'll just shut down.
Click to expand...
Click to collapse
First make a NANDROID backup now. Then try rooting again to see if that fixes the issue.
If not, try to flash a different Radio. I would in your case also suggest wiping all partitions except SD card and re-installing the ROM, after flashing the radio.
Yesterday my Droid Charge running Tweaked 3.2 would not boot, it would get past the samsung logo and start the boot animation and then turn off. Booting into recovery, several things were not mounting, was not able to wipe Dalvik cahce, only regular cache.
When I try to ODIN back to stock with PIT, it always fails on movinand.bin
I used Samsung PSTLite as well with the same result, failing on movinand.bin
I have tried flashing to ED1 and EP4.
I can flash ROMS such as Tweaked that do not have movinand.bin, but the phone does not start up at all afterwards.
Download mode still works.
What can I do??
LethalMonk6 said:
Yesterday my Droid Charge running Tweaked 3.2 would not boot, it would get past the samsung logo and start the boot animation and then turn off. Booting into recovery, several things were not mounting, was not able to wipe Dalvik cahce, only regular cache.
When I try to ODIN back to stock with PIT, it always fails on movinand.bin
I used Samsung PSTLite as well with the same result, failing on movinand.bin
I have tried flashing to ED1 and EP4.
I can flash ROMS such as Tweaked that do not have movinand.bin, but the phone does not start up at all afterwards.
Download mode still works.
What can I do??
Click to expand...
Click to collapse
Have you tried a data wipe/factory reset via cwm?
Sent from my XT907 using xda app-developers app
Yes, I can flash and boot into CWM, but wiping factory data does not do anything, it also shows multiple "error mounting such and such" messages
jco23 said:
Have you tried a data wipe/factory reset via cwm?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Try to re-PIT only.
Sent from my SCH-I510 using xda premium
What am I supposed to do after re PIT'ing? (which I have done, sucessfully)
Then flash any ROM, probably a stock one. Make sure the MD5 is good. Tell us your exact process for Odin-ing something.
Sent from my SCH-I510 using xda premium
This is what I have been doing the whole time, same result.
I know my process for ODIN'ing to be correct, battery in, SD card out, PDA checked only.
Its something other than that, I've flashed return to stock many times in ODIN before...
Is there something else I can do besides simply ODIN'ing, as I've said, I've tried ODIN and PST Lite, both failing at movinand.bin
When flashing straight to for example Tweaked, it works fine, as there is no movinand.bin
At this point, it does not even show the samsung logo anymore, the screen just quickly flashes for a moment and then turns off. Download Mode is still working though. Recovery does not boot either.
Correction, CWM does boot, but none of the partitions are mountable.
Umm, The same exact thing happen to me couple of weeks ago, I got tons of error about mounting. I know I am not helping, but I gonna say my case anyway. I tried PIT (repartition) several times, didn't work! It was random! it worked one time, and I was able to flash the pit, but when I tried to flash the EP4D didn't work! I only was able to get to the home 2 times and got tons of force-closing warnings. I have insurance, so I got a replacement. I hope you are covered as well! Just wanted to share
A fail at movinand indicates a corruption at a hardware level. I've actually pulled mine out of death (had the same issue once upon a time) just by spamming PST over and over again but I seem to be the only one who had ever succeeded in that. You're probably going to have to end up getting a new device but hey, they won't be able to tell you rooted.
Sent from my SCH-I510 using xda premium
kvswim said:
A fail at movinand indicates a corruption at a hardware level. I've actually pulled mine out of death (had the same issue once upon a time) just by spamming PST over and over again but I seem to be the only one who had ever succeeded in that. You're probably going to have to end up getting a new device but hey, they won't be able to tell you rooted.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
At this point it won't even matter. My phone broke like this and I got it switched in on the last day of warranty (luckily), and that was in August.
one last check:
have you tried using a different USB cord/USB port/different computer? I, along with many others, have experienced issues when flashing via odin with a bad cord/port (even though it had worked before). when I switched cords, it worked. but this mostly happens when the computer/ODIN fails to recognize the phone.
also, I did not remove the SD card in any of my flashings. I think once, I did remove the battery just to get the phone into download mode.
oh, and another option could be the kernel/partition/boot animation you were last on. I would recommend to try to make sure you are on RFS with stock FP5 before flashing anything.
but i suspect kvswim is probably right.
hope this helps.
ok, thanks for the help guys. I'm quite sure I dont even have a warranty on my phone, so that sucks. Might try to go into Verizon and see what happens anyway.
Do you think its worth sending it to MobileTechVideos for them to debrick, or is this outside of what they do, since it still can go into Download mode...
LethalMonk6 said:
ok, thanks for the help guys. I'm quite sure I dont even have a warranty on my phone, so that sucks. Might try to go into Verizon and see what happens anyway.
Click to expand...
Click to collapse
The phone comes with a 1 year warranty.
Sent from my SCH-I510 using Tapatalk 2
So I decided to go ahead and put my findings of this issue that several of us have had with our phones getting the dreaded "Battery Disconnect" after upgrading from stock ICS to stock JB. I cannot guarantee that this will work for everyone but it did work for me.
Here are the different solutions I have come across in my research on this issue.
1: Battery corruption: get new battery
2: Gold prongs are dirty on phone and battery: clean them
3: Bad charger: get new charger
4: Dirt or dust in USB port: clean with compressed air
Now I tried each of these and unfortunately none worked for me. It has for some that I have read on different sites, so if you don't want to try and re-flash everything try those above.
For those that have tried each of above 4 and still have the issue, like myself, you can try the following. This worked for me, but you have to have patience. Read entire post before trying, check MD5 sums before any flashing and the typical disclaimer, I AM NOT RESPONSIBLE FOR YOU PHONE, TRY AT OWN RISK. Sorry, had to put that in.
1. Have your battery charged to 100%. You need to go back to ICS if you aren't already. If you are on JB right now, wipe your system clean (factory reset) that's including formatting system, data, cache, dalvic, etc. using CWM (that's just what I prefer for this part and what I used). Do a backup first of anything you don't want to lose. I used Titanium Backup Pro myself but pick your own poison. If already on ICS, proceed to step 4.
2: Using ODIN, flash ICS back on to your phone. If you haven't already looked at Vincom's guides, here you go. http://forum.xda-developers.com/showthread.php?t=1652398 and http://forum.xda-developers.com/showthread.php?t=1785999. Keep it plugged into the computer while it reboots. Should show battery charging. If not, do it over. DO NOT ADD CUSTOM RECOVERY AND ROOT.
3: Test all your chargers. Generic and OEM and any additional batteries you may have. Make sure they all work. If so, let it settle for about 10 minutes and then on to the next step.
4: Power off the device and boot into the stock recovery. Do a factory reset, choose reboot and when the phone powers off, take out your battery.
5: Now using ODIN, flash stock JB. Again, leave the phone plugged into the computer until it boots completely. As long as it is charging and not "Battery Disconnect" you're on the right track. If it does not boot, basically just sits on the AT&T symbol for an extended period of time which can happen, remove battery, reboot into stock recovery, factory reset and re-flash JB again. If it says "Battery Disconnect" after it boots, wipe, and re-flash JB again. DO NOT INSTALL CUSTOM RECOVERY OR ROOT YET. I did on my first attempt of these steps and immediately got the "Battery Disconnect". If you succeeded, on to the next step.
6: This is when your patience comes to affect. You need to let the phone settle. I gave mine 2 days of using and charging when dead without getting the "Battery Disconnect". It happened once after a full charge, but only once. I plugged it in while half charged to see what happened and it popped up. Later when it died and I plugged it in, it charged with no problems. Patience. Something about the drivers taking time to settle either in the rom itself or in the kernel for certain devices. Not sure which. I did re-install my apps but I did with using the Play Store and not with my backup. Make sure you are on Wi-Fi so you don't jack up your data usage.
7: Now that you have had two days of using and charging with no issues, fingers crossed, go ahead and install TWRP using ODIN (no wipes needed). After it reboots, again keep it plugged into the computer and if it is charging after boot without the dreaded phrase, CONGRATULATIONS! BUT, I would wait for at least one day before you try any custom roms on it. Again, let it settle first.
I know this is a lot. But again, this is what worked for me after trying for almost two weeks now to find a solution. Good luck everyone, I hope this works for you as well. And thank you Vincom for the guidance.
Thanks! I will try this perhaps if my attempts to return the device fail...
The other thing I am wondering is if anyone that has had this issue has tried going "the long way around" to upgrade... be on ICS, flash TWRP/CWM, then (assuming everything is OK), flash just the JB radios and a custom JB based AOSP ROM and ignore the full ODIN of official JellyBean if the result would be better?
acejavelin said:
Thanks! I will try this perhaps if my attempts to return the device fail...
The other thing I am wondering is if anyone that has had this issue has tried going "the long way around" to upgrade... be on ICS, flash TWRP/CWM, then (assuming everything is OK), flash just the JB radios and a custom JB based AOSP ROM and ignore the full ODIN of official JellyBean if the result would be better?
Click to expand...
Click to collapse
I still had issues with doing that as well. Try though. If it works then let me know and I'll put as another solution in the OP.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I will let you know, will probably be next week before I get a chance to look at it again.
BTW, I sent an email to tech support, explaining that I used nothing but the stock firmware images and the issues I had... here is there "official" response:
Dear Steve ,
Thank you for contacting Samsung Telecommunications America.
After reviewing your e-mail we understand that, you have updated the device to Jelly Bean and the battery was not charging and you have installed stock ROM of Ice Cream Sandwich.
As we see that, you have rooted the device, we would like to inform you that, rooting the phone will void the warranty. We also would like to inform you that, as the phone is not taking a charge, the device need to be physically examined by the service technicians to reflash the software on the phone. Hence, we request you to contact our voice team, they will assist you further regarding the query.
You can contact our voice support at 1-888-987-4357, Mon-Fri: 7 AM - 9 PM (CST), Sat: 9 AM - 6 PM (CST).
If you have a minute, please click on the “Start survey here” link at the bottom of this email to fill out a brief survey to help us serve you better. Kindly note that you can access the survey page only when the pop-up blocker is disabled on the browser. Have a wonderful day!
Should you have more questions regarding your Samsung Mobile Phone, you can reach out to our chat support team by accessing the following link. Live Chat is available 24 hours a day 7 days a week. Have a wonderful day!
Link: http://www.samsung.com/us/support/contact
Thank you for your continued interest in Samsung products.
Sincerely,
Michelle
Technical Support
Click to expand...
Click to collapse
Basically, it's "Well, too bad... Send it in and we will fix it, for a price!" Thanks Samsung!!!
Yep, that sounds about right.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Changing radios to UCMC1 and installing TWRP recovery and rooting had no effect, with an ICS ROM the battery charges properly.
So this clearly seems to be kernel related with the JellyBean code of the kernel and how it is talking to the hardware, the stock kernel and Marla kernel have the same result... I tried Beanstalk 1.300.3 (Wrap-up 3) and the battery would not charge, in the *#*# menu under battery it showed the exact same thing, "Unknown error" and would not charge. Restore back to ICS from TWRP and everything was OK again. Think I will wait to see how it goes after I get an real Samsung battery, about 95% sure this battery is a fake, but in reading similar discussions on this with SGS2 models, the battery doesn't seem to be the issue but it's worth a shot. I might try a few ICS ROMs and see what happens and report back now that I know restoring back to stock ICS via TWRP is a fix for the problem.
UPDATE EDIT: Well, the seller who sold me this phone, phonesandparts.com on eBay has agreed to take back the device and give me a full refund. Guess I will just do that and now that the Nexus 4 has dropped a $100 on price I can get a Nexus 4. I am tired of messing around with this, I love the device but not being able to flash anything is annoying as all get out, it might be fake, defective, or whatever, but guess I am moving on, just waiting for the RMA then I will have to move back to my old HTC Aria for a while and just deal with it for now and once my refund comes through grab a Nexus.
I flashed my i727 with JB rom, and after do that i recive that message when i tried charge my cell phone, so the sollution was install a Stock rom with odin and go back to ICS every time i try ti update my cellphone with any rom i get that message... but at least i can charge my cellphone again... i write this reply this post because it works for me, and if you had the same problem maybe this can be the solution...
---------- Post added at 11:07 AM ---------- Previous post was at 10:41 AM ----------
acejavelin said:
Changing radios to UCMC1 and installing TWRP recovery and rooting had no effect, with an ICS ROM the battery charges properly.
So this clearly seems to be kernel related with the JellyBean code of the kernel and how it is talking to the hardware, the stock kernel and Marla kernel have the same result... I tried Beanstalk 1.300.3 (Wrap-up 3) and the battery would not charge, in the *#*# menu under battery it showed the exact same thing, "Unknown error" and would not charge. Restore back to ICS from TWRP and everything was OK again. Think I will wait to see how it goes after I get an real Samsung battery, about 95% sure this battery is a fake, but in reading similar discussions on this with SGS2 models, the battery doesn't seem to be the issue but it's worth a shot. I might try a few ICS ROMs and see what happens and report back now that I know restoring back to stock ICS via TWRP is a fix for the problem.
UPDATE EDIT: Well, the seller who sold me this phone, phonesandparts.com on eBay has agreed to take back the device and give me a full refund. Guess I will just do that and now that the Nexus 4 has dropped a $100 on price I can get a Nexus 4. I am tired of messing around with this, I love the device but not being able to flash anything is annoying as all get out, it might be fake, defective, or whatever, but guess I am moving on, just waiting for the RMA then I will have to move back to my old HTC Aria for a while and just deal with it for now and once my refund comes through grab a Nexus.
Click to expand...
Click to collapse
I bought the same cellphone at the same seller and i have problems with the imei: null/null and i search here and maybe they flashed the cellphone with a new rom and lose the files of the EFS folder, so i cant unlock and use with my service network.. i will ask for a return item.
That's rotten luck for both of you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Well, the seller took back the phone, and issued me a full refund, so this is probably going to be one of my last posts in the Skyrocket forums since I am using those funds and ordered a LG/Google Nexus 4 16GB phone. I really liked the SR and would have kept it had it worked as I had hoped, but with all the issues I had I just figured this was a better way go than fighting with another one since Google dropped the price a $100 on the Nexus. Thanks for the help to everyone, enjoy your Skyrocket.
dgoby said:
So I decided to go ahead and put my findings of this issue that several of us have had with our phones getting the dreaded "Battery Disconnect" after upgrading from stock ICS to stock JB. I cannot guarantee that this will work for everyone but it did work for me.
Here are the different solutions I have come across in my research on this issue.
1: Battery corruption: get new battery
2: Gold prongs are dirty on phone and battery: clean them
3: Bad charger: get new charger
4: Dirt or dust in USB port: clean with compressed air
Now I tried each of these and unfortunately none worked for me. It has for some that I have read on different sites, so if you don't want to try and re-flash everything try those above.
For those that have tried each of above 4 and still have the issue, like myself, you can try the following. This worked for me, but you have to have patience. Read entire post before trying, check MD5 sums before any flashing and the typical disclaimer, I AM NOT RESPONSIBLE FOR YOU PHONE, TRY AT OWN RISK. Sorry, had to put that in.
1. Have your battery charged to 100%. You need to go back to ICS if you aren't already. If you are on JB right now, wipe your system clean (factory reset) that's including formatting system, data, cache, dalvic, etc. using CWM (that's just what I prefer for this part and what I used). Do a backup first of anything you don't want to lose. I used Titanium Backup Pro myself but pick your own poison. If already on ICS, proceed to step 4.
2: Using ODIN, flash ICS back on to your phone. If you haven't already looked at Vincom's guides, here you go. http://forum.xda-developers.com/showthread.php?t=1652398 and http://forum.xda-developers.com/showthread.php?t=1785999. Keep it plugged into the computer while it reboots. Should show battery charging. If not, do it over. DO NOT ADD CUSTOM RECOVERY AND ROOT.
3: Test all your chargers. Generic and OEM and any additional batteries you may have. Make sure they all work. If so, let it settle for about 10 minutes and then on to the next step.
4: Power off the device and boot into the stock recovery. Do a factory reset, choose reboot and when the phone powers off, take out your battery.
5: Now using ODIN, flash stock JB. Again, leave the phone plugged into the computer until it boots completely. As long as it is charging and not "Battery Disconnect" you're on the right track. If it does not boot, basically just sits on the AT&T symbol for an extended period of time which can happen, remove battery, reboot into stock recovery, factory reset and re-flash JB again. If it says "Battery Disconnect" after it boots, wipe, and re-flash JB again. DO NOT INSTALL CUSTOM RECOVERY OR ROOT YET. I did on my first attempt of these steps and immediately got the "Battery Disconnect". If you succeeded, on to the next step.
6: This is when your patience comes to affect. You need to let the phone settle. I gave mine 2 days of using and charging when dead without getting the "Battery Disconnect". It happened once after a full charge, but only once. I plugged it in while half charged to see what happened and it popped up. Later when it died and I plugged it in, it charged with no problems. Patience. Something about the drivers taking time to settle either in the rom itself or in the kernel for certain devices. Not sure which. I did re-install my apps but I did with using the Play Store and not with my backup. Make sure you are on Wi-Fi so you don't jack up your data usage.
7: Now that you have had two days of using and charging with no issues, fingers crossed, go ahead and install TWRP using ODIN (no wipes needed). After it reboots, again keep it plugged into the computer and if it is charging after boot without the dreaded phrase, CONGRATULATIONS! BUT, I would wait for at least one day before you try any custom roms on it. Again, let it settle first.
I know this is a lot. But again, this is what worked for me after trying for almost two weeks now to find a solution. Good luck everyone, I hope this works for you as well. And thank you Vincom for the guidance.
Click to expand...
Click to collapse
After step 4 I guess I need to put the battery back in before proceeding with 5 and ODIN right?
djandreski said:
After step 4 I guess I need to put the battery back in before proceeding with 5 and ODIN right?
Click to expand...
Click to collapse
Follow Vincom's steps to use Odin. Step 2. It will tell you when to put the battery back in.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So have you tried installing custom ROM like CM 10.2 or 10.1?
Does it charges properly?
djandreski said:
So have you tried installing custom ROM like CM 10.2 or 10.1?
Does it charges properly?
Click to expand...
Click to collapse
Until I did the novel I wrote above, nothing worked. Either it was an immediate disappointment or wouldn't work after the first charge. Since then the phone has worked perfectly with any rom. Even an aftermarket battery. I don't want to put "solved" in the OP until I get feedback from others that it worked for them as well.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I repeated the step 5 three times and every time the same. Right after reboot I get "Battery disconnected" error message. I re-flashed JB, as I said 3 times but every time i see that error.
So I don't know if I can continue and use my phone until full discharge, I am afraid that I can't charge the battery back, and revert to ICS.
djandreski said:
I repeated the step 5 three times and every time the same. Right after reboot I get "Battery disconnected" error message. I re-flashed JB, as I said 3 times but every time i see that error.
So I don't know if I can continue and use my phone until full discharge, I am afraid that I can't charge the battery back, and revert to ICS.
Click to expand...
Click to collapse
I have to ask of course, did you follow everything exactly? I.e. not rooting or installing custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dgoby said:
I have to ask of course, did you follow everything exactly? I.e. not rooting or installing custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Of course, just plain stock JB ROM.
UPDATE:
Here is what I did. I used stock ICS for about a day, then I updated it with Kies, just to try my luck, and as you guess that stupid error poped up.
I continued from step 5 , so I reboot in recovery, did factory reset and install stock JB ROM with ODIN
djandreski said:
Of course, just plain stock JB ROM.
UPDATE:
Here is what I did. I used stock ICS for about a day, then I updated it with Kies, just to try my luck, and as you guess that stupid error poped up.
I continued from step 5 , so I reboot in recovery, did factory reset and install stock JB ROM with ODIN
Click to expand...
Click to collapse
Instead of using Kies I would use only Odin. I know you're running low on battery but I would start over but charge it up while on ICS. I was only successful using Odin in this process.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I recently upgraded to the 4.22 PAndroid ROM, however, I'm having a battery problem. Furthermore, this problem followed me when I switched over to the 4.22 CM ROM.
When I plug in my charging cord (OEM; have tried computer and wall plug), the phone charges for about 5 seconds before ceasing to charge. However, it charges fine if the phone is off. I've tried wiping the cache/factory resetting on both ROMs, but that didn't solve the problem either.
When I flash back to my current ROM, 4.12 PAndroid, the problem goes away completely and it charges on everything exactly as it should.
If anyone has any idea, I'd love to finally be able to use 4.22.
Thanks!
EDIT: I've used two different OEM cords, so I'm fairly certain it's not a hardware issue. Just to clarify.
Bump
Sent from my SAMSUNG-SGH-I727 using Tapatalk
SlushySolid said:
Bump
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Bump again.
I've tried about 5 ROMs now. This is super frustrating because my current ROM will randomly stop receiving texts, and I don't know how to fix that. I would really appreciate any advice I can get about why I can't install a new one. My install order is:
Backup, Wipe Data, Wipe Cache, Wipe Dalvik, Format /system, ROM, GApps, Reset.
Even changing the kernel doesn't fix this problem.
Which recovery and version are you using? Try updating the recovery
jd1639 said:
Which recovery and version are you using? Try updating the recovery
Click to expand...
Click to collapse
CWM, just updated to the newest (6.0.4.3). Still not charging
Multiple problems(charging,texting) that you can't solve? Best bet would be to Odin back to stock, complete wipes and proceed from there.
jondroid2 said:
Multiple problems(charging,texting) that you can't solve? Best bet would be to Odin back to stock, complete wipes and proceed from there.
Click to expand...
Click to collapse
So, I did that this afternoon. Basically went back to stock, redid the recovery, and then flashed another ROM. It still wouldn't charge properly. Then, when I reverted back to stock (from a backup I did before the flash) I started getting warning pop ups with "Battery Disconnected." Now, even stock won't charge my phone, and now that it's dead, it won't charge when it's off either.
I'm beyond confused about where to go from here, and I'm very frustrated with my Skyrocket. I'm almost at the point of just jumping ship to a Nexus 5 haha. I would hate to waste about tree fiddy though if this is something that is still fixable.
SlushySolid said:
So, I did that this afternoon. Basically went back to stock, redid the recovery, and then flashed another ROM. It still wouldn't charge properly. Then, when I reverted back to stock (from a backup I did before the flash) I started getting warning pop ups with "Battery Disconnected." Now, even stock won't charge my phone, and now that it's dead, it won't charge when it's off either.
I'm beyond confused about where to go from here, and I'm very frustrated with my Skyrocket. I'm almost at the point of just jumping ship to a Nexus 5 haha. I would hate to waste about tree fiddy though if this is something that is still fixable.
Click to expand...
Click to collapse
go back to stock w/odin and see if prob persists, don't use ur backups and don't flash anything else, just stay on stock.
if jb stock fw fails then try stock firmware gingerbread and ics and test each one w/out flashing anything else, stay on pure stock.
some users did have issues w/charging on jb but cant remember their solution if any.
if prob is still there on stock, then it could be battery, battery contacts, bad cable, dirty phone port, bad phone port.
since it does charge albeit w/screen off you could try to live with that instead of chucking it
Found this old thread with a similar problem to what I'm seeing. I'm running liquidsmooth 3.2-2014-08-20 since late November but had something similar before I reinstalled this ROM.
I have two batteries - the original that's 3+ years old and a new Samsung battery bought 4 months ago. When I have the old battery in, it charges when the phone is off or on. With the new battery in, it charges fine when the phone is off. When the phone is on, it charges for about 5 seconds then stops. If the remaining battery is low, I then get the message popping up saying to plug in the charger. When the new battery is in my phone does recognize the chargerbecause it pops in to USB mode and because I have a Tasker profile that's triggered when it's powered. The triggered action doesn't revert until I unplug the cable.
Does this suggest my problem is with my new battery?
Robnw