Related
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Chimpdaddy said:
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Click to expand...
Click to collapse
you can try ot yourself,.but i reckon it will give you error while applying update.
Rootk1t said:
you can try ot yourself,.but i reckon it will give you error while applying update.
Click to expand...
Click to collapse
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Chimpdaddy said:
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Click to expand...
Click to collapse
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
bjrmd said:
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
Click to expand...
Click to collapse
I know, so lazy, if I wait long enough 4.4 will come around and that might keep root!
Nobody's read a successful account of this working then? I may as well just try it and see...
Possibly
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed.
I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root.
If you have CWM or TWRP installed then it won't let you update.
adielee said:
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed. I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root. If you have CWM or TWRP installed then it won't let you update.
Click to expand...
Click to collapse
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Cat McGowan said:
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Click to expand...
Click to collapse
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Rootk1t said:
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Click to expand...
Click to collapse
I would also recommend to flash a pre-rooted 4.3 from scratch for performance and less issues, but if you have a lot of apps installed and everything set up the way you want it can be a pain in the a$#.
Also the OP doesn't want to flash. But if he can it means that the OTA won't install because he has a custom recovery.
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2)
It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
adielee said:
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2) It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
Click to expand...
Click to collapse
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Nope
Cat McGowan said:
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Click to expand...
Click to collapse
Well, I tried it, thinking the worse that could happen is that it would abandon the install, but unfortunately it went right through and upgraded to 4.3 and I lost root
I'd put it into OTA survival mode but not into system/apps. I had no xposed or recovery anything, just root.
So there we go. Thanks for the discussion guys, hope this is useful to someone else.
How do I root it in 4.3? Any ideas?
Try this
http://forum.xda-developers.com/showthread.php?t=2703774
Sent from my SGP311 using xda app-developers app
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
there are a lots of guide but everyone say a different method. OK I AM A NOOB OF MODDING.
but is quite difficult to understand guides that are different in this way:
1) some indicates to just use an apk autorooting the device
2) some do require to change thekernel + manually install the superuser apk
3)not permanent root....
4) others......
so, please be patient......:angel: i only want to find a "normal" root method.......and IF POSSIBLE a root that could allow me to easily UNroot the device to be able to update my firmware OTA in the moment samsung will update our great device to kitkat
If you are a noob at modding don't even bother with rooting. Its dangerous and BTW I think your firmware has KNOX which the GMega doesn't have a workaround.
Sent from my GT-I9200 using Tapatalk
realista87 said:
hi, i have a simple question, is it possible to root my device? i've never root my mega 6.3 since i bought it...... but i heard that the recent firmware have some problems in the possibility of rooting it.
Click to expand...
Click to collapse
If you are brave enough you can try it using this tutorial
http://forum.xda-developers.com/showthread.php?t=2574953
But read it thoroughly and if you do not understand one thing though - do not attempt to try.
Read forums and learn till you can understand what you are doing lest you have quite expensive paperweight... I am not responsible for what you do with your phone!
my previous phone was rooter, the optimus 3d and the ascend mate.
i don't need toor for extreme modding but just to install a custom recovery for a nandroid backup and for use SOME APP THAT REQUIRE root to work properly.
i never installed a recovery but i read everywhere that it is a lot usefull in case of some errors, to restore the previous backup made 1:1 (nandroid)
Every modding attempt must start from root and (optionally) custom recovery. In fact - rooting itself is modding and quite heavy from system point of view. If you want to change ONE THING in system, you have to root your phone. Doing this you are tripping 'warranty flag' and from now on your warranty is void.
If you have firmware with KNOX and new bootloader - tripping this flag is irreversible. But as long as you do not attempt to flash older firmware (before KNOX) it does not affect the operation of the system. Trying to flash older firmware makes your phone softbrick because of tripping security mechanism in new bootloader.
If you already rooted your phone it is resonable to flash custom recovery and by this have wide possiblity making backups of your whole system (nandroid backup) or flashing custom ROMs
It may have been put clearly somewhere else but I can't seem to locate it. Apologies if I am asking an answered question.
If I root this phone (don't intend to unlock bootloader), however:
Will OTA stop working? (because of modification)
Will doing an OTA update on rooted phone remove root?
If so, is it possible to preserve root while doing an OTA?
Will removing all traces of root be as easy as SU uninstall?
With some phones, the OTA will be broken after rooting and some it will not. This is my first Sony and I wanted to confirm if this was also the case.
jcspecs said:
It may have been put clearly somewhere else but I can't seem to locate it. Apologies if I am asking an answered question.
If I root this phone (don't intend to unlock bootloader), however:
Will OTA stop working? (because of modification)
Will doing an OTA update on rooted phone remove root?
If so, is it possible to preserve root while doing an OTA?
Will removing all traces of root be as easy as SU uninstall?
With some phones, the OTA will be broken after rooting and some it will not. This is my first Sony and I wanted to confirm if this was also the case.
Click to expand...
Click to collapse
Will OTA stop working? (because of modification) No, it would not stop working if you just root
Will doing an OTA update on rooted phone remove root? It may or may not. Nobody has tried it yet. But normally we dont recommend doing OTA after rooting
If so, is it possible to preserve root while doing an OTA? No way till now.
Will removing all traces of root be as easy as SU uninstall? Yes, there is an option in SU to unroot the phone.
manu44 said:
Will OTA stop working? (because of modification) No, it would not stop working if you just root
Will doing an OTA update on rooted phone remove root? It may or may not. Nobody has tried it yet. But normally we dont recommend doing OTA after rooting
If so, is it possible to preserve root while doing an OTA? No way till now.
Will removing all traces of root be as easy as SU uninstall? Yes, there is an option in SU to unroot the phone.
Click to expand...
Click to collapse
Hello,
Thanks so much for your clear and concise responses. Previously I've never been concerned about the unrooting of a phone or access to OTA. I just got so comfortable working with Samsung that I feel a bit out of my depth at the moment with the Z2.
jcspecs said:
It may have been put clearly somewhere else but I can't seem to locate it. Apologies if I am asking an answered question.
If I root this phone (don't intend to unlock bootloader), however:
Will OTA stop working? (because of modification)
Will doing an OTA update on rooted phone remove root?
If so, is it possible to preserve root while doing an OTA?
Will removing all traces of root be as easy as SU uninstall?
With some phones, the OTA will be broken after rooting and some it will not. This is my first Sony and I wanted to confirm if this was also the case.
Click to expand...
Click to collapse
On my phone OTA won't work on rooted device. Firmware downloads fine but it fails verification when trying to install.
jcspecs said:
Hello,
Thanks so much for your clear and concise responses. Previously I've never been concerned about the unrooting of a phone or access to OTA. I just got so comfortable working with Samsung that I feel a bit out of my depth at the moment with the Z2.
Click to expand...
Click to collapse
I can understand, I am also coming from SamsungS4. this is my first sony phone.But trust me sony has lot less hassles compared to Samsung Knox Bull****
kamalaggi said:
On my phone OTA won't work on rooted device. Firmware downloads fine but it fails verification when trying to install.
Click to expand...
Click to collapse
Interesting. Could it be something that varies across providers?
manu44 said:
I can understand, I am also coming from SamsungS4. this is my first sony phone.But trust me sony has lot less hassles compared to Samsung Knox Bull****
Click to expand...
Click to collapse
Yes. Happy to have avoided Knox.
manu44 said:
Will OTA stop working? (because of modification) No, it would not stop working if you just root
Will doing an OTA update on rooted phone remove root? It may or may not. Nobody has tried it yet. But normally we dont recommend doing OTA after rooting
If so, is it possible to preserve root while doing an OTA? No way till now.
Will removing all traces of root be as easy as SU uninstall? Yes, there is an option in SU to unroot the phone.
Click to expand...
Click to collapse
So, we can just click unroot in supersu, not have to flash FTF using FlashTool ? After this method of unroot can we safely do ota ?
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.
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!