Related
i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse
elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.
cheers for all your help will give this a go "Dont want to back to windows
Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now
glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse
depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
What am doing so wrong its lucky am not bold yet been trying this all day
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"
I have put the file on the desktop ? is that what u mean
All right guys, I know I should search the forum, but I have no time now, this is what's going on: I tried to install CF3D's plugin on my Transformer, but it went darn bad, I can't get past Asus' "powered by tegra" screen, and I need this by tomorrow, for my class, how do I fiz this?! I unlocked it, running TWRP v 0.2.2.3., can't remeber my rom's name but it's a mod of the CleanRom, v3.1 that's all I know. I think I can fix this by re-flashing my rom, but I don't know if I can put files into my SD only with TWRP in my hands, if not is it a real brick?? Please, help me!!!
TheBloodEagle27 said:
All right guys, I know I should search the forum, but I have no time now, this is what's going on: I tried to install CF3D's plugin on my Transformer, but it went darn bad, I can't get past Asus' "powered by tegra" screen, and I need this by tomorrow, for my class, how do I fiz this?! I unlocked it, running TWRP v 0.2.2.3., can't remeber my rom's name but it's a mod of the CleanRom, v3.1 that's all I know. I think I can fix this by re-flashing my rom, but I don't know if I can put files into my SD only with TWRP in my hands, if not is it a real brick?? Please, help me!!!
Click to expand...
Click to collapse
I don't understand "if I can put files into my SD only with TWRP in my hands", you don't have a pc where you can copy the rom to your sdcard? BTW you should be using twrp 2.3.1.0.
I actually have my PC here with me,
but like I said im not sure I can connect it to the pc since it will be on recovery, you know, like an MTP or mass storage, can TWRP do that?
Sent from my R800i using xda app-developers app
TheBloodEagle27 said:
I actually have my PC here with me,
but like I said im not sure I can connect it to the pc since it will be on recovery, you know, like an MTP or mass storage, can TWRP do that?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
You can't take the sdcard out and put it to your pc, copy the rom from pc to sdcard then put it back to your device? or you could use adb to push the file and hope adb is working on your pc.
ADB is working on my PC, but I don't see the TF700T icon under my computer
Sent from my R800i using xda app-developers app
TheBloodEagle27 said:
ADB is working on my PC, but I don't see the TF700T icon under my computer
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
buhohitr said:
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
Click to expand...
Click to collapse
Alright, I'ts getting late, so I'll try it after school after all, I was thinking of using flashtool to flash the room through fastboot, that's how I used to do on my Xperia Play, but I don't know if the program works with asus' tablets... Anyway, thanks a lot man, for trying to help me and all, If it works I'll have a lot to owe u.
TheBloodEagle27 said:
Alright, I'ts getting late, so I'll try it after school after all, I was thinking of using flashtool to flash the room through fastboot, that's how I used to do on my Xperia Play, but I don't know if the program works with asus' tablets... Anyway, thanks a lot man, for trying to help me and all, If it works I'll have a lot to owe u.
Click to expand...
Click to collapse
EDIT: I must be doing something wrong. Where is the adb.exe location? I found one in the Asus Sync folder, is it that one? Second, where do I put this command? I know, in the command prompt, but which folder is it supposed to open?
TheBloodEagle27 said:
EDIT: I must be doing something wrong. Where is the adb.exe location? I found one in the Asus Sync folder, is it that one? Second, where do I put this command? I know, in the command prompt, but which folder is it supposed to open?
Click to expand...
Click to collapse
You don't move the adb.exe, where ever the adb command located, you need to open command prompt and navigate to the adb.exe folder. Asus Sync is located in C:\Program Files\ASUS\ASUS Sync and so is the adb.exe. so open command prompt and type:
cd\ hit enter, this bring you to root Ccomputer displayed C:\>
type:
cd Program Files\ASUS\ASUS Sync hit enter, you're now in the Asus sync folder (this is where your rom.zip should be in also)
computer should displayed:
C:\Program Files\ASUS\ASUS Sync>
now type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
buhohitr said:
You don't move the adb.exe, where ever the adb command located, you need to open command prompt and navigate to the adb.exe folder. Asus Sync is located in C:\Program Files\ASUS\ASUS Sync and so is the adb.exe. so open command prompt and type:
cd\ hit enter, this bring you to root Ccomputer displayed C:\>
type:
cd Program Files\ASUS\ASUS Sync hit enter, you're now in the Asus sync folder (this is where your rom.zip should be in also)
computer should displayed:
C:\Program Files\ASUS\ASUS Sync>
now type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
Click to expand...
Click to collapse
"system could not find specified directory" Heads up ¬¬...
Do you actually have a microSD card inserted into the tablet?
MartyHulskemper said:
Do you actually have a microSD card inserted into the tablet?
Click to expand...
Click to collapse
haha!! sorry for lol! if you don't have the sdcard, you could push it to internal sd.
buhohitr said:
haha!! sorry for lol! if you don't have the sdcard, you could push it to internal sd.
Click to expand...
Click to collapse
Ok then, how do I push ut to the internal SD?
TheBloodEagle27 said:
Ok then, how do I push ut to the internal SD?
Click to expand...
Click to collapse
adb push rom.zip /sdcard/
or
adb push rom.zip /storage/sdcard0/
Edit: Is it working for you yet??
buhohitr said:
adb push rom.zip /sdcard/
or
adb push rom.zip /storage/sdcard0/
Edit: Is it working for you yet??
Click to expand...
Click to collapse
I'm not sure, i'll try it out right now. I guess if it doesn't work it could be a problem with adb, is there any tutorial on how to set it up?
buhohitr said:
Try this,
Copy the rom.zip to the directory where your adb.exe is, then boot your device to twrp (home screen).
On your pc type
adb push rom.zip /Removable/MicroSD then hit enter (this copy the rom.zip from your pc to the root of your microsdcard.
If you see bunch of number and bytes and time then it's working.
Click to expand...
Click to collapse
I tried this, but got this message:
adb server is out of date. Killing...
ADB server didn't ACK
*failed to start daemon*
error:
what does that mean?
TheBloodEagle27 said:
I tried this, but got this message:
adb server is out of date. Killing...
ADB server didn't ACK
*failed to start daemon*
error:
what does that mean?
Click to expand...
Click to collapse
I thought that you already have adb working on your PC, but seems like you don't. You need to download Android SDK and once installed, you can use adb command from this SKD. Here is the link to how install Android SDK. It shouldn't take no more than 10 min. Just download and run the install, only select packages with the word "Android name" should be only 2. Once you done this, adb and fastboot should work fine. You also need Java, but like 99% ppl with a PC should already had Java installed.
http://forum.xda-developers.com/showthread.php?t=1616059
This tool is very important in rooting, recovery, flash stuff to your device. So I recommend you install this and get it working, it will save you a lot of time and headache in the future.
EDIT; If you think you have all the components already installed, you could download the adb/fastboot package here http://forum.xda-developers.com/attachment.php?attachmentid=1403567&d=1350299936 , unzip it to your C drive, you will have a folder called "Install recovery", in this folder there's adb and fastboot command, and then open cmd navigate to this folder and execute adb command line I provide previously see if that works.
buhohitr said:
I thought that you already have adb working on your PC, but seems like you don't. You need to download Android SDK and once installed, you can use adb command from this SKD. Here is the link to how install Android SDK. It shouldn't take no more than 10 min. Just download and run the install, only select packages with the word "Android name" should be only 2. Once you done this, adb and fastboot should work fine. You also need Java, but like 99% ppl with a PC should already had Java installed.
http://forum.xda-developers.com/showthread.php?t=1616059
This tool is very important in rooting, recovery, flash stuff to your device. So I recommend you install this and get it working, it will save you a lot of time and headache in the future.
EDIT; If you think you have all the components already installed, you could download the adb/fastboot package here http://forum.xda-developers.com/attachment.php?attachmentid=1403567&d=1350299936 , unzip it to your C drive, you will have a folder called "Install recovery", in this folder there's adb and fastboot command, and then open cmd navigate to this folder and execute adb command line I provide previously see if that works.
Click to expand...
Click to collapse
All there is in here is a .cmd file, no adb or nothing, I tried to use the command line you provided me, but all I get is:
adb server is out of date. Killing...
*daemon started succesfully*
Protocol Failure
Edit: I also downloaded the Android SDK Manager and downloaded the two tools
TheBloodEagle27 said:
All there is in here is a .cmd file, no adb or nothing, I tried to use the command line you provided me, but all I get is:
adb server is out of date. Killing...
*daemon started succesfully*
Protocol Failure
Edit: I also downloaded the Android SDK Manager and downloaded the two tools
Click to expand...
Click to collapse
If you go here http://forum.xda-developers.com/atta...7&d=1350299936 download the zip file then unzip to your drive. In this new folder you should see adb.exe and fastboot.exe and a few dll files. Do you see them??? Make sure your anti-virus doesn't strip the files.
buhohitr said:
If you go here http://forum.xda-developers.com/atta...7&d=1350299936 download the zip file then unzip to your drive. In this new folder you should see adb.exe and fastboot.exe and a few dll files. Do you see them??? Make sure your anti-virus doesn't strip the files.
Click to expand...
Click to collapse
Oh man, this sucks, it says 404 page not found, didn't you cpy the wrong link?
I used a Super Wipe Full and my new ROM was in the internal storage (Not on SD) So I lost everything plus the new ROM that I should use to install now.
So I have nothing to install on it now. It doesn't start up, the only thing I can do is go at ClockworkMod (Vol+Down) and travel there but doing nothing very useful.
How can I copy and past my ROM to the SD?
From windows.
Thank you, sorry I am dumb, =/
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
+1 Been there done that.
D
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
Thanks, gonna try later and edit here.
Edit. 1
So for Nakeddrivers should I download this one?
http://forum.xda-developers.com/showthread.php?t=1514942
And do what this guy says?
http://forum.xda-developers.com/showthread.php?t=2139767
Thank you.
frederuco said:
You need to boot to CWM, then connect it to your PC using the charger cable.
Update the drivers to use the NakedDrivers.
Then get a copy of ADB.exe from the android SDK.
Download the ROM you want to flash and put it into the same directory as your ADB.exe file.
Open a command prompt and use the "cd" command to get to the directory with ADB.exe.
Then type this:
adb push ROM.zip /sdcard/
Assuming your ROM is called ROM.zip.
Then you can flash the ROM from CWM.
Click to expand...
Click to collapse
I got a problem, when I type "adb push "ROM".zip /sdcard/"
It says: (by the first try)
"adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:"
(Second and other)
"adb server is out of date. killing...
* daemon started successfully *
protocol failure"
I downloaded this SDK:
http://developer.android.com/sdk/index.html
And this NakedDrivers:
http://forum.xda-developers.com/showthread.php?t=1514942
Help please =/
Did you get the ADB drivers installed?
I often get the same errors on ADB but it should eventually work.
What happens if you type:
adb devices
It should find your tablet.
frederuco said:
Did you get the ADB drivers installed?
I often get the same errors on ADB but it should eventually work.
What happens if you type:
adb devices
It should find your tablet.
Click to expand...
Click to collapse
After 3 errors with "adb devices" I got this:
"adb server is out of date. killing...
* daemon started successfully *
list of devices attached
37c624242616657 recovery"
What now?
type this:
adb shell
ls -l
see what the ouput is. Is there a sdcard directory listed?
If so, type exit so you are out of the ADB shell, then type:
adb push ROM.zip /sdcard/
frederuco said:
type this:
adb shell
ls -l
see what the ouput is. Is there a sdcard directory listed?
If so, type exit so you are out of the ADB shell, then type:
adb push ROM.zip /sdcard/
Click to expand...
Click to collapse
With "adb shell" I got few errors listed above and then this:
"adb server is out...
* daeomon started successfully *
~ #"
Thats all.
What happens if you type "ls -l" at the # prompt?
frederuco said:
What happens if you type "ls -l" at the # prompt?
Click to expand...
Click to collapse
Got a lot of suff:
http://img267.imageshack.us/img267/2112/31377010.jpg
If this helps, my deviece is a Asus Transformer TF101
I am trying to install the android revolution HD 3.6 rom
Filipebergami said:
Got a lot of suff:
http://img267.imageshack.us/img267/2112/31377010.jpg
If this helps, my deviece is a Asus Transformer TF101
I am trying to install the android revolution HD 3.6 rom
Click to expand...
Click to collapse
Perfect.
Now, download the android revolution HD 3.6 ROM if you have not done so. rename it to ROM.zip and put it in the c:\dev\adt\sdk\platform-tools directory.
Next, at the c:\dev\adt\sdk\platform-tools> prompt type:
adb push ROM.zip /sdcard/
It should then push the file ROM.zip to your internal SD card directory. It will say how many bytes were pushed succesfully when it finishes. If you get an error that it failed to start the daemon, just keep issuing the adb push ROM.zip /sdcard/ command until it works.
frederuco said:
Perfect.
Now, download the android revolution HD 3.6 ROM if you have not done so. rename it to ROM.zip and put it in the c:\dev\adt\sdk\platform-tools directory.
Next, at the c:\dev\adt\sdk\platform-tools> prompt type:
adb push ROM.zip /sdcard/
It should then push the file ROM.zip to your internal SD card directory. It will say how many bytes were pushed succesfully when it finishes. If you get an error that it failed to start the daemon, just keep issuing the adb push ROM.zip /sdcard/ command until it works.
Click to expand...
Click to collapse
YES !!!
After about 30 tries it worked, I got a bit scared when after * daemon thingy * got no answer for few minutes, but I manage to install it throught CW.
Thank you a lot.
Description
After always having to search for the latest versions of Android's ADB and Fastboot tools instead of downloading the whole Android SDK for just 1 mb in a few files, I decided to make my own MSI installer using the latest versions of ADB and Fastboot.
You can install it wherever you want and it will work from any path in the command prompt. The installer will append the installation folder location to the system PATH variable, allowing you to run ADB or Fastboot without you having to change the command prompt path to where they are installed.
This installer is 32-bit and 64-bit compatible.
Usage
The default installation path is C:\ADB so you can easily add your flashable files in there.
After installing Android ADB Fastboot you can open a command prompt and type adb or fastboot commands right away, you don't need to change paths. Keep in mind that you need admin privileges, though.
To open a command prompt with administrator rights on Windows 8, just right click on the bottom left corner of the screen or use the Win+X shortcut and then click on Command Prompt (Admin).
Click to expand...
Click to collapse
If you have Windows 7 or Vista, the quickest way to do it is to type CMD on the Start Menu search box and press Ctrl+Shift+Enter instead of just pressing Enter.
Click to expand...
Click to collapse
Requisites
You need to have ADB Debugging under Developer Options on your device. You also need the drivers for every device you want to use with ADB installed and working.
You can type adb devices on a command prompt. If your device is listed, the drivers are working and good to go for ADB and Fastboot use.
Click to expand...
Click to collapse
Download
I will always check the ADB version whenever a new Android SDK is released and I will update my installer when needed.
The download link and screenshots are on my website.
http://rubenalamina.mx/custom-installers/android-adb-fastboot/
Latest version of the installer: 1.5 (ADB 1.0.36) updated on 2016.09.21
Thanks mate, it really help people with lacks internet connection like mine
Sent from my WT19i using xda app-developers app
Installer updated to version 1.2 with the new ADB and Fastboot included in Android SDK 23.0.2.
Installer updated to version 1.3 based on the Android SDK 24.0.2.
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Nightmare-Rex420 said:
no matter what i do it stills says ABD is not reconizedf as an internal or external command. i even downloaded the whole stinking dev kit to make sure nothing missing in these little installers. made sure that a path was put still dose NOT work :/. and yes im running cmd prompt as adminastrator.
Click to expand...
Click to collapse
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
ajua said:
Have you tried running it from the C:\ADB path just in case? Maybe try PowerShell instead of the command prompt. I don't really know what else you can try if even the SDK is not working for you.
Click to expand...
Click to collapse
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Nightmare-Rex420 said:
yes ive been trying both Shift open command prompt here, and aslso left click run as adminastrator and CD c:/abd both still says abd not reconized.
Click to expand...
Click to collapse
Try using PowerShell. Also, see if you are able to run the ADB that comes with the SDK but run it from the folder where it is located.
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.