Database Info

[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.

Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you
* could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
Thread Notes:
I cannot stress this enough--Please READ EVERY STEP FULLY to be sure of what you need to do.
Some steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first. While flashing via bootloader you should see it say "(bootloader) Image not signed or corrupt" - (and can show "bad key" or "N/A" while booting) this is normal expected behaviour as the image is no longer properly signed by motorola (I had to repack as our dtb's are compressed inside the boot image)
This thread is not about custom roms - You may be able to run them using the boot images provided, but this thread does NOT cover that
This guide assumes your are on COMPLETELY STOCK (FACTORY) FIRMWARE. If you have previously flashed *any* other firmware, system images, kernels, or anything else I cannot say for sure that this guide will work for you
This WILL affect your ability to get OTA's if/when they come. This thread does not cover getting back to stock. It's up to you to figure out how to get back to stock if you want the update. You're best bet to avoid issues (boot-loops, non-booting, failed updates, etc) is to go completely back to stock first!
Android GSI's - For the record, I have booted GSI's made (Aonly-32bit) however there are some issues I've noticed regarding sounds while using them. Again, this thread is NOT the place to discuss problems with this.
TWRP - We can now use official twrp! Please click this link to see details. I have edited the first post to reflect the current state of our twrp images. If you see an error or run across an issue please let me know and I"ll see about fixing it. I have linked an unofficial build I made in the official thread to fix some issues with the official build. When I get a chance to properly verify the new test-build (made by the twrp gerrit) I will see about having the official one updated.
PIE - These instructions were made using Oreo, not Pie. There are differences in the boot images at the very least (you may not need a modified boot image for Magisk). I have not flashed Pie yet to test things. If you want to test, please let me know how things work out for you.
Working Images:
The variant models below have been verified working using one of the firmware versions listed.
XT1925-2, XT1925-3, XT1925-4, XT1925-5, XT1925-6, XT1925-13
OPS27.82-19-4 (Build Date: Fri Mar 9 11:04:39 CST 2018)
OPS27.82-41 (Build Date: Sat Mar 24 01:37:45 CDT 2018)
OPS27.82-72 (Build Date: Sun May 27 02:13:41 CDT 2018)
OPS27.82-87 (Build Date: Mon Jul 16 14:54:23 CDT 2018).
OPSS27.82.87-3 (Build Date: September 2018 Security Update)
OPSS27.82-87-6 *Provided by @Jleeblanch
OPS27.104-15-10 (Build Date: Wed Mar 28 21:13:40 CDT 2018)
OPSS27.104-15-10-4 (Build Date: July 2018 Security Update) *Provided by @Jleeblanch
OPS27.104-92 (Build Date: September 2018 Security Update)
OPSS27.104-92-2 (Build Date: November 2018 Security Update) *Provided by @Jleeblanch
*
*Waiting for confirmation:
*OPS27.82-57
*
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio/releases/platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
At least some knowledge of how to use ADB and fastboot, this guide does not cover that.
Some knowledge of how TWRP/custom recoveries work.
Finally, the guide:
Step 1) Downloading TWRP and modified boot image
Download TWRP and a modified boot image that matches your factory firmware version to the ADB/Fastboot folder on your computer. The boot image downloads are based on the premise of the firmware you are running. If yours is not listed please back up (next step) and provide a link for me to edit.
Official TWRP Thread: please read the thread for more information regarding this build. The download link is in that thread.
Unofficial TWRP, this link is just like official but added a vendor image mount for testing vendor operations: [AFH] twrp-v3.2.3-ali.img
BOOT Image Links - [AFH] No-verity edited boot images link
Reboot to your bootloader. You can do this by turning on your device while holding the power and volume down buttons at the same time. Once the device reboots to the bootloader connect your phone to your computer.
Step 2) Backing up your stock boot and recovery images and fstab.qcom file--if you have these already you can safely skip to step 3.
Open a terminal/command prompt on your computer and type the following to boot into TWRP (If your filename is different, please replace the filename below with yours):
Code:
fastboot boot twrp-v3.2.3-ali.img
Once TWRP boots (it may take a bit to boot because it is trying to decrypt your userdata. It will fail as TWRP--at least for now--needs to be flashed to decrypt properly. Swipe to allow modifications if you want if asked), type the following in your computer's terminal/command prompt to back up your boot and recovery images:
Code:
adb pull /dev/block/bootdevice/by-name/boot stockboot.img
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
If you intend to remove encryption you'll want a backup of your fstab.qcom file:
To back up your fstab.qcom file (modified in a later step) we need to mount Vendor in TWRP first if it's not already mounted. From TWRP's main menu press 'Mount'. You can see if the vendor partition is mounted (check mark next to the word 'Vendor') . If it isn't mounted just press 'Vendor' and it should mount. Next type the following:
Code:
adb pull /vendor/etc/fstab.qcom factory-fstab.qcom
Reboot to the bootloader.
Step 3) Installing TWRP and modified boot images
Run the following command from your computer's terminal/command prompt to install the TWRP image to your device (If your filename is different, please replace the filename below with yours).
Code:
fastboot flash recovery twrp-v3.2.3-ali.img
Run the following command from your computer's terminal/command prompt to install the boot image to your device.
usage:
Code:
fastboot flash boot <insert-boot-image-name-here>.img
example:
Code:
fastboot flash boot OPS27.104-92_no-verity_boot.img
Step 4) Wiping your data on your phone to remove the current encryption. Ensure you have a backup beforehand if you want it.
This step is only needed if you intend to remove your current encryption, if you don't want to do this please skip to the next step
Boot into TWRP by using the volume keys on your phone to select "recovery mode" and then press the power button and TWRP will boot up (it may take a bit to boot because it is trying to decrypt your userdata or if you have a screen lock it may ask for it--enter it and proceed. Please read the thread linked above for help if you enter it incorrectly.)
Swipe to allow system partition modifications if you want and are asked. If you wish to backup your data and restore it after formatting then do so now. Next click the "Wipe" button in TWRP and then "Swipe to Factory Reset". This step should have formatted data as it was encrypted (removing internal storage ) however if it didn't and data is still not mountable in TWRP you can use the "Format Data" button above "Swipe to Factory Reset", this will format data and remove EVERYTHING from the internal storage as well. You may need to format data again and reboot into TWRP. DON'T REBOOT TO SYSTEM YET.
Step 5) Removing forced-encryption upon first boot (you may still choose to encrypt after booting--Moto's firmware defaults to saying it's encrypted, at least on mine, in the security tab of settings but it's not and the option to encrypt still exists within that menu)
This step is only needed if you intend to remove forced encryption, if you don't want to do this please skip to the next step
**THIS STEP DOES NOT REMOVE CURRENT ENCRYPTION--IT ONLY REMOVES FORCED ENCRYPTION DURING THE FIRST BOOT: YOU MUST HAVE COMPLETED STEP 4 ABOVE TO REMOVE CURRENTLY ENCRYPTED DATA**
This file has been verified working on Oreo and may not function correctly on Pie, please be aware of this: see HueyT's Post.
Download the force-encryption disabler zip to your ADB/Fastboot folder: [AFH] Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Now push that zip file to your phone. The example uses the /tmp directory. From your computer's terminal/command prompt type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb push Force_Encryption_Disabler_For_ALI_Oreo_v2.zip /tmp
Flash the zip you just pushed by pressing the Install button in the TWRP main menu, select the folder where you pushed the zip to and install it. We can verify it flashed by mounting vendor manually if it's not mounted and using the following command from your computer's terminal/command prompt and checking the line that mounts /data says "encryptable" instead of "forceencrypted":
Code:
adb shell "cat /vendor/etc/fstab.qcom"
The result should include this line:
/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,encryptable=/dev/block/bootdevice/by-name/metadata
Click to expand...
Click to collapse
Note where it says "encryptable". That means we now have the choice to do so vs. being forced to. If for whatever reason it still says "forceencrypted" mount vendor manually and try again.
Step 6) Rooting via Magisk
This step is only needed if you intend to have root access, if you don't want to do this or wish to do this later please skip to the next step
To be safe, you may need to reboot back into TWRP to make sure it sees the data partition mounted correctly and again swipe to allow system partition modifications if you want. (I've seen Magisk say forced-encryption was still detected even though it actually wasn't if I didn't reboot)
Download Magisk from the linked thread to your ADB/Fastboot folder: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Run the following command to push the Magisk zip to your device (v17.3 (beta) is current as of the last edit of this post, if it changes please put your version number instead).
The example uses the /tmp folder:
Code:
adb push Magisk-v17.3.zip /tmp
Flash the Magisk zip from TWRP by pressing the Install button in the main menu and navigate to the /tmp (or wherever you pushed it) folder to select and install it. Magisk should show success without any mention of verity or encryption. If it does, something hasn't gone right and you may need to start again.
Step 7) Almost finished!
Reboot your device. If you installed Magisk it will say "N/A" in the top corner of your device for a few seconds (otherwise it should say "bad key"). This is normal. It may look like it bootloops that screen, just let it go and and it should boot the Motorola boot screen and you can setup your device as a new phone.
Once booted, if you installed Magisk, verify Magisk Manager is installed and the root functionality works.
Step 8) ???
Step 9) Profit
Credits:
@kwiksi1ver - getting things going for us, work with twrp and verity and allowing me to use his thread as base for this guide.
@CodyF86 and his Moto E5 thread for clues as to what it would take to turn off DM-Verity (per kwik)
@Dadud - testing and constantly nuking said device
@AngryManMLS - testing and communications
@Vache - Provided us the fix for sdcards in TWRP.
@Xennet's thread regarding verity and encryption and the disabler zip and everyone there: Disable [DM-Verity]/[Force Encryption] [OnePlus 3T/3] for [Oreo] Oxygen OS
@likemiketoo - Having had TWRP built for us for testing purposes
@Jleeblanch - Helping provide various no-verity images and other help/advice like....everywhere
Everyone else who I am forgetting because let's be honest, I'm sure I have. If you feel like mention is owed please let me know and I'll be happy to add.

