Database Develop

[NOOB-Friendly] starting flashing and customizing on most Samsung Devices

So i will be making a for rooting and flashing tutorial for beginners!
So i will need to tell you a few things first.
Installing ROM's is not illegal though rooting is illegal in the following country's:
North Korea
Malaysia
Singapore
South Korea
SO IF YOU DONT LIVE THEIR THEN STOP COMPLAINING ABOUT ROOTING IS HIGHLY ILLEGAL
And if your running total stock android then i will make a short tutorial on how to install your first ROM
This method is nearly the same for switching ROM's, though after the tutorial i will explain the only thing thats different.
Also this works for all ROM's.
NOTES:
I am not gulity of anything that happens to your device
Your warranty will be void
You will lose all your Apps, except photos and files
Here is what you will need:
A version of CWM to your specific phone (Please notice depending on ROM's android version, you will need a KK-compatible for a Kitkat ROM or a ICS compatible for a Ice cream Sandwich ROM etc.)
Download: https://www.clockworkmod.com/rommanager
gApps
Download: http://forum.xda-developers.com/android/software/gapps-consolidated-gapps-thread-t3064693
SuperSU
Download: http://forum.xda-developers.com/showthread.php?t=1538053
I will be using CyanogenMod12.1 for this tutorial!
Download: http://www.cyanogenmod.org/
Odin 3.07 not higher.
Download: http://www.android.gs/download-odin-3-07/
A working Computer
USB cable for your phone.
Your phone needs to be charged 100% before doing this.
So lets begin!
1. Start by plugging your phone to your PC
2. Start ODIN
3. Hit the PDA button and find your custom recovery and hit OK.
4. Make sure you have your ROM, gApps and SuperSU on your phone.
5. Turn off your phone and hold HOME + POWER + Volume down
6. When a screen appears press Volume up
7. Press start on ODIN and wait till your phone reboots
8. Now power it off and hold HOME + POWER + Volume Up till your recovery comes up
9. Now factory reset and go to Mounts and Storage and format /system
10. Go to advanced tab under you main menu on the recovery
11. Press Wipe dalvik cache
12. At the main menu, go to Install zip now choose either from SD card or Internal Storage Device
(Depending on location)
13. find your ROM and press it
14. After a while when its done, go to install zip and find where you placed gApps and flash it
15. Now factory reset and go to advanced tab and wipe dalvik cache
16. Reboot your device, and wait till you see the Welcome screen
17. Set up your device.
18. Power off you phone and hold HOME + POWER + Volume Up
19. Now install zip and find SuperSU and flash it
20. Reboot your phone and your done!
21. ENJOY!
If done successfully, you should now learned the basics of flashing, though you dont need to install a new recovery everytime,
Though you might need it if you gonna change android version if the ROM dont have a recovery.
Also fo beginners, gApps is for play store and google apps generally, and the SuperSU is for rooting.
But if you wanna become a pro, start switching ROM often.
If you want to know a pro tip, before installing a new ROM, always format /system and factory reset.
As it makes the success rate 99.99%, but if your phone is stuck at the boot screen, then its because you haven't format /system
and factory reset, or you forgot to factory reset after the install of gApps.
If you phone keeps booting into your recovery instead of your ROM, then you have installed a new recovery over the ROM's
recovery, thats not compatible with your'e ROM or its only compatible with another Android-version
If you encounter a problem please comment your phone model and your ROM and Recovery and your problem
I will help as much as possible
I searched around before uploading this, if their is one earlier made than me please send a email to
[email protected] and i will take it down ASAP

Please post your thread in the appropriate forum next time. This thread is closed.

ROOTING a Samsung Tab Active2 ( SM-T397U )

Im trying to Root my Samsung Tab Active2 ( SM-T397U ) but im having problems finding the combination files and stock firmware, any chance someone can link me to them?
Thanks

I still need help.

check my post [RECOVERY][TWRP][Unofficial] Galaxy Tab Active 2 - TWRP 3.2.3-0 [Exynos]
There are links for TWRP recovery for SM-T397, including the use of SuperSu for root.

Shedaim said:
check my post [RECOVERY][TWRP][Unofficial] Galaxy Tab Active 2 - TWRP 3.2.3-0 [Exynos]
There are links for TWRP recovery for SM-T397, including the use of SuperSu for root.
Click to expand...
Click to collapse
is this for the SM-T395 or SM-T397U

EKNOZHF said:
Im trying to Root my Samsung Tab Active2 ( SM-T397U ) but im having problems finding the combination files and stock firmware, any chance someone can link me to them?
Thanks
Click to expand...
Click to collapse
I was able to root an SM-T397U running 8.1.0 using the recovery in the above thread (twrp-3.2.3-0-SM-T397-7.1.2.tar) even though that was for 7.1.2 and not 8.1.0 (assuming these versions are even related). The SuperSU flashing method led to a "Verification Failed" error, and at one point I was able to totally bootloop the device by doing a data wipe from TWRP (bad idea!). Make sure you have stock firmware on hand - I downloaded it from sammobile but it took friggin forever.
NOTE! I bricked the device at least once, and had to restore to stock via ODIN (this is the stock FW I used: https://www.sammobile.com/samsung/firmware/SM-T397U/ATT/download/T397UUES4BSF3/290259/). These instructions are purely at your own risk! Note that the above link contains the full firmware (bootloaders + system + recovery + etc). If you just need the stock recovery for whatever reason, message me (for some reason I can't attach it to the post).
What ultimately worked was:
1. Factory wipe the tablet from inside Android
2. Put Magisk-v19.3.zip on your sdcard (latest stable as of this writing; this is what I tested)
3. Enable Developer Options from inside Android
4. Enable "OEM Unlock" under Developer Options, and do a wipe if it forces you
5. Power down
6. Hold Home + Volume Down + Power until you get to the bootloader
7. Press VolUp (I think) to continue into the bootloader
8. Open Odin3, click "AP", select twrp-3.2.3-0-SM-T397-7.1.2.tar (leave the other boxes blank). Odin might give you an option to NOT reboot after flashing. If you find it, (un?)check the box that prevents reboot after flashing (not sure if matters). Then, do the flash. It only takes a few seconds.
9. Power down device (do not let it boot into Android, but that may not matter)
10. Hold Home + Volume Up + Power until the Samsung Galaxy logo appears, then let go. This boots you into TWRP. The boot into TWRP takes a little over a minute. Be patient.
11. Inside TWRP, ignore any Wipe-related options. It'll ask you to swipe to allow modifications (do that). Then, click on INSTALL (or is it "FLASH"?), then scroll down to "external_sdcard", then find Magisk-v19.3.zip and click on it.
12. Let the Magisk installer do its thing
13. Reboot from TWRP (don't wipe anything, and click DO NOT INSTALL when prompted for the TWRP app). It may take a minute or so to reboot
14. Let the device boot to Android. It may take like, 3 minutes.
15. Uninstall the Magisk Manager app that is now present on the device (it may crash, but this is just a placeholder anyway)
16. Install the *actual* most recent (stable?) Magisk Manager app. I used MagiskManager-v7.3.4.apk.
17. Open Magisk Manager. It may tell you there's an additional download that's needed. Let it do that, then let the device reboot.
18. You should now be good to go, but you might need to disable the annoying "device compromised" nag screens from some mcafee samsung security junk that will pop up sometimes.
Again, this is all at your own risk. Good luck!
-evilwombat

hi
i may be not in the correct topic
can your sm-t397 make phone calls?

How to | Galaxy S9 (SM-G960F & F/DS) Root Android PIE

Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS),
i am not responsible if anything goes wrong. You are still the one who tryed to flash the files. Even tough this should work as it worked for me and some friends.
Hello XDA
This is my first post (sorry if one already exists)
Today i am going to tell you how to root the Galaxy S9 International on android 9 Pie on stock touchwiz rom.
First of all download all these files;
Prince comsy odin: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Team win recovery https://forum.xda-developers.com/ga...cross-device-development/twrp-exynos-t3763464
ElementalX Kernel https://elementalx.org/devices/samsung-galaxy-s9/
No verity encrypt: https://androidfilehost.com/?fid=962187416754474353
Magisk 18.0 https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now for the root
First you need to unlock OEM, you can do this in developer options,
If there is no developer options you need to enable this
you can do this in: Settings>About Phone > software information > click 5 times on build number.
When you unlock OEM everything on your phone gets wiped so make a backup!!
When the wiping is complete, turn off your phone and go to download mode (Vol down + Bixby + Power)
Then connect the phone to your pc and start odin
In odin go to options, and disable f.reset and auto reboot.
Then press the AP button and select the TWRP image you downloaded.
When TWRP is flashed, force reboot your phone (Vol down+ Power) when it is powered off quickly press Vol Up + Bixby + Power to get into recovery
Swipe to allow modifications. And format /data
Then reboot into recovery.
When rebooted mount USB Storage and connect the phone to the PC
Then you can click&Drag the other files (elemental, Magisk, No verity)
When the files are on the phone, go to install and search for the files you just put on the phone.
Install in this order:
Flash No-Verity-Encrypt
Then flash the custom kernel (ElementalX)
And as last flash Magisk.
When you did this, you want to Factory reset, Wipe cache and Dalvik.
Then you can reboot the phone, and install it.
(It is possible that you stay at the boot logo for a long time (Not the galaxy s9 one but the next one) What you need to do then is let it boot for 5 minutes, then force reboot (vol down+Power) and then the phone boots fine)
Again, just to make sure check if OEM is still unlocked (sometimes this get locked again)
Please note that when you do this, you lose secure folder and other functions, also is the knox tripped (0x1)
But the Fingerprint, Irisscanner and samsung account works.
SOMETIMES IT IS NEEDED TO INSTALL THE MAGISK MANAGER MANUALLY, YOU CAN JUST DOWNLOAD THE FILE FROM THE LINK IN THIS POST
Hope this helps.
If you do have any questions, please do the following first;
Note any errors that odin or your phone gives you. I want to help you, but i do need to know what is going wrong.
(Sorry for my bad english)

reserved

So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?

sarius02 said:
So you won't need RMM-state_bypass on pie anymore?!? Seems hard to believe...
And why exactly you need to flash that custom kernel, which benefits does this bring with it?
Click to expand...
Click to collapse
If you dont use the custom kernel, you will get RMM error.
Iris scanner wont work, Fingerprint wont work, Samsung account wont work. When you reboot the phone you get a little "Bootloop" at the lockscreen (Screen flashes and is unusable and your pattern isn't saved)
I dont know what else breaks because i cant even get past the lockscreen with stock kernel
(Also you get better performace and battery life)
Hope this helps

work it with s9+?
Sorry for my English...

Yes, but you want to use tgpkernel then otherwise it will not work (problems described abovel
https://www.androidfilehost.com/?w=files&flid=288240

Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?

effry said:
Last samsung phone i rooted was the note 3, and i remember that doing that "tripped" knox 0x1 and this basically voided the warranty. It's the same with S9? is there some non-reversible change that happens to the phone when rooting?
Click to expand...
Click to collapse
Yes, the knox will still trip (0x1).
In europe, when you can show that the root is not the cause of the problem, they have to fix it under warranty.
Also there are some functions you will lose (forever)
Knox,
Samsung pass,
Samsung Pay,
S-Health(you can fix this one with a build.prop tweak)
Secure folder
If you plan to use one of these (exceptpt s-health) It is better not to root your phone (there are still external app's you can use if you plan to root your phone)

Is there a way to update the stock firmware when you have root? Or do i have to do all over again?

I have this lock screen flashing bootloop issue, what is the fix? I have tried factory restores but get the same results once I set a lock/passcode and reboot. Samsung Account and Bixby also do not work as you mentioned.

You can use TGPkernel then,
Some phones have this issue, some not.
I have seen that 3 friends of mine it worked, and also on 3 not, so this is a very weird issue
What was the fix with them is to install TGPkernel
@co9
The only way i know is to install a custom kernel,
Otherwise you have to download latest stock rom, and flash this using odin.
wich changes your recovery.img and boot.img, aswell as the kernel. so you have to flash this all over again

Thanks for the answer. I already have a custom kernel. So if i always want to have the latest Samsung firmware i have to flash it through odin and do the whole root procedure again?

I tried this method but now everytime I reboot the phone my bluetooth paired device are lost. They also get deleted if I turn ON and OFF the Airplane mode. Anyone else having the same issue ?

Is anyone else experiencing an issue where the password, pin, or pattern set before setting up fingerprint scanning acts like what was entered is incorrect, not allowing you to setup fingerprint scanning?
I've tried setting up fingerprint scanning on initial setup as well as skipping and trying after the phone has been setup but had no luck. What ever I set initially will not work when I'm prompted later on when trying to setup fingerprint scanning or tying to access other secure features. The phone just prompts to try again acting like I entered in the wrong password, pin, or pattern. I've even tested by setting up a REALLY simple password with no luck.
I have confirmed in the settings that Elemental is installed.
Edit: I did find this thread https://forum.xda-developers.com/galaxy-s9/help/root-galaxy-s9-exynos-9-0-android-pie-t3884267. I tried the no-verity-opt-encrypt-6.0.zip that was suggested in some posts but had no success. I've also tried the TGPKernel but had not change in the issue. I am able to setup fingerprint scanning on fresh firmware install but after installing TWRP and everything else the above issue happens.

Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0

menhammer said:
Install steps Magisk 18 for Samsung S8/S9 Android Pie 9
See lot of people have trouble, here are the steps to do, dont get confused keep it simpel nothing more
1 Flash the last pie build (sammobile.com) with Odin, restart mobile, let system install
2 Enable unlock OEM (settings->about phone->softare information-> tap a few times on build so developer options tab is in settings go there and enable oem unlock)
3 Flash TWRP (twrp.me/) with Odin and immediately after the flash hold bixby+volume up+ powerbutton to go to TWRP
4 In TWRP, swipe to allow modifications.
5 Go to Wipe - Format (yes). Press the back button all the way to home of TWRP
6 Reboot recovery
7 In TWRP, swipe to allow modifications, click on install button and flash dm-verity v1 and press the back button all the way to home of TWRP
8 Click on install button and flash magisk v18
9 Reboot system and let system (android 9) install enter pin, google account and so on...
10 Install magisk app
11 Open Magisk, if you see there is no root/magisk installed, no worry!! Just download Magisk from the Magisk app to the download folder on your phone, restart your phone adn go to TWRP and install Magisk again.
Done!
Used Software:
Odin3_v3.13.1
Twrp 3.2.3.2
no-verity-opt-encrypt-samsung-1.0
Magisk-v18.1
MagiskManager-v7.0.0
Click to expand...
Click to collapse
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.

Emre67511 said:
Don't root this phone without flashing a custom kernel or a modified stock kernel. It will drain battery and reduce the performance or even crash the system.
Look in the TWRP thread there it is explained why you shouldn't do it.
Click to expand...
Click to collapse
My personal experience is i have rooted using this method and have had no problems

Hi all,
I tried to flash twrp but never succed.
S9+ last firmware from samsun android 9 pie (update from smart switch)
Then option developper activated, no oem unlock menu found,
boot into download mode and there is written oem unlock desactivated so ok
with odin try to flash (ap, reboot freset unchecked)
then fails and message in red on the phone :
"only official released binaries are allowed to be flashed recovery"
History :
I was in galaxy project oreo, i wanted to upgrade with pie, but reboot cycle
so rescue with odin and original oreo firmware, then update to pie
thanks for help
regards

To get the oem unluck button visible.
After fresh install, go to time/date in settings, choose manual and set the date 1 mount prior (march will be februar)
Than go to software update, choose manual en click on dowload updates manually.
Restart your phone and the oem unlock button in developer options will be there
Cheers

thank's for answering,
Update done, reboot ok but still not oem options in developpers section

Root SM-M405F (Galaxy M40)

Read all the Instructions very carefully, as missing even a single steps cause bootloop.
1. Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Power off your device. Press Volume Up + Volume Down and plug in your device to a PC to boot into download mode
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, surprise surprise, it is actually not! Samsung introduced VaultKeeper in the system, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
2. 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
After installing Magisk, you can directly upgrade Magisk within Magisk Manager without an issue.
3. Flashing Magisk:
Download the firmware for SM-M405F
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: 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 tar file to your PC and boot your device to download mode.
Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
Magisk is now successfully flashed! But there are still several steps before you can properly use the device.
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 Power + Volume Up to boot to recovery partition. Just as mentioned in the previous section, since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select 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 Power + Volume Up. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
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 internet connection.
You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded 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.
Enjoy Root

Successfully rooted Galaxy M40
Thanks for the post. I have successfully rooted Galaxy M40 using magisk. Just one thing to add to the above post-- while copying patched ap from phone to pc use adb otherwise the flashing patched AP fails.

Ayan Chakraborty said:
Thanks for the post. I have successfully rooted Galaxy M40 using magisk. Just one thing to add to the above post-- while copying patched ap from phone to pc use adb otherwise the flashing patched AP fails.
Click to expand...
Click to collapse
I did not use Adb, it went smoothly for me. :good:

Enable 3CA for Rooted M40
Galaxy M40 uses LTE 2CA but the chipset supports 3CA. Can we enable it for Rooted M40?

Be careful doing this, since the latest Samsung firmware update in August it doesn't work anymore. You can root at first, but then every time you reboot the phone unroots... If you persist and do it again Samsung lock the phone for "security reasons" and you can't even reach the bootloader or recovery screens using the up / down buttons... Meaning you can't go back to stock firmware without taking your phone back to the store or sending for service, but of course you now no longer have warranty.

awsmanks said:
I did not use Adb, it went smoothly for me. :good:
Click to expand...
Click to collapse
This method will work for samsung a60 with his own firmware? Its the china better version of m40, i think i'll try this method

Rooted Successfully.
I had to flash twice since it did not boot into the stock recovery first time and messed with root I presume. second time it went perfectly and manually installed magisk manager. later magisk manager did some setups and rebooted my system.
Thanks Dev.
waiting for TWRP

rajeshca911 said:
Rooted Successfully.
I had to flash twice since it did not boot into the stock recovery first time and messed with root I presume. second time it went perfectly and manually installed magisk manager. later magisk manager did some setups and rebooted my system.
Thanks Dev.
waiting for TWRP
Click to expand...
Click to collapse
So this the new update it works?

Scorpio02 said:
This method will work for samsung a60 with his own firmware? Its the china better version of m40, i think i'll try this method
Click to expand...
Click to collapse
The A60 and the M40 are identical, it's not the "china better version" lol, it's just 90 USD more expensive because Chinese people have more money. It's literally identical down to the microchips inside.

Scorpio02 said:
So this the new update it works?
Click to expand...
Click to collapse
I think that I flashed on latest firmware AP_M405FDDU1ASF2_CL16060793_QB24248847_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS9.tar
Android Pie
Magisk 19.3
Magisk Manager 7.3.2
everything works perfectly except that annoying message on the boot screen
Here are my screenshots
View attachment 4807915
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4807917

I've uploaded the latest firmware file to Mega for anyone who doesn't want to wait 10 years for it to download from the snail-speed Samsung Firmware website:
https://mega.nz/#!T1sBka7B!iP8Ub8xbmO4ppa1CJg5vh4dWk_Vh-KjnPM6M6VjiqCc
Feel free to check the MD5 hashes, zero changes.

Theseusperse said:
Be careful doing this, since the latest Samsung firmware update in August it doesn't work anymore. You can root at first, but then every time you reboot the phone unroots... If you persist and do it again Samsung lock the phone for "security reasons" and you can't even reach the bootloader or recovery screens using the up / down buttons... Meaning you can't go back to stock firmware without taking your phone back to the store or sending for service, but of course you now no longer have warranty.
Click to expand...
Click to collapse
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware

rajeshca911 said:
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware
Click to expand...
Click to collapse
Yeah that was the same issue I was having, I'm using the Indian version of the firmware so I wonder if it just affects Indian models.
I did a lot of research and there's actually not just 5 international models but 7, some with a /DS on the end which appear to use different firmwares, and I wonder if that is the cause of the issue.
Anyway I found a temporary fix. Reset everything back to stock firmware, do the rooting as the guide shows on page 1, then ALWAYS reboot using root, either by installing or upgrading a new Magisk module, or updating your AdAway blacklist, or by using ADB Shell #Su... For some reason when you reboot like this it doesn't unroot the phone and everything stays fine. Also make sure you never ever press the "Okay continue" button that appears when the phone first starts and tells you the bootloader is unlocked, just wait a while and allow it to continue automatically.

Theseusperse said:
Yeah that was the same issue I was having, I'm using the Indian version of the firmware so I wonder if it just affects Indian models.
I did a lot of research and there's actually not just 5 international models but 7, some with a /DS on the end which appear to use different firmwares, and I wonder if that is the cause of the issue.
Anyway I found a temporary fix. Reset everything back to stock firmware, do the rooting as the guide shows on page 1, then ALWAYS reboot using root, either by installing or upgrading a new Magisk module, or updating your AdAway blacklist, or by using ADB Shell #Su... For some reason when you reboot like this it doesn't unroot the phone and everything stays fine. Also make sure you never ever press the "Okay continue" button that appears when the phone first starts and tells you the bootloader is unlocked, just wait a while and allow it to continue automatically.
Click to expand...
Click to collapse
Thanks Theseusperse, I will follow that. and can u suggest me easy way to port twrp? I tried carlive image kitchen however when i flashed it not only reboots into stock rom but also shrinked my internal space to 16 GB. To Revert this effect I had to flash stock rom again using Odin ( only odin other tools failed) . Please let me know if there is any safe porting Recovery

rajeshca911 said:
Thanks Theseusperse, I will follow that. and can u suggest me easy way to port twrp? I tried carlive image kitchen however when i flashed it not only reboots into stock rom but also shrinked my internal space to 16 GB. To Revert this effect I had to flash stock rom again using Odin ( only odin other tools failed) . Please let me know if there is any safe porting Recovery
Click to expand...
Click to collapse
There won't be any port of TWRP for a long time, Samsung has to release the source code for the phone first. Based on the Galaxy A series that was released in May this year, they just got their source code last week and the TWRP porting community literally kicked off in the past few days, so we'll probably have to wait some months. I'd estimate November sometime.
I'm excited for when it finally does happen though, I absolutely hate the stock Samsung software and want pure Google, even if it means a GSI rom.
Our phone is actually 100% identical to the Samsung Galaxy A60, so it's possible any TWRP ports made for that device would work, but so far the ones I've tried have all failed and resulted in the same effects you experienced.

SIZE=1]---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------[/SIZE]
[/COLOR]
Theseusperse said:
There won't be any port of TWRP for a long time, Samsung has to release the source code for the phone first. Based on the Galaxy A series that was released in May this year, they just got their source code last week and the TWRP porting community literally kicked off in the past few days, so we'll probably have to wait some months. I'd estimate November sometime.
I'm excited for when it finally does happen though, I absolutely hate the stock Samsung software and want pure Google, even if it means a GSI rom.
Our phone is actually 100% identical to the Samsung Galaxy A60, so it's possible any TWRP ports made for that device would work, but so far the ones I've tried have all failed and resulted in the same effects you experienced.
Click to expand...
Click to collapse
Im excited to hear that A60 recovery might work on M40 any ways me either hate to be on stock rom. I got habituated to the root and custom roms. Hope A60 source works for M40 . Please do update me if anything that kind of miracle happens. Thanks in advance Brother

rajeshca911 said:
I rooted my phone yesterday, today I rebooted my phone. and pfff it is gone.
this rooting procedure is not persistent
Waiting for a stable root method
now I am neither on ofw nor on rooted firmware
Click to expand...
Click to collapse
To prevent loosing magisk root after reboot. NEVER REBOOT NORMALLY but Reboot it via Magisk or Fully Power Off then Turn Power On.

redymedan said:
To prevent loosing magisk root after reboot. NEVER REBOOT NORMALLY but Reboot it via Magisk or Fully Power Off then Turn Power On.
Click to expand...
Click to collapse
Can i reflash again 0n same rom without loosing data ??
Sent from my SM-M405F using Tapatalk

rajeshca911 said:
Can i reflash again 0n same rom without loosing data ??
Sent from my SM-M405F using Tapatalk
Click to expand...
Click to collapse
No, never ever do this, it will shrink your data partition and there's no way to ever fix it, even with a total system restore or using manufacturer tools.

Theseusperse said:
No, never ever do this, it will shrink your data partition and there's no way to ever fix it, even with a total system restore or using manufacturer tools.
Click to expand...
Click to collapse
Too late, I already did that and it shrieked my devices storage to 16Gb first time and 32 gb on second flash. But It got fixed with Odin repartition. Dont worry It is fixable
Sent from my SM-M405F using Tapatalk

Rooting Note 9 Exynos android 10 ?

Anyone was able to Root Note 9 Exynos android 10 ?
i have tried dr.ketan as well as forcedecrypt/magisk 20.2 all combos and stuff ,it results in bootloop.
if anyone is able to root please write steps thanks!
EDIT :- METHOD TO ROOT N960FXXU4DSLB (ANDROID 10) for Exynos version.
i got so many briks today trying different methods to root android 10 latest update, please dont use TWRP recovery posted here which is latest v3.3.1 for Q that is the main issue, dont use dr.ketan root.zip either again bootloop.
SIMPLY FOLLOWS these steps:-
1. Flash android 10 DSLB with ODIN with CSC (Not home_CSC again bootloop).
2. Now it will start the device,do the normal setup.
WAIT UNTIL SIM CARD MANAGER popups (if this popups we have OEM Unlocking option appear, as we have already enabled that before), or you can manually go there and see you should get service provider signels.
and then goto the settings > about > software > tap 7 times build version, then goto developer options, OEM should be enabled itself and then ebale usb debugging.
3. Switch of phone,goto download mode (BIXBY + VOL DOWN + USB Cable plugged in)
4. use odin 3.14 and flash geiti's Twrp-3.2.3-0-crownlte.tar
5. boot to TWRP > allow modifications (important) > Wipe > format data > yes and then boot to recovery again.
6. now transfer the files to internal storage or if you have microsd u can skip this.
files - magisk-20.2.zip , RMM-State_Bypass_Mesa_v2.zip , No-Verity-Opt-Encrypt-6.0.zip.
7. flash RMM-State_Bypass_Mesa_v2.zip
8. flash No-Verity-Opt-Encrypt-6.0.zip
9. flash magisk-20.2.zip
10. flash again RMM-State_Bypass_Mesa_v2.zip.
11. reboot system, it will boot if not it will shut down and reboot itself, resetup again and you are rooted now.

Magisk 20.2 bug. Try with Magisk 20.1

i fixed it, i even ripped all device today when here was only download mode saying goto smartswitch nothing was working, follow steps above you are good to go!

Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?

XGamer404 said:
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
Click to expand...
Click to collapse
after flashing twrp > format data and reboot to recovery
try flashing it in order
https://www43.zippyshare.com/v/8NH3aUn0/file.html
https://www43.zippyshare.com/v/IdZPt02e/file.html
https://www43.zippyshare.com/v/hiKinhVp/file.html

BytesReverser said:
A
1. Flash android 10 DSLB with ODIN with CSC (Not home_CSC again bootloop).
2. Now it will start the device,do the normal setup.
WAIT UNTIL SIM CARD MANAGER popups (if this popups we have OEM Unlocking option appear, as we have already enabled that before), or you can manually go there and see you should get service provider signels.
and then goto the settings > about > software > tap 7 times build version, then goto developer options, OEM should be enabled itself and then ebale usb debugging.
3. Switch of phone,goto download mode (BIXBY + VOL DOWN + USB Cable plugged in)
4. use odin 3.14 and flash geiti's Twrp-3.2.3-0-crownlte.tar
5. boot to TWRP > allow modifications (important) > Wipe > format data > yes and then boot to recovery again.
6. now transfer the files to internal storage or if you have microsd u can skip this.
files - magisk-20.2.zip , RMM-State_Bypass_Mesa_v2.zip , No-Verity-Opt-Encrypt-6.0.zip.
7. flash RMM-State_Bypass_Mesa_v2.zip
8. flash No-Verity-Opt-Encrypt-6.0.zip
9. flash magisk-20.2.zip
10. flash again RMM-State_Bypass_Mesa_v2.zip.
11. reboot system, it will boot if not it will shut down and reboot itself, resetup again and you are rooted now.
Click to expand...
Click to collapse
thank you I have been tring to root android 10 since the Dec 20th I kept doing these steps but it wasn't working for me the main issue was twrp I was using 3.3.1 for Q and for Pie none of them were working I changed twrp to 3.2.3 now it is working perfectly thank you again
but you should upload those files so no one would use a wrong file

anyone has a solution for TWRP? now I have rooted my phone but one small problem after the first autoreboot after installing these files data encryption comes back so after that auto reboot if you go to TWRP you'll need to format data again then you can make modification
I need twrp so I can restore my data and I already tried to restore data before first and then install magisk , RMM bypass and no verity encryption then flasshong RMM bypass again but then it wont boot it will stuck at samsung logo (not first logo)

XGamer404 said:
Following these steps helped me get a working TWRP but there are some weird things going on:
- after I set up a pin there's no lockscreen asking me for the pin
- if I try to log into my Samsung account I get a "processing failed" pop up
- when I try setting up some biometrics like iris scanner it keeps asking me for a pin (not the same as the one I did set up earlier)
- if I restart my phone I end up with a bootloop
Any idea what's going on?
Click to expand...
Click to collapse
I faced that same problem and it is caused by No Verity file you flashed
Solution is
1. Reflash Android 10 with odin (All files) (flash reguler CSC not HOME CSC)
2. Do the above steps in order as @BytesReverser mentioned But skip step 8 and 10
you'll have root access but you will still have one problem after you reboot your phone if you want to install anything or want to make modification with TWRP then you need to format your data again cause after first reboot data encryption reactivates it self

Thats right it still stays but i have took backup using smart switch now, will restore later cuz even fstab removed the forceencrypt still it stays encrypted

Sorry root success, but fingerprint stop working after root!

I can no longer log in to the samsung account. why?

Try this method Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery

BytesReverser said:
after flashing twrp > format data and reboot to recovery
try flashing it in order
https://www43.zippyshare.com/v/8NH3aUn0/file.html
https://www43.zippyshare.com/v/IdZPt02e/file.html
https://www43.zippyshare.com/v/hiKinhVp/file.html
Click to expand...
Click to collapse
Help please
I followed this steps and i´m stuck in boot screen
Got the TWRP 3230, tried with your Magisk file and the version 20.3

Need help to root your Note 9.

Any new method with TWRP without problem?

nothing but adds on those links no matter where i click :S

Zer0De8th said:
Try this method Root Note 9 with Magisk on Android 10 (Q) without Custom Recovery
Click to expand...
Click to collapse
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app

inamie said:
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
which method works for you? twrp?
Am getting error :/

TWRP file please?

inamie said:
Go to this link and works for me.[emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The method from the link works for me as well. But be aware that you will not be able to install TWRP afterwards. You will only have the rooted N9 on Q that works fine.