Related
These are the problems. I did a clean flash and cleared the cache partition, and did a factory reset.
1. No notifications appear at all. Even when I have incoming mail and so on, no new notifications appear in the main bar. I only know things are happening when I check individual apps.
2. I have no settings tiles at all in the pull down quick settings. How do I add to this?
3. The default browser cannot be used. When I click on the icon, it opens to a blank screen and closes within half a second. It never stays open.
4. I can't boot into recovery at all. I've installed clockworkmod via Rom manager, but I cannot boot into it, nor can I use the volume up+home+power combo to reach it.
5. The home button doesn't respond at all.
Can anyone help?
Try booting into download mode and flash a stock rom via odin.
1) take titanium backup of the apps
2) copy internal SD data to PC
3) download KK kernel depending on what recovery you want i.e bauner kernel for cm/kitkat for cwm recovery and raw kernel for twrp.
4) download Odin format kernel (.tar) from bauners kernel thread (its the kernel for touchwiz jb) and keep it on PC.
3) download a different ROM and transfer with the desired kernel to SD card and external SD.
[ we are transferring it to both SD cards in case you are not able to boot to recovery and may have to flash a whole ROM to get it back ]
8) power off and put in download mode by pressing power+home+volume down
9) connect to computer and open Odin and select the tar file i.e the bauner jb kernel in PDA and flash, it will show kernel and successful.
10) once you see the galaxy note logo with yellow triangle remove the battery and don't let the device boot into ROM.
11) put the battery back and boot the device into recovery by power+home+ volume up. if it doesn't boot into recovery then try again.
12) once you are in recovery flash the KK kernel.
13) do factory data reset, wipe cache, dalvik cache and format system.
14) flash a ROM other than PA and gapps if required.
15) reboot
16) use triangle away app to get rid of the flash counter and triangle
these are the steps I followed and was able to successfully flash ROM without losing any data.
follow only if you know what you are doing. I am not responsible if you lose data or mess up your device.
Hope it helps
thank you very much
REVENGE SOLVES EVERYTHING
tysonraylee said:
1) take titanium backup of the apps
2) copy internal SD data to PC
3) download KK kernel depending on what recovery you want i.e bauner kernel for cm/kitkat for cwm recovery and raw kernel for twrp.
4) download Odin format kernel (.tar) from bauners kernel thread (its the kernel for touchwiz jb) and keep it on PC.
3) download a different ROM and transfer with the desired kernel to SD card and external SD.
[ we are transferring it to both SD cards in case you are not able to boot to recovery and may have to flash a whole ROM to get it back ]
8) power off and put in download mode by pressing power+home+volume down
9) connect to computer and open Odin and select the tar file i.e the bauner jb kernel in PDA and flash, it will show kernel and successful.
10) once you see the galaxy note logo with yellow triangle remove the battery and don't let the device boot into ROM.
11) put the battery back and boot the device into recovery by power+home+ volume up. if it doesn't boot into recovery then try again.
12) once you are in recovery flash the KK kernel.
13) do factory data reset, wipe cache, dalvik cache and format system.
14) flash a ROM other than PA and gapps if required.
15) reboot
16) use triangle away app to get rid of the flash counter and triangle
these are the steps I followed and was able to successfully flash ROM without losing any data.
follow only if you know what you are doing. I am not responsible if you lose data or mess up your device.
Hope it helps
thank you very much
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
can i use this method too if i had problem with storage can't detected after flashing KK ROM??
Hi,
I couldn't find any information about so I thought i'd share. I wanted Nougat with encryption and root! Finally managed it, probably didn't need all the steps but this is what worked for me after much trial and error.
You can transfer the zips to a SD card beforehand or just use adb sideload within TWRP.
You will have to go to developer options and enable OEM Modifications.
1. Get all the files needed
Magisk-v16.0.zip from XDA Dev Magisk
no-verity-keep-encrypt-6.0.zip This is my own file with the encryption script commented out. I had to open it and edit from the archive and NOT create a new zip as I got verify errors from TWRP
P580UEU1BQK1_P580XAR1BQK1_XAR.zip which I obtained from sam mobile
ODIN
2. Flash Nougat
AP = AP_P580UEU1BQK1_CL12479655_QB15699972_REV00_user_low_ship_meta.tar.md5
BL = BL_P580UEU1BQK1_CL12479655_QB15699972_REV00_user_low_ship.tar.md5
CSC = CSC_XAR_P580XAR1BQK1_CL12479655_QB15699972_REV00_user_low_ship.tar.md5 OR HOME_CSC_XAR_P580XAR1BQK1_CL12479655_QB15699972_REV00_user_low_ship.tar.md5
Let it boot the device.
EDIT
I flashed my phone after but decided not to flash the DM Verity; it is a Samsung A3 2017 so should be the same here. I basically flashed TWRP, then formatted Data, flashed Magisk and followed step 5 below.
3. Flash TWRP Recovery & DM Verity
Boot into download mode by holding down power + volume down + home
Press volume up
In ODIN put TWRP into the AP box and flash - remember to disable auto reboot
Press the download mode key combination and quickly press volume up when screen blacks while holding down the buttons
DO NOT SWIPE TO MAKE MODIFICATIONS
Format DATA
Flash the no verity zip file
Reboot
4. Magisk 16
Reboot to recovery DO NOT SWIPE TO MAKE MODIFICATIONS
Format DATA this might not be needed but I can't confirm
Flash the magisk zip
Format DATA doubt it is needed but this is what I did
Reboot
5. Enable Encrypt and Update Magisk
Encryption will be off, under security it will say Encrypt Device
Open Magisk App
Tick preserve encryption and untick preserve dm-verity
Update Magisk
Install and select direct Install
Reboot and Encryption should be enabled
Hope this helps! Good luck
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?
How to Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery (Eg.. TWRP)
This method will work with most of the latest Samsung devices running Android 9/10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q).
WARNINGS: I am not responsible for any damage made. Your device warranty will be void. Do it at your own risk.
Warning: Before Installing Magisk
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe. Backup before continue.
You have to have your bootloader unlocked before following the instructions
REQUIREMENTS: (Basic knowledge about android rooting.)
Stock Firmware
Odin v3.14.1
Magisk Manager (You can find in Downloads section of Magisk Thread, I used Magisk Manager v7.5.1)
STEP 1 Unlocking Bootloader (This may need to Wipe your Data/Factory Reset.)
Enable Developer Mode on the Galaxy Note 9
To Enable Developer Mode Open Settings option.
Under Settings option, select About phone, then choose Software Information.
Scroll down the screen and tap Build number several times until you see a message that says "Developer mode has been enabled".
Tap on the Back button and you will see the Developer options menu under Settings, and select Developer options.
Toggle the OEM Unlock option on
Then tap on the Turn On button
STEP 2 Patching and Flashing (This may need to Wipe your Data/Factory Reset.)
Download the firmware for your device.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Install the latest Magisk Manager
In Magisk Manager: Tap Install → Install → Select and Patch a File and select the AP tar file.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files. (I have copied with MTP)
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files (I have used CSC instead of HOME_CSC). (Never flash only an AP file, as Odin can shrink your /data file-system if you do). Important: Uncheck “Auto Reboot” in Odin Options!
Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
STEP 3 Wipe data/factory reset (This may need to Wipe your Data/Factory Reset. : D)
We now want to boot into the stock recovery to factory reset our device. Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the Note 9 it is Power + Bixby + Volume Up). Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen. (I had to release power button when Note 9 logo appeared).
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system. (Just select Select Reboot system now)
The device will automatically reboot for the first time it boots. This is completely normal and done by design.
After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
You shall see Magisk Manager in your app drawer; if not, manually install the Magisk Manager APK and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
How to Root Note 9 with Magisk on Android 10 (Q) with Custom Recovery (Eg.. TWRP)
This method will work with most of the latest Samsung devices running Android 10. (Tested and Working on Galaxy Note 9 (Exynos) with Android 10 Q).
WARNINGS: I am not responsible for any damage made. Your device warranty will be void. Do it at your own risk.
Warning: Before Installing Rooting your device
Rooting your device WILL trip KNOX
Rooting your device for the first time may REQUIRES a full data wipe. Backup before continue.
You have to have your bootloader unlocked before following the instructions
REQUIREMENTS: (Basic knowledge about android rooting.)
Stock Firmware
Odin v3.14.1
TWRP For Android 10
Magisk Latest Stable ZIP or (I used Magisk Canary from Github)
DM-Verity, Force Encryption, and Disc Quota Disabler (I used Dm-Verity & ForceEncrypt Disabler v02.02.2020)
STEP 1 Unlocking Bootloader (This may need to Wipe your Data/Factory Reset.)
Enable Developer Mode on the Galaxy Note 9
To Enable Developer Mode Open Settings option.
Under Settings option, select About phone, then choose Software Information.
Scroll down the screen and tap Build number several times until you see a message that says "Developer mode has been enabled".
Tap on the Back button and you will see the Developer options menu under Settings, and select Developer options.
Toggle the OEM Unlock option on
Then tap on the Turn On button
STEP 2 Flashing Stock Firmware (This may need to Wipe your Data/Factory Reset.)
Reboot to download mode
To Boot into the Download Mode Power Off your device
Make sure you have a USB Type-C cable connected to your PC
Then press and hold the Volume Down and Bixby buttons at the same time
Hold these two buttons down and you insert the USB Type-C cable
Continue holding these two buttons down until you are greeted with the splash screen for Download Mode
Press the Volume Up button to bypass the splash screen and enter the Odin Mode
Now open Odin on your PC, Flash your firmware AP, BL, CP and CSC files. Important: Check “Auto Reboot” in Odin Options and keep your device in your hand and eye on Odin.
After you get flash got PASS! in Odin your device will restart and you will see blue screen saying you device is updating (or similar statement) for 2-5 seconds and then your device will restart again. (Next Step is Very Importent).
As soon as the screen turns off for second restart you have to press Power + Bixby + Volume Up to boot into the stock recovery. (I had to release power button when Note 9 logo appeared).
Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Power Off and remove your USB Type-C cable from your device.
STEP 3 Flashing TWRP(This may need to Wipe your Data/Factory Reset.)
Now your device is in power off state you have to boot into the Download Mode to flash TWRP. (You can get info on STEP 2 to boot into Download Mode)
Now open/reset Odin on your PC and go to the Odin option uncheck “Auto Reboot”
Click on the AP button to select TWRP file (Eg: twrp-3.3.1-r3.7-q-crownlte.tar) and click Start. (Next Step is Very Importent).
After you get flash got PASS! in Odin Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key to boot to recovery (e.g. on the Note 9 it is Power + Bixby + Volume Up). Since we want to boot into TWRP recovery, continue pressing the volume up button until you see the TWRP recovery screen. (I had to release power button when Note 9 logo appeared).
STEP 4 Rooting You Device (This may need to Wipe your Data/Factory Reset.)
In TWRP you have to swipe to allow the modification
Now format your data Tap Wipe->Format Data and type yes to continue. (You can Skip step 2 and 3)
No go back to TWRP home screen by pressing back button multiple times and tap Reboot and then click Recovery. (Your device will restart to TWRP recovery mode).
Insert your USB Type-C cable to connect your device to PC.
You will get your device MPT drive in my computer, Copy Magisk Canary zip file and Dm-Verity & ForceEncrypt Disabler v02.02.2020 zip file to your device.
Now you have to flash Magisk Canary in TWRP click Install and select Magisk Canary zip and start flashing. Then flash ForceEncrypt Disabler in TWRP. (If you get the mount error whioe installing ForceEncrypt Disabler then just ignore it and move to next step).
Click reboot to boot your system.
Done! Enjoy
Biometrics and fingerprint work after root?
Trimis de pe al meu SM-N960F folosind Tapatalk
Detonatte said:
Biometrics and fingerprint work after root?
Trimis de pe al meu SM-N960F folosind Tapatalk
Click to expand...
Click to collapse
Yes it works
Guessing this is non snapdragon use only. I don't see any models this works with but root isn't possible with North American note9 as far as I know. The boot loader is locked down.
I don't understand...where, how flash magisk_patched.tar ????
Please edit title to say this is Exynos only
thanks ..
secure folder still work after root?
Detonatte said:
I don't understand...where, how flash magisk_patched.tar ????
Click to expand...
Click to collapse
Follow STEP 2 Patching and Flashing (This may need to Wipe your Data/Factory Reset.)
Download the firmware for your device from sammobile or via Frija
Unzip the downloaded firmware on your PC and copy the AP tar file to your mobile device. (It is normally named as AP_[device_model_sw_ver].tar.md5).
Install the latest Magisk Manager on you mobile device.
In Magisk Manager: Tap Install → Install → Select and Patch a File and select the AP tar file that you have copied from your pc.
Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar.
Copy the patched magisk_patched.tar file to your PC with adb pull /sdcard/Download/magisk_patched.tar. (Do not use MTP as it is reported to corrupt files. (I have copied with MTP)).
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files (I have used CSC instead of HOME_CSC). (Never flash only an AP file, as Odin can shrink your /data file-system if you do). Important: Uncheck “Auto Reboot” in Odin Options!
macgyver40 said:
Guessing this is non snapdragon use only. I don't see any models this works with but root isn't possible with North American note9 as far as I know. The boot loader is locked down.
Click to expand...
Click to collapse
Yes this is only for Exynos version, before posting this tutorials I don't have info about this.
TokedUp said:
Please edit title to say this is Exynos only
Click to expand...
Click to collapse
Done.
moaz1988 said:
thanks ..
secure folder still work after root?
Click to expand...
Click to collapse
Currently I am not using this System-as-root method to root my device because working version of Dm-Verity & ForceEncrypt Disabler is released so I am using TWRP method to root my device so I can't test secure folder on this rooting method. Now my device is rooted with Magisk via TWRP and secure folder is working without any issue so I think it will work with this method too.
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Detonatte said:
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Click to expand...
Click to collapse
Glad to know it works for you.
And SecureFolder work perfectly!
Trimis de pe al meu SM-N960F folosind Tapatalk
Hello
Thanks to the authors of this tutorial, and others on XDA, I completed a detailed procedure to Root the Galaxy Note 9 SM-N960F under Android 10 with the Recovery Custom TWRP which allows the backup and restoration of all partitions.
This procedure may seem long because it is very detailed because there are very important points not to miss so that the partitions are not locked by Android 10.
I hope the French / English translation is good because I am very bad in English
cordially
https://forum.xda-developers.com/showpost.php?p=81695605&postcount=324
Montero try backup and restore with TWRP? Work??
Trimis de pe al meu SM-N960F folosind Tapatalk
Yes work very fine for All partitions
Detonatte said:
Zer0De8th work perfect root with: twrp-3.3.1-r3.7-q-crownlte.tar, Magisk-v20.3(20300).zip and Disable_Dm-Verity_ForceEncrypt_02.02.2020.zip
Thx very much man!!!
Click to expand...
Click to collapse
Me too....
Restoring my data using Titanium Backup..
Samsung acc working
How to enable hidden menu since no more CSC folder (feature.xml)?
inamie said:
Me too....
Restoring my data using Titanium Backup..
Samsung acc working
How to enable hidden menu since no more CSC folder (feature.xml)?
Click to expand...
Click to collapse
Here is the new location for CSC feature.xml "/odm/etc/omc/XXX- your country code/conf/cscfeature.xml".
You have to Decode / Encode CSC files use OmcTextDecoder .
Many of the old CSC features don't work on Samsung Android Q
Zer0De8th said:
Here is the new location for CSC feature.xml "/odm/etc/omc/XXX- your country code/conf/cscfeature.xml".
You have to Decode / Encode CSC files use OmcTextDecoder .
Many of the old CSC features don't work on Samsung Android Q
Click to expand...
Click to collapse
Thanks,
Any idea how to set Magisk Manager.
New version 7.5.2 no option to hide selected application..
cant use certain apps like shopee pay and ewallet on rooted device.
Previous version 7.5.1 no problem.
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