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.
Related
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
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
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
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
try booting twrp
'fastboot boot img name' then flash recovery from there. hope it works.
BJack0 said:
My device is stuck in the initial boot sequence in which the logo will show as if it is booting normally, then it will stay on this screen until it goes completely blank, at which point I have to hold the power button for a long period of time to get it back to the boot sequence. My phone is unlocked and I was trying my first time at flashing a custom recovery and OS, I flashed my device with TWRP and successfully installed it along with a flash of pixel experience, After using pixel experience I wanted to try lineage OS since it wasn't as good as I hoped, so I tried to get into the TWRP and I could not do it at all I tried every method I could search. After an hour of trying different methods of getting to twrp I tried to re-flash the recovery and that is when the phone because unresponsive and does what I have described above. I currently have access to fast boot and I dont want to go ****ing my phone up more than I have. If anyone can give me a step by step guide on how to fix this it would help so much since im new to android and I cant afford another £400 phone.
Thanks
Click to expand...
Click to collapse
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Go here and get the latest fastboot ROM for your phone.
https://xiaomifirmwareupdater.com/miui/raphael/
For now make sure you get the one that matches the region for your phone.
Then follow this guide to flash it
https://c.mi.com/thread-1857937-1-1.html
Use the fastboot flashing section.
Make sure you change the flash option to 'clean all' when flashing. The default option will lock the bootloader again after flashing. If you do the default option with any ROM that is not the same region as the phone you will hard brick the phone, this is why I recommend getting the ROM that matches your phone.
When unpacking the fastboot ROM, it is a Linux/Unix zipped tarball, most Windows zip software will need to extract it twice. The first time will give you a single .tar file (if it doesn't have an extension then rename it and add .tar to the end) You will then need to extract everything from the tar file, which you give you the folder, containing the ROM data, to point the Mi Flash Tool at.
After doing this you, if you've remembered to change the flash option to 'clean all', then you'll have restored to stock and kept the bootloader unlocked. Now you're good to try again.
Keep a copy of the fastboot ROM on your PC and back everything up on your phone before flashing. Then if you get in a mess you know how to easily recover things.
Once you get more experienced there will be other things you might be able to do, depending on the situation, that allow you to get things working without losing everything and needing to start from scratch.
Thanks
Robbo.5000 said:
Don't worry, things can be recovered easily. Until you get more knowledgeable and you understand more about flashing use this failsafe to recover from (almost) anything
Click to expand...
Click to collapse
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
BJack0 said:
Thank you so much for the details post, I will try what you have said above and will report back with my results. I have one question if you know the answer ( My phone is the UK edition of the Mi 9T pro ) Would I need to download the global or EEA fastboot version.
Click to expand...
Click to collapse
For safety download the EEA ROM.
I also suggest you immediately flash dm_verity (https://forum.xda-developers.com/k20-pro/how-to/flashing-orangefox-recovery-mi-9t-pro-t3980579), after you flash twrp, wipe data and then flash that
Sent from my Redmi K20 Pro using Tapatalk
Robbo.5000 said:
For safety download the EEA ROM.
Click to expand...
Click to collapse
Everything you said worded flawlessly and your a life saver. If you dont mind do you have a link to a set of guides on how to correctly flash a custom recovery and lineage OS? since when I try to research these guides I get 5 different versions of TWRP and lock my phone out :laugh:
ishaqtkr said:
I also suggest you immediately flash dm_verity after you flash twrp, wipe data and then flash that
Click to expand...
Click to collapse
If you dont mind me asking could you go into slightly more detial on that since I have seen orange fox but I dont understand what dm_verity is.
Please ignore all reply's above as I am going to make another separate post about lineage OS
Thank you for replying and resolving my issue.
After months of deliberation I finally decided to root my Note 9. It was the first time I've ever tried rooting and it seems to have gone horribly wrong. To root the phone, I followed the guide in the video titled 'How to Root Galaxy Note 9! [EASIEST METHOD]' on youtube which has an instruction link in the description. As a new user here, the forum doesn't allow me to post links yet, so please just type the title on youtube and it'll come up as the first result.
What I did was:
- unlocking bootloader
- Flash AP file with TWRP version 3.4.0
- Wipe data
- Since I was worried about using a software from an unknown source, I then flashed the official magisk v20.4 instead of the 'N9-S9_root_for_oem_issue_devices_v3' file recommended in the video.
After doing so, the note 9 restarted and showed the error message "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.". I allowed the phone to reset.
Following this, the phone restarted and showed exactly the same message of 'verification failed' and no amount of going through the rebooting process resolved the issue. I googled the issue and was advised to flash the phone with Odin by going into download mode. I then tried to go into download mode, but the phone will simply not go into it and tries to restart the normal way. I also tried to connect to my laptop to see if I can flash with odin but the phone was not recognised at all by the computer.
I then tried to reboot using the twrp key combo and this worked. I then decided to try flashing with the 'N9-S9_root_for_oem_issue_devices_v3' file in the tutorial. Yet, this led to the same issue as with the official magisk file.
Looking at some rooting tutorials, I see that some of them recommend flashing CSC, AP, BL and CP instead of just the AP in the tutorial I followed. I then thought that perhaps the issue is I need to install a ROM on the device. I therefore tried to load the lineage 17.1 ROM in the micro SD card and installed it (top left option on twrp 'install') as well as the magisk and disable_dm_verify_forceencrypt zip files.
In hindsight, this was a stupid move from me - I did so I was in full panic mode at that point and desperate for a solution.
After doing so, the phone rebooted and showed a booting animation of a single blue curved line stuck with a circle rolling from right to left on it.
I left it for a while, hoping that it meant the new ROM was booting. 30 min later it was still stuck on the animation!
I then tried to reboot the phone. Pressing power button did nothing. I then tried different combinations and eventually power + volume up + bixby allowed it to restart in TWRP mode.
As of now, the phone is still in TWRP mode. The phone is still not recognised by my laptop and will not enter download mode if I press volume down + bixby when restarting.
I am fully aware that I've screwed up the rooting process and feel awful about it. It was the first time I've ever tried rooting and I really hope it is only a 'soft brick' and that my phone can be saved. I would really appreciate if anyone here could advise what I can do to complete the root process correctly from here?
Many thanks,
Sam
Is there a "download" or "bootloader" option when you press the reboot button in TWRP? My Note9 is on stock, so I'm not 100% certain myself. However if there is, that should take you to Samsung's download screen. This way you can send yourself back to stock if you give up on rooting your device.
BTW, I do recommend following a note9 rooting guide on XDA (it's not too hard to find) over a youtube video, since YouTube videos can often be out of date or a little sketchy.