I'm moving to a SM-A520W (Canada) from a Moto X Play and I was wondering if it's possibly to modify build.prop without having to actually flash TWRP and trip the Knox counter. On the Moto X Play I can do a "fastboot boot <twrp image>" and it will load TWRP into RAM but not flash it, at which point I can mount /system and use adb to pull/push the build.prop file.
Being new to Samsung's boot loader, is it possible to launch TWRP in RAM using Odin/Heimdall/something else so that I can access /system but otherwise avoid tripping the Knox counter? I want to change fw.max_users, but otherwise I don't want to root my device.
mutantlog said:
I'm moving to a SM-A520W (Canada) from a Moto X Play and I was wondering if it's possibly to modify build.prop without having to actually flash TWRP and trip the Knox counter. On the Moto X Play I can do a "fastboot boot <twrp image>" and it will load TWRP into RAM but not flash it, at which point I can mount /system and use adb to pull/push the build.prop file.
Being new to Samsung's boot loader, is it possible to launch TWRP in RAM using Odin/Heimdall/something else so that I can access /system but otherwise avoid tripping the Knox counter? I want to change fw.max_users, but otherwise I don't want to root my device.
Click to expand...
Click to collapse
Waiting also the answer (new user A5 2017)
Sent from my SM-A520F using Tapatalk
mutantlog said:
I'm moving to a SM-A520W (Canada) from a Moto X Play and I was wondering if it's possibly to modify build.prop without having to actually flash TWRP and trip the Knox counter. On the Moto X Play I can do a "fastboot boot <twrp image>" and it will load TWRP into RAM but not flash it, at which point I can mount /system and use adb to pull/push the build.prop file.
Being new to Samsung's boot loader, is it possible to launch TWRP in RAM using Odin/Heimdall/something else so that I can access /system but otherwise avoid tripping the Knox counter? I want to change fw.max_users, but otherwise I don't want to root my device.
Click to expand...
Click to collapse
SAMSUNG BOOTLOADER does not support fastboot mode
Sorry to bring up an old thread. But would it be possible to root a phone of the same model (not the Canadian or US versions) and repack the system partition. With an updated build.prop without any other modifications. Without tripping KNOX or DM-Verity? Would we have to have MD5s instead of tars while flashing stock firmware? A repacked MD5 with the AP's lz4s would be awesome if possible.
Related
Hello everyone,
after I rooted my phone with the saferoot method, the Knox flag stayed 0 but I have the system status set to 'custom'.
Now I want to return the phone for a warranty case and I want to erase all my data and unroot it. I have read all the posts but I don't get a definitive answer for this. Additionally I have changed my dpi and installed wanam which I used to modify the look. This all means that my system files have been modified, so I can't just do a factory reset.
From what I read, I should remove wanam, busybox, supersu, or use the saferoot unroot script, but as I said, my system files are modified and I dont think this would be enough to set the status to official. I also read that I should use a no-wipe rom, but I cant find the specific rom same as my current firmware, and I'm not sure how I should flash it, from stock recovery or else?
so basically, how do i completely return my phone to stock with status official with currently modified system files?
my current AP is N7100XXUEMK9, CP: N7100XXUEMJ9 and CSC: N7100DBTEMK2, this is all just in case someone needs them. can anyone help me? thanks.
ssterjo said:
Hello everyone,
after I rooted my phone with the saferoot method, the Knox flag stayed 0 but I have the system status set to 'custom'.
Now I want to return the phone for a warranty case and I want to erase all my data and unroot it. I have read all the posts but I don't get a definitive answer for this. Additionally I have changed my dpi and installed wanam which I used to modify the look. This all means that my system files have been modified, so I can't just do a factory reset.
From what I read, I should remove wanam, busybox, supersu, or use the saferoot unroot script, but as I said, my system files are modified and I dont think this would be enough to set the status to official. I also read that I should use a no-wipe rom, but I cant find the specific rom same as my current firmware, and I'm not sure how I should flash it, from stock recovery or else?
so basically, how do i completely return my phone to stock with status official with currently modified system files?
my current AP is N7100XXUEMK9, CP: N7100XXUEMJ9 and CSC: N7100DBTEMK2, this is all just in case someone needs them. can anyone help me? thanks.
Click to expand...
Click to collapse
Flash your official firmware with Mobile Odin pro, with clear data cache options checked.
m.b.jikre said:
Flash your official firmware with Mobile Odin pro, with clear data cache options checked.
Click to expand...
Click to collapse
Thanks for the quick reply. Correct me if I'm wrong but wouldn't mobile odin or even odin from PC trigger knox? I've read in many posts that it would trigger it. Also, the firmware would also flash csc and modem, which would probably again, trigger knox. Am I right or wrong?
ssterjo said:
Thanks for the quick reply. Correct me if I'm wrong but wouldn't mobile odin or even odin from PC trigger knox? I've read in many posts that it would trigger it. Also, the firmware would also flash csc and modem, which would probably again, trigger knox. Am I right or wrong?
Click to expand...
Click to collapse
If you're flashing official rom then Knox would not trigger, so don't worry.
m.b.jikre said:
If you're flashing official rom then Knox would not trigger, so don't worry.
Click to expand...
Click to collapse
are you sure? I don't want to be stubborn, but everywhere I read that if you try to flash anything will trigger knox, and I don't want to void the warranty. so is it really safe?
furthermore, even if I do flash with mobile odin, can I just flash the system partition and not the rest? would this be enough to restore the system status?
ssterjo said:
are you sure? I don't want to be stubborn, but everywhere I read that if you try to flash anything will trigger knox, and I don't want to void the warranty. so is it really safe?
furthermore, even if I do flash with mobile odin, can I just flash the system partition and not the rest? would this be enough to restore the system status?
Click to expand...
Click to collapse
Don't worry, take a look at: http://forum.xda-developers.com/showthread.php?t=1915386
Same to that just flash your official ROM with PC odin or mobile odin, without triggering Knox.
I bought a second hand Samsung Galaxy Tab S a few months ago and it has been working fine.
However, when I looked at version of Android then seems a bit old (5.0.2) and when I did a check for updates it said that it couldn't update because "The operating system on your device has been modified in an unauthorised way". When I checked then it seems that the device has been rooted.
A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
So, should it be possible to remove the root and still preserve all my data, apps, settings, etc?
If so, is SuperSu the way to go or are there other tools I should look at, such as Kingo Android Root?
Or, am I faced with rebuilding with a stock ROM?
Thanks
There is no update. 5.0.2 is the latest.
ashyx said:
There is no update. 5.0.2 is the latest.
Click to expand...
Click to collapse
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
MysteryMan1 said:
OK, thanks for info.
However, I would still like to remove Root and would appreciate advice on this, please!
Click to expand...
Click to collapse
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
If your root manager is supersu then it has the option to unroot in it's settings.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
I've tried to fire up SuperSU, but, run into problems, as described in my initial post, and this is what I need to resolve.
Any ideas?
MysteryMan1 said:
... A quick search suggested I should run SuperSU to remove the root. So, I had to download and install this, but, when I run it says "The SU binary needs to be updated. Continue?" - if I do then I get another message "If you have a custom recovery like TWRP or CWM that can be used to (try to) install the SU binary" and gives me a choice of Normal or TWRP/CWM. I am struggling to know how to proceed.
...
Click to expand...
Click to collapse
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
3DSammy said:
I'm having a bit of trouble understanding the end goal. As stated Android v5.0.2 is the latest non-custom firmware available. As a previous owner has unlocked the bootloader and seems to have flashed a SuperSu version that modification is blocking any OTA update to v5.0.2. It is also clear your trying to avoid loosing user data.
Would it be acceptable to be rooted and use a different method to apply the latest Samsung stock firmware for your region? If the answer is yes install a TWRP recovery for your device model but you'll loose your warranty by tripping KNOX (you may already be in that state). Follow the instructions in the TabS TWRP thread.
Then finish the SuperSU install (where your stuck today). Then install Flashfire. With Flashfire and the downloaded latest Samsung firmware package you can flash the boot and system images to update your install then use ODIN to update the Bootloader image from that download firmware. You could also flash the recovery image but that would overwrite TWRP and in your case I don't see the point. Flashfire needs the whole Samsung firmware file to be available on the device itself unlike when using ODIN to flash the Bootloader image.
As I'm rooted but retained my warranty I use FlashFire and ODIN to update to the latest stock firmware and never loose user data. Unfortunately to root and not trip KNOX I did wipe my user data that first time so it does not seem to be an option for you.
Hope that gives you some ideas. In your current state it maybe as simple as completing the SuperSU install (assuming a custom recovery (TWRP/CM) is already installed) then using Flashfire and ODIN as described.
Good luck
Click to expand...
Click to collapse
Thank you for your very helpful and comprehensive reply. I can't profess to understanding all of it, but, I am sure I will get there eventually!
I shall follow your suggestion of trying to get get SuperSU installed first.
:good:
If you want to go back to stock just flash the latest firmware with odin.
My question is about systemless root. Has any effort been done to get that working on the Z00A?
Systemless root is normally created for Nexus devices where their bootloader detects system partition if it's modified or not, then prevents the end user from booting. Later discovered that systemless root is also able to not trip Knox or break OTA support on Samsung devices.
Systemless root isn't useful on our device, because our bootloader detects kernel and recovery and prevents the end user from booting if these files are unsigned unless the bootloader is unlocked.
Sent from my GT-I9500
I've been reading on the forums and is there anyway to achieve system root on the n5x because i assume flashing SuperSu in twrp just gives you systemless root, I've read something about a modified boot.img, can anyone clarify this? and is system root possible on 7.0 NRD90S?
niklus101 said:
I've been reading on the forums and is there anyway to achieve system root on the n5x because i assume flashing SuperSu in twrp just gives you systemless root, I've read something about a modified boot.img, can anyone clarify this? and is system root possible on 7.0 NRD90S?
Click to expand...
Click to collapse
It is possible to have systen root.
You still need to have boot.img that has dm-verity disabled.
There are flags that you can set for SuperSU install that force it to do system install, but i don't recall if it will disable dm-verity in that case. If not, flash the modified kernel that is on the main thread.
Is it possible to root my motorola moto z play? And still get ota updates/ install them?
Only if you flash back to stock recovery and have the entire os back to stock, is it possible.
You don't need to flash back stock recovery if you don't replace it. Only change needed should be restore original boot partition. This is modified by f2fs fix kernel and any root I know to be working, they work systemless.
You should care not to use the power of root to modify anything (hosts, build.prop, logo, recovery and much more), otherwise you'll end up flashing whole ROMs. Which also isn't that bad.
tag68 said:
You don't need to flash back stock recovery if you don't replace it. Only change needed should be restore original boot partition. This is modified by f2fs fix kernel and any root I know to be working, they work systemless.
You should care not to use the power of root to modify anything (hosts, build.prop, logo, recovery and much more), otherwise you'll end up flashing whole ROMs. Which also isn't that bad.
Click to expand...
Click to collapse
How do does he or she root without having TWRP? Which replaces the stock recovery.
SupahCoojie said:
Is it possible to root my motorola moto z play? And still get ota updates/ install them?
Click to expand...
Click to collapse
You can unlock your bootloader and still receive otas.
All you have to do is flash back boot and recovery before installing the ota.
It Will Works If you not touch on system partition.
Jimi Mack said:
How do does he or she root without having TWRP?.
Click to expand...
Click to collapse
Do not flash it but boot on per-use-base.
fastboot flash twrp
Versus
fastboot boot twrp
Check it out
tag68 said:
Do not flash it but boot on per-use-base.
fastboot flash twrp
Versus
fastboot boot twrp
Check it out
Click to expand...
Click to collapse
Thanks, but what a PITA...
dedraks said:
You can unlock your bootloader and still receive otas.
All you have to do is flash back boot and recovery before installing the ota.
It Will Works If you not touch on system partition.
Click to expand...
Click to collapse
thanks its work with me :good:
OK, is there a guide somewhere that will tell us how to get the OTAs back without losing root?
If not, does anyone have links to the files needed and I'll write one up?
No, it is not possible to generally write such a guide.
1. OTA is not possible while rooted. You need to restore firmware without root, then you can do OTA, then you can root again.
2. OTA is based on blocks, not on files. You need to restore partitions which are modified. If you delete a file and then save it again, it will probably be saved on a different position on the partition.
3. The files which you need (the img-files for the modified partitions) depend on your firmware.
4. The modified partitions differ. Some people flash recovery. Others modify build.prop without using systemless interface of Magisk. Other modify logo.
A complete guide would just be a manual how to flash a stock firmware. At least boot, recovery, system, logo. And you need the exact version which you rooted. A backup after OTA update before rooting or doing other modifications therefore is a good idea.
tag68 said:
No, it is not possible to generally write such a guide.
1. OTA is not possible while rooted. You need to restore firmware without root, then you can do OTA, then you can root again.
2. OTA is based on blocks, not on files. You need to restore partitions which are modified. If you delete a file and then save it again, it will probably be saved on a different position on the partition.
3. The files which you need (the img-files for the modified partitions) depend on your firmware.
4. The modified partitions differ. Some people flash recovery. Others modify build.prop without using systemless interface of Magisk. Other modify logo.
A complete guide would just be a manual how to flash a stock firmware. At least boot, recovery, system, logo. And you need the exact version which you rooted. A backup after OTA update before rooting or doing other modifications therefore is a good idea.
Click to expand...
Click to collapse
I want to lose my moto z play without computer
---------- Post added at 03:10 AM ---------- Previous post was at 03:09 AM ----------
tag68 said:
No, it is not possible to generally write such a guide.
1. OTA is not possible while rooted. You need to restore firmware without root, then you can do OTA, then you can root again.
2. OTA is based on blocks, not on files. You need to restore partitions which are modified. If you delete a file and then save it again, it will probably be saved on a different position on the partition.
3. The files which you need (the img-files for the modified partitions) depend on your firmware.
4. The modified partitions differ. Some people flash recovery. Others modify build.prop without using systemless interface of Magisk. Other modify logo.
A complete guide would just be a manual how to flash a stock firmware. At least boot, recovery, system, logo. And you need the exact version which you rooted. A backup after OTA update before rooting or doing other modifications therefore is a good idea.
Click to expand...
Click to collapse
I want to lose my moto z play without computer which application, please thanks