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?
Related
How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)
I am currently on lineage OS 14.1 (7.1.2) dated 18.09.2017.
I want to go back to stock firmware as I am facing some issues with lineage.
How to find the latest firmware. Found this website which has all the images https://firmware.center/firmware/Motorola/Moto Z Play/Stock/XT1635-02/
But I am unable to select the correct one for my device. (do not want to brick it). Also found another thread stating latest firmware
https://forum.xda-developers.com/moto-z-play/help/addisonnpns26-118-22-1cid50subsidy-t3675521
I am an Indian MOTO Z Play
Is there a way to go full stock and also start to receive OTA updates. Can someone provide me with full guide with links?
First you need exactly your software channel and the build of your baseband and bootloader. You know how to get this information?
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
kkube said:
After a lot of tries, finally was able to go back to stock. Will be compiling a guide for other to follow with links.
On latest 7.1.1 with August patches.
Is there a problem with audio fx,
Even viper4android not working.
Click to expand...
Click to collapse
I'll be waiting for it.
Process to go from custom rom back to stock (August update)
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
Click to expand...
Click to collapse
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
And can we do OTA updates after doing this?
Thank you so much for this guide, my phone was rebooting to recovery every single time and nothing worked. I flashed this rom as you said and my phone just booted and it's working. I can't believe it.
Is this works with European version of Moto Z Play? Like I bought it from France. Thanks.
Click to expand...
Click to collapse
My phone is reteu and after flashing is still on reteu, so it should be fine, dont worry. Also you should get any future updates via OTA.
kkube said:
There are several guides on going back from custom rom to full stock, but still I made this guide with latest links. I just went from LOS 14.1 back to full stock. Below is the step I took:
1) Download and install minimal ADB AND FASTBOOT
I used version 1.4.2 which is the latest version https://www.androidfilehost.com/?fid=745425885120698566
2) Download and install motorola drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3) Download the latest firmware
I used ADDISON_NPNS26.118-22-1 which has august security updates https://www.androidfilehost.com/?fid=673368273298986785
4) Extract the zip file (firmware) and move all its contents to the folder where you have installed minimal adb and fastboot
5) Create a text file, add the following text to it and save it as "launch.bat" in the same folder.
6) Switch off your phone and open it in fastboot mode (press power and volume down button for few seconds after phone as switched off)
7) Connect your mobile to your computer
8) Click on the launch.bat file that you saved and it will install stock firmware on to your mobile. It will take a couple of minutes. (It will wipe everything on your mobile so take a backup of your important data)
9) Once the process is complete, it will ask you to enter any key, after which it will reboot itself.
Once rebooted, you will have full stock, non rooted, and latest firmware with august patches.
Click to expand...
Click to collapse
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
akshaypatil869 said:
Thanks a lot for this guide! Just wanted to ask if it's safe and stable to root this and pass safetynet check.
Thanks for you time
Click to expand...
Click to collapse
Only way to root and still pass safetynet is via magisk
But unfortunately it needs a custom kernel with f2fs fix. However with 7.1 update motorola fixed it but broke some other things.
There is not a custom kernel for 7.1, so till then no way to root and have safety net.
But you can easily root via magisk
Does anyone receive the update with September patch via OTA after back to stock following post #5 instructions?
This a fantastic guide - THANKS!!! - I have linked to it giving credit. Thanks!
I have also a thread, if you follow that one. Bootloader is locked/ u will be able to get ota'$
Hi all,
I'm sorry to ask this question, but I'm really struggling to get my Nexus 5X to boot into stock rom. The install seems to go ok, but there was error when flashing.. See below...
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
The phone now boots to the google boot logo, then loops back to either the "Unlocked Bootloader" or the Custom OS message. (depending on the locked state of the bootloader)
I cannot get into recovery, as the phone just loops back as described above when selecting it from the bootloader option.
Can anyone advise me on how to restore the phone back to stock os. I've tried flashing version 7.1.2 8.0.0 and 8.1.0, using either the flash-all.bat or manually typing the commands. I'm 110% sure this is not to do with over heating on CPU/RAM, I have another nexus 5x that has the bootloop of death and it's bootloop is very different from what I'm seeing on this Nexus 5x.
Thanks in advance
First, the .sig errors are normal so you can ignore those. I would make sure your booloader is unlocked then manually flash the bootloader.img. Then boot back into the bootloader. Then manually flash the remainder of the partitions. Use the 8.1.0 os.
Sent from my [device_name] using XDA-Developers Legacy app
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
pinkstink said:
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
Click to expand...
Click to collapse
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
i.adrian said:
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
Click to expand...
Click to collapse
Hiya,
I have also tried using the .bat script, it leads to the same place. A phone that does not boot.
thanks in advance.
Can you boot into twrp, fastboot boot twrp.img? If you can try formatting, not wiping, the data partition. It also gives you the option to repairing some other partitions, I don't remember which ones. You could try that.
Sent from my [device_name] using XDA-Developers Legacy app
Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?
trickyDicky314 said:
Hi
I decided to try installing Lineage OS on a moto G5. I used this guide on the lineage OS website: https://wiki.lineageos.org/devices/cedric/install
That guide pointed me to the TWRP downloads page where I downloaded the latest version, which is currently:
twrp-3.5.2_9-0-cedric.img17.1M 2021-04-05 15:20:14 EDT
I downloaded this, renamed it to "twrp.img", put it in the same folder as my adb tools, then ran the command: "fastboot flash recovery twrp.img"
It gave me the following output in the command prompt:
"(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17536 KB) OKAY [ 0.562s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed"
I googled this and found a few people mentioning this problem on other devices, but couldn't find a solution. Out of curiosity, I downloaded an older version of TWRP which has a smaller file size. I managed to flash that recovery so I thought I had cracked the problem!.. but since I was using an older version of TWRP it meant that actually flashing the Lineage ROM didn't work. As I understand it, the latest Lineage Rom will only work with latest TWRP.
Does anyone know what the problem is?
I managed to do everything else fine, aka I unlocked the bootloader using code from Motorola website.
I will need to sort something out because in trying to fix this I followed a guide which had me wipe everything and now the phone has no OS at all!
Is this a problem with TWRP's file size being too big now for this old phone's recovery partition? Or am I just being stupid?
Click to expand...
Click to collapse
Note later 64bit twrp version for some reason exceed partition size. If you require a permanently installed TWRP use an old version.
To use the later versions of TWRP you need to boot to TWRP instead each time you want to use it.
Click to expand...
Click to collapse
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com
As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.
sd_shadow said:
see
[Official] [5th April 2021] TWRP 3.5.2_9-0 Moto G5 [Cedric] [32/64bit Roms]
Official TWRP For Moto G5 Cedric Post 1 - Instructions Post 2 - FAQs For full details and notes see Official TWRP for Cedric Site For TWRP news change logs etc see TWRP Official Site Instructions For non rooted and rooted phones...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for fast reply! I will try just booting new version and installing. I didn't realize that would work, I thought u needed TWRP permanently installed for it to work, (am not experienced with this stuff).
Thanks again!
TheFixItMan said:
As clearly stated on my twrp thread. To use newer versions you have to temp boot to twrp
Or use an older version if you want a permanently installed twrp
twrp-3.5.0_9-0 I think is the latest version you can flash rather than only being able to boot.
Click to expand...
Click to collapse
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.
trickyDicky314 said:
Thanks for the reply! I hadn't seen that thread. I will try flashing lineage with temp booted TWRP. I don't need it permanently installed, I just thought it was a requirement.
Click to expand...
Click to collapse
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.
sd_shadow said:
Most builds of Lineage Rom include the lineage recovery anyways.
So when you install the rom it will also install their recovery.
Click to expand...
Click to collapse
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
{
"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"
}
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
trickyDicky314 said:
I booted into TWRP and tried to install lineage 17.1 via adb sideload. It seemed to get stuck at 38%. I had a look through the instructions again on lineage website and noticed a warning " Before following these instructions please ensure that the device is on the latest Android 8.1 firmware."
Don't know how I missed that first time, but I wonder if that could be the problem as am sure the device was still on android v7. I did try to get OTA update before starting this, but it said everything was up to date, so I just assumed that official support in UK stopped at v7.
Should I try installing Lineage version 15.1, to get the right firmware? Then try installing lineage v17?
Sorry for my complete ignorance about how to do this
Click to expand...
Click to collapse
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to
sd_shadow said:
You want stock firmware, custom roms don't overwrite everything.
Depends on your software channel. if it's a UK model it should be on RETGB
There are at least 2 different UK models XT1676, and XT1675.
https://mirrors.lolinet.com/firmware/moto/cedric/official/RETGB/
To be sure you should check getvar all
Code:
fastboot getvar all
Easiest way to install stock is LMSA's Rescue
Just verify it's choosing the correct Model # and Software Channel
Spoiler: This is an example of what LMSA will look like, just a different device
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again
TheFixItMan said:
Download stock firmware from below link
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You want the latest retail version
Put phone into fastboot mode
These are the terminal commands
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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
Download rom zip
Download gapps (open gapps arm64 nano)
Download magisk (for root)
Flash/boot twrp
Go to wipe
Format data (option on the right)
Restart to recovery
Swipe to allow system modifications in twrp
Go to wipe - advanced wipe
Wipe system data cache
Install rom zip
Install gapps
Install magisk
Wipe delvik cache
Restart
Once booted you can encrypt phone via settings if you want to
Click to expand...
Click to collapse
Thanks so much! This worked, I am now in Lineage OS! Thanks for taking the time to help out a newb like me by writing out every step
trickyDicky314 said:
Thank you so much for the help. I installed this programme but it didn't work when I selected the model etc
I tried the longer method provided by the fixitman and it worked! I got lineage installed!
Thanks again
Click to expand...
Click to collapse
Yeah, just skip that, and go straight to the rescue option
Hello,
I have tested a lot of GSI roms, but I must be doing something wrong, because I have LOTS of problems:
My tablet has these specifications:
Allwinner A50 (Cortex A7 4 cores 1,2 GHz)
1 GB RAM
16 GB ROM
supporting legacy of project treble using vndk 27.0 (I don't know what it means)
seamless upgrades not supported
not using dynamic partitions
Existing partitions (I have this script to reset them all)
fastboot erase system
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash private private.img
fastboot flash misc misc.img
fastboot flash metadata metadata.img
fastboot flash media_data media_data.img
fastboot flash frp frp.img
fastboot flash env env.img
fastboot flash empty empty.img
fastboot flash dto dto.img
I always test roms for a-only arm 32, by the way...
- The systems reboot into bootloader, or hangs in the logos, or are or become slow as hell, or have other problems (see the attached file for all the details, please)...
Also, I have some doubts:
- Every time I have to reflash system.img original, and then reset to factory. Why is it necessary, if I also delete the system partition every time and flash with the -w option ?!
- I am also aware of always choosing a rom having a slightly less size than the original to avoid overlapping partitions.
- The roms are generic, so they must work ? It's not normal what is happening to me ?
Thanks in advance ! This is a little nightmare, really...
!!!!!!!!!!!!!!!!!!!!!!!!!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?