Related
Not sure what caused this, I crack flash CM nightlies, constantly convert partitions from ext-3 to ext-4 using beta kernels and at some point in between lost the ability for any computer to recognize my phone mounting (both internal and external). Tried three different computers, two different cables, swapped sd cards, reformatting card and nothing... All that happens when plugging into computer is a charge symbol.
My SD card is accessible through file managers and is mounted just fine to phone (accurate storage space). So I took it into Tmobile and they overnight-ed me a new g2x phone which is expected to come Monday. Claimed it was a hardware failure and acknowledged I had a custom rom and to make sure I put the stock one back . The only problem it is impossible to get the stock recovery image and remove root without a computer so I will be sending them a rooted stock rom with custom recovery. Hopefully they don't charge me for it...
Just wish I knew the cause whether or not it was a bad build or human error issue. Hopefully LG or Tmobile dont charge me full price when they see the firmware has been tampered with. I could always format the system with nothing on it so it just sticks on the LG symbol and has no rom to load up i suppose lol
I had to replace my first g2x because of this. No amount of software/external hardware troubleshooting fixed it. Luckily, I got mine at Costco which has a 90 day return policy. Ill try to find the thread I made... same symptoms though.
Also, my issue occurred on stock rom unrooted, so it wasn't the result of phone tinkering.
Here is the link: http://forum.xda-developers.com/showthread.php?t=1104397
Happened to me to on my first g2x....sometimes (randlmly) it would start working again n so when it did work I was able to bring back to stock n unroot n then a few hrs later the USB stopped working again...got a new one thru warranty and have been fine since
Sent from my LG-P999 using XDA App
dominante58 said:
Happened to me to on my first g2x....sometimes (randlmly) it would start working again n so when it did work I was able to bring back to stock n unroot n then a few hrs later the USB stopped working again...got a new one thru warranty and have been fine since
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
I had this problem on my first G2X phone also. It stopped working then somehow it worked for 1 min then never again. I had to replace that phone.
brdma said:
Here is the link: http://forum.xda-developers.com/showthread.php?t=1104397
Click to expand...
Click to collapse
Yup, this definitely looks like the same issue despite I am rooted and you were stock which is proof to me that it is a defective hardware and not provoked from me tampering with the firmware. Just hope they dont throw a fit when and if they find it rooted with custom recovery image.
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
My One X restarts when I'm in the Google Play app and while using the built in browser. It seems to be data related... Also I get no error or anything of that nature, it just freezes (stops responding to any input whatsoever the capacitive buttons don't respond either) and it just restarts and goes through the HTC and AT&T load screens. Any ideas as to why my phone keeps restarting after a bit of use on the market, browser, etc... I've sent in my original phone thinking it might've been defective. Turns out the one they sent me did the same thing. Mind you they sent me a refurbished one. So I don't know if its a problem isolated to the original shipments of HOX's since I got mine via a pre-order and this is probably the same batch since the AT&T rep said they had no new devices to ship to me as a replacement.
Any ideas?
I've gone through a few HOXs and have never had a single reboot on any of them. My suggestion to you would be to wipe everything (data, cache, dalvik) and reflash your ROM.
_MetalHead_ said:
I've gone through a few HOXs and have never had a single reboot on any of them. My suggestion to you would be to wipe everything (data, cache, dalvik) and reflash your ROM.
Click to expand...
Click to collapse
How exactly would I go about doing that. I used the clockwork recovery mod on my Aria back when I had that. But from what I understand the HOX doesn't have that yet and attempting to use ROM Manager or anything that uses it would brick my phone.
We have clockwork mod and TWRP recoveries. I take it you are on a stock ROM then? Are you rooted?
Oh, and never use ROM Manager. Ever.
_MetalHead_ said:
We have clockwork mod and TWRP recoveries. I take it you are on a stock ROM then? Are you rooted?
Oh, and never use ROM Manager. Ever.
Click to expand...
Click to collapse
Yeah I'm rooted (on the stock ROM) and I managed to get my bootloader unlocked.
I take it you haven't flashed any mods right? I'd get clockworkmod flashed on your phone and then wipe and flash CleanROM SE. It's very close to stock, perfectly stable (I haven't had a single force close except for one youtube one a long while back right after flashing), and it has some great mods and tweaks. If you are still having reboots, then I would RUU back to stock, see if they are still there and if they are, get it replaced.
_MetalHead_ said:
I take it you haven't flashed any mods right? I'd get clockworkmod flashed on your phone and then wipe and flash CleanROM SE. It's very close to stock, perfectly stable (I haven't had a single force close except for one youtube one a long while back right after flashing), and it has some great mods and tweaks. If you are still having reboots, then I would RUU back to stock, see if they are still there and if they are, get it replaced.
Click to expand...
Click to collapse
Sorry, didn't see this (http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att) on the index. Thanks for the help.
xChurchx said:
Sorry, didn't see this (http://briefmobile.com/how-to-install-cwm-recovery-on-htc-one-x-att) on the index. Thanks for the help.
Click to expand...
Click to collapse
Yep, that's the one. Happy to help.
Radio
If your issues were mostly data related its probably a radio issue. Be sure to flash a new radio. If I'm not mistaken most roms don't include the radio. I like the latest AT&T as well as 1.88. Much better than 1.73 or 1.85. you can flash it just like a rom if it's in zip format. There's a thread in development with radio In the title. Normally first page.
xChurchx said:
My One X restarts when I'm in the Google Play app and while using the built in browser. It seems to be data related... Also I get no error or anything of that nature, it just freezes (stops responding to any input whatsoever the capacitive buttons don't respond either) and it just restarts and goes through the HTC and AT&T load screens. Any ideas as to why my phone keeps restarting after a bit of use on the market, browser, etc... I've sent in my original phone thinking it might've been defective. Turns out the one they sent me did the same thing. Mind you they sent me a refurbished one. So I don't know if its a problem isolated to the original shipments of HOX's since I got mine via a pre-order and this is probably the same batch since the AT&T rep said they had no new devices to ship to me as a replacement.
Click to expand...
Click to collapse
I had this exact problem. EXACT. Does it happen on WiFi only? try turning it off.
EDIT: this happened to me on two different HOXs, one just after i updated to 1.82, and the other, stock from the store on 1.85. I was able to narrow it down to the fact that our home wifi was unprotected with a hidden SSID. as soon as we changed it to WPA it worked fine, and continues to.
Hi Everyone, I was wondering if I could get a little help -
I've had my S3 for a little over a month, rooted, stock kernel, cm 10.1. The other day the display suddenly went haywire, shifted green, and is now completely fubar (all black except for a little flickering strip up at the top).
Verizon sent me a replacement and I have to send the old one back, but I need to find a way to reset the flash counter and flash un-rooted stock rom before doing so...without a working screen.
The phone seems to work fine (pc recognizes it as well), I just can't see the damn thing and so can't install Traingle Away or any other apps that would help me.
Could anyone help me figure out a way to clear the flash counter and restore this thing to stock so I can send it back? I have 5 days and am getting kinda desperate...thank you in advance!
UPDATE: Lucky me, the screen turned on again after a day without functioning. It was green and had extremely low resolution, but it was enough to see what I was doing to unroot/return to stock. I wonder if this problem could have been caused by CM 10.1? I'm asking because touchwiz is the ugliest, clunkiest interface since the abacus and I want to root/flash the new phone right away...but I'm not sure if the gpu instability (I'm guessing that's what it was) was related to me flashing a custom rom and new firmware...any thoughts?
...Could I take the motherboard out of the broken phone, put it into the replacement, perform the necessary steps to return it to factory stock, and then put the motherboard back? I hope there's a less intimidating option...
id be shocked if they investigated it further after the device screen wont turn on as you describe.
especially if its not just ablack screen and it still sorta functions.
ddurandSGS3 said:
id be shocked if they investigated it further after the device screen wont turn on as you describe.
especially if its not just ablack screen and it still sorta functions.
Click to expand...
Click to collapse
But won't it become an issue when they replace whatever's defective with the screen/gpu and see that it boots to CM when they try to refurbish it?
If your computer recognizes it and your phone is indeed functional. Try to get into download mode on your phone and flash a stock unrooted image. That should do the trick!
Sent from my Galaxy S3
TheKucho said:
If your computer recognizes it and your phone is indeed functional. Try to get into download mode on your phone and flash a stock unrooted image. That should do the trick!
Sent from my Galaxy S3
Click to expand...
Click to collapse
Can I do that through ODIN? I've always used clockwork for flashing roms, and I can't see the screen even in recovery. Also, would that reset the flash count?
Still kind of a noob at this, so sorry if any of the questions seem obvious. Thanks again for all your feedback
Exactly what thekucho said.
I had this exact problem, my screen took a crap while I was rooted and I needed to get back to stock before I sent it back. I was able to get it into download mode and Odin back to stock. I didn't even bother with resetting the flash counter and I haven't heard anything about it.
Boot into download mode (vol down + home + power), Odin back to stock, and you're good!
Sent from my SCH-I535 using Tapatalk 4 Beta
I just threw mine in a microwave for 4 seconds... :silly:
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