[ROM][11][OnePlus8T] PixelExperience [AOSP]

Search This thread

cesar.mk4

Senior Member
Jun 25, 2013
89
29
Hi all,

Coming from 2021/01/20 build, I was able to ADB sideload successfully to 2021/02/05 build. It booted anyways...
BUT... cmd line ended in " (-47%) adb: failed to read command: No error"...I proceeded to reboot.
It was listing the update as current build, but WiFi took a dump. I did not factory reset. Possibly the issue? I was trying to avoid setting up the phone from scratch again.
I also noticed that recovery was working on slot a when previously it was on b.
I tried fastboot update <filename> - no dice as well.
Anyways, just completed a clean install (used payload this time) and it works.
Simply booted into bootloader and proceeded with the following commands:

fastboot -w
fastboot flash recovery
fastboot reboot fastboot
fastboot flash boot
fastboot flash dtbo
fastboot --disable-verity flash vbmeta
fastboot --disable-verity flash vbmeta_system
fastboot flash system
fastboot flash system_ext
fastboot flash product
fastboot flash odm
fastboot flash vendor
fastboot reboot

Kinda just ranting at this point throwing things out here to see if we can find a solution to a seamlessly install future updates without wiping devices clean.
 
  • Like
Reactions: MattJaO3D

cesar.mk4

Senior Member
Jun 25, 2013
89
29
Hi all,

Coming from 2021/01/20 build, I was able to ADB sideload successfully to 2021/02/05 build. It booted anyways...
BUT... cmd line ended in " (-47%) adb: failed to read command: No error"...I proceeded to reboot.
It was listing the update as current build, but WiFi took a dump. I did not factory reset. Possibly the issue? I was trying to avoid setting up the phone from scratch again.
I also noticed that recovery was working on slot a when previously it was on b.
I tried fastboot update <filename> - no dice as well.
Anyways, just completed a clean install (used payload this time) and it works.
Simply booted into bootloader and proceeded with the following commands:

fastboot -w
fastboot flash recovery
fastboot reboot fastboot
fastboot flash boot
fastboot flash dtbo
fastboot --disable-verity flash vbmeta
fastboot --disable-verity flash vbmeta_system
fastboot flash system
fastboot flash system_ext
fastboot flash product
fastboot flash odm
fastboot flash vendor
fastboot reboot

Kinda just ranting at this point throwing things out here to see if we can find a solution to a seamlessly install future updates without wiping devices clean.

"Edit" WiFi breaks after some time. A reboot fixes until it breaks again.
 

Raza Qadri

Senior Member
Jul 31, 2012
1,172
435
is this Rom not compatible with Chinese variant of 8T KB2000 ? whenever i try to install the rom using adb sideload i get error code : 7 , if i remember correctly you use to get this error if you were applying non compatible rom?
 

yexlin

Member
Oct 21, 2016
38
1
how it this rom? have 90hz option?fingerprint is Woking? 8t model kb2000 can flash or not?
 

alanzaki073

Senior Member
Mar 3, 2011
117
58
Hyderabad
iQOO 9
OnePlus 11
yes i have done that also, still no luck for me
MSM to the latest one available and try to get OOS on both slots (use incremental update then full OTA local update), unlock BL, get into bootloader then follow these commands once you have extracted the files from payload dumper (make sure you use the latest adb tools and the payload dumper files are in the same folder as your adb files are)

fastboot -w
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash odm odm.img
fastboot flash vendor vendor.img
fastboot reboot
 

MattJaO3D

Senior Member
Oct 26, 2012
721
181
Cardiff
Samsung Galaxy S10+
I will try your exact steps tomorrow, i have trying to flash coming from Crdroid , it's just seems a bit long winded , is there any way to make a script like Crdroid has , for the uneducated? Like me lol

i decided to use the USB C port , ran your commands , and it dirty flashed over crdroid , and all is working ok, i will factory reset and have a fresh to be on the safe side, and WIFI is working .
 
Last edited:

Raza Qadri

