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
Related
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.
i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year
Hey, I installed every GSI of android Q. Which is available for our device. So The Problem is Whenever I try to boot gsi with "GAPPS" It Does Boot But The Setup Screen keeps crashing. So, I can't go further then that and it gets stuck in the Setup Screen.
Any Solution?
AmanDevil77 said:
Hey, I installed every GSI of android Q. Which is available for our device. So The Problem is Whenever I try to boot gsi with "GAPPS" It Does Boot But The Setup Screen keeps crashing. So, I can't go further then that and it gets stuck in the Setup Screen.
Any Solution?
Click to expand...
Click to collapse
Resize system partition.
kraken77 said:
Resize system partition.
Click to expand...
Click to collapse
It's not working, I already tried it
AmanDevil77 said:
It's not working, I already tried it
Click to expand...
Click to collapse
On boot connect your usb and open command prompt.
Follow this command and restart.
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
kraken77 said:
On boot connect your usb and open command prompt.
Follow this command and restart.
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
Click to expand...
Click to collapse
Could you please tell step by step process
AmanDevil77 said:
Could you please tell step by step process
Click to expand...
Click to collapse
When your device is booted connect your phone to pc.
Search for command prompt and open it
Make sure you have adb installed.
Type adb devices
Then type
adb shell settings put secure user_setup_complete 1
Press enter
Type again
adb shell settings put global device_provisioned 1
Press enter and reboot your phone. Done
AmanDevil77 said:
Hey, I installed every GSI of android Q. Which is available for our device. So The Problem is Whenever I try to boot gsi with "GAPPS" It Does Boot But The Setup Screen keeps crashing. So, I can't go further then that and it gets stuck in the Setup Screen.
Any Solution?
Click to expand...
Click to collapse
Can you tell me which Android 10 GSI ROMs booted? I am trying to find one.
blazzer12 said:
Can you tell me which Android 10 GSI ROMs booted? I am trying to find one.
Click to expand...
Click to collapse
it's fixed in new builds, I tried latest pixel experience gsi build and it booted. Everything worked fine except camera, so I reverted back to android pie. I hope someone would find a camera fix for our device in android 10 ROM.
AmanDevil77 said:
it's fixed in new builds, I tried latest pixel experience gsi build and it booted. Everything worked fine except camera, so I reverted back to android pie. I hope someone would find a camera fix for our device in android 10 ROM.
Click to expand...
Click to collapse
Thank you for letting me know! :good:
could you please tell what was the gsi ROM that you installed? yesterday I tried with pixel experience and evolution but it only remained in bootloop
For me Havoc Os 2.9 working perfectly..
Wysłane z mojego SM-A750FN przy użyciu Tapatalka
GSI Problem a7 2018 A750FN
Hi all, i have a problema...... i try to install a gsi10 image (RR7, Piexlex; General, and many more) all rom i install stuck on animation boot...
TWRP 3.2
clear all (cache, system, data, dalvick)
Flash image
Flash Gaaps
Reboot but bootloop on animation
i try to flash also (Permissiver_v5)
someone can help me?? PLS!!
Masok77 said:
Hi all, i have a problema...... i try to install a gsi10 image (RR7, Piexlex; General, and many more) all rom i install stuck on animation boot...
TWRP 3.2
clear all (cache, system, data, dalvick)
Flash image
Flash Gaaps
Reboot but bootloop on animation
i try to flash also (Permissiver_v5)
someone can help me?? PLS!!
Click to expand...
Click to collapse
You need GSI Kernal from "Quantom Kernal For GSI" To Boot the GSI ROM, you can find and download it in the rom and Kernal section of the device on XDA
PS : And also Only download A-Only Arm64 version of the ROM, I have seen that latest build of ROMs work, I have only tried pixel experience and AOSP Yet.
AmanDevil77 said:
You need GSI Kernal from "Quantom Kernal For GSI" To Boot the GSI ROM, you can find and download it in the rom and Kernal section of the device on XDA
PS : And also Only download A-Only Arm64 version of the ROM, I have seen that latest build of ROMs work, I have only tried pixel experience and AOSP Yet.
Click to expand...
Click to collapse
Thanks for the reply, i try it, piexel experience needs gaaps?
about how long do I have to wait to see if everything is going well?
---------- Post added at 07:35 PM ---------- Previous post was at 06:57 PM ----------
Wipe Cache, dalvick, data, system
flash with TWRP "PixelExperience_ARM64-A-10.0-20191115-1115-BETA-UNOFFICIAL"
flash with TWRP "Quantum_Kernel-GSI_A7_v3"
reboot....stuck on boot animation..... Where am I doing wrong....
i wait about 20 min....
I try with AOSP and same problem..... :'(
PLS HELP :'(
---------- Post added at 09:16 PM ---------- Previous post was at 08:44 PM ----------
lrico155 said:
could you please tell what was the gsi ROM that you installed? yesterday I tried with pixel experience and evolution but it only remained in bootloop
Click to expand...
Click to collapse
I have some problem....you solving??
i try also Lineage os 17, havoc 3, AOSP, RRemix 7, all time also install Quantum kernel V3, and try with and without GSI Fix boot.......but not solved......
Masok77 said:
I try with AOSP and same problem..... :'(
PLS HELP :'(
---------- Post added at 09:16 PM ---------- Previous post was at 08:44 PM ----------
I have some problem....you solving??
i try also Lineage os 17, havoc 3, AOSP, RRemix 7, all time also install Quantum kernel V3, and try with and without GSI Fix boot.......but not solved......
Click to expand...
Click to collapse
Nope, maybe it's for the kernel
OK, i try GSI 9 and all work..... .probably problem on Quantum kernel for GSI 10 IHMO, do you find it? any suggestions?
That's what I did for getting Android 10 booted
1. Flash official ONE UI rom of android 9 ( you can go for a framework flash with ODIN or try quantum one UI rom and flash with TWRP)
2. Make A Full boot, and make sure it's booted fine
3. Go to official page of gsi roms at git hub and download any android 10 ROM with "a-only arm64" ver. ( i prefer pixel experience or aosp for yet , because I have only tried these )
PS. Don't forget to extract that ROM file to get a .img file
4. Download Quantum kernal for gsi from the " ROMS And Kernal" section of the device
6. Go to TWRP and wipe data ( Reset )
7. Flash the Quantum Kernal for gsi
8. Flash the System image of the rom that you downloaded
Then Reboot to TWRP again
9. Flash The modified Magisk provided in the download.
Credit goes to : phhusson ( i dont know rom will boot with lastest Magisk)
10. Reboot and it should boot into android 10
-You don't need any other zip file to flash
thanks!!! tonight I try, thank you very much
AmanDevil77 said:
That's what I did for getting Android 10 booted
1. Flash official ONE UI rom of android 9 ( you can go for a framework flash with ODIN or try quantum one UI rom and flash with TWRP)
2. Make A Full boot, and make sure it's booted fine
3. Go to official page of gsi roms at git hub and download any android 10 ROM with "a-only arm64" ver. ( i prefer pixel experience or aosp for yet , because I have only tried these )
PS. Don't forget to extract that ROM file to get a .img file
4. Download Quantum kernal for gsi from the " ROMS And Kernal" section of the device
6. Go to TWRP and wipe data ( Reset )
7. Flash the Quantum Kernal for gsi
8. Flash the System image of the rom that you downloaded
Then Reboot to TWRP again
9. Flash The modified Magisk provided in the download.
Credit goes to : phhusson ( i dont know rom will boot with lastest Magisk)
10. Reboot and it should boot into android 10
-You don't need any other zip file to flash
Click to expand...
Click to collapse
thank you very much, it works!
but unfortunately the camera doesn't
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.
I'm not responsible for any damage to your device of any sort.
By flashing this, you take responsibility of anything that happens.
Process at your own risk!
If you want to check - please make backup. Better to store all partitions.
What works
audio
bluetooth
brightness
call/LTE (mondrianlte)
camera
DRM
OTA
video
wifi
wifi display
What doesn't work
Back camera preview : wrong rotation on preview in default app Fixed build 20221204
SELinux Fixed build 20221130
Instructions:
0. Patched TWRP for FOTA : mondrianwifi / mondrianlte
1. Factory reset if coming from another ROM.
2. Install ROM
3. Install GApps (optionally) [Recommended BiTGApps ARM 13]
4. Install Magisk 25.2 (optionally)
Sources & Changes:
Device tree mondrianwifi
Device tree mondrianlte
Kernel tree
Vendor tree mondrianwifi
Vendor tree mondrianlte
TWRP tree mondrianwifi
TWRP tree mondrianlte
Download:
Downloads: mondrianwifi / mondrianlte
Note to users: I'm not responsible if you brick your tablet. See the disclaimer above.
Contributors
LineageOS team for source code.
@retiredtab for helping make mondrianwifi to work on Android12
@khalvat for its work on porting msm8974 to Android12 (https://github.com/LineageOS-UL)
@pocketrule, @bierma32, @Yxo 6o6uka for willing to test WIFI builds and leaving feedback
@bmwdroid for willing to test LTE builds and leaving feedback
ROM OS Version: 13.0
Version Information
Status: Nightlies
Created 2022-11-27
Last Updated 2023-01-05
THX @phoval for the New LOS 20 Version.
Installed this as update over the Version 20221010 without issue's.
FOTA update notification works .
New build: SeLinux is enforcing
Perfect !!!
Amazing !!
Thank you @phoval !!!
Hello, good job.
Thank you @phoval
Installed and runs smooth. Sound, video & wifi works. Excelled work.
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
cwokel said:
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
Click to expand...
Click to collapse
bierma32 said:
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
Click to expand...
Click to collapse
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
@chkdsk90
Charge your battery to 100% and try another clean install, format also system and data .
chkdsk90 said:
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
Click to expand...
Click to collapse
Provide logcat.
zram boot img was alpha kernel for test.
The changes are includes since 2nd december build.
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
chkdsk90 said:
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
Click to expand...
Click to collapse
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
pocketrule said:
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
Click to expand...
Click to collapse
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
chkdsk90 said:
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
Click to expand...
Click to collapse
It's patched for FOTA. A simple internet search reveals, that fota stands for "Firmware Over-the-Air" 😉️ I.e. you can download and update the rom directly from the rom itself. If you (always) download and flash the rom manually / separately, you don't need the patched rom.
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
If I get a app not responding message and I hit wait it will repeatedly pop up despite the app responding again (dirty flash). Otherwise first impressions of this rom are good.
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
cwokel said:
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
Click to expand...
Click to collapse
Just disable it in system > buttons. It's customization during first setup.
You can enable gesture navigation too.
jacomail95 said:
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
Click to expand...
Click to collapse
If someone can find me one to buy?
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.