Database Develop

[Rom] [Ufirm_Flat_QE2_Hybrid_Nougat_Rom_FlashFire_Install][Status Official For All]

Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source

In the OP I had the ADB_Root_G930U_QE2Files.zip linked to the ADB_Root_G935U_QE2Files.zip zip so please make sure you have the ADB_Root_G930U_QE2Files.zip when downloading. Its fixed in the OP now so just double check
I recommend everyone put the Flashfire AP zip and Rom Zip on your internal storage as the AP file is so large that it may not be read properly do too limitations of some SD Cards. When you select AP file in Firmware there should be 4 partitions that are selected. If not then you have a bad download or need to have AP file on internal storage

Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks

ledezma2003 said:
Thanks for all your hard work . I just installed this so far so good but I am missing Wi-Fi calling. Is that normal or am I just not looking in the correct place? Thanks
Click to expand...
Click to collapse
You may have to flash the TMO version of this rom

jrkruse said:
You may have to flash the TMO version of this rom
Click to expand...
Click to collapse
Ok will try that when I get a chance. Thanks again.

Thx for an awesome rom.
Sorry if this question is asked before but couldn't find a solution (checked Verizon thread as well).
I am running Playstore version ROM and everything is working fine except Video Recording.
Photo is fine but when I record a video with included Camera NX, it only plays sound and the screen is either still or black.

I have been taking a needed break. I will update all my s7 roms including this one in the next few days

Nice

That rom can flash for g930p? tks your work!!

@jrkruse
Thanks for all your contributions to this device. I just bought this device and I've been diving through the forums trying to gather as much info on this locked down device.
Could you provide me with just the boot images that don't check the system image and from what model/rom are they from?
Oh and could you provide the partitions locations? The latest roms have an updated Knox that blocks SU from doing it's thing and I have to perform everything via adb (eng boot).

Blank screen
Hello,
I am on your custom rom and the phone was working fine for a day. After I restarted the phone I am not able to see the lockscreen. Its just blank. I do hear the sound of taking a screenshot when I press the buttons and I also can see the " shut down, restart, emg mode" buttons when I hold the power button but no lockscreen. I tried running the recovery boot img but nothing changed.
There is some kind of issue at the locksceen after a restart.

