Develop Bugs

How to go from Lineage OS 14.1 to stock? (Updated with the process & latest links)

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'$

Moto G5 install ota by zip on rooted phone (Can I just install ota zips with twrp?)

Hello, I'm a Motorola Moto G5 owner and I rooted my device some time ago.
Now i found out there is an official motorola update which brings our moto g5 from nougat to oreo. I'd want to update my phone but I have the little problem I cannot update my phone using the regular "System Updates" section in settings because I have a custom recovery and every time I try to update the phone just boots in twrp and to use it I must restart in bootloader and then press on start.
I've found online some official ota updates zips so my question is: Can I just install these zips with the install zip twrp function instead of reflashing stock firmware just to install a few updates? Is there another more simple way to update this damn phone? (I have Magisk 1.19, I'm on build NPPS25.137-93-8 and I'd want to get to the latest one)
(Oh yeh, srry for bad english but it isn't my mother language)

OnionMaster03 said:
Hello, I'm a Motorola Moto G5 owner and I rooted my device some time ago.
Now i found out there is an official motorola update which brings our moto g5 from nougat to oreo. I'd want to update my phone but I have the little problem I cannot update my phone using the regular "System Updates" section in settings because I have a custom recovery and every time I try to update the phone just boots in twrp and to use it I must restart in bootloader and then press on start.
I've found online some official ota updates zips so my question is: Can I just install these zips with the install zip twrp function instead of reflashing stock firmware just to install a few updates? Is there another more simple way to update this damn phone? (I have Magisk 1.19, I'm on build NPPS25.137-93-8 and I'd want to get to the latest one)
(Oh yeh, srry for bad english but it isn't my mother language)
Click to expand...
Click to collapse
No you cannot
Firmware OTA zips can only be installed on a totally unmodified stock system image
You will need to flash the stock firmware via fastboot and I recommend to lock the bootloader to ensure that the firmware is totally unmodified before doing any ota updates else you risk hard bricking the device
Firmware can be found
https://mirrors.lolinet.com/firmware/moto/cedric/official/

TheFixItMan said:
No you cannot
Firmware OTA zips can only be installed on a totally unmodified stock system image
You will need to flash the stock firmware via fastboot and I recommend to lock the bootloader to ensure that the firmware is totally unmodified before doing any ota updates else you risk hard bricking the device
Firmware can be found
Click to expand...
Click to collapse
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Oh well, I just noticed the firmwares you sent me are already on Oreo 8.1.0, Could I just install one of them and then reroot the phone?

OnionMaster03 said:
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Click to expand...
Click to collapse
Use the Oreo TWRP flashable zip for Moto G5 https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913.

Andrej_SK said:
Use the Oreo TWRP flashable zip for Moto G5 https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913.
Click to expand...
Click to collapse
Really thank you!

OnionMaster03 said:
Ok well, how to lock bootloader (Right now I have unlocked bootloader)? How to reunlock it after (Do I just need the same guide to unlock as the first time?)? But most important, how to install the stock image by fastboot? (What's the exact command?)
Oh well, I just noticed the firmwares you sent me are already on Oreo 8.1.0, Could I just install one of them and then reroot the phone?
Click to expand...
Click to collapse
Yes you can flash the latest firmware for your device and root with magisk
Google is always your friend for how tos
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
You can stop here if you intend to root etc or carry on if you want to relock the bootloader
Relock bootloader (note if you do this you won't be able to flash twrp or root etc)
Code:
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
Device will restart
Now flash the entire firmware again (first list)
Note unless you have all the unlock keys you may not be able to unlock it again

I guess i bricked my only phone....:-/

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.

[ROM] [10] OmniRom for OnePlus7T Pro [EXPERT]

CLOSED PER OP REQUEST
{
"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"
}
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2020-01-08

first

Wahoo. Thanks for this.

Oooo nice ?

new build is up
fingerprint should be fine now
10.0x whatever is the latest release blobs.
other little stuff
and whats below:

darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-19
Click to expand...
Click to collapse
download error!

Thx. How to root??

Just_Pisces said:
Thx. How to root??
Click to expand...
Click to collapse
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.

p70shooter said:
Mate if you can't find out how to root I really don't think you should be flashing this. Look thro the forum the answer is there.
Click to expand...
Click to collapse
Thx. Just forgot to check“Preserve AVB 2.0/dm-verity”. Now Successfully

Hello to all ..... Unfortunately, the download link is not up to date or the destination host is not available ... could someone please upload the ZIP or create a new link to download? many thanks

its back online

darkobas said:
Download unoficial:
DOWNLOAD Unofficial
Kernel source:
Source
Selinux Status:
Enforcing
Safetynet Status:
PASS (didnt test, should pass)
MAJOR BUGS:
huh ?
Minor bugs:
?
flash on your own risk.
FLASHING
This is for experianced people only, because theres no working TWRP yet. If you dont know how to read stop here (funny eh ?). Also if you dont wanna follow steps bellow because u know better. Goodbye. I dont wanna listen to you cry here. I will not help you.
opposite of what happens if you flash in twrp, this procedure will flash to the slot whis is active now. if you know what u r doing u can flash to any slot u like.
Despite the red text theres really no big danger here if you follow the steps. I just wana scare away newbs.
BU!
android 10 shipped devices have fastboot like we know it and its pretty much useless. and they have the new fastbootd (google it). Make sure u download the latest fastboot from google.
1st. get into fastbootd.
option a) from old fastboot, type: fastboot reboot fastboot (funny eh ?) another google miracle to not name it fastbootd.
option b) if you have a running os with adb: adb reboot fastboot
this will bring you to OOS chinese recovery look a like, but its fastboot. to test that u r in the right place try a fastboot command. fastboot getvar all for example.
2nd. flash
unzip ROM.
option a) if you are on linux
fastboot -w //this will wipe all your data. you need to do this only on first install, not on updates.
sh ./fastboot_flash.sh
option b)
again! fastboot -w // will wipe all your data and is needed only on first flash
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash dtbo dtbo.img
fastboot reboot
3rd. enjoy opensource
unfortunately because of the flashing procedure I have included gapps. when twrp exists they will be gone.
Updating: (WILL WORK ONCE OFFICIAL)
Use OTA inside rom for updates
if u did something else. we dont need/wanna know about it in the thread
May the force be with you
Device Maintainers
@vache,
@maxwen
XDA:DevDB Information
OmniRom, ROM for the OnePlus 7T Pro
Contributors
darkobas, maxwen
Source Code: https://github.com/omnirom/android_kernel_oneplus_sm8150/tree/android-10
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: 10
Version Information
Status: Beta
Created 2019-11-14
Last Updated 2019-11-22
Click to expand...
Click to collapse
Hi for some reason it didn't work for me
Wipe successful could not partition
Error message Failed remote not discoverable when flashing images.
I'm paraphrasing I accidentally closed the command prompt after rebooting.

