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.
This thread is now irrelevant as Jellybean is available for the device.
The old post can be found below:
As of right now be sure that you all are extemely cautious when trying to flash any type of ICS package (be it firmware, a ROM, or any type of system running it). Our tablet may have an issue with ICS as many other galaxy devices have. A bug currently exists that corrupts the mounting of the data partition on the device which *MAY* lead to a permanent hard bricking of your device.
This is currently a very RARE issue, however, those who are not well educated in Android development and that do not know how to 100% reset their tablet should refrain from flashing any type of ICS ROM or ODIN package.
If you have already flashed an ICS ODIN package or are running CM9 safely and have been for a good amount of time, then my guess is that this issue will not effect you, BUT it may strike you at any given time!
For those of you who insist on upgrading to ICS, *PLEASE* backup your entire ROM and make sure that you have the stock HC ODIN package. Although it probably won't help having them if you are hard bricked.
A quote from an effected user:
ringnutz said:
I also had the can't mount data problem, I tried for 3 days to get it to work. I ended up sending it back to Samsung after reverting everything to stock. I was on cm9 though and one night it just started bootlooping while i was asleep. I.e. it would fully boot then restart after 5 seconds or so. So I tried reverting to stock and trying again, which is when I got the can't mount data issue. I literally tried every combination of wiping, recovery, Odin/heimdall, and the only thing that would get past the Samsung logo was cm9, which would just stick at the boot animation forever. I got tired of messing with it and thought it could have been a hardware problem, so I sent it back under warranty
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
A quote from an effected user:
daviddavid123 said:
i installed cm9 and ics 4 then my tab hard bricked and internal memory damaged
Click to expand...
Click to collapse
A quote from an effected user:
krbabb said:
I dont have posting privleges in the developer forums but i thought i would let you know whats up with my tab.
Rooted it, got cwm on it and flashed cm9. Worked for about a week without issue then started the bootlooping issues. I couldnt even wipe the data in recovery.
Used odin to go back to stock HC according to your instructions. Then i thought it bricked cause it just got stuck on the default screen showing galaxy tab. Tried installing HC a few more times but it never booted.
Tried one more time but now with the stock ics. Still nothing so i gave up.
Only thing is i couldnt power off. I planned to let the battery die. So it just sat on the default gakaxy tab screen and about 30 minutes later it showed the samsung boot animation.
I let it sit for another half hour with samsung pulsing. Nothing. So i reboot into recovery (stock) which i couldnt even get to before now, wipe everything like 5 times then reboot the device.
Booted up and works like a charm. I thought this thing wad gone.
Not sure if the stock ics tar file did the trick but let everyone know that mine came back to life. It possible other devices could be bricked but maybe there is a chance for some people.
Sent from my GT-P6210 using xda app-developers app
Click to expand...
Click to collapse
If you have flashed ICS and you have bricked your device I am sorry. I know there are a few people out there who have....
To conclude, everybody please be careful about tinkering with your device. I know ICS has great speed enhancements and all, but as of right now your box of ice cream sandwiches may or may not be poisoned.
For the daredevils:
CM9 [View thread]
Guide to flashing ICS [View thread]
EDIT: Our case is not the same as the other galaxies.... Ours effects the data partition while theirs effects their emmc... I'm assuming ours may be a bug with the firmware installation / recovery as it was with theirs however I'm not sure why it is effecting users on CM9....
EDIT 2: We should all be cautious and NOT wipe at all using Samsung's ICS Recovery. I was chatting with aorth and he suggested that that may be the cause of the issue. His recovery (or the one I posted in my guide) are safe to wipe on.
EDIT 3: I guess we also have reports of the emmc being corrupted as well...
Just don't wipe data/factory reset using recovery ICS (RECOVERY 3e). Use recovery 5.5.0.4 or 6.0.x.x......only you wipe for up new rom, everything will be OK.
Sent from my GT-P6200 using Tapatalk 2
Yeah, i experienced this type of total brick. I flashed p6200 ics firmware with mobile odin and than did factory reset in ics recovery mode. I think this was the reason of hard brick. After some time tablet did shut down and didn't turn on. Service fixed the problem, they said that main board died.
Ignore this post.
StrumerJohn said:
That's not the case I afraid...
Click to expand...
Click to collapse
I really don't think it was a problem with upgrading. I had been on cm9 for over a month, then I woke up one morning and it was bootlooping. I got all the can't mount data errors afterwards, so it's either a hardware problem or cm9 is somehow magically corrupting the /data partition. I hadn't even installed anything recently
EDIT: Samsung just sent me the email that the repair is finished, they replaced the main board, so it definitely was a hardware problem.
Sent from my myTouch 4g via Tapatalk
This issue was brought up a couple months ago by aorth, I think its in his CM9 thread or in one of the rooting or CWM threads. I don't think it is an issue that will be going away any time soon as Samsung isn't in any hurry to fix it, that is if they even can or want to.
Using stock ICS for almost 3 weeks now.
I was backing up and restoring all of the partitions via CWM 6.0.1.0 two times.
Nothing weird happening for the moment.
I use the ics wipe/factory reset and I don't have any problem, I have 6210 .
Well, aorth entioned sth like this before, here his post:
aorth said:
Maybe you guys have heard, but some early ICS ROMs for Galaxy Note and other similar Galaxy S II variants have triggered hard bricks due to faulty MMC firmware handling erase commands improperly. I never bothered to read up about the issue until now, but it looks like we should also be careful.
Chainfire just released a tool to print out whether your device has a known-bad firmware revision, Got BrickBug?. As you can see, my device has firmware revision 0x19. This revision has been known to cause hard bricks on other devices using Samsung ICS ROMs.
CM9 is safe (Entropy512 haxx0red the kernel), but we should be careful.
Click to expand...
Click to collapse
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Well, aorth entioned sth like this before, here his post:
I got this bad firmware revision too, but iam still safe after 2 months
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if I had the bad one, but mine worked fine for months too. Then out of the blue it bootlooped and when I tried to fix it by reverting to stock, I got the error. Hopefully when it comes back it will have a different firmware revision (if that's what the problem was)
Sent from my myTouch 4g via Tapatalk
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
02xda2 said:
I flashed my tab with 'P6200OXALQ1_P6200XXLQ1_P6200XXLQ1' on 19th July - so far nothing has happened.... and it is working much faster than the 3.2 Honeycomb it came with.:fingers-crossed: Using Stock kernel/recovery... only rooted using temporary touch recovery.
Click to expand...
Click to collapse
If you flashed it using Mobile Odin that's normal because it uses its own recovery.
Ok, so what's the verdict? This bug sounds very scary.
Given that I'm running a stock ICS flashed via ODIN, should I be running:
-Stock recovery
-CWM
-Something else
to avoid bricking while factory reset?
I also use mobile Odin to flash ics and no problem. So, could you say that with Mobile Odin are safe from this problem?
Just read this http://www.reddit.com/r/Android/comments/xj2hd/i777_superbrick/, seems some of the things said could be relevant for us.
I have a galaxy note and Entropy who is dealing directly with samsung on this issue has a thread over on the galaxy note page. Lots of information over there.
I use the free emmc bug check app by vinagre https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en to check my samsung devices on ics. Not entirely sure that the same case applies for the note and the tab plus though but it does give me peace of mind.
Just to err on the side of caution, I always odin flash back to gingerbread to wipe cache and other stuff before upgrading. This seems to have worked for me so far. *fingers crossed*
Check out that app above, its free and have a read of entropy's thread http://forum.xda-developers.com/showthread.php?t=1698977 but beware they don't take kindly to noob questions. I just mainly read entropy's updates and replies and ignore most of the rest of the stuff there.
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
hi,
i have flashed the stock ICS, the Austrian version using ODIN3. i have been running it since july 18th.
so far i dont see any problem with my tab..
just to say, i have flashed the firmware atleast 3 times, just as an exercise. and have factory reset it after ICS flash atleast like 5 times now.
everything so far works fine. i use the stock recovery for factory reset.
after the 1st flash, i had root.. then thought of unrooting, so flashed the firmware 2 more times.
and in between the flashes, i have factory reset a lot of times.
so far, the bootloop problem which i used to have when on HC, is not there. hopefully, it wont occur in ICS.
hope, this helps developers.
Zarvox said:
Is there any chance to bring my tab to life has the repair center hasen't repaired mine
Click to expand...
Click to collapse
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Or use this method:
http://forum.xda-developers.com/showthread.php?t=1661590
Sent from my GT-P6200 using Tapatalk 2
giangp1 said:
Use pit file (tab 7.7) in topic of hg42 - galaxy note this forum.
http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
Thanks with manual method described in this thread I've confirmation that my data partition became corrupted.
Yes it is alive !!!
I've deleted mmcblk0p9 (DATAFS on my P6210) and recreate one with smaller size (3 GB) than normal (15.2 GB).
When the tablet boot I realise I've 1.68 GB of storage
Now I may increase the size of data but previous tries told me if data reach 5 GB in size the creation of partition fail.
I having big issues with my SR lately. I was on chimera 2.2 and things were great. Popped cm10 alpha 3 on there with investgator Xs kernel on there and started getting SODs, one time it was locked for a while before I got to it. Was pretty warm. After that I've wiped the SD cards clean, odin'd back to stock, tried SEVERAL ROMs, cm 9 official, skyics, cm 10 super lite, and others... no matter what ROM (all with the kernel they come with) I get a SOD every 15 to 45 minutes. Even weirder is no last_kmsg is being produced!
With or without any CPU apps. No under volting. Tried 3 different batteries. Tried all I/O Schedulers.
I have exhausted everything I know about this to fix it and I don't know what to do.
I've tried wiping and flashing ROMs with all existing recovery options (twrp, cwm, cwm touch, custom cwm touch) and with or without dark side scripts. I've wiped 3 times or more....restored very old nandroids that never had that problem too, and they get it.
Is it possible there is ANYTHING left in my files that normally won't get wiped that could cause this? Is there anyway to figure this out or does it sound like my SR is going bad? I'm up for any solution. Today using one of the nandroids it didn't get a SOD all day, but it was stuck from going into deep sleep due to a wake lock from chrome which I have since fixed... its getting SODs again now...
I realize you may benefit helping me with a log cat which I'm trying to get with lumberjack. Oh and a dmesg right?
Thanks in advance to anyone who can help. I'll answer any questions I can I may have forgotten.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Forgot to mention I know a repatriation in Odin should help but there is no pit file for this phone... any other ways around that?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Try a fresh new revert back to stock on odin. If you still get sod, you are sol. Your phone hardware has gone bad. I'm guessing your internal sdcard developed corruption and is ireparably damaged.
Try to get it repaired or replaced under warranty.
Sent from my SGH-I727 using xda premium
jamesc760 said:
Try a fresh new revert back to stock on odin. If you still get sod, you are sol. Your phone hardware has gone bad. I'm guessing your internal sdcard developed corruption and is ireparably damaged.
Try to get it repaired or replaced under warranty.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
Wanted to give an update... I sent the phone to Samsung for warranty repairs last week. It is labeled as fixed and on its way home today. The repair tracker they let me see said it was a "Side Button Failure" and the repair was a "S/W Updated"... Now I know there has been talk of a power button issue with this phone.. but I was leaning more towards what the above poster stated.. a corrupt internal SD or something along those lines...
I guess my confusion is, did they really duplicate my problem before throwing a fix at it and then VERIFY it was indeed, fixed? I don't know how shotty Samsung warranty repairs have been for others but I hope they did indeed fix my problem. I guess we'll see.
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've posted this in the GideonX BMS kernel thread of the androis development section as well. Hope someone can help. . I'm currently,or I was up until tonight, running Chris123NT's variation of the 10.2 unofficial build dated 8/29 with GideonX's 8/15 kernel. Its been running fine fore 2 days. Today I went on a hike and used my tracks,the stock camera and the focal camera. At about 9pm I decided to reboot the phone, I was having some problems with ford sync and iheartauto. This has been, what appears to be, a fatal mistake. The phone hung in a bootloop at the BMS splash screen. When I try to use twrp 2.6.0.0 it immediately asks for a password, which I've never set, and if I hit cancel it appears as if there is no data on the internal or external storage. Am I up craps creek? I've search for info on this and came up with very little other than some buzz about a hard brick. Sure hope thats not the case and someone can help. I'd been running masta's builds and gideonx's builds until the other day when I hoped to get some RIL lovin' in Chris' new build. Please help!
Ray
Reborn627 said:
I've posted this in the GideonX BMS kernel thread of the androis development section as well. Hope someone can help. . I'm currently,or I was up until tonight, running Chris123NT's variation of the 10.2 unofficial build dated 8/29 with GideonX's 8/15 kernel. Its been running fine fore 2 days. Today I went on a hike and used my tracks,the stock camera and the focal camera. At about 9pm I decided to reboot the phone, I was having some problems with ford sync and iheartauto. This has been, what appears to be, a fatal mistake. The phone hung in a bootloop at the BMS splash screen. When I try to use twrp 2.6.0.0 it immediately asks for a password, which I've never set, and if I hit cancel it appears as if there is no data on the internal or external storage. Am I up craps creek? I've search for info on this and came up with very little other than some buzz about a hard brick. Sure hope thats not the case and someone can help. I'd been running masta's builds and gideonx's builds until the other day when I hoped to get some RIL lovin' in Chris' new build. Please help!
Ray
Click to expand...
Click to collapse
Well you definitely aren't hard bricked, and you're still rooted and unlocked or the Verizon triangle would come up.
See if you can Google "twrp password" or something similar, maybe there's some kind of default password it's asking for.
If nothing comes up, Try to find an Odin flashable file of twrp, as recent as you can find. See if you can overwrite the recovery partition and at least get to a backup to restore from.
As a last resort, boot into download mode and Odin back to stock. You'll lose all your data but at least you'll have a working phone.
Sent from my SCH-I535 using Tapatalk 2
Seems that I'm at the end of my rope here. Tried to reodin TWRP, that didn't work. Just tried to Odin a no wipe stock 4.1 and that is froze up as well. I'm downloading invisiblek's stock 4.1 and I'm going to try that. If my partitions are shot do I have any options? Man this socks!
Ray
Scratch that, just did a day wipe and it's back up. Had hoped not to loose my pics from my hike yesterday. My niece will be disappointed
Sent from my SCH-I400 using xda app-developers app
Reborn627 said:
Seems that I'm at the end of my rope here. Tried to reodin TWRP, that didn't work. Just tried to Odin a no wipe stock 4.1 and that is froze up as well. I'm downloading invisiblek's stock 4.1 and I'm going to try that. If my partitions are shot do I have any options? Man this socks!
Ray
Sent from my SCH-I400 using xda app-developers app
Click to expand...
Click to collapse
Odin should definitely work, keep trying, there's no reason why it wouldn't be able to pass.
If you can't get it to pass using a normal method, try this:
http://forum.xda-developers.com/showthread.php?t=1840030
Sent from my SCH-I535 using Tapatalk 2