Quick ADB help! - Thunderbolt Q&A, Help & Troubleshooting

I rooted and now I keep losing su permissions and I can't boot into cwm recovery. I figure something messed up during the process. I guess I should unroot and then try the process again. I'm trying to use the HOWTO Return to stock properly and safely process.
I have adb installed and when I try to do the first step:
(adb push misc.img /data/local/)
It says this:
adb server is out of date. Killing....
* daemon started successfully *
cannot stat 'misc.img': no such file or directory
I'm sure I have a file in the wrong directory? Any help is appreciated!

From your pc before you run adb push did you:
cd c:\path\to\downloads\
?
I cannot the 100 percent certain that is what you need from your description but I however am 80 percent sure.
this is not a signature I type it in every time maybe sent from my phone or my computer

In the newer ADB version you need to have your command promt directed to the platform-tools directory. So, whatever you are trying to push also needs to be within that directory.

Even if you add it to your $PATH?
I haven't updated my sdk in a long long time so I'm not sure
this is not a signature I type it in every time maybe sent from my phone or my computer

If you have an old version of the Android SDK then misc.img should be placed in the tools directory. Personally I have the SDK version 7 and I had to place the files in Platform-tools.

rizzomegav said:
Even if you add it to your $PATH?
I haven't updated my sdk in a long long time so I'm not sure
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
It depends which directory path you have in your $PATH variable. If you have the latest SDK and $PATH is still pointing to "tools" then ADB will not be there... you need to update your $PATH variable to point wherever ADB is located.

stedrocklp said:
In the newer ADB version you need to have your command promt directed to the platform-tools directory. So, whatever you are trying to push also needs to be within that directory.
Click to expand...
Click to collapse
How can I see what version I'm using? I'm new to ADB and was just trying to follow the instructions on the HOWTO so I didn't have to ask a bunch of questions.

My adb is in C:\sdk\platform-tools\
if that helps any. That is also the file that the misc.img file is in

If your adb is in C:\sdk\platform-tools\ did you cd C:\sdk\platform-tools\ first?

Thanks to everyone for the help. I got it figured out last night!

Related

[Q] ADB, Odin & SuperOne Click

Any one out there that can help me understand the last part of Adb.
lol.
I learned how to use Odin and superoneclick.
Now I am on Adb.
I read all I can on Team Whiskeys and XDA website and other googled websites. I installed everything and did the My computer/system properties/advance/Enviroment Variables/Path entries.
I start ADB and then I do in command prompt "adb devices" and whoopie I see my phone.
NOW WHAT?
No body on the instructions or website that I have read goes past that.
How do I push down a Rom to overwrite the system with the new Rom I want to try?
Hope someone out in the Forum has really done this before and will post how they do it.
Need to find someone smart enough to finish the instructions.
Thanks,
CatfishKnight
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adv installed it and I just rebooted and it was installed.
birgertime said:
with adb you can copy files to your sd card or system without ever having to mount your sd card to your phone. that's the main thing I use it for
for instance, I have a rom named Trigger_281.zip on my desktop, to push it I would do
Code:
adb push Trigger_281.zip /sdcard/Trigger_281.zip
you can also pull files by using "adb pull <location of file on phone>"
and so on.
Furthermore if you ever need shell access you can do "adb shell" and run unix commands from console instead of on the phone
Click to expand...
Click to collapse
Thanks for showing me how to push to my phone. Now do I install it. In recovery mode as a zip? I thought adb installed it and I just rebooted and it was installed.
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
birgertime said:
It just moves the file to the phone. You have to flash the file yourself if it is a flashable.
You can push a .jpg file if you want, it doesn't matter, it only moves it.
And I think you're getting confused with the 'adb install' command. You can install NON-system APKs by doing that.
Code:
adb install someprogram.apk
Click to expand...
Click to collapse
I guess I was confused on what ADB could do.
I thought it could push down a Rom and install it onto the phone.
Then I would disconnect it and reboot the phone and I would have the newer rom installed.
I didn't know that it only pushed the ROM onto the sdcard and then I would install the zip from the phone itself.
Finally I got an answer to my question.
LOL.
I have tried on the team whiskey site to and no one answered it. Also all the stuff I read on it really didn't tell me that either.
I really appreciate your answer in helping me understand it.
I am also using Trigger 2.8 like you. But you said you had Trigger2.8.1 saved??
I have only seen Trigger 2.8 today.
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
s15274n said:
^ birgertime is the developer of Trigger. He is already cooking something new in the kitchen.
Click to expand...
Click to collapse
Duhhh... I missed that... LOL. I am brain fried!!! I have installed Odin, SuperOneClick, and ADM. I have be learning all three but was having trouble with understanding what ADB could do. Been reading lots and lots about it all day. Whew. I am tired. Ever instruction got down to connecting and seeing your phone and then it would end there. Finally I got an answer from Birgertime. Thanks.
I have 4 different roms saved to my phone to switch between if I want too. But I love Trigger 2.8 with Overclock v2. Also I am seeing 9 sats out of 11 on my gps. With Overclock v2 and using CPUBoostPro I am right at 2000 with Quadrant.

