How to | Galaxy S9 (SM-G960F & F/DS) Root Android PIE - Samsung Galaxy S9 Guides, News, & Discussion

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

Related

Sprint Note 5 Boot-looping trouble!?

This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
saywhhaa33 said:
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
Click to expand...
Click to collapse
First of all you have entered wrong model no here note 5 model no should be SM-N920xx
1)Have you enabled Oem unlocking from developers option before flashing twrp and cf-autoroot using odin? If not then you done a mistake!!
2) Have you tried to flash latest stock firmware using odin with latest usb drivers installed on you pc and proper odin flashing guide?(Flash latest 6.0.1 for your device with latest usb drivers installed on pc and connect phone to main usb port using original usb cable) After flashing stock rom if your facing bootloop then you can try reset through stock recovery (Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
3)If you can boot into twrp recovery normally then flash any custom rom suitable for your device i.e. for sm-n920p..Custom roms are pre-rooted so no need to flash cf-autoroot..Flash custom rom, if you successfully boot up the rom( It's difficult to boot custom rom though if you haven't enabled oem unlocking you will face custom binary is blocked by frp protection),then enable oem unlocking from developers option and try flashing stock rom again
4) Next option for you is download Samsung smart switch for pc, install latest usb drivers on your pc, connect your phone to pc in download mode(Press volume down+power+home button simultaneously),in smartswitch select emergency software recovery, it will ask you imei,model no and serial no which you can find either on box or back panel of your phone,smartswitch will detect latest stock firmware for your device, hit update now,give some time until update complete..Your device will be automatically reboot..If even you face bootlopp, then goto stock recovery(Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
**IF SUGGESTION IN SECOND POST HELPS YOU THEN ITS DONE, AVOID NEXT SUGGESTIONS**
Are you sure you can't install cf auto root again to solve it? IF not...
I did a search and got hits for twrp for N910P. Get it loaded, get it wiped and have another shot at success. Next way to get rid of the persistent rooter gone rogue, load up a factory BL + AP. If that doesn't work download another version and try again.
I've enabled OEM unlocking, flashed latest stock AP...BL.. And so on, factory reset in both factory and TWRP. I have also tried flashing CF Auto root again to see if that would fix it also custom ROMs bootloop except for CM13 and Lineage OS- Which is weird because the ROMs are for the SM N920C model and I'm and Sprint model, So I don't understand that. Weird!! Everything recognizes me as SM N920C except when I am in download mode. Also, having no imei or any back ups make its even harder since my computer completely crashed on me because I am unable to use Samsung smart switch due to the wrong model and null imei. So I'm completely stumped with this issue. Not sure if its a corrupted partition or folders not being in the correct folder locations along with wrong permissions, I've literally stressed everything to my knowledge about this and I'm all out of what issues this could be related to

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?

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.

How to root the tablet A8 2019 T290

Hello guys, decide to mount this tutorial because I still see a lot of people with doubts, yes we already have how to root our device
I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
A tutorials too complex for some users, teaching you how to create your own Magisk modified Img boot, but I like simplicity, so if you don't want to break your head too much, here's a tip, use a successfully modified img boot , what you need is to install the rom stock that was used to create the modified boot first.
let's go to the tutorial, warning that the files posted here are not my own, and if it doesn't work, check if you're not commenting on any flaws, don't try to memorize the tutorial, follow it step by step. come on!:dedos cruzados:
1 - first follow these steps to unlock the bootloader:
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.
Now let's go to the next step, reinstall an outdated system, I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
2 - installing the stock ROM that we will use:
download this rom: https://samfrew.com/ru/download/Gal..._Wi-Fi-__/rue3/KOO/T290KSU3BUE1/T290KOO3BUE2/
OBS: a little detail about this firmware, it is made in arm32, which apparently makes it "lighter", but also has a more acidic use of RAM memory. This was the last software I installed on tab A, and I can say that the use has become better with it, but if you want to stay in the stock rom, even custom gsi didn't get such a good performance. It's worth testing, but be aware of the risks, I'm not responsible for errors.
Updating: use a modified version of Odin, to do the installations, be careful with downgrades, I managed, I was in the most current version of March, and I managed anyway using this modified Odin, but do it at your own risk, download the most current version here:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
And install via Odin, if you need more details just a Google, there are already millions of tutorials for that lol
when you get here you should already be aware that you have lost all your data, but it is necessary that the OEM option is enabled in the options, so in the CSC session use Home CSC, so that you leave the data saved, and do not lose the initial settings : )
once with successful installation, we will now install the file modified by magisk
3 - magisk Installation:
Intall TWRP: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
just follow our friend's tutorial, with a little observation, after starting the process in odin, be sure to hold the volume up button + turn on, to be redirected to the TWRP.
follow the standard steps to install magisk, if it doesn't work, you will have to manually modify the system boot.img along with magisk maneger.
if case of problem:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
I haven't had the tablet in my hands for a few months, so unfortunately I can't help more than that, as I said this was the last system I used, just because GSI are not very functional and are not always light, sometimes they crash more and it has more annoying bugs to fix that discourage daily use. my tip is, stay in stock Koo, excuses for those who can't, the most I can do now is guide them.
As a gift for you, I will teach you how to use Xposed :3
remembering, I did several tests that several times I faced bootlooops but in the end it worked for me, so notice, do it at your own risk.
5 - How to install end use EDexposed with Magisk
these versions were the ones that worked without problems in this rom
Install Riru - (Riru core) V21.0
Install Riru - Edxposed v 0.4.6.1(4510) YAHFA
Reboot, after reboot, install Edxposed Manager
and you can be happy
I thank you all for your help, and remembering that this was just a compilation of tips, to facilitate everyone, take due care to avoid problems, and don't forget to thank: 3 ?
Has anyone attempted this yet?
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
EngineeNerd said:
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
Click to expand...
Click to collapse
is the topic dead
EngineeNerd said:
is the topic dead
Click to expand...
Click to collapse
Hi friend, sorry but there are more current ways of routing, even already working on a TWRP, but now you can do the following, try using the same Firmware in the same version of the bootloader, otherwise there will always be an error, the file compressed this modified to work with Odin, I tested it myself on my T290, but I cannot guarantee its effectiveness if I try to use it in another version, I do not recommend doing this even.
I had trouble unlocking the bootloader until I did this:
After enabling OEM unlocking and turning the device off, plug in the USB cable. Hold both Vol + and Vol - at the same time, then unplug and replug the USB cable. The bootloader unlock screen should come up.
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
does this work if you're on a11?
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking o
Click to expand...
Click to collapse
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
Click to expand...
Click to collapse
what are you specifically asking? the TWRP here is very functional, but custom roms are not very stable for this tablet, some GSI behave well, but it's still better to stock debloated
WillisD said:
isso funciona se você estiver em a11?
Click to expand...
Click to collapse
I do not think so
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
MythoAegis said:
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
Click to expand...
Click to collapse
yes, you can go back to previous versions, but it gets harder when you upgrade bootloader version.
In order not to crash the downgrade, you need to look for the latest Android version you want, from your region you are in now.
An example:
I'm on the latest version ZTO - Brazil - Android 11
to get back to Android 10 I need to download the latest ZTO version with Android 9, of course you can try between different regions, but it will be a little more complicated.
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
themace51 said:
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
Click to expand...
Click to collapse
You mentioned it's on Android 11, didn't you?!
well, I don't have Tab A with me anymore, but the suggestion I give you is to try to go back to Android 10, then install TWRP, and then try to install magisk, I can give you the last firmware I installed,
currently he is with my brother.
The firmware is Koreano, as I said, it is 32bits, and super functional.
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки - 4PDA
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки
4pda.to
take a look here, search for the firmware I told you about, very good by the way
Hey
I am on T290XXU3BUC1 and i do not understand the language on the link you post
I tried your tutorial , but i am getting
sw rev check fail [aboot] Fused 3 > binary 3
hello, about that, but lately I don't have much time, but I'll update it today if I can, you probably got this error because this firmware is old.on 4pda there is a newer version with root, remembering that currently you can root through twrp, I'm going to port my last attempts here, but I notice that I don't have the tablet in my hands. use translation tools, the site is in Russian
I updated the guide as I could, any doubts I'm still here, but I can only guide, it's no longer possible to test.
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
themace51 said:
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
Click to expand...
Click to collapse
have you tried to put the firmware I mentioned? this tutorial probably won't work on android 11 one ui 3.1, i say this because the TWRP is a bit old, so as long as it's on the updated firmware it's really hard to do anything.
if you don't want the specific KOO Firmware, you can get the latest firmware version for your region which is on android 10.

