Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode, in case you bootloop due to flashing a bad module, in fastboot:
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
Once in fastboot:
fastboot boot image-newpixel3axl.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3axlRemove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Ohboy this is helpful. Just out of curiosity, how does one create a magisk patched boot image with core-only mode enabled? I would like to be able to make my own every time a new security patch is out.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
Ohboy this is helpful. Just out of curiosity, how does one create a magisk patched boot image with core-only mode enabled? I would like to be able to make my own every time a new security patch is out.
Sent from my Google Pixel 3a XL using XDA Labs
Click to expand...
Click to collapse
I had planned on keeping these updated but here are the instructions.
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack your magisk_patched.img
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
Tulsadiver said:
I had planned on keeping these updated but here are the instructions.
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack your magisk_patched.img
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
Click to expand...
Click to collapse
Nice. Seems easy enough, if you ever disappear and stop updating images for some reason I'll give it a go ?
Sent from my Google Pixel 3a XL using XDA Labs
Hello
I have regular 3a with Android 10 installed, no twrp. I was in bootloop due to some module and was looking for solution to disable modules with only fastboot.
Before I found this thread, I went and reflash to stock.
Now I know.
Thanks for sharing this.
Tulsadiver said:
I had planned on keeping these updated but here are the instructions.
You have to build your own copy of magisk from GitHub.
Clone magisk
Go to native/jni/core folder and edit the boot stages.cpp file in notepad++ like this:
Approx line 667
If (access(DISABLEFILE, F_ok) ==0)
Change == to !=
Now build magisk as per instructions on GitHub
One you have built it and there were no errors go to native/out/armeb-v7a folder and get a copy of the magiskini64 file.
Unpack your magisk_patched.img
In the ramdisk folder replace the init file with the .magiskini64 file (rename to init)
Repack your magisk_patched.img
The results are a patched IMG that will boot core only mode.
Click to expand...
Click to collapse
I tried to do this for a Pixel 4 XL but the resulting boot image errors with "error boot prepare"
gudenau said:
I tried to do this for a Pixel 4 XL but the resulting boot image errors with "error boot prepare"
Click to expand...
Click to collapse
I have these already made for the pixel 4 xl on the pixel 4 xl forum.
Should just make an AK3 zip that pushes the init from this boot.img into any boot partition, so will work universally.
osm0sis said:
Should just make an AK3 zip that pushes the init from this boot.img into any boot partition, so will work universally.
Click to expand...
Click to collapse
Ooft.
Wait, can you flash that through adb though?
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
Ooft.
Wait, can you flash that through adb though?
Click to expand...
Click to collapse
Hmm.. true, non-working recovery is a definite problem. I'm in that boat right now on my OnePlus 7T, which is how I came across this thread.
Okay, better idea. Instead of mucking around with recompiling magiskinit for the above, just do it via boot script in overlay.d
osm0sis said:
Hmm.. true, non-working recovery is a definite problem. I'm in that boat right now on my OnePlus 7T, which is how I came across this thread.
Okay, better idea. Instead of mucking around with recompiling magiskinit for the above, just do it via boot script in overlay.d
Click to expand...
Click to collapse
Tbh, a custom boot.img is the only way to recover in some situations. Like if you can't boot into an adb environment or if you've never granted adb she'll root access.
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
Tbh, a custom boot.img is the only way to recover in some situations. Like if you can't boot into an adb environment or if you've never granted adb she'll root access.
Click to expand...
Click to collapse
Exactly, so a custom boot.img using overlay.d is the easiest way to accomplish that currently.
osm0sis said:
Exactly, so a custom boot.img using overlay.d is the easiest way to accomplish that currently.
Click to expand...
Click to collapse
How would one do that exactly without being able to use adb shell?
Sent from my Google Pixel 3a XL using XDA Labs
Skittles9823 said:
How would one do that exactly without being able to use adb shell?
Click to expand...
Click to collapse
overlay.d is built into the boot.img, so you take your latest magisk_patched.img, patch it with the overlay.d scripts to have the desired effect, then repack and flash via fastboot.
Same as the OP likely did, but no need to build Magisk to get a modified magiskinit, since you can do it all via boot script, like I said.
If anyone wants to experiment with this idea, here's the basic setup I used for my boot.img to fully reset the /data/adb directory for the soft brick issue (related to a magisk.db failure) I was seeing in the last canary.
Unpack the current magisk_patched.img for your device using my Android Image Kitchen (AIK) project, then create:
ramdisk/overlay.d/init.resetmagisk.rc:
Code:
on post-fs-data
exec u:r:magisk:s0 root root -- /sbin/init.resetmagisk.sh
ramdisk/overlay.d/sbin/init.resetmagisk.sh:
Code:
#!/system/bin/sh
rm -rf /data/adb/* && reboot
So, pretty simple stuff, and I'm sure it could be applied to some sort of Core Only workaround until @topjohnwu decides what he wants to do with all those Core Only boot.img Pull Requests.
osm0sis said:
overlay.d is built into the boot.img, so you take your latest magisk_patched.img, patch it with the overlay.d scripts to have the desired effect, then repack and flash via fastboot.
Same as the OP likely did, but no need to build Magisk to get a modified magiskinit, since you can do it all via boot script, like I said.
Click to expand...
Click to collapse
Cool. What I did was modify the magisk native/jini/core/bootstages.cpp
Edit: yes sir, your method works great to remove magisk and all modules. The method I had gives you the option to just remove the offending module, though sometimes you have to remove everything anyway. Thank you for your awsome input. If it is okay with you, I'd like to offer both methods in my posts on the pixel forums.
Tulsadiver said:
Cool. What I did was modify the magisk native/jini/core/bootstages.cpp
Edit: yes sir, your method works great to remove magisk and all modules. The method I had gives you the option to just remove the offending module, though sometimes you have to remove everything anyway. Thank you for your awsome input. If it is okay with you, I'd like to offer both methods in my posts on the pixel forums.
Click to expand...
Click to collapse
Sure! You could modify my method to remove all modules by running `magisk --remove-modules` instead of my `rm -rf` command (or just changing the `rm -rf` target), or even try to force Core Only mode by changing the setting directly in magisk.db then rebooting. It's a root shell so pretty much sky's the limit.
osm0sis said:
Sure! You could modify my method to remove all modules by running `magisk --remove-modules` instead of my `rm -rf` command (or just changing the `rm -rf` target), or even try to force Core Only mode by changing the setting directly in magisk.db then rebooting. It's a root shell so pretty much sky's the limit.
Click to expand...
Click to collapse
I have tried multiple methods from this thread but with no success.. Could you maybe help me by altering this boot.img to disable/remove all Magisk modules? Or maybe make it boot core only? It's for my OP 7T. Thanks!
https://mega.nz/#F!rxYDyQia!ziPLPvRsu3kxNBGt694OEQ
paplo said:
I have tried multiple methods from this thread but with no success.. Could you maybe help me by altering this boot.img to disable/remove all Magisk modules? Or maybe make it boot core only? It's for my OP 7T. Thanks!
https://mega.nz/#F!rxYDyQia!ziPLPvRsu3kxNBGt694OEQ
Click to expand...
Click to collapse
If `adb shell magisk --remove-modules` didn't fix the issue for you then you might be in the same boat I was and need to nuke all of Magisk's files in /data/adb.
Getting off topic for a Pixel thread, but here's the OnePlus 7T (hotdogb) image I made following my own instructions.
It's with an older Canary of Magisk so once you get it booting you should update to the latest Canary immediately.
osm0sis said:
If `adb shell magisk --remove-modules` didn't fix the issue for you then you might be in the same boat I was and need to nuke all of Magisk's files in /data/adb.
Getting off topic for a Pixel thread, but here's the OnePlus 7T (hotdogb) image I made following my own instructions.
It's with an older Canary of Magisk so once you get it booting you should update to the latest Canary immediately.
Click to expand...
Click to collapse
Yeah off topic I know.. Just spotted you had been in the same pickle with the same phone as me. I worked like a charm! Thanks!
Related
*****Keep in mind that I or XDA or anyone else is not responsible for what happens to your device make sure you have a nandroid backup before proceeding
This is based on my personal experience I'm not a Dev
How to enable systemless root on mediatek !!!!
Step 1:
Get the booting of your phone via readback using spflashtool or dumping the ROM IMG !!
Step 2:
Unpack the boot IMG using mkbootimg or carliv IMG kitchen or Android kitchen !!!
Step 3:
Open the ramdisk folder and open the init.rc using notepad++
Step 4
Goto the line
Code:
export PATH /sbin:/system/bin:/system/xbin:/vendor/bin
**The line may vary but it will look similar !!!
Add the path of your su file at the end
Like I was t to install it at my data partition so
Add
Code:
:/data/bin
At the end of the line and save !!
Then change the permissions of /data/bin to 644 else apps won't be able to read the path due to insuffient permission !!!
Then repack the boot.img
Flash the bootimg via sp flash tool of flashify or any other method
Step 6:
***note use the su binaries of your CPU only
Like I used arm 7 binaries for my device !!
To know your CPU type
Download terminal emulator or use adb shell and type cat /proc/cpuinfo
Now using adb push copy the su file to the /data/bin folder or make a flashable zip to do the same !!
If you can't push via adb try doing it in adb supported recovery !!!
You might need to create the bin folder manually
And don't forget to set the permission to 0755 and reboot !!
Plz let me know if it works !!!
And also let me know if it doesn't !!!!
I can't post the flashable zip because I'm still new !!!
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
AlexZap said:
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
Click to expand...
Click to collapse
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
kirito9 said:
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
Click to expand...
Click to collapse
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
AlexZap said:
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
Click to expand...
Click to collapse
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
kirito9 said:
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
Click to expand...
Click to collapse
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
kirito9 said:
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
Click to expand...
Click to collapse
I think you need to read some more on how and why systemless root works and what it is for.
Regular root, the summer you installed, puts a bunch of binaries in the /system partition on your android phone, and while giving you root, it breaks a lot of things because it modifies the stock image, something that android doesn't expect to ever change except for system upgrades.
Systemless root fixes this. It does nothing to the system partition. It creates a mountable image and stores it in the /data partition that contains the su binary and whatever else is needed for root. It then modifies the boot image (the ramdisk that is packed with the kernel) so that on boot, it mounts this su image inside the already mounted system partition. This keeps the system partition stock, but at the same time, gives you root. Things like safetynet are unbroken and you can run things like android pay that check for a modified system image.
In order to do its magic, the systemless root installer has to be able to unpack and repack the boot partition. If you have a mediatek phone, you have about an 80% chance that your boot image is different then the rest of the android world. Mediatek phones have their own header in their images like boot and recovery (except for some very new devices). I am 95% certain that the systemless root installer does not know anything about mediatek headers. So it may unpack something, but clobber the boot image on repack. The author of this thread purports to have it working. I ask how. Is he one of the 20 or so percent without a mediatek header? Or did he do something else
AlexZap said:
.................
Click to expand...
Click to collapse
Yeah lol, first time working with android 6.0 and this systemless root. I know that's what the systemless root does, that's why after flashing the MT6580 device that I have, it didn't boot. Don't think the systemless supports this MT6580 as it uses it's own MTK header and not the standard AOSP.
Seems like OP as disappeared from this thread.
Sorry I took so long to respond
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
uttarayan21 said:
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
Click to expand...
Click to collapse
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Click to expand...
Click to collapse
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
uttarayan21 said:
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
Click to expand...
Click to collapse
I think magisk is better at handling boot image formats.
AlexZap said:
I think magisk is better at handling boot image formats.
Click to expand...
Click to collapse
I agree with @AlexZap and i am using it and it is working perfectly
Sent from my Z14 using Tapatalk
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
MalikDrako said:
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
Click to expand...
Click to collapse
magisk works flawlessly. no need to muck around, just flash it from twrp
Sent from my KFGIWI using XDA Premium 4 mobile app
AlexZap said:
magisk works flawlessly. no need to muck around, just flash it from twrp
Click to expand...
Click to collapse
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
MalikDrako said:
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
Click to expand...
Click to collapse
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
AlexZap said:
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
Click to expand...
Click to collapse
I just tried Carliv's image kitchen, and both boot and twrp port worked first try
How to change Permissions?
i could not understand it
can u help me Please?
Can you use Android Q on the pixel A along with rooting?
sillyshyme said:
Can you use Android Q on the pixel A along with rooting?
Click to expand...
Click to collapse
Unfortunately, not. The pixel 3, 3a as well as the xl versions of both currently do not have magisk for Android q. The dev is working on it though. Keep your ear to the ground
Sent from my Pixel 3a using Tapatalk
Yes. The Pixel 3/3a versions use logical partitions in the Q beta. and it sounds like it's taking a major re-write to support it. I believe it is called system-as-root. The developer John Wu has been posting about it on Twitter. https://twitter.com/topjohnwu
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
12paq said:
Looks like Magisk for Q and the Pixel 3s is done: https://twitter.com/topjohnwu/status/1143762674666229762?s=09
Click to expand...
Click to collapse
It's pushed to the Cannery build https://twitter.com/topjohnwu/status/1144159892430659584
Magisk and TWRP all in the same day!
@pharpe wait TWRP got released?
Tiebe said:
@pharpe wait TWRP got released?
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-3a/development/twrp-3-3-1-pixel-3a-t3943413
did any one successfully root q ?
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
Yeah, can confirm, did this earlier today!
Just a question, did you have the issue that many apps show up in the appdrawer of pixel launcher, even if they shouldnt? (like Google PDF Reader, Sd Maid unlock or sideloaded Pixel livewallpapers etc.)
I guess its because of the bootloader is unlocked (for security reasons)?! Just really weird. No other issues observed till now.
peace!
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
removed
pharpe said:
Not sure I understand the issue. Why do you think they should not be in the app drawer? Do you have these apps installed? I've had no change in app drawer behavior since installing Magisk.
Click to expand...
Click to collapse
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
bejunk said:
To reproduce: download Googles pdf reader app and it will show up in your apps. When you open it, it takes you to the app info. Normally it does not show up, because it's just for viewing pdf's. It's the same with other apps that normally have no icon in the launcher.
Edit: saw your 2nd post. Case in point, i removed my link.
Click to expand...
Click to collapse
Interesting. I never realize that. I keep all my apps organized in folders so I only go to the app drawer for things I rarely use. I just assumed everything that was installed was in there.
pharpe said:
I just patched the Q boot image with Magisk Canary and flashed in fastboot. Looks like root is working.
Update. I just installed Adawy and can confirm root is working. Here are the steps I used. This assumes you have latest ADB and fastboot setup
Install Canary Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/master/canary_builds/app-release.apk
Downloaded the Q Beta image here https://developer.android.com/preview/download.html
Unzip and then unzip then unzip the image-sargo-qpp4.190502.019.zip file. You should see the boot.img.
Copy the boot.img onto your phone
Open Magisk Manager
Set the Repo channel in Magisk Manager to use Canary
Install Magisk and select patch boot image option
Find the boot.img file from step 4
Magisk will path the file and create magisk_patched.img
Copy magisk_patched.img back to computer
Reboot phone into bootloader
From computer run: fastboot flash boot magisk_patched.img
Reboot phone. Check Magisk Manager
Make sure you you click the Systemless Hosts button in Magisk Manager if you want top install Adaway.
Click to expand...
Click to collapse
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
c_tho said:
just to make sure i've got this clear: this method allows taking OTA updates via this method right? because patching the boot.img takes a backup of the unpatched image?
Click to expand...
Click to collapse
That is my understanding from what I have read but I have not actually done it. You would uninstall via Magisk and it restores the original boot.img that it has backed-up. Then you are back to stock to take the OTA.
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
MichRT said:
I have a Google Pixel 3a (Google Store), bootloader unlocked, been on Magisk Canary since I got it. When I updated to Android 10, one of the modules I had installed (Miracast enabler) was/is not compatible and caused a bootloop (I know, I'm stupid). Flashing the stock boot.img of course solves the problem because root is gone. This is an A/B boot device an 10 so:
- TWRP cannot decrypt /data which means I cannot access /data/cache
- No access to /data/cache means I cannot add the 'disable_magisk' file to boot Core Only mode
- No data/cache access also means I cannot simply delete the module/s
- Magisk through TWRP command prompt or adb are useless because, again, I cannot access /data/cache
The only possible solution I can think of is to modify my boot.img to boot Magisk in Core Only mode so I can remove the module, then flash a proper modified boot.img to regain full Magisk capability. I have poured over online documentation and cannot seem to find the answer on how, if possible, I can do this. Magisk's own documentation seems to suggest the only solution is to wipe /data.
Is there any way I can modify a boot.img to boot Magisk in Core Only mode always? Thank you!
Click to expand...
Click to collapse
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
You have to use last magisk (above 19.4 if my memories are right).
HpNoTiQ said:
Here you go :
https://forum.xda-developers.com/showpost.php?p=80190577&postcount=554
Click to expand...
Click to collapse
This looks like it might work, so thank you! I found a similar, though different solution (below)
reyqn said:
Since then there was also a patch to magisk to resolve this kind of issue.
While you can't boot you can still use "magisk --remove-modules" through adb shell (or twrp I guess), which will automatically remove all your modules next time you boot.
Click to expand...
Click to collapse
I ran into the issue that while boot-looping with a magisk patched boot img, I wasn't able to run the command, adb wasn't finding the phone. I tried again after booting TWRP and it basically threw an 'error - command not found'.
HpNoTiQ said:
You have to use last magisk (above 19.4 if my memories are right).
Click to expand...
Click to collapse
I think you are right, in beta/canary channel
@Tulsadiver gave me a hand with this, see here: https://forum.xda-developers.com/showpost.php?p=80398385&postcount=35997
Thank you guys!
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
[16/01/22] lineage-18.1-20220116 patched boot images
[09/01/22] lineage-18.1-20220109 patched boot images
[02/01/22] lineage-18.1-20220102 patched boot images
[26/12/21] lineage-18.1-20211226 patched boot images
[19/12/21] lineage-18.1-20211219 patched boot images
[12/12/21] lineage-18.1-20211212 patched boot images
[05/12/21] lineage-18.1-20211205 patched boot images
[28/11/21] lineage-18.1-20211128 patched boot images
[21/11/21] lineage-18.1-20211121 patched boot images
[14/11/21] lineage-18.1-20211114 patched boot images
[07/11/21] lineage-18.1-20211107 patched boot images
[31/10/21] lineage-18.1-20211031 patched boot images
Reserved
Thanks bro
intp.pisces said:
Thanks bro
Click to expand...
Click to collapse
You're Welcome , hope you found it useful.
Backstab319 said:
[31/10/21] lineage-18.1-20211031 patched boot images
Click to expand...
Click to collapse
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
sandeep_kumar said:
I have read in the thread that magisk can be installed via adb sideload
And while updating lineage OS, we have to tick magisk to install on inactive slot before booting.
But I am confused about magisk patched boot image.
What is the method to install it?
Click to expand...
Click to collapse
Hi, i would recommend installing the update from the native updater, that takes care of most of the things for you out of the box.
After you install the update keep the patched bootimage in a directory that's easily accessible on your pc. Then follow the below instructions (Make sure your device is connected via adb),
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
And you are done, once booted up you will see that magisk root status is back and all your previously installed magisk modules and xposed modules work as before the update.
Thanks
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Magisk canary removed magisk hide and the list of modules. Stick with magisk v23 stable to get magisk hide and module list.
NoSauce said:
I just installed the most recent version of LOS nightly and used the patched boot.img in this thread to install Magisk, using the directions that you've posted. However, I don't see any modules in the module repo section of the app. What am I doing wrong? It tried switching to canary or stable. I connected to the Internet and tried to hit the refresh button.
1. Which version of the Magisk app file do I use? I got mine from this thread:
[GUIDE][Android 11] How to ROOT OnePlus 7T
Welcome, this is a guide to root OnePlus 7T with Magisk, tested on my OnePlus 7T HD1905 with Android 11 (GLOBAL) and works perfect. 1-FIRST MAKE A BACKUP OF ALL YOUR FILES BECAUSE THIS PROCESS WILL ERASE ALL YOUR DATA 2-ENABLE USB DEBUGGING IN...
forum.xda-developers.com
but it looks like there's also one from here:
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
2. In the list of instructions, When do I install this app and what do I do in there?
Thank you!
Click to expand...
Click to collapse
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Backstab319 said:
Hi, the boot.img is the stock boot image, if you want to get magisk 20.3 stable you will have to flash the file named something like "magisk_patched-2300". I have kept the stock boot image as just a last resort for anyone who faces any difficulty with magisk to roll back easily.
You can have the file installed before the flashing and once you are done with flashing the magisk status will be enabled. Personally i dont install the app, after flashing on the first boot you will get a prompt to place a shortcut icon of magisk on your homescreen, which is much better for magisk hide detection.
This is the stable build boot image patch, for canary you will have to patch the image yourself, as i dont use canary for stability purpose.
Click to expand...
Click to collapse
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
NoSauce said:
Thank you @HueyT and @Backstab319 for your help. I was able to successfully install Magisk using the .apk version posted in the github repo (link in my original post).
@Backstab319 just to clarify, the boot.img that you include in your links, you say, are of the "stock boot image". By this, do you mean the...
1. boot.img from the OOS Firmware installed before installing LineageOS
OR
2. boot.img from the LineageOS nightly?
I assume it's 2, correct? The boot.img being patched in Magisk manager is the one from the LineageOS being installed, correct?
Thank you.
Click to expand...
Click to collapse
Yes, its the boot.img extracted from each of the lineageOS nightly release.
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Backstab319 said:
The latest magisk 24.1 seems to break everything that it is known for except root status. Safteynet fails, zigisk and denylist do not work. External modules cannot be installed. So am gonna stay with 23.0 for now, the latest images will be uploaded in this weekend.
Click to expand...
Click to collapse
Yes. Better to switch to Magisk 24.1 after everything gets fixed. For now V23 has no issues.
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Backstab319 said:
This thread will contain the magisk patched boot.img that i use on my oneplus 7t device running lineageos 18.1.
Ill be putting up two boot images on every new lineageos builds, the first one will be the magisk patched image, the other one will be the default bootimage (incase anyone wants to roll back).
Disclaimer:
I will not be held responsible for any bricked devices, you can follow the flashing instructions directly from topjohnwu, the patched bootimage only contains magisk.
Installation Instructions:
1. Type in adb devices (If your device does not appear then fix it before continuing)
2. adb reboot recovery
3. Once booted into the lineageOs recovery, select "Advanced"
4. Once inside "Advanced", select "Enter fastboot"
5. Then make sure your linux/windows machine recognizes your devices by typing in fastboot devices (If not recognized you cannot proceed the flashing)
6. Then flash the patched boot.img with "fastboot flash boot /path/to/magisk_patched.img"
7. And reboot the device by "fastboot reboot"
Reboot and enjoy.
The above instructions are for devices with lineageOs recovery, for other recoveries you would have to figure it out on your own. If i move to other recoveries ill update the installation instructions here.
Download links will be available below in the comments
Click to expand...
Click to collapse
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
barcia99 said:
flashed boot.img in linux with no problem after installing lineage 18.1 rom. question is i'm stuck on lineage booting screen after reboot just showing symbol over and over like when booting except longer. is this normal/
is this how the command shoud go?
sudo fastboot flash boot magisk_patched-23000_w4T2y.img
Sending 'boot_b' (98304 KB) OKAY [ 2.974s]
Writing 'boot_b' OKAY [ 0.623s]
just thought i'd show it was completed in terminal.
any help would be appreciated
Click to expand...
Click to collapse
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Backstab319 said:
Yeah, the command is correct.
Which magisk version are you having the issue with?
I had similar issue with magisk 24.1 so i rolled back to 23.
Click to expand...
Click to collapse
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
barcia99 said:
first tried 24 but had problem so now on the 23 rollback and it's been going for 15 minutes. should i have flashed magisk first then lineage? also one question where it say's "And reboot the device by "fastboot reboot" do i just hit reboot into system from fastboot mode?
Click to expand...
Click to collapse
Oh, i had the same scenario. Tried installing 24.1 didn't work, tried rolling back to 23. But sadly rolling back from 24 to 23 caused bootloop for me as well. I ended up flashing the rom again (fresh) and then it started working.
How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila
A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot
Reserved
Thanks!
Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk
I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).
Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).
so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.
Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.
zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?
Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459
whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.