Database Users

Can't Unroot S4?

So, i tried to Root my GF's I9506 with CF-Autoroot.
Safteynet fails and PokemonGo doesn't work, login problems.
I Unrooted trough SuperSU, restarted the phone a couple of times but PoGo still wont login.
She's on Stock Samsung Rom with Stock Recovery.
What can i do?
I was able to Re-Root with SuperSU for some reason. Had to update the binary tho. That's strange...
Shouldnt work if SuperSU unrooted in the first place?

Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.

Pwnycorn said:
Maybe it leaves files behind. If you're interested, there are ways to hide root from the game.
Anyway, the only sure way to remove root would probably be the flashing of a stock ROM.
Click to expand...
Click to collapse
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?

If the phone is running a stock ROM, flashing a stock ROM usually leaves all of the data intact.

Dallebull85 said:
Hmm. She really dosen't want to do a factory reset. so i guess i have to hide it then..
I think there are a few options i think all of them needs another recovery though:
Magisk + Magiskhide + phh
SuperSu, Suhide
Something called iSu.
Might it help to root again, remove anu "Su" files and folders trough ES Filexplorer? Then unroot from SuperSu?
Click to expand...
Click to collapse
Removing any root file live might break root, which in turn won't let you remove any of the other files left.
Besides, you don't even know what files to look for.
Having a custom recovery won't affect her usage of the phone, nor the game. Besides, it gives you the benefit of making a Nandroid backup.

Ty for all the answers. So a custom Recovery doesn't trigger Saftynet?
Might as well install TWRP, backup and try to reflash stock rom from there.
Samsung Galaxy S4 International Qualcomm (jfltexx)
Samsung Galaxy S4 LTE Advanced i9506 (ks01lte)
Which one? i suppose its the 9506, flashhing my old CF-autoroot for my 9505(jfltexx) didn't work.

To flash a stock ROM, you need Odin, Samsung phone drivers, and the stock ROM from sammobile.com.

OK. But i'll do a backup on twrp first. Ty ty
Fixed it! Reflashed stock Rom with Odin and now Pogo works again!
Ty a lot for all the help. you guys are the best!

My approach to rooting 7.1.1

Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.

Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.

im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.

leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well

DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?

leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.

fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?

leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too

fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.

leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.

fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.

Root problem (full root not systemless)

Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish

zishhaider said:
Hi, so I was trying to get full root not only system less root on j730gm and what i followed here to rooted mobile witj twrp first(boot.img patched), then after that full unroot (keep boot.img patched) and in twrp gave command and install super su zip again and this time logs clearly showed system method while rooting, after all that I am getting bootloop. Mobile is hang on samsung logo, tried reset with twrp and official recovery both. Can some one tell me where i did mistake or where is the problem. My only requirement is to root this mobile and make super user app as system app. Even after hard reset mobile should stay rooted. Any help would be much appreciated.
Br
Zish
Click to expand...
Click to collapse
I don't understand your goal?
Systemless root IS full root. Your terminology is incorrect.
SuperSU doesn't really support system root on Android 7.
I also dont see the point of making SuperSU a system app. Even though its rather pointless if that is all you require for whatever strange reason then you can just move the Supersu app to the system partition.
There is a better way to stay rooted after a hard reset and it's called FRP.

First there is nothing strange in stay rooted after hard reset, trust me. My friend use this mobile. He needs root for lucky patcher. When first he came to me I rooted it via twrp and after couple of days he came back with custom binary block option and plus he doesn't remember newly created gmail id pass. For me it was hell of a job. So i decided to root it permanently. I am not an expert though but my point was to take full root instead of systemless root. Thanks for clearing that 7.0 isn't supported for full system root. I saw here a rom stock dexoded and pre rooted. Is it better option to install it rather than stock rom?

See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root

zishhaider said:
See this link, i was trying to do the same
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Click to expand...
Click to collapse
Like I already stated Factory Reset Protection (FRP) is already built in to SuperSU.
Just do the following in a terminal then re-install SuperSU:
echo "FRP=true">>/data/. supersu
.

