Last update: 14.10.2017
Fantastic news
No more waiting for manually signed magisk, supersu or twrp versions from now on. Just install any new version and use the image signature fix action in the troubleshoot menu of the toolkit. :good:
Next level reached
No more waiting for special zenfone 2 patched xposed for magisk. Got my own zip to do some hex patching. You can either use one of the (already patched) xposed versions from the toolkit or download xposed for magisk and use the xposed patcher in the troubleshoot menu.
z00x users please read this post https://forum.xda-developers.com/showpost.php?p=72298931&postcount=214
Introduction
This is a windows batch toolkit for automated actions like bl unlock, flash, root, xposed, sideload tasks, ... for your ze551ml/ze550ml/zx551ml.
I hope you find it useful. Check the tabs above for more screenshots, downloads, review ...
Note:
This tookit works well for a lot of situations, but I need feedback especially for the new supported devices ze550ml and zx551ml. Please go on and try the toolkit, then leave a message on this thread, do a review or just vote.
Before you try any action in the menu, check that the device informations are shown.
Features
Supports ZE551ML, ZE550ML, ZX551ML
Device status and connection information
Automated actions
Bootloader unlock
Flash boot/recovery images (twrp, stock)
Fix wrong or missing image signatures!!
Root / unroot Magisk & SuperSU
Xposed for Magisk (install / uninstall)
Patching xposed for magisk for zenfone 2 (if installed the unpatched xposed for magisk by mistake)
Compatible with most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
Currently integrated Tools
v14.0 (default) and v14.2
SuperSU 2.79SR3 / 2.82 (default) / 2.82SR5
TWRP 3.0.3-M4 / 3.1.1 (default)
Xposed for Magisk v87.3 / v88.0 (default)
Stock boot/recovery support of most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
adb/fastboot 1.0.32 (optional: 1.0.36)
Installation instructions
Do a clean start:
Download the latest base package
Extract to your desired location. It will extract a "ze551ml toolkit" directory with all files.
(Optional / If the automatic download of the device specific files fails) Download the device specific packages and extract it directly to the "ressources" directory
To run the toolkit just execute "ze551ml toolkit.bat" (no admin rights are needed).
Usage instructions
Prerequisite:
Ensure that you have installed device usb drivers (e. g. see: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )
Ensure that you have one of the latest MM firmwares for your device installed.
Ensure that you have enabled USB Debugging in Developer Options
Even if only a few actions could be really harmful to your data: Get a backup!
Then:
Run ze551ml_toolkit.bat
Check device status information & see if toolkit really likes your device
If your bootloader is still locked: Unlock it first with menu B -> choice U
(Optional) Choose your desired versions of the integrated tools in menu O.
(Recommended) Flash twrp with menu F -> choice T. If you want to try a newer twrp version, change it first in menu O
Check all the other nice functions of the toolkit
Downloads
Main: xda devdb archive
Mirror 1: https://mega.nz/#F!u8JhhY7T!9PryiRdjVSFf-O4erijDWg
Mirror 2: https://drive.google.com/drive/folders/0B4r2bJ3AgndSRVl5djNPNV9Qbkk?resourcekey=0-i9dHUezdzckVemi93NlYLA&usp=sharing
File structure:
ze551ml-toolkit-<VERSION>-base.zip - contains the base toolkit package without any device specific files
z00a*.zip - contains all device specific files for Z00A (ZE551ML)
z008*.zip - contains all device specific files for Z008 (ZE550ML)
z00x*.zip - contains all device specific files for Z00X (ZX551ML)
Changelog
Code:
[B]v1.3[/B]
Current changelog: 14.10.2017
[added] xposed for magisk v88.0
[new] Patching xposed for magisk for zenfone 2 (if installed the unpatched version by mistake)
Code:
[B]v1.22[/B]
Current changelog: 08.10.2017
[added] magisk v14.2
[removed] magisk v13.3
[fixed] xposed for magisk v87.3
[new] Fix wrong or missing image signatures!!
[fixed] Better support for encrypted devices
Code:
[B]v1.1b9[/B]
Current changelog: 22.09.2017
[added] magisk v14.0
[removed] magisk <v13.3
[removed] twrp 3.0.2-M1
[updated] magisk uninstaller
Code:
[B]v1.1b8[/B]
Current changelog: 19.07.2017
[added] magisk v13.3
[updated] magisk uninstaller
[new] action to download latest mirror file which is used to get some stock files updates
Code:
[B]v1.1b6[/B]
Current changelog: 13.07.2017
[added] magisk v13.2
[removed] magisk v13.1
[fixed] twrp detection
[modified] magisk manager will now be extracted from zip and installation will be forced after sideload
Code:
[B]v1.1b5[/B]
Current changelog: 11.07.2017
[added] magisk v13.1
[removed] magisk v13 betas
[fixed] minor fixes in supersu actions
Code:
[B]v1.1b3[/B]
Current changelog: 02.07.2017
[added] 2 magisk v13 beta versions
[removed] magisk <v12
[updated] xposed installer
[added] 2 more twrp versions
[fixed] hardened detection of installed twrp version (still needs root or already booted twrp for that)
[fixed] changed the way the toolkit downloads files
Code:
[B]v1.0b10[/B]
Current changelog: 04.04.2017
[added] magisk v12.0
[updated] fixed some help messages
Code:
[B]v1.0b8[/B]
Current changelog: 21.03.2017
[added] support for more devices: z00a, z00d, z00x
[added] automatic download for device files if needed
[added] magisk v11.6
[added] twrp 3.0.3-M4 (for encrypted devices or android n installations
[added] backup efs function
[added] integrity check
[modified] menu structure
[updated] changed some help messages
Code:
[B]v1.0b2[/B]
Current changelog: 14.02.2017
[modified] menu order
[disabled] usage of system installed platform tools, internal are forced now
[fixed] boot2recovery could have been failed in some cases
[fixed] timing problems in wipe routine
[added] validations added to each boot states
[removed] twrp 3.0.3.2
[adjusted] code / function names
Code:
[B]v0.9[/B]
Current changelog: 07.02.2017
[added] new twrp 3.0.3.2
[added] new magisk v11.1
[disabled] second disclaimer
[disabled] bootloader status in device overview at the top as I haven't found a secure way to detect a locked/unlocked bootloader yet.
[removed] magisk v10.2
[removed] twrp 3.0.3-N
Code:
[B]v0.7[/B]
Current changelog: 02.02.2017
[added] boot to safe mode
[added] wipe menu
[added] new twrp 3.0.3-N and platform tools 1.0.3.6 (no default yet. versions can be switched in troubleshoot menu for testing)
Code:
[B]v0.5[/B]
Current changelog: 31.01.2017
[added] each action shows some information about what's going to happen now
[changed] each action must be confirmed to be executed. if you don't need that, enable auto-yes in troubleshoot menu
Code:
[B]v0.3p1[/B]
Changelog: 28.01.2017
[fixed] added missing magisk manager to installation procedure
Thanks to/Credits
Code:
:: > shakalaca
:: > chainfire
:: > topjohnwu
:: > twrp
:: > social-design-concepts
:: > phhusson
:: > say99
:: > Deathschythe33
:: > ggrandou
:: > gerasiov
You'll find more credits inside the source code.
I hope i didn't forget anyone. If so please report.
XDA:DevDB Information
Zenfone 2 ToolKit [Z00A/Z008/Z00X], Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Stable
Current Beta Version: 1.3
Beta Release Date: 2017-10-14
Created 2017-01-28
Last Updated 2018-07-31
Reserved
Reserved
What makes this different with @Giovix92's tool?
Yes, same question as above. What makes it different from ZE55xML_Modder by Giovix92
@krasCGQ @fred_gaou
i think that main difference is that this toolkit supports the last 3 MM firmware versions and works automatically for all tasks, so user interaction is reduced to wait & perhaps read
@rummsbumms
Question 1: would you suggest to run ze551ml_toolkit.bat as admin or not?
Question 2: did you personally test all root method provided by toolkit: SuperSU, Magisk+SuperSU, Magisk+phh superuser? Did you succeed to properly unroot all of them? Will you suggest one method rather than another?
Question 3: did you test custom ROM install via TWRP such as last LineageOS after unlock bootloader and install TWRP with your toolkit?
Question 4: What is "Auto Packages" supposed to mean? What does it do? According to script code, it seems to unroot and restore stock bootloader. That's why I don't understand the Auto Packages term.
====
To avoid having to get always the same questions like
How to root for the 1st time or safely upgrade firmware and root again…?
How to get back to a clean stock device?
What does this menu entry really do?
etc.
I would suggest some guide lines to help users in the 1st post as well as in a "how to.txt" file along the toolkit or in the batch itself as a menu entry named "Help" or "FAQ" or else.
====
FEATURES REQUEST
# Add FACTORY RESET DEVICE menu entry. This will imply:
Code:
fastboot erase userdata
fastboot erase cache
# Add Erase /system, /data and /cache menu entry, may be useful before installing a ROM. This will imply:
Code:
fastboot erase system (I guess it will work only if bootloader have been unlocked)
fastboot erase userdata
fastboot erase cache
or a complete wipe that will format the partitions too
Code:
fastboot -w
# Add a way to Back up and restore EFS, see this thread.
# And +1 to the post below about ifwi.
====
I would suggest also in the 1st post as well as in a "how to.txt" that the functions be more detailed. Example:
I see you chose to use adb/fastboot 1.0.32 version. Just to let you know that Minimal ADB and Fastboot v1.42 provide a more up to date adb and fastboot (the last 1.0.36). Why do you use this old 1.0.32 version?
====
I didn't test ZE55xML_Modder by Giovix92 or this toolkit yet, but just by reading the batch file, I can tell your code is way more elegant and skilled and should avoid the magisk root bug that ZE55xML_Modder users encounter.
====
And why checking if ADB is installed as system-wide since your toolkit already provides local adb/fasboot ? What's the point to add this "unnecessary" step ?
====
Great Work ! :good:
I will test your toolkit very soon and give feedback. I hope to get answers from you in the meantime.
Regards
What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
@fred_gaou
You gave some nice questions&suggestions!
About your questions:
You don't need the batch to run as admin as I don't use any function that needs admin rights.
Yes, I've tested all root functions and switched between single supersu, magisk with phh and magisk with supersu, but of course always with running the unroot task first. my personal favorite is magisk with phh b/c of the magisk hide. that's what i need for some banking apps :angel:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
The other points:
Giving more guidelines/hints in this thread&toolkit is a good point. I'll try to add this as soon as possible. :good:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
timbernot said:
What would be ideal , if possible to add
Is ..
An ifwi version detector
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
Click to expand...
Click to collapse
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM
rummsbumms said:
Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
Click to expand...
Click to collapse
Well, I'm still on stock LP so I would not be a good adviser. I trust the experienced users that switch and update ROM weekly so they will give useful feedback soon. Since some guys on LineageOS used Giovix modder to unlock bootloader and install ROM via TWRP, I guess it's currently the way to go.
rummsbumms said:
The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
Click to expand...
Click to collapse
I get it now. It could be a useful section in future to run sequential commands at once.
rummsbumms said:
Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
Click to expand...
Click to collapse
Yes it is wise. I just provided the command because it was implemented in Giovix Modder and often reported as a way to clean up before flash all stock in other device. Don't know for 551.
rummsbumms said:
I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
Click to expand...
Click to collapse
Detail is good to know. What OS do you use: 7, 8.1 or 10? If 1.0.32 works fine on every version, there is no point to risk to break anything using 1.0.36.
Thanks for your answers.
rummsbumms said:
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Click to expand...
Click to collapse
Thinking about it now a bit more , it maybe tail end for this problem .
The actual problem people were having was they thought they had cm13 with M BL , actually they had the LP bootloader cm13 . They would be in a working system then flash 14.1 / 7.1 builds then , brick their devices .
They forget they never upgraded bootloader and with having 6.0.1 M in build information in settings, presumed they had upgraded bootloader at some point but didn't .
Maybe , to prevent the tail enders from performing such tasks again , maybe a simple addition like a warning , like build date which in cm 13 , to check.. if before July 2016 and have IFWI version 0094.0173 unlocked . Then you could direct them to say a return to stock option , flashing back boot and recovery for say on 551 LP 2 20 40 .196 Version , then possibly install the full ROM from say a link or something like ...Then info to upgrade to stock M before returning back to tool to unlock updated to the latest M.
But like mentioned , we maybe at the tail end of this problem.
Probably related to 95% of the bricking threads here for zenfone.
Anyway thanks for taking interest
Deathschythe33 said:
Hi,
I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?
I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM
Click to expand...
Click to collapse
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?
Thank you so much for your awesome ToolKit, works flawlessly !!
<3
v0.5 is out
rummsbumms said:
v0.5 is out
Click to expand...
Click to collapse
thanks, can you simply make 3 downloads complete for the 3 mm versions? now is a bit confusing with this updating/base files.
I don't think that 80mb would be a problem to download, everyone have at least a dsl line, we are not talking of gbs, thanks
v0.7 is out
@fred_gaou: I've tested with win10. 1.0.3.2 works fine and will be default, but I've added 1.0.3.6 too. perhaps someone could test on other machines as i still have problems using it and don't know whats the problem.
@holymoz: I've made a additional "full" package which contains all files. the "base" version still only contains the latest mm firmware files.
@timbernot: Still thinking about it. Maybe some kind of decision tree asking for the problem could lead the user to an action that could cure the problem. I'll keep it on my todo list.
V0.5 works okay on my device with win 10 . i will test later the new build thanks
rummsbumms said:
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.
Is your bootloader still locked?
Click to expand...
Click to collapse
Hello @rummsbumms,
Thank you for taking your time to respond. Yup, my phone's bootloader is still locked. Everything in this phone is "official" including the freaking official bloatwares. I love the HW specs of this phone, but the bloatwares are F***ing crazy!
Got a second Redmi 7A, I'm 99.99% certain it came with *global* 10.2.5 PCMMIXM (it was what ordered, and saw it too, pretty certain), decided to let it upgrade OTA, it picked 11.0.6 OTA, and it came to:
MIUI Global 11.0.6 PCMEUXM (notice the EU there), which, I'm assuming from this url: https://mirom.ezbox.idv.tw/en/phone/pine/
to be this one:
Code:
Redmi 7A – EEA Stable ROM
Lstest V11.0.6.0.PCMEUXM(History)
MIUI 11
Android 9.0
Update at 2019-10-31 19:05:57
Changelog Expand Official Link
Recovery miui_PINEEEAGlobal_V11.0.6.0.PCMEUXM_bcc90ca1df_9.0.zip
Filesize 1.5G
MD5 bcc90ca1df89a4f3d8cc7b9705a70d83
which is a bit confusing, it says Global, but has "EU" in the name.. in any event, flashed TWRP as per:
https://xiaomifirmware.com/guides-and-tips/how-to-install-twrp-and-magisk-root-on-redmi-7a/
choose the LRTeam version:
Code:
2a3296af05267160cba2891bff446203 TWRP-3.3.1-1003-REDMI7A-CN-wzsx150.img
seemed newest, all is great, it boots into TWRP recovery.. Next, trying to get Magisk on it, got the manager apk installed 7.4 all fine, it says 20.1 needs to be installed so...
unzipped the boot.img from above zip file, it has this md5, this is original , unmodified boot.img:
Code:
036d1b6c5a99e9417f8d3e98d5718368 boot_Global_V1106PCMEUXM.img
following this guide: https://romprovider.com/2019/01/create-pre-rooted-patched-boot-img-magisk/
Magisk successfully patched the boot.img on the same phone (running 11.0.6) and got this file:
Code:
dad219422c9302a460d4d2370adafb4f magisk_patched_Global_V1106PCMEUXM.img
transferred to PC, attempted to flash:
Code:
c:\XiaomiADB\bin>fastboot flash boot magisk_patched_Global_V1106PCMEUXM.img
target reported max download size of 535822336 bytes
sending 'boot' (14914 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.190s]
finished. total time: 0.665s
c:\XiaomiADB\bin>fastboot reboot
rebooting...
finished. total time: 0.003s
Phone boots fine, however, magisk still says it needs to be installed...
in developer's options, the USB debugging is enabled, and boot loader is definitely unlocked, it says on splash screen and the OEM Unlocking is greyed out and says "bootloader already unlocked".
Also, attempted to flash boot image from within TWRP, selecting the above boot.img file and selecting the boot partition, flashes OK, however, after normal reboot, as if nothing happened, phone boots, but magisk is NOT installed (no root).
Is there anything missing in these steps? does anyone have a correctly patched 11.0.6 image with magisk in it from an 7A phone?
Only thing that appears as an "error" are these family of cmds to unlock boot loader:
Code:
fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
however, i think that is normal/expected, since the bootloader is already unlocked.. able to flash twrp, etc.
Thanks so much for any ideas...
Stormy.
Forgot to mention that attempted to install Magisk 20.1 zip file downloaded by the app, from within TWRP, attached screenshot of how that looks like all seems okay but after reboot it still says that magisk needs to be installed... Very strange..
Appreciate any thoughts..
Stormy
noticed in above screenshot that it detected a patched boot image so decided to try installing the
v20.1 Magiskk zip file with the stock Boot, the install results in a screenshot, after reboot it still says that magisk has to be installed.!
also attaching screenshots showing the device is unlocked as well as USB debugging and OEM unlocking are all there.
Should this be posted in The magisk forum or is this something specific to the 7A? Or my steps?
How to debug further?
Attempted with the other TWRP image TWRP_v3.3.1-1_all.img, same results also reinstall the magisk manager 7.4 and same results....hmm.. maybe the OTA update took wrong ROM version. (EU and not pure Global)?...
Digging a bit more, found this pretty cool tool: https://www.xiaomitool.com/V2/latest called: "XiaoMiTool V2 ", which basically automated (almost) Everything !! Tried to do TWRP, as well as Magisk, it too followed similar steps I did, all automatically, rebooting, patching, etc. but outcome is still same, when phone boots normally, Magisk Manager says that Magisk 20.1 needs to be installed...
Then tried to flush miui_PINEGlobal_V11.0.4.0.PCMMIXM_674ed79f0b_9.0.zip using that tool, it said all is OK, phone rebooted , wiped all, but it still runs the EU version for some reason.. Now trying to find the path to "downgrade" from 11.0.6 to 11.0.4, or switch from EU to Global.. maybe that's the source of all issues, not sure what else to try
Reporting progress, to keep track of what was attempted. So, decided to WIPE all and start with 11.0.4 Global fresh, from TWRP, wiped everything, to the point it said "no OS installed, are you sure u want to reboot" it rebooted into fastboot, then downloaded the 11.0.4 Global .tgz and flashed, phone booted OK this time into 11.0.4 Flashed TWRP, and then attempted to flash Magisk via both routes, one by patching the boot.img from the .tgz and flashing, all using the Phone (to avoid any PC/driver/adb issues). The flashing worked fine, but upon reboot, Magisk Manager claimed that Magisk is not installed. Second try was to flash the stock boot.img, then flash magisk zip file, did that for v20.1, v19.4 and 19.3, each time from stock boot.img, and reboots to test, none of them showed that magisk is installed...
all this time, usb debugging is enabled despite most work done on the actual redmi 7A phone itself.
Then uninstalled magisk manager 7.4, and tried with 7.2, but that doesn't change much since any action there wants to update to v7.4..
next step will wipe again, and go for the Global 10.2.5... if that doesn't work then I really don't know what can be going on...
If anyone does have a 7A with MIUI 11 with a properly patched boot.img, would love to try it... all my patching attempted booted fine, but none showed that Magisk is installed... finding it hard to think it's a magisk bug, more likely some MIUI 11, lets see how 10 works out...
Stormy
OK, some success! so, wiped ALL again, to the point of no-OS installed; phone only boots into fastboot (brick), using flash_all.sh from 10.2.5 fastboot Global ROM flashed entire phone and it booted OK.
btw, not easy to find 10.2.5 now, as places already updated links to 11.0.x..
Once in 10.2.5, tried to patch Magisk in all possible ways (twrp or patching boot.img on phone the flashing from Windows10/PC) as also described in this thread few weeks ago:
https://forum.xda-developers.com/showpost.php?p=80498891&postcount=179
but it did NOT work, well, the procedure appeared OK, no errors and when booting, it says magisk needs to be installed.
The only thing that works is the provided boot global .img file [size 14.5 MB (15,269,888 bytes)], as soon as this one is flashed, via phone/twrp or PC, then the magisk is correctly detected.
Very mysterious, why only that boot.img is working on my 7A phones.. maybe there's an additional step, to "sign" or fix the boot.img before it can be flashed?
now took a full TWRP backup, and will try to move to 11.0.4 see if magisk is retained, and if not, if possible to re-gain it.. if not, then, will restore from TWRP backup.
Any thoughts welcomed..
Stormy.
Did not manage to get it working with MIUI 11 yet, so backed to MIUI 10.2.5.. all is fine there.
Noticed that TWRP did not "stick", flash but after normal boot, it came back to original recovery. I think this is b/c of Verify Boot in android Pie/9.. so I *think* what helped here is to flash a vbmeta.img from first post of this thread:
https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820
Even after flashing this, and even in 10.2.5, patching the STOCK 10.2.5 from the phone using Magisk 20.1 and installing using TWRP did not work, not sure if this is a bug in magisk or what, but only way to get root was using the provided boot.img as described above. I'll keep using 10.2.5 for now. feel free to add any ideas here , maybe one day will get more time and a spare phone to try MIUI 11
Stormy.
hey , I have the same problem. I noticed you mentioned 'sign', what should I sign what things? and how to sign?
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
depaul9999 said:
I was going to ask for the same thing : is there any method to root Redmi 7A under MIUI 11?
For my case :
-I can flash and boot to TWRP,
-I can 'flash' (install) Magisk through TWRP,
-However : this has no effect. Still Magisk Manager tells me that Magisk was not found!
The Redmi is unlocked and I can install custom roms (Mokee, LineageOS...). I see no reason why the phone can't be rooted it's probably just some bad configuration.
Thank you very much
Click to expand...
Click to collapse
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible.
Click to expand...
Click to collapse
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
depaul9999 said:
Thanks indeed that's the case for the moment. Hopefully we could soon manage to root the phone successfully.
My biggest motive is to install App2SD and move games to external storage, since with my 16GB version I can barely install one or two games and MIUI only allows installation to internal. (I know I should've bought a phone with bigger storage).
Click to expand...
Click to collapse
I've read that the 16GB version of the Redmi 7A is possible to put a micro SD card and format it as internal storage and that was the reason I've bought it, although I'm not yet sure because I'm waiting to buy a microSD card, it's still on the way.
I want to root it because of privacy reasons and that's the only reason. For now I'm using a VPN to block 99% of the google and xiaomi apps, etc. to the internet this way I got some privacy. I have unlocked the phone too so I did uninstalled several apps from the system using the PC.
KnowTheyself said:
Don't bother rooting Redmi 7A, it just isn't possible, not even with the miui 10 (I've tried). There's no way to flash magisk successfuly, because when you do, magisk is still uninstalled, therefore no root and if you try SU instead, it happens some kind of error. If you try magisk without TWRP and flash a patched recovery it still doesn't work either. Since I can only follow tutorials because I understand nothing about Android I can say that there is no tutorial out there that works and all of them are wrong. I just don't understand why people bother to make tutorials that do not work just to make people waste their time.
Click to expand...
Click to collapse
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
stormy1777 said:
I don't think that's correct.. I've rooted several 7A, as many others on the forum, just look around, all these posts, many HAVE done based on the topics...
There are few more mysteries, even to experts, so don't feel bad (like how to path boot.img from Magisk, did it for other phones, but not possible for this one for some reason).. agree, there is no current/updated guide that works for everyone, but one can piece things together..
The reason there is no complete guide is not b/c people want to waste your time, they are really trying to SAVE time, however, there are many FACTORS at play, like initial ROM/state of the phone, some Global, some EU, some 10.x other 11.x and so forth, which change over time...
Once the bootloader is unlocked, then one should be able to:
- flash vbmeta.img
- flash twrp (I'm using 3.3.1-1003 'wzsx150').
boot into twrp and flash a properly patched boot.img (that matches your phone), now that's the tricky part, b/c one cannot be re-generated, u'd have to dig through some of the posts, like this: https://forum.xda-developers.com/redmi-7a/how-to/custom-gsi-firmware-t3965820 and find the boot.img that works, it had magisk 19.3 in it, but then update is easily possible.
it's important to flash vbmeta otherwise the "verified boot" will revert things back to a "working state", and you'll lose twrp..
Once my phone got to MIUI 11 it was not possible to root (since there is no boot.img that's patches correctly, and i couldn't do it), so i've flashed the whole phone back to 10.2.5 and from there rooting was pretty easy, the trick is to find the right boot.img.
Good luck.
Click to expand...
Click to collapse
Well, if you say so... If you're right then I got the wrong Redmi 7A model. It came with the EU version of the miui.
I already knew the tutorial in the link you gave, but that seems very complicated and I do not really know what's going on there so it's better I do not try it. And if I followed that tutorial I would have to flash the phone again with the miui 10, because I have the 11 now. I already wasted many hours trying to root the phone and I had to flash the rom about 4 times because the phone became bricked. Anyway the tutorials I've followed were not the one in the link above and all the other ones I've tried did not work and yet they claim it does, specially using magisk only, without TWRP.
I'll wait for an easier method than the one you shared, if that will ever happen. For now I just use a VPN, it's the closest thing to root I have found, to deny system and apps permission to the internet.
Thank you
In case you're not aware, there are scripts to flash the entire phone automatically, I've done that 10's of times BEFORE putting the phone into "production" use, root was a _must-have_,phone's now heavily used, so can't toy with it much, unless forced to (see below), i may get another phone to play with, but not much TIME to justify it...
Was getting tired of typing:
Code:
:/ # pm list packages|grep xyz
followed by:
:/ # pm uninstall -k --user 0 com.google.android.apps.tachyon
Success
Decided to give some "highly-rated" app a try, it claims to be able to remove system apps: "System app remover (root needed)":
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_US
Took a full TWRP backup, installed, all seems great.. remove, goes to recycle bin, ok.. now, lets REBOOT..
Opps.. phones goes into FASTBOOT... OK!! that's what the backup is for.. go into TWRP, flush SYSTEM, CACHE, DATA, reboot, again, we're in Fastboot, and this time no RECOVERY boot is possible, just goes into FASTBOOT directly.. much like i've described in this thread:
https://forum.xda-developers.com/showpost.php?p=80509823&postcount=111
so, TWRP on phone doesn't help much, took the TWRP backup from SD Card to PC (since phone can only do fastboot at this point), thought it would be easy/possible to fastboot flash all the TWRP into the phone from PC, however, that is NOT simple, since TWRP breaks files, one must concatenate them before flashing..
I was not in the mood, nor did i think a huge change took place, it was just something silly that app did. hmm.. here, i can't exactly explain what took place, but a sequence of flashing of boot.img recovery.img and vbmeta.img all from STOCK and the TWRP backup, was "all it took" to recover the phone fully..
After about 30+ flashes and reboots it came to life much like the last boot, went into that APP again, tried to RESTORE the apps, it failed, and a reboot again, went into FASTBOOT! twrp was there, again, tried recovery, this time only SYSTEM, again, phone lost recovery, and went into, fastboot only... and.. again, sequence of flashing from fastboot, i can tell that vbmeta (Verify Boot) takes a *major* role in this version/device, if something is not right, it just reverts things or decides to go into fastboot.
I saw it work once, so was not going to give up and wipe/start fresh.. kept trying..
I think the app somehow made "direct" modifications to the system partition without proper interface, and thus ruined the "signature" or encryption, otherwise not sure how it could trash the phone so badly..
in any event, after long struggles, flashing the LATEST did _not_ work, it's almost as if the phone had to be taken back to original setting, let it boot into recovery, then reboot again, and flash things in steps, not all at once, at least based on this experience. I know it's silly, b/c in Android 6 I've restored/cloned phones all the time using TWRP directly from phone.. not sure, it does not work on my 7A's...
eventually, phone booted, with 10.2.5 magisk/boot.img (no root, since it did not recognize magisk), then fastboot flashed the canary boot.img, and got root.
anyways, point is, it was pretty ugly, and I'm not complaining, just saying this is pretty complicated stuff, it's a miracle that this even works
keep up the great work everyone, if i can help in any way, let me know...
All this is on Global phone, I don't have an EU/ROM/phone, so can't help u directly, but someone may have a root boot.img EU boot, that's really the key, and the vbmeta.img of course as for MIUI11? so what if that's what you have, it can be flashed, it's a matter of choice, flash to miui 10.2.5 and get root, or try to do it on MIUI11, or, let it be and use w/o root.. which was not an option for me
good luck.
Stormy.
btw, the magisk/patching boot.img did not work for me, and was reported in that same thread:
https://forum.xda-developers.com/showpost.php?p=80560039&postcount=206
MDV106 said that both EU and global boot.img were posted in that thread, and i agree i used one of them, not sure exactly which, but definitely it was the Global, not the EU. and i think it's not goot to mix up.. if u have an EU, stick with it, it might impact Wifi or similar "regional" things..
Same problem, but it works on mokee
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
boody shaban said:
Add-on-su on mokee open source ROM works fine, can enable root from developer options only, magisk and supersu don't work.
I have been trying to make them work but it seems impossible, I have looked in system/xbin and found no su files, maybe the problem is in the meta-INF because it doesn't properly know where to install it.
Click to expand...
Click to collapse
Thanks for this data point, yeah, root was/is also possible with MIUI 10.2.5, I'm sure other ROMs can root pretty easily.. the "goal" of this thread is to somehow figure how to do it on MIUI 11 so we can take the security updates and still retain rootness
working root redmi 7a
Working root for Redmi 7a
thank you stormy1777 - it is your tutorial, I only put it together. It is the only tutorial that works
links unavailable due to site rules:
google for: ROM v10.2.5. global V10.2.5.0.PCMMIXM/pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global_efb78ff9c3.tgz
google for: patched boot v10.2.5. under: xiaomifirmware (dot) com how-to-install-twrp-and-magisk-root-on-redmi-7a
google for: TWRP: under: androidweblog(dot)com xiaomi-redmi-7a-root-install-twrp-recovery I took the version 3.3.1.-0
google for Magisk: Magisk-v20.1.zip
Install in fastboot mode and with Mi Flash Tool
flash: pine_global_images_V10.2.5.0.PCMMIXM_20190805.0000.00_9.0_global
option: clean all
wait until the mobile phone is fully installed (will reboot automatically)
copy Magisk into the root directory on your phone
restart in fastboot mode (volume down + power button)
on PC:
rename twrp file to recovery.img
rename boot file to boot.img
copy boot.img and recovery.img on the PC in the directory, where adb drivers are
open power shell on the PC in the directory, where adb drivers are
type in the power shell window:
fastboot flash recovery recovery.img
Enter
then type in the power shell window
fastboot flash boot boot.img
Enter
then hold volume up + power button until it 2x starts and vibrates, then wait, it opens in TWRP
type install, find Magisk.zip in the phone root directory a flash
restart into system
done
I’ve tried looking for solutions online, but to no avail I can’t seem to fix by myself I have recently installed LineageOS 16 , been using it for months until recently it started to slow down, and die down what i mean is the booting process takes time and after booting there is some random crashes and it reboots , I was able to solve the problem using TWRP by wiping out the cache and resetting back to factory settings, but it was taking so long to boot after and then I decided to flash it once again, started from scratch and it worked for some time until it crashed once again leaving me to unfixable bootloop, it stays on LineageOS logo, then screen dims and then just bootloops, so i decided to flash the STOCK ROM using odin which apparently worked It booted and the process was painful because every boot im doing it got slower and slower until it would be stuck at Samsung Logo and then reboots once again, so I reflashed it once again and when it booted, I was bombarded by system apps not reponsing properly, icon like ‘System UI has stopped’ and then most of the In-built app would do the same and it crashed this time, this time when it booted it is stuck to samsung logo, so i tried wiping the cache and formatting data on stock recovery and it is still stuck on boot-loop, if lucky it goes to samsung logo and just literally in that state forever, i left it for hours and it is still the same. and then when i tried booting to stock rom there was a message below that says (dm-verity verification failed), I googled it and it is a cause for tampering system files and I just couldn’t get to work it out and find a proper solution. I hope you all can help me out. Every-time i try to flash the stock rom the message is , (Installing system updates, error, goes to recovery then it has the problem below) If anyone has encountered the same problem, or has a solution I would appreciate it. Thank you.
Samsung Galaxy Note 4 (SM-N910C) treltex
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Thank you. I hope this fixes my problem.. But where do I flash it through odin or TWRP??
I tried flashing the zip i got error 1
Mr. JAVI said:
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Click to expand...
Click to collapse
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
kenesuuu said:
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
Click to expand...
Click to collapse
Try this, read threw the entire tread, follow the instructions. I'd alsoblike to add dm-verity and drk are some of the most difficult to solve, at least in my experience. Furthermore, I would highly recommend making a nandroid backup of all your partitions, especially EFS, boot. I'll see if I can find the no opt encrypt .zip in the meantime. I believe it was 6.0 or 6.1 .
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Error 1
https://forum.xda-developers.com/galaxy-s7/help/error-installing-verity-opt-encrypt-zip-t3436385
scroll down to
JUST WANT TO DISABLE VERITY/ENCRYPTION
https://www.google.com/amp/s/forum....azyflasher-tool-flashing-custom-t3549210/amp/
read threw the rest of the thread.
I don't believe you'll have any success on pure stock firmware. Chances are you'll need to flash a custom kernel for your specific device and/or root package. Unfortunately, theres no one size fits all when it comes to dm-verity or drk.