Redmi Note 5 root lost - Xiaomi Redmi Note 5 / 5 Plus Questions & Answers

Xiaomi Redmi Note 5 and Magisk 19.3. After restart phone root is lost. Only installation again Magisk in TWRP helps. What can I do to save root permanently ?

please specify what rom u use, what fw, what kernel and based on 3.18 kernel or 4.9 kernel, any mod you use in your phone?

Kastorpol said:
Xiaomi Redmi Note 5 and Magisk 19.3. After restart phone root is lost. Only installation again Magisk in TWRP helps. What can I do to save root permanently ?
Click to expand...
Click to collapse
Install OrangeFox 10 recovery from fastboot, then boot it without restarting.
When it boots, install the latest Magisk, then reboot to Android, reboot twice and magisk should work just fine.

EriecTan said:
please specify what rom u use, what fw, what kernel and based on 3.18 kernel or 4.9 kernel, any mod you use in your phone?
Click to expand...
Click to collapse
Android 9
MIUI 10.5
Kernel 4.4.153-perf+
no mods are installed
installation orange fox recovery doesn't help - sometimes root is lost and must be installed in recovery ( magisk )

Related

Guide to install Magisk

Need proper guide to install Magisk.
From sratch. Need halp
Poacmy said:
Need proper guide to install Magisk.
From sratch. Need halp
Click to expand...
Click to collapse
>Go to your ROM thread
>flash firmware
>flash ROM
>flash GAPPS
>flash Magisk
>reboot
>enable Magisk Hide
That wasn't hard at all.
AutumQueen92 said:
>Go to your ROM thread
>flash firmware
>flash ROM
>flash GAPPS
>flash Magisk
>reboot
>enable Magisk Hide
That wasn't hard at all.
Click to expand...
Click to collapse
LineageOS comes with pre root. When I install magisk(the zip one), it doesnt show Supersu inside magisk manager and my SafetyNwt fails because of pre installed supersu
Poacmy said:
LineageOS comes with pre root. When I install magisk(the zip one), it doesnt show Supersu inside magisk manager and my SafetyNwt fails because of pre installed supersu
Click to expand...
Click to collapse
Flash this before flashing Magisk: https://forum.xda-developers.com/showpost.php?p=63615067
AutumQueen92 said:
Flash this before flashing Magisk: https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
Thanks for the help. Did all the process again.
One question, do I need to reinstall another root or Magisk is ok?
Poacmy said:
Thanks for the help. Did all the process again.
One question, do I need to reinstall another root or Magisk is ok?
Click to expand...
Click to collapse
Nah, Magisk's in-built root is good enough. No need to complicate thigs by adding other stuff
AutumQueen92 said:
Nah, Magisk's in-built root is good enough. No need to complicate thigs by adding other stuff
Click to expand...
Click to collapse
If the OS I'm using will get an update, what to do?
Using LineageOS.
Poacmy said:
LineageOS comes with pre root. When I install magisk(the zip one), it doesnt show Supersu inside magisk manager and my SafetyNwt fails because of pre installed supersu
Click to expand...
Click to collapse
LOS isn't pre rooted. If you are using some unofficial version then it might be pre rooted but official version isn't pre rooted
Kapiljhajhria said:
LOS isn't pre rooted. If you are using some unofficial version then it might be pre rooted but official version is pre rooted
Click to expand...
Click to collapse
LineageOS for Redmi Note 4x isnt official yet…
Prerequisites:
Unlocked bootloader (via http://en.miui.com/unlock/)
Working fastboot and adb
Custom recovery, e.g. twrp: https://dl.twrp.me/mido/
Installing twrp recovery on mido
* download the recovery file to your computer, e.g. twrp-3.1.1-0-mido.img
* enter fastboot mode
a) shut down phone
b) press volume down + power button, release power in ~4 after the phone vibrates
c) from terminal type
Code:
fastboot boot twrp-3.1.1-0-mido.img
Magisk Installation:
From the phone download the latest versions of the following files:
http://tiny.cc/latestmagisk
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ (get latest zip)
As an alternative download the files to your computer and then push them to the phone with:
Code:
adb push /sdcard/Magisk-v14.0.zip
adb push /sdcard/no-verity-opt-encrypt-5.1.zip
Reboot into twrp recovery (`adb reboot recovery` from the computer) and:
1. Flash no-verity-opt-encrypt-5.1.zip
2. Flash Magisk-v14.0.zip
3. Reboot.
If the phone still boots into the Mi Recovery and not into TWRP, then enter fastboot mode and do `fastboot boot twrp-3.1.1-0-mido.img` (with the correct path to the IMG file).
---HELP NEEDED ---
I am not able update magisk to 16.0 , i tried every different way the phone Goes to BOOTLOOP. But MAGISK 14.0 WORKS FINE. PLEASE HELP .
(Redmi Note 4 Snapdragon, 8.1 custom Rom )

Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]