Senior Member
Jul 31, 2012
1,172
435
MSM to the latest one available and try to get OOS on both slots (use incremental update then full OTA local update), unlock BL, get into bootloader then follow these commands once you have extracted the files from payload dumper (make sure you use the latest adb tools and the payload dumper files are in the same folder as your adb files are)

fastboot -w
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash odm odm.img
fastboot flash vendor vendor.img
fastboot reboot
Does using copy partition.zip from pixel experience do the same ? Or should I specifically use incremental update than full update ?
 

MattJaO3D

Senior Member
Oct 26, 2012
721
181
Cardiff
Samsung Galaxy S10+
Does using copy partition.zip from pixel experience do the same ? Or should I specifically use incremental update than full update ?
I flashed it , as I followed the pixel instructions at 1st , had no luck, so I gave up and flashed crdroid , next day then flashed this using the above commands in the payload output folder , and wola it now weirdly works great :)
 

Raza Qadri

Senior Member
Jul 31, 2012
1,172
435
MSM to the latest one available and try to get OOS on both slots (use incremental update then full OTA local update), unlock BL, get into bootloader then follow these commands once you have extracted the files from payload dumper (make sure you use the latest adb tools and the payload dumper files are in the same folder as your adb files are)

fastboot -w
fastboot flash recovery recovery.img
fastboot reboot fastboot
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash odm odm.img
fastboot flash vendor vendor.img
fastboot reboot
wow thanks this actually worked !
 

abalam

Senior Member
Oct 30, 2011
2,497
2,295
github.com
OnePlus 10 Pro
Hi all,

Coming from 2021/01/20 build, I was able to ADB sideload successfully to 2021/02/05 build. It booted anyways...
BUT... cmd line ended in " (-47%) adb: failed to read command: No error"...I proceeded to reboot.
It was listing the update as current build, but WiFi took a dump. I did not factory reset. Possibly the issue? I was trying to avoid setting up the phone from scratch again.
I also noticed that recovery was working on slot a when previously it was on b.
I tried fastboot update <filename> - no dice as well.
Anyways, just completed a clean install (used payload this time) and it works.
Simply booted into bootloader and proceeded with the following commands:

fastboot -w
fastboot flash recovery
fastboot reboot fastboot
fastboot flash boot
fastboot flash dtbo
fastboot --disable-verity flash vbmeta
fastboot --disable-verity flash vbmeta_system
fastboot flash system
fastboot flash system_ext
fastboot flash product
fastboot flash odm
fastboot flash vendor
fastboot reboot

Kinda just ranting at this point throwing things out here to see if we can find a solution to a seamlessly install future updates without wiping devices clean.
Why --disable-verity flash vbmeta_system and not just flash vbmeta_system? Just a question. This is because when I flash product.img I get a message of not enough space in partition
 

Attachments

  • IMG_20210213_222134_229_1.jpg
    IMG_20210213_222134_229_1.jpg
    12.5 KB · Views: 83

Dior DNA