Extras:
THE BOOT IMAGE LINKS IN THIS POST HAVE BEEN REMOVED TO AVOID CONFUSION: THEY WERE OLD DOWNLOADS WITH IMPROPERLY LABELED NAMES.
The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.
XT1925-6 (OPS27.104-15-10) Factory pulled files
These files will get you back to stock as far as this guide is concerned. Remember though, 'bad key' will be displayed as they were pulled from a device instead of being provided by Motorola
Factory boot image - *link removed*
Factory recovery image - *link removed*
Factory fstab.qcom file - factory-fstab.qcom - You can push this file to /vendor/etc/ to go back to stock vendor parition if you need. You'll need to rename it to 'fstab.qcom' to make it work right. Factory boot images will probably have an issue booting without vendor being completely stock.
The following images have been provided by other XDA members:
XT1925-2
Factory boot image - *link removed*
XT1925-4
Factory boot image - *link removed*
XT1925-5
Factory boot image - *link removed*

Notes regarding editing the boot images
First off, this is not going to be a "guide" like the first post. Different devices may have different needs, and at this time I am not changing this thread to answer questions about the editing process. Maybe that'll change in the future.
It took me a minute to realize that the G6 (ALI) dtb's are compressed and this is why directly hex editing the boot images (like the G6 Play (jeter)) initially resulted in non-booting. I'd think anyone could decompress the lz4 archive and edit the necessary info, recompress (I used max compression) and then repack the boot image and it should boot. Before that realization I had at one time built the kernel from source code (OPS27-104.15.10) with verity support disabled there so I could get around verity.
Story time!
I'll keep it shorter than it really was so be happy!
So the last time I was into building roms and such was several years ago. If the dtb's existed then, I didn't remember them I started off with some of the various "kitchens" unpacking the boot image I pulled and was getting no where. Even simply unpacking and repacking seemed like it was causing issues. I saw the results kwiksi1ver was having with the G6 Play and asked for advice: Hex edits, don't unpack..
Not sure where to go from there I searched around for posts regarding verity and at some point came across Xennet's thread: Disable [DM-Verity]/[Force Encryption] [OnePlus 3T/3] for [Oreo] Oxygen OS. Within that thread there was a link for another post in that thread that spoke a more in detail about what needed to change (post #3). Please read up on that if you want to know more.
Details:
Basically, if we're not rebuilding from source, etc etc, then we need to hex edit the dtb file (ours is actually I believe 6 dtb files combined into one, other devices can vary). On some devices these files are not-compressed and we can just edit them and go. For ours, I found the need to unpack them with a kitchen (AIK). Once there, I decompress the dtb archive (it's in 'lz4' format, max compression) and make the edits. The lines we are looking for contain "wait,verify". Under normal circumstances these will mount the system and vendor partitions with verity enabled (verify) to be sure they aren't modified. We need to REPLACE the ",verify" portion of the "wait,verify" with zeros. We can't just delete them, replace with zeros so we don't change the overall file size. We have to make sure we get all references to ",verify" replaced. It'll just say "wait" now. After I've edited the dtb file I recompress in 'lz4' format with max compression and then repack the boot image. After that, we should be good to go!
Please reference Xennet's thread if you want more details of how the lines actually look in code, just be aware ours may not be 100% the same. I may add or change stuff here later.

