Now as we have TWRP for any A11-13 ROMs, there's no need for boot image patching, just flash magisk in TWRP.
Hi!
There's a great root guide here on xda by @zymphad and i thought i'd share the boot images for different OOS and Paranoid Android versions.
I'll keep this updated as long as i think it should be.
The boot images are patched with latest Magisk Canary.
OxygenOS
Android 11 & 12
11.2.6.6 - DA/BA
11.2.7.7 - DA/BA
11.2.8.8 - DA only
11.2.9.9 - DA/BA
12.C36 - Global only
12.C44 - Global only
12.C47 - EU only
12.C48 - Global only
12.C60 - DA only
12.C62 - Global only
12.C64 - EU only
12.C65 - EU only
Android 13
13.F16 - Global/EU/India
Paranoid Android
Android 11 & 12
Ruby Alpha 1
Ruby Alpha 2
Sapphire Alpha 1
Sapphire Beta 1
Sapphire Beta 1 (2022.06.11 build)
Sapphire Beta 1 (2022.06.17 build)
Unofficial Sapphire (2022.07.27 build)
Unofficial Sapphire (2022.08.18 build)
Android 13
Topaz Beta 1
Topaz Beta 1 unofficial (2022.11.20 build)
LineageOS 19.1 and PEX users: You can flash Magisk in recovery, you don't need to patch/flash the images. (probably same for crDroid)
[=HIDE]
Just tested 11.2.7.7, works without any issue.
Thanks for awesome work!
Added PA Ruby Alpha 2 images
Added 11.2.7.7BA images
Added crDroid images
EDIT: Now removed from the list, pretty outdated
oops
Added 11.2.9.9DA/BA images.
Not sure it really matters, but here's a Magisk-patched 11299AA boot img:
boot11299AAmagisk.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks, guys just rooted!
q
reaper000 said:
Not sure it really matters, but here's a Magisk-patched 11299AA boot img:
boot11299AAmagisk.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
hello, do u have stock boot img?
qqroza said:
hello, do u have stock boot img?
Click to expand...
Click to collapse
Here you go:
boot11299AAstock.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
reaper000 said:
Here you go:
boot11299AAstock.img | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Click to expand...
Click to collapse
thx, dude, u are a saint
Added 12.C36 images.
EDIT: Flashing these should work for C39 too, but to be sure here are the steps to get latest image rooted:
1. Install latest Magisk Canary
2. Reboot to fastboot mode
3. Type fastboot boot patched_image.img (DON'T FLASH, JUST BOOT)
4. Now the booted image is rooted, but the one on the device is not, so now we have to patch it. Go to Magisk Manager and Install > Direct Install.
5. Reboot
_MartyMan_ said:
Added 12.C36 images.
EDIT: Flashing these should work for C39 too, but to be sure here are the steps to get latest image rooted:
1. Install latest Magisk Canary
2. Reboot to fastboot mode
3. Type fastboot boot patched_image.img (DON'T FLASH, JUST BOOT)
4. Now the booted image is rooted, but the one on the device is not, so now we have to patch it. Go to Magisk Manager and Install > Direct Install.
5. Reboot
Click to expand...
Click to collapse
Thx Marty, it's working for me. I tried with some methods and yours its perfect and functionally
No mirrors found for OOS 12, patched nor stock.
Add: LE2111_12.C.36 12.C36 / DA - Patched and Stock
franko_m19 said:
Add: LE2111_12.C.36 12.C36 / DA - Patched and Stock
Click to expand...
Click to collapse
Has anyone tried to flash the C36 magisk over C39 and obtained root?
avid_droid said:
Has anyone tried to flash the C36 magisk over C39 and obtained root?
Click to expand...
Click to collapse
+1
C39 file boot doesnt find it?
avid_droid said:
Has anyone tried to flash the C36 magisk over C39 and obtained root?
Click to expand...
Click to collapse
It´s the same boot file. Now it´s working for me but only with Magisk Canary.
iaio72 said:
+1
C39 file boot doesnt find it?
Click to expand...
Click to collapse
Not, but it´s working with C36.
Related
Hello everyone,
if u want to install Magisk without flashing unoffical TWRP here are the steps. U still need to have unlocked Bootloader:
Seems only Global Version works ... Have a try:
1. Download Systemupdate via OTA
2. Copy it to Computer (located InternalStorage/downloaded_rom)
3. Extract "boot.img"
4. Copy it back to your Mix 2s
5. Install Magisk Manager 5.7.0
6. Open Magisk Manager and click install & install
7. select patch Boot-Image
8. Open "boot.img" with Filemanager
9. After Magisk is finished copy "patched_boot.img" (located InternalStorage/MagiskManager) to PC
10. Boot into Fastboot
11. Flash with "fastboot.exe flash boot patched_boot.img" without ""
12. Reboot Mi Mix 2s and u're rooted now
This Boot-Image is for 9.5.19.0 Global:
https://drive.google.com/file/d/1OPvkYbl5rHRMhb7naJPSEzkQSdAvg1VD/view?usp=sharing
This Boot-Image is for 9.5.20.0 Global:
https://drive.google.com/file/d/1r1Gva4DwVmzgyQB5AYK9mB2hwAXLGedK/view?usp=sharing
Try at your own Risk
MainderX said:
Hello everyone,
if u want to install Magisk without flashing unoffical TWRP here are the steps. U still need to have unlocked Bootloader:
1. Download Systemupdate via OTA
2. Copy it to Computer (located InternalStorage/downloaded_rom)
3. Extract "boot.img"
4. Copy it back to your Mix 2s
5. Install Magisk Manager 5.7.0
6. Open Magisk Manager and click install & install
7. select patch Boot-Image
8. Open "boot.img" with Filemanager
9. After Magisk is finished copy "patched_boot.img" (located InternalStorage/MagiskManager) to PC
10. Boot into Fastboot
11. Flash with "fastboot.exe flash boot patched_boot.img" without ""
12. Reboot Mi Mix 2s and u're rooted now
This Boot-Image is for 9.5.19.0 Global:
h**ps://drive.google.com/file/d/1OPvkYbl5rHRMhb7naJPSEzkQSdAvg1VD/view?usp=sharing
Click to expand...
Click to collapse
Nice workaround, didn't try yet, but i'm tempted to do this way....
So with thsi patched_boot image, it's just follow steps 10, 11 and 12
ruicc said:
Nice workaround, didn't try yet, but i'm tempted to do this way....
So with thsi patched_boot image, it's just follow steps 10, 11 and 12
Click to expand...
Click to collapse
Yes you just need to flash ist with Fastboot and install Magisk Manager
It's very helpful , thanks much .
MainderX said:
Hello everyone,
if u want to install Magisk without flashing unoffical TWRP here are the steps. U still need to have unlocked Bootloader:
1. Download Systemupdate via OTA
2. Copy it to Computer (located InternalStorage/downloaded_rom)
3. Extract "boot.img"
4. Copy it back to your Mix 2s
5. Install Magisk Manager 5.7.0
6. Open Magisk Manager and click install & install
7. select patch Boot-Image
8. Open "boot.img" with Filemanager
9. After Magisk is finished copy "patched_boot.img" (located InternalStorage/MagiskManager) to PC
10. Boot into Fastboot
11. Flash with "fastboot.exe flash boot patched_boot.img" without ""
12. Reboot Mi Mix 2s and u're rooted now
This Boot-Image is for 9.5.19.0 Global:
h**ps://drive.google.com/file/d/1OPvkYbl5rHRMhb7naJPSEzkQSdAvg1VD/view?usp=sharing
Click to expand...
Click to collapse
I'm try but it not work for me. my mi mix 2s not boot
heobanhki said:
I'm try but it not work for me. my mi mix 2s not boot
Click to expand...
Click to collapse
Did you use my patched_boot Image or created you're own?
MainderX said:
Did you use my patched_boot Image or created you're own?
Click to expand...
Click to collapse
I used both, use boot.img patched download from your link and patch my boot by magick.
Reflash boot.img (original) device is good boot.
Sorry for my English.
heobanhki said:
I used both, use boot.img patched download from your link and patch my boot by magick.
Reflash boot.img (original) device is good boot.
Sorry for my English.
Click to expand...
Click to collapse
Anyone else with this problem?
MainderX said:
Anyone else with this problem?
Click to expand...
Click to collapse
The model m1803d5xe version( known as 6GB ram black color version in China, have limited bands) probably has a limit on flashing root( magisk) in the Global rom. It will cause bootloop and currently have no solution. The m1803d5xa version( Global version) works well.
simonsmh said:
The model m1803d5xe version( known as 6GB ram black color version in China, have limited bands) probably has a limit on flashing root( magisk) in the Global rom. It will cause bootloop and currently have no solution. The m1803d5xa version( Global version) works well.
Click to expand...
Click to collapse
Could be possible. I got the m1803d5xa and it works well. Added it to my First Post
simonsmh said:
The model m1803d5xe version( known as 6GB ram black color version in China, have limited bands) probably has a limit on flashing root( magisk) in the Global rom. It will cause bootloop and currently have no solution. The m1803d5xa version( Global version) works well.
Click to expand...
Click to collapse
Oh yes yes, this maybe!!!! My model m1803d5xe
So if m1803d5xa works and m1803d5xe doesn't it's exactly the same problem as when flashing Magisk 16.4 with TWRP:
All devices with xe will bootloop. The only difference is, your variant without TWRP doesn't work on Chinese ROMs, only global. But flashing 16.4 on xa model and Chinese ROM works
underlines said:
So if m1803d5xa works and m1803d5xe doesn't it's exactly the same problem as when flashing Magisk 16.4 with TWRP:
All devices with xe will bootloop. The only difference is, your variant without TWRP doesn't work on Chinese ROMs, only global. But flashing 16.4 on xa model and Chinese ROM works
Click to expand...
Click to collapse
You can install Magisk on m1803d5xe with Chinese ROM. It works fine, but gpay don't works.
So basically magisk only works if you are running native rom for your phone model? What about 256gb version?
I am very confused about which method can be used on which model and ROM. I try to read again through the different threads.
I tried to come up with a matrix that shows all working and non working ways. Can anyone help me to correct and complete this please?
View attachment 4518265
underlines said:
I am very confused about which method can be used on which model and ROM. I try to read again through the different threads.
I tried to come up with a matrix that shows all working and non working ways. Can anyone help me to correct and complete this please?
Click to expand...
Click to collapse
I have a d5xa and it works with patched boot image. I'm on global rom
underlines said:
I am very confused about which method can be used on which model and ROM. I try to read again through the different threads.
I tried to come up with a matrix that shows all working and non working ways. Can anyone help me to correct and complete this please?
View attachment 4518265
Click to expand...
Click to collapse
I don't know if i can help, but i have the XE Model (chinese version).
I'm using the last Xiaomi.eu rom (8.5.17), it's rooted with Magisk 16,4 and 'ive installed TWRP from notsyncing. No problems so far.
If you need some screenshots, i'll post them.
XE model. Magisk work's fine if install via TWRP on developer, global, xiaomi.eu chinese rom.
Thanks for the tuto but it don't work, i'm in France with a global 9..5.4.0, the tuto was fine but when i did the fastboot, it wrote FAILED Flashing is not allowed in lock status. I unlock my phone but i have to wait the famous 360 hours. Do you think it's for that it don't work ?
Thanks again for the tuto
bazochien said:
Do you think it's for that it don't work ?
Click to expand...
Click to collapse
OP: "U still need to have unlocked Bootloader"
This is the answer to your question.
You need patience and wait the infamous 360 hours (so do I, sadly).
Lineage 17.1
Custom ROM for the LG G7 ThinQ
WARNING: Discontinued
No more Updates from me
This is Lineage 17.1 (Android 10) ROM designed for the LG G7 ThinQ. It was designed with the help of @thenotonly and @SGCMarkus and without them this would not have been possible. Thank you guys for all your help!
Supported models:
Anything that can go into Fastboot
(exept T-Mobile model G710TM and Korean users will have a hard time following the guide)
Warning: You need to have Android 9.0 Stock pre-installed.
Warranty Void:
I am not responsible if you are late for work, missed an important call, got yourself stuck under a rock or break your TV with a wii remote. That also includes turtles. Make sure everything important is working for you before you decide to use this ROM as a daily driver.
Click to expand...
Click to collapse
What is working:
Auto-brightness
Camera
Calls
DAC Controls
FM Radio
NFC
Bluetooth
WiFi
SDCard
Always on Display
Vibration
Most stuff i haven't mentioned
What are the Bugs:
Hotspot Fixed
Bluetooth Audio (Workaround)
USB Hotspot
The ones that are still hidden
Click to expand...
Click to collapse
Download link:
There are 2 Versions. One with Google apps (Gapps) pre-installed and one without Google apps (Gapp-less) witch is for people who dont like Gapps and want an alternative like Nanodroid (Not included).
Google Drive Folder for the LIneage 17.1
Click to expand...
Click to collapse
Installation:
Step 1: TWRP
Backup any data you have (including music, photos, etc)!
- You cannot do that in TWRP!
FIrst you need to boot TWRP. You can refer to the Guide right here
TWRP Guide for the LG G7 ThinQ < -- Link
Once you meet all the requirements boot into TWRP and proceed to step 2
Step 2: Installing
In TWRP go to Wipe -> Format Data. ( This will wipe absolutely everything on the phone.)
Connect your phone to your PC.
Download Lineage 17.1 Installation zip file from Google Drive and copy it to your phone
In TWRP go to Install -> Find your zip file -> Install it
Once done reboot the phone
Done
Step 3. Install Magisk (Optional)
Make soure you have successfully booted into LineageOS
Reboot to bootloader
Boot into TWRP using "fastboot boot"
Download Magisk zip file from the official Magisk XDA thread (Google it) to your phone
Install Magisk zip
Reboot to system
Done.
Click to expand...
Click to collapse
Congratulations! Now You have LineageOS installed on your device! WooHoo! :victory:
Sources:
https://github.com/LameMonster82/android_device_lge_judyln
https://github.com/LameMonster82/android_device_lge_sdm845-common
https://github.com/LameMonster82/proprietary_vendor_lge
https://github.com/TheNotOnly/android_kernel_lge_sdm845 (Kernel by @NotTheOnly)
XDA:DevDB Information
LineageOS 17.1, ROM for the LG G7 ThinQ
Contributors
LameMonster82, @thenotonly,@SGCMarkus
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9.0 pre-installed + TWRP guide
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 202200218
Stable Release Date: 2020-02-18
Created 2020-02-19
Last Updated 2020-04-17
Reserved
Changelog 2020-04-18
- Updated Gapps
- Fixed Bluetooth bug
- Updated Security patch
- Switch Kernel
- Added OTA Updates support (20200401 and up versions)
- Some other changes I forgot about
Changelog: 2020-03-02
- Updated Gapps
- Fixed Hotspot
- Fixed some issues with the LED
Changelog: 2020-02-18
- Initial commit
Is there a working AOD?
FluffyDiscord said:
Is there a working AOD?
Click to expand...
Click to collapse
Yes there is
Does GCam works? 6.2 version
This being unofficial, how do we get updates and how are they installed?
does vibration works?
It does not start, it starts defront the rom stock, as if nothing had been installed.
Modelo LG G7 Thinq G710EM
HimikoMw said:
It does not start, it starts defront the rom stock, as if nothing had been installed.
Modelo LG G7 Thinq G710EM
Click to expand...
Click to collapse
I answer myself, it is necessary to have android 9, but of the European version
Stvn77 said:
does vibration works?
Click to expand...
Click to collapse
It's not in the "not working" list so it works.
Does the aod work the same as the official system?Use a second backlight?
Hi guys i got the G710N korean version. how can i root and install this rom? do i've to convert to another firmware?
First Thank You for such great ROM!
I think for now there is no way to root this ROM on korean version. I tried to Install this Rom, next I changed with LGUP only boot_a using partition.dl for flash boot from ULM 11g ROM to unlock fastboot, flashed twrp (after this step I was able to boot stock ROM from slot a) and installed magisk from TWRP to boot_b which is used by LineageOS (select slot b in TWRP) after magisk install bootloop. Tried also flash only boot_b with ULM 11g boot same result.
I think there is problem with booting this with any other boot installed.
Aseiel said:
First Thank You for such great ROM!
I think for now there is no way to root this ROM on korean version. I tried to Install this Rom, next I changed with LGUP only boot_a using partition.dl for flash boot from ULM 11g ROM to unlock fastboot, flashed twrp (after this step I was able to boot stock ROM from slot a) and installed magisk from TWRP to boot_b which is used by LineageOS (select slot b in TWRP) after magisk install bootloop. Tried also flash only boot_b with ULM 11g boot same result.
I think there is problem with booting this with any other boot installed.
Click to expand...
Click to collapse
You can't keep twrp with lineage you have to Fastboot boot Twrp image and flash magisk zip
SELinux permissive? enforcing?
mr3p said:
SELinux permissive? enforcing?
Click to expand...
Click to collapse
Permissive
they know which version of Gcam works in this rom (lineage os 17.1)??
Thank you very much. It's great to see some progress on this phone. Works on G710EAW.
HimikoMw said:
they know which version of Gcam works in this rom (lineage os 17.1)??
Click to expand...
Click to collapse
These are the ones that are working for me...
LGN2_MGC_6.1.021_MI8_V1d
LGW2_MGC_6.1.021_MI8_V1d
theParanoid04 said:
These are the ones that are working for me...
LGN2_MGC_6.1.021_MI8_V1d
LGW2_MGC_6.1.021_MI8_V1d
Click to expand...
Click to collapse
Thank you, you know why the photo is not saved when the HDR is activated, it stays in processing HDR +, in the LGW2_MGC_6.1.021_MI8_V1d.
Just Posted
https://developers.google.com/android/images#sunfish
fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs
hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.
moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary
@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)
fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik
tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints
Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy
I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?
Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk
So im kinda lazy, and don't want to make a new thread for each of my builds, so i will share them here if they are decent enough.
INSTALLATION:
You MUST have an unlocked bootloader
TINY FASTBOOT SCRIPT - First Time Install / Clean Flash
1. Download the ROM zip and TinyFastbootScript
2. Extract both zip files into the same folder on your PC
3. Run flash.bat and install latest Motorola drivers
4. Reboot device to bootloader mode and connect to PC
5. Select Flash Custom Firmware (option r)
6. Wait for the program to flash all images
7. After flashing, in the tinyfastboot main menu, press n, then press 3, then type fastboot -w and enter
8. Once finished, Reboot to System
Update / Dirty Flash
1. Download the ROM zip
2. Extract the ROM files into the same folder as previous update
3. Reboot device to bootloader mode and connect to PC
4. Select Flash Custom Firmware (option r)
5. Wait for the device to flash all images
6. Once finished, Reboot to System
All my builds will be GAPPS INCLUDED, and no, i WONT make you a vanilla version.
HAVOC-OS 4.16 (April security patch)
https://drive.google.com/file/d/16QLxXqCxdz_5socjV4sVGbHPOBbai-eG/view?usp=sharing
MSM Xtended (november security patch)
https://drive.google.com/file/d/1Irz9eExiix4o9u16AI7j6HDRziSkLnMN/view
Pixel Experience Plus (december security patch)
https://drive.google.com/file/d/1R10N9qay1Ku3TEErWxNIlifkNFET6NIk/view?usp=sharing
Project Sakura 5.2 - (january security patch)
https://drive.google.com/file/d/15v18B0z6m2lf1LyaL9MQJpvubtUiS5C1/view?usp=sharing
dotOS 5.2.1 (november security patch)
https://drive.google.com/file/d/1g9GL6H5dixe62DbEzcQRD95ljgZ5W_B7/view?usp=sharing
Kernel Source Code: https://github.com/moto-sm8250/android_kernel_motorola_sm8250
Device Source Code: https://github.com/moto-sm8250/android_device_motorola_nio
Device-Common Source Code: https://github.com/moto-sm8250/android_device_motorola_sm8250-common
Vendor-Common Source Code: https://github.com/moto-sm8250/android_vendor_motorola_sm8250-common
Vendor Source Code: https://github.com/moto-sm8250/android_vendor_motorola_nio
Special thanks to @Electimon for all his help!
18-11-21 - Havoc OS and MSM Xtended added
20-11-21 - Pixel Experience plus added (not fully tested, but all major things working)
22-12-21 - Havoc OS 4.12 added
02-01-22 - Pixel Experience Plus added (december patch)
21-1-22 - dotOS 5.2.1 added
29-1-22 - Project Sakura and Havoc updated to january security patch
18-3-22 - Havoc OS 4.14 added (feb patch)
Thank you will test these
Tested MSM Xtended dont boot on moto g100 just restarts on boot.
Pixel Experience plus is well dont boot on my g100 do i missing something to do ? did all instruction how to flash same just restarts to bootloader.
Any help how get running these all not working on g100
rackis18 said:
Any help how get running these all not working on g100
Click to expand...
Click to collapse
Try formatting data (fastboot -w) in the bootloader
rackis18 said:
Tested MSM Xtended dont boot on moto g100 just restarts on boot.
Click to expand...
Click to collapse
This one has been tested by a g100 user and i was told it boots up
Beetle84 said:
This one has been tested by a g100 user and i was told it boots up
Click to expand...
Click to collapse
That's interesting because on my g100 it won't boot just reboot into bootloader. I did format data etc in tiny script.
@rackis18 Open tiny fastboot script, press n and then 3 and type fastboot -w, enter and reboot
rackis18 said:
That's interesting because on my g100 it won't boot just reboot into bootloader. I did format data etc in tiny script.
Click to expand...
Click to collapse
Hey mate, just heard back from a guy on telegram with a g100, it boots up fine for him.
Beetle84 said:
Hey mate, just heard back from a guy on telegram with a g100, it boots up fine for him.
Click to expand...
Click to collapse
Which one you own, g100 or Edge S?
Windoors said:
Which one you own, g100 or Edge S?
Click to expand...
Click to collapse
I have the edge S mate
I can boot any other rom from here and they boots and works no problems but these 3 have issues on g100 i think needs to look at these mate. Thanks
rackis18 said:
I can boot any other room from here and they boots and works no problems but these 3 have issues on g100 i think needs to look at these mate. Thanks
Click to expand...
Click to collapse
The latest evo x (november build) is working?
Beetle84 said:
Could you try flashing a vbmeta
The latest evo x (november build) is working?
Click to expand...
Click to collapse
Yes works no problems I'm using it now. Anyway, nice build mate.
Beetle84 said:
@rackis18 Open tiny fastboot script, press n and then 3 and type fastboot -w, enter and reboot
Click to expand...
Click to collapse
This worked mate thanks for help.
rackis18 said:
This worked mate thanks for help.
Click to expand...
Click to collapse
So all good now?
Beetle84 said:
So all good now?
Click to expand...
Click to collapse
Yup. All good. I don't know if that's made any difference before I tried install from stock rom now from evo so just let you know because maybe a reason.
rackis18 said:
Yup. All good. I don't know if that's made any difference before I tried install from stock rom now from evo so just let you know because maybe a reason.
Click to expand...
Click to collapse
Definitely the data format was the problem i think. I changed the instructions to include that instead of the tinyfastboot reset
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE!!!
YOU HAVE BEEN WARNED!!!
Watch dogs is a ROM I created and it started with the OnePlus 9 Pro back in December. I have decided to bring it to the OnePlus 9, it's based on LineageOS & crDroid source & dependencies and I thank them for its use. SafetyNet and CTS passes whether your rooted or not. Modules not required. Most features are the same as crDroid but I have made some adjustments to bluetooth quality and some fonts that are not available there, plus Gapps are included.
Before you begin, if you don't have the latest platform tools installed on your windows machine. Download it here:
DO NOT FLASH GAPPS!!!! THEY ARE INCLUDED IN BUILD!!!!!
Flashing Instructions
First time installation (clean flash):
This update requires OOS 13.1 - 13.1.0.500(EX01) firmware
Backup your data
Download the ROM, and firmware flasher listed further down on this post and place all in your platform tools folder,
Extract all the contents in platform tools, Firmware flasher in folder.
You must flash firmware in bootloader.
Boot to recovery and factory reset then adb sideload
adb sideload WatchDogs-13.0-20230625-lemonade.zip
Reboot to system
reboot to recovery if you want root
adb sideload magisk.apk or adb sideload magisk.zip
Reboot to system
Update installation:
Updates can be sideloaded with custom recovery. Updates do not appear in system updater.
Sources:
ROM
Kernel
Downloads:
ROM
FIRMWARE FLASHER
Bugs?
Let me know.
Initial builds
WatchDogs-WITHGAPPS-13.0-20230312-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230312-lemonade.zip
If you require Google apps, flash the first one only!
If you do not want Google apps, flash the second one only!
You can't cross dirty flash a update which should be common sense. Example, you can't dirty flash the with gapps build then next update, dirty flash the no gapps one.
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Telegram group please
lorilucille9 said:
I tried CRdroid recovery and the one I was on and both said name mismatch. Got any suggestions for me to try? Thank you for the new development too!
Click to expand...
Click to collapse
That's weird. Did you try sideloading the firmware flasher first before the ROM? If you still have difficulties, I will post the dtbo, boot and vendor_boot files for you to flash to make it compatible. I don't have this phone. I have the OnePlus9 Pro so I can't test it. I'm sure it works or there would be other users saying the same thing.
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
lorilucille9 said:
I flashed the firmware successfully and tried it again but still got the same error. It wouldn't hurt to post the kit files and recovery for others too. If you do then I'll try again before I have to head into work in a couple hours.
UPDATE:
I used the CrDroid boot-20230106 file and then sideloaded fw_Oneplus9_IN_OOS13_F20 on both slots and was able to flash the rom on both slots successfully. Will let you know what I find in time and thanks again for another version rom to pplay with
Click to expand...
Click to collapse
Good deal, and no problem. Since I use crDroid sources, I figured that should work. I will still post the files necessary to flash recovery when I get a chance. Let me know if there are any bugs or issues with the ROM itself so I can work on it. Thank you!
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
incesu571 said:
I installed it on my first try without any problems. but I couldn't understand how it differs from crdroid.
Click to expand...
Click to collapse
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
thx bro
TheSayaMan said:
Bootanimation, fonts, bluetooth, sound audio and other tweaks.
Click to expand...
Click to collapse
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
lorilucille9 said:
Not to mention Gapps included if you choose it so OTAs with no issues... otherwise you'd have to sideload Gapps again after at least for me that's what was happening.
Click to expand...
Click to collapse
correct, sorry, forgot to mention that as well. Thank you!! crDroid doesn't offer a with gapps build. You can use the no gapps build to flash your own gapps but I won't support force close issues with the ROM. Example, pixel setup wizard can't be used because it interfers with the default launcher. And yes, on updates, just sideload the with gapps build and your done, unless you want root, then you will have to reboot and sideload magisk because root will be gone on a update.
incesu571 said:
Telegram group please
Click to expand...
Click to collapse
There is one in my 9 pro thread. I will update when I can.
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
Convert your T-Mobile to EU as listed on another thread, then you can use the EU firmware. I will be posting a update soon with the boot, vendor_boot and dtbo. If you don't want to do that, I will post them later to flash recovery on your phone. Keep in mind that different variants act different, so you may have bugs on T-Mobile, it wasn't tested.
screenshots?
pubmastervnt said:
screenshots?
Click to expand...
Click to collapse
Not by me, maybe someone else who is running it
MARCH UPDATES: 03/24:
WatchDogs-WITHGAPPS-13.0-20230324-lemonade.zip
WatchDogs-NOGAPPS-13.0-20230324-lemonade.zip
Sady94 said:
I have op 9 t-mobile version le 2117, can you please guide me which firmware should i use IN, EU or NA?
Click to expand...
Click to collapse
You can use my custom recovery, files added in OP. You still need latest stock A13.
fastboot flash --slot all boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
You cant install this (or any rom but base 11) on tmobile 2117 without BL unlock key. Pretty sure its not possible.
You can only convert to base global 11\OOS11 on 2117 for root, then in ui updater doesnt work OTA or manually. You can get to 13 stock only, because you need to be stock to ota, where you need a key to unlock bootloader again (conversion would bring you back to 11).
*The rooting situation with this phone sucks. I think Jaguar is the only one that will work because it is base 11.