yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] fac51void:
:laugh: true

For clarity:

- adb sideload can used for installing zip updates from PC, as an alternative for using the ROM/recovery manager on your tablet/phone.

adb sideload update.zip

- fastboot flash is used for installing img files to a specific partition (boot, recovery, system)

fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
[Nexus 7 Q&A, Help & Troubleshooting] cloudbyday90:
Thank you!!! Spending hours trying to figure it out, so simple. Although not sure why the toolkit didn't work, but using CMD did work.
[Nexus 7 Q&A, Help & Troubleshooting] teaclarke:
I've tried both of these, I still get the cannot read sideload FML why is this keep happening? :crying:
[Nexus 7 Q&A, Help & Troubleshooting] brandnewyc:
I was getting that message because my zip file already was a zip file and I named the file update.zip. Had to remove .zip from the file name then it worked.
[Nexus 7 Q&A, Help & Troubleshooting] spewak:
This is what got me on the right trail. I opened the command prompt, navigated to the correct folder, used the sideload command and copied the name of the update file into the command prompt window, but it wasn't until I appended it with the .zip extension that it finally worked.:victory:
[Nexus 7 Q&A, Help & Troubleshooting] ShogunShad:
Hey guys! I don't have the sideload problem anymore, but, I get this error. cannot read '(name of file).zip'
[Nexus 7 Q&A, Help & Troubleshooting] krouri:
I am either really dumb or this isn't working! I have it connected to adb device number and all working fine. I have the zip in platforms-tools cmd window opened etc. when i go to adb sideload and then top of cmd window edit paste the name of the file add .zip and it says can not read file!

Please help!!
[Nexus 7 Q&A, Help & Troubleshooting] jihoon526:
Same problem...fixed

I had the same cannot read sideload problem.

The problem was when I renamed the update package (so i don't have to type in the ridiculously long file name), i renamed it as "kk.zip".

Because this was done in windows, the file system recognized it as "kk.zip.zip".

Just rename the file without ".zip" (just "kk")

then try again - in my example: adb sideload kk.zip

it works~
[Nexus 7 Q&A, Help & Troubleshooting] DigitalOSH:
So I had a similar experience. when I tried to use

adb push

, it would say error:closed. This was weird since the device showed up when I ran

adb devices

.

When I tried to do

adb sideload xxx.zip

I would get the

cannot read sideload

error. I have Windows set to show file extensions, but decided to rename the file and remove the extension. Then I renamed it again and re-added the extension. After that, sideload worked like a charm. I have no idea what changed (if anything), but it worked for me!
[Nexus 7 Q&A, Help & Troubleshooting] hkleiner:
Fix

For me all that worked was using an aosp for the sideload, and then copying the real rom once I had android booted.
[Nexus 7 Q&A, Help & Troubleshooting] Wripper:
are you on the same directory as your file?
[Nexus 7 Q&A, Help & Troubleshooting] PiperTen:
Try addind ".zip" at the end of the file name in CMD. So if the name in the directory is ROM, type into cmd "adb sideload ROM.zip"
[Nexus 7 Q&A, Help & Troubleshooting] x000x:
oddly this helped me a lot with another device. i was having the exact same problem and found this topic in searching for a solution. but after removing the extension, renaming, then renaming and re-adding the extension it worked. i also had to type adb sideload fielanme.zip.zip to get it working.
[Nexus 7 Q&A, Help & Troubleshooting] jdarc:
Same issue, my fix

So I had the same issue when trying to get 4.4.3 on my Nexus 5 following this guide http://www.androidpit.com/install-android-4-4-3-on-your-nexus-5 I could wait for google to OTA this to my phone but I am impatient. A few problems to check when having problems.

1. adb devices should list your phone if it doesn't make sure adb universal drivers are installed.

2. make sure when you rename your .zip file you are not prepending .zip before the systems file tiyp of .zip e.g. "update.zip.zip"

3 make sure you are spelling correctly if you named your file something like nexus5-443-ota.zip you don't type something like adb sideload nexux5-443-ota.zip.

When all is said an done, this should work, if it cannot read the file try downloading a new copy of the file.
[Nexus 7 Q&A, Help & Troubleshooting] sdsingh98:
Just added a ".zip"after the file name and it worked on my Nexus5!!

For example...

adb sideload "filename"

Doesnt work..

But

adb sideload "filename.zip" works....

Hope this helps...
[Nexus 7 Q&A, Help & Troubleshooting] dwatch:
cannot read sideload

If you have renamed your file in windows (ie. update.zip ) windows takes this to mean that the filename is update.zip and from the file format it decides that it's a zip file and adds the extention .zip, in effect naming it update.zip.zip which adb sideload can't read.

Try renaming your file to update444 or whatever and don't input .zip..
[Nexus 7 Q&A, Help & Troubleshooting] AndroidsKings:
Thank You So Much Bro ^_^
[Nexus 7 Q&A, Help & Troubleshooting] KidPresto92:
run as administrator!

I opened command prompt as administrator and went to the platform-tools folder. then i did the adb sideload "filename" command and it worked fine. :D
[Nexus 7 Q&A, Help & Troubleshooting] _Morfic_:
Check available PC memory

Hi,

Adding to the list of things that may lead to * cannot read 'file.zip' * : check your PC's available memory. I'm a dev so I had a few apps running and hogging all of my 12Gb of ram, but I wasn't aware until windows suggested to close one of them :). I then realised adb may not have enough memory to open the file (or whatever it is that it's doing before sideloading). Once I stopped some of the apps, thus lowering the memory usage, it worked OK.