[Q] ADB, Is a directory help

Hey I'm havging a simple adb issue. I'm trying to push a file via adb to the root of my sdcard but I keep receiving "Failed to copy.......Is a directory. What does that mean, and what could I be doing wrong? Thanks
Here's what I've tried:
adb push cd C:\Users\David\Documents\Capture.JPG /sdcard
adb push C:\Users\David\Documents\Capture.JPG /sdcard
cd C:\Users\David\Documents\
adb push Capture.jpg
filmaker said:
Hey I'm havging a simple adb issue. I'm trying to push a file via adb to the root of my sdcard but I keep receiving "Failed to copy.......Is a directory. What does that mean, and what could I be doing wrong? Thanks
Here's what I've tried:
adb push cd C:\Users\David\Documents\Capture.JPG /sdcard
adb push C:\Users\David\Documents\Capture.JPG /sdcard
cd C:\Users\David\Documents\
adb push Capture.jpg
Click to expand...
Click to collapse
you're typing incorrect paths and commands.
first you need to cd into your tools, mine looks like this:
cd C:\android-sdk\platform-tools
then it'll be in your tools folder and you'd do this:
adb push Capture.jpg /sdcard/Capture.jpg
by the way, you probably coud've simply mounted the phone as a disk drive and transefered the image that way too.
it is in your best interest to learn more about adb, I made a links thread with a few links to adb guides, just click my avatar to find my threads. also if you ever have a quick question feel free to ask in the q+a thread in my sig.
filmaker said:
Hey I'm havging a simple adb issue. I'm trying to push a file via adb to the root of my sdcard but I keep receiving "Failed to copy.......Is a directory. What does that mean, and what could I be doing wrong? Thanks
Here's what I've tried:
adb push cd C:\Users\David\Documents\Capture.JPG /sdcard
adb push C:\Users\David\Documents\Capture.JPG /sdcard
cd C:\Users\David\Documents\
adb push Capture.jpg
Click to expand...
Click to collapse
First cd to the directory that the file you want to push is in. So if its in documents, do:
cd \Users\David\Documents\
Then do : adb push Capture.jpg /sdcard/
That should do the trick, assuming you have adb set up properly to execute commands from any directory (adb.exe must be set in PATH)
Sent from my PG86100 using Tapatalk
il Duce said:
you're typing incorrect paths and commands.
first you need to cd into your tools, mine looks like this:
cd C:\android-sdk\platform-tools
then it'll be in your tools folder and you'd do this:
adb push Capture.jpg /sdcard/Capture.jpg
by the way, you probably coud've simply mounted the phone as a disk drive and transefered the image that way too.
it is in your best interest to learn more about adb, I made a links thread with a few links to adb guides, just click my avatar to find my threads. also if you ever have a quick question feel free to ask in the q+a thread in my sig.
Click to expand...
Click to collapse
Thanks lol that helped a lot
Pushing via ADB - permission denied
Hello!
I accidently bricked my phone. Zenfone 2...
On trying to send file via adb push in order to flash via tethered cwm, i get notice permission denied.
Actual status, fully reset via cwm, no possibility to get rom on device, external sd not detected, otg same.
HELP ME!
Device was rooted und adb allowed before first trial flashing new rom and the actual desaster...
AlexDGF said:
Hello!
I accidently bricked my phone. Zenfone 2...
On trying to send file via adb push in order to flash via tethered cwm, i get notice permission denied.
Actual status, fully reset via cwm, no possibility to get rom on device, external sd not detected, otg same.
HELP ME!
Device was rooted und adb allowed before first trial flashing new rom and the actual desaster...
Click to expand...
Click to collapse
This is an HTC Evo 3D thread. Check this thread for Zenfone 2. If you can't figure it out feel free to send me a message to give you some information.
http://forum.xda-developers.com/showthread.php?t=3096596
Asus Zenfone 2 | Resources all in one thread
Sent from my Evo 3D.
Crashed zenfone 2
Hello!
I accidently bricked my phone. Zenfone 2...
On trying to send file via adb push in order to flash via tethered cwm, i get notice permission denied.
Actual status, fully reset via cwm, no possibility to get rom on device, external sd not detected, otg same.
HELP ME!
Device was rooted und adb allowed before first trial flashing new rom and the actual desaster...

