Related
Hi
I have a Nexus 5 currently on KitKat 4.4, and am trying to manually update to 4.4.1 but with no success
Have read and followed all stages in posts relating to updating the firmware, have downloaded the 4.4.1 file and Android SDK.
All steps work as they should, have got as far as my PC recognising my device serial number, until I get to the step where I enter, in the command prompt opened from the platform tools folder
adb sideload KitKat.zip (KitKat.zip being the name I have given the file)
I then keep getting the error message "unable to read file KitKat.zip"
I have tried with and without .zip in the command but still no luck
Help please?? I have run out of ideas to try
The command adb sideload (filename).zip has no space between side and load.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
Also is your 4.4.1 update file in the platform tools folder? Are you opening the command prompt in the platform tools folder?
Sent from my Nexus 7 using XDA Premium HD app
Please ask questions in q&a. General is not for questions
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
nohcho said:
When you type in the command prompt: adb sideload update, do not type in the .zip part in the command line
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
marleyfan61 said:
Wrong. First, rename the file to "update.zip" without the quotes. Make sure it's not "update.zip.zip." . Make sure the file is in the platform-tools folder. The command is "adb sideload update.zip" no quotes
Click to expand...
Click to collapse
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
I was having the same issue. I just kept the ota name as it was when I downloaded it and added .zip to the end. It worked fine after that. Just copy and paste it in cmd
red83 said:
Have tried renaming the file to update.zip as well as trying several other file names, doesn't make any difference the same error message appears
Click to expand...
Click to collapse
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
forgive me if you did this already, does your operating system display the three letter file extension like 'update.zip, adb.exe' etc.
marleyfan61 said:
Maybe a corrupt download. Try downloading again. Make sure you make file extensions visible so you don't accidentally name it .zip.zip. Then try my instructions again.
Are you booting to recovery then doing the power/volume up thing then select apply update from adb?
Click to expand...
Click to collapse
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
Try my suggestion above, worked for me. I was having the same problem.
red83 said:
yes I put the phone into recovery mode as described in the online tutorials by holding the power button and the down arrow volume button simultaneously and from there I can select recovery mode and then into the sub menu that you popular by hold power and tapping the up volume button and it appears at the top of the screen, I then select ''update via ADB''....... by the way by default the windows drivers package doesn't have a specific ADB driver, and as a result you get an on screen prompt to verify this is the case.
When you activate usb debugging from developer options on the android desktop is when this becomes apparent, to get round this I have loaded up a couple of generic ADB drivers and tried them, they work as when you open the command prompt and specify the location of the adb.exe file it recognises the adb device when you put in ''adb devices''...its serial number/ imei can be seen from there.
Now here is the random part...when you populate the string under command prompt and then add '' adb sideload update.zip (exactly as that) you get an on screen prompt appear stating the ' cannot read update.zip '
I was thinking this file may be corrupt but I have located several now and none work at all.......basically I can run the adb.exe file from the ''platform-tools'' folder where the ''update.zip'' file has been located....regardless of what I name it or whether it is called kitkat.zip or without the .zip extension it still says it cannot read the file....what am I doing wrong??
Click to expand...
Click to collapse
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Yes what you said works, straight into recovery no probs by putting 'adb reboot recovery in a cmd prompt window to the specific directory that the abd file is located......(in platform tools) then if I put adb devices the serial number comes up straight away with 'sideload next to it.
So then I put adb sideload update.zip, and guess what!
cannot read update.zip....
Have you tried my suggestion?
richport29 said:
Have you tried my suggestion?
Click to expand...
Click to collapse
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
marleyfan61 said:
I'm not following some of what you are saying. I think it may be an adb driver issue. Have a look at this thread :http://forum.xda-developers.com/showthread.php?t=2514396
Also, I don't use adb.exe. I open a command prompt and navigate to the platform-tools folder and execute the commands in the cmd window. You say you are getting into recovery by doing the button presses. You should be able to connect your phone when not in recovery and within the cmd window execute "adb reboot recovery" to get into recovery. If that's not working it's a driver problem.
Beyond that I'm not going to be much more help - not that I've been any help since you are still having the problem.
Click to expand...
Click to collapse
Should I be "de-activating/activating" anything else other than activating the developer options and selecting USB debugging....should I remove my SIM card??
Anything else I may have overlooked please?
red83 said:
Yes have just tried what you suggested and only added .zip to the original name of the file and still the same error message appears
Click to expand...
Click to collapse
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
richport29 said:
Try re-downloading the ota. Place it in the platform-tools folder, and try again.
7ed504f678cea49ecf0974e8cd956e2974e3f943.signed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
Click to expand...
Click to collapse
Have tried re-downloading the file from several locations, placing it directly into the platform-tools folder and only adding .zip to the file directory name.....still no joy
When you type adb devices, what comes up?
Unless you absolutely have to have the camera fix in this update right now, then I suggest you just wait til the OTA becomes available on your phone. The camera fix is the only significant thing in the update. I don't know what the issue is with what you are trying but I suspect there is something not being done right. Sounds like it's not worth the frustration tho.
I have a galaxy light I an attempting to abd sideload a zip via recovery. I am able to boot into recovery, when I "adb devices" nothing appears that is all fine. The recovery has an option for adb update, I select this. It shows up as use "adb sideload <filename>" via usb. At that point "adb devices" shows the device "<serial number> sideload", I then attemptto "adb sideload <filename>" filename is a zip file in the correct directory. I then get a list of adb commands as if "adb sideload" is not a recognized command. I am using the latest adb version of 1.0.29. note: when i recheck "adb devices" it will now come back as "<serial no> host". the "adb sideload <filename>" prompt is still on the recovery screen. Does anyone know why my sideload cmd is not working? thanks
bg.
solved
no more problems reinstalled platform and tools.
bg
I try to hard reset but I'm still stuck on loading screen. How do I add a zip file to my sd so I can flash it, since it doesn't even detect my oneplus on my computer? Please help me and lend me your knowledge and power =].
Can you boot in bootloader and connect it through adb and fastboo with your pc? in that case it would be easy to reflash everything
I can boot into fastboot and TWRP but I'm wondering how can I add file into my internal hard drive since it doesnt detect the phone on my computer?
Any help with some instructions would be really nice =] :good:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
right now its on MTP USB Device as my device on my Device Manager, can you link me to the proper usb driver? Because I"m pretty sure I updated it and it was working while my phone is working. Also how can I check if its using adb devices?
bud77 said:
Do you see it using "adb devices" or "fastboot devices" ?
If not, you must update your adb drivers on your computer and reboot it
Click to expand...
Click to collapse
Also it said "Windows has determined the driver software for your device is up to date" but doesnt detect my phone?
Anyone still here so they can help me?
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
yes i see adb push , but there's no file there. How can i add file there?
Dzhedaj said:
So as asked previously, when you connect via fastboot, and boot it into TWRP, do you see it via adb ("adb devices" command in the platform-tools folder)? Did you try adb push <filename> /sdcard/ ?
Click to expand...
Click to collapse
Basically i'm in TWRP and i dont see any thing in recover or etc or in my sd, all blank so how can I put an image there to flash?
Anyone still here to have any answers to help?
which jeithis
http://i.imgur.com/378HzRp.png also get this image also
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
@M I N E, go read the sticky posts in the general section. It will explain how to do an adb push command.
@timmaaa and others have done a great job with some write ups for this device.
timmaaa said:
Use an adb push command to send a ROM zip to your phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Either method is fine though.
If OP has problems with drivers, I recommend using http://forum.xda-developers.com/showthread.php?t=2386956 they work great.
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
M I N E said:
what is the push load command? How can i push something if i dont have any file on my phone to flash? can you guys type out the command?
Click to expand...
Click to collapse
Read the post above you that I posted. Use that command as well as the instructions and you can flash a file using adb sideload.
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
M I N E said:
well I try factory swipe nothing there, i check the TWRP , no files is there i mean nothing. And I cant do adb push because my when i type adb devices it doesnt recognized, because how can i turn on debugging if my phone doesnt have any rom?
Click to expand...
Click to collapse
You're not reading my message properly. I'm telling you to do adb sideload. Please read what I said carefully word-by-word.
Or do a factory wipe then go into TWRP -> Advanced -> ADB Sideload -> Swipe
adb sideload <name-of.zip>.zip (ensure the .zip is in the same folder as your fastboot/adb) and then it'll send the zip over to the phone and flash.
I prefer the adb sideload method as it pretty much pushes the file over to the phone and then flashes it afterwards.
Click to expand...
Click to collapse
The whole point of adb sideload is that you're sideloading a flashable zip that is not on your phone but on your computer and you're pushing the file onto your phone which will followup with flashing the zip.
You need to be typing adb sideload on your computer with the proper environment for adb set up with the proper drivers installed if you haven't already.
Section A would be for me but on MAC i dont know how to open a command prompt.. i have the renamed zip file in my platform-tools location as ordered but how do i get "adb reboot recovery" working?
My phone is connected to the MAC with an USB and Debugging is enabled through the developer - options...
Im new in this forum but i havent found any thread like this so would be aweseome if you could help here?
Would it be easier to root my device on a mac and then flash it on my nexus directly? just read too much forum stuff but im just a beginner!
so lets see what this forum got
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. It's attached at the bottom of this post.
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press volume up and release. The menu will appear. Select “apply update from adb”
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
http://www.wikihow.com/Get-to-the-Command-Line-on-a-Mac
?
ok i had this then already running but "adb reboot recovery" doesnt do anything then!
will i have to put another phrase in front? im stuck on 4.4.4....
I believe you have to type ./adb or whatever command you want to use. That's just how Unix works. So ./adb sideload update.zip. Try that.
Kristofs-iMac:~ kristofgervautz$ /Users/kristofgervautz/Desktop/adt-bundle-mac-x86_64-20140702\ 2/sdk/platform-tools/adb sideload update.zip
* cannot read 'update.zip' *
Kristofs-iMac:~ kristofgervautz$
thx im getting forward but still not right! :fingers-crossed:
I have Not found a good tutorial for Mac so I haven't been able to upgrade. This is the best video I found. Except it does not show how to setup android Sdk or what I'm supposed to use it for. Check it out it might be helpful
http://youtu.be/NPIWZxPTbbQ
kristwi said:
Kristofs-iMac:~ kristofgervautz$ /Users/kristofgervautz/Desktop/adt-bundle-mac-x86_64-20140702\ 2/sdk/platform-tools/adb sideload update.zip
* cannot read 'update.zip' *
Kristofs-iMac:~ kristofgervautz$
thx im getting forward but still not right! :fingers-crossed:
Click to expand...
Click to collapse
first, it may be easier to cd to your platform-tools directory. So is the adb command being accepted by terminal? As I said earlier, I am pretty sure you have to type ./adb for the adb command, unless you changed that in your bash_profile
So, type:
cd /Users/kristofgervautz/Desktop/adt-bundle-mac-x86_64-20140702\ 2/sdk/platform-tools
then:
./adb sideload update.zip
while making sure you are in STOCK recovery and selected "apply update from adb"
ethantarheels123 said:
first, it may be easier to cd to your platform-tools directory. So is the adb command being accepted by terminal? As I said earlier, I am pretty sure you have to type ./adb for the adb command, unless you changed that in your bash_profile
So, type:
cd /Users/kristofgervautz/Desktop/adt-bundle-mac-x86_64-20140702\ 2/sdk/platform-tools
then:
./adb sideload update.zip
while making sure you are in STOCK recovery and selected "apply update from adb"
Click to expand...
Click to collapse
oh thx it worked tried it again today and yes i forgot the "./" in front and now when i wrote ./ adb devices it recognized my device!
THX GUYS!
Problem Android 5.1 on Mac... (5.0 no problems anymore )
on my Terminal it says... Total xfer: 0.00x
on the Nexus 5 it says...
E: footer is wrong
E: signature verification failed
Installation aborted.
Keep in mind i just have a MAC and my phone is stock Android 5.0.1.
And i dont wanna get out of stock anyways..
So bored of fixing all these problems aber i already did this whole thing with Android 5.0 months ago...
Already updated my Android Studio and all the packages cause before it wouldnt even get till this point.
DISCLAMER: DOING THIS MIGHT RESET YOUR PHONE SO PLEASE BACKUP YOUR FILES BEFORE DOING THIS
now lets get started
download this tool (even if you already have adb and fastboot)*
https://forum.xda-developers.com/showthread.php?t=2317790
and go to your phone's settings then System > about phone and press on build number until it tells you: "you have developer options"
now go to System > developer options and enable android debugging and OEM Unlocking
now plug your phone into the pc and open the file: "cmd-here.exe" from the tool you downloaded
now type adb devices and it will probably tell you unauthorized, if it does then open your phone and click on accept
if you dont see any thing other than "list of devices attached" then download this
open it and input in, N and then Y so you dont install adb but you do install the phone's drivers
now type adb devices and you should see random numbers, if it says unauthorized just go back to when I said how to fix it
so now that everything is working type in the command prompt: adb reboot bootloader
now you should see a russian cat fixing a android machine with blue text: "FASTBOOT"
now type "fastboot oem unlock" and it should unlock your phone
now type "fastboot reboot"
--------------------------------------------------------
good, Now you have the bootloader unlocked
--------------------------------------------------------
If you are now put in the setup screen don't do it, just shut down your phone and then when it's shutdown hold on the power button and volume down buttons until you enter fastboot again
now go to this page: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases and download the latest boot only and regular versions
put them both in the adb (tool) folder and type in the command prompt: "fastboot boot boot-recovery.img"
if your phone doesnt do anything (doesn't do anything in the 30s after you input the command) then restart it and get it back in fastboot and type fastboot --set-active=b
and then type the previous command again, if that doesnt work then restart your phone back to fastboot again
and then type fastboot --set-active=a and the command "fastboot boot boot-recovery.img" and it should work
so now you will be in twrp, good!
type "adb push (regular twrp zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push TWRP-Installer-3.2.1-with-Tissot-Manager-2.5.zip /sdcard/"
and then in your phone go to install and you should already be in /sdcard if not then go there and then tap on the zip and swipe on the thing
after it finishes installing go to reboot and then tap on recovery
--------------------------------------------
good now you have TWRP installed!
-------------------------------------------
Now its up to you, do you want to install only root or rom and root? its up to you
Root Only:
Download Magisk (you can also use SuperSU but I strongly recommend magisk)
put it in your adb (tool) folder and type "adb push (magisk's zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push Magisk-v17.1.zip /sdcard/"
go to install, press on the zip file and swipe on the thing and click on restart system at the end
and congrats! you have root on your phone!
Rom:
If were talking about a treble rom then you should follow this guide: https://forum.xda-developers.com/mi-a1/how-to/treble-stock-to-treble-everything-to-t3793734 but if not you can continue using this one
download your favorite rom and download magisk (you can also use SuperSU but I strongly recommend magisk)
also go to opengapps.org choose arm64 and the android version your rom is and I recommend the nano variant
now in twrp tap on Wipe and Advanced Wipe and choose everything there (you dont have to choose micro SDcard tho) and swipe THIS WILL RESET YOUR PHONE AGAIN BUT YOU PROBABLY DONT CARE ABOUT THAT RIGHT NOW
now in the command prompt type: "adb push (rom zip name, remember to put .zip at the end!) /sdcard/"
example:"adb push RR-O-v6.1.0-20180709-Official /sdcard/"
and install it, some roms include gapps and other things in their installation for example: pixel experience. but most roms don't have that
so if you check the xda page and they say nothing about including opengapps in the rom then you should be able to fully follow the next steps.
type "adb push (magisk zip name, remember to put .zip at the end!) /sdcard/" and install it
then type "adb push (opengapps zip name, remember to put .zip at the end!) /sdcard/" and install it
now tap on reboot system and congrats! you just rooted and custom rom-ed your phone!
* "even if you already have adb and fastboot" the reason for this is because that link uses the newest version (or new enough) that is surprisingly not common in other places I downloaded adb and fastboot. the new version adds a new command that is used in the guide if you are experiencing a certain problem
I hope I helped you, if you have any questions or problems post them in the comments
a big THANK YOU
Months ago I rooted and installed a new ROM for first time in my life and, although I read another guides, with them I always break my phone, so I must flash and start again. And your guide, 4 months later, saved me again. I don't know why, really. Maybe because is super friendly. But thank you, again. The only thing I'll add is wtf to do when TWRP asks if install in slot a or b because that's the point I always mess it :'(
Thank you forever
vainille said:
The only thing I'll add is wtf to do when TWRP asks if install in slot a or b because that's the point I always mess it :'(
Click to expand...
Click to collapse
You mean when you flash the rom it asks you which slot to install to?