Cheers
[Nexus 7 Q&A, Help & Troubleshooting] slashingtemaki:
What I DID to solve this problem: I realised that the file name was too long, so I renamed it to "a.zip". Also, I set Windows to always show the extensions of files (who knows, huh?). Then I entered "adb sideload a.zip" and everything went just like a charm.

HIT THANKS IF MY ANSWER WAS HELPFUL!!
[Nexus 7 Q&A, Help & Troubleshooting] Sloth:
I have found sideload to be hit or miss, failing more time then it's successful.

I use adb push instead

adb push filename.zip /sdcard/
[Nexus 7 Q&A, Help & Troubleshooting] vinuneuro:
Thank you!!!
[Nexus 7 Q&A, Help & Troubleshooting] nrsmac:
For me, I just ran adb sideload with sudo and it fixed the problem
[Nexus 7 Q&A, Help & Troubleshooting] M2ohamad:
I had the same problem.

The fix for me is to run it with Administrator privileges., or sudo if using Linux. ;)
[Nexus 7 Q&A, Help & Troubleshooting] Steel_Alchemist:
Thank u!! you saved my phone :D
[Nexus 7 Q&A, Help & Troubleshooting] gent.b:
Hey guys, have you thought that simply you do not have the right ota file for this?

I had the same problem as you, but the solution was quite simple. I just re-downloaded the ota file from another source, in my case the 6.0 marshmallow ota, coming from Lollipop 5.1.1. then I again used the adb sideload ota.zip command, and yes, I got it right finally.

Anyway, hope this helps. Cheers
[Nexus 7 Q&A, Help & Troubleshooting] prash_cool27:
Simple FiX

To all the users searching for a fix for this !Cannot read sideload file problem !

Here's the actual fix !

After two days of searching i found the solution belive me two hectic days !:crying:

The actual problem is the update file u downloaded should have come preloaded with a .zip extension i found this while going through file properities ! in the name tab u can find ur file name to be the name.zip.zip so this is the actual problem !! this is why you cannot update ur device !! To fix this u just follow these steps !

1. after placing the downloaded file in the platform tools folder u just rename it to update ! and dont add .zip extension

2.after you reach the phase where it asks to send the package you type in the following command !!

3. adb sideload update.zip

4.Now u manually type .zip extension and download should start !! :laugh::laugh::good:

5.Enjoy the new software :cool::p

