Related
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
I think a lot of people recommend the root66 stock..... But I'd try noSympathy's image
Sent from my SCH-I535 using Tapatalk 2
I'm rooting immediately after so whatever is a proven version will make me happy
SGS3 production
They're both rooted so no need to do after. Both are tried and true, noSympathy's is based off the last OTA but some people like to start from scratch so that would be root66.
Sent from my SCH-I535 using Tapatalk 2
I want to get back to unrooted stock.
I can't seem to locate the route66 stock image
SGS3 production
http://forum.xda-developers.com/showthread.php?t=1762204
It's up to you but it's just more work to go unrooted then root yourself. Check the development threat there maybe an un rooted image there
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:36 AM ---------- Previous post was at 07:27 AM ----------
http://forum.xda-developers.com/showthread.php?t=1755386
Thought there would be a newer one but here's unrooted...
Sent from my SCH-I535 using Tapatalk 2
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
FormeriPhoney said:
My main reason to flash stock was I was told that would be the only way to restore my faulty gps lock.
Do you think flashing a stock rooted image would do the same for me? Or should I flash unrooted image then start fresh? Time is not a concern, im patient
SGS3 production
Click to expand...
Click to collapse
Flash back to stock then root. Click link in sig.
i tried this......still having the same issue, switched from CM10 back to stock and had issues with my GPS being way off, like by 3300 meters off haha.....so flashed back to stock, still had the issue, so i used the rooted stock image and flashed that and i'm still off by about over 2k meters.....don't use my navigation or maps all that much but when i do need it i'll have a bit of an issue lol
I had issues with my gps for a few days. If was real flaky but got better with synergy 1.5. I have since move to 1.6 with a fresh install and am still okay. Check out a app called gps status. See if you can see any gps satellites. Maybe in that app clear your agps state in tools. Then if that doesn't work try to download gps assistance with the same app in the same settings. Make sure your out side for this stuff with your gps. It's probably not gonna hit ya sitting on the couch.
Sent from my SCH-I535 using Tapatalk 2
FormeriPhoney said:
My maps gps lock got totally f*cked by synergy 1.7 so it was suggested to go back to stock and reroot since flashing new rom from clean wipe did not work.
A lot of links and methods are out of date, so I was wondering what the best way to get back to stock at this point.
I have the latest odin on my computer, I guess I'm looking for the most recent or most reliable stock image to flash.
Thanks
SGS3 production
SGS3 production
Click to expand...
Click to collapse
I used the stock image from here:
http://samsung-updates.com/device/?id=SCH-I535
and used this method for rooting:
http://forum.xda-developers.com/showthread.php?t=1792342
my gps doesnt work at all
After Odin back to stock, non rooted image my GPS is fixed.
Now on CM10, loving it. Not sure if I'll ever try synergy again bc of that nightmare situation.
I use my gps pretty much all day. I needz it
SGS3 production
New AOKP JB issue with radio
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
douglasf01 said:
Well I am trying to get something fixed and I am going through a complete restore to do this.
But just so you are aware the new AOKP JB release will kill your data. I learned a hard lesson with this when trying to recover and nandroid back to my previous rom. It killed my data completely and would not allow me to do anything with data in any rom. I used the root66 stock rom in hopes it would work, and that didnt even solve the issue.
Right now I am restoring a factory image through kies and seeing if that will do what I need. If it does, I am sticking with stock roms for awhile until AOSP roms have more time to develope with less bugs.
Click to expand...
Click to collapse
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
still had IMEI
toy028 said:
It sounds like you may have lost your IMEI or MEID. I hope you made a backup with QPST.
Click to expand...
Click to collapse
Well it turns out I still had my imei present on my phone and even after a factory reset like I did wit kies it still didnt work. Initially I wasnt able to get past the activation screen on the root66 rom, but I was able to with the stock factory image from kies in which case this allowed me to follow the steps in this link.
http://forum.xda-developers.com/showthread.php?t=1838791
Once I did that my phone rebooted and everything came back as it was never gone, well except for all of my data on the internal sd card, but that is to be expected.
After 2 hours of going through numerous steps I finally found a fix, mind you not the most simple of fixes, but a fix none the less.
I think I am just going to stay stock for awhile like I mentioned and wait for the OTA that comes out in 2014 lol, unless in review of AOSP roms the issues present now are gone after sometime.
Tks
Nice. Tks
Gps works like a champ on beans!
Gps seems to work substantially better on cm10 than on stock....ran the GPS test and i locked onto 14/19 satellites.
Beamed via NFC through the local store to the internet from my SGS3.
So I decided to go ahead and put my findings of this issue that several of us have had with our phones getting the dreaded "Battery Disconnect" after upgrading from stock ICS to stock JB. I cannot guarantee that this will work for everyone but it did work for me.
Here are the different solutions I have come across in my research on this issue.
1: Battery corruption: get new battery
2: Gold prongs are dirty on phone and battery: clean them
3: Bad charger: get new charger
4: Dirt or dust in USB port: clean with compressed air
Now I tried each of these and unfortunately none worked for me. It has for some that I have read on different sites, so if you don't want to try and re-flash everything try those above.
For those that have tried each of above 4 and still have the issue, like myself, you can try the following. This worked for me, but you have to have patience. Read entire post before trying, check MD5 sums before any flashing and the typical disclaimer, I AM NOT RESPONSIBLE FOR YOU PHONE, TRY AT OWN RISK. Sorry, had to put that in.
1. Have your battery charged to 100%. You need to go back to ICS if you aren't already. If you are on JB right now, wipe your system clean (factory reset) that's including formatting system, data, cache, dalvic, etc. using CWM (that's just what I prefer for this part and what I used). Do a backup first of anything you don't want to lose. I used Titanium Backup Pro myself but pick your own poison. If already on ICS, proceed to step 4.
2: Using ODIN, flash ICS back on to your phone. If you haven't already looked at Vincom's guides, here you go. http://forum.xda-developers.com/showthread.php?t=1652398 and http://forum.xda-developers.com/showthread.php?t=1785999. Keep it plugged into the computer while it reboots. Should show battery charging. If not, do it over. DO NOT ADD CUSTOM RECOVERY AND ROOT.
3: Test all your chargers. Generic and OEM and any additional batteries you may have. Make sure they all work. If so, let it settle for about 10 minutes and then on to the next step.
4: Power off the device and boot into the stock recovery. Do a factory reset, choose reboot and when the phone powers off, take out your battery.
5: Now using ODIN, flash stock JB. Again, leave the phone plugged into the computer until it boots completely. As long as it is charging and not "Battery Disconnect" you're on the right track. If it does not boot, basically just sits on the AT&T symbol for an extended period of time which can happen, remove battery, reboot into stock recovery, factory reset and re-flash JB again. If it says "Battery Disconnect" after it boots, wipe, and re-flash JB again. DO NOT INSTALL CUSTOM RECOVERY OR ROOT YET. I did on my first attempt of these steps and immediately got the "Battery Disconnect". If you succeeded, on to the next step.
6: This is when your patience comes to affect. You need to let the phone settle. I gave mine 2 days of using and charging when dead without getting the "Battery Disconnect". It happened once after a full charge, but only once. I plugged it in while half charged to see what happened and it popped up. Later when it died and I plugged it in, it charged with no problems. Patience. Something about the drivers taking time to settle either in the rom itself or in the kernel for certain devices. Not sure which. I did re-install my apps but I did with using the Play Store and not with my backup. Make sure you are on Wi-Fi so you don't jack up your data usage.
7: Now that you have had two days of using and charging with no issues, fingers crossed, go ahead and install TWRP using ODIN (no wipes needed). After it reboots, again keep it plugged into the computer and if it is charging after boot without the dreaded phrase, CONGRATULATIONS! BUT, I would wait for at least one day before you try any custom roms on it. Again, let it settle first.
I know this is a lot. But again, this is what worked for me after trying for almost two weeks now to find a solution. Good luck everyone, I hope this works for you as well. And thank you Vincom for the guidance.
Thanks! I will try this perhaps if my attempts to return the device fail...
The other thing I am wondering is if anyone that has had this issue has tried going "the long way around" to upgrade... be on ICS, flash TWRP/CWM, then (assuming everything is OK), flash just the JB radios and a custom JB based AOSP ROM and ignore the full ODIN of official JellyBean if the result would be better?
acejavelin said:
Thanks! I will try this perhaps if my attempts to return the device fail...
The other thing I am wondering is if anyone that has had this issue has tried going "the long way around" to upgrade... be on ICS, flash TWRP/CWM, then (assuming everything is OK), flash just the JB radios and a custom JB based AOSP ROM and ignore the full ODIN of official JellyBean if the result would be better?
Click to expand...
Click to collapse
I still had issues with doing that as well. Try though. If it works then let me know and I'll put as another solution in the OP.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I will let you know, will probably be next week before I get a chance to look at it again.
BTW, I sent an email to tech support, explaining that I used nothing but the stock firmware images and the issues I had... here is there "official" response:
Dear Steve ,
Thank you for contacting Samsung Telecommunications America.
After reviewing your e-mail we understand that, you have updated the device to Jelly Bean and the battery was not charging and you have installed stock ROM of Ice Cream Sandwich.
As we see that, you have rooted the device, we would like to inform you that, rooting the phone will void the warranty. We also would like to inform you that, as the phone is not taking a charge, the device need to be physically examined by the service technicians to reflash the software on the phone. Hence, we request you to contact our voice team, they will assist you further regarding the query.
You can contact our voice support at 1-888-987-4357, Mon-Fri: 7 AM - 9 PM (CST), Sat: 9 AM - 6 PM (CST).
If you have a minute, please click on the “Start survey here” link at the bottom of this email to fill out a brief survey to help us serve you better. Kindly note that you can access the survey page only when the pop-up blocker is disabled on the browser. Have a wonderful day!
Should you have more questions regarding your Samsung Mobile Phone, you can reach out to our chat support team by accessing the following link. Live Chat is available 24 hours a day 7 days a week. Have a wonderful day!
Link: http://www.samsung.com/us/support/contact
Thank you for your continued interest in Samsung products.
Sincerely,
Michelle
Technical Support
Click to expand...
Click to collapse
Basically, it's "Well, too bad... Send it in and we will fix it, for a price!" Thanks Samsung!!!
Yep, that sounds about right.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Changing radios to UCMC1 and installing TWRP recovery and rooting had no effect, with an ICS ROM the battery charges properly.
So this clearly seems to be kernel related with the JellyBean code of the kernel and how it is talking to the hardware, the stock kernel and Marla kernel have the same result... I tried Beanstalk 1.300.3 (Wrap-up 3) and the battery would not charge, in the *#*# menu under battery it showed the exact same thing, "Unknown error" and would not charge. Restore back to ICS from TWRP and everything was OK again. Think I will wait to see how it goes after I get an real Samsung battery, about 95% sure this battery is a fake, but in reading similar discussions on this with SGS2 models, the battery doesn't seem to be the issue but it's worth a shot. I might try a few ICS ROMs and see what happens and report back now that I know restoring back to stock ICS via TWRP is a fix for the problem.
UPDATE EDIT: Well, the seller who sold me this phone, phonesandparts.com on eBay has agreed to take back the device and give me a full refund. Guess I will just do that and now that the Nexus 4 has dropped a $100 on price I can get a Nexus 4. I am tired of messing around with this, I love the device but not being able to flash anything is annoying as all get out, it might be fake, defective, or whatever, but guess I am moving on, just waiting for the RMA then I will have to move back to my old HTC Aria for a while and just deal with it for now and once my refund comes through grab a Nexus.
I flashed my i727 with JB rom, and after do that i recive that message when i tried charge my cell phone, so the sollution was install a Stock rom with odin and go back to ICS every time i try ti update my cellphone with any rom i get that message... but at least i can charge my cellphone again... i write this reply this post because it works for me, and if you had the same problem maybe this can be the solution...
---------- Post added at 11:07 AM ---------- Previous post was at 10:41 AM ----------
acejavelin said:
Changing radios to UCMC1 and installing TWRP recovery and rooting had no effect, with an ICS ROM the battery charges properly.
So this clearly seems to be kernel related with the JellyBean code of the kernel and how it is talking to the hardware, the stock kernel and Marla kernel have the same result... I tried Beanstalk 1.300.3 (Wrap-up 3) and the battery would not charge, in the *#*# menu under battery it showed the exact same thing, "Unknown error" and would not charge. Restore back to ICS from TWRP and everything was OK again. Think I will wait to see how it goes after I get an real Samsung battery, about 95% sure this battery is a fake, but in reading similar discussions on this with SGS2 models, the battery doesn't seem to be the issue but it's worth a shot. I might try a few ICS ROMs and see what happens and report back now that I know restoring back to stock ICS via TWRP is a fix for the problem.
UPDATE EDIT: Well, the seller who sold me this phone, phonesandparts.com on eBay has agreed to take back the device and give me a full refund. Guess I will just do that and now that the Nexus 4 has dropped a $100 on price I can get a Nexus 4. I am tired of messing around with this, I love the device but not being able to flash anything is annoying as all get out, it might be fake, defective, or whatever, but guess I am moving on, just waiting for the RMA then I will have to move back to my old HTC Aria for a while and just deal with it for now and once my refund comes through grab a Nexus.
Click to expand...
Click to collapse
I bought the same cellphone at the same seller and i have problems with the imei: null/null and i search here and maybe they flashed the cellphone with a new rom and lose the files of the EFS folder, so i cant unlock and use with my service network.. i will ask for a return item.
That's rotten luck for both of you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Well, the seller took back the phone, and issued me a full refund, so this is probably going to be one of my last posts in the Skyrocket forums since I am using those funds and ordered a LG/Google Nexus 4 16GB phone. I really liked the SR and would have kept it had it worked as I had hoped, but with all the issues I had I just figured this was a better way go than fighting with another one since Google dropped the price a $100 on the Nexus. Thanks for the help to everyone, enjoy your Skyrocket.
dgoby said:
So I decided to go ahead and put my findings of this issue that several of us have had with our phones getting the dreaded "Battery Disconnect" after upgrading from stock ICS to stock JB. I cannot guarantee that this will work for everyone but it did work for me.
Here are the different solutions I have come across in my research on this issue.
1: Battery corruption: get new battery
2: Gold prongs are dirty on phone and battery: clean them
3: Bad charger: get new charger
4: Dirt or dust in USB port: clean with compressed air
Now I tried each of these and unfortunately none worked for me. It has for some that I have read on different sites, so if you don't want to try and re-flash everything try those above.
For those that have tried each of above 4 and still have the issue, like myself, you can try the following. This worked for me, but you have to have patience. Read entire post before trying, check MD5 sums before any flashing and the typical disclaimer, I AM NOT RESPONSIBLE FOR YOU PHONE, TRY AT OWN RISK. Sorry, had to put that in.
1. Have your battery charged to 100%. You need to go back to ICS if you aren't already. If you are on JB right now, wipe your system clean (factory reset) that's including formatting system, data, cache, dalvic, etc. using CWM (that's just what I prefer for this part and what I used). Do a backup first of anything you don't want to lose. I used Titanium Backup Pro myself but pick your own poison. If already on ICS, proceed to step 4.
2: Using ODIN, flash ICS back on to your phone. If you haven't already looked at Vincom's guides, here you go. http://forum.xda-developers.com/showthread.php?t=1652398 and http://forum.xda-developers.com/showthread.php?t=1785999. Keep it plugged into the computer while it reboots. Should show battery charging. If not, do it over. DO NOT ADD CUSTOM RECOVERY AND ROOT.
3: Test all your chargers. Generic and OEM and any additional batteries you may have. Make sure they all work. If so, let it settle for about 10 minutes and then on to the next step.
4: Power off the device and boot into the stock recovery. Do a factory reset, choose reboot and when the phone powers off, take out your battery.
5: Now using ODIN, flash stock JB. Again, leave the phone plugged into the computer until it boots completely. As long as it is charging and not "Battery Disconnect" you're on the right track. If it does not boot, basically just sits on the AT&T symbol for an extended period of time which can happen, remove battery, reboot into stock recovery, factory reset and re-flash JB again. If it says "Battery Disconnect" after it boots, wipe, and re-flash JB again. DO NOT INSTALL CUSTOM RECOVERY OR ROOT YET. I did on my first attempt of these steps and immediately got the "Battery Disconnect". If you succeeded, on to the next step.
6: This is when your patience comes to affect. You need to let the phone settle. I gave mine 2 days of using and charging when dead without getting the "Battery Disconnect". It happened once after a full charge, but only once. I plugged it in while half charged to see what happened and it popped up. Later when it died and I plugged it in, it charged with no problems. Patience. Something about the drivers taking time to settle either in the rom itself or in the kernel for certain devices. Not sure which. I did re-install my apps but I did with using the Play Store and not with my backup. Make sure you are on Wi-Fi so you don't jack up your data usage.
7: Now that you have had two days of using and charging with no issues, fingers crossed, go ahead and install TWRP using ODIN (no wipes needed). After it reboots, again keep it plugged into the computer and if it is charging after boot without the dreaded phrase, CONGRATULATIONS! BUT, I would wait for at least one day before you try any custom roms on it. Again, let it settle first.
I know this is a lot. But again, this is what worked for me after trying for almost two weeks now to find a solution. Good luck everyone, I hope this works for you as well. And thank you Vincom for the guidance.
Click to expand...
Click to collapse
After step 4 I guess I need to put the battery back in before proceeding with 5 and ODIN right?
djandreski said:
After step 4 I guess I need to put the battery back in before proceeding with 5 and ODIN right?
Click to expand...
Click to collapse
Follow Vincom's steps to use Odin. Step 2. It will tell you when to put the battery back in.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So have you tried installing custom ROM like CM 10.2 or 10.1?
Does it charges properly?
djandreski said:
So have you tried installing custom ROM like CM 10.2 or 10.1?
Does it charges properly?
Click to expand...
Click to collapse
Until I did the novel I wrote above, nothing worked. Either it was an immediate disappointment or wouldn't work after the first charge. Since then the phone has worked perfectly with any rom. Even an aftermarket battery. I don't want to put "solved" in the OP until I get feedback from others that it worked for them as well.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I repeated the step 5 three times and every time the same. Right after reboot I get "Battery disconnected" error message. I re-flashed JB, as I said 3 times but every time i see that error.
So I don't know if I can continue and use my phone until full discharge, I am afraid that I can't charge the battery back, and revert to ICS.
djandreski said:
I repeated the step 5 three times and every time the same. Right after reboot I get "Battery disconnected" error message. I re-flashed JB, as I said 3 times but every time i see that error.
So I don't know if I can continue and use my phone until full discharge, I am afraid that I can't charge the battery back, and revert to ICS.
Click to expand...
Click to collapse
I have to ask of course, did you follow everything exactly? I.e. not rooting or installing custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dgoby said:
I have to ask of course, did you follow everything exactly? I.e. not rooting or installing custom recovery
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Of course, just plain stock JB ROM.
UPDATE:
Here is what I did. I used stock ICS for about a day, then I updated it with Kies, just to try my luck, and as you guess that stupid error poped up.
I continued from step 5 , so I reboot in recovery, did factory reset and install stock JB ROM with ODIN
djandreski said:
Of course, just plain stock JB ROM.
UPDATE:
Here is what I did. I used stock ICS for about a day, then I updated it with Kies, just to try my luck, and as you guess that stupid error poped up.
I continued from step 5 , so I reboot in recovery, did factory reset and install stock JB ROM with ODIN
Click to expand...
Click to collapse
Instead of using Kies I would use only Odin. I know you're running low on battery but I would start over but charge it up while on ICS. I was only successful using Odin in this process.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I recently upgraded to the 4.22 PAndroid ROM, however, I'm having a battery problem. Furthermore, this problem followed me when I switched over to the 4.22 CM ROM.
When I plug in my charging cord (OEM; have tried computer and wall plug), the phone charges for about 5 seconds before ceasing to charge. However, it charges fine if the phone is off. I've tried wiping the cache/factory resetting on both ROMs, but that didn't solve the problem either.
When I flash back to my current ROM, 4.12 PAndroid, the problem goes away completely and it charges on everything exactly as it should.
If anyone has any idea, I'd love to finally be able to use 4.22.
Thanks!
EDIT: I've used two different OEM cords, so I'm fairly certain it's not a hardware issue. Just to clarify.
Bump
Sent from my SAMSUNG-SGH-I727 using Tapatalk
SlushySolid said:
Bump
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
Bump again.
I've tried about 5 ROMs now. This is super frustrating because my current ROM will randomly stop receiving texts, and I don't know how to fix that. I would really appreciate any advice I can get about why I can't install a new one. My install order is:
Backup, Wipe Data, Wipe Cache, Wipe Dalvik, Format /system, ROM, GApps, Reset.
Even changing the kernel doesn't fix this problem.
Which recovery and version are you using? Try updating the recovery
jd1639 said:
Which recovery and version are you using? Try updating the recovery
Click to expand...
Click to collapse
CWM, just updated to the newest (6.0.4.3). Still not charging
Multiple problems(charging,texting) that you can't solve? Best bet would be to Odin back to stock, complete wipes and proceed from there.
jondroid2 said:
Multiple problems(charging,texting) that you can't solve? Best bet would be to Odin back to stock, complete wipes and proceed from there.
Click to expand...
Click to collapse
So, I did that this afternoon. Basically went back to stock, redid the recovery, and then flashed another ROM. It still wouldn't charge properly. Then, when I reverted back to stock (from a backup I did before the flash) I started getting warning pop ups with "Battery Disconnected." Now, even stock won't charge my phone, and now that it's dead, it won't charge when it's off either.
I'm beyond confused about where to go from here, and I'm very frustrated with my Skyrocket. I'm almost at the point of just jumping ship to a Nexus 5 haha. I would hate to waste about tree fiddy though if this is something that is still fixable.
SlushySolid said:
So, I did that this afternoon. Basically went back to stock, redid the recovery, and then flashed another ROM. It still wouldn't charge properly. Then, when I reverted back to stock (from a backup I did before the flash) I started getting warning pop ups with "Battery Disconnected." Now, even stock won't charge my phone, and now that it's dead, it won't charge when it's off either.
I'm beyond confused about where to go from here, and I'm very frustrated with my Skyrocket. I'm almost at the point of just jumping ship to a Nexus 5 haha. I would hate to waste about tree fiddy though if this is something that is still fixable.
Click to expand...
Click to collapse
go back to stock w/odin and see if prob persists, don't use ur backups and don't flash anything else, just stay on stock.
if jb stock fw fails then try stock firmware gingerbread and ics and test each one w/out flashing anything else, stay on pure stock.
some users did have issues w/charging on jb but cant remember their solution if any.
if prob is still there on stock, then it could be battery, battery contacts, bad cable, dirty phone port, bad phone port.
since it does charge albeit w/screen off you could try to live with that instead of chucking it
Found this old thread with a similar problem to what I'm seeing. I'm running liquidsmooth 3.2-2014-08-20 since late November but had something similar before I reinstalled this ROM.
I have two batteries - the original that's 3+ years old and a new Samsung battery bought 4 months ago. When I have the old battery in, it charges when the phone is off or on. With the new battery in, it charges fine when the phone is off. When the phone is on, it charges for about 5 seconds then stops. If the remaining battery is low, I then get the message popping up saying to plug in the charger. When the new battery is in my phone does recognize the chargerbecause it pops in to USB mode and because I have a Tasker profile that's triggered when it's powered. The triggered action doesn't revert until I unplug the cable.
Does this suggest my problem is with my new battery?
Robnw
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
I didn't. What I did have was bootlooping that started about 48 hours after installation. Stock, not rooted and very minimal apps. I ran a factory reset and it has been much better.
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
anbowlynn said:
My phone is bootlooping, too, after the update. My phone is also stock, not rooted. I'm afraid to do a factory reset, as I don't want to loose all of the photos of my new baby. I wish I hadn't delayed turning on my cloud back up.
Click to expand...
Click to collapse
( it was the same problem with my S5 from 5.0.1 to MM will never do same error save all yr data and do clean flash )
1- do just cache clean
2- you can flash the old MM tmb but dont flash csc flash HOME_csc
but wait for more suggestion but for me is that the only solution
hapakun said:
Hey Ya'll,
Updated my phone this morning with the official T-Mobile Nougat update and man is my phone lagging! Anyone else having this problem?
-Travis
Click to expand...
Click to collapse
same. s7 slow and laggy as hell crappy battery life. they did this with the s5 too. slowed it down with updates until youre forced for a new phone.
This last update definitely negatively impacted my battery life. Stock, no root, and I wiped cache. I'm not in the mood to do a factory reset. Weasles.