Will it cause any problem if I grant permission through ADB shell? Will I get OTA updates? And if so, will flashing OTA update cause any problem?
Device : Redmi 6 PRO
Running OS : MIUI 10 (Android OREO 8.1)
3xp1r3d50ul said:
Will it cause any problem if I grant permission through ADB shell? Will I get OTA updates? And if so, will flashing OTA update cause any problem?
Device : Redmi 6 PRO
Running OS : MIUI 10 (Android OREO 8.1)
Click to expand...
Click to collapse
If your device is rooted, you can't use OTA update. OTA update requires having stock recovery and an unmodified system partition, meaning, no root, no Xposed, nothing of any kind that modifies your system partition in any way other than what it is supposed to have.
Applying OTA updates on a rooted device causes the device to be softbricked(or hardbricked in some cases), then the device has to be recovered and reflashed with your stock firmware to repair the device.
Sent from my LGL84VL using Tapatalk
Related
I rooted my Nexus 6P when I purchased however a few months ago, something happened which kind of messed up my root. I can't remember now exactly what it was (maybe I updated OTA) however when I run Root checker, I get the message "Sorry! Root access is not properly installed on this device". Also Titanium Backup complains about my device not being properly rooted.
The strange thing is, my banking apps complain that my device is rooted and don't give me the full functionality
Also, my phone always downloads monthly updates, but I haven't been able to install since around June. It has now downloaded Android 7.1.1 and after trying to install this morning, it just booted into TWRP.
I'm after 2 things..
to have a properly rooted phone again
to have Android 7.1.1 installed
What's the best way for me to achieve this? What's actually happened to my phone? I would like to achieve the above 2 things with zero data loss if possible
5aq1b said:
I rooted my Nexus 6P when I purchased however a few months ago, something happened which kind of messed up my root. I can't remember now exactly what it was (maybe I updated OTA) however when I run Root checker, I get the message "Sorry! Root access is not properly installed on this device". Also Titanium Backup complains about my device not being properly rooted.
The strange thing is, my banking apps complain that my device is rooted and don't give me the full functionality
Also, my phone always downloads monthly updates, but I haven't been able to install since around June. It has now downloaded Android 7.1.1 and after trying to install this morning, it just booted into TWRP.
I'm after 2 things..
to have a properly rooted phone again
to have Android 7.1.1 installed
What's the best way for me to achieve this? What's actually happened to my phone? I would like to achieve the above 2 things with zero data loss if possible
Click to expand...
Click to collapse
If you are talking about stock OTA updates, that doesn't work on rooted devices.
To do stock OTA updates you need to remove root, you need stock recovery instead of custom recovery and you need to have an unmodified system partition.
Flash your stock firmware then update then root again after all updates are installed.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
If you are talking about stock OTA updates, that doesn't work on rooted devices.
To do stock OTA updates you need to remove root, you need stock recovery instead of custom recovery and you need to have an unmodified system partition.
Flash your stock firmware then update then root again after all updates are installed.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ok thanks for the reply...
So if I don't want to do the stock update, then how do i fix my root first of all?
After I fix my root - Can i perform an update to 7.1.1 via a non-stock method? ie. download the update somehow and flash via ADB or install via TWRP?
5aq1b said:
Ok thanks for the reply...
So if I don't want to do the stock update, then how do i fix my root first of all?
After I fix my root - Can i perform an update to 7.1.1 via a non-stock method? ie. download the update somehow and flash via ADB or install via TWRP?
Click to expand...
Click to collapse
As I said, flash your original stock firmware, then apply any stock updates that you want and THEN root. The 7.1.1 OTA is a stock update.
YOU CAN'T APPLY STOCK UPDATES WHILE YOU ARE ROOTED AND YOU CAN'T DO STOCK UPDATES IN CUSTOM RECOVERY.
Or you can flash stock firmware to fix the device, then install root and custom recovery again and then if you want to flash a CUSTOM 7.1.1 you flash it in recovery but you can't apply the stock 7.1.1.
Sent from my SCH-I535 using Tapatalk
Thanks... And in both cases, i shouldn't lose my data because my bootloader is unlocked already from when i originally rooted... Is that correct?
Sent from my Nexus 6P using Tapatalk
Droidriven said:
As I said, flash your original stock firmware, then apply any stock updates that you want and THEN root. The 7.1.1 OTA is a stock update.
YOU CAN'T APPLY STOCK UPDATES WHILE YOU ARE ROOTED AND YOU CAN'T DO STOCK UPDATES IN CUSTOM RECOVERY.
Or you can flash stock firmware to fix the device, then install root and custom recovery again and then if you want to flash a CUSTOM 7.1.1 you flash it in recovery but you can't apply the stock 7.1.1.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks... And in both cases, i shouldn't lose my data because my bootloader is unlocked already from when i originally rooted... Is that correct?
Sent from my Nexus 6P using Tapatalk
5aq1b said:
Thanks... And in both cases, i shouldn't lose my data because my bootloader is unlocked already from when i originally rooted... Is that correct?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm not sure about that. Flashing something that upgrades or downgrades bootloader usually wipes data.
Sent from my SCH-I535 using Tapatalk
Hello,
So my Oneplus 6 was rooted on Android 8.1 for a while now. Recently i got the update for Android 9 and did the official OTA Update to 9. Now my root seems gone or at least it doesn't work anymore.
Now I actually want to remove the root completly because I want to use my banking app, which won't work on rooted phones.
How do I remove the leftovers of this root? I had Magisk + TWRP on it. TWRP shouldn't affect any apps right? Would it be enough to just relock the bootloader? Cause root seems gone already there is no need to uninstall it right?
Thank you for your help.
-Elekted
you need to flash boot.img and system.img from the start. You can dump them from the OTA you have installed.
Elekted said:
Hello,
So my Oneplus 6 was rooted on Android 8.1 for a while now. Recently i got the update for Android 9 and did the official OTA Update to 9. Now my root seems gone or at least it doesn't work anymore.
Now I actually want to remove the root completly because I want to use my banking app, which won't work on rooted phones.
How do I remove the leftovers of this root? I had Magisk + TWRP on it. TWRP shouldn't affect any apps right? Would it be enough to just relock the bootloader? Cause root seems gone already there is no need to uninstall it right?
Thank you for your help.
-Elekted
Click to expand...
Click to collapse
Just flash full ROM zip file in TWRP. Data will stay in tact, stock boot img and stock recovery.
Hello,
my oneplus 7 is rooted with magisk and has TWRP as custom recovery installed.
With the release of Android 10 closing in, would I be able to update to the new Android via the normal update process, or do I have to do something else in order to get that?
zloboh said:
Hello,
my oneplus 7 is rooted with magisk and has TWRP as custom recovery installed.
With the release of Android 10 closing in, would I be able to update to the new Android via the normal update process, or do I have to do something else in order to get that?
Click to expand...
Click to collapse
Yes, local update, data will be not erased, but make backups: https://forum.xda-developers.com/on...7-repo-oxygen-os-builds-t3937152/post80177128
But this is only for non rooted phones with locked bootloader, but sure if the current twrp will work.
zloboh said:
Hello,
my oneplus 7 is rooted with magisk and has TWRP as custom recovery installed.
With the release of Android 10 closing in, would I be able to update to the new Android via the normal update process, or do I have to do something else in order to get that?
Click to expand...
Click to collapse
Yes it's possible. Follow my guide to get TWRP to work also.
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
BlobTea said:
Hey all
So a while back I wanted to use a certain app on my Motorola One Hyper that required root privileges, so I rooted my phone using Magisk for it. I didn't need the app later so I unrooted my phone, but now when I try to update my phone to a newer version, I get an error message saying "Package verification failed. The update package being downloaded is not compatible with the current software version on the device".
I'm not sure if me rooting the device has anything to do with it or not, but I'm guessing it is since I never had this issue before the root. Any way to fix this? Thanks in advance!
Click to expand...
Click to collapse
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
RVR said:
Yes, it probably is the root.
If you are trying to update the stock rom, it probably will not work. You may have to manually flash the stock rom again. Then, you may be able to upgrade to android 11. Otherwise you can just manually install android 11.
Click to expand...
Click to collapse
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Does having a SafetyNet fix have something to do with it? Maybe unrelated, maybe not but when I check off the software update on the Magisk DenyList, exit and then come back, it becomes unchecked and I don't know why. Perhaps if the OTA updates werent detecting root, I could update to a security patch.
BlobTea said:
Ahh gotcha. Looks like I'm gonna have to flash the stock rom then. Thanks a lot for your help!
Click to expand...
Click to collapse
Stock updates usually can't be applied to rooted devices or devices with custom recovery, root has to be completely removed and stock recovery has to be reinstalled. If those aren't corrected before applying the update, it will fail because it checks the system partition for modifications and requires stock recovery to apply the update, whether it actually boots into recovery or not during the update process.
I recently installed Resurrection Remix 5.8.5 Custom Rom by @SaberShip based on Android 7.1.2 which came with root access enabled and supersu installed by default. So I tried to unroot by flashing unsu.zip by @osm0sis through twrp recovery. After that I checked using Root Beer Sample app but my device was still showing up as rooted. It fails the dangerous build.prop and selinux flag tests. I need to unroot for using an education app which doesn't run on rooted devices.
To check whether Android is rooted or not people do it themselves via ADB
Code:
adb devices
adb shell "which 'su'"
If a path containg "su" is returned, Android is rooted, otherwise it's not.
To get rid off of root simply re-flash device's Stock ROM.
xXx yYy said:
To check whether Android is rooted or not people do it themselves via ADB
Code:
adb devices
adb shell "which 'su'"
If a path containg "su" is returned, Android is rooted, otherwise it's not.
To get rid off of root simply re-flash device's Stock ROM.
Click to expand...
Click to collapse
It didn't return with anything. The stock rom is Android 4.4 based and the app which I need to run needs android 7 atleast. That's why I flashed a custom rom based on Android 7, unfortunately which came with root enabled. Now I can't get rid of it completely and the app which I need to run says my device is still rooted.