Database Develop

[Q] Update, OTA/Kies with root?

I have rooted my GS4A with odin. but now i see there is a update for my phone out.
i am still on mf7, but got an update for HM2(nordic countries).
and i cant update with OTA or kies, ("unit have been changed"). could i just download the firmware from ammobile and flash it with odin? and hopefully nothing is lost?
if someone could give me a writeup i would appriciate it.. want to stay with stock roms but still rooted.

Anyone?
Sent from my GT-I9295 using XDA Premium 4 mobile app

I just did the update myself - I use Triangle Away to work past the detection and do the OTA update, but I had to use the advanced features in the paid version to get it to work. After update you have to re-root it the same way you did the first time. Note that super su might not be installed automatically again, so you might have to uninstall it and reinstall from the playstore after rooting to get it working.
The Triangle Away setting I had to use is "System modified workaround", and the instructions are right below the setting. You enable it, reboot, then disable it and do the update before rebooting. First time I had to try a couple of times, this time I enabled and rebooted, then started the download of the update, then disabled it before installing, and it worked first try.
Good luck!

Cederic said:
I just did the update myself - I use Triangle Away to work past the detection and do the OTA update, but I had to use the advanced features in the paid version to get it to work. After update you have to re-root it the same way you did the first time. Note that super su might not be installed automatically again, so you might have to uninstall it and reinstall from the playstore after rooting to get it working.
The Triangle Away setting I had to use is "System modified workaround", and the instructions are right below the setting. You enable it, reboot, then disable it and do the update before rebooting. First time I had to try a couple of times, this time I enabled and rebooted, then started the download of the update, then disabled it before installing, and it worked first try.
Good luck!
Click to expand...
Click to collapse
Hi thanks for your reply. i fiddled with triangle away all morning, got my status to official. but i couldnt get it to work.
here is what i`ve done:
ticked off "System modified workaround", rebooted and downloaded the firmware. but when i try to disable the "SMW" I get an error from triangle away as it could not access superuser su/root access.. so i have to wait till supersu is enabled again to gain access to triangle away to disable "SMW".
tried again and again, but everytime i get an error that says "could not update, try with kies or contact samsung".

buljo said:
Hi thanks for your reply. i fiddled with triangle away all morning, got my status to official. but i couldnt get it to work.
here is what i`ve done:
ticked off "System modified workaround", rebooted and downloaded the firmware. but when i try to disable the "SMW" I get an error from triangle away as it could not access superuser su/root access.. so i have to wait till supersu is enabled again to gain access to triangle away to disable "SMW".
tried again and again, but everytime i get an error that says "could not update, try with kies or contact samsung".
Click to expand...
Click to collapse
Yeah that's the problem I had when I got the first update. What I did the second time was...
Tick system modified workaround
Reboot
Start download of update while root is not available
Click hide or whatever it is, the download will move to notifications
Wait until you have root back
Go into Triangle Away and untick system modified workaround
Proceed with update install (I think you click the notification once the download is complete).
Basically I'm guessing you have to be in the unrooted grace period to start the download, and then it won't check again, so just wait it out so you can disable it, but that's just a guess based on my fumbling around so far. If someone knows better, please correct me.

Cederic said:
Yeah that's the problem I had when I got the first update. What I did the second time was...
Tick system modified workaround
Reboot
Start download of update while root is not available
Click hide or whatever it is, the download will move to notifications
Wait until you have root back
Go into Triangle Away and untick system modified workaround
Proceed with update install (I think you click the notification once the download is complete).
Basically I'm guessing you have to be in the unrooted grace period to start the download, and then it won't check again, so just wait it out so you can disable it, but that's just a guess based on my fumbling around so far. If someone knows better, please correct me.
Click to expand...
Click to collapse
thank you fo such a fine list but still i only get a "couldnt resume with update, try kies or contact samsung".. my status is official according to triangle away.. hmmm
Edit: it worked with kies though, just took painstakinly much time...

