Database Users

ERROR: could not clear input pipe; result -536870163

Trying to use fastboot to get back to factory default and I get this on the first step "erase userdata"
david-ln-imac:~ David$ /Users/David/fastboot-mac devices
HT036P900126 fastboot
david-ln-imac:~ David$ /Users/David/fastboot-mac erase userdata
ERROR: could not clear input pipe; result -536870163< waiting for device >

ERROR: could not clear input pipe; result -536870163< waiting for device >
Just bringing this old post back to life as I've run into the exact same problem. My N1 only boots into the multi-coloured X and there is no option to go into recovery. I previously had this issue when trying to push a CM rom onto it and solved it by going back to stock. But this time this error appears when trying to push a stock rom onto the phone:
"ERROR: could not clear input pipe; result -536870163< waiting for device >
"
Can someone help, please? The whole string looks like this:
MSM:~ m$ cd desktop
MSM:desktop m$ cd fastboot
MSM:fastboot m$ ./fastboot-mac
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
MSM:fastboot m$ ./fastboot-mac devices
HT09GP801010 fastboot
MSM:fastboot m$ ./fastboot-mac update signed-passion-img-FRG83_0923.zip -w
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
ERROR: could not clear input pipe; result -536870163< waiting for device >

Can't boot into recovery - phone just restarts
Odd, after a few more attempts the N1 is now able to boot as normal. But I no longer have access to recovery. My Market keeps force closing and I therefore wanted to flash the market again, but every time I try to go into recovery the phone just reboots. I've tried:
- Flashing CWM 25.1.0 in RomManager and booting into recovery
- Manually booting into recovery by holding vol down and power button
- via Quickboot
I can see that CWM is on the SD card but can't seem to be able to boot into it. Any suggestions?

[Q] Fastboot?

Ive modified the android_winusb.inf to show the correct device ID 0FCE for windows 7 x64 installed it and thats gone fine.
Now trying devices gives me nothing reboot-bootloader gives me <waiting for device> cant make a decent boot.img backup to inject Root, anyone got any ideas how we can connect fastboot, the bootloader is unlocked but unconfirmed.
Until we can get a decent boot.img we cant really start the development.
fastboot.exe -i 0x0fce getvar version connects and displays fine.

are you starting your phone in bootloader mode?
power off
hold <search> + plug into usb
I was able to issue fastboot commands from there such as fastboot reboot. If your bootloader is unlocked you should be able to use any of the below commands. You can also modify the boot.img from the recovery image from the bundled software. And boot to it on sd without writing to nand.
I've been pretty busy or else I'd try it myself, I just played with it enough to unlock my bootloader myself and that's where I stopped. If you need some help let me know.
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
EDIT: if you are having issues with "fastboot devices" and you are entering bootloader correctly, you may need to restart your workstation

Yeah done all that im sure the bootloader is now unlocked it erased the blocks and reset my phone, ill boot into ubuntu and try it from there. Windows wont let me issue any commands
Sent from my R800i using XDA Premium App. the keyboard auto correct function is mental it changes all my words got to turn that off

waz000000 said:
Yeah done all that in sure the overloaded is now unlocked it erased the blocks and reset my phone, ill boot into ubuntu and try it from there. Windows wont let me issue any commands
Sent from my R800i using XDA Premium App
Click to expand...
Click to collapse
I tried downloading the "repair" image and it sees that we modified the bootloader and won't download the image and the only files on SE website is for the update software not the image which I think is kinda bullsh*t but whatever.
so... if someone that *HAS NOT* unlocked the bootloader can download and mirror the file it downloads, should 100+ mb somewhere on your computer possibly in your %temp% directory if you are on a windows based workstation

I had the same problem cant restore major over sight by sony if our software breaks any time soon....
We need the unmodified boot.img only problem is i have another play ones got to go back that one is fresh in the packet but with the bootloader locked we cant issue commands with fast boot. catch 22
Sent from my GT-P1000 using XDA Premium App

waz000000 said:
I had the same problem cant restore major over sight by sony if our software breaks any time soon....
We need the unmodified boot.img only problem is i have another play ones got to go back that one is fresh in the packet but with the bootloader locked we cant issue commands with fast boot. catch 22
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
also the /proc/mtd for the boot partition is hidden in case anyone suggests we just pull for a backup.
Another reason I won't be doing much tinkering untill someone can provide us with a recovery image (note not just /system dump)

