Related
This guide lets you install any GSI treble roms on our Daisy.
Read carefully and go step by step!
Update: Since Havoc OS doesn´t need permissive Kernel, I just installed the latest stock rom (9.6.9.0), flashed Havoc, set everything up and ended with sh...t... Camera´s not working, Opera freezes, everything sucks. It was a waste of time... So it´s still the situation:
If you want to use a custom GSI-Rom Only use this combination: Stock rom before flashing GSI: 9.6.4.0 and Kernel: Unofficial TWRP by Yshalsager - this combination works like a charm
Let´s get started: Be sure you are on Stock 9.6.4.0 (july security patch) if not, your wifi will not work in treble rom!
1) Download latest AB arm 64 gsi build. - ONLY ARM 64 AB GSI WILL WORK!
2) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/sho....php?t=2588979 and install it!
3) Extract gsi64-ab-image to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt as admin and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> your screen will show FASTBOOT - connect your phone to your PC
6.) type in your command prompt
Code:
fastboot oem unlock
Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- to enter fastboot.
Now you have to decide: If you want to use Android 9 roms and TWRP together, you have to decrypt your data - else TWRP will not be able to read data! If you don´t care continue on step 11
8.) Download a patched_boot.img and place it in your fastboot folder - since only 9.6.4.0 works without bugs, you have to choose the patched 9.6.4.0 boot
9)
Code:
fastboot boot patched_boot.img
10) Connect to internet and update Magisk manager, download a root explorer - you could use this and go to
/vendor/etc/ and open the file fstab.qcom in editorreplace the text "forceencryption=footer with "encryptable=footer" and reboot to bootloader
11) Download this, rename it to boot.img and copy it to your fastboot folder
Code:
fastboot flash boot boot.img
12) Install official TWRP
13) After installing official TWRP reboot to TWRP agian and go to "wipe" -> "format data" and type "yes". Reboot to bootloader
14.) Download your GSI AB Image and place it in your fastboot folder
Code:
fastboot flash system [imagename].img
If you want, you can boot now to twrp and install magisk and/or gapps whatever - everything will work. Else you boot up your new system - Sometimes your GSI-rom will not boot up without a rooted kernel.
So if you stay in bootloop, just install magisk.zip!
Violla - Now you have a treble gsi rom on your Mi A2 Lite!
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
tutankpusch said:
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
Click to expand...
Click to collapse
Updated: I removed that line...
merlin.berlin said:
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
Click to expand...
Click to collapse
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
elkhshap said:
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
Click to expand...
Click to collapse
If you like to have more features and/or pie (Android 9), then I would suggest to flash a custom gsi rom. If you can live with stock, I wouldn´t touch it.
Voodoojonny said:
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
Click to expand...
Click to collapse
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
merlin.berlin said:
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
Click to expand...
Click to collapse
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Voodoojonny said:
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!b) Download latest havoc and place it in your fastboot folderc) Download this TWRP and place it in your fastboot folder - you need this as Kerneld) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.imge) copy userdata.bin from stock to fastboot
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!after doing all the steps:
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Click to expand...
Click to collapse
Please explain by video
thank you so much for this guide:good:
i'll try it later when im home:fingers-crossed:
Where do I find a userdata.bin file?
monzer said:
Where do I find a userdata.bin file?
Click to expand...
Click to collapse
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Voodoojonny said:
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Click to expand...
Click to collapse
Please post a video for ease of action
monzer said:
Please post a video for ease of action
Click to expand...
Click to collapse
Sorry, that will not happen!
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Voodoojonny said:
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Click to expand...
Click to collapse
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
Voodoojonny said:
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
Click to expand...
Click to collapse
Lol, this site has gone way down hill... It's almost a joke now.
So many people asking for the 'easy' way and want answers to easily searchable questions. Sooo many multiple posts, and people not wanting to do the research themselves. How many threads need to be created on bricked devices because you didn't heed the warnings or follow the directions...
I wonder if xda even cares? This place use to be a great tool for the ones who like to tinker.
There are definitely a few folks keeping the spirit alive, but so many unnecessary posts - like what I'm writing right now...
Anyway thanks to anyone who puts time and effort for the greater good, we should all understand that tinkering with our devices can potentially have adverse effects.
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Bokoko006 said:
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Click to expand...
Click to collapse
You're welcome. Don't have problems with bugs and havoc 2.0... Interesting to test would be arrow pie! Benzo had problems with camera and flashlight... All the 8.1 can't handle the notch and overlay!
Quick and concise how to for obtaining a Stock Boot Image from your Oneplus 8, 8T or 8 Pro device and patching with Magisk to create a fastboot flashable patched boot.img.
DISCLAIMER:
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked, broken or dead devices. This is a high-level
* how to for users with a basic knowledge of ADB and Fastboot. YOU alone are
* choosing to make these modifications, and you are solely responsible for your
* device's fit for use and wellbeing.
*
* Backup your data!
*
*/
PREREQUISITS:
An unpatched Stock Boot.img running on your device
General knowledge and understanding of ADB and Fastboot
Download latest op8, op8p, or op8t Horizon Kernel img from [e.g., op8p_7.img]:
https://dl.akr-developers.com/?dir=oneplus/horizon_kernel/R/images
Download latest Magisk Canary build from Github [e.g., app-debug.apk]:
https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
DEVICE/PC OPERATIONS:
→ ADB
Enumerate devices
Code:
adb devices
Boot into Fastboot
Code:
reboot bootloader
→ FASTBOOT
Enumerate devices
Code:
fastboot devices
Determine the current slot (A/B), whichever slot you're on should be the "good" img
Code:
fastboot getvar current-slot
Boot with the custom kernel downloaded from Horizon to use root [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot boot "C:\Users\User\Downloads\op8p_R7.img"
Code:
fastboot boot xxxxxxx.img
→ ADB
Copy the boot.img from each slot to the root of the device
Code:
adb shell
su
dd if=/dev/block/sde11 of=/sdcard/boot_a.img
dd if=/dev/block/sde35 of=/sdcard/boot_b.img
→ Android Device [NOTE: Some Android 11 devices experience patching issues on the Beta Channel like bootloop] [NOTE: Some users experience issues on Canary like no SIM detected; if so switch to Beta]
Install Magisk app-debug.apk (Canary)
Go to Settings → Update Channel → Canary
Go to Home → Install → Install → Select and Patch A File
Navigate to internal storage and select the stock boot.img [choose the img from whichever slot you're on]
When it’s done patching copy the file, named magisk_patched.img, from the root → Downloads of your device to PC
→ ADB
Code:
reboot bootloader
→ FASTBOOT
Test to ensure it boots before flashing; if not you'll need to patch the other img
Code:
fastboot boot magisk_patched.img
→ Android Device
If the device boots and you have root in the Magisk Manager app, reboot the device into Fastboot then flash the active slot [NOTE: Both slots do not need to be flashed; just the current active slot]
→ FASTBOOT
Flash the patched image file [NOTE: Include the full path of the img if not in the same directory]
e.g., fastboot flash boot_b "C:\Users\User\Downloads\magisk_patched.img"
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
- OR -
Code:
fastboot flash boot_a magisk_patched.img
fastboot reboot
- OR -
Code:
fastboot flash boot_b magisk_patched.img
fastboot reboot
ADDITIONAL RESOURSES:
→ FASTBOOT
If you need to set the other slot to be the active slot use:
Code:
fastboot --set-active=a
- OR -
Code:
fastboot --set-active=b
→ ADB
ADB Magisk Bootloop Fix
Code:
adb shell
magisk --remove-modules
→ OTA Help
Magisk stock boot.img missing fix [NOTE: Android 11 onwards, the /sbin folder might not exist, so Magisk will randomly create a folder under /dev and use it as the base folder]
Rename to: stock_boot_0.img
Compress with gzip = stock_boot_0.img.gz
Copy stock_boot_0.img.gz file to the root of: /data
Edit the config file: /dev/xxxxxxx/.magisk/config → Change SHA1= to 0
Magisk Manager → Uninstall Magisk → Restore Images
→ ADB
Determine the random folder name generated by Magisk on Android 11+
Code:
ls -laR /dev | grep '.magisk/rootdir'
→ ADB
Determine the Boot Image partition location [NOTE: Will list all partitions; look for boot_a and boot_b]
Code:
ls /dev/block/bootdevice/by-name/ -all
Tried some other way on android 11 but failed, so back to android 10.
maybe i won't get android 11 until TWRP is work.
can't easily backup data without root is very annoying, thanks for the work!
I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?
mrram said:
I have followed every step, but root only last until I restart my Oneplus.
What am I doing wrong? Why want the device stay rooted?
Click to expand...
Click to collapse
Guessing here, but have a second look at these two commands:
Code:
fastboot boot magisk_patched.img
△ This will NOT flash the rooted image, it will only boot up once so you can test it or use it for temporary root
verses
Code:
fastboot flash boot magisk_patched.img
▲ This will flash the rooted image and is used after you've tested the patched image to be sure it doesn't bootloop and to have persistent root
If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.
MagikGab said:
If I use this Horizon kernel to boot with root on 11.0.4.4, could I use directly Magisk 22.0 to root the device permanently? Thanks in advance.
Click to expand...
Click to collapse
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.
CarvedArt said:
I only use the Horizon to boot then grab my kernel to patch with Magisk. You could use the Horizon kernel, but you would have to flash it, not just boot it. So, root device, backup stock dtbo, flash Horizon & dtbo, re-root if lost during flash. I would recommend against that until there's a custom recovery available in case there were any issues. Additionally, you must backup your stock dtbo if you ever want to return to stock. You should visit the Horizon thread for more details, but again if you're not familiar with kennel mods you might not want to start learning on a device without a custom recovery.
Click to expand...
Click to collapse
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root
MagikGab said:
I'd like only to root my device, remaining as more stock as possible, for now. If I want to avoid using a custom kernel (also for the rooting process), should I extract the boot.img with Python, then patch it with Magisk 22? Thanks in advance for your reply, but I'm coming from a Xiaomi that was quite easier to root
Click to expand...
Click to collapse
Just follow the steps above -- that'll get you a stock kernel (your current kernel) patched with Magisk and permanently rooted. The above process is only using the Horizon kernel to boot your device with root so that you can extract your kernel and patch it. The final result will be as stock as you can get with root.
Hey everyone. OP8 Pro user here. Just took OTA going from 11.0.9.9 running Magisk Canary 23 to the newest 11.0.10.10. I restored images before taking the OTA and reinstalled magisk to the other slot like I always do to retain root. Ive now lost root and am trying to boot the last two versions of the Horizon kernel. Ive tried the two latest ones (r9.2 and r9.2.1 from February 2021) and while they do boot my phone, I cant get SU access to extract the stock images.
Anything else that anyone things I should try? All i want from Christmas is root.
Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.
Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"
tosho1 said:
Unfortunately I have another problem with my OnePlus8 and Lineage:
I'm using AdAway which replaces the hosts file, but on my OP8 it cannot.
"Unable to cppy the hosts file to /System partition. Please check if the Magisk Systemless module is active"
What does it mean? The Magisk app says: "ramdisk yes"
Click to expand...
Click to collapse
Magisk → Settings (Gear icon) → Systemless hosts ← Click it
tosho1 said:
Isn't there a more easy way to obtain root?
That's strange. I use OnePlus smartphones with LineageOS for years now and cannot remember to execute such a complicated procedure. Just now I got a OnrPlus 8, installed LineageOS and Magisk and restored my apps with Titanium. So, it definitely worked.
Now, after a Lineage system update, root is gone.
Unfortunately I cannot tell exactly how I installed Magisk. I have a very poor memory. Think I just installed the app and said either just "install" or patched the zip with TRWP
But I definitely never downloaded or extracted any boot image manually.
Has anyone an explanation for this?
Even more strange: I just tried to flash magisk.zip again with TRWP. Now it tells me
"Magisk patched boot image detected"
and later:
"Failed to mount '/system_root' (Device or resource busy)"
After reboot the Magisk app now offers me three choices in the install tab:
- choose a file and patch (only this one existed before)
- direct installation (recommended)
- install into inactive slot (after OTA)
I don't understand the last one and tried the recommendet one.
Now, root is there again. Do I have to do this after each update? With my OnePlus5 I didn't.
Click to expand...
Click to collapse
LineageOS is not the stock ROM so it's slightly different and not covered in this thread.
Thank you, CarvedArt. I wasn't aware of this.
Does anyone have the latest stable Android 13 patched boot image for the IN2015 that they can share with me ?
Hey folks,
I have rooted (magisk) OnePlus 8 phone with Android 11, w/o TWRP recovery. I'm trying to replace kernel with one of blue_spark, here's what I'm doing
1. Download zip file from https://github.com/engstk/op8/releases/tag/r112
2. Extract and unpack Image.gz
3. Unpack Magisk patched boot.img to /tmp (magiskboot unpack boot.img)
4. Replace kernel with unpacked Image (cp Image /tmp/kernel)
5. Repack boot.img (magiskboot repack boot.img boot-new.img)
6. Boot with boot-new.img (fastboot boot boot-new.img)
And here is when I'm getting into "QUALCOMM CrashDump Mode"
The same result if I build kernel from sources. Repacking boot.img with original kernel works, so problem is unlikely in magiskboot.
I'm trying to figure out the problem, but without kernel logs it's troublesome. Any ideas?
Thanks.
Hm... It looks like, I also have to update DTB. After that device boots successfully. Seems a bit strange to me. What's the difference in supported devices between blu_spark and stock kernel?
Ok, turned out AVB was enabled in the original device tree:
fsmgr_flags = "wait,slotselect,avb";
Switching it off fixes boot process.
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.
It was modified from latest stock kernel of WearOS 2.
Features:
[OC] Overclocked to 1.8Ghz
[Magisk] Magisk v23.0 pre-installed
How To Use :
Reboot to fastboot
You are supposed to try it first in order to make sure it is suitable to your system by using
Code:
fastboot boot boot.img
If your test is passed, you could input the command below to flash it
Code:
fastboot flash boot boot.img
Enjoy
Download Link: MEGA
Cannot get it to work on my W200, stuck on LG logo and heating up considerably
Xspeed said:
Cannot get it to work on my W200, stuck on LG logo and heating up considerably
Click to expand...
Click to collapse
Sorry for having forgotten that the fstab in the ramdisk was modified in order to support the system partition which had been formatted to ext4 by myself.
You could use magiskboot to edit the boot.img by yourself. Just replace the kernel and kernel_dtb by the one unpacked from the stock boot.img and then repack the image file.
Prebuilt magiskboot can be checked here: https://github.com/TeamWin/external_magisk-prebuilt/tree/android-11/prebuilt
If available, I will reupload the correct version in several month.