Cederic said:
Yeah that's the problem I had when I got the first update. What I did the second time was...
Tick system modified workaround
Reboot
Start download of update while root is not available
Click hide or whatever it is, the download will move to notifications
Wait until you have root back
Go into Triangle Away and untick system modified workaround
Proceed with update install (I think you click the notification once the download is complete).
Basically I'm guessing you have to be in the unrooted grace period to start the download, and then it won't check again, so just wait it out so you can disable it, but that's just a guess based on my fumbling around so far. If someone knows better, please correct me.
Click to expand...
Click to collapse
system modified workaround is disabled in my phone, i have samsung grand i9082 with Super SU pro 1.65 and triangle away 3.00, what to do now to enable it

trychandan said:
system modified workaround is disabled in my phone, i have samsung grand i9082 with Super SU pro 1.65 and triangle away 3.00, what to do now to enable it
Click to expand...
Click to collapse
This forum is for the Galaxy S4 Active, you need to go to the Samsung Galaxy Grand forum:
http://forum.xda-developers.com/forumdisplay.php?f=2288

[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!

Help, Bricked after using Kingroot

The first few times I used Kingroot to achieve temp root, it worked great and then just went back to unrooted after a while. One time after rooting, it was spammed with error messages that the play store and other apps were crashing. I rebooted the phone and it seemed to fix it. The errors were gone and so was root. I tried kingroot again and I had the same problem. I did the same reboot and then deleted the kingroot app. I thought everything was fixed then until I plugged my phone in to charge. It shut down even though it was around 75%. I didnt know what i was doing so I put it in recovery mode and choose factory. I thought this would do a factory reset but now when my phone powers up all my apps and stuff is there. Please advise how to completely rid my device of kingroot. Thanks in advance
Update: When I started in factory mode, there was a testing app called commserver or something like that running. I saw in other forums to reboot to remove that and i did and it worked. Still would like advice on removing kingroot completely.

Jefff0101 said:
The first few times I used Kingroot to achieve temp root, it worked great and then just went back to unrooted after a while. One time after rooting, it was spammed with error messages that the play store and other apps were crashing. I rebooted the phone and it seemed to fix it. The errors were gone and so was root. I tried kingroot again and I had the same problem. I did the same reboot and then deleted the kingroot app. I thought everything was fixed then until I plugged my phone in to charge. It shut down even though it was around 75%. I didnt know what i was doing so I put it in recovery mode and choose factory. I thought this would do a factory reset but now when my phone powers up all my apps and stuff is there. Please advise how to completely rid my device of kingroot. Thanks in advance
Update: When I started in factory mode, there was a testing app called commserver or something like that running. I saw in other forums to reboot to remove that and i did and it worked. Still would like advice on removing kingroot completely.
Click to expand...
Click to collapse
To remove Kingroot completely, you need to reflash the system partition. You can do this by plugging your phone into a computer, installing the Verizon Upgrade Assistant, and using the "repair your phone" option. Doing this will wipe your phone, so backup any data first.

TheSt33v said:
To remove Kingroot completely, you need to reflash the system partition. You can do this by plugging your phone into a computer, installing the Verizon Upgrade Assistant, and using the "repair your phone" option. Doing this will wipe your phone, so backup any data first.
Click to expand...
Click to collapse
Thanks, I'm kinda a noob so could you walk through the steps like you were talking to a baby? Like do I put my phone in recovery mode and then download the version thing on the computer? How do you suggest backing up my phone? Sorry for the bother, I'm new to this stuff. Thanks again

Sure:
1. Boot your phone normally. Backup whatever data you want to preserve. Make sure that whatever backups you make are stored in a place that is outside of your phone.
The best way to backup your phone depends on what you want to backup. If you're worried about losing contacts, don't be. I'm pretty sure Google backs those up automatically. You can make sure by going to https://www.google.com/contacts/. If you see contacts there, you're good. If you're worried about losing pictures, plug your phone into a computer and use a file browser to copy the folder called DCIM to your computer. If you want to try backing up your texts, there's an app on the play store called Super Backup that might help. Just make sure that you transfer whatever backup file it makes to a cloud drive or your computer.
2. Plug your phone into a computer running Windows (I'm not sure if it what I'm about to describe works on a Mac or not, but I know that it does not work on Linux). You should get a pop-up that says something like "do you want to install the verizon upgrade assistant?" Install it. If you don't see the pop-up, install this instead: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. This is the Motorola Device Manager, and it's basically the same thing.
3. If you're using the Verizon tool, select "repair device" and follow the instructions. If you're using the Motorola tool, look for something that says "repair phone" or something like that, and follow those instructions.
4. The tool will wipe your phone, along with all of that nasty Kingroot stuff that tries to make modifications to /system despite the fact that /system is write-protected until you unlock with Sunshine (which is why it messed up your phone).
5. If you decide you want it, download Sunshine from here: http://theroot.ninja/download.html.
6. Go into your phone's security settings and allow installation of apps from unknown sources.
7. Click on the Sunshine apk that you downloaded to your phone to install it.
8. Open the Sunshine app and follow the instructions. If, when your phone reboots, you see a bootloader unlocked warning message instead of the black and white Motorola M symbol that usually appears, it was successful. If it was unsuccessful, keep trying. It should get it after a few tries.

Lost root access after a week, possibly by entering "smart manager"

I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..

I have the same problem?? Did you get any answer from any body? Do I have to re root again?

Just flash super su in recovery. Same thing happened to me and i don't know what is the cause of the problem

Roamin64 said:
I got a note 5 SM-N920W8 Telus last week. First thing i did was to upgrade to marshmallow, and then root it. I rooted it fine, wiping the phone in the process of installing the custom recovery. Now i've used plenty of apps that require root, and all have worked fine. About 15 minutes ago I try to go in "Ad away" to disable it temporarily to check if firefox was gonna to react faster on loading pages (it seemed so fast last week, but sluggish lately) only to find out Ad away is complaining I dont have root access anymore. So I go and check in SU , and sure enough, he also complains I don't have root. Marshmallow 6.0.1
Who deleted my root?
The only thing different I recall doing on my phone recently, and could coincide with me not noticing it between 2 apps that need root, was that in the settings, I went into "Smart manager". In there, I was curious to see what this "Device Security" (deactivated) could hold.
Anyone else has had their root removed? Or is there anything else I should look out for , background process or something , that targets my root? I just reflashed it, and it works fine again, but that just never happened to me before..
Click to expand...
Click to collapse
Im having similar issues. 6.0.1 on my tmo note 5 rooted perfectly using Max Lee's method. However as soon as I rooted and transfered all my data back I did a nandroid backup. Happen to wipe my phone the other night and and restored the nandroid backup and as soon as it restored I lost root. Happens everytime I restore even a newer nandroid in twrp. Never had this happen on any root method on any note.

WTF..
It's happened again this morning.. Root dissapeared by itself. The only recent thing I can think I did , was buying a game (The cave) from play store last night.
Any way to identify what is removing SU ?

Flash SuperSU 2.74 and delete 'SecurityLogAgent'

I also lost root
I have a Samsung Galaxy Note 5 on the Sprint Network. I just now noticed that my applications that require root access, including Titanium Backup are reporting that my device is no longer rooted. Weird. This has never happened in the past when I had rooted Samsung phones. I will re-flash the Super User file as instructed in this thread and see if that resolves the issue.
---------- Post added at 03:01 AM ---------- Previous post was at 02:32 AM ----------
Per your insstuctions, I reflashed SuperSU 2.74 using TWRP. Then once my Note 5 rebooted, I launched Titanium Backup and found "SecurityLogAgent" and uninstalled it. However, in order for me to access TWRP I have to reinstall it using ODIN and immediately after I get the green "PASS" light in ODIN I have to quickly do the 'three finger' button press to launch TWRP. Weird....
Anyway, so far so good.
Thank you.
Battlehero said:
Flash SuperSU 2.74 and delete 'SecurityLogAgent'
Click to expand...
Click to collapse

Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.

Bosbouer said:
Has a permanent solution been found? I am suffering the same inexplicable loss of root. International N910F on stock.
Click to expand...
Click to collapse
Yes, follow Battlehero's instructions (post #6) worked fine for me.

Roamin64 said:
Yes, follow Battlehero's instructions (post #6) worked fine for me.
Click to expand...
Click to collapse
Thanks that worked to a certain extent. Titanium requesting root privileges for backup would still pop up as failed. Checking root would show as unrooted. The Superuser app was updated on the 5th of July 2016. Since I applied that update, i have not lost root on any of my devices.

Root won't "stick"

I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??

Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.

Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...

I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app

Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?

Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..

Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?

Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...

Thanks! I'll give that a try when I get home today.

S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!

Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...

Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app

marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.

https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app