I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!
marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??
Related
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
MAGISK modules are HERE
Magisk MANAGER is available on PLAYSTORE
BEFORE making a twrp backup... (after data format ect.)...
you may want to FIX the huawei theme manager not working problem for some of us... the FIX is HERE
Thanks to Henkate
Youll need a good file system manager...i'm using ROOT EXPLORER and theres that new FX file explorer
does it work with android 7?
tanlikar1 said:
does it work with android 7?
Click to expand...
Click to collapse
Yes. In fact, this was meant for Android 7, but it should work on Android 6 too.
Absolutely...Im on Nougat emui5
does anyone have stock rom for MLA-L12C636B340 ?
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
virusdunil said:
Do you mean original firmware ?
Maybe you can still get it via firmware finder...
Click to expand...
Click to collapse
ya
Working on Nova?
Does it work in the non plus Nova as well? Any experiences?
Worked on Can-L11. Tested. No need format data, in twrp tree, i add img, that work with encrypted data.
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Cooks_08 said:
I can't get this to work on my MLA-03, i have TWRP installed and unlocked b/l. I tried to flash RR and Lineage but getting "can't mount" errors up the ying yang. Anyone with MLA-03 got any tips? Is there a certain recovery that is recommended?
Click to expand...
Click to collapse
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
virusdunil said:
hi...yes and its a bit confusing...but,just follow instructions for LOS install...forget about /mount data and after flashing ,just reboot
Click to expand...
Click to collapse
Got the flash working. Used Garak's Twrp and now i got. Thanks.
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Mezo21 said:
Does it work for android 8.0 or Huawei nova 2s in particular? I did make unlock the bootloader, but i could not find reliable root method. Please help with advice. Thank you.
Click to expand...
Click to collapse
Hi there,
I have Nova 2s, carefully follow this thread's instructions, it will 100% works : https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Thanks for the guidance, Magisk is doing very well.
Only TWRP is missing, but later.
Huawei Nova
CAN-L01C432B382
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
meskafonas said:
Magisk modules not working even if i rooted. Cant install modules from magisk app and twrp .zip
Click to expand...
Click to collapse
did you format data as f2fs? If yes, magisk doesn't go well along with it. If no, then you would get better support at magisk thread
virusdunil said:
Yes,its working...
REMOVE ALL OTHER ROOT...working or not befor installing magisk....may end with....something you dont want...
Maybe it would be best to start with a freshly factory resetted phone.... (anyway,to erase all errors in TWRP,youll format/data so... )
you need bootloader unlock... followed instructions HERE don't forget to OEM UNLOCK in /settings/Developer section on phone..(enable it while pressing repeatedly on Phone version (in ''about phone also in settings)
You need MINIMAL ADB on pc...HERE
You need TWRP recovery installed...HERE
but before doing all that...BE SHURE to have the original UPDATE.APP (firmware from huawei) somewhere on your pc
you will need the BOOT.img from your original firmware... (extract it from the update.app (update.zip for huawei firmware)
HERE
extract the boot.img somewhere on your pc... like on your desktop...
then,youll need 2 magisk things...
the LATEST magisk ZIP file...
and the LATEST MAGISK APK...
FOLLOW THESE INSTRUCTIONS (from Magisk post...i did it and its working :silly: )
Installation Instructions
If you already have Magisk installed, you can directly upgrade through Magisk Manager
For installing Magisk the first time
Make sure to remove any other root, best to restore your boot image back to stock
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
the ADB method is the best...
after reboot,in magisk app,youre supposed to be GREEN checked....
after that,if all green,you can FIX that DATA problem in TWRP...saying cant mount or blablabla...
DO a backup cuz yess,youll loose everything... Hisuite for your apps
in twrp, FORMAT DATA... ...wipe data factory reset...re install your things then,youll be able to do recoverys ect. in twrp
dont forget to RE INSTALL magisk APK after formatting and factory reset
IT WILL take some time TO BOOT... so let it do its thing...
Now about magisk modules...all of them ive tried ended in (blablabla not a magisk module)...
no big deal....just dload the zip and look for the app or file in it... and apply to where it belongs... like new Oreo Emojis...ive dloaded the zip,found the file, then paste the file in /system/fonts...then reboot
now...if i made a mistake somewhere in my explanations well... sorry....
WARNING
IF youre device is bricked or what so ever... its not MY fault....you do that on your own......Ive done it,followed MAGISK instructions and its working....
Not shure about it...DONT DO IT....
DON'T DO TWRP backups with fingerprints/nip/code unlock methods activated on your phone... i had to factory reset phone cuz code was not working.
YES there's a way to recover anyway... THANKS HENKATE
Regarding fingerprint, boot in recovery and go to advanced > file manager and delete data/system/locksettings.db
Then advanced > terminal and type:
cd data/system
rm -rf *.key
Then reboot and you won't have secured lockscreen
Click to expand...
Click to collapse
Do you have this problem with fingerprint? [emoji853] https://r.tapatalk.com/shareLink?ur...share_tid=3907398&share_fid=3793&share_type=t
Enviado desde mi HUAWEI CAN-L11 mediante Tapatalk
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
Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.
so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself
So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)
Hello, can someone help me with a detailed guide to flashing TWRP on my LG g820n. I'm kinda new to all this.
kofisefa30 said:
Hello, can someone help me with a detailed guide to flashing TWRP on my LG g820n. I'm kinda new to all this.
Click to expand...
Click to collapse
I can give you an overview of how to / why do it. But it would be much easier if you mentioned which android version you're running, and then find a copy of that boot loader with twrp already injected.
twrp is no longer in it's own recovery partition, so 'flashing' it is not the same. It has to be ram disk injected into the boot partition. To do that, you actually need the / a device with twrp already working, as it's an option in twrp to ramdisk inject the twrp image.
In some cases, if you have a version of fastboot that will boot certain versions (that are bootable) of twrp, then you can use it to do the 'ramdisk' inject twrp.
As said, mention the version of android you are running, the boot partitions with twrp are around for all of them.
Whew, I didn't think I could know any less .
Anyways, I'm running Android 11.
kofisefa30 said:
Whew, I didn't think I could know any less .
Anyways, I'm running Android 11.
Click to expand...
Click to collapse
So what you'll have to do, to use the attached zip file, is to be; 1) rooted, 2) use magisk manager to create the boot partition with magisk installed, 3) use qfil to flash the newly created boot partition with magisk (be sure to save off your original boot partition first), 4) flash the attached zip file with magisk manager which will inject twrp into boot partition.
You'll get a message after doing above saying you're now 'unrooted'. But to fix that just use twrp to flash magisk zip.
AsItLies said:
So what you'll have to do, to use the attached zip file, is to be; 1) rooted, 2) use magisk manager to create the boot partition with magisk installed, 3) use qfil to flash the newly created boot partition with magisk (be sure to save off your original boot partition first), 4) flash the attached zip file with magisk manager which will inject twrp into boot partition.
You'll get a message after doing above saying you're now 'unrooted'. But to fix that just use twrp to flash magisk zip.
Click to expand...
Click to collapse
If I'm already rooted and trying to get TWRP for flashing ArrowOS, is this what I should do?
Flash TWRP with magisk > flash ArrowOS with TWRP > Flash magisk with TWRP > Reboot?
And does any of this require modifying the abl_a.bin file again to get into fastboot mode or can it all be done on device?
BWA_Dallas said:
If I'm already rooted and trying to get TWRP for flashing ArrowOS, is this what I should do?
Flash TWRP with magisk > flash ArrowOS with TWRP > Flash magisk with TWRP > Reboot?
And does any of this require modifying the abl_a.bin file again to get into fastboot mode or can it all be done on device?
Click to expand...
Click to collapse
I'm not familiar with the process for installing after market roms, look in the guides section or even better, follow the info that's specific to arrowOS, there should be some doc available.
AsItLies said:
I'm not familiar with the process for installing after market roms, look in the guides section or even better, follow the info that's specific to arrowOS, there should be some doc available.
Click to expand...
Click to collapse
These are the instructions given
Boot TWRP
Make backups
Tap Install -> Select Rom zip
Go to reboot menu -> Select opposite inactive Slot
Reboot recovery
Now in Arrow Recovery
Factory reset
Apply Update -> Flash Magisk if any
Reboot system now
I'm just confused on the TWRP part as the first step is to boot TWRP and that's what I'm confused about. The only guide I see on here for installing TWRP is for the sprint version.
I also see some people talking about different GSI related things and some don't mention it all, I'm a bit confused with it all haha
I am trying to Unlock my bootloader, Install TWRP then install Magisk for the customizations. I connected my Mi Account on my phone, and I have to wait 5 more days from the 7 days wait period. Meanwhile I was wondering If there were any simple tutorials for Installing TWRP out here, or any specific channel/video you guys would recommend for my phone. which I can watch and prepare myself, while I wait.
I checked YouTube, there are a few good tutorials there, but they each do a slightly different method, or they mention that all the Xiaomi phones will have the same method but go on to mention that "for this specific X phone you will have to do slightly differently" and that's where It gets confusing.
I don't want to end up bricking my phone in the process, that's why I was looking to ask directly in the forums so I can get more relevant suggestions, rather than just watching a YouTube follow along video which the channel owner doesn't check comments on.
Any suggestions, recommendations welcome
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
percharnel said:
Suggestion before flashing the ROM you need to read the whole page of the ROM because it's the number one thing that people missed up and bricking their phone because they don't read the whole post. Also backup your data.
Click to expand...
Click to collapse
I'm just tryna install Magisk as the end goal. No plans for ROM currently. But thanks for the suggestion nontheless. Something to keep in mind in case I change my mind later
My advice for you is as follows:
Let TWRP go and don't use OpenGApps.
Use the things that are working flawlessly.
Take LOS Recovery instead of mighty, but outdated TWRP,
Take MindTheGApps instead of highly customizable OpenGApps.
(Think about LOS as your custom ROM).
I used to use both together with my Mi 8. But installing LOS, the recovery and GApps on my Poco F3 was possible within round about an hour. All this went well, while I watched Netflix and cuddled a beautiful woman on her Sofa. By the way - I had to install ADB and divers on her Surface Laptop at first.
Hi,
You could check out My Beginners guide post:
Also a Very important Note, "NEVER RE-LOCK YOUR BOOLOADER" with a custom recovery or Custom Rom installed, as this will BRICK your device and you will have to pay to get it unbricked.
The Re-lock could happen when you use the MIFlash Tool and select "Clean all and Lock".
.
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
cyanGalaxy said:
SDK Platform Tools (ADB & Fastboot): https://developer.android.com/tools/releases/platform-tools
Xiaomi USB Driver: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
(link source: https://developer.android.com/studio/run/oem-usb)
OrangeFox Recovery: https://orangefox.download/device/alioth
Notes:
-During BL-Unlock, your phone will auto. factory reset.
-Unlike on many AOSP-ROMs, using a Custom Recovery on MIUI will cause OTAs to not work anymore as the MIUI Update relies on MIUI Recovery. Instead you have to manually flash each MIUI-update in your Custom Recovery.
-I'm suggesting OrangeFox Recovery, because it never failed me personally, and because it's simply much more modern than TWRP.
-On MIUI, Magisk (by default) will cause you to fail Google SafetyNet, which means Banking Apps, Netflix, and many other apps won't work. You will have to spoof Attestation to "Basic" by using a Magisk Module that changes the fingerprint. And you'll have to hide Magisk from Play Services (.gms and .gms.unstable specifically) and user-apps that check for Magisk/Root.
Boot to Fastboot Mode (Power + Vol Down),
extract "recovery.img" from OrangeFox.zip,
Open Terminal inside Platform-Tools folder and do "fastboot boot <path_to_recovery.img>"
To install OrangeFox, go to its Menu and tap "Install current Recovery" (something along those lines)
To install Magisk, you can rename Magisk.apk to Magisk.zip and flash it in Custom Recovery (only TWRP or OrangeFox!, other recoveries may not be able to install anything other than the ROM ZIP file). It's the easy method of getting Magisk, however flashing Magisk.zip in Recovery isn't supported anymore by TopJohnWu.
Recommended way is to obtain the boot.img and patch it with the Magisk App. I personally do a Boot Backup with OrangeFox Recovery, patch the backup file, and restore the magisk-patched Boot file with OFox.
My break is over, so I'll have to cut here, but I think I have my socials linked in my profile. if you need more help you can message me privately on TG
Click to expand...
Click to collapse
I'm considering to switch from latest TWRP 3.7.0_9-0 to OFR R11.1_3_A12 on my old dipper. But that dosn't play a role here, because I have some general questions about it that are the same for alioth.
Just want to try it out and see, if it's really so much better than TWRP like lots of people tried to tell me in the last years...
So may I ask you some vital questions?
1. From what I understood, it should be possible to flash OFR easily through my already installed TWRP on the device, right?
2. Which decryption methods does the A12-Branch of OFR support? A12 only or A11+A12 so that it's possible to dirty flash from A11 to 12?
3. In OFR there's an inbuild (and easy to handle?) direct management of the preinstalled Apps, right? This could be avery interesting feature for me, especially with regards to the slowly dying OpenGApps-Project that was imho the best way to customize GApps over the last few years...
If you are a visual learner just watch them carefully, watch the suggestions above they work great, works perfectly on OFOX too