Help rooting AT&T xt1097, 5.1 2016.08.01 OTA Security - X 2014 Q&A, Help & Troubleshooting

Hi,
I'm trying to root my XT1097 running android 5.1 with the August 01 OTA security update. I've tried running the KingRoot APK but it gives an error "Not adaptable yet". I ran the Windows version and I get to 18% and then the device reboots (I've tried over 15 times). I also tried KingORoot and it fails each time at 51%. I went back to KingRoot and now it simply loses connection at 51%. At this point I must disable/re-enable usb debugging and restart KingRoot ad infintum.
Thanks for any help.

Try clearing the cache of KingRoot everytime you run it.
I rooted with KingRoot before the August security update. Though I had trouble with it but finally got it to work by clearing the cache each time.

Related

[Q] AT&T Software Update - Fails due to low battery

I've tried searching, but didn't seem to get anything on this one.
I've been trying to install the OTA Update to 4.3 for a minute, now... Currently, I've got the update downloaded, but it won't continue b/c it's saying the battery is too low. The thing is, the battery is at 100%. It is also plugged into a charger... Tried it with and without.
Here's info on my phone:
MJ5
Rooted via Kingo
Xposed Installer installed (very few modules installed - nothing hardcore)
RootCloak [1.4] installed in order to hide root status from the OTA update service
I have a bit of bloat uninstalled by Titanium Backup... But, that was all AT&T stuff like Navigator - I left the OTA service in place. I froze some Samsung bloat, but didn't uninstall it.
Any ideas on why I'm getting this error?
You have to be unrooted. At least that what I hear . When I got the update I did a factory reset and downloaded the update and installed with no issues.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Ah, great. Now Kingo won't re-root the phone. Looks like factory reset is what I'll be spending my evening doing.
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Pscheoverdrive said:
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Click to expand...
Click to collapse
Unfortunately nothing will work except restoring back to stock. I had to do that for the last 2 updates we've received. I just did it to get the last update and I am staying stock until Kitkat arrives then will look for a root solution. I know, it sucks.
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
Pscheoverdrive said:
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Click to expand...
Click to collapse
If you didn't uninstall the Xposed modules the uninstall Xposed that could be your issue right there. Try uninstalling everything root then try again.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Pscheoverdrive said:
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Click to expand...
Click to collapse
Factory reset just wipes your data and cache. It will not reinstall the system files. When you rooted you directly modified some of your system files via root access. Simple solution however. Follow these steps as mentioned before by theorioles33 using Odin and Heimdall. Takes about 10 mins (maybe 30 if its ur first time) Follow every step to the T and when ur back to stock try the OTA. Good Luck!

Randomly Lost Root? - No Updates/OTAs applied

Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.

Having Some Trouble. Lost my Root Access, Can't Seem to get it back

Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Disable OTA
Dmriskus said:
Hello,
I'm having issues with my new tablet. I followed the instructions outlined here
http://forum.xda-developers.com/amazon-fire/development/wip-achieving-root-thread-t3238152
And achieved root. All was well, but about 24 hours later, my tablet decided to restart, and when it rebooted, I no longer seemed to have root access. I then confirmed this with a root checker app. I still had the Google Play store, and the SuperSU app however. I checked using a file explorer and I still have an su file under /system/xbin.
I tried a reboot using the same method as above, but it seems to be failing because the files already exist. I tried uninstalling the SuperSU app using the full unroot option inside the app, but it simply says 'uninstalling, please wait' for a few seconds and then goes back to the home screen, SuperSU still there. I then attempted to restore to factory defaults, but alas the app remains and I am still unable to reboot (as well as losing all my data sadly). I am getting a drop down notification telling me that 'the SU binary needs to be updated' but that installation fails as well.
I'm unsure how to proceed trying to reroot my device, and feel stuck. Any help would be greatly appreciated. Also, I'm not sure what caused the device to restart and me to lose my root in the first place. From what I've read trying to figure this out, an OTA update may of caused me to lose my root, so I'm also wondering if there's anyway to prevent this from happening again if I can regain root.
Thanks
Click to expand...
Click to collapse
1. Disable updates, link one post up
2. Root in TWRP
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548

Multiple issues with my Moto G 2014

I had rooted my phone using Kingroot. When I got the notification saying that a new update us available, I unrooted my phone through Kingroot itself. I tried to install the update but it failed. Then I performed a factory reset through the settings and attempted the update once again. It failed, and another issue rose up with this. The Google app was not updating to the latest version and was stuck at version 4.1.24.1672412.arm. I reset my phone through the settings again but to no avail. There is no issue in running the phone, but the Google app in the play store now says that your device is not compatible with the current version of this app. And my device software is not updating to the latest version. Please help

Will the latest Update lose my root access?

I just picked up a used T817T yesterday. I was able to root it with Kingroot. I then found out that I lose root after a reboot. Even worse, without enabling the developer options and enabling the OEM unlock, it would no longer boot. I had to reflash the stock ROM with ODIN to recover.
I purchased and installed SuperSu Me-Pro and that replaced the Kingroot SU with SuperSu. Now I can reboot without losing root.
I'm being prompted to install an update T817TUVS2APB1/T817TTMB2APB1/T817TUVS2APB1. If I install this update, will I lose root? If I install it, can I still root with other methods?
I still have the stock recovery.
I'm currently on T817TUVS2AOL1.
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
DonS said:
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
Click to expand...
Click to collapse
Install it with Flashfire.

Categories

Resources