Unable to unlock Nexus 6p with Windows PC

I'm trying to unlock my Nexus 6p but am unable to successful unlock it. Steps I have taken:
1) Turned on device and enabled developer options, unlock permissions, and usb debugging
2) Plugged phone into computer and granted permission to computer
3) Booted phone into fastboot and confirmed connection with commands fastboot devices and fastboot reboot-bootloader
4) After the steps above I type fastboot flashing unlock and get a string of options in the command window but nothing happens on the phone (see copy of text options that appear after typing fastboot flashing unlock)
I'm using ADB version 1.0.31 with Windows 10
Is there a newer version of ADB I need to be using? Any tips or ideas would be appreciated as I would like to unlock the bootloader before I set up my phone.
Thanks,
Rick
Android Debug Bridge version 1.0.31
C:\Users\RXXXX\Android_adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
C:\Users\RXXX\Android_adb>

Under Developer options did u enable the option that says, enable bootloader unlock?

Thanks for the response. Yes I did. In fact, I reset the phone and went back in and enabled developer options and allow unlocking again. I still can't get it to unlock the bootloader.

C5Longhorn said:
Thanks for the response. Yes I did. In fact, I reset the phone and went back in and enabled developer options and allow unlocking again. I still can't get it to unlock the bootloader.
Click to expand...
Click to collapse
I went to developer option and selected allow OEM unlocking. Then my fastboot command worked to unlock my bootloader. I know this is not new information but wanted to confirm to you that I did what you did and it worked

I don't know the version numbers but you have to make sure you are using the latest version of fastboot. If you aren't it won't work. When you open the SDK folder open the exe file, I forget exact name but something like SDKmanager.exe, although I know that isn't right. Make sure to update the platform-tools folder and the latest android version. It should work after that.
If not delete any Nexus toolkits you might have downloaded in the past and try again.
Sent from my Nexus 6P using Tapatalk

C5Longhorn said:
Thanks for the response. Yes I did. In fact, I reset the phone and went back in and enabled developer options and allow unlocking again. I still can't get it to unlock the bootloader.
Click to expand...
Click to collapse
Your issue is that your adb/fastboot is out of date and therefore doesn't recognise the "fastboot flashing unlock" command. How did you install it on your PC? If you didn't install it via the Android SDK that's what you need to do, it's the only way to ensure that you're fully up to date. See my guide for details:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Sent from my Nexus 6P

Thanks everyone, I will download the latest SDK.
Sent from my Nexus 7 using Tapatalk

latest adb version is 1.0.32

Just to close this out, it was indeed the version of ADB I was using. After updating, I was able to unlock quickly. Thanks again to everyone, and esp. Heisenberg.
Sent from my Nexus 7 using Tapatalk

Help !! please my phone crash and now fastboot appears

well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please

Frost817 said:
well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please
Click to expand...
Click to collapse
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me

Frost817 said:
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me
Click to expand...
Click to collapse
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I tried the method but just send me this
[LEFT]commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]

