Hey all, just wondering what the best/ easiest way is to go from an unlocked, rooted phone with android 8 on it, and get it to 10. During this process I would prefer to lock it and unroot. I've been rooting my phones since the first Droid phone back in the day... but alas, I just don't have the time for it these days... life and work catch up to you. I would also like to perform a totally clean install and format the phone. I was under the impression that simply taking an OTA for 10 would do this? Am I wrong? If so, a link to a guide or some advice would be greatly appreciated!
I am also unlocked and rooted on 8, looking at going to 9 or 10 but stayed on 8 because with 9 I was having issues with wifi tether to certain device types (I think it may have been due to hardware tethering acceleration). I am not sure if wifi tether is working yet on Android 10, I have read here: https://forum.xda-developers.com/pixel-2-xl/help/android-q-beta-3-wont-mount-rw-t3929443 that there is problem mounting /system as rw.
But getting to your original question, I think the process of getting to 10 would be similar as going to 9. You will need to do a full wipe, so back up everything.
Download the OTA file
Boot into Recovery mode
Navigate to ADB sideload
Connect the handset to a computer with ADB tools installed
Enter the sideload command
Reboot your phone
Extract Boot Image
Install Magisk 19.4
Patch boot image in Magisk
Move patched boot image to computer
Boot into fastboot
Flash patched boot image
https://9to5google.com/2019/09/03/android-10-google-pixel-sideload-ota/
https://android.gadgethacks.com/how-to/root-your-pixel-3-android-10-0200295/
Update, I went from 8 to 10 with canary magisk and tether is working
I downloaded latest platform tools, factory image, twrp 3.3 img, magisk canary apk and zip
ran the flash-all.bat, had to do it twice, the first run failed
wait for the phone to reboot and start
put canary magisk apk and zip on phone storage
install canary magisk apk
fastboot boot twrp3.3.img
flash canary magisk in twrp
reboot into system
followed barski's instructions from https://forum.xda-developers.com/pixel-2-xl/how-to/android-10-root-t3964176/page2 :
1. Magisk -> Downloads -> MagiskHide Props Config
2. Magisk -> Downloads -> BusyBox
3. Reboot
4. Adb shell -> type ‘props'
5. Select ‘5’ -> n -> ’net.tethering.noprovisioning’ -> y -> y
6. Wait for reboot
7. Adb shell -> settings put global tether_dun_required 0
8. Reboot
Hi
I have installed Lineage Os 16 custom rom for Poco F1.
But the problem is i can't root the device.
I have downloaded the magisk 20.1 zip and the Disable-Force-Encryption-Treble.zip from:
https://magisk.me/root-xiaomi-poco-f1-using-magisk/
I enter the TWRP , i flashed first the disable force encryption zip, i rebooted to twrp , i flashed the magisk and i rebooted the device,
Magisk manager installed properly but when i tap Safety Net Check Success i get the ctsProfile:false.
Rootchecker also gives me the message that root is not properly installed.
Any ideas but if possible without having to format data .
I also tried (after another members suggestion) to flash magisk 19.4, canary magisk but with no results.
thank you in advance
First of all: keep it simple. Set screen lock to swipe. That avoids encryption too. Go twrp and wipe system and re-flash ROM (and GApps if needed) that restores boot image.
Second: try rooting with lineageOS native addonsu from download/extras. Enable it in developer options.
When i try to get in to magisk from recovery, it turns on but after like 10 seconds it turns off. i can get my phone to boot in to nonroot system. this has been issue for half a year.
using android 9
model: SM-A505FN
magisk manager version: 7.5.1 (267)
magisk version: not sure. i think i have 19 or 20
installed it by patching ap and flashing the patched file with odin
Voutsjude said:
When i try to get in to magisk from recovery, it turns on but after like 10 seconds it turns off. i can get my phone to boot in to nonroot system. this has been issue for half a year.
using android 9
model: SM-A505FN
magisk manager version: 7.5.1 (267)
magisk version: not sure. i think i have 19 or 20
installed it by patching ap and flashing the patched file with odin
Click to expand...
Click to collapse
android 9 isnt the best for modding like this, works alot better on android 10, if you read the install instructions [https://topjohnwu.github.io/Magisk/install.html];
After installing Magisk in recovery:
(Powering up normally) → (System with NO Magisk)
(power + vol up) → (Splash screen / bootlock warmning) → (Release all buttons) → (System with Magisk)
(Power + vol up) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
I will note that this suffers from random bootloops and things. just update
I used this after update - https://forum.xda-developers.com/galaxy-a50/how-to/guide-samsung-galaxy-a50-btc4-firmware-t4071817
just remember to unlock the boot loader again after flashing 10
can you give me the instructions for updating to android 10 with magisk installed in android 9
Voutsjude said:
can you give me the instructions for updating to android 10 with magisk installed in android 9
Click to expand...
Click to collapse
Just a fresh stock install is the best way to go, updating via ota wont work because of magisk
1) Find you firmware [https://www.sammobile.com/firmwares/search/a505/]
-Clicking on your model will present you with firmware downloads
-Find yours and download it [country and network or just the country should work]
-Extract it somewhere.
2) Get Odin [https://dl2018.sammobile.com/Odin3-v3.14.4.zip]
-Extract it somewhere
-Load it
-Add the files from the firmware folder into the correct sections (i.e/ ap, bl, csc - I cant remeber them all of the top of my head)
3) Get into download mode
-Power off device or if its boot looping Press and hold power + vol down to force a restart
-Press and hold both vol buttons and connect it to your computer with usb
-Odin should now say added in the log
4) press start and wait
-Its easier to set up your phone with no account because your going to wipe it again anyway,
-unlock bootloader
5) Flashing the things
-When selecting the downloads of twrp make sure you get the magisk patched one.
-Start from step 5, as you have just flashed stock. [https://forum.xda-developers.com/galaxy-a50/how-to/guide-samsung-galaxy-a50-btc4-firmware-t4071817]
-When flashing twrp make sure auto reboot is OFF is odin options
notes:
I've updated to magisk 20.4 with no issues, xposed seems to trip the saftey net tho.
i cant figure out which country i should pick.
my build number is A505FNXXS2ASJ1
and csc: A505FNOXM2ASH2
and im from finland but i remember that i took like baltic (SEB) firmware when i installed magisk but not sure which one to pick now
idk why there are not any actually firmwares for finnland...
im gonna say try this one; https://www.sammobile.com/samsung/galaxy-a50/firmware/SM-A505FN/SEB/download/A505FNXXS4BTCA/336036/ ??
I really dont know tho
got it working. updated to android 10 with twrp and magisk installed. thank you
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.
The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)
sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.
Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
[deleted]
johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Rename magisk from apk to zip, and then flash the magisk zip from recovery
Saezrfff said:
Hi,
When my phone automatically updated to MIUI 14, a error message appeared and then, my root was lost...
Il tryed several times to get it back patching boot.img from Magisk.. (canary version included), but when I install patched.img my phone does not start and i have to get back to boot.img
Any ideas?
Click to expand...
Click to collapse
Hi,
Boot your F3 into fastboot mode and connect to a PC,
Download "Temporary Recovery" and unzip, run the "RUN ME Temporary TWRP A13-Orange Fox Recovery.bat" file and choose TWRP.
Once rebooted select: Advanced from within TWRP and tap "Flash current TWRP", copy over the included Magisk files into the internal memory (I use a OTG adaptor and USB Stick), install Magisk V26.1.apk, when in recovery you can install Magisk as a .apk format.
Included are the files i use when switching between roms, included are the latest, Magisk V26.1 and Magisk Delta, it also includes the latest versions of TRWP/OrangeFox recovery and other goodies,
I hope it helps
It's possible that the MIUI 14 update may have caused compatibility issues with your previous root method. You could try using a different root method or a different version of Magisk. Additionally, make sure you are following the correct steps for patching the boot.img file and installing it. If the issue persists, you may need to wait for an updated version of Magisk or seek assistance from the Magisk community.
you can try patching Boot.img instead of flashing Magisk.zip
you can do a OrangeFox/TWRP Backup of Boot-partition and patch the resulting "boot.emmc.win" file in Magisk App, because it's actually just a normal partition-image.
then flash the magisk-patched image file.
no pc required. just a custom recovery.
you can try the new Magisk v26.1, or Magisk Alpha (not affiliated with official Magisk).
i use Magisk v26.1 Official but I'm on AOSP