Related
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is oppo neo 7 android 5.1
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Didgeridoohan said:
The boot image is a part of your device's software. It's what Magisk modifies to do it's thing. If the installer can't recognise it, there's not much you can do... Except providing logs, that is.
The update binary is a part of the installer. It's the script that modifies the boot image to install Magisk on your device.
When you have these kind of errors, save the recovery log after flashing the zip (Advanced -> Copy Log) and post that (attach it or use Pastebin or similar, don't copy it directly to the post). It's so much easier to troubleshoot with proper logs.
First thing you can try is to use the latest beta and see if that works.
Click to expand...
Click to collapse
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
rajoholic said:
i got the log, how do i upload it here? im only using android browser.
so itried to install magisk v14 and it didnt detect bootimg but v14.5 did detect but still failed to install.
Click to expand...
Click to collapse
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Didgeridoohan said:
I guess you can't attach a file, being so new... You can upload it somewhere and provide the link or use Pastebin and provide the link/id for it.
Click to expand...
Click to collapse
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
I m also facing same problem
rajoholic said:
after reformatting my device and flashing stock rom through twrp, i went and download the zip file with magisk manager latest version and then i fully unroot my device with full unroot of supersu. after i rebooted to twrp, i installed magisk v14 zip and this is what it tells me after i flashed it.
Installing '/sdcard/Magisk-v14.0.zip...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
************************
* Magisk v14.0 Installer
************************
- Mounting /system, /vendor, /cache, /data
- Device platform: arm
- Constructing environment
! Unable to detect boot image
- Unmounting partitions
E: Error executing updater binary in zip ' /sdcard/Magisk-v14.0.zip'
Error flashing zip ' /sdcard/Magisk-v14.0.zip'
Updating partition details...
...done
i have few questions.
1. unable to detect boot image. what do you mean by that? where can i get this boot image?
2. what's that updater binary in the zip file?
what can i do to be able to use magisk? thank you in advance
my device is Micromax canvas nitro a310 current android version is cyanogen mode 13
Click to expand...
Click to collapse
rajoholic said:
https://dropmb.com/download/aca1616df3f0d913cb70d1f88176d9d4.html
here it is. thanks for the help
Click to expand...
Click to collapse
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
sorry bout that. i just search the google free and temporary storage online. haha! thank you for the help. I'll try what u just said
Didgeridoohan said:
That was a bit of a shady file sharing site. Anyway...
Your installed TWRP is pretty old. That might have something to do about it. Update TWRP, or you could try letting the Magisk Manager patch the boot image and then flash the patched image with TWRP. Installation instructions in the release thread.
Click to expand...
Click to collapse
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
rajoholic said:
how do i flash the patched boot.img with twrp? i cant find it in my sd card. it's not showing up. i already got the patched boot img
Click to expand...
Click to collapse
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Didgeridoohan said:
Hm.... It might be that your TWRP is to old, but it should be the same procedure as when flashing a zip file except you switch to image flashing by pressing the "Image" button after going to the "Install" screen.
If that doesn't work, use fastboot (or whatever is available for your device).
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
rajoholic said:
So I did what u told me and flashed the boot.img succesfully. Now after flashing that, I flashed v14 and still error in executing update binary. Same with 14.5. But this time after I saw that, I rebooted my device and found magisk manager on my phone. It says v14 installed. Is it installed already?
Click to expand...
Click to collapse
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Didgeridoohan said:
Yes, if you flash the patched boot image you don't have to do anything else. The Magisk Manager has already taken care of everything.
If you want v14.5 beta, you should now be able to change the update channel (in Manager settings) to beta and update. Just as a FYI, you could have done this already when patching the boot image.
Sounds like it's working now, or? Can you install modules?
Click to expand...
Click to collapse
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
rajoholic said:
I installed an app and gave it root permission. It looks like it's working. However the module part, I'm still unsure. When I try to add modules, the screen took me in storage. Looks like it requires me to import something? Where can I download modules?
Click to expand...
Click to collapse
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Didgeridoohan said:
First of all, don't even mention that piece of piracy software on xda. It's used to steal from developers and is not allowed here.
In the "Modules" part you can manually install modules that you've previously downloaded. If you want to install directly from the Magisk repo, you (unsurprisingly ) go to the "Downloads" section of the Manager. If you can't see "Downloads", make sure the Manager has internet access.
Click to expand...
Click to collapse
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
rajoholic said:
Sorry I didn't know. What I had in mind is that I'll give u all the details without leaving none so u know what I do and be able to help fast. Anyway, again I'm sorry. I didn't mean it.
I tried to dl greenify4magisk and I successfully download and install it. Rebooting the device now
Click to expand...
Click to collapse
Sir, did you manage to install? when i tried to install log is failed.
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
I
blitzball said:
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
Click to expand...
Click to collapse
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
zgfg said:
I
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
Click to expand...
Click to collapse
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
blitzball said:
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
Click to expand...
Click to collapse
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
zgfg said:
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
Click to expand...
Click to collapse
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
blitzball said:
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
Click to expand...
Click to collapse
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
zgfg said:
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
Click to expand...
Click to collapse
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
blitzball said:
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
Click to expand...
Click to collapse
TWRP backup that can be restored through TWRP (Restore option in TWRP)
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Thanks man. I'll go ahead and install magisk
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Dude so I installed it with no problems but I still can't pass safety net
blitzball said:
Dude so I installed it with no problems but I still can't pass safety net
Click to expand...
Click to collapse
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
zgfg said:
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
Click to expand...
Click to collapse
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
blitzball said:
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
Click to expand...
Click to collapse
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
zgfg said:
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
Click to expand...
Click to collapse
I have Netflix now. It's weird though cause only after maybe ten or twenty minutes did it show up in my store. Still can't buy anything though google still detects my phone for some reason. Thanks anyways.
Disclaimer: Your warranty will be void, use at your own risk. YOU are choosing to make these modifications and I am not responsible for any damages these changes might do to your device or sanity.
Hi.
Based on the feedback from this thread, the following steps can be used to aquire root on the SM-T590. The process is quite similar to rooting other devices by using Magisk. It might also work on other versions of the SM-T59x family, which can be OEM unlocked (sorry Verizon users).
Obtain the boot image
Get the firmware that matches the version installed on your device. This is important, otherwise you can easily end up in a bootloop.
Extract the AP tar.md5 file, e.g. "AP_T590XXU2ARJ1_CL14463952_QB20043720_REV00_user_low_ship_MULTI_CERT_meta.tar.md5".
Upon the extracted files, there is a file called boot.img.lz4. Extract it. Important: Most standard compression tools, e.g. 7-zip, are unable to extract lz4 compression ccorrectly. Use the offical lz4 binary from your Linux distribution or get the Windows version here. Once extracted, you should have a file called boot.img.
Patch the boot image
Copy the boot.img file to your device.
Download and install the Magisk Manager apk from the offical Magisk Thread.
In Magisk Manager settings, set the image format to "img.tar".
Enable the "Keep AVB2.0/dm-verity" in the Magisk main screen.
Hit "Install" and select "Patch boot image".
Select the boot image copied previously to your device.
Once finished, the patched image will be located in the Download directory on the internal storage.
Copy the patched image back to your PC.
Unlock and flash
Go into settings and enable developer settings.
In the developer settings, select OEM unlock, read the help text and enable the unlock, if you consent.
Once the device is factory reset and rebooted, turn the device off.
Boot the tablet into download mode.
Flash the patched boot image with Odin in the AP-slot
Reboot, Install Magisk Manager apk again and check if root is available.
Have fun.
Thanks to @gscollier, @airmaxx23 and @EinsamerSpieler for testing.
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
J.Edwards(not the killer) said:
Rooting works but having the same problem as the others. Modifying system files leads to reboot.... damn
Click to expand...
Click to collapse
did you find a solution?
stupid question
I know this is a dumb question but where do you get the firmware....
Also was wondering if that reboot thing is still an issue.
I'll still root, I would like to try the LineageOS, eventually... how well does this work with Android apps/F-droid?
Update: still looking for confirmation on which boot image to use... guess you can't do a backup before flashing like you used to be able to do.
I installed heimdall and adb both seem to work
heimdall instructions
User848 said:
Yes, there is such problem.
I have Root Explorer app installed
When I try to move some app from "/data/app" to "/system/priv-app" (using Root Explorer) the device reboots and nothing is being saved at "/system/priv-app"
I want to make my app a system one
This method works ok on many other devices
Any ideas how to solve this problem?
I think system apps Device Security and Device Maintenance prevents me to do it.
I tried to delete them using Titanium Backup but phone reboots and they are installed again
Also there is Samsung Knox security technology
Click to expand...
Click to collapse
the same happens to me.
I also tried removing some microsoft apps with Titanium, but after removing the excel, it goes to a kernel panic...
And then there's the "Security notice" from "SecurityLogAgent" notifications (unauthorised actions have been detected, unauthorised access to a secured area)
any solutions, followed steps but no root
I have the same problem Root is present but once i try to rename a file in /system/app, the device reboots.
Using SM-T590 with canadian image:T590XXU2ASC1
Using Magisk version V7.1.2(208) - V19.1 (19100)
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Quick help please, I have the patched boot image on my pc but when I click the AP slot on odin it doesnt detect it only finds tar, md5 files etc. in the settings i cant change the format to .tar there is no option.
IET_DEMO said:
I Found this procedure inside git magisk code:
https://github.com/topjohnwu/Magisk/blob/master/docs/samsung.md
Follow the Instructions part and it should work.
Click to expand...
Click to collapse
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
mingkee said:
Be advised it's for Android 9 (Pie)
You can try to patch entire AP file, but I was told 19.1 may have problem. Try 18.0 first and see.
Unfortunately, there's no TWRP at this time
Click to expand...
Click to collapse
Well I did it on android 8.1.0, seems like it work on Oreo too
IET_DEMO said:
Well I did it on android 8.1.0, seems like it work on Oreo too
Click to expand...
Click to collapse
How about Titanium Backup?
It works on rooted T510
mingkee said:
How about Titanium Backup?
It works on rooted T510
Click to expand...
Click to collapse
I dont have or use Titanium Backup, I usually clone my devices with twrp backup
There needs to be a better option that works without the current issues when rooting. You either end up with reboots or can not log in to Samsung account at all
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Would it work on 595? Bootloaders should be the same without boot loop?
vq8acsxht said:
Would it work on 595? Bootloaders should be the same without boot loop?
Click to expand...
Click to collapse
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
kidkrooks said:
I honestly don't know as I don't have a 595. I took a chance on mine and it worked
Click to expand...
Click to collapse
Mine is on it's way. I will try it when I get it. I think bootloaders should be same in in both 590/595.
kidkrooks said:
For anyone who needs it, here's the latest tar for both stock boot and the magisk patched boot. works in Pie.
Click to expand...
Click to collapse
Does this still have "Modifying system files leads to reboot" issue or it's solved ?
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Thanks, works great.
Daniehabazin said:
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Click to expand...
Click to collapse
Can you provide download links and instructions on how you have rooted EMUI 9.1 mate 20 pro.
I tried to root, but unable to mount few partitions. I have formatted "/data" using TWRP but still unable to flash magisk. After mutiple retries able to flash magisk with some errors mentioning about error in mount. Then my mobile keeps on rebooting and going to erecovery. Am on EMUI 9.1.0.300
adaway is working fine for me.
side_flip15 said:
adaway is working fine for me.
Click to expand...
Click to collapse
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
sharath91221 said:
Can you provide download links and instructions on how you have rooted EMUI 9.1 mate 20 pro.
I tried to root, but unable to mount few partitions. I have formatted "/data" using TWRP but still unable to flash magisk. After mutiple retries able to flash magisk with some errors mentioning about error in mount. Then my mobile keeps on rebooting and going to erecovery. Am on EMUI 9.1.0.300
Click to expand...
Click to collapse
there is no difference rooting 9.0 or 9.1, you do it the same way.
well, with the exeption that directly after factory reset you have to flash the recovery_ramdisk, if you let the phone boot up without the modified recovery then android messeges stops working.
so the step is simple, install 9.1, if your phone is messed up use the hstool or erecovery, hstool was faster for me.
get yourself a patched recovery_ramdisk from 9.1 (i did this myself by extracting the ramdisk and patching in magisk on my phone when i was still on 9.0)
before first boot, enter fastboot and flash the recovery_ramdisk.
boot with volume up, and then profit.
for more information check: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Daniehabazin said:
there is no difference rooting 9.0 or 9.1, you do it the same way.
well, with the exeption that directly after factory reset you have to flash the recovery_ramdisk, if you let the phone boot up without the modified recovery then android messeges stops working.
so the step is simple, install 9.1, if your phone is messed up use the hstool or erecovery, hstool was faster for me.
get yourself a patched recovery_ramdisk from 9.1 (i did this myself by extracting the ramdisk and patching in magisk on my phone when i was still on 9.0)
before first boot, enter fastboot and flash the recovery_ramdisk.
boot with volume up, and then profit.
for more information check: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
You used patched_recovery_ramdisk.img from 9.0 on 9.1 or you have extracted recovery_ramdisk from 9.1 and then patched it using magisk?
If you have extracted recovery_ramdisk.img from 9.1, can you provide me the link?
sharath91221 said:
You used patched_recovery_ramdisk.img from 9.0 on 9.1 or you have extracted recovery_ramdisk from 9.1 and then patched it using magisk?
If you have extracted recovery_ramdisk.img from 9.1, can you provide me the link?
Click to expand...
Click to collapse
i extracted the ramdisk from 9.1.0.310 and patched it in magisk on my phone. i'm unable to share the file right now because i'm on a trip right now but i'll be back on monday. but it's easy to patch it yourself, just extract it with huaweiupdateextractor and transfer it to your phone.
Daniehabazin said:
i extracted the ramdisk from 9.1.0.310 and patched it in magisk on my phone. i'm unable to share the file right now because i'm on a trip right now but i'll be back on monday. but it's easy to patch it yourself, just extract it with huaweiupdateextractor and transfer it to your phone.
Click to expand...
Click to collapse
Great. Thank you Daniehabazin :good:. I will download 9.1.0.310 using firmware finder app and extract UPDATE.APP using hauweiupdatextractor and use magisk to patch ramdisk.
sharath91221 said:
Great. Thank you Daniehabazin :good:. I will download 9.1.0.310 using firmware finder app and extract UPDATE.APP using hauweiupdatextractor and use magisk to patch ramdisk.
Click to expand...
Click to collapse
sounds good, hit me up for the patched ramdisk if you can't get it to work and i'll upload it on monday.
have a lya-l29c432 but the firmware i downloaded was for lya-lgrp-ovs, i guess it covers several hardware versions
Daniehabazin said:
sounds good, hit me up for the patched ramdisk if you can't get it to work and i'll upload it on monday.
have a lya-l29c432 but the firmware i downloaded was for lya-lgrp-ovs, i guess it covers several hardware versions
Click to expand...
Click to collapse
After factory reset, I have flashed patched ramdisk.img from 9.1.0.310 and while rebooting press and hold vol+ button, it is going to "press power key to continue, press volume up key..." thing. If i reboot and press vol- key again it was going to "press power key to continue...."thing. Magisk app still shows it was not installed.
Off topic for rooting... There is already a thread for that with patched recovery img 9.1 and procedure for rooting. 9.1...(search my posts) To return to subject of this topic, what is missing and why I don't use energized it's because it don't have blocklist GoodbyeAds (Google ads)
Also you can use private dns in network setting and put dns.adguard.com in it, but in my case that break mms so...
---------- Post added at 10:58 PM ---------- Previous post was at 10:56 PM ----------
Daniehabazin said:
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
Click to expand...
Click to collapse
Wrong, it's only "/system" and "/" r/o. Subfolders are r/w (ie /etc /cache...)
Daniehabazin said:
on 9.1?
with 9.1 huawei intruduced a new file system that is read only.
Click to expand...
Click to collapse
Take a look at my screenshots. I got something like storage error at first. Adaway worked after I debloat and systemize app using magisk module. Not sure if it's related but works for me three times already. Those two modules actually alters files on /system without any issue. Worth trying...
sharath91221 said:
After factory reset, I have flashed patched ramdisk.img from 9.1.0.310 and while rebooting press and hold vol+ button, it is going to "press power key to continue, press volume up key..." thing. If i reboot and press vol- key again it was going to "press power key to continue...."thing. Magisk app still shows it was not installed.
Click to expand...
Click to collapse
Trick is not to send command on fastboot to reboot. After flashing recovery_ramdisk successfully remove the usb cable then press and hold power + volume up buttons. Release them when you see the yellow text warning saying "your device is booting now..."
side_flip15 said:
Trick is not to send command on fastboot to reboot. After flashing recovery_ramdisk successfully remove the usb cable then press and hold power + volume up buttons. Release them when you see the yellow text warning saying "your device is booting now..."
Click to expand...
Click to collapse
I found an another way. After flashing patched ramdisk and after reboot if it shows "press power key to continue.." thing. Go to erecovery and then go to factory wipe. It does not actually wipe the phone, it simply reboots and turn on with magisk installed.
Now am unable to install exposed or core. If i install them, mobile is stuck at boot
side_flip15 said:
Take a look at my screenshots. I got something like storage error at first. Adaway worked after I debloat and systemize app using magisk module. Not sure if it's related but works for me three times already. Those two modules actually alters files on /system without any issue. Worth trying...
Click to expand...
Click to collapse
oh, ok.
because i also got the storage error and on the thread for p30 pro rooting i saw that adaway doesn't work, checked the p30 forum because they got their phone with 9.1.
i'll try adaway again, but i also kinda like the feeling of running a terminal on my mate 20 pro
Adaway is working just fine here in LYA 9.1.
But Energizer should be also fine.
oslo83 said:
Adaway is working just fine here in LYA 9.1.
But Energizer should be also fine.
Click to expand...
Click to collapse
Yes if systemless host is enabled. This is the trick. You can use all ad blocker apps.
Daniehabazin said:
Found a way to get adblocking back on rooted emui 9.1.
in magisk settings enable systemless hosts
then in downloads, search for "busybox for android NDK" install that, then search for "energized protection" and install that too, then reboot
in a terminal emulator type "su" and allow the terminal emulator to run as root.
Then to configure the adblock just type "energized"
let it do it's check and then you have several options, first you have to choose the pack
i usually go with basic (4)
after applying, exit with q and type reboot in the console.
after reboot check some website with known ads and enjoy
for more information check out Github: https://github.com/Magisk-Modules-Repo/energizedprotection#usage
Or Energized website: https://energized.pro/
Click to expand...
Click to collapse
Great work, just did it and it works. Have been busting my head for a week now without Adaway. Thanks man!
adaway just works fine on 9.1
Fairly newbie user here. I'm looking for a guide that lists how to upgrade the P5 to a new firmware and keep Magisk and all of that. I've looked at the thread below and it is good for getting started up in the beginning, but I'm not following how it works for a new firmware.
[Tutorial] Unlock Bootloader, get root and valid Safetynet
04/09/21 v2 Just install this Module via magisk manager: https://forum.xda-developers.com/attachments/hardwareoff_1-1-zip.5058405/ which is mentioned by this thread...
forum.xda-developers.com
Like how do I flash the new February firmware onto my phone?
Do I then copy the boot.img to the P5 and patch it with Magisk?
Then do I copy the patched boot.img back to my PC and flash it back onto the P5?
Are there are new step or process for unlocking SafetyNet?
I'm just very confused and would appreciate something simple and basic to follow, please.
Thanks!
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
UPDATING Pixel 5 Factory Image & Re-Rooting
Why This Thread? I have seen several questions on the process for updating a rooted Pixel 5, since the existing guides only explain the unlock and initial rooting, I thought I'd throw together a quick HOW TO on UPDATING and Re-Rooting for...
forum.xda-developers.com
You can bypass safetynet perfectly with hiddencore module for xposed.
HiddenCore Module | Xposed Module Repository
repo.xposed.info
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
hanni2301 said:
Xposed is dead since Android 10 and higher, so forget about the post of VD171. Sorry if I#m wrong with that, but never heard of working xposed on Pixels (with newest firmware).
This will work definitely fine. Don't mess with uninstalling Magisk as whole application, just disable the modules. Otherwise it will cause bootloops.
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
hanni2301 said:
I also wonder, why I can not first patch the boot.img and insert the patched version back in the .zip archive and only have to flash then once with flash-all? So no rebooting and flashing of the boot.img would be needed? Does someone tried this? I was to tired because of slow internet and have had to reflash the january boot.img to quit my bootloops.
It would only timesaving and you may don't need to disable the magisk modules. that is my hope of doing this. Otherwise just follow cesmans posting.
Click to expand...
Click to collapse
I have tried few years ago, in some previous version of android, instead of running flash-all.bat, I flash each image individually, (fastboot flash bootloader..., fastboot flash boot..., fastboot flash recovery.... etc. ). If I took the shortcut of not flashing the original boot image first and then the patched one, but flash the patched boot directly, then the phone run into a bootloop.
cescman said:
1. Download the rom, extract it and copy boot.img to phone, patch with magisk then copy the patched file to computer
2. Disable all magisk modules and reboot
3. Remove -w from flash-all.bat, copy all the files in the ROM to where the adb files are located, reboot to bootloader and run flash-all.bat
4. Reboot to bootloader and flash the patched boot image
5. Reboot and enable magisk modules
6. Reboot
Click to expand...
Click to collapse
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
VD171 said:
My friend, you can find a huge a mount of videos about it in youtube.
Adb is NOT for flashing.
Taken care or you can damage your device.
You need to READ and learn first, before to try anything.
If you try to search it, certainly you will find it.
Click to expand...
Click to collapse
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Ewto16 said:
Thanks, I appreciate the advice. I was able to follow the initial tutorial on how to setup my phone the first time, but it is well written out step by step. The other guides I've seen for upgrading just sort of breeze through the steps, assuming you know what you are doing.
My phone actually updated to the February release today, which broke my Magisk and lost me my Props configurations. I just want to get those things back.
Click to expand...
Click to collapse
Next time, don't flash the factory image. Sideload the OTA.zip instead. That way you won't lose any of that.
Sideload the OTA, flash the patched boot.img (the boot.img you need to get from the factory image though), and you won't lose Magisk, your modules, or your root settings.
I used to do the same. Edit out the -w flag from the flash-all and re- setup my phone. Sideloading the OTA is easier and quicker in the end.
Ewto16 said:
1. Can I just do all of the file movement through Windows Explorer?
3. What command do I run? Like do I have to run ADB something before I run flash-all.bat?
4. What is the command for that? Is it ADB flash boot.img?
Sorry, I don't know and understand a lot of the commands and how you get it to work with the phone.
Click to expand...
Click to collapse
1. Yes
3. Edit the flash-all.bat file with any editor, e.g. notepad in windows, you will see -w near the end of the file, remove it, then save and run the file. You must make sure the -w is removed, otherwise all the data will be wiped
4. To boot into bootloader: adb reboot bootloader
To flash the patched boot image: fastboot flash boot magisk_ patched.img (the file name changes every time, just use the one you have when you patch the boot image)
It's easier to replace the "-w" with "--skip-reboot" (first one is double dashes). The phone won't reboot when the image flashing is complete so you can immediately re-flash the patched boot img.
This youtube video is great to follow and has clear step by step guide.
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Ewto16 said:
Thanks for the help and tips everyone. I really appreciate it! I was able to get my phone updated and re-rooted.
The only issue I'm having now is that I can't use GPay for contactless payments. When I go to try and use GPay, i get a slashed out line through the contactless payment symbol. It doesn't let me do anything with it from there.
I am on the Feb update, with Magisk installed, and the Universal SafetyNet Fix 2.0.0 module installed. I also have the MagiskHide Props Config module loaded. I pass the SafetyNet Check, but I can't do contactless payments.
I have Magisk hidden from GPay as well.
Any thoughts?
Click to expand...
Click to collapse
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
swangjang said:
Have you actually tried to use your phone at a pay terminal?
My device also passes safetynet but has contactless crossed out. However, it still works at payment terminals.
Click to expand...
Click to collapse
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Ewto16 said:
I have not attempted to use it yet. I just assumed that it wouldn't work since it was crossed out. I will have to give it a try.
Click to expand...
Click to collapse
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
swangjang said:
On my device, I uninstalled the Google pay app and used the built-in "cards and passes" that shows up when you long press the power button.
Click to expand...
Click to collapse
Interesting....I thought those were one and the same. Thanks for the tip. I'll give that a try.
I'd still like to get GPay working again though.
VD171 said:
Xposed and Xposed modules are working perfectly on ANDROID 10.
So forget about post of hanni2301, lol
Click to expand...
Click to collapse
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
hanni2301 said:
And the Pixel 5 is on ANDROID 11.
So forget about post of VD171, lol^2
Click to expand...
Click to collapse
Grow up, my friend.
Anything can changes from device to device.