Frost817 said:
I tried the method but just send me this
[LEFT]commands:
update reflash device from update.zip
flashall flash boot + recovery + system
flash [ ] write a file to a flash partition
erase erase a flash partition
format format a flash partition
getvar display a bootloader variable
boot [ ] download and boot kernel
flash:raw boot [ ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s specify device serial number
or path to device port
-l with "devices", lists device paths
-p specify product name
-c override kernel commandline
-i specify a custom USB vendor id
-b specify a custom kernel base address. default: 0x10000000
-n specify the nand page size. default: 2048
-S [K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]
Click to expand...
Click to collapse
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?

Frost817 said:
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs

sd_shadow said:
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result

Frost817 said:
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result
Click to expand...
Click to collapse
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs

sd_shadow said:
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
well don't use the fb_mode_set but it keeps sending me Failure
failed flashing process 1/24 flash partition gpt.bin -> phone returned Fail
bootloader logs:
cmd: getvar- max sparce size
cmd: getvar- max download size
cmd: download 0000b600
cmd: flash: partition

after seeing your post I also believe my phone moto g5 XT1686 failed not able to start, the same issue I tried everything all tools and commands. In a final conclusion Buying Motorola devices is a waste of money.
feeling dishearted...

[GUIDE] Unbrick or restore to OOS using only fastboot

This guide will only work up to OOS 11.
This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with a fastboot capable of executing fastboot reboot fastbootd.
To start, download the appropriate Oxygen OS zip for your device from the OP8T repo thread. Extracting the zip file should give you a file named
payload.bin.
Use payload dumper to extract payload.bin.
You can grab payload_dumper from here (Windows and macOS), here (linux), or here (github, any OS).
For the download link from github, make sure you're running python 3.6 or higher. Run payload dumper with:
python payload_dumper.py payload.bin
The image files will be extracted to a folder named output.
Before starting the flashing process, you can check your device memory type using the DevCheck app by flar2 or with the command adb shell getprop ro.boot.ddr_type. The adb command will return 0 for LPDDR4X chips and 1 for LPDDR5 chips. This is important to flash the right xbl img files. LPDDR4X is more common for OP8T, so no worries if you miss this step.
You can start flashing from the standard bootloader or fastbootd. The first three lines below will flash the stock recovery then reboot into fastbootd.
Code:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash --slot=all recovery recovery.img
fastboot flash --slot=all boot boot.img
fastboot flash --slot=all dtbo dtbo.img
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
If your phone has the LPDDR4X memory chip (returned 0 with the adb shell command above), flash the images below:
Code:
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
LPDDR4X is the more common chip for OP8T, so if you forgot to check, you can flash this.
If your phone has the LPDDR5 chip (returned 1 with the adb shell command above), flash the images below:
Code:
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img
This next section will clear the super partition (contains odm, system, system_ext, vendor and product). It's not absolutely necessary, so you can skip to the next step. Clearing the super partition will help avoid the following error, which can come up if you had manually flashed ROMs on both slots previously.
Code:
Resizing '<partition name>' FAILED (remote: 'Not enough space to resize partition')
Example: Resizing 'product' FAILED (remote: 'Not enough space to resize partition')
If you've ever had this error or you just want to be sure that everything is cleared, check the spoiler.
Spoiler
Before deleting, you can check the names of the logical partitions on your phone using fastboot getvar all. Scroll up to the section that looks like this:
Code:
(bootloader) is-logical:odm_a:yes
(bootloader) is-logical:product_a:yes
(bootloader) is-logical:system_a:yes
(bootloader) is-logical:system_ext_a:yes
(bootloader) is-logical:vendor_a:yes
or
(bootloader) is-logical:odm_b:yes
(bootloader) is-logical:product_b:yes
(bootloader) is-logical:system_b:yes
(bootloader) is-logical:system_ext_b:yes
(bootloader) is-logical:vendor_b:yes
As @Matt85m pointed out, you may also have:
Code:
(bootloader) is-logical:odm:yes
(bootloader) is-logical:product:yes
(bootloader) is-logical:system:yes
(bootloader) is-logical:system_ext:yes
(bootloader) is-logical:vendor:yes
It is also possible to have logical partitions with the same names ending in -cow (system_a-cow, system_b-cow, system_ext_b-cow, vendor_a-cow, product_b-cow, etc).
These are created by various ROMs during an OTA. Shout out to @mslezak for the discovery.
Delete everything with the commands below:
Code:
fastboot delete-logical-partition odm
fastboot delete-logical-partition system
fastboot delete-logical-partition system_ext
fastboot delete-logical-partition product
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
Delete any -cow partitions with the same command:
Code:
fastboot delete-logical-partition system_a-cow
and so on.
If you get an error deleting the -cow partitions, @firegate22 suggests changing slots from the bootloader (fastboot --set-active=a or b) not from fastbootd, then return to fastbootd and try the delete command again.
All logical partitions can be deleted to free up space in the super partition.
Recreate partitions a and b with the commands below.
Code:
fastboot create-logical-partition odm_a 100000
fastboot create-logical-partition odm_b 100000
fastboot create-logical-partition system_a 100000
fastboot create-logical-partition system_b 100000
fastboot create-logical-partition system_ext_a 100000
fastboot create-logical-partition system_ext_b 100000
fastboot create-logical-partition product_a 100000
fastboot create-logical-partition product_b 100000
fastboot create-logical-partition vendor_a 100000
fastboot create-logical-partition vendor_b 100000
Flash the rest of the images.
Code:
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash product product.img
fastboot flash vendor vendor.img
fastboot flash --slot=all vbmeta vbmeta.img
fastboot flash --slot=all vbmeta_system vbmeta_system.img
Assuming everything flashes with no errors, return to recovery, do a factory reset and reboot.

I like what you're proposing. I've been thinking along these lines also.
Would you mind explaining why you're flashing to both slots rather than just the inactive one?
If you leave the current slot untouched you have a fallback position (the whole point of having A/B partitioning).
The same question applies to the flashing/deleting of the dynamic partitions in super.

BillGoss said:
I like what you're proposing. I've been thinking along these lines also.
Would you mind explaining why you're flashing to both slots rather than just the inactive one?
If you leave the current slot untouched you have a fallback position (the whole point of having A/B partitioning).
The same question applies to the flashing/deleting of the dynamic partitions in super.
Click to expand...
Click to collapse
For this guide specifically, the idea is to return as close to stock as possible. Wiping everything and replacing with OOS would be the best way to do that.
More generally, other than boot.img and recovery.img, the images flashed on both slots in the first part are the firmware files. You can grab and flash them from pretty much any new OOS version to update the firmware without affecting the installed ROMs. The specific files for the ROM are all in the third part. If you extract the payload.bin for any custom ROM, those are usually the only image files included.
You can certainly run two different firmware versions on the two slots, but if the inactive slots are empty or contain much older firmware, you can end up with weird issues in the active slots (usually a boot loop but could be more or less serious). Keeping the versions close is just to avoid unnecessary issues.
Some custom ROMs for OP8T like Lineage recommend or insist on flashing the copy-partitions.zip package for this reason. It's also why the install instructions for older A/B phones that have TWRP generally begin with "flash the stock ROM on both slots" - only the firmware files are strictly necessary, so you can keep the fallback ROM on the other slot if you want to.
That ended up much longer than planned. Hope it answers your questions though!

I'm going through this process rn, and I figured I'd ask here. How long does it usually take to flash dsp? It's been over 20 minutes of Sending 'dsp_a' (65536 KB)
65 M looks pretty big, and that's maybe the max size? How long did it take for you?
edit: seems to be unrelated to size as the modem part went fine, and that's bigger

No go, next step : fastboot reboot fastboot enter QDLoader mode

nero075 said:
I'm going through this process rn, and I figured I'd ask here. How long does it usually take to flash dsp? It's been over 20 minutes of Sending 'dsp_a' (65536 KB)
65 M looks pretty big, and that's maybe the max size? How long did it take for you?
edit: seems to be unrelated to size as the modem part went fine, and that's bigger
Click to expand...
Click to collapse
Did you figure this out? Flashing dsp should only take a couple seconds.

coomac said:
Did you figure this out? Flashing dsp should only take a couple seconds.
Click to expand...
Click to collapse
I ended up just skipping that one, and it turned out fine ¯\_(ツ)_/¯

Full time Linux user here, glad to see this guide after few days looking for a way to go back to stock without Msmtool.
However I do have some question, is it possible to have a OTA update from Oneplus if I go back to stock using this method and re-lock my bootloader?

mrhieu059 said:
Full time Linux user here, glad to see this guide after few days looking for a way to go back to stock without Msmtool.
However I do have some question, is it possible to have a OTA update from Oneplus if I go back to stock using this method and re-lock my bootloader?
Click to expand...
Click to collapse
Shouldn't be a problem. I was able to install an OTA update after returning to stock using this method with no issues even without relocking my bootloader.

thanks for this helped me alot to restore my device, i have one question though i checked all the commands and i see there might be one command missing, when i extracted the rom i checked all the img files and saw :
xbl_lp5.img
xbl_config_lp5.img
cant help wonder if i have to input the commands as well

rdlr19 said:
thanks for this helped me alot to restore my device, i have one question though i checked all the commands and i see there might be one command missing, when i extracted the rom i checked all the img files and saw :
xbl_lp5.img
xbl_config_lp5.img
cant help wonder if i have to input the commands as well
Click to expand...
Click to collapse
Glad it helped. Those files depend on whether your device has a DDR type 0 (LPDDR4X) or DDR type 1 (LPDDR5) memory chip.
You can check your device memory type with adb shell getprop ro.boot.ddr_type. It will return 0 or 1. You can also use the DevCheck app by flar2.
I believe most OP8Ts use DDR0, which requires xbl_config.img and xbl.img. The lp5 images are for DDR1.
According to the lineage OS wiki, you'd flash the lp5 images with the same commands on DDR1:
Code:
fastboot flash --slot=all xbl_config xbl_config_lp5.img
fastboot flash --slot=all xbl xbl_lp5.img

I've tried to bring my KB2003 back to stock from LineageOS using this guide and when it comes to flashing the odm, product and vendor files I get the following errors
Code:
Sending 'odm' (34544 KB) OKAY [ 0.849s]
Writing 'odm' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'product_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'vendor_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've cleared the logical partitions. any ideas? Ignoring these errors and the device doesnt boot, just get a black screen
edit: if I do these product and vendor files first, system throws the error. Are the posted logical partition sizes correct?

Matt85m said:
I've tried to bring my KB2003 back to stock from LineageOS using this guide and when it comes to flashing the odm, product and vendor files I get the following errors
Code:
Sending 'odm' (34544 KB) OKAY [ 0.849s]
Writing 'odm' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'product_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'vendor_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
I've cleared the logical partitions. any ideas? Ignoring these errors and the device doesnt boot, just get a black screen
edit: if I do these product and vendor files first, system throws the error. Are the posted logical partition sizes correct?
Click to expand...
Click to collapse
You need to clear more space in the super partition. You can basically delete and recreate both slots a and b for system, system_ext, product, vendor, and probably even odm to get more space.

coomac said:
You need to clear more space in the super partition. You can basically delete and recreate both slots a and b for system, system_ext, product, vendor, and probably even odm to get more space.
Click to expand...
Click to collapse
is't that was the
Code:
fastboot delete-logical-partition
fastboot create-logical-partition
commands were about? I've followed that step as you laid out. I've now tried it by adding a line for deleting and recreating the odm partition and still no joy

Matt85m said:
is't that was the
Code:
fastboot delete-logical-partition
fastboot create-logical-partition
commands were about? I've followed that step as you laid out. I've now tried it by adding a line for deleting and recreating the odm partition and still no joy
Click to expand...
Click to collapse
Yeah, that's what they're for. Strange. Any other errors before the one for odm? Would be helpful if you can upload a screenshot of your terminal with all the commands.
Edit: One suggestion is to make sure you're in fastbootd, not fastboot. Also, the size for the new logical partitions is arbitrary - they get resized when being flashed.

coomac said:
Yeah, that's what they're for. Strange. Any other errors before the one for odm? Would be helpful if you can upload a screenshot of your terminal with all the commands.
Edit: One suggestion is to make sure you're in fastbootd, not fastboot. Also, the size for the new logical partitions is arbitrary - they get resized when being flashed.
Click to expand...
Click to collapse
it definitely is in fastbootd, I ran into that issue initially as the android-tools package shipped with Fedora was out of date, I dumped the newer tools from google into my /usr/bin.
Here is a dump of my last step by step attempt text file

OK, couple things you can try.
- Switch to slot a and try flashing again.
- If that doesn't work, flash the copy-partitions zip from the lineage wiki then try again.
Btw you can check the size of the super partition using fastboot getvar partition-size:super (you'll have to convert the hex value to decimal). It should be around 7.5 gb. Use fastboot getvar all to get the sizes of all the logical partitions. The total should be between ~3.3 and 4 gb after flashing or about 500 mb after you delete/recreate them.

Matt85m said:
it definitely is in fastbootd, I ran into that issue initially as the android-tools package shipped with Fedora was out of date, I dumped the newer tools from google into my /usr/bin.
Here is a dump of my last step by step attempt text file
Click to expand...
Click to collapse
Responded above.

coomac said:
Responded above.
Click to expand...
Click to collapse
worked it out looking at the entire list of partitions - I had 3 lots of each rom partion for example system_a, system_b and system, for all vendor product etc. purging the ones without the _a/b allowed the process to complete.
Might be a quirk of lineageOS installation process - you might want to make a note of it on the OP incase someone else runs into it

Matt85m said:
worked it out looking at the entire list of partitions - I had 3 lots of each rom partion for example system_a, system_b and system, for all vendor product etc. purging the ones without the _a/b allowed the process to complete.
Might be a quirk of lineageOS installation process - you might want to make a note of it on the OP incase someone else runs into it
Click to expand...
Click to collapse
Good to know. I'll update the OP.