Magisk manager and Bootloader

Hello everyone. I want to know, if I unlock my bootloader with TWRP then root with Magisk manager, then do I lose my next Official OTG update? I'm using Stock Samsung Galaxy S8 Oreo. TIA.

najmulbappy said:
Hello everyone. I want to know, if I unlock my bootloader with TWRP then root with Magisk manager, then do I lose my next Official OTG update? I'm using Stock Samsung Galaxy S8 Oreo. TIA.
Click to expand...
Click to collapse
Yep. Your Knox get busted and you won't be able to get another official OTA update..
You can still upgrade though, by flashing it using Odin, but I wouldn't recommend using that every time since it wipes your data.

StardustGeass said:
Yep. Your Knox get busted and you won't be able to get another official OTA update..
You can still upgrade though, by flashing it using Odin, but I wouldn't recommend using that every time since it wipes your data.
Click to expand...
Click to collapse
I heard that Magick is not same as SuperSU. It won't make any change in system and partition. It is systemless root process so if I unlock just my bootloader and root with Magick why I won't be able to get another official OTA update!

najmulbappy said:
I heard that Magick is not same as SuperSU. It won't make any change in system and partition. It is systemless root process so if I unlock just my bootloader and root with Magick why I won't be able to get another official OTA update!
Click to expand...
Click to collapse
The Knox system got busted not because of magisk, but because you're unlocking your bootloader and installing TWRP.
Yes, magisk does offer systemless root, and it ables you to pass safetynet check that is needed to turn on features like Android pay and some bank apps.. But, Samsung pay, and several Samsung apps that relies on Knox is busted once the Knox is tripped.

StardustGeass said:
The Knox system got busted not because of magisk, but because you're unlocking your bootloader and installing TWRP.
Yes, magisk does offer systemless root, and it ables you to pass safetynet check that is needed to turn on features like Android pay and some bank apps.. But, Samsung pay, and several Samsung apps that relies on Knox is busted once the Knox is tripped.
Click to expand...
Click to collapse
Thank you so much for nice explanation

S7E - Install Magisk without wipe or flashing TWRP

Hi guys,
S7E Exynos International 935F here.
Is it possible to temp flash TWRP just to install Magisk?
Is it possible to flash anything useful using stock recovery? (Which seems to happen after booting with vol up+ home + power and waiting for abit)
Will the modded/patched boot image trip knox?
Main objective is to do a titanium backup, wipe the phone, reinstall minimum stuff + app data for that minimum stuff.
Will a ROM like Black Diamond be considered custom and thus trip knox?
Thanks!

TWRP = trip knox.
ivoryroot ( Xperia) for Samsung?
I think not, knox is not drm keys

Airbag888 said:
Hi guys,
S7E Exynos International 935F here.
Is it possible to temp flash TWRP just to install Magisk?
Is it possible to flash anything useful using stock recovery? (Which seems to happen after booting with vol up+ home + power and waiting for abit)
Will the modded/patched boot image trip knox?
Main objective is to do a titanium backup, wipe the phone, reinstall minimum stuff + app data for that minimum stuff.
Will a ROM like Black Diamond be considered custom and thus trip knox?
Thanks!
Click to expand...
Click to collapse
Any custom binary (whether twrp or samsung based custom roms or aosp based custom roms) will trigger knowx bit..
And no you can't install anything useful in stock recovery. Twrp isn't that heavy lol. You can keep it because it is 1000% more useful then stock recovery : )
And no, you cannot even flash magisk without twrp ; )
Want twrp-less root ? And a systemless too like magisk ? Try cf auto root- create your own root file (you can choose system less option there! ) and flash it using odin, other options like magisk or super su require twrp..
Sent from my S7 Edge using XDA Labs