Great guide!

thanks, can't try it yet but i will soon.

Excellent work broski, sweet guide. Really looking forward to testing some stuff out, I'm off for the next two days... so gotta get to a computer [I know pathetic, I don't have one] ... Jeez you couldn't make a one click solution for all this? ?
For real though, super big thanks to all of you for
enduring the grueling task of cracking this bad boy
How bout some donate links? ... and @kwiksi1ver, I'm not sure if you're into developing ROMs or Kernels, but I say more is always better, so there's still good cause for you to get a G6.

dejello said:
Extras:
The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.
Moto G6 (Ali - OPS27.104-15-10) Factory pulled files
Factory boot image - MotoG6-ali-factory-boot.img
Factory recovery image - MotoG6-ali-factory-recovery.img
Factory fstab.qcom file - factory-fstab.qcom
Click to expand...
Click to collapse
it serves for XTI 1925-4?
OPS 27.82-72
Enviado desde mi moto g(6) mediante Tapatalk

dejello said:
Extras:
The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.
Moto G6 (Ali - OPS27.104-15-10) Factory pulled files
Factory boot image - MotoG6-ali-factory-boot.img
Factory recovery image - MotoG6-ali-factory-recovery.img
Factory fstab.qcom file - factory-fstab.qcom
Click to expand...
Click to collapse
First off thank you for the work, this is incredible and I would love to donate.
And second, I am running the RetBr firmware as I softbricked my retus version, do you know how or where I could get the us firmware?
stifmaster81 said:
it serves for XTI 1925-4?
OPS 27.82-72
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
This is for the US version xt1925-6, but seems that it may work for you depending on the files

bird412 said:
First off thank you for the work, this is incredible and I would love to donate.
And second, I am running the RetBr firmware as I softbricked my retus version, do you know how or where I could get the us firmware?
This is for the US version xt1925-6, but seems that it may work for you depending on the files
Click to expand...
Click to collapse
I just want to install magic, I do not want to decrypt it at the moment, what I'm scared if it's boot.img will be useful for me, anyway if it goes wrong, installing the factory image
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------
anyway if something goes wrong, installing the factory image by adb is solved everything not?
Enviado desde mi moto g(6) mediante Tapatalk

stifmaster81 said:
I just want to install magic, I do not want to decrypt it at the moment, what I'm scared if it's boot.img will be useful for me, anyway if it goes wrong, installing the factory image
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 04:37 PM ---------- Previous post was at 04:35 PM ----------
anyway if something goes wrong, installing the factory image by adb is solved everything not?
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
I believe you are correct, that if you fastboot the original boot img it should fix any issues. Of course you should back up your data in the case that you need to completely reflash

someone could do this same but for the version OPS27.82-72 XTI 1925-4 ??
This did not work for me, I had to reinstall everything again, I would be very grateful

Same here
It didnt work for XT1925-2
Thanks anyway
But could anyone help us to do the same with the other varients pls :b as it seems it depends on it (and the boot img) (i had ALI_OPS27.82-72_cid50 in mine)
Btw thanks you again, all of you did a great job giving us a working TWRP, Root and magisk
(Just we need make it work for everyone )

Josio67 said:
Same here
It didnt work for XT1925-2
Thanks anyway
But could anyone help us to do the same with the other varients pls :b as it seems it depends on it (and the boot img) (i had ALI_OPS27.82-72_cid50 in mine)
Btw thanks you again, all of you did a great job giving us a working TWRP, Root and magisk
(Just we need make it work for everyone [emoji14] )
Click to expand...
Click to collapse
+1
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------
stifmaster81 said:
someone could do this same but for the version OPS27.82-72 XTI 1925-4 ??
This did not work for me, I had to reinstall everything again, I would be very grateful
Click to expand...
Click to collapse
Help us please
Enviado desde mi moto g(6) mediante Tapatalk

bird412 said:
First off thank you for the work, this is incredible and I would love to donate.
And second, I am running the RetBr firmware as I softbricked my retus version, do you know how or where I could get the us firmware?
Click to expand...
Click to collapse
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience Can you let me know what all files you flashed?
For everyone else on different variants
Looks like we're going to have to do what @kwiksi1ver has done on G6 Play boot images, just slightly different. It will take a tiny bit more time per device.... Plus I'm about to go out for a bit so yeah, it'll still be a minute.
Firstly, does the TWRP image boot for you?
Secondly, if TWRP boots for you, I'd like for you to get me a couple of things:
A) I need you to pull the boot image following the steps in the first post and post a link here (along with your model number ie XT1925-#). I will see what I can do and try to find what's actually different so maybe we can avoid having to do this in the future.
B) If someone could pull the config.gz from the phone while booted in TWRP and post the model number you're using (XT1925-#) that may help.
Code:
adb pull /proc/config.gz

dejello said:
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience [emoji14] Can you let me know what all files you flashed?
For everyone else on different variants
Looks like we're going to have to do what @kwiksi1ver has done on G6 Play boot images, just slightly different. It will take a tiny bit more time per device.... Plus I'm about to go out for a bit so yeah, it'll still be a minute.
Firstly, does the TWRP image boot for you?
Secondly, if TWRP boots for you, I'd like for you to get me a couple of things:
A) I need you to pull the boot image following the steps in the first post and post a link here (along with your model number ie XT1925-#). I will see what I can do and try to find what's actually different so maybe we can avoid having to do this in the future.
B) If someone could pull the config.gz from the phone while booted in TWRP and post the model number you're using (XT1925-#) that may help.
Code:
adb pull /proc/config.gz
Click to expand...
Click to collapse
If you tell me the steps that I have to do I will try to take mine out of my variant XTI 1925-4
Enviado desde mi moto g(6) mediante Tapatalk
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
stifmaster81 said:
If you tell me the steps that I have to do I will try to take mine out of my variant XTI 1925-4
Enviado desde mi moto g(6) mediante Tapatalk
Click to expand...
Click to collapse
Tell me the steps to remove from the phone the configuration you are asking me please
Enviado desde mi moto g(6) mediante Tapatalk

dejello said:
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience Can you let me know what all files you flashed?
For everyone else on different variants
Looks like we're going to have to do what @kwiksi1ver has done on G6 Play boot images, just slightly different. It will take a tiny bit more time per device.... Plus I'm about to go out for a bit so yeah, it'll still be a minute.
Firstly, does the TWRP image boot for you?
Secondly, if TWRP boots for you, I'd like for you to get me a couple of things:
A) I need you to pull the boot image following the steps in the first post and post a link here (along with your model number ie XT1925-#). I will see what I can do and try to find what's actually different so maybe we can avoid having to do this in the future.
B) If someone could pull the config.gz from the phone while booted in TWRP and post the model number you're using (XT1925-#) that may help.
Code:
adb pull /proc/config.gz
Click to expand...
Click to collapse
thank You for your help, I am gonna try to find out what @kwiksi1ver did to modify the boot.img.
But in every case here are the files for XT1925-5

dejello said:
@bird412 I do not currently. I have yet to see them posted anywhere. @Dadud had a similar (same?) issue and is now on a different bootloader as a result. If you give us a bit we can see about getting links for what you need (minus the bootloader) to see if we can get you mostly back to stock. I will not post pulled bootloader files at this time as I have zero clue if it could brick your device *permenantly* and I just don't want that on my conscience Can you let me know what all files you flashed?
Click to expand...
Click to collapse
I downloaded the firmware from this and flashed it using the code provided in the op. Later in the thread someone uploaded some files from their RetUS phone but I could not get past their encryption passwords

nightmw said:
thank You for your help, I am gonna try to find out what @kwiksi1ver did to modify the boot.img.
But in every case here are the files for XT1925-5
Click to expand...
Click to collapse
Can you help me make mine? What steps do I have to do, thanks
Enviado desde mi moto g(6) mediante Tapatalk

nightmw said:
thank You for your help, I am gonna try to find out what @kwiksi1ver did to modify the boot.img.
But in every case here are the files for XT1925-5
Click to expand...
Click to collapse
Thanks for doing this...Stifmaster hold on buddy, it's going to be okay, breath.

adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
what to put who ... by-name / boot adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
what to put who . ... by-name/boot para el motog6 ali xti 1925-4

Tutorial flashing GSI image for Oukitel K9

Hi,
So long i've dont active my account on XDA Developers because my studies. Finally i've found to update Oukitel K9 by using Treble Img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video Review : https://youtu.be/EMbBpCc0R-Y

Please make sure you have download Generic GSI from Google and already unlocked bootloader.
Here the link ( Download Generic GSI )
Choose ARM64+GMS / ARM64, if you want to flash android Q treble rom, just download Android Q only.
Let's start it.
1. Flash to stock firmware using MTK Tools
2. Extract vbmeta.img from Generic GSI.
3. Connect to usb to device (enter fastboot mode) hold volume up and power button, choose fastboot mode.
4. Type this and make sure using generic vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Next erase file system
Code:
fastboot erase system
6. a) Flash file system
Code:
fastboot flash system ######.img
# = your file system name
or
6. b) Using TWRP > Flash> Click image> find img to flash> Select system>then swipe to flash
7.
Code:
fastboot -w
8.
Code:
fastboot reboot
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Test
Working GSI:
system-quack-arm64-ab-gapps.img.xz
Evolution X , Lineage 17.1 - All Working
Havoc 3.3 - RIL bugs, no simcard detect
All GSI Rom list you can find here : Phhusson GSI

Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again

TiTiB said:
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
Click to expand...
Click to collapse
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks

Levered said:
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Click to expand...
Click to collapse
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.

TiTiB said:
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
Click to expand...
Click to collapse
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.

Levered said:
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Click to expand...
Click to collapse
nvm, you are obviously not going to share useful information
1) build# you were able to root
2) what you mean by 'MTK Tools'
3) and other important stuff

Additional information I have discovered
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.

Thanks
hello, my name is bausette i'm italian, i'm sorry for my bad English i hope you cand understand me. First of all
thanks for your work, that's amazing my Oukitel k9 has new life :fingers-crossed::victory:, that's amazing Everything work better, than Stock Rom.
Can i Ask you some question please? i had Flash Vmeda generic files, Open Gapp, Orange State fix message, Lineage Rom project Treble, TWRP recovery, but i think i forgot something, because after install Magisk it say that the device is not Rooted, please can you tell my step by step Guide to Root the phone? thanks so much

Levered said:
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Click to expand...
Click to collapse
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie

lschafroth2 said:
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
Click to expand...
Click to collapse
You can try A partition images.

Levered said:
You can try A partition images.
Click to expand...
Click to collapse
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie

lschafroth2 said:
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
Click to expand...
Click to collapse
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254

Levered said:
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Click to expand...
Click to collapse
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
nation888888 said:
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Click to expand...
Click to collapse
How do you verify you are A/B? Mine says A only on 4 different treble apps. Is there a way to verify for sure? I have a Oukitel K9.
Lannie

lschafroth2 said:
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
Click to expand...
Click to collapse
You can try it first both partition. If not boot, try another partition. :fingers-crossed:

Everything seems to work except hotspot
The no verity, Lineage rom a/b, vbmeta, resizing system partition size, installing stock gapps all works making this one of the nicest roms I have worked with. The only issue I find so far I cannot get the mobile Hotspot to stay on. Mobile Hotspot works in safe mode. I did a fresh install and does the same. Modded buildprop, no results. Installed module tether enabler, no results.
Mobile Hotspot switches off right away. Any ideas?
---------- Post added at 06:01 AM ---------- Previous post was at 05:57 AM ----------
It is this one a/b I have not seen any other variants. Both Global and Chinese have same partition setup. Yes I have tried a only and doesn't boot.

How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.

lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
If recovering to stock is easy, I guess I can dive in and try the A/B image and see if it works.
Lannie

use the lineage ab... it is ab. Make sure to do the no verity first with vbmeta line. Then flash lineage ab the file is not clear it states b. I tried them all see my post for direct download.

Same result
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
I have same firmware, K9 OUKITEL_K9_V21_20190524, and same results for Treble check (see screenshots for info).
Also, device not recognized using fastboot.
Code:
adb devices
OUKITELK90007961
Code:
adb reboot bootloader
success; 'FASTBOOT mode. . .' on phone
Code:
fastboot devices
blank line
From what I understand, this is because our devices' bootloaders are locked; and there is nothing we can do to change that, period. So, no flashing anything but stock. I hope I'm wrong, and someone more knowledgeable corrects me, but I'm pretty sure this is correct.
For now I'm just stuck, and using temporary root as mentioned in previous post.

[stock Rom] Blu G-90 G0310WW

Blu G90 device shipped from factory with Android 10
as with other devices from blu they do not have a public download of there roms. So here is the stock rom pulled from the device with SP-Flash tool.
Both the shipped rom build fingerprint
Code:
ro.bootimage.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020/1585383273:user/release-keys
And the ota update from June fingerprint
Code:
ro.system.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020/1592848714:user/release-keys
are in android file host flash-able with spflash tool, if needed.
I know the first thing to have before modifying android is the method to recover from bad edits. So here they are.
Other works will be stored in this same folder.
https://www.androidfilehost.com/?w=files&flid=315927
First stock rom is Dumped to github, If you need or want specific files, without needing to download whole rom.
https://github.com/mrmazakblu/blu_g0310ww_dump
Stock kernel source:
https://github.com/mrmazakblu/Blu_G90_G0310WW_stock_kernal
Device INFO
*******Above links are pulled firmware. Below is an official firmware file, w/ verified images.********
https://www.mediafire.com/folder/ocmvgrcd73bqy/G90
**
.

Bootloader unlock is same as past devices.
1. enable develper options
2. enable OEM unlock , from inside developer options
3. Reboot to bootloader (adb reboot bootloader, or button combo)
4. fastboot flashing unlock
5. Select confirm on device
6. fastboot reboot (causes factory reset)

Flashing GSI
few more steps than Pie devices, but not too complicated.
You will need recent fastboot tools as tested these steps were done with V30.0.4
https://developer.android.com/studio/releases/platform-tools
Verified boot is enabled on device. The verity key is stored into 3 section.
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
All found in stock rom. Shared in first post.
1. Unlock bootloader. (see last post)
2. Reboot to bootloader to disable verity
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
3. Reboot from bootloader to fastboot(new interface for android 10)
Code:
fastboot reboot fastboot
4. flash sysem from "fastbootd"
Code:
fastboot flash system **gsi-system.img**
Use 64 bit AB GSI
5. Wipe data so the new system will work
Code:
fastboot -w

ROOT::
Not yet confirmed yet. Magisk patched_boot has not provided root as of yet.
Currently looking into pre-rooting the system.img, but not success yet.

TWRP;;
https://forum.xda-developers.com/android/development/twrp-twrp-3-4-0-0-blu-g90-g0310ww-t4163497
.

I have been able to edit the stock /system and flash it back to phone.
--I have added adaway host file
--Removed the SIMO app
-- Removed the IGNITE adware app (dti.blu)
--Removed The Verizon Remote SIM lock app
--Removed Blu-Privacy app
--Removed Opera browser app
--Deodexed Rom (rom would not boot past splash screen without this)
Uploaded edited sysem.img to device folder listed in OP.
Flash with same instructions as How to flash GSI
--Attempting to add SU binary makes rom fail to boot. So still no stock rooted.
Maybe soon.
/