Step by Step for ADB Push

I soft bricked my One. I have a rom to flash but have no idea how to push it via adb. I am downloading the Android SDK now but can someone point me to a very clear step by step tutorial on how to push via adb? Everything I find on the internet seems to be geared to those who are already familiar with command prompts. I am not.
thank you.
I wrote a primer about a year ago
http://forum.xda-developers.com/showthread.php?t=1754018
most of the instructions are universal though.
gunnyman said:
I wrote a primer about a year ago
http://forum.xda-developers.com/showthread.php?t=1754018
most of the instructions are universal though.
Click to expand...
Click to collapse
Thanks for the response, but I need to back up a little bit.
I go to start, type in cmd and then what? I have to switch users?
garment69 said:
Thanks for the response, but I need to back up a little bit.
I go to start, type in cmd and then what? I have to switch users?
Click to expand...
Click to collapse
Can somebody please help me. I have to get this phone up and running today.
garment69 said:
Thanks for the response, but I need to back up a little bit.
I go to start, type in cmd and then what? I have to switch users?
Click to expand...
Click to collapse
I cant get adb installed on my computer I think. When I go to start, cmd and type adb i get "adb is not a recognized command".
Run adb from the directory you installed it. Also on a mac put a./ dot slash in front of the command
garment69 said:
I cant get adb installed on my computer I think. When I go to start, cmd and type adb i get "adb is not a recognized command".
Click to expand...
Click to collapse
When I try and install the ADB exe from the zip file provided in your tutorial it says unable to start because ADBWinApi.dll is missing from my computer.
gunnyman said:
Run adb from the directory you installed it. Also on a mac put a./ dot slash in front of the command
Click to expand...
Click to collapse
Run adb from the directory I installed it? How?
garment69 said:
Run adb from the directory I installed it? How?
Click to expand...
Click to collapse
Find adb.exe in your hard drive. When you downloaded the sdk you unzipped the files somewhere.. I'm assuming you didn't add the path of adb.exe to your environment variables (if you did you would be able to type in adb commands from any directory in cmd prompt).
So navigate to driveletter:\adbdirectory\
From this directory you should be able to type in adb and get feedback
Sent from my HTC One using xda premium
born_fisherman said:
Find adb.exe in your hard drive. When you downloaded the sdk you unzipped the files somewhere.. I'm assuming you didn't add the path of adb.exe to your environment variables (if you did you would be able to type in adb commands from any directory in cmd prompt).
So navigate to driveletter:\adbdirectory\
From this directory you should be able to type in adb and get feedback
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I found the adb.exe and I ran it. A cmd window popped up for a second then vanished. I have no adb directory that I can find.
garment69 said:
I found the adb.exe and I ran it. A cmd window popped up for a second then vanished. I have no adb directory that I can find.
Click to expand...
Click to collapse
You don't run adb as an application, you run it in command prompt as an MS Dos command.
Adb is located in the tools directory of the sdk..not necessarily it's own directory. I was just saying to navigate to where that directory is from within cmd prompt.. I.e if adb.exe was located in c:\android, you would go to "cd c:\android" then run "adb commandhere"
Sent from my HTC One using xda premium
born_fisherman said:
You don't run adb as an application, you run it in command prompt as an MS Dos command.
Adb is located in the tools directory of the sdk..not necessarily it's own directory. I was just saying to navigate to where that directory is from within cmd prompt.. I.e if adb.exe was located in c:\android, you would go to "cd c:\android" then run "adb commandhere"
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
thank you. I found a tutorial which instructed me to put the destination folder into environmental variables. Then I was able to get it to work.
Minor miracle I was able to get it to work!