M21 Stuck at bootloader unlocked warning screen

Hi mate... need your help so badly,
my M21 is stuck at the bootloader unlocked screen. Can't do anything more than restarting the phone by pressing Vol down + power. Doesn't detect from PC. Can't get into download mode or anything else. this happened while I'm flashing the TWRP and trying to restart the phone into recovery mode. please help.....
Did you resolve this?
hey did you solved the issue ? and how please. I have managed to flash firmware using odin but still stuck at the bootloader warning. What should I do ?? anyone ?
indike114 said:
Hi mate... need your help so badly,
my M21 is stuck at the bootloader unlocked screen. Can't do anything more than restarting the phone by pressing Vol down + power. Doesn't detect from PC. Can't get into download mode or anything else. this happened while I'm flashing the TWRP and trying to restart the phone into recovery mode. please help.....
Click to expand...
Click to collapse
Hey I have the same issue. I have tried Odin to flash stock firmware also repartitioned the phone using Odin but did not solve the Issue . Please can anyone help us?
Also can you remember what you did before getting stuck cause I did nothing wrong . Opened the maps And gave the permission to use location after that calibrated the compass and phone hung on me from then it is on that warning screen
rajhridoy said:
Hey I have the same issue. I have tried Odin to flash stock firmware also repartitioned the phone using Odin but did not solve the Issue . Please can anyone help us?
Also can you remember what you did before getting stuck cause I did nothing wrong . Opened the maps And gave the permission to use location after that calibrated the compass and phone hung on me from then it is on that warning screen
Click to expand...
Click to collapse
Bro i have also same problem when I was flashing twrp through Odin .
My phone is stucking on twrp twrp is blinking again and again.also when I try to go to the download mode it automatically comes to bootloader and then to twrp please bro help if have fixed it
I was just speaking to a phone retailer and he told me how Shamshung M-series phones are getting locked by OEM manufaturer automatically within 6-7 months of usage (he was ready to show me evidence also so I believed him) , he said there is no solution to this So pls guys just an advice DO NOT CONNECT YOUR PHONE TO INTERNET FOR ANY OEM UPDATES,
1> TRY TO BUY PHONE FROM ONLINE STORE (BECAUSE RETAILER WILL FORCEFULLY UPDATE THE PHONE EVEN IF YOU TELL THEM NOT TO UPDATE)
2> FIRST, DONT PUT IN ANY SIM CARD IN SIM TRAY
3> SECOND, DISABLE WiFi (DONT SAVE ANY WiFi PASSWORDS) & TURN ON AIRPLANE MODE
4> THIRD, TURN ON DEVELOPER OPTIONS- USB DEBUGGING "ON" & DISABLE "KEEP MOBILE DATA ALWAYS ON" UNDER DEVLOPER OPTIONS
5> FOURTH, USE "DEBLOAT LIST" ATTACHED BELOW TO UNINSTALL INSTALLED APPS USING ADB
6> FIFTH, ONLY CONNECT TO WiFi FOR FEW SECONDS SO THAT THE OEM UNLOCK OPTION IN DEVELOPER OPTIONS GETS GREYED OUT.
7> SIXTH, FLASH ODIN-TWRP TAR FILE, WIPE/FORMAT DATA, BOOTLOGO PATCHER ZIP, MAGISK 24.3 ZIP, PRISH KERNEL (OR ANY KERNEL OF CHOICE), THEN FLASH TOTSUKA/PIXIE/CLEAN_OS/CrDroid10 (ONLY 3 STOCK-BASED ONEUI ANDRO 11 ROMS AVAILABLE, NO CUSTOM-BUILT NON-ONEUI ANDRO 11 ROMS AVAILABLE NOT EVEN M30S PORT ROM), VBMETA IMG
8> REBOOT TO TWRP, WIPE DATA
9> AFTER DEVICE BOOTS FIRST THING IS DISABLE WiFi & TURN ON AIRPLANE MODE, INSTALL NETGUARD FIREWALL APK THROUGH PACKAGE INStALLER (ALWAYS KEEP NETGUARD ON THROUGHOUT THE PHONE LIFETIME OTHERWISE SHAMSHUNG OTA MIGHT KILL THE DEVICE),
10> DEBLOAT BUILT-IN GAPPS USING ADB
11> INSTALL MICRO-G FROM TWRP
#NOTE: FOR FACTORY RESET SCENARIO REPEAT STEPS 10 & MAYBE 11 TOO.
AVOID VISITING OR USING OEM WEBSITES AND APPS. REMEMBER, FOR GUGLE EVERYONE IN THE WORLD IS A POTENTIAL TERRORIST.

Categories

Resources