Database Develop

Question about installing Magisk through Odin

So I've already used magisk on my A520F. But the thing is I had to use TWRP to flash it- So that meant that the binaries changed from Samsung Official to custom and things like Knox tripped as it detected I had tampered with the OS (because of TWRP, not Magisk)
So recently I started to search for a way to flash magisk on the ROM I have without the need of using a tool like TWRP, and I just read the official thread but, as I'm almost a noob on these things, I have some questions to ask:
1- I know how to extract boot.img- but then what? What is to patch it? I didn't understand that quite well
2- Lets say I have a firmware(official) which I flashed into my phone. If I extract the AP file and get the boot.img from there, as it's the same file It's supposedly flashed onto my phone, can I use that boot.img to install magisk?
A third thing, not related to magisk but I would be intrested to know
I've installed a UK firmware which turned out to be a Carrier firmware- I had to delete hidden.img to make it flash. I entered into downlaod mode to check everything was in 'official mode' and then I just realised that a new line had appeared in the Download mode list
RMM STATE: Prenormal
Can someone explain what is it?
Thanks anyone who helps me.

Okay, I've already figured out what to do with the boot.img
Tho I still need answer for the second question

carlosmedia said:
So I've already used magisk on my A520F. But the thing is I had to use TWRP to flash it- So that meant that the binaries changed from Samsung Official to custom and things like Knox tripped as it detected I had tampered with the OS (because of TWRP, not Magisk)
So recently I started to search for a way to flash magisk on the ROM I have without the need of using a tool like TWRP, and I just read the official thread but, as I'm almost a noob on these things, I have some questions to ask:
1- I know how to extract boot.img- but then what? What is to patch it? I didn't understand that quite well
2- Lets say I have a firmware(official) which I flashed into my phone. If I extract the AP file and get the boot.img from there, as it's the same file It's supposedly flashed onto my phone, can I use that boot.img to install magisk?
A third thing, not related to magisk but I would be intrested to know
I've installed a UK firmware which turned out to be a Carrier firmware- I had to delete hidden.img to make it flash. I entered into downlaod mode to check everything was in 'official mode' and then I just realised that a new line had appeared in the Download mode list
RMM STATE: Prenormal
Can someone explain what is it?
Thanks anyone who helps me.
Click to expand...
Click to collapse
RMM state: This probably stands for Remote Monitoring & Management. RMM seemingly manages to prevent users from installing a custom binary on their devices while its active.
How RMM works?
There’s more to it than just that though. Say, your device was stolen, or you dropped it and someone found it but decides to use it himself. He’ll wipe your device probably, and when he does, RMM will make it a requirement that the device is connected to the Internet after the first boot. Otherwise, the person, or the thief, won’t be able to get past the setup screen. If he does connect to the Internet, the device will ask for your Google account instead of letting any account be used. Your account information is saved on an FRP partition the device. Since he can’t flash any custom binaries at all, there’s no way for him to get rid of it.

Same Situation
carlosmedia said:
Okay, I've already figured out what to do with the boot.img
Tho I still need answer for the second question
Click to expand...
Click to collapse
Can you help me on how you manage to flash the boot.img of magisk along with the stock ?

How to upgrade rooted SM-T719 from Android 6.0.1 to Android 7 or 8

