I don't know if it's possible but I do know that there are methods with Magisk to pass the SafetynetCan you relock it when using custom ROMs? I kind of need safetynet to pass
I don't know if it's possible but I do know that there are methods with Magisk to pass the SafetynetCan you relock it when using custom ROMs? I kind of need safetynet to pass
For me with Redrice, bootloader open but without modifying the boot partition, Safetynet passesI don't know if it's possible but I do know that there are methods with Magisk to pass the Safetynet
Can you relock it when using custom ROMs? I kind of need safetynet to pass
Oh. Only asked because calyx on my pixel gets you to.No way... NEVER relock bootloader if you are not on a official / stock rom.
Recovery and partitions has been changed, so if you relock you will brick your phone.
What is calyx ?
Um. It's a custom ROM for pixels. Like graphene os but a bit less tinfoil hat. After flashing it makes you lick the bootloader again. It's a security focussed ROM so it makes sense. I just don't know what they do that makes it ok for them to relock it but you can't in other ROMs
1.1.7 Incremental build (EEA SPACEWAR)
Hello, is anyone already has the 1.1.7 EEA-Stock-boot.img link, by any chance ?
.\fastboot boot Magisk-Patched_EEA_1.1.6_Boot.img
Many thanks for each time provide the stock boot for all
Thank you, it works perfectly !
Thank you for the advice and for the impressive work already done on this page but I ended up flashing the corresponding image. Good weekendYou can try to boot with Magisk Patched 1.1.6, it's often the same boot between same branch release.
So download the Magisk-Patched_EEA_1.1.6_Boot.img and just boot command (no the "flash" command, any risk)
If after this command device d'on't properly boot, just keep ON/OFF button for do a hard reset/reboot and device will boot again with the stock/installed boot.
Code:.\fastboot boot Magisk-Patched_EEA_1.1.6_Boot.img
Device will reboot, after, on system, open Magisk :
- Install
- Direct installation (recommanded)
- Go
-After patching, reboot
It's safe and with this trick you can wait for the true 1.1.7 boot.img when it will be available
I'm having a weird behaviour, maybe someone can help.
I've done the 1.1.17 update using system updater.
After the update, I tried commands "fastboot boot XXXX" and "fastboot flash boot XXX" using
patched version of 1.1.7 from here
But also old 1.1.6 patched versions.
OS boots up as normal, but when I enter Magisk it always shows root not installed.
When I flash HofaTheRipper boot, I noticed that it says that is for partition b, so I set partition b as active, but even so, it does show on magisk as not rooted.
Any ideas?
I patched the version HofaTheRipper provided.HofaTheRipper has provide the Stock Boot, not patched, so it's normal.
You must follow this (especially for safe, use fastboot boot, not fastboot flash)
You must use Magisk Boot Patched image available on the page 2
Yes you can. You just need to wait for the Full update package to be available. Keep checking the first page here.Is there any way to update the phone from 1.1.6 to 1.1.7 while rooted without wiping?
Can I uninstall magisk, update the incremental and then root again?
The updatenotification is nagging me
I'm on EEA 1.1.6
Is there any way to update the phone from 1.1.6 to 1.1.7 while rooted without wiping?
Can I uninstall magisk, update the incremental and then root again?
The updatenotification is nagging me
I'm on EEA 1.1.6
DoHmmm, I fell in a trap : no Magisk-Patched_EEA_1.1.8_Boot.img around. I'm stuck at bootloader not knowing what to do now but searching the web
It's not mandatory but booting unrooted with an unlocked bootloader can trigger the device certifications (widevine L3 for netflix) to be revoked which is kind of an hussle to deal withIt was huge! Weak network here. Now I got the update installed, System optimization stage done, ready to reboot, but didn't reboot yet.
Is it mandatory to immediately reboot to recovery then from PC "adb fastboot boot patched.img" or can I reboot now the normal way and postpone the patched boot/root for later ? Your magisk_patched-25200_TrVLh.img and the Magisk-Patched_1.5.2_Boot.img one from post #2 has not the same sha1sum hash. I wanted to have a look at my Magisk app but the icon has changed (since uninstalled from within?-didn't notice at the time) and says "An upgrade of Magisk Manager to full version is required to complete installation. Do you wish...?"
In the lap time I grabbed the ota.zip from "logcat|grep zip" => ... https://android.googleapis.com/packages/ota-api/package/6718db370773ad0191b970df545f54c4163a014e.zip ... *
Someone said it is better to build the patched-boot.img from our own original payload.bin because phones may have hardware differences. Any chance I could extract this 1.5.2-stock-boot.img from the payload.bin in the incremental ota zip?
* silly: it was available here at the NP1 tracker
![]()
It's not mandatory but booting unrooted with an unlocked bootloader can trigger the device certifications (widevine L3 for netflix) to be revoked which is kind of an hussle to deal withIt was huge! Weak network here. Now I got the update installed, System optimization stage done, ready to reboot, but didn't reboot yet.
Is it mandatory to immediately reboot to recovery then from PC "adb fastboot boot patched.img" or can I reboot now the normal way and postpone the patched boot/root for later ? Your magisk_patched-25200_TrVLh.img and the Magisk-Patched_1.5.2_Boot.img one from post #2 has not the same sha1sum hash. I wanted to have a look at my Magisk app but the icon has changed (since uninstalled from within?-didn't notice at the time) and says "An upgrade of Magisk Manager to full version is required to complete installation. Do you wish...?"
In the lap time I grabbed the ota.zip from "logcat|grep zip" => ... https://android.googleapis.com/packages/ota-api/package/6718db370773ad0191b970df545f54c4163a014e.zip ... *
Someone said it is better to build the patched-boot.img from our own original payload.bin because phones may have hardware differences. Any chance I could extract this 1.5.2-stock-boot.img from the payload.bin in the incremental ota zip?
* silly: it was available here at the NP1 tracker
![]()
getprop ro.product.system.name
.\fastboot boot Magisk_Patched_XXX.img
Thanks for the tip! This did the trick, and I'm now happily re-rooted on 1.1.3I was not even aware of the local system update wizard...
.\fastboot boot magisk_patched-2XXXX_XXXXX.img