Systemless Root & SafetyNet working [GUIDE][Magisk][StockROM-6.0.1][SkyMelon][TWRP]
Hi XDA friends,
After quite investigation I finally have found the way to have our devices Systemless Rooted.
The main advantage? SafetyNet working on our rooted device. That means Google does not notice our device is rooted ...yes, you can play Nintendo games or use Android Pay as well!
View attachment 4371569 View attachment 4371476
Here is the step by step guide:
You Must Have: Unlocked bootloader, ADB Fastboot drivers and Flashtool installed.
- Flash Stock Android 6.0.1 ROM with Flashtool (Wipes checked). I recommend 26.3.A.1.33 for the E2303 model. You can find Stock ROMs in this post.
- Flash TWRP from ADB: "fastboot flash recovery recovery.img" (I tried with v3.0.2.0 and also the new v3.2.1-0 recently published here!)
- Flash custom kernel (SkyMelon 8.1 or 9 without-root) from TWRP. Download v8.1 from this post or v9 directly here: View attachment 9-20171210-no-root.zip. Wipe Dalvik/Cache after install it.
- Flash the latest version of Magisk with TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
- Install the latest version of Magisk Manager.apk. GitHub repo: https://github.com/topjohnwu/MagiskManager/releases
- [Optional] In order to avoid flashing errors with TWRP it is recommended to update directly through Magisk Manager. If you want to install previous versions of Magisk (between v14.6 and v15.2), could be neccesary to check the box "Preserve AVB 2.0/dm-verity" before "Direct Install" it.
Note: Magisk v16.4 and Magisk Manager v5.7.0 was the last version working tested by me. From this version I will discontinue testing new Magisk releases on this device. Feel free to post your experience with the new ones
- This method is compatible with E2303, E2306 (reported by @zputnyq) and E2333 (reported by @Yester_Ko) models.
- Compatibility with Apps2SD reported by @tim_pear
Please if this works for you, thanks are very welcome to my first post! Also ideas or improvements to the post are welcome.
Credits:
- Special thanks to @osmank3 who built SkyMelon v9 without-root and help me with Magisk updates.
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Hi othmane.os,
I cannot provide information about restoring the TA. My warranty expired some time ago and I don´t have a TA backup.
Thanks for comment.
othmane.os said:
thanks for sharing your experience , I have A question what about DRM fix , did restore you TA backup ?
Click to expand...
Click to collapse
Hi osmank3,
I have modified the post with the screenshot request and also with some links to the material used in the guide.
If you have any problem, I will be glad to help you. Thanks for comment.
osmank3 said:
Hi! Thanks for your guide. Can you share your safety net check screen on magisk? I try that kernel and some other kernels with different magisk versions, but I don't understand safety net checking status.
Click to expand...
Click to collapse
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 9-20171210-no-root.zip
Thanks
Hi osmank3,
I have tested the kernel that you built and it is working perfect. Thank you! This version has been added to the post and of course is menctioned your contribution.
I'm afraid you'll have to install a stock ROM...
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
osmank3 said:
I want to use your guide but I'm busy to do current configuration of my phone. I delete some files on my system partition for gaining storage (I copied some new versions of upgraded apps to system partition) This take my time but I haven't got enough.
I use skymelon 9 kernel, with supersu. I guess because of supersu changed system partition and safetynet fails. I dislike supersu app but skymelon 9 comes with it. So I built skymelon 9 myself without supersu, but I didn't flash stock rom before installing skymelon 9 without-root and magisk. Now on my phone Magisk15 and skymelon9(compiled by me) installed. Magisk's hide function hiding itself from google apps and choosen apps but safetynet check fails.
Can you or anybody try this guide with skymelon 9 without-root which built by me?
View attachment 4371416
Thanks
Click to expand...
Click to collapse
GameBoy1989 said:
BTW: I cannot get working Magisk v15. If I install it direclty from Magisk Manager the installation fails. If I install it through TWRP (and do wipes), the process is correct but when I check it, Magisk Manager not shows it as installed. So for the moment, it is only working for v14.5.
Click to expand...
Click to collapse
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
It works
Thank you very much. Post updated!
osmank3 said:
I'm using magisk manager to patch boot.img with v15. I flash patched_boot.img with TWRP. It is working.
When I update it from v14.5 /data/magisk link crashing. I delete /data/magisk and upgrade on magisk manager as recommended type and reboot system, it is starting to work.
Ups! I forget to say. Check AVB 2.0/dm-verity
Click to expand...
Click to collapse
Hey, i downloaded Magisk v14.5 and tried to flash it with twrp but i got error "invalid zip file format" What should i do now or what did i do wrong?
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Great! Thanks for sharing :good:
Which is the difference between methods? I see that it also works for you by flashing Magisk v14.0.
Artsii said:
Yay i got this work but little bit different way.
1. Flashed stock rom with flashtool. I downloaded my stock rom from XperiFirm.
2. Flashed TWRP with this guide.
3. Flashed Skymelon 8.1 with TWRP and wiped Dalvik/Cache after install.
4. Flashed Magisk v14.0 with TWRP from this post and wiped Dalvik/Cache after install.
When that was done i rebooted and Magisk and Magick manager was installed. They aren't latest versions so i updated them.
1. Downloaded latest Magisk manager from here and installed it.
2. From Magisk manager i checked "Preserve AVB 2.0/dm-verity" and installed it with choosing the recommended option "Direct Install"
Everything seems to working fine and i did this to my E2303 with 26.3.A.1.33
Click to expand...
Click to collapse
GameBoy1989 said:
- Flash Magisk v14.5 from TWRP. Wipe Dalvik/Cache after install it. GitHub repo: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
This was only thing i made differently. I didn't find right magisk there what would work when flashing because i had problem with "invalid zip file format" so i downloaded that magisk zip file from another place.
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
If you try to flash directly the last Magisk version (v15.1 in this case) I don´t know why yet but it doesn´t work. For that reason it is neccesary to first flash Magisk v14.5 (last version working with TWRP).
The way that you do it is also a very good one! Thanks for sharing @lordmd.
lordmd said:
This worked fine for me but I directly tried flashing/installing latest version (15.1) from TWRP and later after booting via adb the .apk of the Manager.
Didn't show the Magisk as installed.
With making a backup in TWRP of the boot (just renaming it to .img it has a different extension in the name) and then modifying it (as Manager tells you when you want to install) I could make it work (flashing the modified boot image with fastboot).
(Other steps like flashing the stock ROM and the recovery worked as usual. Also no problems with installing the kernel in TWRP.)
Click to expand...
Click to collapse
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
osmank3 said:
After magisk 14.6+ there is a problem about dm-verity. Magisk can't patch it, so we must preserve the original dm-verity. When you are applying magisk 14.6+ from twrp, you can't preserve and magisk can't patch it. The true way is using magisk manager and patch with preserve dm-verity.
Magisk 15.2 version notes says that problem solved but I try it, it is not solved yet.
My first applying procedure is:
First, patch skymelon 9 boot.img file with new magisk version also with preserve dm-verity on Magisk Manager,
Flash recovery and open with twrp
Apply skymelon 9 wipe dalvik and cache
Apply new magisk
Flash patched img
Click to expand...
Click to collapse
GameBoy1989 said:
Let´s see if the next v15.3 beta finally works. Thanks @osmank3
BTW: Did you finally install the stock ROM or could you unroot your CFW for installing Magisk?
Click to expand...
Click to collapse
I must flash system partition from stock Rom, after that safetynet passed.
Ty
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
I´ve tried with Pexo Rom v3 and systemless root works with Magisk but it does not passed Safety Net check.
Sayan Qadri said:
Is pexorom better than stock. Is this going to work on pexorom.
Please reply
Click to expand...
Click to collapse

