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
Related
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
Hi All,
My Xoom had worked normally but since few days ago, it could not hold charging anymore.
Xoom will be on as long as it's connected to power charger (battery indicator always showed 82% but not increase or decrease) and will switch off immediately if i unplug the charger. By the way the Xoom date and time was also changed back to 1970s.
I have tried to delete the batterystats.bin and refreshed it. Also try to use "Battery calibration" software but not thing change.
Please help.
Thanks in advance.
A bit more information would be nice...
That's unfortunate.
It might be worth putting up some more information about your device, it might help other people help you...
It might be worth mentioning if your xoom is rooted. if it's bootloader is unlocked or not, the rom/kernel you are running, and of course, the model of your xoom.
Have you tried factory resetting the tablet? Back up your data if you do that..
If your device is rooted with an unlocked bootloader, you could also try flashing or re-flashing a rom. Perhaps something went wrong and a fresh start might be required. Switching to a different rom though might require a full data wipe. Luckily, if you were using TitaniumBackup, that wouldn't be too much of an issue.
I am not responsible for what happens because of my advice..
EDIT: If all else fails you could also go to http://developer.motorola.com/products/software/ and download the images for your xoom, and flash them through fastboot, if your xoom's bootloader is unlocked. I have never tried it with a locked bootloader, so I cant guarantee it working in that case. Anyways, following all the steps should completely return your xoom back to factory condition.
As mentioned. Root it. Get custom rom, EOS nightlies recommended.
Factory reset.
Thru recovery, Wipe cache. Wipe dalvik. Wipe battery stats. Flash rom, and gapps. Then reboot. Set date and time and google account and then try.
Sent from my MZ601 using Tapatalk 2
Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo
OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app
bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548
To start, I have never had problems flashing Skyrocket ROMs before. I flashed the ICS leak with Odin when I first got the phone, then CWM, then Cyanogeonmod when that came out, and some other things. But recently I decided to flash SlimBean which suggested TWRP so I flashed that and I had it working well for awhile.
After Google I/O I decided to f;ash the weekly build, SlimBean 5.5. The flash went OK but the ROM was glitchy and crashed a lot. So I decided yesterday to go back to the release channel of SlimBean. So I downloaded SlimBean 5.0 and AIO Addons 5.x and I moved them to my SD card. However before I did that I noticed I already had a 5.x from my last flash that would turn out to be the Aroma installer that i didn't want. But anyways, after wiping the cache, Dalvik cache, system, and data, I flashed the 5.0 ROM then the 5.x aroma aio addons, and then it sent me into the Aroma installer which I figured out that I used the wrong addons aio package. So then I hit next all the way through the installer without changing anything and didn't hit reboot device. Then, still in the TWRP menu, I wiped the same sections I did last time, mounted the SD card through TWRP, moved the AIO Addons 5.x on, and deleted the AIO Aroma 5.x. Then I flashed SlimBean 5.0 from before with the AIO Addons 5.x.
When I hit reboot, my phones screen was off and it never went on again. I took out the battery, had it hooked to the charger, and tried everything and it wouldn't even vibrate. So I knew pretty fast that I had hard bricked it. I Google'd a little bit and read about the jig, but I have a feeling that wouldn't work with this low level of a brick. So I guess what I want to know is what actually happened, and I just want to get this story out there because I have no idea how I got such a low level brick from just flashing ROMs like usual.
Also, I'm planning on making a trip to the AT&T store with hopes of getting a replacement. I don't know if I will because it is refurbished and I bought it online over a year ago. (the warranty being 90 days) Does anyone have experience getting replacements out of warranty?
First off if it's bricked it's bricked it's not about low level or whatever.
Second a jig does nothing for this phone that can't be done manually, don't waste your time or money on it.
Third you can have it jtag'd for $50 by some dudes if you search tons of people have done it.
You left out an astounding amount of detail for an extremely long post so no one can tell you exactly where you went wrong.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yea, way too many words. But to your last paragraph, good f'n luck. You're way out of warranty.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
You will get no warranty. Send it away for jtag if you want it fixed, you can't fix it if it's hard bricked.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
TankTan38 said:
I sent the phone to be jtag'd and they sent it back saying they couldn't fix it. What could have gone so wrong in the flashing process that it is bricked so badly?
Click to expand...
Click to collapse
probably wasnt the flash but bad hardware, most likely mobo/memory, jtag can only write to the mem chip if its corrupted or a incompatible rom was trying to write to it but it wont/cant fix a hw failure of chip
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