Related
I'll likely be purchasing a new TF700T and Dock today, probably at Best Buy (they've indicated they'll match Amazon and such). I doubt it will have JB onboard, so will need to do the update.
Since I'm starting completely fresh with this device, I imagine the update is the first thing I'll do, so will have no data or other files, settings, etc. for me to worry about. But I've read here that some have needed to do a cold boot or a factory reset to get things working right with JB.
So - what is the optimal way for me to get my new Tablet working best with JB? Just do the update and get started, or a cold boot and/or factory reset after the update is done? Any particular steps or actions that need to be taken?
Thanks for the help.
I just did the update without having to factory reset and/or cold boot.
rndmnss said:
I just did the update without having to factory reset and/or cold boot.
Click to expand...
Click to collapse
Thanks. I was also researching this at transformerforums.com and they have a protocol recommended to minimize the potential for problems, which includes a cold boot before and after updating the OS, as well as a Factory Reset as the final step. It sounds like possible overkill (although not harmful), and was just wondering if there were any consensus about an optimal way to do this for a brand new device.
Thought I'd get a "second opinion" here.
I did the update and then did a cold boot. No factory reset.
*shrugs*
On windows you reboot your pc after an install. (Usually. I never do...)
On Android you do a cold boot. It's the same process, except a regular restart on Android doesn't empty the memorycache.
DLCPhoto said:
Thanks. I was also researching this at transformerforums.com and they have a protocol recommended to minimize the potential for problems, which includes a cold boot before and after updating the OS, as well as a Factory Reset as the final step. It sounds like possible overkill (although not harmful), and was just wondering if there were any consensus about an optimal way to do this for a brand new device.
Thought I'd get a "second opinion" here.
Click to expand...
Click to collapse
Out of curiosity, what build number for your tablet??
buhohitr said:
Out of curiosity, what build number for your tablet??
Click to expand...
Click to collapse
Just bought it a couple of hours ago. Not sure exactly which numbers you're asking for, but here's what it says:
Build # JRO03C.US_epad-10.4.4.16-20120927
Plugged the Tablet in, it booted up and very quickly advised of a Firmware Update. I allowed this to proceed, but this wasn't the JellyBean update. The only setup I did was allow it to connect to my WiFi network.
I then checked Settings, System Update, and that's when it downloaded and did the JB update. Everything went smoothly. No problems.
So far I haven't done any cold boot or anything out of the ordinary. Guess it wouldn't hurt to cold boot now before I start testing it out.
DLCPhoto said:
Just bought it a couple of hours ago. Not sure exactly which numbers you're asking for, but here's what it says:
Build # JRO03C.US_epad-10.4.4.16-20120927
Plugged the Tablet in, it booted up and very quickly advised of a Firmware Update. I allowed this to proceed, but this wasn't the JellyBean update. The only setup I did was allow it to connect to my WiFi network.
I then checked Settings, System Update, and that's when it downloaded and did the JB update. Everything went smoothly. No problems.
So far I haven't done any cold boot or anything out of the ordinary. Guess it wouldn't hurt to cold boot now before I start testing it out.
Click to expand...
Click to collapse
OK, you already on JB. I thought you maybe lucky and still on .26, then I would recommend to save your bootloader with NVflash. Back to cold boot, if you have issue then you could try cold boot or worst case factory reset, but if you don't, it's not needed. This had happened to me after upgrade to JB, I did a cold boot and my table started to have randomly rebooted and blank screen issue.
buhohitr said:
OK, you already on JB. I thought you maybe lucky and still on .26, then I would recommend to save your bootloader with NVflash. Back to cold boot, if you have issue then you could try cold boot or worst case factory reset, but if you don't, it's not needed. This had happened to me after upgrade to JB, I did a cold boot and my table started to have randomly rebooted and blank screen issue.
Click to expand...
Click to collapse
So far so good. Just plugged in my Seagate 7200 RPM Expansion Portable HD, and it was recognized without problem. That's a big thing for this to work for me as hoped!
Hi all, I bought a new TF700 two days ago. I proceeded to successfully unlock, root, flash Cromi-x. After some teething problems got it working beautifully. Unfortunately my girlfriend noticed what looks like a big smear of some type of adhesive inside the glass. Kind of looks like something has wiped the back of glass or the panel itself, and has dried but with residue. Anyway its only visible when the screen is off or on a black background but I contacted Asus anyway and they immediately advised me to get it replaced at place of purchase.
I realise they don't normally allow this but they've given me the Return Authorisation number and the store has shipped the replacement device to my nearest store for collection. SO, do I just go ahead and swap it or do you think it will come back to bite me later on? Even if they do come back later and say they found it was unlocked, Ill have already unlocked + flashed the replacement so I figure whats the worst that can happen?
It seems the rumored 'database update' back to Asus when unlocking isnt accurate as I got through no problems and they checked serial number etc.
Any thoughts?
Great Minds Think Alike!
rogannzb said:
Hi all, I bought a new TF700 two days ago. I proceeded to successfully unlock, root, flash Cromi-x. After some teething problems got it working beautifully. Unfortunately my girlfriend noticed what looks like a big smear of some type of adhesive inside the glass. Kind of looks like something has wiped the back of glass or the panel itself, and has dried but with residue. Anyway its only visible when the screen is off or on a black background but I contacted Asus anyway and they immediately advised me to get it replaced at place of purchase.
I realise they don't normally allow this but they've given me the Return Authorisation number and the store has shipped the replacement device to my nearest store for collection. SO, do I just go ahead and swap it or do you think it will come back to bite me later on? Even if they do come back later and say they found it was unlocked, Ill have already unlocked + flashed the replacement so I figure whats the worst that can happen?
It seems the rumored 'database update' back to Asus when unlocking isnt accurate as I got through no problems and they checked serial number etc.
Any thoughts?
Click to expand...
Click to collapse
A fellow immediate modder...I like it
For me, you've already answered your own question. Once you've got your new tablet, what do you care? Even if they do notice that your original tablet was rooted, what are they going to do, force you to give the new one back....threaten to sue you if you don't? Not likely. You've got to remember that it's all about money for these guys, so once you've got your new tablet, even if they do spot your rooted original, it's going to cost them more to try to get the new one back from you than it would for them to just repair & re-sell the original.
I think that once you've got your new one, start enjoying it
Ok so Im taking it back tomorrow for replacement. But before I do...
For my reference can anyone explain to me how to flash this back to the stock Rom? I downloaded from Asus website, rebooted into TWRP and tried to install the stock software, which failed.
Also I'd like to know if I should be 'removing TWRP somehow? I know I cant reverse the unlock process but can I revert everything else back to factory configuration?
When one reboots via power and holding volume down, you get the menu with RCK, Android and Wipe Data - what are the definitions of RCK and Android? From what I gather one boots recovery and the other the installed ROM?
Finally - when one does a Restart from within Cromi and there are options for Bootloader and Recovery - what is the difference between these two options? Do they achieve the same things as the point above (ie reboot to recovery versus the installed rom?)
Thanks, sorry for the noob questions.
Unzip the zip from Asus first and you will see an update zip inside. Flash this from twrp and it will reset you back to stock.
rogannzb said:
Ok so Im taking it back tomorrow for replacement. But before I do...
For my reference can anyone explain to me how to flash this back to the stock Rom? I downloaded from Asus website, rebooted into TWRP and tried to install the stock software, which failed.
Also I'd like to know if I should be 'removing TWRP somehow? I know I cant reverse the unlock process but can I revert everything else back to factory configuration?
When one reboots via power and holding volume down, you get the menu with RCK, Android and Wipe Data - what are the definitions of RCK and Android? From what I gather one boots recovery and the other the installed ROM?
Finally - when one does a Restart from within Cromi and there are options for Bootloader and Recovery - what is the difference between these two options? Do they achieve the same things as the point above (ie reboot to recovery versus the installed rom?)
Thanks, sorry for the noob questions.
Click to expand...
Click to collapse
If you flash the stock firmware it will replace TWRP with the stock recovery.
If you bot with Power + Volume down you boot into the bootloader menu. Your correct on RCK and Android.
It is not recommended to use Wipe Data fro the bootloader if you have a custom recovery installed, btw. If you want to wipe do it fro TWRP.
The Restart options are just a more convenient way to boot into the bootloader or recovery .
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
Thanks to you both for the replies.
@ sbdags - Its funny I actually noticed the zip within the zip and after it failed the first time removed the zip out on its own. I astill got the same error message. To be clear, I was using the install option from within TWRP and selecting this file on my external sd card. Im re-downloading it now to test this again.
rogannzb said:
Thanks to you both for the replies.
@ sbdags - Its funny I actually noticed the zip within the zip and after it failed the first time removed the zip out on its own. I astill got the same error message. To be clear, I was using the install option from within TWRP and selecting this file on my external sd card. Im re-downloading it now to test this again.
Click to expand...
Click to collapse
I've done it lots of times and it works fine for me.
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
I just got a 6a. I have an older Pixel 3A XL that I am trying to trade in. The phone was rooted (but I just uninstalled Magisk) and I never took most updates so the phone is still on Android 10. I am wondering which stock firmware I should download to get this back to factory settings so I can lock the boot loader?
Do I need to download the newest Android 12 OTA update and then flash a stock rom or should I just download an Android 10 stock from and flash that?
Android 10 has less "surprises" in it... scoped storage will be fully enforced in 12.
dr0832 said:
I just got a 6a. I have an older Pixel 3A XL that I am trying to trade in. The phone was rooted (but I just uninstalled Magisk) and I never took most updates so the phone is still on Android 10. I am wondering which stock firmware I should download to get this back to factory settings so I can lock the boot loader?
Do I need to download the newest Android 12 OTA update and then flash a stock rom or should I just download an Android 10 stock from and flash that?
Click to expand...
Click to collapse
If you are trading it in, just back up anything you want from it, factory reset it and flash a factory image to it. Then run the OEM bootloader lock command. You can also go into Developer Options and turn off bootloader unlock and reset it again. Doesn't matter which factory image because you are not keeping the phone or selling it. When they get the phone, they will likely reflash the latest factory image to it anyway.
To reiterate, flash the factory image, not the OTA image. Factory images contain everything, including the modem/bootloader/etc. That way everything is likely to work together properly. Mismatched firmware/modem/bootloader from flashing an OTA can be a bad day.
So if I had my 4a rooted a couple years ago, but went back to stock, I should be able to just factory reset, right? No flashing needed? Does it matter if you send it back with bootloader unlocked?
tcat007 said:
So if I had my 4a rooted a couple years ago, but went back to stock, I should be able to just factory reset, right? No flashing needed? Does it matter if you send it back with bootloader unlocked?
Click to expand...
Click to collapse
I think you should re-lock the bootloader, just to be on the safe side; it's an easy thing to do. I had to do a warranty replacement for my Pixel 4 XL a few years ago and the google technician told me to relock the bootloader when returning the 'defective' device.
Google is not going to deny your trade in due to being rooted. This is not a warranty replacement! The only requirements are that the screen turns on and is not cracked.
Just go into settings and do a "factory reset" and turn the phone in. Doing anything more is simply a waste of time.
sic0048 said:
Google is not going to deny your trade in due to being rooted. This is not a warranty replacement! The only requirements are that the screen turns on and is not cracked.
Just go into settings and do a "factory reset" and turn the phone in. Doing anything more is simply a waste of time.
Click to expand...
Click to collapse
Yep, Im sure all our old devices are just promptly going in the trash or possibly to a donation project so theyre not going to care.
The best way to return your device to bone stock is with the Android Flash Tool. Ensure you check the "Force flash all partitions" and "Wipe device" boxes, as well as "Lock bootloader' if desired.