I HOPE THIS HELPS !! THANK YOU ALL !! TECHKY:victory:
[Nexus 7 Q&A, Help & Troubleshooting] Msf107252:
You Can overcome this error by this command adb sideload yourfile.zip (.zip) is important
[Nexus 7 Q&A, Help & Troubleshooting] chaybag:
Same thing by me thank you. I opened in regular CMD open file directory of adb with desired Rom inside and typed adb sideload (update.bin)

Loading

Oy, now fone won't turn on and when I plug it into the computer the computer shows several disks each with a message that they need to be formatted in order to be used. but when I try to it fails and says the disk is read only.

Any hope or is my phone GONE?
[Nexus 7 Q&A, Help & Troubleshooting] xosio:
Hi , I too faced the same issue. Finally I found the solution here ht.tp://sh.st/nR6Fg

Hope it will help you

Thanks !
[Nexus 7 Q&A, Help & Troubleshooting] zainkool:
I keep getting can not read Filename.zip

I tried everything. I changed the name so many times. Typed it with .zip and without zip. I do not know what else to do.
[Nexus 7 Q&A, Help & Troubleshooting] Android Tz:
Thank you very much.
[Nexus 7 Q&A, Help & Troubleshooting] cizi:
Adb cannot read

I tried all the mention here but no luck. I have a look on adb and its commands and the problem solved this:

adb kill-server
adb root
adb sideload <filename.zip>

I hope it will help you guys.
[Nexus 7 Q&A, Help & Troubleshooting] hyderaly:
Phew. Been banging my head against the desk for a while. Finally got the OTA Nougat installing on my Nexus 6p. This is how it goes.

Initially - nexus 6p in standard boot mode was recognised by my x64 Win10. Installed Android Studio. Ran adb reboot recovery to put my phone in recovery mode, used the key combo to get to menu, activated sideload from ADB but.... my Win10 machines would not identify my nexus 6p.

Adb devices and sideload would not return a device. Windows Device manager was empty too.

Turns out I was missing two items:

1. The Google USB driver - which I had to get from Android Studio/Configure/SDK Manager/Android SDK/SDK Tools.

2. Because it was a fresh install of Android Studio, it only installed with Android 7 platform. Had to select Android 6 platform from Android Studio/Configure/SDK Manager/Android SDK/SDK Platforms.

Then, after connecting the nexus 6p in standard boot mode (non-recovery) had to update the driver for 6p from Windows Device Manager (which showed up as ADB interface within USB Devices section). The automatic search re-categorised 6p to Android Phone/Android Composite ADB interface.

Next, used adb reboot recovery to boot into recover mode. Unplugged and reconnected the phone, switched to ADB sideload mode and Windows Device Manager recognised the device.

Hit another snag - this time side-load erred "cannot read zip file". After mucking about with renaming the file and re-downloading a couple of times, decided to rename the image using command prompt. And this time side-load read the file.

Conclusion:

=========

Need the correct ADB drivers.

Need the correct paltform tools for the current version on the phone

Rename the OTA using command prompt (rename command)

Hope this helps.
[Nexus 7 Q&A, Help & Troubleshooting] e363ma78:
You are a legend!
[Nexus 7 Q&A, Help & Troubleshooting] MuhammadBilal:
God bless you random strangers
[Nexus 7 Q&A, Help & Troubleshooting] Valiante:
I'm still stuck with this issue, I've tried everything listed. Hate technology these days, overly complicated for no reason
[Nexus 7 Q&A, Help & Troubleshooting] rpatey7394:
reached the end

I've read so many threads on this problem where the zip file cannot be read that I decided to chip in myself.

Here's all the information I can give you.

I rooted my OnePlus 3 and installed CyanogenMOD 13 but within a day realised that I wanted to go back to Oxygen OS.

I followed a pretty straightforward set of instructions I found on this following a link on the

forums.oneplus.net / threads / guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232

But when I got the bit where you sideload the zip file I got the same error a lot of people seem to get.

C:\Android>adb devices

List of devices attached

c0368ebc sideload

C:\Android>adb sideload abc.zip

loading: 'abc.zip'

* cannot read 'abc.zip' *

I have done a lot of reading in the last few hours but nothing seems to have any positive effect.

Things I've tried.

downloaded the zip file again

renamed the file

renamed the extension

put the file name back to the original again

tried looking for new drivers

At the moment I'm stuck.

No idea what to do next.
[Nexus 7 Q&A, Help & Troubleshooting] rpatey7394:
I chanced upon the solution.

The .zip file was in a folder called C:\android

I spotted a folder called C:\adb and as soon as I put the .zip file in there it worked.

Simple as that.

Hours of reading and searching and it all came down to luck.
[Nexus 7 Q&A, Help & Troubleshooting] jstegeman:
I will point out that adb.exe on Windows is not linked to be "large address aware" If you set the environment variable ADB_DEBUG=all and try to adb sideload a large file, you'll see that the call to malloc is failing to allocate enough memory for the file. The "obvious" fixes would be for adb not to try to read the entire file into memory or to be linked with the /LARGEADDRESSAWARE flag on Windows.

As a workaround, I've used https://www.techpowerup.com/forums/threads/large-address-aware.112556/ to make adb.exe large address aware, and it's now working for me.
[Nexus 7 Q&A, Help & Troubleshooting] Trak-X:
Finally found a solution for this issue. Been struggling for the last 3 days :D

Thank you.
[Nexus 7 Q&A, Help & Troubleshooting] iamamitkumar:
bless you!

Only your technique worked. You are so awesome and I wish you loads of success in whatever you do. Your life be great! Thank you so much.
[Nexus 7 Q&A, Help & Troubleshooting] jstegeman:
I've been struggling with it for a week, too - glad to help :)
[Nexus 7 Q&A, Help & Troubleshooting] sundar.seetharaman:
Thanks you so much, finally side loaded successfully
[Nexus 7 Q&A, Help & Troubleshooting] NielsKersic:
You are a goddamnd legend
[Nexus 7 Q&A, Help & Troubleshooting] jstegeman:
First time I've heard that haha. Thanks for the kind words though
[Nexus 7 Q&A, Help & Troubleshooting] Scratchling:
Scratching my head for an hour at this, SU was pushing but not any roms. Thanks a mil jstegeman for your solution.

Is it worthwhile opening a bug with google over this that we can all upvote?
[Nexus 7 Q&A, Help & Troubleshooting] glenn4466:
I tried all of the above and still got the read error. What I did to solve this was 1st to download the zip file again and not rename it and 2nd I went to the phone settings and under the developer settings there is an option something like check files over USB or something like that. I turned it off and it worked.
[Nexus 7 Q&A, Help & Troubleshooting] hideous:
Would having the device encrypted play a part in this not working?
[Nexus 7 Q&A, Help & Troubleshooting] DirkBelig:
Didn't work for me. After pounding my head flat against the desk, checking the hash, re-re-re-renaming the file with and without .zip in Windows and the cmd box, entering the command as "adb sideload ota.zip" and "...zip.zip", ran the Large Address Aware tool on adb.exe (though I've got 16GB RAM), turned off Verify Files Over USB as glenn did. NOTHING WORKS!

I'm not a super hardcore h4x0rZ, but I've messed around a bit with ADB since the Nexus 4 and I have NEVER seen this "cannot read ota.zip" error when doing ADB stuff until tonight trying to put 7.1.1 on my 6P. I've wasted an hour on this. So frustrated. :mad:
[Nexus 7 Q&A, Help & Troubleshooting] glenn4466:
You said that you re-re-renamed the file but did you try it with the original name and yes I know that is a lot of typing? The reason I ask is that I could not do it until I used the original name and the following statement on the update web page which "seems" to indicate that the file checksum is self checked and is included in the file name.

"2. Verify the checksum of the image: the OTA mechanism has a built-in validation feature, but verifying will save you some time if the file is incomplete. The last portion of the filename is the first 8 digits of its SHA-256 checksum; the full SHA-256 checksum is also shown next to the download link."

