Develop Bugs

[HOW TO] build an autosigner for OSX

Ok, so I'm kind of new to automator which is why I'm making this as a tutorial instead of a download.
1. First you need to download the AndroidMod.zip JesusFreke posted
http://android-dls.com/forum/index.php?f=24&t=191&rb_v=viewtopic
2. Copy the three highlighted objects from the SignApk folder to the folder of your choice, I chose one called signapk in my applications folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. Open the info window for one of the files in there final destination, keep it open as we're going to use the Where field in the next step.
4. Open Automator and choose a custom workflow. First go to Files and Folders then choose Duplicate Finder Items. What this does is create a duplicate of the file we're going to sign and pass it to the shell script we're about to create.
Then scroll down to utilities and then choose Run Shell Script.
5. Change the drop down for pass inputs from to stdin to as arguments. This allows us to either create an application we can drop files we want to sign onto, or create a finder plugin so we can right click(or ctrl-click if you're on a single button trackpad or mouse) and sign it from there.
6. The basic usage for the signapk.jar included in the android mod file is as follows: java -jar signapk.jar testkey.x509.pem testkey.pk8 <update.zip> <update_signed.zip>
what we need to change is add the absolute path to signapk.jar, testkey.x509.pem, and testkey.pk8. Thats what is listed in the where field in the get info window comes into play, just type everything listed there right infront of each of those three files. In my case thats going to be /Applications/signapk/. We also need to change <update.zip> to "[email protected]" with the quotes. Thats what is actually going to be the input from either dragging and dropping or right clicking. Finally the last parameter we just need to remove because we made a duplicate of the file to be signed, and if theres no final parameter it overwrites the file sent to it. My final shell script is shown in the image below.
7. Save the file as an application if you want to drag and drop files onto it and Save it as a plugin and then select finder if you want to be able to right click and sign. When using a finder plugin you right click and go to more, then automator, then choose the plugin you just saved.
Thats It! whenever you use it it will automatically create a copy of the file you're signing (ex. Launcher.apk -> Launcher copy.apk or update.zip -> update copy.zip) and sign that. The copy is the signed version and the original is left untouched.
Feel free to modify this however you want, if someone wants to release a prebuilt version of this automator action, thats perfectly fine by me, you don't even need to ask for permission. Do whatever you want with it.

Thanks very much! I was getting tired of launching Parallels whenever I wanted to do something like this.

yes super useful, was sick of tossing files back and forth between my computers. definitely needs to be a sticky.

I couldn't get it to work for me with ADP1.1 When I try to boot up with update.zip I get the error that the files were not signed. For argument sake I redid everything a few times. And saved my files exactly where you saved them and still no luck. Any ideas?
::edit:: I think that my problem has something to do with certain files not changing to .apk when I change them back from .zip. Some of my .apks change to that black square that you know are some executable program while the rest remain little white ones. Any ideas on how to change them to normal executable files?

yeah, if you open the info (command + i) on the file you'll see that the file has the .zip hidden. In the info window you can delete the .zip extension and just leave the .apk. Theres a setting somewhere to enable file extensions always, and it's quite nice to have that enabled

I already have it enabled. That is why I can't figure out why some files do that and some don't.
Edit: Finder is reading some of them as Unix executable and others as documents. I guess the trick is trying to figure out how to fix that.

That would be as simple as running chmod on them in the console, however I've never had a problem with that, as long as they're named.apk and not .apk.zip I've never had a problem putting them back on the phone even if osx didn't see them as unix executables

That is the only thing I could think of and chmod did not work. But I am not 100% sure that it is even the files that is the problem.
::Edit:: After testing things a little more I think it has something to do with the signing itself. Even though it makes that copy I don't think it is actually signing the file. Would you be able to upload your program?

i have had the exact same problem as Broopa and its getting really anoying lol could someone please upload the file for us to use.

Anyone have any idea why the folders aren't getting signed. I even installed java from Apples developer site and no luck.

c'mon people...youve all done it can you please send some info our way??

sorry guys I don't know why it's not working now. I'll try to get it fixed and reposted.

Any updates on this? I still can't get it to work.

i created the workflow, saved it as a service for finder, and tried it out.
it creates the dupe file, but pops up with an error message:
The action "Run Shell Script" encountered an error.
there must be something wrong with the script itself, or the arguments being called by it.
is nobody still working on this? i know it's been over a year, but this would be very helpful to have available.

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!

Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.

Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz

I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?

Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.

confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus

error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz

djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm

mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App

edit: got it thanks

Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium

whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?

bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?

oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks

so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it

|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,

Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat

when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be

When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

[Q] Wiped OS need help to sideload zip file

I just messed up big time.
I have been rooted for a couple of months now and played around with a couple of roms. I noticed my free storage shrinking when there apparently should have been nothing on my Nexus 7 except for the system files. What I did was delete my system,storage and cache with Clockworkmod Recovery leaving me with a blank tablet. Unfortunately now I can't install any zip from my sdcard as there is just emptiness on my tablet meaning I have no OS. I had initially thought I would be able to just install the OS from my usb stick but I couldn't find any way to mount my usb stick in recovery mode and I have reason to believe it just isn't possible.
As far as my research has taught me the only way to install a OS now is via sideloading it. I have spent like 2 hours reading through several threads and various other sites how to sideload a zip file onto my tablet but I'm having trouble with that. I downloaded ADB tools and I looked into this thread: http://forum.xda-developers.com/showthread.php?t=2380913
My current state is that I am in recovery mode and selected 'install zip from sideload' I have ADB tools and the OS but can't sideload it onto my tablet. When I use the command 'adb devices' my N7 is not listed. When I go to device manager the N7 is listed but there is also a warning sign displayed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I desperately need help to resolve this issue, I love my Nexus 7 and can't bear the thought of having bricked it for good because of my own stupidity.
Much thanks in advance.
P.S. It is already late at night in Germany so I won't answer in the next few hours.

I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images here:
http://developers.google.com/android/nexus/images
Pick nakasi or nakasig depending on whether you have wifi or mobile version

You need to install this to use ADB while in recovery. You can use fastboot to flash the stock ROM.

sfhub said:
I think you are on the wrong sub-forum, this is the Nexus 7 - 2013 (2nd revision) sub-forum.
However to answer your question, personally I would boot into the bootloader and use the factory images
Click to expand...
Click to collapse
I'm sorry I wasn't aware of this being the wrong sub-forum.
Thanks for your submitted fix, it sounds very simple yet I don't know how to perform it. Do you mean I have to select 'Restart bootloader' on my N7?
How do I then get the factory image onto my tablet?

I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.

sfhub said:
I'll just summarize, the factory restore is in .tgz (tar.gz) formst. Using 7-zip to open the .tgz and extract the tar file. Open the tar file in 7-zip again the get the factory image directory. Within that directoy is a batch file called flash-all.bat. It needs fastboot.exe to work. Easiest way, copy these files from your platform-tools (adb directory)
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
into the factory image directory.
Reboot your tablet into bootloader (power down, then power+vol- until bootloader menu comes up) That's the button sequence on N7 2013. I don't know about N7 2012
then just type flash-all in a command prompt. It will do the rest.
Make *sure* you get the right version of the factory restore (wifi or mobile).
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery. He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.

sfhub said:
...
Alternatively do as Username mentioned. You'll need to delete your existing drivers and install the one he pointed you to. This should get the adb connection recognized. From there you can do the adb sideload you've been attempting.
Click to expand...
Click to collapse
Username invalid said:
The ADB/Fastboot driver from SDK only works when in bootloader and booted into ROM. Without the Naked Driver 0.72, his computer would show "Nexus 7" under Unknown Devices in the Device Manager while in recovery.
Click to expand...
Click to collapse
That's why I suggested he follow your post to install the naked drivers if he wanted to use adb sideload in recovery instead of using fastboot and the images.
Username invalid said:
He needs to install it in addition to the SDK driver for his computer to recognize the device while in recovery to Sideload or ADB push.
Click to expand...
Click to collapse
According to the OP for naked drivers, he suggests removing old drivers. I just relayed what was in that post.
1wayjonny said:
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse

merchants oicedBri
Update:
Thanks for your helpful answers, I figured it out now.

Get Continuum on Lumia x5x devices

Hello guys! In this thread I will show you how to get Continuum on Windows Lumia x5x devices.
Please follow the steps exactly.
1. Download and install the program from this link Windows Phone 8.0 SDK Lite
2. Enable Developer Mode on your device (Settings > Update & Security > For Developers)
3. Download the files from this link and unzip them to your downloads directory.
4. Connect your device to your PC via USB
5. Go to
Code:
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\XAP Deployment
and open up XapDeploy
6. Select Target Device and in xap browse to your downloads folder and select vcREG_1_6_W10M.xap file and press Deploy.
7. Download and install the tools from here
8. Open an Administrator Command Prompt at this location
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
9. Run the following command pointing to your previous unarchived files in download
Code:
iutool -v -p "path to the file acer.service.acersystemservice.spkg"
, the device will reboot into the gear mode and back to the OS.
10. If the above step throws an error try going to Device manager and delete the drivers regarding your phone from usb devices unplug and reconnect the device then repeat the above process and it should work.
11. Copy newndtksvc.dll and ndtksvc.dll to your Documents folder on your phone through USB also in the parent directory of Documents make a folder called ndtk and copy the files there as well because they will be needed in a further step.
12. Open up vcREG and from the bar press the dotted menu select x50 series unlock press step 2, reboot then step 3 reboot then from the same menu check the Live Interpool/Capability Unlock and press Apply.
If you have some unclear steps or you don't find the files here is another tutorial regarding the above steps.
Now we are ready to proceed with the Interoop tools app and with the installation of the Continuum cab file.
13. Download the files in this link
14. Extract the files and copy the file “microsoft_ms_docking…” cab file to C drive on your PC under (C:\cabs)
15. Open up an Adiminstrator Command Promt go to the folder
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
and run
Code:
iutools -p C:\cabs -v
. The device will reboot into the Gear screen and then back into the os.
16. Copy and paste interop tools file(.appxbundle) into your phone memory
17. Go to the phone's file explorer and open the interp tools file and install it if it doesn't come up into your app menu please download it from this link and drag into your phone the apx bundle files from the Dependencies folder install them and then retry to install the InteropToolsApp.
18. Open up InteropToolsApp select INTEROP UNLOCK from the menu and thick Interop/Cap Unlock, New Capability Engine Unlock, Full Filesystem Acess(Make sure the MTP Root Path is C) and the most important one is Restore NDTKSvc (x50) do not thick the RestoreNDTKSvc simple because you will need to format your phone and follow again all the steps above.
19. Go back to the REGISTRY EDITOR Enter Registry Type as “Integer”, Registry Key path as SOFTWARE\Microsoft\Shell\Docking, Registry Value Name as EnabledForTest and Value data as 1 then press Write Data and reboot your phone.
20. You have sucessfully installed Continuum on your x5x Lumia device.
Additional information.
You will need a windows 10 computer to install the programs and to put them into your phone.
Also if you want to connect your continuum device to your desktop just go to settings find Projecting to this PC and select Available everywhere from the first dropdown then you will be able to see your PC in wireless adapter connection of the Continuum App.
Tested it on a Lumia 550 phone with 1gb ram and 8gb internal storage with Windows 10 Mobile on it. And here is the proof
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

13. cab file must be for OS build version on phone
your cab is NOT FOR build .693! is for .448 build!!!!
download correct cab file from catalog.update.microsoft.com (for search use 000-gb or 000-ru, 000-de..)
when you open download windows, use ctrl F to search for docking... is two files, you download file with CBS in name (not CBSU)

dxdy said:
13. cab file must be for OS build version on phone
your cab is NOT FOR build .693! is for .448 build!!!!
download correct cab file from catalog.update.microsoft.com (for search use 000-gb or 000-ru, 000-de..)
when you open download windows, use ctrl F to search for docking... is two files, you download file with CBS in name (not CBSU)
Click to expand...
Click to collapse
Thanks, it worked well for my device with the cab provided in my link. Hope your comment will help others! Really thank you

is recommended to use cab file from same build version... maybe you are just lucky but next time watch out

Adb sideload error

hi, I've tried to clean install oos 4.0.3 with adb side load and it show me error 'cannot read .zip'
when I enable adb trace, it show me error like this
adb sideload ota.zip
load_file: 324: 1020 | load_file: could not allocate 1504196936 bytes
* cannot read 'ota.zip' *
anyone can help me ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yep known error, wrong drivers, not much known of the issue. Do you have TWRP? Then type adb push zipfile /sdcard/ then you can manually flash it.

Puddi_Puddin said:
Yep known error, wrong drivers, not much known of the issue. Do you have TWRP? Then type adb push zipfile /sdcard/ then you can manually flash it.
Click to expand...
Click to collapse
1.I'm not sure cause of wrong driver because I just sideload oos Open beta 11 3 days ago, and it work well;
2. yep I've TWRP, but I want to find down why I got this bug

isibiki said:
1.I'm not sure cause of wrong driver because I just sideload oos Open beta 11 3 days ago, and it work well;
2. yep I've TWRP, but I want to find down why I got this bug
Click to expand...
Click to collapse
Oh ye even weirder.. have you tried "adb kill-server"? Maybe rebooting the PC while keeping the phone plugged in? Last one helped for me once.. But i still cant sideload either.

Puddi_Puddin said:
Oh ye even weirder.. have you tried "adb kill-server"? Maybe rebooting the PC while keeping the phone plugged in? Last one helped for me once.. But i still cant sideload either.
Click to expand...
Click to collapse
I tried everything like re-install driver, adb kill-server, larger address adware and more, but it didn't work. Luckily oos stock recovery can install from internal storage or flash twrp and install throught it

You are on a 32 bits windows computer. Which is unable to load the entire file in memory on default settings.
You should try this:
jstegeman said:
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.
Click to expand...
Click to collapse

JorgeManuelSilva91 said:
You are on a 32 bits windows computer. Which is unable to load the entire file in memory on default settings.
You should try this:
Click to expand...
Click to collapse
My computer running 64 bit windows 10 and I already tried this solution and it didn't help me resolve this bug

isibiki said:
My computer running 64 bit windows 10 and I already tried this solution and it didn't help me resolve this bug
Click to expand...
Click to collapse
Then, your computer may be out of RAM, check how much RAM your computer has and close programs you're not using.

JorgeManuelSilva91 said:
Then, your computer may be out of RAM, check how much RAM your computer has and close programs you're not using.
Click to expand...
Click to collapse
8gb ram with 56% free memory isn't enough ?, I think it because L Speed app I install in my phone, after install it, I cannot full unroot in super su app and this adb error happened after that.

isibiki said:
8gb ram with 56% free memory isn't enough ?, I think it because L Speed app I install in my phone, after install it, I cannot full unroot in super su app and this adb error happened after that.
Click to expand...
Click to collapse
Check this topic on OnePlus forums: https://forums.oneplus.net/posts/15306505
I had the cannot read 'update.zip' issue. Turned out it'd been installed as the wrong device in Windows 10 - it'd been recognized as a Marshall London Phone for some reason. To fix it, I removed it from device manager, and told it to delete the drivers. Then rescanned, and reinstalled it as a standard Android ADB Interface - it then accepted the file on the sideload. Drove me mad for a couple of days!
Click to expand...
Click to collapse