Related
Last update: 17.10.2017
Introduction
This is a small flashable script that will add the device signature for z00a, z008 or z00x devices to boot and recovery image. This function is part of my Zenfone 2 toolkit which primary supports stock rom users, but could be useful for any other custom rom user too.
It will fix any kind of missing signatures on boot or recovery that could happen, e. g. if you updated magisk within magisk manager, installed anything that modified boot image with proper device signatures or flashed a new twrp recovery. If you want to patch the recovery image, you should temporary boot a (probably older but) properly signed twrp recovery first of course.
I hope you find it useful. I appreciate any kind of code improvement, just leave me a note.
Usage instructions
[SIZE=+1]Just flash attached zip in custom recovery[/SIZE]
Downloads
Main: Downloads tab (see above)
Thanks to/Credits
Code:
:: > topjohnwu
:: > ggrandou
:: > gerasiov
XDA:DevDB Information
Image signature tool for Zenfone 2, Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Beta
Beta Release Date: 2017-10-17
Created 2017-10-18
Last Updated 2018-09-11
Attachments
Most current version:
Great work! This is awesome!
Now I can update OTA LineageOS and keep Magisk without the need of a computer.
rummsbumms said:
Most current version:
Click to expand...
Click to collapse
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily
Big thanks for this great tool bro. :good:
drixse said:
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily
Click to expand...
Click to collapse
Did you succeed with installing twrp 3.2?
sushuguru said:
Did you succeed with installing twrp 3.2?
Click to expand...
Click to collapse
I don't try yet. I would like to be sure how to proceed first.
drixse said:
I don't try yet. I would like to be sure how to proceed first.
Click to expand...
Click to collapse
Well, i don't think you should, twrp is not released yet for our device.
thanks a lot bro..really very helpful :good:
Very useful，but I still don't know why bootloader already unlocked，it still need the signature to boot
Thanks a lot man! Worked like a charm!
Thanks m8! Works like a charm!
Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?
marcossanches said:
Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?
Click to expand...
Click to collapse
Yes
Sent from my ASUS_Z00A using XDA Labs
can you add boot signature for z00d?
Then after installing Magisk...
- I have to flash this ZIP to make the system boot?
- Or just leave it?
Pls make signature fix for z00d?
Nothing to do for z00d?
@rummsbumms, have you got something for z00d?
Thanks in advance
towerman said:
@rummsbumms, have you got something for z00d?
Thanks in advance
Click to expand...
Click to collapse
sorry for the confusion, this script doesn't support the z00d as I don't know anything about this device. i've fixed the typo in the first post.
have you already tried the verified boot signer from chainfire? that tool is the best way to sign boot images! my script just adds a signature, which is a signature generated with oem keys but for an older boot image, to the current boot image. so the signature is valid but doesn't fit to the boot image. this way you can boot but get a red exclamation mark on each boot. if you use the verified boot signer, a signature with a custom key will be generated and added to the installed boot image. that signature is valid and fits to the boot image, but isn't created with oem keys from asus. this way you can boot too but get a orange (or yellow? i don't remember) exclamation mark on each boot.
Hello, so I decided to reflash my ROM because I kept running into issues, and I didn't uninstall Magisk before doing so.
Then when I tried flashing Magisk it showed me error 1. Flashing the uninstaller gives the same error. Magisk Manager shows that it is not installed, Root Checker states that the device is unrooted, and so far the only app that mentioned my phone being rooted is LastPass.
What can I possibly do to reinstall Magisk so it's back on my device in its full grace?
I checked other posts and either they are not related to my problem or didn't help
Phone: Xiaomi Redmi Note 4 Snapdragon, Recovery: official TWRP non-treble, ROM: latest build of official AOSP Extended
Maybe try dirty flashing and flashing Magisk again?
Not Sally when Magisk is already installed, I can flash it again with no problem. Weird that you're having these issues. ?
LennyTheCat said:
Hello, so I decided to reflash my ROM because I kept running into issues, and I didn't uninstall Magisk before doing so.
Then when I tried flashing Magisk it showed me error 1. Flashing the uninstaller gives the same error. Magisk Manager shows that it is not installed, Root Checker states that the device is unrooted, and so far the only app that mentioned my phone being rooted is LastPass.
What can I possibly do to reinstall Magisk so it's back on my device in its full grace?
I checked other posts and either they are not related to my problem or didn't help
Phone: Xiaomi Redmi Note 4 Snapdragon, Recovery: official TWRP non-treble, ROM: latest build of official AOSP Extended
Click to expand...
Click to collapse
Did you wipe everything? Wipe system and data before re flashing your rom.
@LennyTheCat To be absolutely sure what's going on you're going to have to provide the recovery log, saved after you've attempted you flash Magisk.
madbat99 said:
Did you wipe everything? Wipe system and data before re flashing your rom.
Click to expand...
Click to collapse
Yes I did
Didgeridoohan said:
@LennyTheCat To be absolutely sure what's going on you're going to have to provide the recovery log, saved after you've attempted you flash Magisk.
Click to expand...
Click to collapse
Will provide later now I have stuff to do
@Didgeridoohan here's the log file
LennyTheCat said:
@Didgeridoohan here's the log file
Click to expand...
Click to collapse
Try updating your TWRP. That has solved "cannot mount vendor" for other Mido users.
https://forum.xda-developers.com/search/forum/5903?query=mido cannot mount vendor
Didgeridoohan said:
Try updating your TWRP. That has solved "cannot mount vendor" for other Mido users.
https://forum.xda-developers.com/search/forum/5903?query=mido cannot mount vendor
Click to expand...
Click to collapse
well, it has installed no problem, but then my phone got stuck in a bootloop after rebooting. I have to reflash everything now, will tell if it worked later
@Didgeridoohan when I install Magisk, the phone keeps running into bootloops. Clean install of the ROM and Gapps seems to work fine. Tried 16.0 and 16.4 packages
LennyTheCat said:
@Didgeridoohan when I install Magisk, the phone keeps running into bootloops. Clean install of the ROM and Gapps seems to work fine. Tried 16.0 and 16.4 packages
Click to expand...
Click to collapse
Well... You're using a Treble ROM, right? So I'm assuming you're using a Treble modified Magisk version (since there's no official Treble support in Magisk yet)... If not, I'm sure you can find the relevant information in your ROM's thread.
Always go to the source...
Didgeridoohan said:
Well... You're using a Treble ROM, right? So I'm assuming you're using a Treble modified Magisk version (since there's no official Treble support in Magisk yet)... If not, I'm sure you can find the relevant information in your ROM's thread.
Always go to the source...
Click to expand...
Click to collapse
I decided to flash Lineage OS and then I flashed the Magisk package included in the post. Now it's working all squeaky and shiny. Thanks for help anyway
Hello,
Until now I could only install magisk 16.4 on the mi8se without getting a bootloop.
Do you know if magisk 17.3 has already solved the problem?
yes, bootloop here too with 17,3
OK thanks...
I leave the subject waiting until magisk 17.4
Any luck??? I've been getting Boot loops with every magisk I flash other than what comes with the recovery Wich is 16.4
j0an said:
Any luck??? I've been getting Boot loops with every magisk I flash other than what comes with the recovery Wich is 16.4
Click to expand...
Click to collapse
Just install latest TWRP 3.2.3 from this thread, and choose Install Root in TWRP, it will instal Magisk 16.6 and working fine with both Android 8.1 and 9.0 of MIUI roms.
https://forum.xda-developers.com/mi-8-se/development/recovery-twrp-recovery-3-2-3-lr-team-t3828854
longnt2007 said:
Just install latest TWRP 3.2.3 from this thread, and choose Install Root in TWRP, it will instal Magisk 16.6 and working fine with both Android 8.1 and 9.0 of MIUI roms.
https://forum.xda-developers.com/mi-8-se/development/recovery-twrp-recovery-3-2-3-lr-team-t3828854
Click to expand...
Click to collapse
Thanks for the information. I must apologize for providing the wrong information, the magisk version I was referring was 16.6 which comes with the twrp. I still trying to get the magisk above 17.0 working... Some of the modules I use like YouTube vanced don't work on magisk below 17.x:crying:
But again .. thank you for the quick response
Did somebody tries magisk 18?
zudo said:
Did somebody tries magisk 18?
Click to expand...
Click to collapse
I did ... And guess what?...... Boot loops :crying: the:crying:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
vehz said:
Hi there,
Looking for some assistance to root on Lineage OS 17 for my S10. I had previously rooted my stock rom before installing the custom rom. However, I realized that Magisk is not registering on LOS. I tried to reroot via zip on TWRP with no success. Any ideas on how I can root again? Would I have to reroot on my stock rom again before installing LOS?
Thanks
Click to expand...
Click to collapse
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
ISoreo said:
try to patch boot.img from your ROM by using Magisk Manager and flash boot.img from magisk patched in TWRP
Click to expand...
Click to collapse
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
vehz said:
could you please walk me through this step by step? sorry this is my first experience in rooting after a long time
Click to expand...
Click to collapse
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
ISoreo said:
1. install the Magisk Manager into your phone
2. extracted your rom that you installed to your phone find the boot.img and copy to somewhere in your phone
3. go to magisk manager click install and select "select and patch a file"
4. find your boot.img that your are already copied and select it
5. after finish patched magisk will give you "magisk_patched.img" then reboot to the TWRP recovery
6. select install then select install image
7. find "magisk_patched.img" then select to install in boot.img
8. reboot
Click to expand...
Click to collapse
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
vehz said:
I've just tried this but now my S10 is stuck on boot warning. Was I supposed to do a full wipe too?
Edit: Resolved now. There was a custom Magisk boot.img specifically for Lineage OS root
Click to expand...
Click to collapse
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
jonapiron said:
Hi @vehz! Same situation here: I'd like to root my S10e on Lineage 17.1. Could you tell me where you found the Magisk boot.img for Lineage OS root? Many thanks!
Click to expand...
Click to collapse
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
https://drive.google.com/drive/folders/1UdPbIbM3luYIiOdXMXb7raAnWLERjssh
beyond0lte folder is for S10E.
vehz said:
You will need to do a format/wipe, flash multi_disabler.zip then flash the new updated LOS rom, then Magisk.img
Below link for the updated LOS rom and Magisk .img
This is from the official LOS thread.
beyond0lte folder is for S10E.
Click to expand...
Click to collapse
Oh I'm so stupid, I had seen the Magisk boot img in the files but ended up using another one... It seems to work now, thank you sooo much!!
It still cannot pass SafetyNet check (ctsProfile), I'll investigate that...
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
I am trying root Lineage 18.1 on my s10. I have tried differtent magisk-files from TWRP, but still no root access.
What are the required files for 18.1 for Galaxy s10 and steps to get root-access?
Hafizp5100 said:
I had the same issue with lineage 17.1 in xperia z2 when using the latest magisk version 21.4 , solved by flashing an older version (magisk version 20.4).
Click to expand...
Click to collapse
Dude, thanks so much. I faced the exact same problem with my Z2, now it's running magisk just fine. You saved me a bunch of headaches.
I'm new here on this site and idk if I'm doing I correctly but I need help with it. I'm a noob to rooting and Twrp stuff. I have unlocked my bootloader and have tried to watch videos about rooting and read articles but I couldn't understand. That's why I am posting this thread. Could someone explain things to me in the most simple way and how can I avoid bootloops or stuff like that if I come across one. I'd appreciate it very much.
I think it is best to start with reading the "HowTo" guides
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Alright I'll try it, thanks
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com
Elinx said:
I think it is best to start with reading the "HowTo" guides
Click to expand...
Click to collapse
Hello Sir, sorry to disturb you again. I have installed the adb, fastboot and fastbootd drivers. I need your help with something, should i continue with the latest version of Magisk? I have Redmi note 10 pro (sweet)
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Elinx said:
Because you are a starter, I advice to follow the guide exactly.
If you flash a lower version of Magisk, you always can update afterwards with Magisk manager
You haven't said what the reason is for root.
If you want to flash custom rom, you need Twrp or OrangeFox too
That is also done with ADB
In case of Magisk you patch the original boot.img
(that is why you need an original stock boot.img. Keep a copy for revert back)
Click to expand...
Click to collapse
Im following the guide that you have given the link for. And by update do you mean I can install new updates of the phone (because I know after rooting you can't or won't receive updates) or do you mean magisk by it? Well I want to modify and tweak with my Phone appearance and install some modules. For now Im not going for custom roms. Since I just want to root my phone for now, could you please tell me what do you mean by original stock boot.img? Because I have downloaded and extracted the rom contents that i have in my phone (following the guide). I know I am asking too much, sorry
p.s. what would you like to suggest me to use the latest version of magisk or some old version?
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Elinx said:
I mean update of Magisk.
The older versions are working with the same modules till v23
From v24 Magisk has another base (zygisk) and you need other modules
So decide which modules you need for which Magisk version, before flashing
Inside the stock rom you find boot.img and recovery.img (these are replaced by magisk.img and twrp.img)
If something goes wrong you can flash these original images back with ADB and you have stock Miui without root again and can start again with clean sheets.
Click to expand...
Click to collapse
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Bilalbilly87 said:
Thank you alot. Its really helpful to me. Also I just checked that I do not have the recovery.img but the boot.img
Click to expand...
Click to collapse
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Elinx said:
If you only flash Magisk you only need boot.img
I see now what you mean
Normally inside the stock fastboot rom you find all partition images, but you recognize only the boot.img
Boot.img is one of them, also recovery.img is one of about 13 partitions.
Be sure to double check the version. It must be exactly the same as what you have now on the phone.
Click to expand...
Click to collapse
I have installed Twrp and Magisk As well. I was able to install some modules but with some modules I'm having this problem and I don't quite understand why. I downloaded it from GitHub like the zip file and after flashing.
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Elinx said:
Congrats with flashing Twrp and magisk
I understand you speak about Magisk modules?
As I said before, ckeck carefully for which Magisk version the module can be flashed
v.xx t/m v. 23 or v24 t/m 25.3 (zygisk)
Click to expand...
Click to collapse
Thank you for helping me. Actually i was having problem with flashing the modules, because the contents are in the zip file in a folder and they need to be outside of any folder meaning all those files need to be in the zip instead of being in a folder in the zip. I'm good to go as i checked and its installing now.
kon kkonsay modules use krra ha hmy bhi bta
MehtabMad said:
kon kkonsay modules use krra ha hmy bhi bta
Click to expand...
Click to collapse
English forum....
Laptapper said:
English forum....
Click to expand...
Click to collapse
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
MehtabMad said:
Laptapper, one thing is happening to my RN10P
I have Lineage Os
I have flashed your vantom kernel
Using magisk in it
Problem is my phone is heating after kernel install, i checked cpu clock speed
when i changed min* clock speed to 300 it always reset back to max
i.e. 2304Mhz min and @2304Mhz max.
Click to expand...
Click to collapse
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Sorry for late reply. Everything has been working okay with modules altho i didnt install alot of them but a few. So i guess there weren't enough modules which provided me any customization for Miui 13 because i had the wrong concept. Now i want to take it a step further, i want to flash a custom rom. I have looked and searched. Have decided to go for either Pixel Exp A12 or AncientOS A12 (It has alot of customizations). Now i want to ask you a few questions that i have in mind.
1) Should I flash Custom Rom through Twrp?
2) If so, do i need to flash that Dm verity file (because when I installed twrp in my stock rom which im still using rn, they told us to do that to avoid bootloop and to keep Twrp permanent so do i also need to do it with custom rom?
3) And if its safe to flash through Twrp, Could you please tell me how to (through twrp if its safe)?
4) Which Rom should i go for? Pixel or AncientOs
lineage Os
Laptapper said:
For me not.
Clean install? With format data yes?
Which kernel vantom latest?
If yes, try the lineage os original kernel again.
Click to expand...
Click to collapse
yes the problem was with magisk module, thermal profile disabler. i removed it and everything is stable now