After doing a bad flash, I wiped my system data for some reason. I want to flash the rom again but ADB won't push files
It says that device hasn't been found in the terminal. I know for sure that not only do I have USB drivers installed, but my ADB, JDK is also installed. The rom file is in my platform-tools folder. Also, I CD'ed to the platform-tools because that is where ADB is located. Any help is appreciated.
Related
So I'm just now installing the SDK on my gf's computer and it puts ADB in /tools and Fastboot in /platform-tools. Fastboot refuses to run.
Code:
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem.
What's this about?? I downloaded the sdk.zip (the installer exe wanted me to install the java jdk, which I definitely don't need) and extracted it to C:\android-sdk-windows. Then I ran the SDK manager and installed the platform tools. Should I copy the platform-tools contents into tools or the other way around?
I haven't set the environment variable in system properties yet because I'm not sure which directory to use. The computer has the drivers for my phone and adb works fine. I booted into fastboot mode and it installed drivers.
Why would they give me an SDK with a non-working fastboot? Kind of irritated...
Copied contents of \platform-tools into \tools (DID NOT REPLACE ANY FILES!) and now everything works.
I would still like to know what was going on with this, and is there any advantage to adding the environment variable? I'd like to be able to run commands from any directory if possible, instead of having to cd all over the place.
i have a slight problem. i grabbed the ubuntu touch alpha and went in to recovery, loaded it (according to thread instructions) but ended up with a bootloop.
in the end i thought "lets just put another rom back on for now" and then realised i had deleted the other rom from the sdcard! so i'm stuck with it not booting in to ubuntu, and not able to get another rom on as it doesn't boot in.
can i connect to the internal sdcard area myself by plugging the usb in to the pc or something?
i have twrp loaded as recovery
thanks
ah, TWRP adb sideload to the rescue!
problem
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
partti86 said:
my problem is stuck in boot screen after i did super wipe full what should i do? i have cwm 5.5.0.4. i try flash from sd put it says no files found
Click to expand...
Click to collapse
The issue, Superwipe wipes the internal /sdcard/ and also this is where it flashes from.
You need to boot to recovery and then use ADB to push files to the sdcard.
If you have never used ADB, it can be a bit daunting.
First, you need adb from the Android SDK. It is a big file for the few you need. I have a copy of the relevant ADB files here: https://db.tt/b9dQ6xzp
Unzip this to c:\adb folder on windows. If you are using Linux, it should already have adb in the /usr/bin/ folder.
Next, you need the Universal Naked Drivers: http://forum.xda-developers.com/attachment.php?attachmentid=1934814&d=1367674531
Unzip these to c:\universal_naked_drivers
Boot to CWM and then plug in your USB cable. It should show a new device found. It may find 2, an MTP and then there should be another either Unknown device or an Android ADB device. Right click and update the driver. Be sure to search for driver, then tell it you want to pick from a list. Hit the Have Disk button and then hit the browse button and browse to c:\universal_naked_drivers and hit OK. It should show you a driver to select and hit OK. If you are using Win 8, there is an additional step that is required to used non-signed drivers.
Once the driver is updated, download the zip file you want to flash on your PC. I assume it is a ROM.zip file for this example. Place this file in the c:\adb folder and call it ROM.zip (can be named something else, but this is what we will use for this example).
Now, open a command prompt and execute the following:
Code:
> [B]c:[/B]
c:\> [B]cd c:\adb[/B]
c:\adb> [B]adb devices[/B]
It will probably say some messages about the daemon is not running, restarting adb.
Then it should show a list. There should be some numbers followed by "recovery"
If no devices are shown, check that your ADB device is showing in the Device Manager.
Once you see it in the adb devices list, continue:
Code:
c:\adb> [B]adb push ROM.zip /sdcard/[/B]
successfully pushed xxx bytes
c:\adb>
At this point you should now see the ROM.zip file on the internal storage in CWM to allow you to install it.
Choose to install the file then reboot (not to recovery). You have to let it flash the file (progress bar will show). Once the screen goes black and the progress bar disappears, it should now boot to your ROM..
If your ROM requires a custom kernel and/or GAPPS to be flashed, use the same procedure to push your kernel.zip and GAPPS.zip to the /sdcard/ directory.
mk2media said:
ah, TWRP adb sideload to the rescue!
Click to expand...
Click to collapse
Can you explain what you did please? what is adb sideload?
hello guys, i just installed a nightly cm 11 on my LG G2 D805, i used a trick to convert it to D802, so its ok, but when i install the zip, i got stuck in the bootloader, i already wiped the data and cache, system, etc, the problem is i cant download and install another zip because the LG G2 has no SD ! ...i cant add more files to install, i need help, how i can unbrick my phone? please!
Can you enter the download mode?
This is easily solvable, I've had a few issues like you since the Nexus 5 does not have an SD Card slot either.
What you'll need to do is set up ADB, Google it if you don't have it.
Then go to where you have the contents (adb files). Or you can go into cmd (command promt) and type in "cd your/adb/folder/destination" if you haven't done the "cd" method simply go into the adb folder. And open a cmd window there, once open. Boot your device into recovery mode and plug in your cable to your PC. So that it detects your device.
Then in the command prompt window type the following command - "adb devices" (This will run adb and it'll check to see if adb is properly installed, if your device does not pop up, make sure you cable is in properly. If it still doesn't show, you will have to install the drivers for your device again... Properly).
Now it should list your device, go into the G2 section and download the preferred rom.
Once downloaded simply type this in the command prompt window.
Adb push path/to/rom.zip /sdcard
Eg - adb push c:/user/user/Downloads/cm11.zip /sdcard
Now this should push the .zip to your internal memory, in the recovery mode (after adb has down its job). Simply wipe data and install the .zip c:
Your device should work.
If I helped, don't hesitate to hit that Thanks button
Hey,
I've installed TWRP on my S6 and wiped my device but then I realized that I forgot to safe the custom ROM on the sdcard.
Is there a possibility to safe it on the sdcard without a system on it?
Greetings
iRemix
S6 does not have a sdcard in the first place
[iRemix] said:
Hey,
I've installed TWRP on my S6 and wiped my device but then I realized that I forgot to safe the custom ROM on the sdcard.
Is there a possibility to safe it on the sdcard without a system on it?
Greetings
iRemix
Click to expand...
Click to collapse
twrp has support for adb so you can adb push files to your device if you accidentally wiped system and the internal memory.
1. make sure you have adb and the samsung adb/fastboot drivers installed. as well as adb,.
2. if adb is not set up as a system path, copy the rom in the folder where adb is located
3.. open a command prompt window where the rom and adb are located (if adb is setup with system path you can open a command prompt window where the rom is located. (shift + right click will give you the option to open a command prompt within the current folder.)
4. within the command prompt use the command adb push romfilename.zip /sdcard/
5. copying may take a few minutes but will give you a confirmation with bytes in copied. the rom will be on the root of your sdcard. and you can then flash.
i have installed so many different adb/fastboot packages how do i get rid of all the installs and install the latest set only? when i download the platform latest tools for windows what do i do with the files inside the archive?
stackz07 said:
i have installed so many different adb/fastboot packages how do i get rid of all the installs and install the latest set only? when i download the platform latest tools for windows what do i do with the files inside the archive?
Click to expand...
Click to collapse
I set the sdk up at some point but now I just download the platform tools from Google instead of updating from the Android Studio app:
Download platform tools
extract
navigate to your platform-tools directory (something like c:/user/you/AppData/Local/Android/SDK)
rename the existing folder to platform-tools-bak
paste new platform-tools folder
Not sure how you would end up with multiple adb/fastboot files, should just have 1 platform-tools folder in the SDK folder (plus a backup if you're like me) and only one adb.exe and one fastboot.exe in there.
How does that update the driver? Just having the folder on your computer you computer runs the latest adb? That doesn't sound right
stackz07 said:
How does that update the driver? Just having the folder on your computer you computer runs the latest adb? That doesn't sound right
Click to expand...
Click to collapse
Assuming you already have adb setup and you are just updating your adb and fastboot this is exactly what to do. It sounds like you were updating these through Android Studio, correct? You can also continue to do that; it will download the new platform-tools and replace the files with the new ones. If you are not developing apps and just need fastboot/adb then there's really no need for Android Studio so like I said, I prefer to just download and replace the files manually. I think you are confusing fastboot and adb with the basic android usb driver. The driver recognizes your phone, then adb.exe and fastboot.exe send commands to it.