Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Vanb85 said:
Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Click to expand...
Click to collapse
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Davey126 said:
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Click to expand...
Click to collapse
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Vanb85 said:
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Click to expand...
Click to collapse
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Davey126 said:
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Click to expand...
Click to collapse
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Vanb85 said:
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Click to expand...
Click to collapse
Uninstalling KingRoot (KingUser) via conventional means also removes root. There are methods for transitioning a different root manager (eg: SuperSU) if you plan to stay on FireOS. SuperSume is one such tool. Does not seem to be effective against more recent KingRoot builds which actively resist removal.
Unlocking refers to the bootloader; wiping is a recommended prerequisite for cleanly replacing FireOS with a custom ROM. Wiping also removes KimgRoot detritus.
Anatinae said:
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Click to expand...
Click to collapse
Have you tried installing SuperSu or another root manager as a replacement since rooting with KingRoot?
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Anatinae said:
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Click to expand...
Click to collapse
I see. So you replaced KingRoot with the default root manager that came with the LineageOS build?
Update: I did install KingRoot. And I installed the Google Play Store after that. I was unable to replace KingRoot with SuperSu. So, I uninstalled KingRoot, and of course, it took root access with it. But I got what I wanted, for the most part, which was to be able to install the Google Play Store on my HDX. It appears to be working fine even without root access. I would have preferred to keep root access, but I don't really trust KingRoot enough to keep it on my device. Now, I just need to block updates so Amazon doesn't mess with GPS.
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Vanb85 said:
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Click to expand...
Click to collapse
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Davey126 said:
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Click to expand...
Click to collapse
Good to know. Yeah, it was just the one file. Thanks so much for your help.
Took delivery of a couple of HDX tablets today. I got a chance to try a "Replace Kingroot with SuperSU script" I modded for the HDX. The script was taken from supertools which also used chainfires root.sh script.
Anyway it seems to have worked perfect, I've two HDX on 4.5.5.2 with SuperSU on them instead of Kingroot 4.8.2 which was used in the script. That kingroot version rooted on the 2nd attempt on both tablets, both factory reset and unregistered.
Files attached feel free to modify as required.
any ideas
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
thumper_ss said:
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
Click to expand...
Click to collapse
Please don't cross post; responded in other thread.
Related
Hello,
I was rooted running OS 4.2.2 and everything was great until one day I came home from dinner, got out my kindle and saw the dreaded message: "OS Updated to 4.5.4." I forgot to disable OTA! I can't believe I made such a silly mistake, but now I'm wondering if I can rollback 4.5.4 to 3.2.8, and then update to 4.5.2 and root. Does this only work for 4.5.3, or is it possible on 4.5.4? If it is possible, can someone link me to instructions?
Thanks,
Zman8881
Update
I talked to Arun from Amazon support who said it's not possible. He did, however, credit my Amazon account with $5.00 and tell me that an update resolving the inability to rollback will be available soon (EDIT: he later said 3-4 months, nevermind...) , meaning hope for myself and all of you out there who made the same mistake that I did.
EDIT: Is there any backdoor way to downgrade that someone can think of? I have no use for this device without a root, so I'm willing to risk bricking it.
-Zman8881
Zman8881 said:
Hello,
I was rooted running OS 4.2.2 and everything was great until one day I came home from dinner, got out my kindle and saw the dreaded message: "OS Updated to 4.5.4." I forgot to disable OTA! I can't believe I made such a silly mistake, but now I'm wondering if I can rollback 4.5.4 to 3.2.8, and then update to 4.5.2 and root. Does this only work for 4.5.3, or is it possible on 4.5.4? If it is possible, can someone link me to instructions?
Thanks,
Zman8881
Click to expand...
Click to collapse
The 'classic' 3.2.8 rollback method has reportedly worked for some. There does not appear to be any harm in trying; your device will either accept/recognize the file or not. Obviously follow all the usual cautions if you are successful (eg: keep WiFi off at all times!).
Zman8881 said:
I talked to Arun from Amazon support who said it's not possible. He did, however, credit my Amazon account with $5.00 and tell me that an update resolving the inability to rollback will be available soon (EDIT: he later said 3-4 months, nevermind...) , meaning hope for myself and all of you out there who made the same mistake that I did.
EDIT: Is there any backdoor way to downgrade that someone can think of? I have no use for this device without a root, so I'm willing to risk bricking it.
-Zman8881
Click to expand...
Click to collapse
I highly doubt Amazon is addressing the rollback issue. Why would they do that? The tech had a good laugh at your expense. Best path (aside from attempting a 3.2.8 rollback) is to enjoy or shelve your device until a root exploit becomes available for 4.5.4. You will need to keep it off the network as Amazon will undoubtedly push new updates that will be root resistant. And no - there is no known (or at least well communicated) way to root 4.5.4 as of now.
Davey126 said:
The 'classic' 3.2.8 rollback method has reportedly worked for some. There does not appear to be any harm in trying; your device will either accept/recognize the file or not. Obviously follow all the usual cautions if you are successful (eg: keep WiFi off at all times!).
I highly doubt Amazon is addressing the rollback issue. Why would they do that? The tech had a good laugh at your expense. Best path (aside from attempting a 3.2.8 rollback) is to enjoy or shelve your device until a root exploit becomes available for 4.5.4. You will need to keep it off the network as Amazon will undoubtedly push new updates that will be root resistant. And no - there is no known (or at least well communicated) way to root 4.5.4 as of now.
Click to expand...
Click to collapse
Can you by chance link me to instructions and/or the link for the 3.2.8 rollback method?
Okay, so here is the rollback file, but I urge you to proceed with caution. If you let Amazon update this build, you are ensured a brick. You need to use the hdx toolkit to block OTA on *.3.2.8.
http://forum.xda-developers.com/showthread.php?p=59220996
Good luck.
Zman8881 said:
Can you by chance link me to instructions and/or the link for the 3.2.8 rollback method?
Click to expand...
Click to collapse
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
One Last Question...
Davey126 said:
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
Click to expand...
Click to collapse
Thanks for all of the help... Just one last question. What is the name of the internal storage folder on the kindle that I should put the file in? Sorry, I'm new to Android. Believe it or not, I won my Kindle Fire from an arcade machine! Sorry again.
-Zman8881
Zman8881 said:
Thanks for all of the help... Just one last question. What is the name of the internal storage folder on the kindle that I should put the file in? Sorry, I'm new to Android. Believe it or not, I won my Kindle Fire from an arcade machine! Sorry again.
-Zman8881
Click to expand...
Click to collapse
Hey - congrats on the win! The rollback file goes in the root of sdcard when viewed from a tool such as ES File Explorer. If you have tethered your Kindle drop it into "internal storage" which is the base folder when viewed from Windows. After the file is in place reboot. If nothing seems to happen (give it 5-10 min) use the 'check for updates' function from within FireOS (located somewhere under settings). At some point the file will either be recognized/processed, recognized/rejected or ignored all together. Post back your results.
Although it has probably been burned into your brain be sure to do whatever is necessary to prevent network access if your Kindle rolls back to 3.2.8.
Davey126 said:
Hey - congrats on the win! The rollback file goes in the root of sdcard when viewed from a tool such as ES File Explorer. If you have tethered your Kindle drop it into "internal storage" which is the base folder when viewed from Windows. After the file is in place reboot. If nothing seems to happen (give it 5-10 min) use the 'check for updates' function from within FireOS (located somewhere under settings). At some point the file will either be recognized/processed, recognized/rejected or ignored all together. Post back your results.
Although it has probably been burned into your brain be sure to do whatever is necessary to prevent network access if your Kindle rolls back to 3.2.8.
Click to expand...
Click to collapse
I thought I did it, but after I hit update, I was stopped by an error message telling me that an update isn't possible because the update I'm trying to install is an earlier version than what I have on my device. Oh well, I guess it will be a long wait until someone finds a root exploit for 4.5.4. Thanks for all of your help!
-Zman8881
Zman8881 said:
I thought I did it, but after I hit update, I was stopped by an error message telling me that an update isn't possible because the update I'm trying to install is an earlier version than what I have on my device. Oh well, I guess it will be a long wait until someone finds a root exploit for 4.5.4. Thanks for all of your help!
-Zman8881
Click to expand...
Click to collapse
Sorry it didn't work. There is a way around that message but you need root to make the change. Catch 22.
The wait may not be that long. Fingers crossed
Couple more questions
Davey126 said:
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
Click to expand...
Click to collapse
Hey, Davey126, sorry to post here again quite a while after it's relevant, but I had a couple more questions.
You state here that you just have to make sure the wifi is not enabled, so OTAs aren't pushed. But another user (below) seems to push that I'll have to use the HDX Toolkit--which I can't seem to figure out how to actually use; is just disabling the wifi enough to keep it from bricking from an immediate OTA after the rollback?
lekofraggle said:
Okay, so here is the rollback file, but I urge you to proceed with caution. If you let Amazon update this build, you are ensured a brick. You need to use the hdx toolkit to block OTA on *.3.2.8.
http://forum.xda-developers.com/showthread.php?p=59220996
Good luck.
Click to expand...
Click to collapse
I haven't actually tried to get the update to be recognized yet, because I want everything to be sorted out question wise before diving in, but let's say it works and I get my kindle to roll back. How would I then get it up to 4.5.2?
Sorry for the questions! I just can't seem to find the answers anywhere else.
Rvby1 said:
Hey, Davey126, sorry to post here again quite a while after it's relevant, but I had a couple more questions.
You state here that you just have to make sure the wifi is not enabled, so OTAs aren't pushed. But another user (below) seems to push that I'll have to use the HDX Toolkit--which I can't seem to figure out how to actually use; is just disabling the wifi enough to keep it from bricking from an immediate OTA after the rollback?
I haven't actually tried to get the update to be recognized yet, because I want everything to be sorted out question wise before diving in, but let's say it works and I get my kindle to roll back. How would I then get it up to 4.5.2?
Sorry for the questions! I just can't seem to find the answers anywhere else.
Click to expand...
Click to collapse
Good questions; I appreciate you looked around before posting. If your intent is to rollback to 3.2.8 and then immediately upgraded to 4.5.2 there is no need to block OTA updates on 3.2.8 provide WiFi remains off (as an added precaution I would keep your device in Airplane mode). However, you'll need to enable WiFi for a few seconds while rooting. While that's not enough time to download a complete update a file fragment could potentially cause complications. Hence an OTA block could be beneficial. Really depends how fast you work and whether you can detect an incoming OTA update. You'll need to remove the block before upgrading to 4.5.2.
HDX Toolkit is a tethered solution. It runs on a Windows host and requires USB debugging to be enabled. Commands are issued to your device via the tether. Nothing needs to be installed on your device. You will also want a working tether to copy the 4.5.2 bin and possibly other files to your device when it's time to upgrade. Some folks load everything on the device in advance but I prefer to copy files as they are needed.
Davey126 said:
Good questions; I appreciate you looked around before posting. If your intent is to rollback to 3.2.8 and then immediately upgraded to 4.5.2 there is no need to block OTA updates on 3.2.8 provide WiFi remains off (as an added precaution I would keep your device in Airplane mode). However, you'll need to enable WiFi for a few seconds while rooting. While that's not enough time to download a complete update a file fragment could potentially cause complications. Hence an OTA block could be beneficial. Really depends how fast you work and whether you can detect an incoming OTA update. You'll need to remove the block before upgrading to 4.5.2.
HDX Toolkit is a tethered solution. It runs on a Windows host and requires USB debugging to be enabled. Commands are issued to your device via the tether. Nothing needs to be installed on your device. You will also want a working tether to copy the 4.5.2 bin and possibly other files to your device when it's time to upgrade. Some folks load everything on the device in advance but I prefer to copy files as they are needed.
Click to expand...
Click to collapse
Gotcha!
Actually, thanks a bunch for not only explaining the tool a bit, but prompting me to go take another look at it. Turns out I was downloading the wrong batch of files--everything seems to be working now. You just tether your kindle and tell it to block OTA, right? Don't have to worry about version number or anything like that?
So with upgrading to 4.5.2, is the process pretty well the same as with downgrading to 3.8.2? If so, where can I find the update file?
Thanks a million!
Rvby1 said:
Gotcha!
Actually, thanks a bunch for not only explaining the tool a bit, but prompting me to go take another look at it. Turns out I was downloading the wrong batch of files--everything seems to be working now. You just tether your kindle and tell it to block OTA, right? Don't have to worry about version number or anything like that?
So with upgrading to 4.5.2, is the process pretty well the same as with downgrading to 3.8.2? If so, where can I find the update file?
Thanks a million!
Click to expand...
Click to collapse
HDX Toolkit only works on FireOS v3 (3.2.8 and below). After rolling back to 3.2.8 tether your Kindle and use the toolkit to block OTA. Once OTA is blocked you can enable WiFi and use towelroot to root. Gather any other files you may need on your device, disable WiFi (also recommend 'airplane mode') and then use the toolkit to reenable OTA (under '5 More'). Move the 4.5.2 bin (here) to the root of sdcard and check for updates. Once on 4.5.2 you'll need to root and block OTA once again. Check the forums for the appropriate tools and method for FireOS v4. Kingroot and renaming DeviceSoftwareOTA.apk seem to be the most reliable.
Davey126 said:
HDX Toolkit only works on FireOS v3 (3.2.8 and below). After rolling back to 3.2.8 tether your Kindle and use the toolkit to block OTA. Once OTA is blocked you can enable WiFi and use towelroot to root. Gather any other files you may need on your device, disable WiFi (also recommend 'airplane mode') and then use the toolkit to reenable OTA (under '5 More'). Move the 4.5.2 bin (here) to the root of sdcard and check for updates. Once on 4.5.2 you'll need to root and block OTA once again. Check the forums for the appropriate tools and method for FireOS v4. Kingroot and renaming DeviceSoftwareOTA.apk seem to be the most reliable.
Click to expand...
Click to collapse
Okay, thanks so much for all the information! I actually just got my kindle to rollback to 3.2.8, but this brought up two more questions for me.
With the HDX Toolkit, it's asking me to grant root access on the device, which I can't do yet until it blocks OTAs; despite this message, it seems to go through and, after displaying the same message 5 times, state that OTAs are blocked. Is there anyway to safely check that they've actually been blocked? Also, is doing it twice okay? The message seemed less than assuring, so I did it again, but it displayed a different message 5 times on the second attempt.
Lastly, I want to root 3.2.8 and /then/ update to 4.5.2, right?
Thanks so much!
Rvby1 said:
Okay, thanks so much for all the information! I actually just got my kindle to rollback to 3.2.8, but this brought up two more questions for me.
With the HDX Toolkit, it's asking me to grant root access on the device, which I can't do yet until it blocks OTAs; despite this message, it seems to go through and, after displaying the same message 5 times, state that OTAs are blocked. Is there anyway to safely check that they've actually been blocked? Also, is doing it twice okay? The message seemed less than assuring, so I did it again, but it displayed a different message 5 times on the second attempt.
Lastly, I want to root 3.2.8 and /then/ update to 4.5.2, right?
Thanks so much!
Click to expand...
Click to collapse
The OTA blocker in HDX Toolkit is very comprehensive (probably overkill). Some actions require root, others do not. I suspect OTA is effectively blocked but there is no way to conclusively test. Suggest rooting with towelroot (you'll need to toggle WiFi momentarily) and then run the OTA blocker again. Multiple executions should have no adverse consequences. While unlikely to happen watch for any signs of a download in progress. If you see it turn off WiFi and post back for further instructions.
Remember to undo the OTA block after the 4.5.2 bin is in place; otherwise your device won't 'see' it.
Technically you don't absolutely have to root 3.2.8 to upgrade to 4.5.2 but I find it much easier to move files around and take corrective action if something goes wrong. Downside is root gives you unfettered access to everything; navigate carefully.
Davey126 said:
The OTA blocker in HDX Toolkit is very comprehensive (probably overkill). Some actions require root, others do not. I suspect OTA is effectively blocked but there is no way to conclusively test. Suggest rooting with towelroot (you'll need to toggle WiFi momentarily) and then run the OTA blocker again. Multiple executions should have no adverse consequences. While unlikely to happen watch for any signs of a download in progress. If you see it turn off WiFi and post back for further instructions.
Remember to undo the OTA block after the 4.5.2 bin is in place; otherwise your device won't 'see' it.
Technically you don't absolutely have to root 3.2.8 to upgrade to 4.5.2 but I find it much easier to move files around and take corrective action if something goes wrong. Downside is root gives you unfettered access to everything; navigate carefully.
Click to expand...
Click to collapse
Gotcha!
Alright. I think this is the final question before I go through with everything: on rooting with Towelroot, can I just use the HDX Toolkit for that? It says it only works up to 13/14.3.2.6 and below, so I just want to be safe.
Rvby1 said:
Gotcha!
Alright. I think this is the final question before I go through with everything: on rooting with Towelroot, can I just use the HDX Toolkit for that? It says it only works up to 13/14.3.2.6 and below, so I just want to be safe.
Click to expand...
Click to collapse
Neither Towelroot nor HDX toolkit has changed much (if at all) in the past 12-18 months. The version range was likely current when coded. It can't hurt to try; it will either work or not with no side effects. If it doesn't work head off to towelroot.com for the official variant. Obviously this means keeping WiFi on for a longer period.
Davey126 said:
Neither Towelroot nor HDX toolkit has changed much (if at all) in the past 12-18 months. The version range was likely current when coded. It can't hurt to try; it will either work or not with no side effects. If it doesn't work head off to towelroot.com for the official variant. Obviously this means keeping WiFi on for a longer period.
Click to expand...
Click to collapse
Got Towelroot to go through, despite a weird error the first execution. I didn't seem to have to enable wifi at all, believe it or not, and HDXTools said I was properly rooted.
I've been searching for the past hour or so, but I can't for the life of me find anything that clearly states how to go about rooting 4.5.2 once I get my kindle updated. I've found the supposed root file through the rollback thread, but I can't find out how to actually use it. As for Kingroot, I can only seem to find threads for 4.5.3. Can you impart any knowledge to me about this?
Also, in trying to find the solution, I found another post by you:
Davey126 said:
You'll need to follow the guide linked by ggow (here) which is rather technical and requires a Windows host to complete (there are variants for Linux and OS X) plus a fair bit of technical knowledge. There are no canned tools, videos or step-by-step tutorials. Unlocking is not risky (failed attempts won't harm your device) but it can be a frustrating experience.
If unlocking feels uncomfortable you can do a controlled upgrade to FireOS 4.5.2 and then install Safestrap v4 followed by Nexus v4 or CM11. However, you will permanently loose the ability to unlock your bootloader which is the key to running roms like Nexus and CM in 'native' mode. Unlocking also offers greater recovery capability should something go wrong.
There is also the 'do nothing' option which leaves you with a perfectly serviceable device running a very nice Nexus rom (Jelly Bean 4.2 based).
Click to expand...
Click to collapse
From all that I've read, it seems like we can only go back as far as 3.2.8 now. Is it too late to unlock the bootloader? Sorry for bringing an entirely different thread here, haha--I just want to make sure I get everything done in one fell swoop.
Rvby1 said:
Got Towelroot to go through, despite a weird error the first execution. I didn't seem to have to enable wifi at all, believe it or not, and HDXTools said I was properly rooted.
Click to expand...
Click to collapse
Surprised about that but glad it worked! Perhaps the version built into HDX Toolkit contains the bits & pieces that normally require online access.
Rvby1 said:
I've been searching for the past hour or so, but I can't for the life of me find anything that clearly states how to go about rooting 4.5.2 once I get my kindle updated. I've found the supposed root file through the rollback thread, but I can't find out how to actually use it. As for Kingroot, I can only seem to find threads for 4.5.3. Can you impart any knowledge to me about this?
Click to expand...
Click to collapse
Kingroot works great on 4.5.2 and is far easer than the alternative methods. Some question the origins of Kingroot (China) but the tool is widely used across a variety of platforms. Personally I could care less where it comes from as long as the reputation is solid. Sharing this in case you have a different perspective.
Rvby1 said:
Also, in trying to find the solution, I found another post by you:
[removed - see previous post for content]
From all that I've read, it seems like we can only go back as far as 3.2.8 now. Is it too late to unlock the bootloader? Sorry for bringing an entirely different thread here, haha--I just want to make sure I get everything done in one fell swoop.
Click to expand...
Click to collapse
As your start point was FireOS v4 your device was never eligible for bootloader unlocking. More specifically, Amazon fixed the vulnerability that allowed bootloader signature forging in 3.2.4. Clever folks figured out how to roll back to 3.2.3 up through 3.2.6. Starting with 3.2.7 Amazon became aggressive about blocking rollbacks. Any attempt to do so will blow an efuse which is equivalent to a brick. It's always possible another vulnerability will be discovered in higher firmware levels that permits bootloader unlocking. Don't hold your breath.
Ok.. so.. I keep seeing people saying there is a way to root still if you are on GOC1.. but I can't find anything that says what that way is. I also see 5.1 roms for this phone, but nothing that says how to install the bootloader it requires to install them. On my old phone, a Droid X2 you had to root before you could install a bootloader before you could install a rom. I am not seeing any straight up guides on here for working with this S4.
What I really want is just a basic root, so I can uninstall all the hardcoded crapware on this phone (NFL Mobile, Trip Advisor, etc..)
Short of that I want to install CM 12.1, which is probably a better route anyway, but the page for that says you must be on so and so bootloader without telling you how to INSTALL said bootloader. I'm totally lost here, things were a bit more straight forward on that old phone.
Edit: Yeah, I think what I really want to do is install CM 12.1, but I don't even know where to start.
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
skepticmisfit said:
you can't install cm12.1 or any version of cyanogenmod. the bootloader on this device is locked, meaning no custom recovery and ROMs. there is one bootloader that is the target of an exploit called Loki (basically, boot images and recoveries have to be patched in order to work, most popular ones are) but it only works with VRUAMDK, a bootloader that shipped with the device in like July 2013 when the s4 first released.
for oc1, you can root using the kingroot desktop version. Google it
Click to expand...
Click to collapse
Kingroot doesn't work. I don't know what its saying in the orange text after I run it since its not in english, but it doesn't work.
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Try getting KingRoot desktop version 3.0 I just used it on Version I545VRUGOC1 that I did the OTA update with and got it rooted I can use Titanium Backup to remove all samsung Knox and other bloat wear.
bangdosa said:
I did some rough translations of kingroot statements here from someone's pictures using google trans. Maybe they'll help.
also, people have said that if kingroot fails the first time, uninstall, restart comp and reinstall before trying again, as the system tends to stay on even after closing the program.
p.s. probably not worth mentioning, but, remember to have USB debugging turned on.
Click to expand...
Click to collapse
I gave kingroot another try since I had rebooted a couple of times since making this post, it worked this time! Huge thanks for that tip.
XxD34THxX said:
As far as ROMs if and when you get root, you need flashfire and Stangs ROM. It's modded and debloated OC1
Click to expand...
Click to collapse
Thank your for that. Flashfire is in the process of installing the rom. We'll see how it goes.
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
DallasDave said:
DiaSin did everything work out for you? Kingroot desktop makes me nervous. I download the desktop version and it didn't work for me so I tried to uninstall the desktop version and it wouldn't uninstall from my computer.
Click to expand...
Click to collapse
Just use the KingRoot app to root. It worked for me on first try.
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
kkcheong said:
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
Click to expand...
Click to collapse
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Thanks. I thought only 4.5.5.1 supported based on first page of the downgrade thread. Upon reading, seems like work on 4.5.5.2 too.
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
bigboolean said:
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
Click to expand...
Click to collapse
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Davey126 said:
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Click to expand...
Click to collapse
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Archangel1183 said:
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Click to expand...
Click to collapse
- TowelRoot typically roots within seconds; KingRoot can take many iterations
- KingRoot modifies various system files and installs additional components (crapware) without permission
- KingRoot actively resists uninstallation with each revision being increasingly difficult to remove
- TowelRoot is only effective against FireOS 3.x (Android 4.2 based); Kingroot works on a much wider range of Android builds and at present is the only reliable root solution for FireOS v4 and v5
I just rooted my Kindle HDX 7 firmware version 4.5.5.2 with Kingroot v. 4.9.2. You just have to be "VERY PERSISTENT" because it root will fail over and over again but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
RMNDGGG said:
... but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
Click to expand...
Click to collapse
It's not Amazon's firmware somehow resisting rooting; KingRoot's vulnerability detection and exploit matching algorithm is (generously) unsophisticated. Not much better than trial and error with a short fuse.
Also consider unlocking the bootloader and installing a custom ROM (ie: pure Android) to fully liberate your device. You'll probably want to do this anyhow to remove the malware like detritus KingRoot leaves behind.
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Archangel1183 said:
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Click to expand...
Click to collapse
You will need to unlock the bootloader first: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Archangel1183 said:
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Click to expand...
Click to collapse
Likely reamed the wrong file(s). If you haven't unlocked the bootloader it's pretty much game over. You can try a 'factory reset' from the stock recovery menu but that rarely fixes system problems. Stock recovery does not offer the ability to reload or repair FireOS. Sorry ...
Yeah, I think I did one too many files. The post I read only mentioned one file but I found two with similar names. I'll try a factory reset later. Thanks, Davey.
I used the Kindle Fire Unbrick Utility V1.1 that I found on the forums. I tried a couple different options offered in the tool and it seemed like none of them were doing anything. They kept saying "Device not found". I knew the computer was detecting it because I installed the drivers a couple weeks back and it was showing "Fire" in device manager. I was done with the tool and was going to use this unbricking method (forum.xda-developers.com/showthread.php?t=2793253), when my kindle suddenly went passed the boot screen into my lock screen. I unlocked it and again got a black screen. I wanted to get into ES File explorer to rename the 2nd file back to the original name, but I couldn't see any app icons. I accidentally swiped up from the bottom and a menu with app icons popped up. I was then able to get into ES File explorer and rename the file. I exited the app and wooot.... no more black screen.
For anyone reading this..... DO NOT Rename DeviceSoftwareOTAContracts.apk or you will get a black home screen without any apps. I renamed DeviceSoftwareOTA.apk to DeviceSoftwareOTAold (no apk) and it's working fine. So far my Kindle fire HDX 7 is still rooted.
Huge thanks to vadosnake for discovering this !
It's been a wait of 2 years, and King root has finally achieved root on this device. This method was tested on the Lollipop firmware, and others have said it works on KitKat as well. To root the G850A, follow these steps:
1.) Download the two APKs provided below, which we'll need for later
2.) Enable Unknown Sources by going to Settings, then Security, and the option should be right there
3.) Now install KingRoot 4.81. A message will pop up saying that the app is malicious, but just click "Install Anyway"
4.) Now enter the King root app and click Root. The phone will reboot, but that is normal. Go back into the app again and the process should continue until it's complete. Voila, your phone is now rooted. However, we will be replacing KingRoot with SuperSU.
5.) Install the second APK called SuperSume. After it's done, click the big green button, give it root access, and it will replace KingRoot with SuperSU in 1 minute.
6.) Go into the Play Store and update SuperSU. After it's done updating, go into the app and it will pop up with a message saying to update the binaries. Click continue then "Normal". DO NOT CLICK TWRP/CWM, OR IT WILL SOFTBRICK YOUR DEVICE.
7.) After that., you're done. You now have root with SuperSU.
Please make sure to show this to AT&T Galaxy Alpha users. Especially developers, so we can get some roms
Did anyone try this? Why does King Root need internet access to root? I'm afraid to turn on the internet in case it tries to steal data.
PopTartKing said:
Huge thanks to vadosnake for discovering this !
It's been a wait of 2 years, and King root has finally achieved root on this device. This method was tested on the Lollipop firmware, and others have said it works on KitKat as well. To root the G850A, follow these steps:
1.) Download the two APKs provided below, which we'll need for later
2.) Enable Unknown Sources by going to Settings, then Security, and the option should be right there
3.) Now install KingRoot 4.81. A message will pop up saying that the app is malicious, but just click "Install Anyway"
4.) Now enter the King root app and click Root. The phone will reboot, but that is normal. Go back into the app again and the process should continue until it's complete. Voila, your phone is now rooted. However, we will be replacing KingRoot with SuperSU.
5.) Install the second APK called SuperSume. After it's done, click the big green button, give it root access, and it will replace KingRoot with SuperSU in 1 minute.
6.) Go into the Play Store and update SuperSU. After it's done updating, go into the app and it will pop up with a message saying to update the binaries. Click continue then "Normal". DO NOT CLICK TWRP/CWM, OR IT WILL SOFTBRICK YOUR DEVICE.
7.) After that., you're done. You now have root with SuperSU.
Please make sure to show this to AT&T Galaxy Alpha users. Especially developers, so we can get some roms
Click to expand...
Click to collapse
cqdiep said:
Did anyone try this? Why does King Root need internet access to root? I'm afraid to turn on the internet in case it tries to steal data.
Click to expand...
Click to collapse
It needs Internet access to search in their database for a root solution.
I got SuperSU to install, but it can't update the binaries. It says "Installation failed! Please reboot and try again." after trying to update the binaries. The Root Checker app did confirm that it was rooted.
PopTartKing said:
It needs Internet access to search in their database for a root solution.
Click to expand...
Click to collapse
cqdiep said:
I got SuperSU to install, but it can't update the binaries. It says "Installation failed! Please reboot and try again." after trying to update the binaries. The Root Checker app did confirm that it was rooted.
Click to expand...
Click to collapse
For now, I tend to leave the app closed, and just wait until root prompts appear for root apps
Yeah, I'm doing that too.
PopTartKing said:
For now, I tend to leave the app closed, and just wait until root prompts appear for root apps
Click to expand...
Click to collapse
No Luck
I just ran the included 4.8.1 and online 5.0.1 versions, neither worked. So I tried the 4.8.1 a few times (including restarts) and the Super-SuMe anyway, but it didn't do anything past "Preparing environment" for 20 minutes.
Additional note, the 4.8.1 seems to have problems in general. After trying to root and failing, it'll continue using 80% of my cpu on some other processes within it's directory (mostly Schrodinger).
I'm running Android 5.0.2 (G850AUCU1BOC7), Kernel 3.4.0-4486597, Build LRX22G. It's the last update ATT gave us.
zyphuris55 said:
I just ran the included 4.8.1 and online 5.0.1 versions, neither worked. So I tried the 4.8.1 a few times (including restarts) and the Super-SuMe anyway, but it didn't do anything past "Preparing environment" for 20 minutes.
Additional note, the 4.8.1 seems to have problems in general. After trying to root and failing, it'll continue using 80% of my cpu on some other processes within it's directory (mostly Schrodinger).
I'm running Android 5.0.2 (G850AUCU1BOC7), Kernel 3.4.0-4486597, Build LRX22G. It's the last update ATT gave us.
Click to expand...
Click to collapse
Same, tried both 4.8.1 and 5.0.1, neither worked. Same android and baseband version as yours.
Thanks so much for this. I'm curious exactly which version of Lollipop on the g850a this was tested and working on? Was it specifically 5.0.1 or 5.0.2 something like that? I just want to make sure I can follow it exactly so it works.
Root access was lost after a couple of days. I'm on 4.4.4.
cqdiep said:
Yeah, I'm doing that too.
Click to expand...
Click to collapse
Well this is strange, I followed this exact tutorial about 1 month ago and everything worked fine, now the app just freezes and after 5 minutes gives off a "Root Fail" message. I'm still running v4.8.1 on the app and still running on the KitKat firmware. This makes no sense at all.
Edit: The phone is no longer supported by Kingroot
Hey guys, sorry for not replying, my internet has been down for the past two weeks . It seems that everyone is having problems keeping root after a while. I might not be a developer, but here's my advice: Once root is obtained, do what you want to do (ie. change emojis or install ViperAudio), then don't touch the SuperSU app until some more skilled developers put this root to full use . I'm sorry for not being more useful, but I just want everyone to know that this device isn't dead. What we need right now is something like SafeStrap for some some-what custom roms.
Any one having issue getting this to work?
PopTartKing said:
Hey guys, sorry for not replying, my internet has been down for the past two weeks . It seems that everyone is having problems keeping root after a while. I might not be a developer, but here's my advice: Once root is obtained, do what you want to do (ie. change emojis or install ViperAudio), then don't touch the SuperSU app until some more skilled developers put this root to full use . I'm sorry for not being more useful, but I just want everyone to know that this device isn't dead. What we need right now is something like SafeStrap for some some-what custom roms.
Click to expand...
Click to collapse
Yeah, Kingroot pulled support from it after people started using supersu-me to get supersu on their devices instead of kingroot. Well, to me, it sounds like a jealousy problem on Kingroots end. It's not like everyone is buying the pro version of the app. Their main source of money is ad revenue. They also pulled support from the Galaxy S5 and many other devices mainly because of people using supersu-me. Kingroot has got to get the stick that is in it's butt right now out ASAP. A 'friend' of mine literally sold his S5 because it couldn't be rooted anymore, and i'm thinking about selling my G850A because it can't be rooted anymore.
Just to clarify this, there's absolutely no way on the internet that the G850A can be rooted, ever?
chocolatewings said:
Just to clarify this, there's absolutely no way on the internet that the G850A can be rooted, ever?
Click to expand...
Click to collapse
Not anymore. It only had root for like 1 month then Kingroot removed support, you can blame them. Unless someone is exploit something so we can have root back, there is no way to root this phone anymore. I know, it sucks, just like the Kingroot developers, but that's just life.
cqdiep said:
Root access was lost after a couple of days. I'm on 4.4.4.
Click to expand...
Click to collapse
Hi
Im doing that and 100% complete but i check root by root check not request from super user
Solution found!
Hi guys. I think I found the trick. Just disable Internet connection (Mobile data and WiFi) just before lunching kingroot app this would evade the app from "searching the best root solution" which is "nothing found".
I used the exact same files uploaded in the OP and it works great, including the supersume part.
Good luck.
I'm very lucky to root my device. waited One year and 4 months and got the fruit of patience. Now I love my device. I have patched Tethering Provision. Now I can easily open hotspot.. no need of foxfi etc... ? Congratulations to those who got there device ROOOOTED.. ?
babarjoya said:
I'm very lucky to root my device. waited One year and 4 months and got the fruit of patience. Now I love my device. I have patched Tethering Provision. Now I can easily open hotspot.. no need of foxfi etc... Congratulations to those who got there device ROOOOTED..
Click to expand...
Click to collapse
Salam. Babar bhai hamen bhi bata den k kaise root kar lia ap ne. please
Hi guys, my questions would refer to root privileges with regard to OTA software update...
But firstly...
Do you think that KingoRoot apk constitutes a reliable root service? Do you think one can root his/her device just by installing the app via browser in the phone and launching the root process?
And now the initial question:
Do you think that OTA software update can remove root from the device? Or, does the fact that one can perform OTA software update indicate that there is acutally no root on the phone?
(Device: Samsung Galaxy J5 2016)
Thanks!
Yannikk said:
Hi guys, my questions would refer to root privileges with regard to OTA software update...
But firstly...
Do you think that KingoRoot apk constitutes a reliable root service? Do you think one can root his/her device just by installing the app via browser in the phone and launching the root process?
Click to expand...
Click to collapse
Generally no - Android functions such as Verified Boot and dm-verity are supposed to prevent persistent rootkits, unless the bootloader is unlocked. Yes, there are some exploits, but usually these only provide temporary root.
As a general rule I advise against using closed source software, simply because you don't know if there's anything malicious going on under the hood. A safe alternative is Magisk, although this does not utilize any exploits, so you would have to unlock your bootloader and root the "right" way.
Yannikk said:
And now the initial question:
Do you think that OTA software update can remove root from the device?
Click to expand...
Click to collapse
Yes - in most cases, a OTA update overwrites several partitions on the device, including /boot and /system. This means that after rebooting from an OTA update, root would no longer be available. The workaround for this is the "Patch to inactive slot" function in Magisk on A/B devices - once the update is complete and the device is ready for a reboot, Magisk uses root privileges to patch the new boot image, so that root persists after reboot.
For A only devices such as Samsung, it's a bit more tricky...you'd need to flash a custom recovery after the update and flash Magisk from there.
Yannikk said:
Or, does the fact that one can perform OTA software update indicate that there is acutally no root on the phone?
Click to expand...
Click to collapse
Not always. In most cases, update_engine conducts various checks to determine whether critical partitons such as /system and /boot are intact and untampered; if they are, the update will fail. This is why Magisk has the "Restore images" function for systemless root - Magisk restores the unpatched boot image written to flash, so that the device may pass these checks. It doesn't always work, and on the opposite end of things, there are some devices that will happily install an OTA update even with modified binaries present on the device.
Thanks for you answer, V0latyle.
Now, I would present a broader picture of an issue that gains my attention...
It happend some time ago, on an older device (Galaxy J5 2016, as mentioned)...
I installed KingoRoot apk (directly via browser in the phone) and launched rooting process... The app signalized that the rooting process has been successful... I did not install any custom ROMs or apps... The phone functioned pretty normally then... However, after few months, out of the blue, my device started behaving strangely... Videos on YT took a great amount of time to load or they lagged after some time... Newsfeed on IG did not work, nor instastories... Browsers were also considerably slower... Approx. 2 months later, when Nougat 7.1.1 came out and after I downloaded this software update (OTA), the phone got somehow faster - YT videos loaded faster or did not lag, IG newsfeed got updated regularly, browsers were not so slow either... On the other hand, yes, some apps still behaved in an unusual way...
Do you have any idea what might have happened in this case?
Thank you very much for any suggestions!