I tried for two hours and could not get it to work. Only after I changed the two things I mentioned, did it work. Since I did both things at the same time, I don't know which one did it. Anyone who has "show file extensions" enabled should not have a problem with the double zip issue. Putting the file in the same directory as adb.exe or changing the system path will eliminate most of the other problems. Enabling large file support seemed to have no impact on my 64 bit 8GB Win 10 PC.
[Nexus 7 Q&A, Help & Troubleshooting] DirkBelig:
Yes, I tried the original long file name. (You can copypasta into cmd by hitting Alt+Space, then E, then P.) I also ran the SHA-256 checksum on the renamed file just in case the file name impacted the hash. I even copied the full hash from the download page to paste into the checker to verify. I also have show file extension turned on. Believe me, I've tried everything in this thread that people said cured their ills with no success.
[Nexus 7 Q&A, Help & Troubleshooting] DirkBelig:
Gave up and DLed Wugfresh and it slammed the OTA onto my phone, first try, less than 15 minutes from start to finish. Now running 7.1.1 and cursing that I wasted hours on ADB. Yeah, real nerds do it on a command line. Would've, but it didn't work, so pffft. Got results.
[Nexus 7 Q&A, Help & Troubleshooting] fubecapobre:
Make sure you kill adb before you try to run Large Address Aware

Many thanks to [MENTION=845421]jstegeman[/MENTION] for the genius insight into LARGEADDRESSAWARE. I wanted to clarify a couple things for those who are still having issues...

1) Enable debug tracing for adb.exe so you actually know why it's failing. Clarification on [MENTION=845421]jstegeman[/MENTION] post -- you need to set the env. variable ADB_TRACE to all, not ADB_DEBUG. Open a command prompt and type 'set ADB_TRACE=all' and you should be set.

2) Once ADB_TRACE is set try the sideload command again: 'adb sideload <filename>'

3) adb should now spit out an error message. If it's the large address problem you'll see something like 'Unable to allocate 13345........ bytes'.

4) BEFORE YOU RUN THE LARGE ADDRESS AWARE EXECUTABLE LINKED TO BY [MENTION=845421]jstegeman[/MENTION] YOU NEED TO KILL ADB. If you don't kill the service then the utility will fail (without any error message) because you can't modify a running EXE. Type 'adb kill-server' then run the utility.

Once I did 4) then everything worked like it should. Hope it helps.
[Nexus 7 Q&A, Help & Troubleshooting] kaylz4:
solution

all you have to do is add the file extesion whether it be .rar or .zip dont unzip or unrar the file
[Nexus 7 Q&A, Help & Troubleshooting] pranay7777:
This 1 billion times. Doing step 4 fixed the issue..... Thanks!!!!
[Nexus 7 Q&A, Help & Troubleshooting] Jayce Jocelyn:
Thank you so much!

You are a bloody legend! Thank you so much for posting this :*
[Nexus 7 Q&A, Help & Troubleshooting] cv636r@gmail.com:
Thank you Good Sir

This is what got me going. Did the set ADB_DEBUG=all but didn't see any difference, file is only 1.5 GB and LAA stated it's used to make application recognize files over 2gb (and useful for application pre-2000) which threw me off. After setting the CORRECT variable (ADB_TRACE) i'm now sitting looking at the matrix (hex codes flying) in my cmd window as my phone is getting updated. Many MANY thanks for your attention to detail, and providing ACCURATE and reproducible steps. :good::good:

For anyone who is still having issues here's what I did as i'm not sure if there are other factors that would account for errors:

1) Open cmd.exe as Administrator

2) cd to ADB directory (for me: C:\Users\<USERNAME>\AppData\Local\Android\sdk\platform-tools)

3) Copy zip file to to ADB directory

4) Do a "dir" to make sure you're not double extentioning yourself (file.zip.zip) and rename if you are

5) "adb devices" to make sure adb can see your device

6) "set ADB_TRACE=all" to show all output

7) adb sideloader file.zip

8) IF you see something like 'Unable to allocate 13345........ bytes'. Follow steps above to make adb Large Address Aware

9) Kill adb - "adb kill-server"