I'm Stuck
jrkruse said:
Latest Ufirm QE2 Nougat Firmware For The S7 Flat Only
This well give you a Customizable NonRooted Rom that uses stock boot.img not the eng boot image so there is no lag and it will pass safetynet checks and samsung pay will work
Give this guy @umaro some thanks he worked on this until it became reality even when I gave up​
Files To Download
Odin.zip
ADB_Root_G930U_QE2Files.zip
UFIRM_G930_Odin_Firmware.zip
FlashFire_Flashable_G930UFirmware.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip
These first 2 step must be done first unless you are on my previous version of this rom or my carrier specific rom that do not have root or if your unsure just do this first
This Will Wipe Your Phone
1. Unzip UFIRM_G930_Odin_Firmware.zip and flash all files in odin
2. Go through setup ignore invalid sim message and skip adding accounts
3. Goto Step 3 Below
If you are on one of my previous version of this rom or my carrier specific rom
1. Unzip UFIRM_G930_Odin_Firmware.zip
2. Use odin to flash BL and CP
3. Unzip ADB_Root_G930U_QE2Files.zip
4. Flash EngBoot image with odin
5. Root Phone. Im not going to have half a page about rooting there is an entire rooting thread here. The Eng Boot.img can be found in the UFIRM_QD2_Modified_Nougat_Firmware Folder
6. Unzip FlashFire_Flashable_G930UFirmware.zip
7. Copy AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 to your phone
8. Copy UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip to your phone
9. Open FlashFire and click Add Zip and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PS_BS_Free_G930U_QE2_V2.zip make sure to check mount system
10. Now in FlashFire click Add Firmware and choose AP_FlashFire_Only_G930U_QE2_Firmware.tar.md5 select all the partitions
11. Make sure Inject SuperSu is not selected
12. Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last
13. Now Choose Flash
14. Phone will take Up to 20 minutes to boot
15. Reflashing Zip Will Require Flashing The AP File In FlashFire At The Same Time
16. Do not use Package Disabler Pro if you Choose NoNaMe mods in Aroma
MODS- (NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Kernel source
RomControl Source
Click to expand...
Click to collapse
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?

Reegs said:
I followed the directions up to Step 7.
For the life of me I can not get the AP file to copy to my SD card. Yes I have enough space on it and I can get the ROM copied.
I tried copying the AP file with a file explorer, on my PC, external card reader. Every time I try, it gets to about 95-99% and says "copy failed".
I know it says flashfire only, but is that my only option?
Click to expand...
Click to collapse
In my case I created a folder named Download in Internal Storage and copied Zip and AP files there. I didn't have trouble coping files there.
From my experience & guess, you may still have old files & settings even though you flashed U-firm files Step 1-2.
Try to access recovery mode and do factory reset and see if this helps. Make sure you backup all important files to External SD because it will factory reset.

So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!

wolfpls254 said:
So I rooted my phone using Araltd's guide in this forum. I've got a couple of questions about this rom...
1. If I were to flash this rom to my device, would it remove my root access?
2. What's device performance like? After rooting, my device is very slow and buggy. Will this fix that?
3. Will my device still be full of T-Mobile's bloatware?
Thanks!
Click to expand...
Click to collapse
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.

kyungone said:
1. Yes, it will remove Root Access but you can still use ADB to do root stuff like push / pull files.
2. Since it will use stock boot instead of ENG boot, it will fix the lag issue.
3. This is U (universal) firmware so it won't have Tmobile bloat but it will have Samsung bloat/apps. During the install you can also choose de-bloat level too. From my experience BS-Free (2nd one), is both lightweight and stable. If you go with Playstore level (most lightweight, replace Samsung Apps with Google ones), you will have trouble with camera.
Click to expand...
Click to collapse
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?

wolfpls254 said:
Do you know how this rom compares to the QF6 one which seems to be a bit more popular?
Click to expand...
Click to collapse
The QF6 ROM you mentioned is T-mobile firmware so it will have Tmobile apps. Most of them can be removed from ROM install or disabled after.
Other than that there's no performance difference.
If you want Tmobile like environment with Tmobile update schedule, go with T-mobile one. If you want less carrier apps, go with U-Firmware one.

I will no longer be updating my s7 threads until the time Oreo is released with root method. For now I have worked with @stang5litre to bring my non-root method to his amazing rom. He currently has a nougat release found here http://stang5litre-roms.proboards.com/

I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?

amdeng said:
I keep getting samsung pay connection error. any fixes? i tried factory reset and reset settings, but the app still doesnt work. do i have to reflash the rom?
Click to expand...
Click to collapse
If you at any point tried to root it or flashed the modified boot image then you are no longer passing the safteynet checks, my suggestion is to do a clean install and see if it works then try it again making sure you don't root after you are done installing this rom.

[GUIDE][XT1789-06+][EU/intl.] How to safely BLunlock/TWRP/Root/BusyBox/Xposed

WARNING #1: operations indicated on this post might potentially brick your device, make it unusable, to cause explosions, eruptions of nearest volcano and a lot of similar disasters.
For sure they will void your warranty in most countries and need all of your data permanently deleted, so make a copy of anything valuable before starting and don't do any operations if you are not a trained guy and sure about what you are going to do.
These are *not* operations for rookies. I will not be responsible in any case about eventual damages. XDA is your friend: if unsure, please ask! :fingers-crossed:
WARNING #2: operations elencated on this post are indicated and first hand tested as working only on Moto Z2 Force (Nash) XT1789-06 GSM/3G/LTE dual sim 6GB RAM 64GB storage unbranded international version on sale on German market with Nougat v.7.1.1 onboard.
They will probably work on most of unlockable bootloader & SIM unlocked versions, included US -04 versions too, but you'll test them yourself.
They are not intended for (US mainly...) CDMA versions (-01 & -03 if I don't go wrong...) since of a bit different hw/fw so avoid to apply them "as is" on those devices.
WARNING #3: there will probably be better methods to obtain same results and, for sure, there would be more in future. This is only a "recap" of what I've found working and applied first hand on my unbranded XT1789-06 Nash - with, IMHO, great results... - on November 2017.
I think this could be useful for many.
WARNING #4: I'm Italian, English is not my first Language, so... be patient!
1. INTRODUCTION
On this guide you will not find anything particularly new and/or not already present on this section of XDA.
So, why this guide? For some reasons...
First of all, to date every guide posted here is for a single operation (e.g. root, TWRP, etc...) and do not take in needed consideration interactions between single operations that, often, can be present, potentially dangerous and/or lead to unexpected behaviours.
More, for a single operation here there are often different posts with different guides/solutions and this could leads to errors and or doubts about what's better for our device...
Last but not the least, to date Nash developers here are mainly from US and so working on devices for the most part provided with branded fw and/or a bit different hw/fw respect to international unbranded versions sold on Europe, Asia, South America & Australia.
From my previous experience with my "old" Griffin (Moto Z) Motorola's fws are often interchangeable between devices with no (or only minimal...) issues at all, but, anyway, having a guide with operations first hand tested on same device is surely safer...
So, in this guide I'll link all best single guides posted here and I'll comment & link them to obtain a single complete "to do list" of works...
2. WHAT WE'LL GET
Following this guide we'll get a Moto Z2 Force with unlocked bootloader, latest available firmware (at present...) on board, a working TWRP recovery, complete root access, BusyBox support (needed for A LOT of interesting sw/tasks...) and Xposed support (I don't think I need to explain Xposed features & benefits here... ).
Taking in consideration how Moto's devices come with a "quite stock/vanilla" Android version on board, they are between the best devices to be rooted & Xposed provided to obtain a great customized system.
If you want to remain stock with your device eventually go with Samsungs (or similar...), but if you want a device that is a "blank canvas" for your customizations, Motorolas and this configuration would quite be the best you could want.
You are surely thinking about lack of Magisk and "SU hiding" solutions... obviously there are reasons for this.
Magisk: I have first hand seen how Magisk is a "very intrusive" software with its installation, it goes to modify *A LOT* of things on system partitions and this could leads to eventual issues/incompatibility.
More, it has its own rooting system (that in my humble opinion isn't better than SuperSU) that I preferred not to use (beneath I think it could be disabled... ) and that could conflict with SuperSU, if not now, maybe on successive Magisk updates (as it happened on my old Griffin... ).
Last but not the least, it seems to still have issues with particular partitioning present on our device (we'll see them later) and with TWRP flashing for same reasons...
Not to mention how, to date, it has really so few functions/modules we can't have using Xposed....
SUhide: there is a detailed guide on how to install succesfully SuperSU with its SUhide function on our device. On the same guide it's reported how that method is uncompatible with Xposed and leads to unsolvable bootloops if we setup both of them.
It is still not clear (to me...) if this is related to SUhide itself or to the different SU installation needed for SUhide to work but, anyway, I preferred Xposed obviously.
Not to mention that for Xposed have been developed some modules to succesfully hidden root (even if I don't know if they already works with Nougat... )
3. LET'S TAKE A LOOK TO OUR DEVICE
Knowledge is power. So, taking a look to our device particular features will help us to avoid errors and eventual issues...
Motorola developed our device with a new configuration/partitioning scheme seen before only on Google Pixels / Pixels XL, making our device probably the first "not Google" one to adopt it.
It is mainly marked by two news:
- there is no more a recovery partition :crying:
- there are two copies of boot and system partitions, called boot_a, boot_b, system_a & system_b and device is capable eventually to boot from every of them :cyclops:
Let's look them in details..
Recovery is obviously still present victory BUT it has no more its own partition, it is instead included in boot partition (where before there was only kernel and little more...) creating a potentially unwanted (by us tweakers, probably wanted by Google for the opposite reason! ) link between boot and recovery where safe rules would want them as unlinked as possible!
This leads to the need to flash a boot.img containing both kernel and recovery when we want to update only one of them (e.g. installing TWRP...) and this will have to be taken in account every time we would go to update kernel, TWRP but even when rooting (in fact, at first, developers were not able to gain root together with TWRP... issue then solved succesfully :highfive.
On Pixels their developers have found some methods to overcome this problem, but on our device, to date, we still don't have a complete solution to this issue. Anyway we are going in the right direction and it will be only matter of time in my opinion (especially since I'm "stressing" our developers to realize a similar solution...! ).
Double partitions for boot & system, often referred as "A/B partitioning" is a system introduced by Google to distribute OTAs in safer & seamless way, without interrupting user work during updates... (bah... ).
They are so totally unuseful as originally designed for US, since of going with TWRP/root, OTAs are no more a solution to upgrade and this partitioning scheme introduced some complications which have led to issues as with Magisk (as already seen...).
BUT as soon as we'll learn how to well manage them, new horizons will open (like updating fw on a partition still having the older one on the other for safety reasons and/or having two different fw versions and be able to choose what to boot from.. ). It's only matter of time...
Anyway in this guide we'll face them ever with safe in mind at the moment...
4. READY? LET'S GO WITH UNLOCKING BOOTLOADER!
If your device has unlockable bootloader (and if it is an international unbranded XT1789-06 it should have...!), you can easily unlock it with this good guide:
https://forum.xda-developers.com/z2-force/how-to/how-to-unlock-bootloader-t-mobile-t3654657
There is no more to say about this guide since it is well done, only some notes:
- guide title speaks of T-Mobile but obviously is suitable for international/unbranded too...
- please note that unlocking bootloader will wipe from your device all data & media storage (and they will be wiped again in successive steps, so *be sure* not having nothing valuable - e.g. your girl pics.. - before starting with procedures);
- install Motorola's latest drivers & fastboot provided on their site as hinted on guide. Don't skip this step to avoid potential issues in successive steps...
- if I don't wrong remember, step 8 of guide has to be repeated two times to confirm unlocking. Anyway look at your console messages and follow directions...
Reboot to system and make a fast configuration (we'll wipe them in minutes... ) to check all is ok and re-enabling usb debugging is preferred.
5. DOWNLOAD & UPDATE YOUR FW
I don't know with what firmware your device will come, BUT if it has anything *before* Nougat v.7.1.1 rel. NXPS26-122-68-1 we well go to update to this for following reasons:
- we need a (good) complete stock fw image to be flashed in case of problems;
- it is updated to September 2017 security patch;
- we have a TWRP with *this exact kernel* (they are linked in same image, remember?) for those (like me... ) which like a "so close to stock as possible" system...
This firmware can be downloaded from the following link: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (about 2,35 GB..)
PLEASE NOTE: If you have newer firmware don't use this BUT try to download a matching version with your actual one.
Zipped file has to be fully unzipped into the folder containing fastboot executable (downloaded from Motorola!) on your PC.
If you get any error unzipping, *DON'T FLASH* anything and download again (eventually from another browser/PC).
Fastboot sequence I used is the following:
Code:
fastboot devices
pause
fastboot flash modem NON-HLOS.bin
pause
fastboot flash fsg fsg.mbn
pause
fastboot erase modemst1
pause
fastboot erase modemst2
pause
fastboot flash bluetooth BTFM.bin
pause
fastboot flash dsp adspso.bin
pause
fastboot flash logo logo.bin
pause
fastboot flash boot boot.img
pause
fastboot flash system system.img_sparsechunk.0
pause
fastboot flash system system.img_sparsechunk.1
pause
fastboot flash system system.img_sparsechunk.2
pause
fastboot flash system system.img_sparsechunk.3
pause
fastboot flash system system.img_sparsechunk.4
pause
fastboot flash system system.img_sparsechunk.5
pause
fastboot flash system_b system_b.img_sparsechunk.0
pause
fastboot flash system_b system_b.img_sparsechunk.1
pause
fastboot flash system_b system_b.img_sparsechunk.2
pause
fastboot flash system_b system_b.img_sparsechunk.3
pause
fastboot flash oem oem.img
pause
fastboot erase carrier
pause
fastboot erase cache
pause
fastboot erase userdata
pause
fastboot erase ddr
pause
fastboot reboot
That is ready to be put into a batch file to avoid errors and having the possibility to check results of every single flashing since of pause commands presence (press a key to continue to next file). Batch file has to be placed and started from same folder of fastboot & unzipped files to avoid errors.
Please note:
- I've added a fastboot devices command as first to check if your device is properly connected;
- I've used stock sequence of flashing BUT removed gpt (partitions) and bootloader for safety reasons (no need to flash them usually... and let Motorola upgrading your bootloader rarely is a good choice... )
If all flashes will go fine your device /data would be wiped (yes, again!) and phone will reboot after last command.
If something go wrong stop the sequence by CTRL+C and do not reboot your phone until you have understood/cleared/fixed what has gone wrong.
If fine, again... reboot to system and make a fast configuration (we'll wipe them in minutes... ) to check all is ok and re-enabling usb debugging is preferred.
6. INSTALL TWRP
This is a quite simple step, but you have to take a decision before you start...
I'll provide two different boot+TWRP image files as attachment to chose from (both of them realized by @joemossjr )
First one is composed by stock NPXS26 kernel and TWRP v.2 (it's a 3.1.1-0 in TWRP versions), while the second is composed by a kernel recompiled (with little modifications) from sources by joemossjr and TWRP v.3 (still a 3.1.1-0 in TWRP versions) with some little improvements (you can go to his thread for details on TWRP https://forum.xda-developers.com/z2-force/development/twrp-3-1-1-0-moto-z2-force-nash-t3687421 and to this one for details on Pantheon kernel https://forum.xda-developers.com/z2-force/development/kernel-pantheon-kernel-t3702208 ).
If you are on NXPS software version (flashed before) and want to remain "full stock" go with TWRPNPXS.zip, otherwise (you preferring newest firmware or want all newest features) go with TWRPREV3.zip.
Both files *have to be* decompressed, *can't be directly flashed* and your choice of them has to be flashed in fastboot mode with the command:
Code:
fastboot flash boot TWRPxxxx.img
where xxxx is matching your choice.
If all have gone fine, you can now reboot to recovery and make some backups if you prefer (please note you will need to place them to an sd card or to a plugged USB key, since internal memory will be fully deleted again soon...
PLEASE NOTE: during this phase still *don't enable* TWRP to Mount system as R/W ("Swipe to allow modifications for /system" message...) since it could lead to a not booting system if DM verity check is still enabled (it shouldn't since what @ChainfireXDA reported on Twitter, but it is better to be safe...).
A reboot to system to check all is still ok is preferred. If TWRP asks to install his app files on exit, *be sure* to decline/skip (ever! There is an option in TWRP to disable this request too!).
PLEASE NOTE: this way we are flashing ONLY ONE of the boot partitions with TWRP (usually boot_a) while the other (boot_b) is unaffected. This is a wanted behaviour to stay on "safe side".
PLEASE NOTE: On the linked thread @joemossjr put a flashable zip file to update it from inside TWRP itself which flash both boot_a & boot_b. So if you'll want to update to newer versions (and remain on safe side...) unzip that file too (instead to flash it in TWRP), extract boot.img contained inside and flash it with the same command indicated before.
Please note all newer versions will use Pantheon Kernel.
WARNING: If you will in future reflash kernel/TWRP to update them, you would lose both root & disabled forced encryption!!!
So, after every boot.img flashing *you will need*, before booting system, to boot TWRP and flash again SuperSU before reboot to system.
If you fail to do this you'll face bootloops and/or your /data partition will be corrupted. So a /data backup (on external storage!) before a kernel/TWRP update would be mandatory.
7. ROOT & DECRYPT DEVICE
In this step we will go to finally root the device and decrypt its /data partition. This operation *will delete all data again* on you device (downloaded files & pics too!).
Decryption of /data is needed for many reasons:
- to date TWRP is unable to work with compressed /data (and, anyway, it's ever dangerous to work with encrypted data backups/restore... )
- some advanced software you'll go to use could have issues with encrypted data
- a decrypted device is slightly faster
- you definitely will want it unencrypted... listen to me!
Since our phone will come "force encrypted" (it can't be disabled on stock fw!), we need SuperSU help on this and so we'll need to follow *at perfection* the following provided sequence!
Not all SuperSU are equals (more... they are all different! :silly so, tested working fine version to be used is this: http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
If newer will be out, don't mind, you could ever upgrade it from inside a working system...
Steps are:
- boot to fastboot mode (from off, VOL DOWN + POWER)
- from fastboot mode select RECOVERY mode
- go to wipe menu and select /data FORMAT (not wipe or factory reset, FORMAT!)
- if you have placed downloaded SuperSU zip file on SDcard or USB key browse to it in TWRP Install menu (otherwise connect your phone to PC and trasfer it to internal memory and then browse for it), then Flash it.
- *do not* and I repeat it, *do NOT* clear cache/dalvik cache
- reboot to system
First boot could take a while and probably it reboots one (or two...) times, but at the end it will boot... :fingers-crossed:
You'll have to reconfigure again your system BUT this time, if all has gone fine, it's the good one, so you can do a better configuration if you want.
You will need a working Play Store for next steps, so add a data SIM and/or a wireless network and setup a Google account to enable it.
To check if all has gone fine you should have:
- a SuperSu icon into apps drawer
- on Settings - Security there should be an option to encrypt your system (DON'T chose it! :silly instead of the previous "encrypted" status..
It could be a good moment to download an useful Root check app. A good one is Root Check by JRummy Apps which is able to check Busybox & Xposed presence too (and more...).
8. BUSYBOX & XPOSED
If you have reached this point and all is fine, now it's very simple to complete.
Both Busybox & Xposed can in fact be installed from inside a working rooted system, so...
- download from Play Store BusyBox (free version) by Stephen (Stericson), open it, grant root permissions and press Install button without wait all the (unuseful) checks
- reboot
- enable in Settings - Security the "unknown sources"
- download from here https://forum.xda-developers.com/attachment.php?attachmentid=4319220&d=1509453299 latest Xposed installer/manager apk
- install it, open it and grant root
- select Xposed v.88.2 (or newer if available) for arm64 (if many options are showed be sure to select this, arm64!!!) and select Install (*NOT* via recovery... simply normal Install)
- when prompted for a reboot, accept it.
Please note first reboot could take a while and, again, it could self reboot one (or two times...). When at last it will reboot... gotcha!!! It's cigar time!!! :victory:
Well... it has been a LONG WORK to write this as simple & complete as possible. I hope to not have inserted any error and to have been enough clear on provided instructions.
If you'll find any errors please report to me for corrections.
Newer & better methods are welcome too.
If you liked this, PLEASE USE THANKS BUTTON!
EneTec
MANY THANKS TO:
@seniorstew
@joemossjr
@jhofseth
@Uzephi
for their useful linked guides and/or great development! :good:

Reserved #1.

Reserved #2.

Awesome guide! One of the most intricate guides that goes over every last detail that I've read on XDA in a long time. Thank you. ?

...

Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)

3's&7's said:
Great guide, thanks for the notes re: Xposed...I kept trying to install from TWRP (habit)
Click to expand...
Click to collapse
Our device still needs some cautions & tips...

Issue with Modem/Radio
After following your guide to the letter, my phone would not connect to a mobile network and would say "Error while searching for networks" when I tried to force it to find one. I ended up following this guide to try and get back to a working setup:
https://forum.xda-developers.com/z2...m-stock-november-hybrid-rom-t-mobile-t3712795
Unfortunately, nothing is working. Any help would be greatly appreciated.
Thanks!
-Josh-

I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.

might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao

just Wow!! What a great post!!

Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!
Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!
Any one have full stock image, at least of the boot partition from Dual SIM, UK?
PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.

hashnon said:
Damn! Why did follow this guide!? I knew I didn't need to flash anything but boot/boot_a and stay on stock FW with only TWRP from Pantheon kernel!
Now I have a Moto Z2 Force (Dual SIM, UK, retail) without wifi, mac 02:00:00:00:00:00:00:00 and it cannot switch it on!
Any one have full stock image, at least of the boot partition from Dual SIM, UK?
PS: No need to link to Factory Image Moto Z2 Force (NASH) RETAIL. both of them aren't fixing anything for me.
Click to expand...
Click to collapse
Bitdefender blocked it for me for the longest time, then after reinstalling minimal ADB and Fastboot, Motorola Manager, and allowing access to Windows File Explore through Bitdefender, it worked for me; check your antivirus, hope that helps.

Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!

hashnon said:
Blocked what? And anyway, I don't have any antivirus. There is brain and Linux for that!
Click to expand...
Click to collapse
Oh my bad, lol

Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.

hashnon said:
Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave my general idea what to do and what to check.
Click to expand...
Click to collapse
Good to hear that, I got so mad when I went in and tried rooting my Z2F without reading this guide first on the very first day that I got it. ??

Deester4x4jr said:
I figured it out. Had to use the Flash ALL Package from that other post. The modem firmware is very specific.
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

ilovemeow said:
might be this is the reason i loose 4G+ (4G instead) signal after flashing lmfao
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?

hashnon said:
Ok, fixed it my self, this: https://forum.xda-developers.com/ne...0000000000-t3257465/post65960082#post65960082 gave me general idea what to do and what to check.
Click to expand...
Click to collapse
This is intended/tested only on EU/intl. XT1789-06... on what version did you applied all this?
How do you fix your wifi issue exactly?

How to ROOT Samsung Galaxy Tab Active 2 T395 - SOLVED !

First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!

How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.

Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!

I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.

[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)

Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you

oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.

RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew

Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,

Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.

Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.

Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt

Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?

Hello, did you manage to remove the "format as internal" lock?

Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?

alguma fortma?

Alternative method magisk root [stock android 9][NO TWRP][Samsung A70 FN/DS]

purpose of this post is to share an alternative method for those who fail to root using @topjohnwu recommended method or the method posted by @Grarak here on A70 forum that involves patching recovery.img in magisk and then flashing that in twrp>install to boot.
failing to root means either bootloops or unstable magisk root or magisk root disappearing randomly or after a module installation.
this is not my original guide , i was told this method by @raeumler via PM and i am sharing it on A70 forums incase other methods dont work.Some of the steps may not be neccesary , but i did them ritually anyway
my phone model is SM-A705FN /DS and firmware version is A705FNXXU5ASL4( with 1st jan 2020 updates) . country is PAK
do this at your own risk! i will not be responsible for any negative consequences
appropiate links and files will be posted as attachments
rooting procedure( read each step twice)
1- UNLOCKING BOOTLOODER= this will factory reset device . backup your data
read step 02 of this linked guide https://forum.xda-developers.com/galaxy-a70/development/recovery-twrp-galaxy-a70-t3955984
DOWNLOAD FIRMWARE AND ATTACHMENTS= now i am assuming you have stock samsung android 9. if not, download your firmware via SamFirm windows program and flash in odin to go to stock[ program available in attachements]. Download other attachements too
2-Find vbmeta.tar in downloaded attachments and unpack it. you will get vbmeta.img file.
3. unzip stock Samfirm downloaded firmware. you will get 5 files in it (BL,AP,CP,CSC and CSC_HOME).open the AP File from the factory rom with 7zip
4. remove userdata.img, vendor.img and system.img from the AP file
5. replace vbmeta.img with the one you have downloaded in step 2.
6. repack AP as AP.tar [ use 7zip or peazip. i used peazip windows program, ensure file type is TAR]. transfer this AP.tar to your phone
7. install magisk manager 7.5.1 on your phone and open it. connect your phone to internet.
8. hit the upper install button and choose "patch a file"
9. choose the repacked AP file and patch it[ this requires active internet as magisk needs to download its zip file]
10. copy the AP file which magisk creates in internal storage/download/magisk_patched.tar back to your pc (better keep it named as such for differentiation, its irrelevant how the file is named as long its a tar file)
11. download,unzip and open Odin 3.1.3.1[available in attachements]. i used Odin3+v3.13.1_3B_PatcheD.exe , there is a simple version too inside the zip
12. go into download mode on your phone (shut down completely then hold vol+ vol- togather and plug in cable connected to PC ). Odins should show Com port X as blue
13. in odin: put the BL, CP and HOME_CSC in its place (the files from the factory firmware you downloaded in step 1 from SamFirm windows program) and place the magisk patched AP on AP
16. check if you want autoreboot or not, its your own taste (some feel safer with autoreboot unchecked, both works)[ i kept autoreboot checked]
15. hit start and let it finish (when it stucks on something try another cable and install latest samsung adb driver.)
16. let the system reboot
17. if you get stuck in bootloop or freeze >10 min on samsung logo, try to force reboot.press volume down + power till screen turns blank then press volume + and power till bootloader unlock screen appears and then let go of all keys.
if still it doesnt boot, then press volume down and power togather to force shutdown and then press volume up and power till stock recovery boots up. Mine at this stage said firmware is corrupt ,factory reset needed so thats what i did in stock recovery. power off system in stock recovery and then press volume+ and power till bootloader warning screen , let go of all buttons, it should now boot up fine with magisk manager app in app drawer. DONT OPEN IT YET
download this app from play store https://play.google.com/store/apps/details?id=fr.petrus.tools.reboot&hl=en_US. open app and press reboot. No need to press any keys
on reboot complete ,connect to internet,open magisk, let it check for updates, it should say installed in both portions. magisk will do additional enviromental steps and then reboot. on booted up, use the linked reboot app to reboot again.
now magisk should be installed all fine
for viper4android>open magisk>swipe left and tap downloads> installed 2.7.1.6> reboot with linked app
on reboot check if app is installed, if not > install and login on xda labs and download viper4android 2.7.1.6> open app> give it root accesss> let it reboot device on installtion> on bootied up reboot again with linked app and then check drivers on viper4android[ make sure master switch is on and then play some music ,tap the chip icon to see driver status and processing status
from here onward, always use the linked reboot app to reboot device. if an app or module reboot device automatically( like viper4android does ) then on boot complete,reboot again with the linked app
Credits to @Grarak for his original work and files
 @raeumler for his guide.

Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.

kac222 said:
Unfortunately, it doesn't work on Android 10.
There is an error in Odin when flashing files.
The error is when flash the AP file, more specifically vbmeta.
Click to expand...
Click to collapse
This is for stock android 9 as the title says.
Follow @MarvinMod guide to root android 10

Yes i know but i tried for yourself. I know how rooted on Android 10. Regards.
Wysłane z mojego SM-A705FN przy użyciu Tapatalka

Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?

DelphisDoofer said:
Looks like a useful guide, thank you for putting it up. I'm really not sure how to get the firmware though from the SamFirm program. I found this ( https://androidmtk.com/use-samfirm-tool - might be useful info?) since I have never used the samfirm tool before I am lost at that step. I don't know if there's a list of region codes somewhere? I have an 'international version' A70. Using SM-A705MN, baseband version A705MNXXU3ASI1 .. Since I'm in the US, should I look to getting that type of ROM or should I find out what region this particular ROM already on the phone is, and use that?
I've done rooting before (Samsung S4, HTC M9, LG V20) but these phones seem even more complicated.
Even if all this works, then the root is not 'permanent'? I'm not sure why a different 'reboot app' would be needed if the system is modified in a way to enable things like magisk/super su?
Click to expand...
Click to collapse
Download phone info app and note pda, csc and phone codes.
Use these codes to Google your exact firmware and download that ( you may have to visit various websites that offer better speed)
The samfirm, frija only allows latest firmware to be download, not the currently installed one.
One you have the stick firmware file, then you can proceed with rooting.
If you are on android 9 use this guide
If you are on Android 10 use MarvinMod guide.
This reboot app is what I currently use. Haven't experimented with other apps.
The root is permanent as long as your reboot with the mentioned key combination or the reboot app.
The reboot app simple allows you to reboot without the key combination. If you don't want to use this app then you must reboot with the mentioned key combination to retain root. Otherswise you wouldn't have root unless you reboot again with correct combination.
To make this easy I suggested that reboot app
Yes I feel you bro, I had Samsung note 2 then note 4 phone and they were easier to root.
But with Google changing things the best way to root is to use magisk and this complicated methods

i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....

raeumler said:
i think you can make a little script for rebooting. should work. i really want to know how the bootpartition is corrected, at boot its recovery-from-boot.p as image and install-recovery.sh for reenabling stockrecovery. if you rename this files bootup should work without reflashing boot or recovery. there have to be something similar to the rebootprocess, a script that flashes a sparse image (the *.p file to delete su binary or something like that..) or it just kills the su binary in the folders itself. im to stupid for dmesg and logcat i couldnt find out whats going on at reboot. also the petrus reboot app reboots instant, keys doesnt. seems to be that adb reboot deletes root too. yesterday, somehow my fone did sonething last night, which crashes root again.....i need twrp urgent to make backup. but the binary let not decrypt it. U5 is android 10 bootloader and there are some issues with twrp (decrypt). last time it has saved my backuptry to /data/backupfolder as internal is encrypted. i dont want to factoryreset this phone....is it complicated to build a recovery ? or is there something like a clickitalltogetherapp?
---------- Post added at 09:46 AM ---------- Previous post was at 09:24 AM ----------
following reboot variants keeping root:
hold all keys for 10 seconds
reboot via terminal or script
petrus app
following kills root:
standartreboot with hw-keys
adb reboot (on a dosprompt from pc)
boot to stockrecovery
magisk module reboot
but thats is such a XXXX .. i dont have a word for it, in the beginning computers and so are working logical....seems that samsungs security trends are not that logical as needed... i hate samsung :/. there have to be someone who find the "unsu"-files...cannot be....
Click to expand...
Click to collapse
I didn't messed with boot or recuvery files like the way you DM me.
But I have been noticing strange behavior with petrus app.
Reboot option in petrus app is kinda of like fast reboot or reboot UI. Because all apps opened and present in task manager remain so after reboot with petrus app.
Also once you power off with petrus app,
1= booting up with root key combination results in phone getting freeze Or bootlooping
2=. Force shutting phone again bootloop phone.
3= Going to stock recovery and rebooting system bootloop.
4= going to stock recuvery and shutting off phone from there and then simply pressing power button without key combination, successfully bootup phone with root intact.
This is such a bizzare behaviour
Oh and i am still on Android 9 pie.

Solved - Boot S10 into rooted ROM without requiring 3 buttons pressed

I have purchased my Samsung S10 Exynos and successfully rooted it using the only possible ways that have seems to be available so far. I have gained root, but I was wondering if anyone has solved the issue of having to turn the device on with all 3 keys held down at the same time. I understand that this is because the rooted version of the phone has be installed on the recovery of the phone, but I hope that there becomes a way to turn on the phone with root and use only the power button. I check from time to time, but it seems that this has not been solved yet. If anyone can find a solution for me so that I do not have to keep searching then I will reward them $100. An idea that I had is if there was a way to modify the power button to boot into recovery by itself? I believe this would be impossible but if anyone could think of a way to do that then that would solve the problem. I am okay with never being able to unroot the device if this would be the case.

How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery

DHGE said:
How often do you cold boot?
reboot:
- Magisk boot menu
- adb reboot recovery
Click to expand...
Click to collapse
Hello, thank you for the suggestion. I thought about that idea already and I forgot to mention it in my post. I am looking for a way to do it via a cold boot. I know about the reboot into recovery method already, and I know of a way to map the power button to reboot into recovery if held down, but I am looking for a way to cold boot into recovery with just the power button.
I like your idea, but if there was a way to do it as a cold boot then that is ideally what I'm looking for. Your method would work if there was a way to just keep the phone shut down and wait until I hold the power button to turn it on and then it boot into recovery. If you can think of a way to do that then let me know.
The reason I am seeking this is because I root the S10 out to have a proprietary app on it and the app requires root to function properly. I need the power button to boot with root on the S10 so that it will always do so and my employees / customers will not access the non-rooted side of the phone by accident. The 3 button combination is too difficult, so I would need to resort so either a S8 or S9 if the S10 won't allow power button only to boot with root access. The app that I make uses a great amount of battery life so I need the ability to shut down the phone and cold boot it back into recovery. Thanks.

Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.

pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
Awesome. Your solution sounds perfect for what I was looking for. Yes, I got my S10 back over a year ago and rooted it with patched AP file and magisk. I was only able to find that method even up until yesterday. I would like a step by step if you are able to quickly put one together. If it works then I am glad to grant you the reward for your help. I am willing to do this in the easiest way possible, even if it requires wiping data. I never used the phone so wiping is no problem at all. I am looking to do this to several devices so the easiest and fastest way would be the best. I will look into your comments and see if I can figure out doing this over this weekend. Will keep everyone updated.

pjc21 said:
Hi, I assume you have rooted using the magisk-patched-recovery method (patched AP file) and if memory serves and from what I am re-reading this method does require the 3-button-combo to boot to rooted system.
When I first got my s10 and rooted this was the only method at the time, but then came custom kernels with built-in magisk.
With this method from power menu if I...
- reboot, phone will reboot to rooted system.
- power off, the power on button will boot to rooted system.
In fact I'm not sure how/if I can boot to non-rooted system with this method.
I currently on custom rom AmbasadiiRom 2.2 with AmbasadiiCruel Kernel G97xF-v3.10.
There are a few custom kernels that have built-in magisk. You will have to check rom compatibility but believe they work on samsung stock based firmware/roms, AmbasadiRomi is based on stock firmware.
- Cruel Kernel
- ThundeRStormS kernel
If you like I can provide a step-by-step, but you will lose all data as it will require flashing stock unpatched firmware, unpatched twrp in odin then custom rom (optional - depending on if the custom kernel does work on stock firmware) & custom kernel.
Click to expand...
Click to collapse
I just read some info on the links you provided and i think i can figure it out. if i have any trouble then ill let you know. Dont worry about a step by step for now unless I have any trouble. Thanks!

Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help

pjc21 said:
Here is a bit of a step-by-step for Samsung s10 Exynos Model:SM-G973F
Info below is based on using December Security patch: 2020-12-01 firmware G973FXXS9DTK9 (Android 10) and Ambasadii Rom
NOTICE: The easiest and fastest way would probably be flashing kernel with stock firmware/rom. I have only done custom (but stock based) roms with kernel so am assuming the steps (5a.) for stock firmware/rom, you may want to post in chosen kernel thread to confirm if those steps are correct.
- both kernels I mentioned say they are compatibly with stock roms & AmbasadiiCruel Kernel is based on Cruel Kernel so I assume that would also work on stock rom.
This assumes you have already unlocked your bootloader, if not check this Recovery thread under Instructions: Odin (windows) - steps 1-6 for how to unlock bootloader.
1. Download all files needed to pc.
- Current latest firmware G973FXXS9DTK9, I use frija tool as downloading from samfirmware.com is very slow.
Enter Model, CSC, check the auto box & click check update and download.
Once complete unzip with 7Zip or preferred zip tool.
- In Recovery thread download latest twrp for device, is this case for S10 G973F latest twrp is - twrp-3.5.0_9-1-beyond1lte.img.tar
Under Instructions: Odin (windows) download
- Odin v3.14.1
- avb disabled vbmeta.tar
- click link to multidisabler-samsung-2.* and download latest version from there, currently multidisabler-samsung-3.1.zip
If sticking with stock and custom kernel
- easiest one looks like it would be Cruel kernel or AmbasadiiCruel kernel.
- check kernel thread of choice for compatibility with stock firmware and specific install instructions.
For custom rom in this example for Ambasadii rom
- Download files from Ambasadii rom site
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip (rom does include previous kernel 3.9 but this one is updated to latest magisk 21.2)
Bootlogo patcher - this will get rid of the warning about bootloader being unlocked when booting phone. (optional)
TWRP_Bootlogo_patcher.zip
Copy the below files to phones external SDCard
- multidisabler-samsung-3.1.zip
- TWRP_Bootlogo_patcher.zip (optional)
- chosen kernel zip - if sticking with stock
Custom Rom files
- ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip
- mods_DTJA-v1.3.4.zip
- magisk_safetynet_fix.zip
- AmbasadiiCruel-G97xF-v3.10.zip
2. Flashing stock firmware - Odin
- Open Odin on pc
- Turn off the phone
- Use vol down + bixby, then connect usb cable to phone from pc to start the phone in download mode, press vol up to confirm and go to download mode.
- In Odin under log you should see added, I also like to turn off auto reboot under the options tab and do manual reboot once complete but that's up to you.
- Add BL, AP, CP & CSC from the unzipped firmware downloaded in step 1. The AP & CSC can take a little time as they are larger files.
- Once all files added click start and wait until complete, you should see SUCCESS in the top left area once done.
- If you turned off auto-reboot then unplug usb and do manual reboot by pressing vol down + power for 7 seconds, else phone should reboot automatically then unplug.
3. Once phone boots up
- complete setup and connect to Wi-Fi or data
- skip adding Google & Samsung accounts.
- enable developer settings & check OEM unlock is on.
- turn off the phone.
4. Flashing TWRP Recovery - Odin
- In the Recovery thread under Instructions: Odin (windows) continue on from step 8 including formatting data and flashing multidisabler zip which you copied to SDCard.
- in twrp go back to wipe and select advanced and wipe data, cache & dalvik-cache
5a. If sticking with stock & custom kernel - Read NOTICE at top of post
Assumed Steps
- Still in twrp recovery go back to main menu
- select install and flash kernel zip, then TWRP_Bootlogo_patcher.zip
- Not sure if magisk_safetynet_fix is needed or works on stock, would need to confirm in Ambasadii thread.
- go back to main menu and select reboot & system
- give the phone a few minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
OR
5b. If flashing Custom Rom & Kernel - steps below for Ambasadii Rom
- Still in twrp recovery go back to main menu
- select install and flash ROM.G97xF.XXS9DTK9-v2.2.by.ambasadii.zip, choose options in aroma - once the install is complete exit back to twrp recovery
- select and flash mods_DTJA-v1.3.4.zip, then magisk_safetynet_fix.zip, then AmbasadiiCruel-G97xF-v3.10.zip, then TWRP_Bootlogo_patcher.zip
- once you have flashed all files go back to main menu and select reboot & system
- give the phone about 8 minutes to start, and then complete setup including adding your accounts.
- once setup is complete open magisk and it will run additional setup, and then phone will reboot
- done
6. If you went with Ambasadii Rom
- you will then notice status bar icons are pushed to the right behind the camera
- open rom control, grant superuser rights
- select status bar/options and play around with notch adjustments and positions
- can be a little confusing to start but play around and you'll get the hang of it.
Hope this info helps, let me know if you need any clarification/detail to any of the steps
Also no need for reward, happy to help
Click to expand...
Click to collapse
Hey There, Been busy lately and I haven't gotten around to trying any of these methods until today. Today I attempted the stockrom+CruelKernel. I am having a strange problem. I am acquiring root but as a read-only. I can not make any changes to system files, I can only view them. Can you tell me if you are able to modify or add to the system directory? Let me know. I know your phone is running custom rom + custom kernel, so I just might have to do that if that is the only fix. I have tried several things and read all of the threads but can not find anyone else that is experiencing this issue / I can not find a fix. I'm about to try the custom rom (stock based) + custom kernel to see if that works. If you can tell me if you have access to read/write system files then let me know so I know if this is even possible. Thanks.

I have found out that I can modify system files through twrp recovery, but when I boot into the main operating system then I have root but as read-only.

Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.

pjc21 said:
Hey, sorry for late reply - ever since xda updated it's not sending me emails when I get a notification.
As for the system directory being read-only, I believe this is normal even with root. Root just gives access to the /root dir that you would not normally have without it.
- my system dir permissions by default are 755/rwxr-xr-x
After a bit of searching looks like there are a few ways to change permissions
- twrp, can mount system as r,w - but as you said this reverts on reboot
- adb shell, and chmod permissions, same why you do with linux
- in android using either root explorer or x-plore, haven't tried root explorer as it is a paid app but did test with x-plore and working fine.
check this vid on changing the root access to superuser+mount writable which allows for changes in read-only folders and how to set permissions for files/folders.
I not sure if changing permissions on the system folder itself is safe or would cause any issues, I just created a folder within system and set permissions to 644 reclusive, created some files and rebooted - created folders/files and modified permissions remained fine after reboot.
If you need write permissions in system to install apps as system/app you may find this magisk module useful, it's called App Systemizer which allows you to use apps as system apps systemlessly. Just search in magisk modules.
Hope this helps.
Click to expand...
Click to collapse
Cool, I'll give your suggestions a try. I'm a fan of ES File Explorer. They have a root explorer built in their app and previously I had a S8 Exynos and a S9 Exynos and that app worked for those phones but with this S10 the switch is grayed out and no other app is working for me either. On my older S8 Exynos and S9 Exynos I rooted with stock-rom + stock-kernel and just needed TWRP+Magisk and I always was able to modify or add/delete system files with ES file explorer. I guess Samsung is getting more and more strict on allowing this by making us hop through more hoops in order to do so. So far I only have ready only system files on the S10 Exynos which is new to me because the S8 and S9 always allowed modifying system files in the past but I will try your methods you suggested. Worst case I'll attempt the custom-rom + custom-kernel and see if that works. Right now I have stock-rom+custom-kernel. I was able to make changes in the system files in TWRP but hopefully your method will allow me to edit system files without having to switch to TWRP every time I want to change something. I will keep you updated.
On a side note I just rooted a Samsung S20 Exynos and turns out that the system files are read only everywhere whether in TWRP or not, so Samsung keeps making things more difficult on us all. I currently have no way of modifying system files on the S20 no matter what I try but that phone is still much newer so I will give the magicians more time before I look into the forums more for that phone. Right now if I can get the S10 Exynos then I'll be happy.
I'll let you know how things progress. If I get what I need done with this S10 then I am happy to give you a donation for your help in this matter. I would not have gotten this far without your help. Previously the S8 and S9 days were so much easier and people had youtube videos galore that described how to root. The process was easy and everything was unlocked as read write back in the S8 and S9 days.

Yeah I use to use ES on android 6-8 then moved of to solid explorer, very similar ui to ES and also has root explorer but unfortunately it does not work to change permissions on s10 android 10 (bloody samsung/google). So far the only free one I have found is x-plore to be able to do this now. Looks like google is locking down android even more now with android 11