Hello
Those who tried on j727t rooting they know its very difficult
Now i solver this issue i can rooted fully RW permissions and for this i always meed to make kernel permissive but after reboot i back to enforce i even remove whole knox stuff etc but still same, even removed rlc or rmm apps but stl same
so is there any dev who can give me any hint or guide to fix it or anyway to unlock bootloader like g900v etc?
Thansk
Related
Hello all,
This is my first Samsung device, the Galaxy S7 Edge Dual sim (SM-G935FD) bought from UAE.
I used to install TWRP and root every android phone I had before, so I am still not sure whether to root this one. I already have the files required for rooting, but I noticed that there are 2 ways of rooting:
1. Using Odin to install TWRP and then from there install SuperSU.
2. CF-Auto-Root.
What is/are the difference(s) in both methods?
My other question is: I read that rooting will trip Knox, and there is NO WAY to get it back to normal even flashing the original ROM. Is that the case?
One last thing, I am now stuck in the download mode (turned off the phone, pressed "Volume down", "Home" and "Power"), I did that just to check the info on the top left (model and warranty void...) but I cannot seem to restart the phone even by pressing the power button for more than 20 seconds, how can I turn the phone off then back on?
Thank you
*****EDIT*****
Regarding my last question (stuck in Download mode), pressing the same combination got me back to start the phone normally
Cf-AutoRoot will root your phone but then you will have to put your recovery on also usually flashed with Odin anyway or an app if it's working for the Galaxy S7... Twrp plus superuser will root and you'll have the recovery installed.... They both will trip your official (0x0) knox and make it (0x1) custom.... You can always go back to stock rom and get OTA updates but your knox will remain at 0x1......this is supposed to void the warranty but depending on where you live it won't make a difference.... Also if you want to flash roms and mods and kernels just use the twrp method and if you just want root and to be able to use root permission apps use the Cf-AutoRoot.... As of right now I haven't rooted because there aren't to many Roms available... I'm sure I will cause I miss titanium backup and the ability to get rid of all the bloat ware (especially Facebook & Microsoft ****).... The phone runs great without root and battery is excellent.... The last reason I was waiting was Samsung pay won't work with tripped Knox counter.... I live in the US but have the international 935F... So it doesn't look like this variant will support Pay anytime soon.... Probably gonna root when development picks up a little....
*edit*... Always have a stock rom just in case saved to your computer just in case... That would of saved me lots of freak outs and headaches years ago... Now it's the first thing I do before Rooting or flashing anything to my phone
Galaxy S7 edge
Kjc99 said:
Cf-AutoRoot will root your phone but then you will have to put your recovery on also usually flashed with Odin anyway or an app if it's working for the Galaxy S7... Twrp plus superuser will root and you'll have the recovery installed.... They both will trip your official (0x0) knox and make it (0x1) custom.... You can always go back to stock rom and get OTA updates but your knox will remain at 0x1......this is supposed to void the warranty but depending on where you live it won't make a difference.... Also if you want to flash roms and mods and kernels just use the twrp method and if you just want root and to be able to use root permission apps use the Cf-AutoRoot
Galaxy S7 edge
Click to expand...
Click to collapse
Thank you for the detailed reply.
I made a research yesterday on Knox (as I said, this is my first Samsung device), and I just wanted to make sure that I understood things properly.
So now after reading, tripping Knox will disable Samsung Pay (I do not have it in my country) so that is not going to make any difference. But, what about paying using the fingerprint sensor in Google Play, will it stop working if Knox is tripped? I also use the fingerprint sensor to login to my mobile banking app (instead of typing the password every time I want to login), will that stop too? I guess not but again just to be sure.
Thanks a lot once again.
I know when I rooted my S6 all the fingerprint stuff still worked so I dont think it will make a difference... Im not sure with the S7 edge but I would think it would still work cause all of those require a typed password before you use your fingerprint(1st setup only) Then use your fingerprint there after... .. Doesn't have anything to do with Knox
Galaxy S7 edge
yep, it all still works. just Samsung pay & private mode.
Hi XDA.
I have had this idea for a while, not specifically for the Galaxy S8+, but if one device were to be worthy, it would be this one, due to the much higher kernel version compared to past devices.
The idea is to keep the 100% stock ROM, except with root, and have the system believe that it is 100% official. My idea is to root, and replace the Device Root Key (DRK) with a self-generated one, and then rebuild the whole ROM with all of the apps, the kernel, and other parts self-signed, with the device believing that the signatures are by Samsung. This would potentially allow us to relock the bootloader by having the device believe that the boot image is official.
This way we should be able to pass dm-verity whilst allowing modifications to system, pass safety net, and in the long run, pass KNOX with a kernel that fakes the KNOX bit to be cleared, and with further modifications, fake KNOX bit cleared in download mode. We could also make system modifications and convince KNOX that the changes are authorised and official.
Also, I do not like how theoretically Samsung can sign custom firmware to break into your device and remove the reactivation locks and potentially decrypt the device. In theory they cannot decrypt it if the encryption key is derived from the password and is not stored on the device, but I would not be surprised if there is a way.
I love Samsung stock software, but I wish I could root and still have the OOBE with Samsung Pay and KNOX containers.
But I am having trouble gathering concrete information. I am only partially sure that the DRK does what I said, and I am not sure if there are any other keys hardcoded into the device hardware, like the bootloader.
Can anybody comment on whether this is theoretically possible, and how? Or just any helpful information.
One thing I need to know is how the system reads the KNOX bit. If it is a protected mode instruction (unlikely because it would violate ARM compatibility) to put the result into a register, then it would be practically impossible to fake. But if only the kernel can check, then we can patch the kernel.
Also, can the KNOX eFuse be blown by unauthorised actions at runtime? As in, if one obtains root through a kernel vulnerability (like Galaxy S6 with PingPong) without tripping KNOX, are there actions / system modifications that can be done as root that can blow KNOX without flashing some unsigned image? My thoughts are that ideally, if rooting without blowing KNOX happens with another kernel exploit, we could use that window to replace the DRK and the whole system with self-signed software, that we would then have the golden experience of truly owning our own Samsung device, without KNOX ever tripping.
Thanks for any discussion!
Karatekid430
karatekid430 said:
Hi XDA.
I have had this idea for a while, not specifically for the Galaxy S8+, but if one device were to be worthy, it would be this one, due to the much higher kernel version compared to past devices.
The idea is to keep the 100% stock ROM, except with root, and have the system believe that it is 100% official. My idea is to root, and replace the Device Root Key (DRK) with a self-generated one, and then rebuild the whole ROM with all of the apps, the kernel, and other parts self-signed, with the device believing that the signatures are by Samsung. This would potentially allow us to relock the bootloader by having the device believe that the boot image is official.
This way we should be able to pass dm-verity whilst allowing modifications to system, pass safety net, and in the long run, pass KNOX with a kernel that fakes the KNOX bit to be cleared, and with further modifications, fake KNOX bit cleared in download mode. We could also make system modifications and convince KNOX that the changes are authorised and official.
Also, I do not like how theoretically Samsung can sign custom firmware to break into your device and remove the reactivation locks and potentially decrypt the device. In theory they cannot decrypt it if the encryption key is derived from the password and is not stored on the device, but I would not be surprised if there is a way.
I love Samsung stock software, but I wish I could root and still have the OOBE with Samsung Pay and KNOX containers.
But I am having trouble gathering concrete information. I am only partially sure that the DRK does what I said, and I am not sure if there are any other keys hardcoded into the device hardware, like the bootloader.
Can anybody comment on whether this is theoretically possible, and how? Or just any helpful information.
One thing I need to know is how the system reads the KNOX bit. If it is a protected mode instruction (unlikely because it would violate ARM compatibility) to put the result into a register, then it would be practically impossible to fake. But if only the kernel can check, then we can patch the kernel.
Also, can the KNOX eFuse be blown by unauthorised actions at runtime? As in, if one obtains root through a kernel vulnerability (like Galaxy S6 with PingPong) without tripping KNOX, are there actions / system modifications that can be done as root that can blow KNOX without flashing some unsigned image? My thoughts are that ideally, if rooting without blowing KNOX happens with another kernel exploit, we could use that window to replace the DRK and the whole system with self-signed software, that we would then have the golden experience of truly owning our own Samsung device, without KNOX ever tripping.
Thanks for any discussion!
Karatekid430
Click to expand...
Click to collapse
I have also been doing extensive research on this and made some progress. I have a private github wiki where I am detailing my experiments. PM me if you are interested in collaborating.
I recently have rooted my s6+ G928C with build number G928CXXS3CQH1.
Everything work fine except for secret mode in Samsung internet that I knew not working with rooted device.
Although, I didn't find anypost that said samsung pass also not working, I just want to ask thak anyway to make
samsung pass working along with root? Thanks in advanced.
Please help me, any custom kernal or way to fix this?
As far as I know it will never work... but you could try magisk hide but dont get your hopes up.
Flash the superuser uninstall zip when you want to use it and reroot when you need root? Or get magisk set up so you pass safetynet
I have a Samsung j5 2015.
I want to temporarily root it.
After I restart my phone, I want it to act like it never was rooted. Ever. If I give it to my carrier, even, and they investigate it, they won't be able to find it. its status also must be official after doing this.
Is this possible? I don't need a custom ROM or anything, I just want to remove the pre-installed crapware.
just root it and unroot if you dont want it anymore, its that simple(but it might still void your warranty but eh)
That's not much problem my device warranty is already voided. The problem is when i root it it shows root failed i think its is due to locked bootloader. I want to unlock bootloader without wiping data. Is it possible...? @dankfrank33
btw what android ver are you using? did you root it thru twrp(flash method)?
6.0.1 Marshmallow
What you suggest me how to root it...?
i tried kingroot and kingoroot it failed always...
Hi!
I have issue with app on my S7 Edge that demands me to unroot. I rooted my phone 5 years ago or more and I don't remember a thing about it. I did this to permanently remove bloatware. Only way I know to unroot is to flash stock-rom again but I don't want to loose my hard effort on debloating + data and so on. Is there any tricks for that? Like hide/remove su binary? I really don't remember where to start. Also with factory reset or something I cant remember I lost root access partially - that is apps can still tell that phone is rooted (root checker tells that root access is available but then also orange warning that root access is not properly installed on this device). But they can't request root privilege for some reason. But I still have this custom recovery rom installed where I have basically root access to phone - do you think I could use this to somehow hide temporarily root from my app that is complaining about it and then later restore root to the full - that is to make apps able to request root access again? I would like to keep my apps/data and I remember them getting lost in process of rooting due to some samsung encryption crap - not sure how to check data/app loss would be case now since I did it so long time ago. Could anyone help me out?
For documentation purposes. So in my case I had lost root with factory reset. I had to boot into TWRP and re-flash super su. Difference from official tutorial: https://forum.xda-developers.com/t/...ial-twrp-for-galaxy-s7-edge-hero2lte.3334084/ was that in step 9 my phone did not complain about dm-verity,. I did not have to disable encryption and I did not loose my data. Someone may correct me but it was because I had already rooted in past and the most likely cause for "loosing" root was doing factory reset. PS I have european model so I am not sure how much it makes this tutorial different.
Now what is left to do is come up with ideas how to hide root from 1 specific app in Android 7.