Related
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
sray1 said:
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
Click to expand...
Click to collapse
In order to root, you have to unlock the bootloader using the nexus toolkit which unfortunately wipes the device. then you can root it
Yes you can go completely back to stock and relock the bootloader
No, you cant get updates without losing root. so basically you update and then reroot, it takes 5 seconds.
The play store works perfectly fine on rooted devices
jombo2323 said:
No, you cant get updates without losing root. so basically you update and then reroot, it takes 5 seconds.
Click to expand...
Click to collapse
So I would get the same OTA update notice and just lose root by telling it to ahead?
However, the bootloader would remain unlocked so the reroot would not require a wipe. Also installing CWM recover would not interfere with any of that.
Is that all correct?
sray1 said:
So I would get the same OTA update notice and just lose root by telling it to ahead?
However, the bootloader would remain unlocked so the reroot would not require a wipe. Also installing CWM recover would not interfere with any of that.
Is that all correct?
Click to expand...
Click to collapse
i cant remember if cwm interferes or not. if your just stock then dont worry about it.
yes, it does not require a wipe, just a re root.
Another thing. I haven't done anything about the $25 google credit. Does doing the wipe effect that?
Installing a custom recovery WILL prevent you from receiving OTA updates. The $25 credit is applied to your account and isn't affected by anything you do with your tablet afterward.
sray1 said:
So I would get the same OTA update notice and just lose root by telling it to ahead?
However, the bootloader would remain unlocked so the reroot would not require a wipe. Also installing CWM recover would not interfere with any of that.
Is that all correct?
Click to expand...
Click to collapse
There are some apps out that may retain root. OTA RootKeeper in the play store has one Nexus 7 reviewer that claims he retained root from 4.1.0 to 4.1.1
But you are correct, even if you lose root reflashing is a trivial matter.
WugFresh has a toolkit that can do all this for you, including unlocking/rooting but NOT permanently installing CWM if you so desire.
Or, if you prefer a hands-on and more educational approach take a look at my guide here: http://forum.xda-developers.com/showthread.php?t=1816048
jombo2323 said:
In order to root, you have to unlock the bootloader using the nexus toolkit which unfortunately wipes the device. then you can root it
Yes you can go completely back to stock and relock the bootloader
No, you cant get updates without losing root. so basically you update and then reroot, it takes 5 seconds.
The play store works perfectly fine on rooted devices
Click to expand...
Click to collapse
you do not have to use any toolkit. as a fact, toolkits take longer to root the device. this is a nexus device, toolkits are discouraged. all you need to do is fastboot oem unlock, flash your custom recovery via fastboot, then either flash su binaries or your custom rom in recovery, and reboot. that is all. and yes, unlocking your bootloader will wipe the device. thats why its best to do it before you get to comfortable on it.
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
gosku26 said:
I have a rooted (no CWM changed) and unlocked Nexus 4 with JB 4.3.
I did not get the OTA yet and I wondered if it is because the phone is rooted. In addition, I read some problems with people who tried to update to 4.4 with rooted phones and are getting infinite bootloops.
Do I have to unroot my 4.3 for getting the OTA and achieving a successful installation?
Thank you all on advance
Click to expand...
Click to collapse
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
gbarayah said:
I am rooted and received the OTA notification yesterday. You 'SHOULD' be able to install if ALL you did was root. However, if you applied any mods that made changes to the system, the OTA will fail.
This is your best bet if you want to run 4.4. You'll need to install a custom recovery to flash the zip files. All the files and instructions are here:
http://forum.xda-developers.com/showthread.php?t=2527806
Click to expand...
Click to collapse
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
gosku26 said:
Will flashing the stock 4.4 wipe my data, or it is like getting the OTA, that I keep my settings...?
Click to expand...
Click to collapse
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
taodan said:
Why do you need OTA update when you can get the stock ROM in flashable zip file? All features are remain the same for stock ROM. Search and download it in the Development sections.
Click to expand...
Click to collapse
I would like to keep my settings if it's possible.
gbarayah said:
Did you read the linked post?
First step after installing custom recovery is to wipe data/factory reset, so yes, you will lose your settings.
Click to expand...
Click to collapse
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
gosku26 said:
What I would like is to update to kitkat without losing my data.
I have the bootloader unlocked and the phone rooted, but when I go to recovery mode I get "No command" screen (is that normal?).
I was thinking of getting the phone unrooted, then update through the OTA, then root it again, just for making sure I don't break anything, but the "No command" screen does not look very good...
On the other hand, Would I lose my data if I "unroot" the phone?
Click to expand...
Click to collapse
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
gbarayah said:
To unroot, all you need to do is go into SuperSu, disable root, uninstall the app and then reboot the phone.
If all you have done is root the phone, and didn't modify anything else, then the OTA update 'SHOULD' install without a problem.
You can go to Android Police and download the OTA files and flash them via ADB, or you can just wait for the OTA to be pushed to your device.
If you decide to do it the manual way, there is one additional step you must take to ensure to keep your data I believe.
Click to expand...
Click to collapse
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
gosku26 said:
Thank you for your help gbarayah, I really appreciate it.
One last thing: I'm not pretty sure the only thing I modified was the rooting. I did not install any zip to modify my stock version, but there is something weird. I will explain:
At first I had 4.2.2, then I rooted and installed CWM. When 4.3 was released I got the OTA update correctly but I lost the root, so I rooted it again, this time without CWM.
Is the "No command" screen what is supposed to appear when I go to the recovery mode from fastboot menu? Or I would get a default recovery mode program?
If everything is right I will unroot for getting the OTA, but if not, I'm afraid I will have to flash CWM and the stock version, loosing my settings...
EDIT: Ok, I've just realized to get into stock system recovery I have to press VolUp and Power buttons once I'm in the 'No Command' screen, so I'm pretty sure I don't have problems installing the OTA update. Thank You!!!
Click to expand...
Click to collapse
Glad I could help. In the future, as long as you don't modify the system by flashing any modifications, you should be able to get the OTA update to install. Root doesn't affect this, and if you're worried about it, you can always uninstall it.
I opted to update using the stock zip files that were posted above and it worked just fine for me.
I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
KishanW said:
Maybe user Titanium Backup or some kinda backup software to backup files and stuff then just go for a fresh installation? Most of the basic settings should be saved to your google account.
This post should help you with setting up ADB in your computer and to get you up to speed with using ADB and Fastbooot
Click to expand...
Click to collapse
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
605
tommyhj said:
Thanks for the quick reply! But i was hoping for a solution that DIDN'T wipe my phone. I just wanna undo all the rooting business, so i can do the OTA...
Click to expand...
Click to collapse
That would be interesting if someone has an answer for your question. I can use it too
Sorry that I couldn't help you.
tommyhj said:
I want Lollipop and my Nexus 4 won't shut up about the OTA update. Naturally, it failed, and i have since tried to find a fool-proof guide to uptade it WITHOUT LOOSING DATA. Not been so lucky. Theres talk about fastbooting (?) and going back to stock, but not much in the way of step-by-step guides. I think most people with nexus 4 and root are like me - did it because it was easy, not knowing a lot about it...
I have rooted with towelroot, installed TWRP custom recovery with flashify, unlocked bootlocker with Bootunlock, installed Xposed framework and SuperSU. Never used ADB or any commands. Can't be the only one in this exact situation
What excactly do i need to do to get Lollipop without loosing any data (like a regular OTA update)?
Click to expand...
Click to collapse
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
gardn227 said:
Hey,
Follow these instructions http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312.
there are a few things to note:
1. You do not need to unlock the bootloader, you will have done that when you rooted
2. Download the 5.0 image instead of the original stock image when you do this.
3. DO NOT flash userdata.img. That will wipe your data.
Those are the steps I followed to flash over to 5.0 without losing data.
But I would absolutely do a backup anyway, just in case something goes wrong.
Click to expand...
Click to collapse
Ok, cool. So you're saying to towel-root my device, unlock bootloader with bootunlocker app, remove root by installing SuperSU and using the clean-up funtion. And then adb fastboot flash boot/recovery/system from the FACTORY img? Why not sideload the OTA instead? Because it wont work unless i reflash stock 4.4.4 completely?
Just got my phone and I need to wait on rooting. Can I take the January OTA updates and still root later?
Yes. If you plan to root later, unlock the bootloader first before you set everything up. Unlocking the bootloader will force a wipe of all data. Rooting will not, if the bootloader is already unlocked.
fury683 said:
Yes. If you plan to root later, unlock the bootloader first before you set everything up. Unlocking the bootloader will force a wipe of all data. Rooting will not, if the bootloader is already unlocked.
Click to expand...
Click to collapse
If I'm reading this right, I need to unlock the bootloader just to get root? Does that also mean it would take a data wipe to un-root?
blindguyinanorgy said:
If I'm reading this right, I need to unlock the bootloader just to get root? Does that also mean it would take a data wipe to un-root?
Click to expand...
Click to collapse
Unlocking does not provide root access, but it is a requirement for gaining root. If you wait to unlock your bootloader and set all your apps and settings on your phone, it will all be lost when you decide to root because the bootloader must be unlocked to root.
Therefore it is best to unlock first if you have the intention of rooting later to save your data and settings.
blindguyinanorgy said:
Just got my phone and I need to wait on rooting. Can I take the January OTA updates and still root later?
Click to expand...
Click to collapse
blindguyinanorgy said:
If I'm reading this right, I need to unlock the bootloader just to get root? Does that also mean it would take a data wipe to un-root?
Click to expand...
Click to collapse
To get root access you need to install SuperSU, to install SuperSU you need TWRP recovery, to install TWRP recovery you need an unlocked bootloader. Unlocking the bootloader wipes all userdata from the device. The best way to do it is like this:
1. Unlock your bootloader.
2. Flash the factory images for the latest build to make sure you're completely up to date.
3. Install TWRP.
4. Make a nandroid backup with TWRP.
5. Install SuperSU to get root.
6. Install whatever root mods/apps you want.
Read my detailed guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
I see thank you. This is different from any other phone I've been on where root is found before unlock, if unlock is ever found
blindguyinanorgy said:
I see thank you. This is different from any other phone I've been on where root is found before unlock, if unlock is ever found
Click to expand...
Click to collapse
That's the beauty of owning a Nexus, they're meant to be tinkered with so it's all very easy. No hacks or exploits required.
Banking apps can be not running when they think the phone is not safe even the phone is “not” rooted .
And factory reset or OTA update after rooting can make root access botched. Just like unrooting phone. So root checker apps can’t detect rooting after factory reset.
Then can i tell whether my phone has ever been rooted before factory reset without checking knox?
(Cuz broken knox doesnt necessarily mean rooting.)
My phone is reset . Root checking apps say its not rooted. But banking apps dont work.
Is thery any way to check..?
Jenjenjney said:
Banking apps can be not running when they think the phone is not safe even the phone is “not” rooted .
And factory reset or OTA update after rooting can make root access botched. Just like unrooting phone. So root checker apps can’t detect rooting after factory reset.
Then can i tell whether my phone has ever been rooted before factory reset without checking knox?
(Cuz broken knox doesnt necessarily mean rooting.)
My phone is reset . Root checking apps say its not rooted. But banking apps dont work.
Is thery any way to check..?
Click to expand...
Click to collapse
know triggered pretty much means custom recovery, custom rom, or root, and they can all break banking apps. Did you buy the device used?
You might find better support in the specific forum for your device. What is the make and model of the device in question? Additionally, which banking apps aren't working?
Outside of Knox, there's not really any way to tell if a device has been rooted, if it is currently on OEM firmware with a locked bootloader. If the bootloader is unlocked, it most likely has been rooted at some point., but none of that should matter if the device is restored to factory state with OEM firmware and a locked bootloader.
V0latyle said:
You might find better support in the specific forum for your device. What is the make and model of the device in question? Additionally, which banking apps aren't working?
Outside of Knox, there's not really any way to tell if a device has been rooted, if it is currently on OEM firmware with a locked bootloader. If the bootloader is unlocked, it most likely has been rooted at some point., but none of that should matter if the device is restored to factory state with OEM firmware and a locked bootloader.
Click to expand...
Click to collapse
My phone is galaxy note4 910k and samsung phone’s bootloader is already unlocked in korea.
Jenjenjney said:
My phone is galaxy note4 910k and samsung phone’s bootloader is already unlocked in korea.
Click to expand...
Click to collapse
I mean whether it is currently unlocked now, not whether it is unlockable.
If your bootloader is unlocked, your device will fail Play Integrity, and banking apps may not work.
V0latyle said:
I mean whether it is currently unlocked now, not whether it is unlockable.
If your bootloader is unlocked, your device will fail Play Integrity, and banking apps may not work.
Click to expand...
Click to collapse
Samsung phones in korea dont have bootloader locked. They are sold with bootloader unlocked in the first place.
Thats default. So i dont need to unlock it to root or install ROM.,,
Jenjenjney said:
Samsung phones in korea dont have bootloader locked. They are sold with bootloader unlocked in the first place.
Thats default. So i dont need to unlock it to root or install ROM.,,
Click to expand...
Click to collapse
Ah. Well, you have two choices:
Lock your bootloader (only do this if your firmware is completely stock)
Root using Magisk and read this thread, and use the linked module
An unlocked bootloader will result in the device failing integrity attestation, which DRM and banking apps rely on. The only way to fix this is to either use a Magisk module for a partial workaround, or to relock the bootloader.
V0latyle said:
Ah. Well, you have two choices:
Lock your bootloader (only do this if your firmware is completely stock)
Root using Magisk and read this thread, and use the linked module
An unlocked bootloader will result in the device failing integrity attestation, which DRM and banking apps rely on. The only way to fix this is to either use a Magisk module for a partial workaround, or to relock the bootloader.
Click to expand...
Click to collapse
Thanks but i wonder
Is there way to check if my phone was rooted before factory reset…?
I mean reset is not like installing stock rom, so even if files related to rooting are gone after factory reset, i think there are some traces to check,,,
Please…?
I ve never thought factory reset can wipe rooting trace like installing stock rom
Jenjenjney said:
Thanks but i wonder
Is there way to check if my phone was rooted before factory reset…?
I mean reset is not like installing stock rom, so even if files related to rooting are gone after factory reset, i think there are some traces to check,,,
Please…?
Click to expand...
Click to collapse
No - you can reflash factory firmware using Odin, but there's not really any easy way to tell if your device was previously modified.
Jenjenjney said:
I ve never thought factory reset can wipe rooting trace like installing stock rom
Click to expand...
Click to collapse
Factory reset just wipes /data and does not remove the SU binary. In my case, with my Magisk rooted Pixel 5, I could perform a factory reset...but because the boot image is patched, my device would still be rooted, unless I selected "Complete Uninstall" in Magisk. Factory reset and clean flashing factory firmware are not the same thing.
If you don't know what state your device was in previously, the only thing you can really do is perform a reflash of the factory firmware using Odin. This overwrites all partitions including /boot, /recovery, and /system.
Again, even after a complete clean flash, your device will still fail Play Integrity until you lock the bootloader, meaning that banking/DRM apps may not work.
Jenjenjney said:
Thanks but i wonder
Is there way to check if my phone was rooted before factory reset…?
I mean reset is not like installing stock rom, so even if files related to rooting are gone after factory reset, i think there are some traces to check,,,
Please…?
I ve never thought factory reset can wipe rooting trace like installing stock rom
Click to expand...
Click to collapse
no,no way to check if was rooted, samsung device to check own security uses knox, is tripped means device has been modded but not in a specific way like rooting
V0latyle said:
No - you can reflash factory firmware using Odin, but there's not really any easy way to tell if your device was previously modified.
Factory reset just wipes /data and does not remove the SU binary. In my case, with my Magisk rooted Pixel 5, I could perform a factory reset...but because the boot image is patched, my device would still be rooted, unless I selected "Complete Uninstall" in Magisk. Factory reset and clean flashing factory firmware are not the same thing.
If you don't know what state your device was in previously, the only thing you can really do is perform a reflash of the factory firmware using Odin. This overwrites all partitions including /boot, /recovery, and /system.
Again, even after a complete clean flash, your device will still fail Play Integrity until you lock the bootloader, meaning that banking/DRM apps may not work.
Click to expand...
Click to collapse
Thank you.
So factory reset affected the rooting and root checker apps can’t detect rooting , then
No other way to check whether my phone was rooted before reset right?
But still wonder reset can not touch system partition but how come root checker cant detect …
This is another question…
if i rooted my phone and then used rooting hide or unrooting or rootcloak to make banking apps run on my phone then i do factory reset,
would banking apps still run While root checker apps dont detect rooting anymore??
Or those efforts that i make to run banking apps are gone with other rooting traces..?
Jenjenjney said:
Thank you.
So factory reset affected the rooting and root checker apps can’t detect rooting , then
No other way to check whether my phone was rooted before reset right?
But still wonder reset can not touch system partition but how come root checker cant detect …
Click to expand...
Click to collapse
Again, factory reset doesn't necessarily affect root, especially with modern system-as-root, or with recovery hijacks. Factory reset just wipes the /data partition - removing user apps and data. In the case of Magisk, this would remove the Magisk manager app, but would not remove the Magisk patch from the boot image.
Jenjenjney said:
This is another question…
if i rooted my phone and then used rooting hide or unrooting or rootcloak to make banking apps run on my phone then i do factory reset,
would banking apps still run While root checker apps dont detect rooting anymore??
Click to expand...
Click to collapse
No, because as I stated above, performing a factory reset does not remove root nor does it hide your unlocked bootloader. Using Magisk as the example yet again, a factory reset would remove the Magisk app as well as installed modules. However, if there were "permanent" system modifications, these would persist after a factory reset.
Jenjenjney said:
Or those efforts that i make to run banking apps are gone with other rooting traces..?
Click to expand...
Click to collapse
Yes.
So to use my device as an example again: Pixel 5 on OEM firmware, rooted with Magisk 25.2, using Universal SafetyNet Fix 2.3.1 mod 2. I pass BASIC and DEVICE integrity and am able to use banking apps.
If I perform a factory reset, the boot image will still be patched with Magisk, and the bootloader will still be unlocked, so Play Integrity will fail DEVICE at the very least, and most likely BASIC too. Because the Magisk app is installed as a user app, this would be removed during a factory reset, meaning there would be no manager available to manage root permissions or load modules until I installed Magisk again.
The only thing a factory reset does is wipe the /data partition and internal userspace storage. It does not reset or restore anything else, so any modifications to any system partitions will persist after a data wipe.
V0latyle said:
Again, factory reset doesn't necessarily affect root, especially with modern system-as-root, or with recovery hijacks. Factory reset just wipes the /data partition - removing user apps and data. In the case of Magisk, this would remove the Magisk manager app, but would not remove the Magisk patch from the boot image.
No, because as I stated above, performing a factory reset does not remove root nor does it hide your unlocked bootloader. Using Magisk as the example yet again, a factory reset would remove the Magisk app as well as installed modules. However, if there were "permanent" system modifications, these would persist after a factory reset.
Yes.
So to use my device as an example again: Pixel 5 on OEM firmware, rooted with Magisk 25.2, using Universal SafetyNet Fix 2.3.1 mod 2. I pass BASIC and DEVICE integrity and am able to use banking apps.
If I perform a factory reset, the boot image will still be patched with Magisk, and the bootloader will still be unlocked, so Play Integrity will fail DEVICE at the very least, and most likely BASIC too. Because the Magisk app is installed as a user app, this would be removed during a factory reset, meaning there would be no manager available to manage root permissions or load modules until I installed Magisk again.
The only thing a factory reset does is wipe the /data partition and internal userspace storage. It does not reset or restore anything else, so any modifications to any system partitions will persist after a data wipe.
Click to expand...
Click to collapse
Oh i got it!
But i used that phone before magisk came out. So i think if my phone was rooted , defintely via one click rooting apps .
Then the answer to my qustion can be different..?
Btw i also saw people saying that they rooted phone with kingroot app and then they did factory reset, root checker apps dont detect rooting.
Its another curioustiy,
Can i bring back stock camera app via OTA update that i deleted with rooting?
Jenjenjney said:
Oh i got it!
But i used that phone before magisk came out. So i think if my phone was rooted , defintely via one click rooting apps .
Then the answer to my qustion can be different..?
Click to expand...
Click to collapse
No. Regardless of how the device is rooted - whether it's the "old" system-as-root way, where su was installed as a system app, or the "new" systemless root way, a factory reset aka data wipe makes no difference. The only way to get rid of it is to reflash the factory firmware.
Jenjenjney said:
Btw i also saw people saying that they rooted phone with kingroot app and then they did factory reset, root checker apps dont detect rooting.
Click to expand...
Click to collapse
Regardless of the "vendor" the process generally remains the same. Either /recovery is hijacked and the system is forced to load root, or root is installed as a system app, or the boot image is patched to allow user root access.
As an aside, Kingroot is dangerous because of some serious security issues. Magisk avoids these through signature verification and private keys.
Jenjenjney said:
Its another curioustiy,
Can i bring back stock camera app via OTA update that i deleted with rooting?
Click to expand...
Click to collapse
Yes.
Reflashing factory firmware, as I stated previously, overwrites everything with the firmware Samsung originally installed on the device - meaning all included apps.
So if you want to return your device to complete bone stock, you'd reflash the factory firmware in Odin, and you'd use the CSC.tar instead of HOME_CSC.tar (the latter is for updating when you want to keep your user data and apps)
Then, you would lock your bootloader.
V0latyle said:
No. Regardless of how the device is rooted - whether it's the "old" system-as-root way, where su was installed as a system app, or the "new" systemless root way, a factory reset aka data wipe makes no difference. The only way to get rid of it is to reflash the factory firmware.
Regardless of the "vendor" the process generally remains the same. Either /recovery is hijacked and the system is forced to load root, or root is installed as a system app, or the boot image is patched to allow user root access.
As an aside, Kingroot is dangerous because of some serious security issues. Magisk avoids these through signature verification and private keys.
Yes.
Reflashing factory firmware, as I stated previously, overwrites everything with the firmware Samsung originally installed on the device - meaning all included apps.
So if you want to return your device to complete bone stock, you'd reflash the factory firmware in Odin, and you'd use the CSC.tar instead of HOME_CSC.tar (the latter is for updating when you want to keep your user data and apps)
Then, you would lock your bootloader.
Click to expand...
Click to collapse
Just updating software that pops up in phone reinstalls stock apps??
But only updating software via ota in phones still dont allow banking apps run. I mean flashing a stock rom and just updating firm ware in phone via ota is different.
Jenjenjney said:
Just updating software that pops up in phone reinstalls stock apps??
But only updating software via ota in phones still dont allow banking apps run. I mean flashing a stock rom and just updating firm ware in phone via ota is different.
Click to expand...
Click to collapse
Yes, because OTA is generally a partial update, as opposed to a full factory flash.
I've told you several times...If you want banking apps to run on your device, and you don't want to use a root solution, you need to clean flash the factory firmware and lock your bootloader. That is the bottom line.
V0latyle said:
Yes, because OTA is generally a partial update, as opposed to a full factory flash.
I've told you several times...If you want banking apps to run on your device, and you don't want to use a root solution, you need to clean flash the factory firmware and lock your bootloader. That is the bottom line.
Click to expand...
Click to collapse
just doing ota update is going to reinstall stock cam app i deleted -amazing thanks.
Honestly… I am worrying malware app could root my phone . Cuz my phone got factory reset by malware app suddenly. So what i have now is reset phone .Thats why i want to know if my phone was rooted..
+ i used data recovery program after reset So i think thats maybe reason banking apps dont run now . But not sure the name of program so cant check if that programs have rooting feature.
So i just want to know if my phone has ever been rooted before reset. So worrying… i cant even sleep.
Jenjenjney said:
just doing ota update is going to reinstall stock cam app i deleted -amazing thanks.
Honestly… I am worrying malware app could root my phone . Cuz my phone got factory reset by malware app suddenly. So what i have now is reset phone .Thats why i want to know if my phone was rooted..
+ i used data recovery program after reset So i think thats maybe reason banking apps dont run now . But not sure the name of program so cant check if that programs have rooting feature.
So i just want to know if my phone has ever been rooted before reset. So worrying… i cant even sleep.
Click to expand...
Click to collapse
We have gone around and around this topic in this discussion. I have provided the answers for you. Without somehow comparing every partition against untouched firmware, there is no way to know what is currently modified. If everything is stock, there is no way to know whether it was previously modified. Your best option, once again, is to perform a clean flash of the factory firmware, and lock your bootloader. Locking your bootloader enables additional security features that verify whether or not the images have been modified, and will prevent boot if they are, which is why you need to perform a clean flash first. Doing this will remove any potential rootkit or hijack, because you'll be overwriting everything to bone stock.
V0latyle said:
We have gone around and around this topic in this discussion. I have provided the answers for you. Without somehow comparing every partition against untouched firmware, there is no way to know what is currently modified. If everything is stock, there is no way to know whether it was previously modified. Your best option, once again, is to perform a clean flash of the factory firmware, and lock your bootloader. Locking your bootloader enables additional security features that verify whether or not the images have been modified, and will prevent boot if they are, which is why you need to perform a clean flash first. Doing this will remove any potential rootkit or hijack, because you'll be overwriting everything to bone stock.
Click to expand...
Click to collapse
Thanks.. i really appreciate it
I dont use that phone anymore . Just wanted to know how to tell ,,
For the last ..
can i check if my stock camera app was modified? Or hackers can delete stock cam and install modified stock cam with rooting.
Can i analysis this app..?
Jenjenjney said:
Thanks.. i really appreciate it
I dont use that phone anymore . Just wanted to know how to tell ,,
For the last ..
can i check if my stock camera app was modified? Or hackers can delete stock cam and install modified stock cam with rooting.
Can i analysis this app..?
Click to expand...
Click to collapse
Yes, there are ways to compare files to determine whether a copy has been tampered with by comparing it with a known trustworthy original. A Google search turns up several results.