10) adb sideloader file.zip
[Nexus 7 Q&A, Help & Troubleshooting] gleggie:
Does anyone have another link to that forum post? It's not loading for me, and I need to find a way to fix my large address aware

Edit: Resolved, I had to clear my computer's RAM and that allowed it to flash
[Nexus 7 Q&A, Help & Troubleshooting] ams73:
It works, thank you so much!

You saved my day... thank you so much! I was reading trying all 'renaming' stuff, but nothing worked. Finally I ran 'set ADB_TRACE=all' and that told me about the LARGE ADDRESS issue. Ran the utility, fixed adb.exe and then everything went just fine.
[Nexus 7 Q&A, Help & Troubleshooting] jookas:
Thank you, Thank you, finally :good: :laugh:
[Nexus 7 Q&A, Help & Troubleshooting] eLHAMiiD:
how did you do that for adb to recognise the larger files?

please go step by step and give out the syntax properly.

your help is highly appreciated.

---------- Post added at 05:08 PM ---------- Previous post was at 04:59 PM ----------

Many thanks dear comrade, I was so stuck whatever I did to sideload this NOUGAT on my phone.

Best regards

---------- Post added at 05:16 PM ---------- Previous post was at 05:08 PM ----------

thanks a lot
[Nexus 7 Q&A, Help & Troubleshooting] jasonnm:
I signed in just to say thanks! :good::good:
[Nexus 7 Q&A, Help & Troubleshooting] ziggary:
Champion !!!!
[Nexus 7 Q&A, Help & Troubleshooting] Kamkol:
So if i'll use Linux this shouldn't be a problem? Its easier for me.
[Nexus 7 Q&A, Help & Troubleshooting] Cypher dude:
Worked for my ONEPLUS 3 to flash BETA 25 :)(ANDROID OREO)

Thanks for simplifying things!! The first file of laa(large address aware) didn't work for me I downloaded the second one named "laa net framework" something like that and I followed the steps given at the top and BAMM.... it started to flash!! Thanks again [MENTION=845421]jstegeman[/MENTION] and [MENTION=7921430]fubecapobre[/MENTION]
[Nexus 7 Q&A, Help & Troubleshooting] shitnil:
ive used the large address awareness app and it made adb.exe in the android folder, but it still does not work. please please please help.

i have a oneplus 5 and i feel miserable with this problem.
[Nexus 7 Q&A, Help & Troubleshooting] sahed01:
download the flash tool from here "https://www.asus.com/zentalk/thread-119788-1-1.html" this is a simple adb fastboot foldar. and then put the zip file here and do your thing. it should work.no more "can't read x file". it worled for me. i am flashing the oxygen os 5.0.2 in windows 10.
[Nexus 7 Q&A, Help & Troubleshooting] gai4000:
Guys can someone team weaver help me with this?
[Nexus 7 Q&A, Help & Troubleshooting] avetny:
I don't know who you are but thank you from 2019 !! (Pixel 3 Xl)

I tried with original name and is work !
[Nexus 7 Q&A, Help & Troubleshooting] CustomRomNoob:
Bro, thank you so ****en much. You saved me from a panic attack. God bless you man!!!
[Nexus 7 Q&A, Help & Troubleshooting] nigelrodrigues95:
Thank you all so much! This ended up working for me as well
[Nexus 7 Q&A, Help & Troubleshooting] StuardBr:
I'm necroing this post just to add ONE GODDAM INFORMATION:

BEFORE use the program to change the adb to large address,

YOU MUST USE adb kill-server FIRST OR THE CHANGES WON'T APPLY.

Yes, I forgot to do this int he first time...
[Nexus 7 Q&A, Help & Troubleshooting] unaib:
i can't use adb sideload. although i have used the stock rom still i can't use it.

Any help
[Nexus 7 Q&A, Help & Troubleshooting] iano31254:
C:\Users\Utente>adb sideload rom.zip

loading: 'rom.zip'

* cannot read 'rom.zip' *

I can't install the rom, can you please give me step by step instructions? I've read all the posts, but I couldn't figure out the real solutions