Database Develop

[help] ADB sideload 'cannot read' while installing stock ROM

Hey guys I have the OnePlus 3T A3010 (Chinese Version) trying to install OxygenOS v3.5.3 (i know it's not the latest) from "downloads.oneplus .net"
I have:
- Windows 10 x64
- Installed 15 seconds ADB Installer v1.4.3
- Rebooted PC
- Enabled developers option on mobile
- Enabled USB Debugging on mobile
- Verified MD5 hash of zip file for "OnePlus3TOxygen_28_OTA_027_all_1611222319_884473ff95304c30.zip"0e2b4f9c7e7a1edf533f0d436ba48d95 (file is not corrupted, have re-downloaded and tested as well)
- Tried Administrative privilege (run as Admin) for CMD
- Tried renaming the .zip file
- Tried another PC that has Android SDK instead of "15 seconds ADB Installer v1.4.3" still no luck same error
- I go to recovery mode by holding vol+down and power
- Selected "Install from ADB" and "Ok"
- Plug the USB cable
- I can see the device while prompting "adb devices"
But i receive this error:
Code:
adb sideload OnePlus3TOxygen_28_OTA_027_all_1611222319_884473ff95304c30.zip
loading: 'OnePlus3TOxygen_28_OTA_027_all_1611222319_884473ff95304c30.zip'
* cannot read 'OnePlus3TOxygen_28_OTA_027_all_1611222319_884473ff95304c30.zip' *
I'm wondering do I need OxygenOS for A3010 model ? Are they separate for US and Chinese ? Is that why it's not loading?

Try minimal adb 1.30, and yeah rename that zip to something shorter. The A3010 doesn't require a special ROM, it can be sideloaded to all OnePlus 3T variants.
Use a different cable if you have one too.

r.spanish said:
Try minimal adb 1.30, and yeah rename that zip to something shorter. The A3010 doesn't require a special ROM, it can be sideloaded to all OnePlus 3T variants.
Use a different cable if you have one too.
Click to expand...
Click to collapse
I've tried them already.
I've got it working. I've just copied the file into the internal storage of the phone and used the local file to flash the ROM instead of using ADB.

Hello, same issue. Someone has solved? I cannot flash stock rom, neither via adb nor within stock recovery (no way to go to internal storage)
Thx

No OS Installed VTR-L29, EMUI 9.0 (Can't download stock)

I have the VTR-L29C605E2R1P8B119-log (9.0.1.119), EMUI 9 (android pie) of the P10 and I accidentally deleted my system, with only fastboot and twrp working. My EMUI erecovery is broken since there is no official global PIE update for the P10 (except the chinese) It will say "Failed to get package info"
I need help on how to fix this because I have tried downgrading and no avail.
Tried using funkyhuawei well, i'm getting "Failed to get package info" and i can assure you that the dns was working, and my oem isn't damaged.
Tried using DC-Pheonix but then it says phone not supported.
What a waste of 30$ but it's better than wasting 200$ for a new motherboard.
Tried using the Dload method. Software Install Failed (using the same rom)
Tried doing the HWOTA but it won't write to my recovery because it's set to "Recovery" not "recovery_ramdisk" I tried changing it's script to recovery_ramdisk, but when I tried to boot up to twrp and it gave me func 11 and 2 errors.
Tried flashing the images... Well, I couldn't flash system because of the "cannot load system.img" file.
Tried using oreo images, failed.
Tried using the Multi-Tool for huawei, well i thought it worked but it didn't because it flashed the system and everything else (the program doesn't know that the ramdisk is inside system) it gave me the error #1 at the end. Still didn't boot.
Tried flashing AOSP Roms and I bam it didn't work.
Do you guys have anymore solutions?

Did you try this?

Jannomag said:
Did you try this?
Click to expand...
Click to collapse
I did. But without adb working, I can't get it to work since it will look for devices/emulators which needed adb and it seems like my phone isn't responding to those.

If you flash the twrp image from the archive of the post I linked before, does it boot up and is adb then available?

Jannomag said:
If you flash the twrp image from the archive of the post I linked before, does it boot up and is adb then available?
Click to expand...
Click to collapse
Nope. It does not detect the adb.

Can you try this TWRP please, eventhough it's for Oreo.
If this isn't gonna work do something for me:
- Boot into your working TWRP and open the terminal (under Advanced).
- Type: "ls /dev/block/platform"
- You should get something like "FF3B0000.UFS" or other, please post in the next reply.
- Now type "ls /dev/block/platform/RESULT/by-name" - for RESULT enter the output of the first command.
- Please post the recovery and erecovery lines from the output in your reply.
With this output I should be able to write a small script, but I can't guarantee that this will work.
EDIT: I made a script based on my UFS device. Please do the commands above first.
If it shows "ff3b0000.ufs", then proceed with my script:
- create a new directory on your sdcard (it has to be sd, not internal!) called "downgrade" (without qoutes).
- Download my zip package and put it into /sdcard/downgrade
- Download your desired firmware - it has to be the same region C605! (Links for B374: update.zip, update_full_VTR-L29_hw_la.zip, update_data_full_public.zip)
- put all three zip files into /sdcard/downgrade and rename "update_full_VTR-L29_hw_la.zip" to "update_hw.zip".
- Boot into TWRP, tap in Install and navigate to the sdcard/downgrade directory.
- Install downgrade.zip. If there's any output, post it here.
The device will reboot itselfs and should start into Huawei's recovery, which should install the firmware.
Download my script here.

Jannomag said:
Can you try this TWRP please, eventhough it's for Oreo.
If this isn't gonna work do something for me:
- Boot into your working TWRP and open the terminal (under Advanced).
- Type: "ls /dev/block/platform"
- You should get something like "FF3B0000.UFS" or other, please post in the next reply.
- Now type "ls /dev/block/platform/RESULT/by-name" - for RESULT enter the output of the first command.
- Please post the recovery and erecovery lines from the output in your reply.
With this output I should be able to write a small script, but I can't guarantee that this will work.
EDIT: I made a script based on my UFS device. Please do the commands above first.
If it shows "ff3b0000.ufs", then proceed with my script:
- create a new directory on your sdcard (it has to be sd, not internal!) called "downgrade" (without qoutes).
- Download my zip package and put it into /sdcard/downgrade
- Download your desired firmware - it has to be the same region C605! (Links for B374: update.zip, update_full_VTR-L29_hw_la.zip, update_data_full_public.zip)
- put all three zip files into /sdcard/downgrade and rename "update_full_VTR-L29_hw_la.zip" to "update_hw.zip".
- Boot into TWRP, tap in Install and navigate to the sdcard/downgrade directory.
- Install downgrade.zip. If there's any output, post it here.
The device will reboot itselfs and should start into Huawei's recovery, which should install the firmware.
Download my script here.
Click to expand...
Click to collapse
Thanks for trying to help me, but I think this would work. I tried the ls /dev/block/platform command but it gave me the "sh ls /dev/block/platform: not found. " Is my device unrecoverable now? I tried to flash but gave me the error: 255 Maybe a backup twrp of kernel,cust,oeminfo,product,recovery,system,sys img, vendor, vendor img, version would work if i use the restore button in twrp but I don't have any backups because I forgot to. If you have any it might work I think?

[Solved]
Thanks for your help, I did a bit of changes though to your script.
Instead of of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
I changed it to: of=/dev/block/sdd37
It installed the update well.

This explained that the other tools like HWOTA8 didn't work. sdd37 is only on eMMC device which are rare. I forgot that the eMMC devices have a different path tree under /dev than UFS devices.
I'm glad that this works now.
The script is based on HWOTA and I use this in my Update Guide, too.

have u tried to "reinstall" the FULL OTA (the version that u have installed) via HuRu updater?

Stock firmware clean flash

Hi. I have recently bought a ROG 3 Tencent version from AliExpress (865+, 12 GB ram, 128 gb storage). The phone came with the pre-installed WW version. I presume it was converted from the CN version by the seller. He did a really good job since there are no problems whatsoever, no "incompatible firmware" error, refresh rates working fine. However I'm a bit paranoid about buying electronics from CN, so i wanted to perform a totally clean firmware flash.
My knowledge of Android is limited so I'm asking for help. To my understanding what i should do is:
- install adb and drivers, fastboot binaries or tool all in one (does it download all the necessary files and drivers automatically?)
- unlock bootloader with asus tool or command line in adb, (is it necessary to format internal storage?)
- put the phone into recovery mode by turning it off and then pressing volume+ and power and connect it to pc
- run the command prompt from the adb folder
- type "adb reboot bootloader" to get into fastboot mode
And that's where im getting confused.
What i want to do is fully format internal storage (don't know the fastboot command for that) and perform a clean flash of the newest stock firmware (it comes in a zip file on the official ROG3 support page). From my understanding, since ROG3 doesn't support sd card i need to put the firmware file in the adb folder and run "adb sideload firmware file name.zip" than "adb reboot bootloader" again and sideload the same file again to flash it to the second partition. Do I need to wipe cache after that? If so what is the command for that? Than i would like to relock the bootloader (fastboot oem asus-lock). I'm sure I'm wrong at some point and probably missing some steps so please guide me through the process.

Also, can someone explain to me what is the difference between RAW, UL, and "normal" WW firmware available at Asus support page? As I can recall UL firmware and Asus unlock tool were also available for download at Asus support page but now they are gone.

About MIUI EU ROM Brick and won't be able to connect to PC or OTG (Lose usb port)

Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)

This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...

zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
I was talking about the Miui 12.5 update but it's good to know it

ZeroNoTime said:
Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)
Click to expand...
Click to collapse
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip

4. Have you tried simply formatting data from TWRP before attempting to boot?

Dobsgw said:
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip
Click to expand...
Click to collapse
Yep, i tried everything but doesn't work
I only have access to twrp and fastboot but the usb connection doesn't work

Dobsgw said:
4. Have you tried simply formatting data from TWRP before attempting to boot?
Click to expand...
Click to collapse
Yep but shows the message e: Unable to decrypt FBE device

Used Pixel 4a 5G can't get OTA update sideloaded. Cannot read zip, can't mount system or sd card, and can't connect to pixel repair tool. Stuck on Jan

Hey All, this is a more specific thread related to this other one:
https://www.reddit.com/r/GooglePixel/comments/ufa7o3
My pixel 4a 5g is on the january update and does not find the newer update
https://www.xda-developers.com/how-to-install-android-12/
I tried all the steps here including trying to put the zip file in the adb folder, making a full path for the file, etc, but it always says:
PS C:\adb> adb sideload .\bramble-ota-sp2a.220405.003-080c4046.zip
loading: '.\bramble-ota-sp2a.220405.003-080c4046.zip'
* cannot read '.\bramble-ota-sp2a.220405.003-080c4046.zip' *
I put the zip file on the base directory of my phone and tried mounting system but got:
"E: Couldn't Access State File
Mounted System"
I tried use the "install from sd card" but it couldn't find the sd card volume (obv)
I also tried the pixel repair tool at
But it just gets stuck at " Your phone is connected. The tool is checking your phone's software version."
Does anyone have any suggestions on how to fix this without wiping my data or if I really am stuck, how can I fix this?

SOLVED: So it seemed that my solution was that I needed to uninstall and reinstall the stock adb drivers: https://developer.android.com/studio/releases/platform-tools