shah22 said:
Any custom binary (whether twrp or samsung based custom roms or aosp based custom roms) will trigger knowx bit..
And no you can't install anything useful in stock recovery. Twrp isn't that heavy lol. You can keep it because it is 1000% more useful then stock recovery : )
And no, you cannot even flash magisk without twrp ; )
Want twrp-less root ? And a systemless too like magisk ? Try cf auto root- create your own root file (you can choose system less option there! ) and flash it using odin, other options like magisk or super su require twrp..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
@shah22 Thanks!
Sorry if I'm being thick.
You mentioned custom binary - do you mean firmware or does that include recovery?
I was under the impression that installing systemless root like magisk (or as you mention cf auto root) would not trigger knox and also be hidden from detection from google and/or banking type apps
My main reason for root (temp twrp) would be to either be able to do a nandroid of my system or titanium before having to wipe everything. From what you're telling me that's not going to happen.
I went through a bunch of root-less apps like smart switch for example that never saved application data, only the apk
Would you say there's a custom ROM that offers several features similar to stock but performs better with better battery life and is mature enough to be a daily driver? I saw Black Diamond but I'm cautious and I realise knox will blow but right now outside of s-health I don't think I have any 'knox' data
Anyway thanks for your time

Airbag888 said:
@shah22 Thanks!
Sorry if I'm being thick.
You mentioned custom binary - do you mean firmware or does that include recovery?
I was under the impression that installing systemless root like magisk (or as you mention cf auto root) would not trigger knox and also be hidden from detection from google and/or banking type apps
My main reason for root (temp twrp) would be to either be able to do a nandroid of my system or titanium before having to wipe everything. From what you're telling me that's not going to happen.
I went through a bunch of root-less apps like smart switch for example that never saved application data, only the apk
Would you say there's a custom ROM that offers several features similar to stock but performs better with better battery life and is mature enough to be a daily driver? I saw Black Diamond but I'm cautious and I realise knox will blow but right now outside of s-health I don't think I have any 'knox' data
Anyway thanks for your time
Click to expand...
Click to collapse
Flashing any firmware or recovery NOT signed by samsung triggers knox bit irreversibly, so flashing anything other then samsung stock WILL result in knox being triggered.. so now you know bruh xD
Any root systemless or not, any rom which is modified will trigger knox. Till now there is NO root method which doesn't triggers knox..
If you want fast stable rom, you can try black diamond rom yeah.. but i will recommend flashing latest stock oreo rom for your region and then flashing twrp+magisk plus debloat it and add any other mods you want. This way it may get less bugs then custom rom, and maybe more stable and faster, upto your preference..
And yeah, triggering knox causes samsung pay, secure folder / encryption to not work properly.. some other samsung related services and some banking apps too..
Sent from my S7 Edge using XDA Labs

shah22 said:
Flashing any firmware or recovery NOT signed by samsung triggers knox bit irreversibly, so flashing anything other then samsung stock WILL result in knox being triggered.. so now you know bruh xD
Any root systemless or not, any rom which is modified will trigger knox. Till now there is NO root method which doesn't triggers knox..
If you want fast stable rom, you can try black diamond rom yeah.. but i will recommend flashing latest stock oreo rom for your region and then flashing twrp+magisk plus debloat it and add any other mods you want. This way it may get less bugs then custom rom, and maybe more stable and faster, upto your preference..
And yeah, triggering knox causes samsung pay, secure folder / encryption to not work properly.. some other samsung related services and some banking apps too..
Sent from my S7 Edge using XDA Labs
Click to expand...
Click to collapse
Haha that does clear things up thanks!
I used to try/flash custom ROMs back in the day (think nexus 1, S2, S3) then got too busy (2 kids popped up plus more work responsibilities) to delve into the community to keep up on what can and cannot be done.
My biggest gripe right now is there's no 'stock' method to nandroid where you actually save application data =\
Anyway I also naively thought you could push a custom recovery not to be flashed but just to run in fastboot so you could perform the nandroid / other stuff.. guess not
I do appreciate your advice on the way forward. I wonder if I can easily copy my s-health data to g-fit for example and be done with it :shrug: