Related
Okay, so im new to this stuff and still i managed to root the phone and flash RR 7.1.2. But i tried to unroot it and this happend:
I only have access to the bootloader and thats it. No recovery, no ROM nothing....when i start ti, it says that my phoe is unlocked and its dangerous and that the phone will boot in 5 secs but it never does....plz help me..and i wanna know where can i learn about all this stuff...its freaking me out since this the only phone i have.....plz help me..
You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image
TheFixItMan said:
You have two options
1 - flash twrp recovery and then use it to flash a custom rom
Assuming you have named the recovery image recovery.img
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
2 - flash stock rom firmware which can be found (plenty of guides out there for how to just search)
https://mirrors.lolinet.com/firmware/moto/cedric/official/
If you have unlocked the bootloader it will always says your device is not secure unless you flash a modified boot image
Click to expand...
Click to collapse
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.
Astitva_ said:
Dude, I'm a total idiot at this stuff...
I was trying to flash the stock ROM by some help from a youtube channel called Andoid Doctor. I used the codes he gave me and the stock firmware he provided me for cedric. But all my computer showed was some slot error.
I'd really appreciate it if you helped me out.
Click to expand...
Click to collapse
Firmware must be the same or newer
See the link in my post above for all the firmware - choose the right one for your region
If you don't know which to choose just use this one
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands are (assuming you know how to use & have fastboot already setup as you have already unlocked the bootloader)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin (only flash if newer version of android eg going from nougat to oreo)
fastboot flash bootloader bootloader.img (only flash if going to a newer version of android)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
TheFixItMan said:
fastboot flash recovery recovery.img
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Then wipe system data cache/format data & follow procedure to flash a custom rom
Click to expand...
Click to collapse
Wasn't trying to go back to stock myself (though I did have to in the end) but this was the only rom I found that worked full stop. Thanks so much for this.
so I've been trying to install a gsi for 5+ hours, I can never even get to the system boot animation. I've used permissiver, disable dm-verity, I've tried phh, erfans miui, oneui, oos, but cant get to the bootanimation. here are the steps i followed:
1. format
2. flash lineageos
3. wipe cache, dalvik, system, data
4 flash system.img gsi to system
5. flash permissiver and disable dmverity
6. reboot system
7. I get a redmi logo for 4 seconds, a black screen for 1 second and it keeps looping.
pls somebody help
You need to create a vendor.
hussain_mdj said:
You need to create a vendor.
Click to expand...
Click to collapse
pls elaborate, do i need to backup my current vendor, and then restore after installing the system.img?
I don't know why you have process steps like above, but basically the steps should be ( tested and used by me and all 2k members of my grp ) :
1st, you should be on stock, because GSI has only System images, and for a device to work, it need more than just a System images.
Boot into system, using adb reboot bootloader to get into bootloader mode ( or you can use hard keys, its up to you ). Execute these command in correct order :
fastboot devices ( check if device is connected )
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img ( remember to use patched vbmeta.img )
fastboot erase system
fastboot flash system system.img ( change to gsi's image file name )
fastboot -w
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot
It may depends on what kind of device u have, but basically it should be like this. Try and feedback.
THIS WILL WIPE YOUR DATA!
YOU MIGHT BRICK YOUR PHONE!
MAKE. A. BACKUP!!!
THIS IS A GENERAL GUIDE BASED ON THE x70 PRO PLUS AND NEEDS A LOT OF MODIFICATIONS FOR YOUR DEVICE.
Requirements:
- Unlocked Bootloader: Guide I, Guide II
- Root to extract boot.img and recovery.img (and make a backup)
- Android Image Kitchen (AIK)
- QFIL / Split image of your target firmware
- OTA Firmware with a higher version than your Split Image
I. Root your phone You should backup all partitions either through magisk (if you have the current running firmware as ota.zip) or LineageOS GSI with me.phh.superuser.apk
The backup commands for the Vivo x70 Pro+ and a general guide can be found in the linked post.
If you have another device use adb to find your blocks and their proper partition names and modify the "script" from my post.
Code:
adb shell
ls -al /dev/block/by-name/
Do NOT backup userdata and sda.
II. Modify recoveryIn order to enable adb in recovery we have to unpack the recovery.img and change some prop.default values. (You got this recovery.img either by backing up your partitions or having the correct ota.zip)
THIS post has a great guideline, you can skip everything TWRP related.
In Short:
1. Use AIK to unpack recovery.img
2. Delete the /split_img/*ramdisk*.zip ONLY
3. Open /ramdisk/default.prop or /ramdisk/prop.default or similar with a text editor
4. Modify according to step 22 in the linked post (care vivo uses adb.secure=1 two times, edit both properties)
5. Save, repack and flash the new recovery.img
III. Folder Structure1. Create a new folder "transform" on your system and extract your SPLIT firmware files into a subfolder called "split". -> /transform/split/
First off identify your super_x.img files and their corresponding dynamic partitions. In general "system" should be the largest, "vendor" the second largest and odm / oem should be smaller.
You can open them with 7zip and identify their contents. Take note.
For the X70 Pro+: super_2.img = system | super_3.img = vendor | super_4.img = odm
2. Open these files in your ota.zip: /dynamic_partitions_op_list and /oem/dynamic_partitions_op_list.
Take note of the partition sizes for system, vendor, odm and vgc (ex. # Grow partition system from 0 to 5373415424).
3. Rename your OTA file to ota.zip and put it into /transform/ota/
IV. Modified Images1. Download the attached misc-data.img and place it in /transform/modded/ (Thanks to @Pervokur).
If you flash this it tells recovery to look for "ota.zip" in /data/ on the next boot and install it if its available.
You can edit the path via hex editor but its fine for this guide. Dont flash it yet.
2. Patch the recovery.img from /transform/split/ according to step II and place it in /transform/modded/recovery-adb.img
V. Modify the flash script1. Download my reference script and place it as info.txt into /transform/. Modify this script according to the files from your SPLIT firmware and your partition backups. Vivo phones with different hardware versions might be way more complicated. Analyze everything and take your time - you dont want to brick your device.
PAY ATTENTION: In the best case and at the very least you will have to modify vbmeta_oem, vbmeta_vgc, system, vendor, odm, oem and vgc to match your files.
DO NOT flash your fsg partition. This one basically contains your modem. If you do flash it or if you dont have signal after an ota update scroll down.
2. Go to "::RECREATE DYNAMIC PARTITIONS" and modify the partition sizes according to the values of III.2.
Code:
::OPEN A SHELL IN THIS FOLDER
::REBOOT YOUR PHONE INTO FASTBOOT (REBOOT AND HOLD POWER + VOL UP)
fastboot reboot bootloader
fastboot flash abl split/abl.elf
fastboot flash aop split/aop.mbn
fastboot flash boot split/boot.img
fastboot flash bluetooth split/BTFM.bin
fastboot flash cpucp split/cpucp.elf
fastboot flash devcfg split/devcfg.mbn
fastboot flash apdp split/dp_AP_signed_minidump.mbn
fastboot flash dsp split/dspso.bin
fastboot flash dtbo split/dtbo.img
fastboot flash factory split/factory.img
fastboot flash featenabler split/featenabler.mbn
fastboot flash storage split/firmware.bin
fastboot flash hyp split/hypvm.mbn
fastboot flash keymaster split/km41.mbn
fastboot flash logfs split/logfs_ufs_8mb.bin
fastboot flash mdcompress split/mdcompress.mbn
fastboot flash metadata split/metadata.img
::fastboot flash modemst1 split/modemst.mbn
::fastboot flash modemst2 split/modemst.mbn
fastboot flash multiimgoem split/multi_image.mbn
::fastboot flash fsg split/PD2145F_EX_fs_image.tar.gz.mbn.img
fastboot flash persist split/persist.img
fastboot flash qupfw split/qupv3fw.elf
fastboot flash recovery modded/recovery-adb.img
fastboot flash rtice split/rtice.mbn
fastboot flash secdata split/sec.elf
fastboot flash shrm split/shrm.elf
fastboot flash spunvm split/spunvm.bin
fastboot flash storsec split/storsec.mbn
fastboot flash tz split/tz.mbn
fastboot flash uefisecapp split/uefi_sec.mbn
fastboot flash vbmeta split/vbmeta.img
fastboot flash vbmeta_oem split/vbmeta_oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vbmeta_system split/vbmeta_system.img
fastboot flash vbmeta_vgc split/vbmeta_vgc_NULL_PD2145F_EXMA.img
fastboot flash vendor_boot split/vendor_boot.img
fastboot flash vm-bootsys split/vm-bootsys.img
fastboot flash vgc split/vgc.img
fastboot flash xbl_config split/xbl_config.elf
fastboot flash xbl split/xbl.elf
fastboot flash xbl_configbak split/xbl_config.elf
fastboot flash xblbak split/xbl.elf
fastboot flash modem split/NON-HLOS.bin
::RECREATE DYNAMIC PARTITIONS
fastboot reboot fastboot
fastboot delete-logical-partition system
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm
fastboot delete-logical-partition vgc
fastboot create-logical-partition system 5373415424
fastboot create-logical-partition vendor 3128008704
fastboot create-logical-partition odm 1392640
fastboot create-logical-partition vgc 348160
::FLASH DYNAMIC PARTITIONS
::VGC WILL OUTPUT AN ERROR - DONT MIND
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot erase odm
fastboot erase oem
fastboot erase vgc
fastboot flash system split/super_2.img
fastboot flash vendor split/super_3.img
fastboot flash odm split/super_4.img
fastboot flash oem split/oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vgc split/vgc_NULL_PD2145F_EXMA.img
fastboot reboot recovery
::IF IT DOESNT REBOOT JUST USE THE BUTTON ON YOUR PHONE
::NOW GO TO WIPE AND WIPE DATA & CACHE 2X
::CHECK SYSTEM -> RECOVERY SHOULD FAIL, EVERYTHING ELSE PASS
adb push ota/ota.zip /data
adb reboot bootloader
fastboot flash misc modded/misc-data.img
fastboot reboot
::LET THE PHONE START ONCE (ABOUT 1-5MIN)
::YOU ARE NOW ON FUNTOUCH
--------------------------------------------------------------------------
::YOU CAN BACKUP OTA PACKAGES FROM HERE WHEN THEY ARE DOWNLOADED (ROOT ONLY)
/data/vivo-updater/com.bbk.updater/OTAPackage/
::UPDATE TO THE LATEST VERSION VIA OTA ONLY AFTER YOU BACKUP THE OTA
::YOU MUST FLASH YOUR ORIGINAL BOOT.IMG BEFORE UPDATING
VI. Run the commands according to your modified flash script.VII. Problems1. Brick?
Flash all partitions from your backup
2. No signal?
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg your-original-backup-fsg.img
3. DM-Verity Warning?
Code:
adb shell service call package 134 s16 com.vivo.daemonService i32 0 i32 0
Might be different for you but try it.
4. Fingerprint not working?
Try this post.
Huge thanks to @Pervokur for finding the bootloader exploit, guiding me through this and providing help all the way!
In general there should be an easier method without having to flash a lot of things. This is hypothetical information:
Vivo Recovery looks for device identifiers in the following locations:
Code:
/vgc/env.prop ro.*
/vendor/vgc/vendor_env.prop ro.*
/vgc/vgc.prop ro.*
/vendor/vgc/vgc.prop ro.*
/oem/oem.prop ro.*
/recovery/prop.default
/default.prop
/prop.default
If we mod the recovery of our target firmware by removing all import functions from prop.default and apply the adb fixes from post 1 we should in theory be able to fake our device identifiers for the ota.zip.
In order to boot the target firmware recovery we also need to flash boot, vendor_boot, vbmeta and dtbo from the target firmware.
Then we adb push ota.zip to data, flash misc-data and reboot to flash the ota update.
This is just a theory at the moment, if you feel adventurous you can try it and report back.
Sir, I try your way to flash x80pro, cannot boot in system...
CHECK SYSTEM in recovery show system check fail....
I'm sure the super_5 is system because it is the largest.
Use 7z check it, have system folder inside.
May work for VIVO IQOO 9 Pro also ?
i have the x70pro+ unlocked bootloader, backup the partition and modify recovery, the next step is about the ota.zip and flashing. Can you give me more details about those steps? Killuminati91. Many tks sir
NHQ Thang said:
i have the x70pro+ unlocked bootloader, backup the partition and modify recovery, the next step is about the ota.zip and flashing. Can you give me more details about those steps? Killuminati91. Many tks sir
Click to expand...
Click to collapse
This is as far as I got to on my x70pp, not sure how to make a split rom but assume it needs to be from the funtouch rom (but not the newest release)?
Killuminati91 said:
THIS WILL WIPE YOUR DATA!
YOU MIGHT BRICK YOUR PHONE!
MAKE. A. BACKUP!!!
THIS IS A GENERAL GUIDE BASED ON THE x70 PRO PLUS AND NEEDS A LOT OF MODIFICATIONS FOR YOUR DEVICE.
Requirements:
- Unlocked Bootloader: Guide I, Guide II
- Root to extract boot.img and recovery.img (and make a backup)
- Android Image Kitchen (AIK)
- QFIL / Split image of your target firmware
- OTA Firmware with a higher version than your Split Image
I. Root your phone You should backup all partitions either through magisk (if you have the current running firmware as ota.zip) or LineageOS GSI with me.phh.superuser.apk
The backup commands for the Vivo x70 Pro+ and a general guide can be found in the linked post.
If you have another device use adb to find your blocks and their proper partition names and modify the "script" from my post.
Code:
adb shell
ls -al /dev/block/by-name/
Do NOT backup userdata and sda.
II. Modify recoveryIn order to enable adb in recovery we have to unpack the recovery.img and change some prop.default values. (You got this recovery.img either by backing up your partitions or having the correct ota.zip)
THIS post has a great guideline, you can skip everything TWRP related.
In Short:
1. Use AIK to unpack recovery.img
2. Delete the /split_img/*ramdisk*.zip ONLY
3. Open /ramdisk/default.prop or /ramdisk/prop.default or similar with a text editor
4. Modify according to step 22 in the linked post (care vivo uses adb.secure=1 two times, edit both properties)
5. Save, repack and flash the new recovery.img
III. Folder Structure1. Create a new folder "transform" on your system and extract your SPLIT firmware files into a subfolder called "split". -> /transform/split/
First off identify your super_x.img files and their corresponding dynamic partitions. In general "system" should be the largest, "vendor" the second largest and odm / oem should be smaller.
You can open them with 7zip and identify their contents. Take note.
For the X70 Pro+: super_2.img = system | super_3.img = vendor | super_4.img = odm
2. Open these files in your ota.zip: /dynamic_partitions_op_list and /oem/dynamic_partitions_op_list.
Take note of the partition sizes for system, vendor, odm and vgc (ex. # Grow partition system from 0 to 5373415424).
3. Rename your OTA file to ota.zip and put it into /transform/ota/
IV. Modified Images1. Download the attached misc-data.img and place it in /transform/modded/ (Thanks to @Pervokur).
If you flash this it tells recovery to look for "ota.zip" in /data/ on the next boot and install it if its available.
You can edit the path via hex editor but its fine for this guide. Dont flash it yet.
2. Patch the recovery.img from /transform/split/ according to step II and place it in /transform/modded/recovery-adb.img
V. Modify the flash script1. Download my reference script and place it as info.txt into /transform/. Modify this script according to the files from your SPLIT firmware and your partition backups. Vivo phones with different hardware versions might be way more complicated. Analyze everything and take your time - you dont want to brick your device.
PAY ATTENTION: In the best case and at the very least you will have to modify vbmeta_oem, vbmeta_vgc, system, vendor, odm, oem and vgc to match your files.
DO NOT flash your fsg partition. This one basically contains your modem. If you do flash it or if you dont have signal after an ota update scroll down.
2. Go to "::RECREATE DYNAMIC PARTITIONS" and modify the partition sizes according to the values of III.2.
Code:
::OPEN A SHELL IN THIS FOLDER
::REBOOT YOUR PHONE INTO FASTBOOT (REBOOT AND HOLD POWER + VOL UP)
fastboot reboot bootloader
fastboot flash abl split/abl.elf
fastboot flash aop split/aop.mbn
fastboot flash boot split/boot.img
fastboot flash bluetooth split/BTFM.bin
fastboot flash cpucp split/cpucp.elf
fastboot flash devcfg split/devcfg.mbn
fastboot flash apdp split/dp_AP_signed_minidump.mbn
fastboot flash dsp split/dspso.bin
fastboot flash dtbo split/dtbo.img
fastboot flash factory split/factory.img
fastboot flash featenabler split/featenabler.mbn
fastboot flash storage split/firmware.bin
fastboot flash hyp split/hypvm.mbn
fastboot flash keymaster split/km41.mbn
fastboot flash logfs split/logfs_ufs_8mb.bin
fastboot flash mdcompress split/mdcompress.mbn
fastboot flash metadata split/metadata.img
::fastboot flash modemst1 split/modemst.mbn
::fastboot flash modemst2 split/modemst.mbn
fastboot flash multiimgoem split/multi_image.mbn
::fastboot flash fsg split/PD2145F_EX_fs_image.tar.gz.mbn.img
fastboot flash persist split/persist.img
fastboot flash qupfw split/qupv3fw.elf
fastboot flash recovery modded/recovery-adb.img
fastboot flash rtice split/rtice.mbn
fastboot flash secdata split/sec.elf
fastboot flash shrm split/shrm.elf
fastboot flash spunvm split/spunvm.bin
fastboot flash storsec split/storsec.mbn
fastboot flash tz split/tz.mbn
fastboot flash uefisecapp split/uefi_sec.mbn
fastboot flash vbmeta split/vbmeta.img
fastboot flash vbmeta_oem split/vbmeta_oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vbmeta_system split/vbmeta_system.img
fastboot flash vbmeta_vgc split/vbmeta_vgc_NULL_PD2145F_EXMA.img
fastboot flash vendor_boot split/vendor_boot.img
fastboot flash vm-bootsys split/vm-bootsys.img
fastboot flash vgc split/vgc.img
fastboot flash xbl_config split/xbl_config.elf
fastboot flash xbl split/xbl.elf
fastboot flash xbl_configbak split/xbl_config.elf
fastboot flash xblbak split/xbl.elf
fastboot flash modem split/NON-HLOS.bin
::RECREATE DYNAMIC PARTITIONS
fastboot reboot fastboot
fastboot delete-logical-partition system
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm
fastboot delete-logical-partition vgc
fastboot create-logical-partition system 5373415424
fastboot create-logical-partition vendor 3128008704
fastboot create-logical-partition odm 1392640
fastboot create-logical-partition vgc 348160
::FLASH DYNAMIC PARTITIONS
::VGC WILL OUTPUT AN ERROR - DONT MIND
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot erase odm
fastboot erase oem
fastboot erase vgc
fastboot flash system split/super_2.img
fastboot flash vendor split/super_3.img
fastboot flash odm split/super_4.img
fastboot flash oem split/oem_PD2145F_EX_IN_NULL_NULL.img
fastboot flash vgc split/vgc_NULL_PD2145F_EXMA.img
fastboot reboot recovery
::IF IT DOESNT REBOOT JUST USE THE BUTTON ON YOUR PHONE
::NOW GO TO WIPE AND WIPE DATA & CACHE 2X
::CHECK SYSTEM -> RECOVERY SHOULD FAIL, EVERYTHING ELSE PASS
adb push ota/ota.zip /data
adb reboot bootloader
fastboot flash misc modded/misc-data.img
fastboot reboot
::LET THE PHONE START ONCE (ABOUT 1-5MIN)
::YOU ARE NOW ON FUNTOUCH
--------------------------------------------------------------------------
::YOU CAN BACKUP OTA PACKAGES FROM HERE WHEN THEY ARE DOWNLOADED (ROOT ONLY)
/data/vivo-updater/com.bbk.updater/OTAPackage/
::UPDATE TO THE LATEST VERSION VIA OTA ONLY AFTER YOU BACKUP THE OTA
::YOU MUST FLASH YOUR ORIGINAL BOOT.IMG BEFORE UPDATING
VI. Run the commands according to your modified flash script.VII. Problems1. Brick?
Flash all partitions from your backup
2. No signal?
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg your-original-backup-fsg.img
3. DM-Verity Warning?
Code:
adb shell service call package 134 s16 com.vivo.daemonService i32 0 i32 0
Might be different for you but try it.
4. Fingerprint not working?
Try this post.
Huge thanks to @Pervokur for finding the bootloader exploit, guiding me through this and providing help all the way!
Click to expand...
Click to collapse
Hi. I'm very much a noob in dealing with flashing and those stuff. Is there an easier way to do this? Some way that will be idiot-proof?
I currently have a x70pro+ with originOs Ocean and an unlocked bootloader (I think?), do I still need to root to do this process?
Thank you for sharing
edcsxz said:
Sir, I try your way to flash x80pro, cannot boot in system...
CHECK SYSTEM in recovery show system check fail....
I'm sure the super_5 is system because it is the largest.
Use 7z check it, have system folder inside.
Click to expand...
Click to collapse
Which files do you use for QFIL or split image and OTA firmware?
First, a small "introduction":
Would you like to gain up to 10-15% more performance in GPU-based tasks just by replacing the GPU drivers with something newer?
Sadly, Qualcomm doesn't seem to care about updating the GPU drivers on older devices or generally updating drivers at all after the initial release of the device.
Both OpenGL and Vulkan APIs are mostly outdated on our devices, and thanks to some folks, they extracted the GPU drivers from newer devices/GPUs, added some tweaks, and made it flashable to any device using XY compatible GPU.
Now, the issue with this device (The OnePlus 9 Pro) is that it doesn't have an A12 compatible TWRP, and these drivers REQUIRE TWRP, otherwise they can't be flashed. The other problem is that most of the Custom A12 ROMs come with their Vendor partitions being only RO (Read Only). In order to flash the custom drivers, Vendor partitions need to be mounted as RW (Read-Write) and it requires a certain amount of free space so that the drivers can be replaced by the custom ones (GPU drivers are located in the Vendor partition).
So, let's start with the tutorial...It might get a bit lengthy, and the process is a bit time-consuming and requires patience and careful execution. (I'm not gonna write about basics like how to use Fastboot and ALL of the commands, you should be familiar with some basics, otherwise, maybe you should skip the tutorial and stay on the old drivers, I don't have much free time to explain the basics, sorry).
WARNING: This tutorial requires FORMATING your DATA during the process. BACKUP YOUR DATA BEFORE ATTEMPTING ANYTHING, I'M NOT RESPONSIBLE FOR YOUR FILES OR WHATEVER HAPPENS TO YOUR PHONE.
This tutorial is tested on BOTH OOS11 and OOS12 based CUSTOM ROMs. This tutorial doesn't apply to STOCK OOS ROMs and I don't support STOCK ROMs in this case.
There are two parts to this process, one concerning only people who are on OOS11-based CUSTOM ROMs, and the other part is an addition to the first part for people who are on OOS12-based custom ROMs. (I'll upload most of the needed files)
So, let us begin (bruh...I'm already tired):
PART ONE: Users of OOS11-based CUSTOM ROMs:
In order to boot TWRP, you need to replace the Boot.img, dtbo.img and Vendor_boot.img with a stock one from OOS11 ROM.
Extract the "OOS11 boot,dtbo, vendor_boot.zip" file and use those IMGs.
So, boot to Fastboot, and execute the following commands:
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Fastboot flash vendor_boot_a vendor_boot.img
Fastboot flash vendor_boot_b vendor_boot.img
Restart the bootloader once (DON'T attempt to boot into the system, you're gonna end up in Bootloop or crashdump)
Now you're in bootloader again, do the following command to boot the TWRP.
Fastboot boot twrp.img
This will boot into TWRP. Now you're inside the TWRP, go and FORMAT DATA (wipe internal storage), when it's done, go back to Bootloader, and boot TWRP again, remember, BOOT TWRP with the previous command I shared, don't attempt to FLASH it.
Now, FLASH the systemrw_1.32-MOD-Edit.zip file. This is a bit "lengthy" process, it takes a few minutes. When the process is done, reboot again to the bootloader and boot back to TWRP.
After this, mount the vendor partitions inside TWRP, and FLASH the drivers "[email protected]_twrp_v3.zip".
When you're done doing that, we need to flash the BOOT, DTBO and the Vendor_boot IMG's from the ROM you're currently using. (You can extract the IMG's from your ROM.zip by using Payload dumper-GO from Github.)
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Fastboot flash vendor_boot_a vendor_boot.img
Fastboot flash vendor_boot_b vendor_boot.img
After you're done flashing these stock partitions, you should be able to boot inside the system without any issues. (tested, working, on multiple ROMs, the process is universal).
You can check if the drivers are updated with AIDA64 (Playstore) by going to the Display option. Drivers should be revisioned as 615_V3. (Old drivers are either 530 or 525)
PART TWO: Users of OOS12-based CUSTOM ROMs:
This is the "tricky" part now since TWRP WON'T boot on these ROMS just by replacing the stock (OOS11) dtbo and vendor_boot IMGs. We need to flash the OOS11 FIRMWARE first and later on, we need to go BACK to OOS12 firmware otherwise the ROM won't boot since the blobs are based on the OOS12 firmware.
First, we need to flash a recovery that supports FastbootD mode so that the following script can flash all the necessary firmware files.
Extract PEX Recovery.zip, and flash the partitions using the following commands:
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Fastboot flash vendor_boot_a vendor_boot.img
Fastboot flash vendor_boot_b vendor_boot.img
After this is done, restart once to bootloader.
Now we need first to flash the OOS11 firmware. Flashing this is kind of one-click, it's a script that is kind of automated.
Extract the "OP9Poos11.2.10.10(GL)-FIRMWARE-fastboot.zip" file, and click on "Update firmware.bat" file. It will start the process automatically, and it will reboot to fastbootD once by itself.
Once the flashing process is completed, reboot once to bootloader, and proceed to flash the OOS11 stock partitions by extracting the file "OOS11 boot,dtbo, vendor_boot.zip", commands as follows:
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Fastboot flash vendor_boot_a vendor_boot.img
Fastboot flash vendor_boot_b vendor_boot.img
When you're done, reboot once to bootloader and boot the TWRP:
Fastboot boot twrp.img
This will boot into TWRP. Now you're inside the TWRP, go and FORMAT DATA (wipe internal storage), when it's done, go back to Bootloader, and boot TWRP again, remember, BOOT TWRP with the previous command I shared, don't attempt to FLASH it.
Now, FLASH the systemrw_1.32-MOD-Edit.zip file. This is a bit "lengthy" process, it takes a few minutes. When the process is done, reboot again to the bootloader and boot back to TWRP.
After this, mount the vendor partitions inside TWRP, and FLASH the drivers "[email protected]_twrp_v3.zip".
Now, we need to go back to OOS12 FIRMWARE so that our ROM can boot (once again, OOS12 based ROMs require OOS12 firmware as a base in order to work/boot).
We need to repeat again this step:
We need to flash a recovery that supports FastbootD mode so that the following script can flash all the necessary firmware files.
Extract PEX-Recovery.zip, and flash the partitions using the following commands:
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Fastboot flash vendor_boot_a vendor_boot.img
Fastboot flash vendor_boot_b vendor_boot.img
After this is done, restart once to bootloader.
Extract the "OP9Poos12(LE2125_11.C.48(GL))-FIRMWARE-fastboot.zip" file, and click on "Update firmware.bat" file. It will start the process automatically, and it will reboot to fastbootD once by itself.
When it's done doing that, we need to flash the BOOT, DTBO and the Vendor_boot IMG's from the ROM you're currently using. (You can extract the IMG's from your ROM.zip by using Payload dumper-GO from Github.)
The commands are the same, as follows:
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
Fastboot flash dtbo_a dtbo.img
Fastboot flash dtbo_b dtbo.img
Fastboot flash vendor_boot_a vendor_boot.img
Fastboot flash vendor_boot_b vendor_boot.img
After you're done flashing these stock partitions, you should be able to boot inside the system without any issues. (tested, working, on multiple ROMs, the process is universal).
So, that should be all, If I made a mistake somewhere, I'll keep editing the thread on the go if I find something wrong.
I attached 2 screenshots from 3DMark Wildfire test, before and after the score increase. Keep in mind, that the score might differ a bit, different CHIP quality might yield worse or better scores regardless of which drivers are used.
Vulkan API based games will gain more than OpenGL games, FYI. If you're playing some less demanding games, you won't obviously need more performance, but the GPU, in this case, will work "less", you'll have lower GPU usage considering the overall increase of the GPU performance.
{
"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"
}
Once again, I'm not trying to be rude, but people with questions like "Fastboot not detected, how to extract payload.bin, how to format DATA in TWRP" will be totally ignored, this is a more "advanced" tutorial, I don't have time explaining absolute basics. Use Google for that, there is plenty of information for your "basic" issues/questions.
You can thank me later, once your OS booted with the new drivers.
Works great running aospa. Thanks for this
JWnSC said:
Works great running aospaView attachment 5667123
Click to expand...
Click to collapse
Josh, you noob. lol Yes, GPU scores are indeed increased, and not only synthetic benchmarks but actual performance in games.
Do we have to do this every time we change roms?
gillim74 said:
Do we have to do this every time we change roms?
Click to expand...
Click to collapse
Unfortunately YES. Changing the ROM will replace the Vendor partition and that vendor partition is stock and contains the stock drivers.
The process of installing custom drivers would take probably less than 5 minutes if we would have a TWRP compatible with A12 ROMs, sadly we don't, and this is one of the "sophisticated" workarounds to boot the TWRP on our devices which use A12 ROMs.
Another "solution" would be that the Developers of the ROMs start including those drivers directly in their ROMs. It's possible, and I've seen some Xiaomi devices which ship Custom ROMs with these updated drivers. It just requires some additional work.
So far, 2 devs attempted to include these drivers, but their ROM builds for some reason didn't boot.
Where Can I find this for stock based rom? I'm using stock 12 OOS with magisk.
Nice ! Could there be a possibility to make it like a magisk module or is that impossible ?
does not work on op9? it goes to crash dump i was at flashing oos12 boot and so on
Alex1911 said:
Nice ! Could there be a possibility to make it like a magisk module or is that impossible ?
Click to expand...
Click to collapse
Theoretically yes, if you find someone to do it. I prefer permanent modification rather than using Magisk in this case.
Diaze said:
does not work on op9? it goes to crash dump i was at flashing oos12 boot and so on
Click to expand...
Click to collapse
Could it be because this is a OnePlus 9 PRO subforum and the files are meant to be used on OnePlus 9 PRO device?
Confirmed working on Stag a12. Decrypted, 615v3 drivers. One plus 9 pro
This with konibess insane results!
Stag Os A12, Vulcan 615 adreno drivers, and gpu oc to 855mhz with uv.
can we have this for op9? maybe make it unified. that would be awesome
.
Custom roms based on OOS12 like Crdroid just moved to base firmware C.61 would this still work provided I follow the same steps with a C.61 update?
Has someone tried with stock oos11?
deleted
CtrlValCanc said:
Has someone tried with stock oos11?
Click to expand...
Click to collapse
u have twrp for oos11 so no need this hassle. flash twrp and flash drivers
I found a Magisk module that seems to be doing the same. It can be flashed on any ROM.
_MartyMan_ said:
I found a Magisk module that seems to be doing the same. It can be flashed on any ROM.
Click to expand...
Click to collapse
A 12 also?
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
thanks for the amazing work on this rom
sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you, guys, for your awesome work. Hope we'll get a stable update. Good luck
sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon)
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
So installed fine on a G10 now the problem is a lack of google apps I want it and I need magisk for half the apps to to add a custom way to run apps that need root.
I cannot get gapps on it for starters as can't go into a recovery menu it's twrp I need to do all this with and the recovery on this is stock really, I will say though that is is an amazing firmware I mean really clean brilliant work but I must have twrp so I can root but also so I can add google apps which is my primary necessity root is a distant second if at all needed i do newed my apps to make images and other tools I use it for daily driver wise.
l Tried to use this TWRP https://cloudhazy.com/download/motorola-moto-g10-xt2127-2-twrp-recovery-3-5-2/ and it fails but I know the model number XT2127-2 is correct so it just doesn't allow installing or launching it, from inside platform tools openeing in a command window here mode????
I am stuck completely now.
@PHYSC-1 you should be able to find magisk inside the attached lineageos zip. Flash that to boot and you should be rooted. I am working on gapps and dual sim currently. Also, don't feel like you are stuck. At any moment, you can flash the stock firmware and go back to stock if you are not able to daily drive lineage os without gapps.
I don't want to have gapps on my phone so I didn't work on it at all until now. I see that many people are asking for gapps, so giving it a try.
In case you don't find the magisk boot image in the lineage os zip, you can create one yourself by installing magisk app and passing this lineageos boot image to it.
@PHYSC-1 we are testing gapps on this ROM now. Me and two users present on our group are testing GAPPS on this ROM. As of now, its running smooth, will publish the update in a week or so.
sultanahamer said:
!!!!!!!!!!!!!!!!!!!!!!!!!WE ARE NOT RESPONSIBLE FOR ANYTHING THAT MIGHT HAPPEN TO YOUR DEVICE TRYING TO INSTALL THIS ROM!!!!!!!!!!!!!!!!!!!!!!
This ROM has been tested for about a week on two capri devices one from India and other from South America
Loads of thanks to @Electimon for his trees and all his help fixing issues we faced in bringing this ROM
Kernel Source: https://github.com/sultanahamer/android_kernel_motorola_msm-4.19 (forked from electimon)
Manifest: https://github.com/sultanahamer/local_manifests
Not working:
FM Radio
Dual Sim (Will look into this soon) - Looked into it. This is being flaky once enabled. Will need more time to fix this.
Telegram group: https://t.me/MotoG10Official
Flashing instructions:
Code:
Make sure you are on latest of your stock Android 11, Booted and the rom is working.
Download zip and extract it and run the following commands
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vendor_boot vendor_boot.img
fastboot -w
fastboot reboot fastboot
fastboot flash system system.img
# In case the above command fails saying parititon size is not enough then try to resize it with below command
fastboot resize-logical-partition system_a 1073741824 #(run this only if the above command fails and if you are on slot_a else change it to system_b)
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot reboot
Click to expand...
Click to collapse
Thank you for this work! I'm also anxious to get a stable, dual chip working version too.
I think the Gapps should be separate to ROM. Of course if it is possible.
Gapps works 2 problems found in testing 1 is a big one for anyone using screen cast the network auto switches from 2.4ghz to 5ghz and back intermittently causing screen cast to drop out mid use and this stuns it and creates constant bad image quality and freezing completely up.
Secondly this could be unrelated to the OS but it doesn't happen on official Motorola OS's when using the app from F-Droid called simple gallery pro if you edit an image and try to draw on an image the drawing occurs in the wrong position the pointer is below where you draw on?