how to root the device by magisk?

In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Tysovwik said:
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Click to expand...
Click to collapse
yes
Usually you don't even have to flash TWRP recovery if you want to keep original recovery, you can just boot it with "fastboot boot twrp.img".
Just a FYI, the latest magisk 17 has not been working for me. Magisk 16 works just fine.
I am on the xiaomi.eu rom
I'm on latest xiaomi.eu and Magisk 17.1 is working fine
bartekm01 said:
I'm on latest xiaomi.eu and Magisk 17.1 is working fine
Click to expand...
Click to collapse
After I flash magisk 17.1 , my mipad 4 can't use LTE
簡_OvO said:
After I flash magisk 17.1 , my mipad 4 can't use LTE
Click to expand...
Click to collapse
That's strange... I've using magisk on 6 device's and never had this sort of problems. Uninstall magisk and check if it's working again
@簡_OvO
On what Rom you have this problem with Magisk ?
I use Mi Pad 4 LTE and Magisk 17.1 on AOSP 8.1_v25 and everything works as it should.
Magisk it has nothing to do with Modem/Baseband he patching Kernel.
After using Magisk uninstaller or restore stock Kernel works for you LTE ?
bartekm01 said:
That's strange... I've using magisk on 6 device's and never had this sort of problems. Uninstall magisk and check if it's working again
Click to expand...
Click to collapse
After I flash again, it can work well
---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------
Andro_Nicus said:
@簡_OvO
On what Rom you have this problem with Magisk ?
I use Mi Pad 4 LTE and Magisk 17.1 on AOSP 8.1_v25 and everything works as it should.
Magisk it has nothing to do with Modem/Baseband he patching Kernel.
After using Magisk uninstaller or restore stock Kernel works for you LTE ?
Click to expand...
Click to collapse
I use MIUI10.I cannot understand why.But after I flash magisk again,LTE works well.
Could you please explain where I find the mipad 4 boot image when using this method to patch it?
When choosing the option in magisk manager to patch boot image I have to search for the original boot image to patch as the app doesn't point staight to it...
Many thanks
@Tysovwik, I see you want keep miui. You have to block overwriting recovery by original one. I have seen option for it in twrp, but i have not tested it. The same you can have if you use special zip package.
Twrp has second option for auto install magisk 17.1, but i installed it from zip file (twrp labeled 20.12.2018 can have 18.0)
is this the best way to Root a Mi Pad 4 LTE ?
A long time ago someone said:
Tysovwik said:
In next 2 weeks my mi pad 4 LTE will come to me.
Could you tell me, how to root it by magisk?
1) unlock it by xiaomi (360 hours waiting)
2) flash twrp
3) flash magisk
4) reboot
That is all I need to do to get a root ?)
Click to expand...
Click to collapse
My plan is to follow this process.
Does anyone know if I still have to do step (1) ? or how that is done ?
Some noobie questions.
I already have TWRP installed in my Mi pad 4, and want to keep my original MIUI rom
To install Magisk what should I do next?
Just flash magisk from twrp?
Do I need to flash no-verify-opt-encrypt.zip?
Select any option of wipe in twrp before flashing Magisk?
If I get a bootloop can I just use Magisk unistaller?
soulgazer said:
Some noobie questions.
I already have TWRP installed in my Mi pad 4, and want to keep my original MIUI rom
To install Magisk what should I do next?
Just flash magisk from twrp?
Do I need to flash no-verify-opt-encrypt.zip?
Select any option of wipe in twrp before flashing Magisk?
If I get a bootloop can I just use Magisk unistaller?
Click to expand...
Click to collapse
I would wipe cache /dalvik cache before and wipe cache again after flashing. But yeah, just flash the magisk zip. You check in the settings under security if your device is encrypted, which I'm guessing it probably is already. In which case there's no need to flash no verify encrypt zip. Unless you want to have no encryption. In which case you'll have to start all over, complete format in twrp then flash magisk and no encrypt zip before first boot.
If you want to stay encrypted (assuming you are already), just flash magisk. I haven't done it in a while! So not sure if magisk manager will be installed with zip flash, if it's not there when you boot to system, just download and install latest magisk manager. You can always then download a root checker app from playstore to be sure all went well.
Good luck dude