Senior Member
Aug 17, 2015
1,631
695
Why --disable-verity flash vbmeta_system and not just flash vbmeta_system? Just a question. This is because when I flash product.img I get a message of not enough space in partition
Slightly off topic from your question, I sometimes wonder if it is better or recommended now to flash from fastbootd (as compared to from bootloader). Because:
seems to indicate fastbootd is partition (re)size aware...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 48

    NFjZzFl.png

    PixelExperience for OnePlus8T[kebab]

    What is this?
    PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)

    Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

    Based on Android 11



    Whats working?
    Wi-Fi
    RIL
    Mobile data
    GPS
    Camera
    Flashlight
    Camcorder
    Bluetooth
    FM radio
    Fingerprint reader
    Face unlock
    NFC
    Lights
    Sound/vibration


    Known issues
    Nothing yet
    You tell me

    DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
    Download from PixelExperience website


    Donate
    [*]UPI-ID:- hasaber@icici
    [*]Paypal:- paypal.me/KakatkarAkshay


    14
    New instructions to flash - NOOB Friendly:


    1. Download the latest build
    2. Download the latest platform tools, if you haven't already: https://developer.android.com/studio/releases/platform-tools
    3. Extract the adb and fastboot drivers zip and add that folder to path (if you don't know how to add a path, google it)
    4. Enable USB debugging via developer options on your phone and after that connect your phone via USB to PC
    5. Extract only the recovery.img file from the ROM zip
    6. Open a command prompt window where the extracted recovery.img is present, and enter the following one by one:

    Code:
    adb reboot bootloader
    fastboot boot recovery.img

    7.From the phone's recovery page, do the following:

    Factory reset -> Format data/factory reset -> Format data.

    8. Go back to recovery page from clicking back.

    9. Select "Apply Update -> Apply from ADB"

    10. From the command window already opened, sideload the rom using:
    Code:
    adb sideload <ROM>.zip
    (Replace <ROM> with actual ROM file name)

    11. If you want to root, after first boot, reboot to recovery again, select "Apply Update -> Apply from ADB"

    12. Connect your phone to PC, open a command prompt window where Magisk zip is located, execute:
    Code:
    adb sideload <MagiskFileName>.zip
    (Replace <MagiskFileName> with actual file name)


    For updating, open a command prompt window where the new ROM zip is present, execute:
    Code:
    fastboot reboot recovery
    , then follow steps 9-12.

    Old instructions:

    @GDZechariah @Moffei97 @firdoshakir @matteosaeed @manhong2112

    The zip is flashable, but without the twrp, you can't flash that way.

    Instructions to flash (noob friendly):

    YOUR BOOTLOADER SHOULD BE UNLOCKED

    1. Flash OOS 11 on both slots (Use local upgrade option/flash via fastbootd).

    2. Check using this app if u have OOS on slot_b:-
    https://play.google.com/store/apps/details?id=flar2.devcheck

    1-2. (ALTERNATE WAY) - Flash OOS to slot_b via fastbootd and set the active partition as slot_b.

    3. Download the latest Pixel experience ROM.

    4. Download and install Python3 on your PC (TICK THE ADD PYTHON TO PATH OPTION):-
    https://www.python.org/downloads/

    5. Download payload dumper and extract its zip:-
    https://androidfilehost.com/?fid=818070582850510260

    6. The Pixel Experience ROM should be on ur PC.

    7. Now extract the Pixel Experience ROM.

    8. Put the "payload.bin" file from the extracted ROM file to payload dumper/payload_input

    9. Run payload dumper.exe

    10. Wait for all files to be extracted.

    11. Now install adb and fastboot drivers (Skip to step 13, if you already have it):-
    https://developer.android.com/studio/releases/platform-tools

    12. Extract the adb and fastboot drivers zip and add that folder to path (if you don't know how to add a path, google it).

    13. Enable USB debugging via developer options on your phone and after that connect your phone via USB to PC.

    14. Now go to payload dumper/ payload_output folder and open a command window there.

    15. On the command window, type the following commands one by one:

    Code:
    adb reboot bootloader
    fastboot -w
    fastboot flash recovery recovery.img
    fastboot reboot fastboot
    fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    fastboot --disable-verity flash vbmeta vbmeta.img
    fastboot --disable-verity flash vbmeta_system vbmeta_system.img
    fastboot flash system system.img
    fastboot flash system_ext system_ext.img
    fastboot flash product product.img
    fastboot flash odm odm.img
    fastboot flash vendor vendor.img
    fastboot reboot

    16. Done! Enjoy Pixel experience ROM

    For updating subsequent builds of Pixel Experience ROM, download the latest build, follow steps 7-10, 14-15. But in step 15, skip the "fastboot -w" command.

    Alternate Platform Generic payload dumper: https://github.com/theincognito-inc/payload_extractor.git
    12
    New Official Build up

    Changelog:

    - December security patch
    - Added Alert slider customization
    - Added OOS White fod icon
    - Updated Gcam
    - Fixed slow charge message on lock screen
    - Fixed Screen off ok google
    - Fixed screen color issues
    - Added DC Dim
    6
    Just wanted to take a moment to give a shout out to chandra1.jd what a great guy and friend to bounce ideas off of. Normally devs are alone in their work, but this guy is just awesome.
    5
    Flashed. Working fine. Fingerprint is working, included Gcam works well.