Blu released kernel source today. 8-27. The tar.hz is dated April, eh, whatever.
I added the source files to the wip twrp tree, it compiles without error. (Not my normal experience , on first time out with Blu kernel).
But as mentioned before, the twrp will not pack the image correctly. Because of the need for new dtb commands that twrp 9.0 build environment does not accept.
And when building in the twrp 10.0-wip tree, the results have not booted for me yet. (I'm on build attempt 12, or so)
I'm rambling, sorry.
When I repack the twrp using the built kernel, twrp has only blank screen, and adb is active. So kernel is slightly off.
Build did not output separate dtb or dtbo.

Well I confirmed it, the screen on this phone is not the one the kernel is building for.
I compared the defconfig from source, the one that matches the name in build prop, to the one I pulled from /proc. And they are different, and the kernel errors out during build when using right defconfig. So, waiting again for Blu to provide the files.

There does not appear to be any interest in this phone, other than my own.
Well maybe it will catch on
It's been advertised on many mm ore locations than the average BLU phone.
Amazon
Ebay
Walmart
Newegg
Best buy
B&H photo
Time will tell.

mrmazak said:
Well I confirmed it, the screen on this phone is not the one the kernel is building for.
I compared the defconfig from source, the one that matches the name in build prop, to the one I pulled from /proc. And they are different, and the kernel errors out during build when using right defconfig. So, waiting again for Blu to provide the files.
Click to expand...
Click to collapse
Any luck with Blu providing the correct kernel files?

Ivisibl3 said:
Any luck with Blu providing the correct kernel files?
Click to expand...
Click to collapse
Not yet. They acknowledged my email, but as yet have not updated there posted source.

Root is half way achieved.
Factory rom was found. It included a boot-debug.img
When this image is used in boot partition, adb root is allowed.
It is only limited root. Example: blockdev command , used to allow remount / to rw, is not permitted. Bit is start.
Factory flashtool rom shared on Blu developers mediafire page.
Will add link to debug-boot.img soon
added to device folder listed in OP
google information on debug-boot.img
https://source.android.com/compatibility/vts/vts-on-gsi

if you have the stock boot.img, and magisk manager, why cant you patch the boot.img and then disable dm-verity by flashing vbmeta.img/vbmeta_system.img/vbmeta_vendor.img and then flash the boot.img via sp flash tool to give you root access?

aryanhington said:
if you have the stock boot.img, and magisk manager, why cant you patch the boot.img and then disable dm-verity by flashing vbmeta.img/vbmeta_system.img/vbmeta_vendor.img and then flash the boot.img via sp flash tool to give you root access?
Click to expand...
Click to collapse
because magisk init is not starting on a patched image. have no sign on magisk in the any of the logs.
the issue is posted on magisk github issue tracker. no solution as of yet.

mrmazak said:
because magisk init is not starting on a patched image. have no sign on magisk in the any of the logs.
the issue is posted on magisk github issue tracker. no solution as of yet.
Click to expand...
Click to collapse
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?

aryanhington said:
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
Click to expand...
Click to collapse
different brand, so built differant. just like ther are redmi (xiamoi) devices with mtk, but fastboot unlock doe not work, it needs redmi app to unlock. and flash tool not work on all devices with MTK, like amazon fire device , they have mtk and do not work with fastboot unlock, or spflash.

mrmazak said:
I have been able to edit the stock /system and flash it back to phone.
--I have added adaway host file
--Removed the SIMO app
-- Removed the IGNITE adware app (dti.blu)
--Removed The Verizon Remote SIM lock app
--Removed Blu-Privacy app
--Removed Opera browser app
--Deodexed Rom (rom would not boot past splash screen without this)
Uploaded edited sysem.img to device folder listed in OP.
Flash with same instructions as How to flash GSI
--Attempting to add SU binary makes rom fail to boot. So still no stock rooted.
Maybe soon.
/
Click to expand...
Click to collapse
which steps did you take to modify the stock /system?

aryanhington said:
which steps did you take to modify the stock /system?
Click to expand...
Click to collapse
used superr script to unpack stock super.img and continued to extract system.img
manually went through the extracted system/system/app folder and deleated the aps I did not want (adware// bloate)
used the rom tools option / deodex
then repacked the system.img

aryanhington said:
why this that occurring, because for umidigi devices on android 10 work fine https://community.umidigi.com/forum.php?mod=viewthread&tid=19114 and they also use a mediatek chipset?
Click to expand...
Click to collapse
This is not entirely true.
Many Umidigi phones have been upgraded from 9 to 10. So the partitions would be very similar and considerably easy to root.
But for new phones coming with 10 the story changes. Read the last pages of your link's article. In addition, I know why and effect on Umidigi Power 3 still has limitations on root.
So this BLU G90 is not very different and depends on a lot of experimentation and tests. I believe that the OP is doing a great job mainly taking everything to github and trying to compile the kernel and firmware.

DragonPitbull said:
This is not entirely true.
Many Umidigi phones have been upgraded from 9 to 10. So the partitions would be very similar and considerably easy to root.
But for new phones coming with 10 the story changes. Read the last pages of your link's article. In addition, I know why and effect on Umidigi Power 3 still has limitations on root.
So this BLU G90 is not very different and depends on a lot of experimentation and tests. I believe that the OP is doing a great job mainly taking everything to github and trying to compile the kernel and firmware.
Click to expand...
Click to collapse
can you elaborate what you mean by this?

[LG Velvet 4G | LMG910EMW] A noobs guide for installing Magisk (rooting), SafetyNet, Gcam buffer fix and fingerprint fix

Disclaimer: None of this is my work! I only used guides from other people and decided to create single a step-by-step guide for the LG Velvet (4G version). I tried crediting all people at the end of the post.
I am not responsible if you brick your device - use this guide at your own risk and know what you are doing.
After unlocking, your fingerprint reader will no longer work, this can be fixed and the instructions can be found below.
All these tools are commandline tools (cmd) - you should know how to use them.
You should also be familiar with "adb" and "fastboot".
This is not a guide for noobs, only a guide made by a noob.
Unless mentioned otherwise, all these steps are to be done on your computer.
I used Windows 10, it should work on other platforms just fine with a few modifications.
Bootloader Unlock
(European Version - I have no idea about the possibilities of unlocking provider-locked phones or other regions!!!)
Create an account and follow the instructions here:
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The steps are explained quite well, therefore I will not write them down here unless people actually have problems with the steps.
(Preparation on the phone: Enable developer options, allow USB debugging and allow OEM Unlock.)
As always, unlocking the bootloader will WIPE your phone.
Installing Magisk / Systemless root
(After you successfully unlocked the bootloader, remember to re-enable developer options on the phone and allow USB Debugging)
Download the latest firmware here.
Use the IMEI search if you don't know which one you need!
Using this page, you will eventually receive a link ending in .kdz.
I don't recommend using the Download tool provided by lg-roms, but instead this script:
https://forum.xda-developers.com/t/...nd-lgup_ui-fixer.3916444/page-2#post-84148225
Paste the .kdz URL in the tool and wait for the Download to complete.
Next, you will need a copy of kdztools. Download a copy of this repository.
Important: Do not download from "Releases" - they are outdated! Instead, download a copy of the current master branch!
To be able to use this tool, you need to have python3 installed.
I will not further describe this step as there are enough tutorials out there and it is usually self explanatory.
You will have to install the module "zstandard" for the script to work:
pip3 install zstandard
Click to expand...
Click to collapse
Use KDZ Tools together with the downloaded firmware.
First, exctrat the KDZ file:
python unkdz.py -f G910EMW10i_00_0520.kdz -x
Click to expand...
Click to collapse
You should now have a large .dz file in the subfolder "kdzextracted". We can use this file to extract the boot image:
python undz.py -f c:G91010i_00_user-signed-ARB0_COM1_EU_OP_0520.dz -s 41
Click to expand...
Click to collapse
After this step, you should have a file "boot_a.image" in the subfolder "dzextracted".
(If you received a different file, use "python undz.py -f c:G91010i_00_user-signed-ARB0_COM1_EU_OP_0520.dz --list" and search for the partition named boot, edit the number "41" in the previous command accordingly)
Rename the boot_a.image to "boot.img" and copy it to your phone.
Download and install the latest Magisk release on your LG device.
In Magisk, select Install and patch the boot.img file.
After patching, copy the patched Magisk image back to your computer, rename it for easier use.
Using adb/fastboot on your pc:
adb reboot bootloader
fastboot flash boot_a magisk.img
fastboot flash boot_b magisk.img
Click to expand...
Click to collapse
Finally
fastboot reboot
Click to expand...
Click to collapse
Wait for the phone to boot and check Magisk installation status.
Congratulations!
Disable automatic firmware updates on your phone if you want to avoid having to re-install a patched Magisk image after every update!
Passing SafetyNet (Google Pay and more)
(You might not need all steps - after every step, you can check SafetyNet status via Magisk and if it is still broken, continue with the next step.)
Reboot after every step!
In the Magisk App, open Settings (top right) and enable the option "MagiskHide"
Download Universal safetynet fix and manually add as a module in the Magisk app
Download Magisk Hide Props Conf (manual DL not needed, can be found as a module directly in the app)
Unless there was an update to SafetyNet, you should now be able to set up and use SafetyNet services like Google Pay
Fixing your fingerprint reader
After the bootloader unlock, you will no longer be able to register fingerprints. This can be fixed using the following steps:
Launch the hidden service menu by dialing #*462633*#910# (might require an inserted SIM card)
SVC Menu -> Handprint -> HandID Logging "ON"
Go to the start of the menu and then navigate to "Device Test" -> SAAT -> Manual Test -> Optical FingerPrint Test
Press SEVERAL times firmly on the green button until it says FAILED, confirm and exit the menu
Go to settings and set up your fingerprints!
AFAIK, you can now disable "HandID Logging" again
Gcam Buffer Fix (Viewfinder Lag)
Using Gcam on the LG Velvet 4G, you will notice that most of the ports will not work properly.
Only a few versions based on Gcam 6.x with the option "buffer fix" will somewhat work, but not very well.
If you have Magisk installed, you can install the Buffer Fix that was originally designed for the LG V40 (Use the one for Android 10). Just flash the ZIP as a Magisk module.
Some Gcams will crash but MGC builds by BSG appear to work well!
(I don't know how this buffer fix works so I don't know if it is healthy to flash a module that was designed for a different phone but I tried several bufferfixes for different phones and this one appears to work flawless.)
Credits:
The very good rooting guide for the LG Velvet 5G by MikGX - THANK YOU
https://forum.xda-developers.com/t/root-lg-velvet-lm-g900em.4171117/
KDZ Download Tool by CXZa
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
SafetyNet Fix by kdrag0n
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
MagiskHide Props Conf by Didgeridoohan
[MODULE] [DEPRECATED] MagiskHide Props Config - SafetyNet, prop edits, and more - v6.1.2
MagiskHide Props Config v6.1.2 Note: This project is dead, and has been for some time. I have not been involved in the Android modding scene for some time and I no longer have the energy to take it up again. If anyone feels like taking over...
forum.xda-developers.com
Buffer fix for LG V40 by Wyroczen.
[GCAM] Buffer fix by Wyroczen
[GCAM] Buffer fix by Wyroczen Hey, I've made buffer fix for LG V40 in a form of TWRP flashable zip and second option with file for replacement: It will fix lagging viewfinder in GCAM both nightsight and normal mode. Instructions: Boot into TWRP...
forum.xda-developers.com
Fingerprint fix instructions provided by raj_ch2002 for the LG G8X
Steps to get the Fingerprint working with unlocked bootloader and Root
Make sure you have backed up your 20e stock abl. You will need to download the Android 9 kdz "G850EMW10c_00_1126.kdz" link to Android 9 kdz: https://drive.google.com/drive/folders/1nVbxo_sLKXQ_qN030ZZCThd8peER0pRM?usp=sharing If you are already...
forum.xda-developers.com
(Linked by foggydew88 here) - thanks!
paolotheking for providing the LG Velvet 5g service menu code, which is similar to this model
LG Velvet Hidden Menu code
Enjoy: #*462633*#900# Works with G900EM
forum.xda-developers.com
Finally, thanks to the devs of Magisk, kdztools and lg-roms

Reserved

thx!

can you provide boot img for G910EMW10i?

GerRudi said:
Bootloader Unlock
(European Version - I have no idea about the possibilities of unlocking provider-locked phones or other regions!!!)
Create an account and follow the instructions here:
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
Click to expand...
Click to collapse
Hi. I wonder how it is possible to unlock the bootloader using this page since the LG Velvet 4G (LM-G910EMW) doesn't seem to be at the supported devices list. How did you got it?

Is there a way someone can help to unlock Korea version of velvet?

Can someone from 20a backup me system and vendor partitions ? Not the ones from kdz, i need as they are in the phone with partition backup app that requires root either with qfil? i can give instructions just dm me on telegram @EmanuelCN0 . I specifically need from EMW model.

Got the German Version of the phone (DEA) ... Everytime i want to use undz.py it says Error: extraneous data found IN version. Also unkdz.py says something but extracts the .dz. Any idea what i could do ?

Hello. I've succesfully rooted my European Velvet LTE/4G variant.
Most of the kdz extractors are a total disaster and won't work with recent KDZs. You have to use this one:
A correct extractor for LG's KDZ Android image files
A correct extractor for LG's KDZ Android image files - kdz.py
gist.github.com
This is the correct, working KDZ extractor. Save this raw Python script for example as a kdz_extractor.py.
Now, assuming you already have performed the previous necessary steps like installing zstandard with pip, all you have to do is:
python3 kdz_extractor.py -e <where to extract> <kdz to extract>
You'll have a file called 4.boot_a.img, around 96 MBs. Now you can keep following the OP guide.
I can provide the patched boot_a.img for LMG910EMW Android 11 20a version if someone needs it.

Pinging @Chick0Nugget and @KRAZZIEBOY because they were interested.

swaguduzo said:
Pinging @Chick0Nugget and @KRAZZIEBOY because they were interested.
Click to expand...
Click to collapse
Yeah i already saw it and it worked.... Just forgot to write you a big : THAAAANNNNK YooooooUUUU!!!!!!!!!

Hi. Thank you very much for the detailed explanations.
Update. Rooting worked for me for LG Velvet LMG910EMW and Android 12 with a minor change:
The extract of boot.img did not work as described. Following tools failed for me
1 kdztools -> "Error: extraneous data found IN version" :-/
2 LG Extractor tool -> ZlibException: Bad state - zero bytes :-/ (also with kdz DZ file)
3 "hovatek" ectractor -> unsupported data file :-/ (tested with both DZ and KDZ files)
4 adb dd command to dump the my-name boot partition -> permission denied :-/
Finally it worked with kdz.py from https://gist.github.com/iscgar/e0da0868df7b2f179b000c61f12d1a8c
So i just put in the 5GB Android 12 KDZ from my previous flash and it extracted all partitions including the boot_a.img/boot_b.img files (each around 93 MB).
A quick test with fastboot boot boot_a.img showed that they are working.
Btw. I unlocked the bootloader already with Android 10 (see other post), before i updated to Android 12 with LGROMUP1.1.
The original LGUP did not work because the roms i found are in region "DEA" and my phone seems to be restricted for EU market.
In LGROMUP1.1, this seems to play no role. There was no partition selection, just "flash" button, but it preserved the unlocked bootloader to my surprise.
A lot of automatic restarts until it reached 100%, but everything went smooth.
Cheers.

I am interested in this Velvet 4G with dual screen. Can you answer me two questions please: 1º Is the battery life good? 2º Does the dual screen of the Velvet 5G snap765 work in this 4G model? Thanks friends.

General Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)

These images are NOT built from source.
These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification.
18.0840.2202.231
18.0840.2201.226
18.0840.2112.211
18.0840.2111.200
18.0840.2111.196
18.0840.2109.188
18.0840.2109.176
18.0840.2107.151
18.0840.2106.86
18.0840.2104.56
You must have already unlocked the bootloader to flash these images. If you have not unlocked the bootloader, you will need to install and run the Unlock Device App from Asus before continuing.
You will also need fastboot to install these images. If you do not wish to install the Platform Tools Package, there is a portable package available. Extract the archive and move the images to the same folder as fastboot.
Each folder on AndroidFileHost contains the stock boot image, stock vendor_boot image, and stock DTBO named by firmware.
Code:
fastboot flash boot [/path/to/image]
fastboot flash vendor_boot [/path/to/image]
fastboot flash dtbo [/path/to/image]
Root images have been removed due to misuse. As a reminder, do NOT lock your bootloader without restoring stock images FIRST.
If you want a rooted device, the stock boot image can be used with the "Select and Patch a File" install option in Magisk.
If you have wiped your device or uninstall magisk, even with a rooted image, root will not work until the app is installed again.
The vendor_boot and dtbo are flashed when restoring from a custom kernel. They are not required to (un)root your device.

Can the Vendor Boot image (Patched) give read/write access to system via root explorer ?
May sound stupid, But I was wondering.. ^^
I used to patch the hosts file manually, and replace it in system,
Now I need the magisk hosts module, and the adaway app both.

JazonX said:
Can the Vendor Boot image (Patched) give read/write access to system via root explorer ?
May sound stupid, But I was wondering.. ^^
I used to patch the hosts file manually, and replace it in system,
Now I need the magisk hosts module, and the adaway app both.
Click to expand...
Click to collapse
Doubtful. The new Android layout is a mess. The actual purpose of the vendor image is for Google to make generic base kernels and have all the customization as an overlay. It isn't the vendor making the system read only. That is part of the partition layout and firmware structure.
They use images that are much larger than the partition size, but compressed and mounted like a virtual machine. Even though the old "Ubuntu on Android" mods did much the same thing and allowed editing, I believe they locked these up to prevent issues with changing the compressed size or flat out lack of necessity to write the code.

MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Leaving this here for anyone that ends up using these images to root the device

twistedumbrella said:
Doubtful. The new Android layout is a mess. The actual purpose of the vendor image is for Google to make generic base kernels and have all the customization as an overlay. It isn't the vendor making the system read only. That is part of the partition layout and firmware structure.
They use images that are much larger than the partition size, but compressed and mounted like a virtual machine. Even though the old "Ubuntu on Android" mods did much the same thing and allowed editing, I believe they locked these up to prevent issues with changing the compressed size or flat out lack of necessity to write the code.
Click to expand...
Click to collapse
Did you come across this tool ?

JazonX said:
Did you come across this tool ?
Click to expand...
Click to collapse
Neat party trick, but fundamentally just piece of mind. You end up using a bunch of space that could just as easily be a fraction with modules. We have a super partition, but no custom recovery. You will be running it with a live install, which is a whole lot of risk for partition corruption. The partitions on this seem a little too finicky. I couldn't bring myself to try.
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
(For our friends that prefer the preview panel)

Added V18.0840.2109.176

2109.176 and 2109.188 may be interchangeable. There appear to be no kernel changes.

Added V18.0840.2109.188

Added V18.0840.2111.196
payload_dumper is returning an empty image for vendor_boot, so it was not uploaded. I am not sure if this is because it is a legitimately empty image or some other issue. If anyone happens to have different results, please let me know. I will investigate further.

twistedumbrella said:
Added V18.0840.2111.196
payload_dumper is returning an empty image for vendor_boot, so it was not uploaded. I am not sure if this is because it is a legitimately empty image or some other issue. If anyone happens to have different results, please let me know. I will investigate further.
Click to expand...
Click to collapse
the vendor_boot.img I have extracted is 98,304 kb which I just downloaded yesterday.

arctic4x4 said:
the vendor_boot.img I have extracted is 98,304 kb which I just downloaded yesterday.
Click to expand...
Click to collapse
It extracted fine today. Who knows.

it boot patched magisk, or stock pulled from the firmware?

starshina1976 said:
it boot patched magisk, or stock pulled from the firmware?
Click to expand...
Click to collapse
I don't know what you're asking, but both are provided.

I mean, is the kernel stock, or patched? Sorry, I'm using a translator.

I need it for firmware 196. Rog phone 5.

starshina1976 said:
I mean, is the kernel stock, or patched? Sorry, I'm using a translator.
Click to expand...
Click to collapse
boot-(version),img is stock
boot-(version)-magisk.img is patched.

Thanks, I will try.

I just load the boot.img you posted it for
root.
18.0840.2111.196 for my same firmware and relocked my bootloader
So now I'm Stucked on bootloader i can't even go recovery

So after you ruined my experience on mobile any help can help me with