Bootloop after installing Xposed and uninstalling Magisk

Hello !
I've tried to install Xposed with Magisk (the v3 beta version, notorious for provoking bootloops instead of the v4 which was the right one) and got stuck in a bootloop. I rebooted into TWRP and tried to restore a backup (system, system image, vendor image and ramdisk), and it still went in bootloop. I figured that, as Magisk was systemless, Magisk and Xposed were still there, so I flashed uninstall-magisk.zip.
Unfortunately, now I don't have access to TWRP (maybe flashing uninstall-magisk flashed the original erecovery over TWRP ?) and whenever I try to boot, I enter the eRecovery with written "Serious problems occured when the device boot" and the options I have are:
-Download latest version and recovery
-Wipe data/factory reset
-Reboot
-Shutdown
Should I use the "download latest version and recovery" ?
Should I try to flash TWRP with fastboot ?
I guess I can't do a factory reset since I updated before to BLA-L29 8.0.0.157(C432) from BLA-L29 8.0.0.120(C432) and downgrading seems to provoke a hard brick.
Thank you.
Edit: Thanks to ante0, I had access to TWRP (couldn't access it since USB was still connected). He suggested I use HuRUpdater TWRP script to update to the same build I have on my device now. I will report once, and if, I succeed in doing this. In the meantime, if anybody as ideas, I wouldn't mind hearing them !
Edit: Ante0 told me that I had to use the HuRUpdater TWRP script to update to the same build I was before bootlooping, so I did and everything went back to normal.
if u you want try xposed or any system less magisk modules be sure to have magisk manager for recovery mode
that's will ensure if u got bootloop to boot to recovery mode and only un tick xposed module or any module got ur devise to bootloop
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Antidote03 said:
if u you want try xposed or any system less magisk modules be sure to have magisk manager for recovery mode
that's will ensure if u got bootloop to boot to recovery mode and only un tick xposed module or any module got ur devise to bootloop
Click to expand...
Click to collapse
Didn't know that there was a Magisk Manager available for the recovery, if I succeed in unbricking the device I'll try it out before installing any Magisk Module, thanks !
thref23 said:
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Click to expand...
Click to collapse
I went on the official Magisk thread to get the latest build, absolutely forgetting about the v4 that I had seen on another thread a few hours before, unfortunately it was too late when I realized the mistake I had done by flashing the wrong version
Finally systemless Xposed works on Mate 10 Pro
thref23 said:
FYI Xposed v90 beta 3 (which I think is the latest official build) is not compatible with EMUI 8.0 and will cause a bootloop. You need to install v90 beta 4.
https://forum.xda-developers.com/showpost.php?p=77269446&postcount=7439
https://github.com/rovo89/Xposed/issues/310
Click to expand...
Click to collapse
MANY thanks indeed !! After days of searching on XDA and elsewhere...your link brought back Xposed on Ore0 8.0 Mate 10 Pro. Greatly appreciated.

root Android Q on s9+

Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q?
visit: h t t p s : / / twrp.me/site/update/2019/10/23/twrp-and-android-10.html
As, if now you cannot. For Android Q, it's still in research.
------------------------------------------------------------------------
Never tried but: ClockworkMod Recovery – a past alternative to TWRP custom recovery.
h t t p s : / / en.wikipedia.org/wiki/ClockworkMod#ClockworkMod_Recovery
Research over it & let me know if anything worked for you-!
I successfully roote Q with this ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I just flash TWRP, format and flash custom rom. Rooted.
First of all. What device do you have and what exactly have you tried? Include references.
Remember first step is to search before asking.
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
StonebridgeGr said:
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
Click to expand...
Click to collapse
I would recommend you flashing custom firmware, like the one in my signature. Everything is working, including Security Folder.
Rooting S9 +
sarjarim said:
I just flash TWRP, format and flash custom rom. Rooted.
Click to expand...
Click to collapse
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
xectis said:
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
Click to expand...
Click to collapse
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
sarjarim said:
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
Click to expand...
Click to collapse
Magic! Thanks bro.
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
hi im new to this but what do you mean by Q??
i have sprint s9+ sm-g965u1, can i root my phone now ?
Devilix said:
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
Click to expand...
Click to collapse
This isn't true I flashed Twrp 3.5.091 via Odin, S9+ exynos android 10, then flashed Magisk 21.4.
When I got phone it was android 10 June 2020 security update. It then updated again to 21/02/2021 ota.. I was able to flash recovery twrp and root/debloat. Only problem I did find is that I cannot flash lineage 18.1 or any custom roms.
Regards
JeyKul said:
Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q? No root method root android Q.
Click to expand...
Click to collapse
hey ,
1.install magisk manager on your phone
2.download the firmware from samfirmware for your model of phone to pc
3.download 7zip with lz4
4. use 7zip lz4 to extract boot img from AP(firmware)
5. send the xtracted boot.img to phone sdcard and use magisk manager to patch said image .
6. send the patched img to pc and use 7zip to create archive as boot.tar file
7. one you install the firmware as normal via odin (disable auto reboot ) go back and disconnect/reconnect usb from phone so it appears as added in odin once more.
8. add the boot.tar file to AP in odin and flash the phone , reboot system and install magisk manager again , go into magisk and it will reboot again to fix the root.
there is a video somwhere on youtube showing you better than ive tried to here.
this is by far he best way as you can still take ota updates because stock recovery is still present .
regards

Categories

Resources