Related
Greetings!
The latest beta (v14.1) of Magisk just dropped (Magisk Beta Thread), which is the first release to officially support Pixel (XL).
Before I spend more time investigating TWRP and Magisk combination, please refrain from flashing Magisk through TWRP installed in your boot image (because Magisk cannot get a 100% stock boot backup)
The recommended way to install Magisk on Pixel (XL) are
Fastboot boot this TWRP Image, and flash the Magisk zip
Get a stock boot image (download the full factory image here), and patch via Magisk Manager, then flash the patched boot by fastboot
Once you got over the ""initial pain" and get Magisk installed with proper stock boot image backup, it is very easy to migrate Magisk across OTA updates on Pixel devices.
This thread is not a support thread, all bug reports should be in the Magisk Beta Thread, discussions should be in Magisk General Discussions
------------------------------------------------------------------------------------------------
The followings are for Pixel (XL) developers:
I've written some descriptions on how Magisk works on Pixel devices in my Release Notes for v14.1.
You can directly check MagiskInit's code here. The code is fairly simple so you should get the idea.
However, I'm still fairly new to Pixel development, and I'm not sure how current custom roms and custom kernels workaround the skip_initramfs thing. Instead of trying all custom roms and custom kernels out, I think it would be easier for me to just open a thread and ask
I would like to have some insight from developers whether my Magisk solution can work well with current Pixel development projects. Since all my work is open source, if you have some suggestions to improve my work, please tell me and I'll be really grateful.
I've been waiting for this for a long time.Thank you.
Yaaay! Thank you! I've been waiting for official
Keep up the good work, and congrats!
Works fine here " Android 8.0 "
ElementalX + Magisk 14.1 + Twrp 3.1.1-0 ( Twrp Sticks ) Root also works.
Thanks OP!!!!
WOOOOT WOOOOT
Tylog said:
Works fine here " Android 8.0 "
ElementalX + Magisk 14.1 + Twrp 3.1.1-0 ( Twrp Sticks ) Root also works.
Click to expand...
Click to collapse
How did you flashed them what is your Order ?
I literally booted into recovery (via fastboot) nandroid backed up my boot partition and then flashed magisk so if anything goes wonky I have a backup
tessut said:
How did you flashed them what is your Order ?
Click to expand...
Click to collapse
Stock Boot img , TWRP , MagisK , reboot .
Back to recovery
ElementalX , TWRP , MagisK , reboot.
Done.
Hello
I am currently on stock , so for me the steps will be :
Fastboot TWRP , install Magisk and reboot
Reboot to recovery
EX kernel , TWRP, Magist and reboot
Correct ?
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
I'm still on a custom rom based on 7.1.2 and all i had to do is flash magisk 14.1 zip using twrp RC2. Everything works fine. Had to manually install magisk manager tho.
chowtom said:
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
Click to expand...
Click to collapse
No problem here was 8.0 stock latest installed 14.1 and everything works.
If i'm already rooted and on Su and SuHide, how does one go about installing Magisk
Rockstar! Nice to be certified once again...
Thank you
---------- Post added at 01:13 PM ---------- Previous post was at 01:08 PM ----------
Nexus6pMyPhone said:
If i'm already rooted and on Su and SuHide, how does one go about installing Magisk
Click to expand...
Click to collapse
Hello,
Follow the instructions on the SULite site for removal and also uninstall the SU app itself. Download the full September Oreo zip and remove the -w from the bat file. Then execute the bat file from bootloader which will flash the full Oreo image. This will give you a new boot image that is not rooted and one Magisk can patch.
Cheers
chowtom said:
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
Click to expand...
Click to collapse
Yep, worked fine after flashing rom then magisk. Rebooted to flash EX kernel, after coming back magisk manager said it wasn't installed. Rebooted, flashed magisk again, came back and I had no mobile network connection, and my wifi connection appeared to work fine but in actuality nothing loaded. Also, camera was totally blank.
Update: Magisk 14.2 (just released) seems to fix issues with networking and camera. Running EX and Magisk together without issue, except...
SafetyNet check in Magisk shows both checks as false, and I can confirm as I'm unable to sign into snapchat lol.
One more update: Netflix and root checker behave how they should with Magisk hide enabled, but SafetyNet test, Magisk's SafetyNet checker, and Snapchat don't. Have tried turning off USB debugging, Magisk Hide box is checked, and SELinux is Enforcing. Just trying to be thorough with info I give.
Are you able to use the sky go app with Magisk 14.1 on the Pixel? Suhide fails to hide root from sky go
any one have the issue where you don't have magisk manager installed after flashing 14.2? or am i doing something wrong?
[email protected] said:
any one have the issue where you don't have magisk manager installed after flashing 14.2? or am i doing something wrong?
Click to expand...
Click to collapse
you have to download and install the apk separately
EDIT: hm... not seeing a download for the 5.3.5 version of the app :S
EDIT 2: https://github.com/topjohnwu/MagiskManager/releases
there should be version 5.3.5
WarningHPB said:
you have to download and install the apk separately
EDIT: hm... not seeing a download for the 5.3.5 version of the app :S
Click to expand...
Click to collapse
yup, I didnt see it either so i assumed it must install apk while flashing like it used to.
i dont see any apk to download and i dont see anything mentioned about this.
attaching recovery log. hope it helps @topjohnwu
[email protected] said:
yup, I didnt see it either so i assumed it must install apk while flashing like it used to.
i dont see any apk to download and i dont see anything mentioned about this.
attaching recovery log. hope it helps @topjohnwu
Click to expand...
Click to collapse
apologies i edited my post a few times you might not have seen the second one there's a download link on the git hub
EDIT 2: https://github.com/topjohnwu/MagiskManager/releases
there should be version 5.3.5
Click to expand...
Click to collapse
Hello all
Its been a while since I used root or flashing but few weeks back I heard about "magisk" and wanted to give it a go.
I came a cross 2 issues:
1.My device showes up as uncertified in google play store
2. Safenet check shows ctsProfile and basic integrity as FALSE
Here is what I did with my device:
1. Unlocked my device by using fastboot oem get_unlock_data and fastboot unlock xxxxxxxxxxxx
2. Downloaded TWRP and installed it via fastboot flash recovery twrp-3.1.1-0-griffin.img stared it right away
3. Installed magisk 14.0 by using twrp (one zip file)
4. rebooted the phone
When I start magisk I get msg that update is available but when I press update nothing happens.
I hid google play store in magisk and cleared google play data but device still comes up as uncertified.
Allow Unknown source is enabled
What do I need to do in order to get my device certified again and pass safenet check ?
All input in regards to mentioned issue are greatly appreciated.
I use the stock rom by erfanoabi (ErfanROM).
All you have to do is to flash that ROM and magisk.
After that you should have a tweaked stock rom with root.
You should also pass safenet.
Thank you for your comment.
I would like to resolve this issue with out flashing another rom, stock rom is more then enough for me.
Hello, do you think that it could be possible to use xposed and magisk on that stock Rom by Erfan?
Sent from my XT1650 using Tapatalk
castra said:
When I start magisk I get msg that update is available but when I press update nothing happens.
Click to expand...
Click to collapse
Give Magisk storage permission
I also did something like you on my phone but google play working perfectly, Maybe this module helps you:
https://forums.oneplus.net/threads/magisk-module-fix-google-play-certification-status.535634/
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
jbonlinea said:
Hi,
I'm a happy new owner of the redmi note 4 and I've already unlocked the bootloader.
I would like to use google camera, and eventually adblock.
I've seen there are various way to
- install bootloaders (and it seems there are also various boatloaders)
- root the phone
- enable camera2 api, with and without root
- ...
Actually I like to keep the stock rom and the phone as vanilla as possible, as I've read there are redundant issue with custom rom. I also do like the idea of being able to update the phone "normally", which seems to be what you call OTA update . Also, I've seen that some app may not work if some verification fails ?
So basically the question could you explain me a bit the broad picture and what would you recommend ?
Thank's
PS : sorry I'm not super acurate, I rooted my LG G2 years ago and things seems to have evolved a lot since then.
Click to expand...
Click to collapse
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
I am using pixel experience 8.1 oreo rom in my redmi notr 4.and i have also install google canera mod.mgcmod5.i have done all the settings but ehen i am trying to take puctures its force closing and lagging..need solution..
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
After every OTA update do I need to re-flash everything?
ÀnkanKoley said:
After every OTA update do I need to re-flash everything?
Click to expand...
Click to collapse
If RedWolf succeeds OTA survival, then there is no need. But after OTA if RedWolf is replaced by stock recovery, then yes you'll have to flash everything once again. Refer RedWolf thread for more details on OTA survival.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
jbonlinea said:
Sounds right and great, thank's !
Two question.
- I've read somewhere that some custom recovery and/or root may cause some app to fail, notably banking app.
Well I used to use such app on my rooted G2 , but will it remain posible after folowing the process you suggest above ?
about redwolf, there is quite a lot of explainations in theses two links 1 and 2, however I can figure out how to install redwolf ?! what am I suppose to do with the .iso image available for download ? isn't there a step by step install guide somewhere ?
Thank's
Click to expand...
Click to collapse
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
ArK96 said:
So, you want root and GCam working on your MIUI without breaking OTA updates, is that right?
• Unlock bootloader, flash RedWolf recovery then through Redwolf recovery flash LazyFlasher.
• In Redwolf enable OTA survival.
• Flash Magisk through recovery for root.
• For GCam to work, you need to enable Camera2API in your build.prop. This can be done through a simple Magisk module too. But I must warn you enabling Camera2API on MIUI might break some functionalities of your MIUI stock camera app.
Click to expand...
Click to collapse
What would broke on miui camera?
amnher said:
What would broke on miui camera?
Click to expand...
Click to collapse
The HDR mode.
ArK96 said:
Use Magisk for root and once Magisk is installed enable Magisk hide for the banking app, this will hide root from that particular app.
Installing a custom recovery like redwolf :
1. Unlock your phone's bootloader.
2. Download the recovery image file, rename it to "recovery.img" and place in a folder on your computer. Make sure you have working ADB and fastboot drivers installed on this computer.
3. Connect your phone in fastboot mode (Volume Down + Power button)
4. Open command prompt in the folder containing the downloaded recovery. (Shift + Mouse right click)
5. Type the below command into the command prompt
fastboot flash recovery recovery.img
fastboot boot recovery.img
Once inside recovery flash ROM, Magisk, if ROM is MiUI flash lazyflasher too, or phone won't boot. If custom ROM ignore lazyflasher and flash GApps instead.
If recovery installation instructions confuse you there are infinite number of YouTube videos that will help you.
Click to expand...
Click to collapse
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone
jbonlinea said:
Thank's again , that's awesome!
Maybe a few more question
FIRST
at step 2) how do I make sure I have a working ADB and Fastboot drivers ?
As far as I understand, fastboot drivers should already be installed ; however I suspect ADB not to be installed.
Indeed, I've already unlocked the bootloader with this tutorial, and I can confirm the phone is unlocked from settings > more settings > developper options > Mi locking status.
So basically I've already installed MiUSBDrivers and ran miflashunlock. There are fastboot.exe, fastboot_unlock.exe and AdbWinApi.dll files in the miflash_unlock folder I downloaded and used to unlock, but I haven't used any of these later 3 files.
I have found this post to install ADB
SECOND
at step 4), the best would be to place the recovery image downladed from here into the folder containing ADB downloaded just above right ?
Then, go on with step 5)
THIRD
If everything went well, my phone is supposed to reboot in redwolf recovery, ok.
but whart do you mean by "Once inside recovery flash ROM" ?
Why am I suposed to flash a rom ?
To my understanding, I already have a rom, miui, and do not want to change for the moment.
Should I download the "Full Rom" from here, or the "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File" rom from here ? If so, what souhld I do with the rom; where sould I place it, on the computer, on the phone ?
Or do I need to flash ROM only if I want to change/upgrade my rom ?
FOURTH
To flash Magisk and Lazyflasher.
I understood that redwolf recovery comes with Magisk, so I assume I'll only have to go to "install" tab of redwolf, and I'll find the Magisk file to flash.
Ok what about Lazyflasher ? is it also provided with redwolf ?
Or should I download it ? and if so where should I place the file ?
FIFTH (and last)
I assume once installed from recovery, Magisk will show himself as an app/icon on the "desktop", and I'll be able to selectively enable Magisk hide for the banking app.
Thank's again for your help.
Sorry if I have too many questions, I'm a little rusted, and prefer having a comprehensive picture of the porcess before jumping into it, and avoid one more post entitled helpppp pleeeeeese I bricked my phone pen
Click to expand...
Click to collapse
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
ArK96 said:
ADB/Fastboot Drivers
Looks like you don't have ADB/Fastboot installed system wide. Although it is completely fine to use adb/fastboot in a folder, installing it system wide is much more convenient because you can open a command window in any folder and execute ADB/Fastboot commands. [URL="https://forum.xda-developers.com/showthread.php?t=2588979”]Here's the link[/URL] to download the system wide installer. Install it and REBOOT your PC.
Flashing RedWolf
Once drivers are installed and PC rebooted, connect phone in Fastboot mode and follow my previous instructions. Also now you can open command prompt in any folder and execute the commands since ADB/Fastboot is installed system wide.
Flashing ROM
Sorry if I confused you there in the previous post. If you wish to stick with your current MIUI ROM then you don't need to flash any ROM file.
Flashing Lazyflasher
You MUST flash lazyflasher since you want to stay with MIUI. If you install a custom recovery on MIUI without flashing lazyflasher, the phone will not boot and will be stuck at the MI logo. I've attached the file.
Flashing Magisk
Flash Magisk after lazyflasher. You may download the latest package from Magisk thread or use RedWolf's built in Magisk package as you said and update it later through the Magisk manager app. And yes, you can select which apps can be Magisk hidden.
Click to expand...
Click to collapse
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
jbonlinea said:
Awesome !
Great to know that I should fisrt flash lazyflasher and then magisk.
Stupid, probably last question
Should I do everything up to and incliding flashing lazyflsher, rebot normally, and then reboot again in redwolf and flash magisk ?
of is this extra zealous ?
Thanks
Click to expand...
Click to collapse
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
ArK96 said:
While it can all be flashed at one go, I suggest you to flash LF and once boot your device successfully and reboot to redwolf and flash Magisk afterwards.
Click to expand...
Click to collapse
Thank you very much !
jbonlinea said:
Thank you very much !
Click to expand...
Click to collapse
No problem.
ArK96 said:
No problem.
Click to expand...
Click to collapse
hum, :silly:
the link you sent for adb do not work
jbonlinea said:
hum, :silly:
the link you sent for adb do not work
Click to expand...
Click to collapse
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
ArK96 said:
Here,
https://www.dropbox.com/s/mcxw0yy3jvydupd/adb-setup-1.4.3.exe?dl=0
Click to expand...
Click to collapse
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
jbonlinea said:
Excellent !
so
- I did installed redwolf recovery - changed settings as advised here
- flashed lazyflasher
- reboot -> wokrs I'm back on miui
- reboot in redwolf and flashed magisk
- reboot into android, installed rootchek, I'm rooted
- hide magisk from magisk manager for my apps --> working
Everything works
Further questions :
- Am I suppose to clean cache at some stage ? I can still do it now ?
- Is there some recomended module for magisk ? (not sure what they are for)
- as for everything else, I've seen many options to enable camera2api. Which one would you recomend ? is "persist.camera.HAL3.enabled=1" the only needed change or this treat rises something this
- is there a recomended version/release of google camera to use with miui9 global, latest update (not developper) (I've seen various reported issues depending on version/release)
- any other must/nice/interesting hacks to fully enjoy this phone ?
- any security recomendation ? (re-locking the bootloader ? instally some utilities... ?)
thanks
after that, I'll be done
Click to expand...
Click to collapse
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
ArK96 said:
Clean cache not required.
Magisk modules are MODs for your system but they are done without tampering your system. (Systemless MODs).
Try Dolby atmos ZTE Axon 7 audio MOD module, YouTube vanced module (100% Adfree, background play)..etc
Use Arnova's GCam.
Never ever relock bootloader with a custom recovery or custom ROM. Else irreversible brick.
I've repeated too much stuff that has been posted in the forum already, if you have any further doubts search the forum or use Google.
Flash through redwolf the attached file to enable camera2api. If you want to uninstall it later go to magisk manager and delete it.
Cheers.
Click to expand...
Click to collapse
Hi dude
I'm almost done but back to square 0, with blinking black screen at boot !
No crisis, I can still go to redwolf recovery, as well as fastboot.
How it happend ?
In magisk manager (on miui) I checked what modules were available in the download panel, and tried "Google Pixel 2 Experience" or something similar.
On reboot, the mi logo is displayed, then I have a black screen blinking on and off, without mi logo, just black, on and off
I thus wanted to unistal the mod with magisk module uninstaller, but the install fails and return that "magisk is not installed" and "magisk is required for this mod"
So I obviously couldn't try to uninstall the supposed failing module
I thus rebooted in redwold and installed magisk from redwolf (the included release), things went well
However, I still cant install magisk module uninstaller, getting the same error as above.
I took my chance and try to re-install magisk from the zip filed I downloaded, the install process was successfull, but I still can't install magisk mod uninstaller, and the black screen issue persist.
Lastly, I took my chance and try to re-install lazy flasher, the install process was successfull, but the black-screen issue persist.
To be honest, I'm a bit sctuck now.
What may be the right procedure to solve this problem ?
Am I screwed and do I have to reflash a whole rom ?
If so Should I do it from redwolf, and how ?
Or should I do it from the pc with fastboot, and how ?
Thanks for your directions
ps: i was interested by pixel 2 experience module as at it was written that it was compatible with mido and provides camera2api, which might have been a nice combo.
ps 2 : I also did installed dolby as you suggested, it worked but the demo crashed to app
ps 3 : I also did installed youtube vaccant, but I couldn't see any new app and my original youtube still had add and couldn't play in the back... not sure it reveals something on the effectiveness of magisk...
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Good job. thanks you, i wait updates
Elkingb said:
magisk app-debug.apk working, but boot.img from
Model Number : SM-A217M
Region Code : COB
Device Version info :->>
BL version : A217MUBS5CUE2
AP version : A217MUBS5CUE2
Click to expand...
Click to collapse
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
DKXC said:
Forgot to mention that I used the latest DBT boot image for SM-217F/DSN. Not sure if it works for other models, but there aren't really many models anyways.
Click to expand...
Click to collapse
For SM-217M Working full
everything is fine for the SM-217F
Im waiting for the twrp so much Good job!
To DKXC:
Hi There Expert,
I Would Recommend You To Upload Your Project To Github,
So Everyone Will Be Able To Give You Feedback
It Will Probably Help You In Developing A Better A21s Community
LonelyCracker said:
Github twrp a21s
Click to expand...
Click to collapse
Flashing this patched_magisk_v23\boot.tar ain't working.
Error displayed on the DL screen:
Only official released binaries are allowed to be flashed (BOOT)
My specs:
Loading ADB module.............OK
Starting ADB module...OK
Searching for SAMSUNG ADB device...OK
Checking device authorization...OK
Reading ADB device information...
ADB Serial Number : R58R52BFNKP
Model Name : SM-A217F
Device CodeName : A21S
Hardware : EXYNOS850 EXYNOS850
Modem Board : SHANNON318
HW Version : MP 0.500
BL version : A217FXXU5CUD6
AP version : A217FXXU5CUD6
CP version : A217FXXU5CUD4,A217FXXU5CUD4
CSC version : A217FOXM5CUD6
Android version : 11
Build date : Thu Apr 29 11:41:41 +07 2021
Country : Poland
IMEI : 35xxxxxxxx691
Serial Number : N/A
Carrier : XEO
Unlock by IMEI : Unknown
SIM State : ABSENT,ABSENT
Debug Level : 0x4f4c
CP Debug Level : N/A
Warranty VOID : 1
SIM operator : N/A
USB Settings : MTP,ADB
SamKEY Team (2017)
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
Decoded the boot.img.lz4 file using LZ4 tool:
Copied boot.img file to the phone internal memory.
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Go to Options tab and disable "Auto Reboot", make sure "Re-Partition" is also disabled.
Aaand it fails again.
And the message in phone DL mode says:
Only official released binaries are allowed to be flashed(boot)
Perhaps vsmeta.img also needs to be included into the tar file?
No idea how to move on with this subject.
skazi.chris said:
Installed app-debug.apk (patched Magisk) onto the phone.
Downloaded original XEO firmware.
Samfw.com_SM-A217F_XEO_A217FXXU5CUD6_fac.zip
Unzipped it.
Found AP file inside unzipped folder:
AP_A217FXXU5CUD6_CL21209953_QB39896814_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS11.tar.md5
Unpacked the AP file.
Contents:
View attachment 5336407
Decoded the boot.img.lz4 file using LZ4 tool:
View attachment 5336525
Copied boot.img file to the phone internal memory.
View attachment 5336527
Opened Magisk and patched the boot.img file, which created magisk_patched-23001_nmETW.img in the phone Downloads folder
View attachment 5336541View attachment 5336543
Copied patched file (magisk_patched-23001_nmETW.img) from the phone to my laptop - and changed its name to boot.img
Compressed it into boot.tar file using 7zip.
View attachment 5336545
Restarted the phone into DOWNLOAD mode (using SamKey, or adb, or key combinantion, whatever).
Put boot.tar into AP section in ODIN.
Vá para a guia Opções e desative "Reinicialização automática", certifique-se de que "Re-Partição" também esteja desativado.
View attachment 5336551
Aaand ele falha novamente.
View attachment 5336553
E a mensagem no modo DL do telefone diz:
Apenas binários lançados oficialmente podem ser atualizados (boot)
View attachment 5336559
Talvez o vsmeta.img também precise ser incluído no arquivo tar?
Não tenho ideia de como seguir em frente com esse assunto.
Click to expand...
Click to collapse
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
To skazi.chris :
Try Unchecking Re-Partition
Jukmisael said:
Edit3: Use MiracleBox to pass the Prenormal you have to Checking, I had this problem on J7NXT, and I made this post to help.
Edit4: Full AP patch on Magisk, and use full patched on Odin.
First with Unlock, go to developer options and activate Unlock Bootloader, restart in download mode, Press the Vol UP button, if reset only, do it again, Download->VolUP Mode, until formatting, In download mode, with all Unlock, go to Odin. Now with the Magisk patched file modified for the A21s, the entire Magisk .tar, you don't need to unpack boot.img.lz4, After this it is normal to start, it will give you an unlocked system alert, just press the Power button to continue, then an Unofficial System warning will appear and just wait A few seconds it starts normally (first boot takes considerable time)
Some tips:
-With V23 use LsPosed to use Xposed framework, Edxposed has infinite log bugs, which causes conflict and slowdown.
-For SatefyNet, Use MagiskHide only apps needed to avoid unnecessary processes, install Universal SatefyNet Fix module, Only this gets through SafetyNet, you don't need to install additional modules for SafetyNet, it will just slow down the system.
For those who use Lucky Patcher:
-Use in LsPosed, and activate it for System Framework and Play Store, you don't need to activate for each app, it will only slow down. Use CorePatch to go through the signatures as Lucky Patcher cannot do this function on Android 11. Use Lucky Patcher with LsPosed as LP Patch's are not compatible with Android 11 But LSPOSED does, so it can work just fine.
For those who use Game Guardian:
-It is best to use a Virtual System, as its functions on Android 11 are limited as it is not 100% compatible.
All I have from my own experience is:
-Avoid redundant modules as much as possible, as they can affect the battery and the System.
Click to expand...
Click to collapse
Patching the entire TAR with patched Magisk did the trick. Thank you very much!
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
DKXC said:
Patched Magisk v23 for A21s (A11/OneUI 3)
Since I've seen and tried installing Magisk via the default instructions from the legend topjohnwu himself, I noticed it does not work at all. The phone
just doesn't even boot into Android at all, and after researching I have seen that this is a very specific problem with the phone itself due to weird implementation from Samsung.
Extremely simplified, apparently there is a conflict with skip-initramfs because of System-as-Root and the A/B system partitioning introduced with Project Treble. I will still have to read more into it.
There are already patched Magisk apps/images for this phone available, but I noticed they are not really in active development (last patched Magisk was still v22), so I pulled the latest Magisk from the official repository and implemented the fix from this pull request on the official repo. They are not interested in accepting the pull request, so we'll have to do our own "Magisk" for the time being.
I will try to update this as much as possible and try to incorporate fixes, user feedback and more. This has been only tested on latest A11 and OneUI 3. I will also start working on TWRP soon.
Since the APK isn't signed yet, please uninstall Magisk Manager if present, and install this one. It will display a warning when installing, but don't worry.
Options to install:
Flash boot.tar from the ZIP in Odin on AP
Install the APK from this thread and patch your own boot image
Click to expand...
Click to collapse
Haha thank you so much bro it worked for M12 too I took the apk file and flashed
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Are you sure you unlock Bootloader?
[How To] Unlock Bootloader
How To Unlock Bootloader A21s. *** Disclaimer I am not responsible for any damage you made to your device You have been warned - Go to Settings -> About phone and find your build number. - Tap on your build number 6 times until you see...
forum.xda-developers.com
====#####=======
In relation to the topic, I think that this one will also be abandoned. Eagerly waiting for a developer to look at the A21S/M12 to finally get Magisk working without a patch
Olep84 said:
Did this solution also work on the latest SW update?
I tried all, but Stuck at ODIN prism.img
when I use the Magisk tutorial
How to Root Samsung Galaxy A21s using Magisk (Android 11)
Samsung Galaxy A21s is a budget smartphone with great features and decent performance. But there are some limits to what the phone can do without rooting
magiskapp.com
i get the error Only official released binaries are allowed to be flasehd (boot)
Relock/Unlock Bootloader is necessary, then it work with patching the complete AP file
thanks for the tips
Click to expand...
Click to collapse
Have you used the patched magisk or official one; see official one doesn't work on a21s and m12 i was getting that error before but it solved by using patched one see the first post and download the .apk
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
dbreed53 said:
I have the SM-A215U. I get the impression this method won't work for me.
I have Developers Options, but do NOT have the OEM option in that menu.
Is there anyway to unlock it without that menu item?
Click to expand...
Click to collapse
No idea
I have a Alcatel U3 4055T phone (same as TCL 4055T) and I have tried all the simple methods (PC/APK …Kingroot, kingoroot etc) of rooting it with NO SUCCESS. It has Android 6.0, Baseband MT6737M, 3G/LTE. Now I have thought of trying rooting it manually, I have read online and figured out that I might need do as follows:
(1( UNLOCK the boot-loader
(2) FLASH a custom Recovery (TWRP)
(3) EXTRACT Boot image from the phone
(4) PATCH the image in (3) with Magisk
(5) FLASH the patched image back to the phone
I have just successfully unlocked the boot-loader BUT I can find any version of TWRP or any other custom recovery to FLASH into my phone. I have tried all suitable TWRP(s) that I could find online with no success.
PLEASE help me out in rooting my phone … any help from the members and admins will be highly appreciated.
This is to inform that I have successfully rooted this phone using Magisk and now I can enjoy all those apps which require root. I wish to thank the makers of Magisk ... this was simple and straightforward . BUT I I still have stock recovery.
Hello friend can you share the details, I just installed Magisk but cant find any option to root.
sorh said:
Hello friend can you share the details, I just installed Magisk but cant find any option to root.
Click to expand...
Click to collapse
What is the model number of your phone??
sorh said:
Hello friend can you share the details, I just installed Magisk but cant find any option to root.
Click to expand...
Click to collapse
Well … the method I had used only applies to devices with MTK chips. The Best part is that the device only gets rooted after boot && running a script. Means if you wish to keep it un-rooted (for some reasons) you can also do that. The package contains 2 apks and one of them is “magisk” … and other is “mtk-easy-su” install both , you only have to run the later and it will execute magnisk. You can also tic the box for automatically root at boot. Here is the package: https://offlinemodapk.com/mediatek-easy-root-apk/#more-3134
To run those kinds of application, you need the Magisk Manager app if you have a rooted device. By enabling the magisk hide on the app, you would able to run whatever application you need, which cannot work on rooted devices. Becric