It clearly says its only for people that can read and follow instructions.

Hm, I can't write system neither to 'a' or 'b' slot ... boot image is looking ok.
What I am doing wrong?
I am on latest 10.0.4.
Code:
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_a' (98304 KB) OKAY [ 2.309s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.651s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.412s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.039s]
Finished. Total time: 0.047s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash boot boot.img
Sending 'boot_b' (98304 KB) OKAY [ 2.317s]
Writing 'boot_b' OKAY [ 0.410s]
Finished. Total time: 2.753s
PS C:\op7t\omni-10-20191201-oneplus7tpro-IMG> fastboot flash system system.img
Sending sparse 'system' 1/2 (786428 KB) OKAY [ 18.450s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
EDIT:
Not sure if it helps but this is what I get from "fastboot getvar all"
Code:
(bootloader) has-slot:system:no
Also tried it from 10.0.3 base to check if it's bootloader issue with no change.
EDIT2:
Oh well, I am an idiot who can't read instructions properly and didn't realize there are two fastboots
You need to reboot to fastbootd from fastboot !!
I will leave this here for people like me.

@darkobas thanks for the amazing rom!!! it works flawlesly

guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks

darkoj2007 said:
guys does anyone know if any other kernel work with this rom? I have issues with usb dac which I connect with usb type c to female usb, it`s otg cable but when I connect it somehowpower from the kernel is not enough to power it. Had same issue on stock oos until I flashed ElementalX but this kernel throw the phone is bootloop. Probably someone more experienced have info how to fix this? Thanks
Click to expand...
Click to collapse
Find the kernel patch then we can continue to talk

maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
Can we talk about Wireguard?

maxwen said:
Find the kernel patch then we can continue to talk
Click to expand...
Click to collapse
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?

houmles said:
Can we talk about Wireguard?
Click to expand...
Click to collapse
No - somr things never change
---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------
darkoj2007 said:
interesting thing is I flashed other kernels and get them to work but none of them actually does the job. returned to stock oos also I can`t get it working tried same combo on wife`s samsung phone all works as it should. I have Dragonfly dac whic i connect with usb type c to female usb, the dac has incorporated mechanism to change colour dependant from what khz comes to him. but when I connect it to a phone shows colour like 96khz which is maximum and when I start playing music goes to blue which is equal to 44.1 khz which is android native. anyone can provide solution for connecting properly with otg?
Click to expand...
Click to collapse
BORING!!!

How To Guide GPU Drivers from Qualcomm - How to update

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?