Hi,
about 2 years ago I rooted my S2 Galaxy Tab (T719) and now I would like to upgrade from Android 6.0.1 to Android version to 7 or 8. I have googled for instructions on how to upgrade a rooted S2 Tab but did not find anything useful (most info is on OTA upgrades which no longer works on rooted devices). Could someone please post step-by-step instructions (please bear in mind that I only ever deal with this kind of thing once every 2-3 years so I do not have much experience). I have TWRP v 3.0.2 installed (do I need to update this as well?) and the tablet is not encrypted (so hopefully I won't have to wipe the system partition and re-install all the app?!?). Thanks.
I also noticed that there is now a huge variety of ROMs out there. How can one know which ones are trustworthy? The main reason I rooted the tablet was to be able to increase privacy (control app permissions with XPrivacy). So I do not want to install some custom ROM that maybe contains spyware or other compromising features. Any advice on this would be greatly appreciated. Given my motivation (privacy) for rooting, would it maybe be better to go back to Stock ROMs (i.e. non rooted) and simply control web access via netguard (by preventing net access for some apps, they may still spy on my contacts, location, or email but cannot phone home to transmit the information)? At least I would still get OTA updates because being excluded from the OTA channel also poses a security risk in itself I suppose. Ok so any advice would be appreciated.
Thank you in advance!

There is no official Android 8 for our device. If you want 8 or 9 you have to install a custom ROM like LuK1337's LineageOS port. It is as safe as LineageOS is by itself on any device. Only problem you might have then is that calling is not possible anymore for now, but LTE works. If you want to use LOS, you HAVE to format data because it's not compatible at all. If you wanna stay on official Android you might keep it. Installing is done by flashing the official firmware with the correct country code over Odin. This will remove TWRP at first so you have to reflash it by Odin afterwards. For firmware download I always use: https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 and Odin is found by google. If you wanna got the way to LOS you have to do all the steps I mentioned before too anyways to have a recent Modem firmware and bootloader. In that case you just have to flash LOS and OpenGAPPS by TWRP and delete /data aka Factory reset.
Regardless what you do, after ODIN is done, you HAVE TO boot into TWRP immediately to keep it from being removed by official firmware. While you are in there anyways you can install magisk to keep it from encrypting /data

Many thanks emuandco. So I guess I will stick with the Android 7 as I do not want to reformat the tablet and reinstall all the apps. I have started to download the Android 7 stock ROM, but it is taking quite long so in the meantime just to confirm, the steps to follow are:
1- use odin to flash the stock ROM (no steps required prior to this? I simply overwrite the existing ROM? I suppose that I will loose root then and need to re-root the device using the standard procedure as explained here: http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html ?)
2- use odin to flash TWRP (I will need the newest version I guess and cannot use the same as for Android 6?)
3- boot into recovery mode to ensure that TWRP does not get overwritten
4- done
Is this correct? Do I then need to reinstall Xposed, SuperSU and Xprivacy or will they be preserved?
Thanks again!
P.S.: BTW, I also found these instructions: https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 which are slightly different from http://www.samsungsfour.com/tutoria...nougat-7-0-using-cf-auto-root-all-models.html and require a wipe of the data partition. Does this mean that for an update to Android 7 I definitely do need to wipe the data partition? If this is the case then this would be a major disadvantage of rooting in the first place and maybe I simply flash the stock ROM and do not root at all but go the "netguard" route as mentioned in my original message?

I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.

emuandco said:
I never used the official Firmware that much. Fist thing I did was going on LuK1337's nerves to get a port of LOS for it up and running So no clue if Samsung manages to keep /data but I guess so. Yeah, looks fine what you list there. You COMPLETELY overwrite ANY modification in kernel or /system, so reflash your mods and root (Magisk). I always recommend to uase the MOST recent TWRP. (https://dl.twrp.me/gts28velte/ should be it in your case).
Ah and looking at your manuals... Check OEM unlock just to be rather safe than sorry if things go mad.
Click to expand...
Click to collapse
Deleted

Root [TWRP + Magisk] kills device Security :: Pin/Fingerprints broken

Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you

dekalbcountyman said:
Hello XDA, I'm going to keep this short and sweet - I was able to root my device using the TWRP + Magisk method and some online guides. I believe after experimenting and flashing over the weekend, there is a bug, race condition, or something that prevents bio metrics and security from properly working on the Note 9.
If I set a pin, as it's required for me to add my fingerprints - when I later try to unlock the phone, the device will say the wrong pin. Deleting the cache, reading guides etc will only get you in a bootloop.
I'm in a state right now where I'm rooted with no device security, as adding a pin will effectively brick the device until flashing with Stock Android again.
_______
I was able to root last week Friday. I didn't bother setting a pin as I was happy to have root. Yesterday, I decided to go ahead and set my pin and soon enough, was prompted to use it to disable security.
I really thought I had mistakenly confirmed a stray character in my pin, and after toying, researching, and flashing my device over the weekend, Ive come to a crux where I could use some expert assistance.
Some guides I used had links to an RMM disabled or some ****, another guide had two zips for a different type of disabler. I'm not linking them, because apparently none of them work, but I believe this is where the problem lies. I think one of the zips is to remove the OEM Integrity Check or some **** Samsung wrote to secure the device. One of the packages I flashed took all those packages but nothing has worked.
Setting your pin during setup, or later in settings yields the same results - you will lock yourself out until you flash Stock Android to restart the process.
We're almost there guys, just need to be able to lock my device like a normal cellhpone user - thank you
Click to expand...
Click to collapse
did you encrypt your device? when you reboot, do you see an animation of a pad lock?

bober10113 said:
did you encrypt your device? when you reboot, do you see an animation of a pad lock?
Click to expand...
Click to collapse
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin

dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
Are you using Snapdragon or Exynos?

mmjs14 said:
Are you using Snapdragon or Exynos?
Click to expand...
Click to collapse
Sir, I am using a
Galaxy Note 9
SM-N960F Internationals Unlocked
Alpine White
Exynos
Boot loader is TWRP and OEM Unlock is staying open permanently
I have all the hardware required, just need to overcome this software quirk so I can lock my phone when I’m not using it

dekalbcountyman said:
Bober, first of all thanks for taking YOUR TIME to respond - as a senior member I feel like we can make progress
No, my phone is not encrypted - there is no lock when booting up, just the Stock Samsung animation
I do not use any system encryption or anything like that. I’m a hardware first guy, and use a suite of my own private encrypted cloud software
I played with my Note 9 before I rotted cow TWRP + Magisk - all tutorials out there mentioned flashing various encryption/security zips which I have - I think those zoos are geared for Knox
After you root the phone, you cannot set any type of biometric security or pin or you will be stuck in a bootloop/lock loop as the device is unable to authenticate your pin
Click to expand...
Click to collapse
ive never seen this. what firmware are you on?
have you tried to download the very latest and completely wipe your phone? use samfirm tool 0.3.6 do dl the latest.
fill up all the slots with the md5 files u dled with samfirm and flash using odin( in csc slot use csc.md5 instead of home_csc.md5.)
go dl
magisk zip:
https://github.com/topjohnwu/Magisk/releases/download/v19.2/Magisk-v19.2.zip
and apk:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.2.0/MagiskManager-v7.2.0.apk
ketan oem fix +root
https://www.androidfilehost.com/?w=files&flid=281291
once back on latest stock firmware root again using twrp 3.2.x.x tar
flash it with odin but go to option and uncheck autoreboot
and flash twrp.tar in the AP slot.
once successful, manualy reboot phone to recovery( dont let it boot to homescreen! so hold vol up + Bixby +power
once in twrp swipe to get in recovery. go to wipe button and Format ( type yes) and go to reboot button and choose reboot to recovery
once back to recovery go again to wipe button and choose factory wipe.
once done flash dr ketan oem and root zip. ( within the aroma setup of that zip choose yes to both option for root and kernel)
once finished you can now flash the latest magisk.zip as dled earlier.
now reboot and setup your device. once done you can install magisk manger .apk that was dled earlier.

Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate

dekalbcountyman said:
Bober, I did your steps exactly as described and used the links you provided and got it working w/ Biometric Security
I've flashed my phone like 20 times so the process took like 15 minutes max - this was also the first time I flashed all the files in the firmware download. Other guides out there tell me I only need to load the AP slot when flashing for this phone.
The "ketan oem fix +root" is the only security/system level zip I flashed using TWRP - besides looking like an early 2000s rootkit, the Terms of Use had an old version listed and said the binary was from 2015
I couldn't take screens, but everything went well when I checked the version
Thank You so much - in the future, will this root method hold for the life of the Note 9? Like when the new Android after Pie is released, will it be as simple as
1. Backing Up Phone
2. Flashing Android 10 Stock via Odin
3. Reflashing TWRP and Rooting
or is there a more streamlined approach to this? Thanks mate
Click to expand...
Click to collapse
actualy the root method that dr ketan created is just a way to bypass an issue that not all phones have(rmm state aka binaries error when booting.
but technically the method should be;
flash twrp, format, reboot again to recovery and flash official magisk .zip
you can also rely on rom developpers to flash their version instead of stock android via odin. this allows you to not always have to go through the twrp/root procedure each time and also rom devs include nice additional features.
anyways glad i could help.

Root galaxy S10 (July security patch update)

hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.

You didnt do it right. I would suggest youtube the magisk rooting process

Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead

Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.

TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).

Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol

TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)

Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon

TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.

Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?

It's real like a $2 dollar bill.

bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.

FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.

Did a root today without issues on my S10 with ASG8

ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?

chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!

ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.

Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.

Note 8 soft bricked

Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.

This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock

ZeroXO said:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
Click to expand...
Click to collapse
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.
Is the unknown (bat) firmware the one I need to flash to stock?
Sent from my OnePlus6T using XDA Labs

TheLogicalGamer said:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
Click to expand...
Click to collapse
Using odin 13.1.3 is recommended.
As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)
If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.