[Q] Please help- simple mistake... bricked phone

Hi all-
I have unknowingly renamed the framework-res.apk file to framework-res.bak, following the suggestion of a website (who had said to copy the file over, not rename it). I had no idea that would make the phone instantly useless, and render everything inoperative
I was rooted. All I need to do is copy the backup back over, but how?
I am able to get into CMM-based Recovery v5.0.2.7 and can mount the system directory and see it on my PC, but for some reason the framework directory is invisible. There is talk on the web about getting to a prompt and typing:
adb push framework-res.apk /system/framework/framework-res.apk
But how in the world do you get to a prompt? I don't see it on any menu, anywhere and the adb command is unrecognized on my OS.
Hoping I'm not ruined...... thanks for any advice.
Samsung Captivate Glide Android 2.3, Ubuntu
To get ADB, you first have to install the Android SDK.
http://developer.android.com/sdk/index.html
Then, you have to put ADB in the PATH variable.
http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
After that, you can just type adb in the command prompt and it should work.
Hi,
I downloaded the SDK tools and got the adb command, but when I mount the phone with recovery I still don't see any framework directory.
I got to DOS and navigated to the directory where my copied framework-res.apk file was, and ran:
c:\adb\adb push framework-res.apk L:\framework\framework-res.apk
it replied with:
1319 kb/s (7979827 bytes in 5.905s)
However, then I rebooted the phone and it won't get past the SAMSUNG screen at all, it just sits there forever.
- why can't I see the framework directory, even though I have mounted it through CWM based recovery?
- can I see it using the ADB tools?
- has just copying the copied file back over, destroyed the cell phone? I can't possibly see how.
Thanks for any help
OK I found out the problem.
you need to use forward slashes and put the whole pathname in:
C:\adb\adb push framework-res.apk /system/framework/framework-res.apk
Thats assuming you have the adb command in the c:\adb directory.
It seems the phone is working again.
WHEW! Man that file is dangerous. be warned.

Summoning Those with T-Mobile V521!

I'm trying to make an AOSP ROM, and while doing so, I now have a dysfunctional bootloader. If your tablet is rooted, please duplicate the boot.img from your system and share it with me. Would very much appreciate.
Instructions:
Use CMD and paste these 2 lines:
adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img"
adb pull /sdcard/boot.img
Then from ADB directory, upload to somewhere easily accessible.
Does it matter if we have updated to 7.0 or not? I'm rooted and have updated to 7.0 and would be happy to help.
That would actually be a good idea. The ROM is supposed to be 7.0.0 anyways.
Running the first command comes up as " no such file or directory"
Do you already have ADB?
mr_verystock said:
Do you already have ADB?
Click to expand...
Click to collapse
Yep. I do adb devices to make sure it recognizes the tablet and all is good there.
Maybe so I'm the same page i just open up ADB as normal : open the command prompt in my platform tools. I paste the first line in : adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img" I get no file or directory.
Unable to get the dumb file:
adb shell "dd if=/dev/block/platform/soc.0/by-name/boot of=/sdcard/boot.img"
dd: /dev/block/platform/soc.0/by-name/boot: No such file or directory
Edit: does a backup from the recovery could make the task done ? I backup the boot from the TWRP and I get a file of 32Mb with the name: boot.emmc.win
adb shell
cd /dev/block/platform
ls
And tell me the output. I appreciate your help!
mr_verystock said:
adb shell
cd /dev/block/platform
ls
And tell me the output. I appreciate your help!
Click to expand...
Click to collapse
Nothing, it returns an empty result
Unusual... Normally there's soc.0 or msm_sdcc.1.
mr_verystock said:
Unusual... Normally there's soc.0 or msm_sdcc.1.
Click to expand...
Click to collapse
That command never worked for me on this tablet. Yes the default kernels is 32mb.
You can get it from twrp backup as .win and then rename it (if it is not compressed) or use AUT or SuperR's kitchen to obtain it.
Another method would be flashifire>backup.
Im still on MM so I can not help you.
Try these: https://drive.google.com/file/d/0Bz54O_w1LEYpQ1k0aDVHX29NbkE/view?usp=sharing
the rooted files I grabbed from TWRP backup, should be idential to the ones get using dd method.
the stock files I extracted from stock kdz file using WindowsLGFirmwareExtract-1.2.6.1-Release

Categories

Resources