Cat command help please - Android Q&A, Help & Troubleshooting

Hi,
I have a rooted device, and im using adb su to run the command 'cat /dev/block/mmcblk0>/sdcard/mmcblk0.img' but there is not enough space on the devie for it to complete, the device doesn't have a memory card slot - 'sdcard' is referring to its onboard storage. How can I dump directly to my PC instead of the device?
Thanks

Can't you just use adb pull instead?

reply
Hi, I used the command 'adb pull /dev/block/mmcblk0 c:\' and I get the error '/dev/block/mmcblk0 is not a file or directory' so the pull command wont work for this.
Thanks

aaronmarsh632 said:
Hi, I used the command 'adb pull /dev/block/mmcblk0 c:\' and I get the error '/dev/block/mmcblk0 is not a file or directory' so the pull command wont work for this.
Thanks
Click to expand...
Click to collapse
I get the same error in Windows, but it works in Linux. Hope this helps.

reply
Hi,
Thanks for the reply, I'll try it on my ubuntu system and see what happens, Tnx

Related

android on ubuntu 10.04

i searched and cant seem to find anything on my problem....i connect via mass storage mode , it detects the phone, but for some reason it doesnt let me access the files on the card....in other words ,i cant open them...any help ????
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
I am using it just fine on Ubuntu 10.4
I connect my phone and it is mounted automagically, and I can move the files from/to the phone.
Do you have se_linux installed?
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
thanks, I'll give this a try, let you guys know tomorrow...
Gotta say it works on Ubuntu better then does on Windows XP. You may have some permissions fudged somewhere. Do as the guys above said and let us know.
the3dman said:
try opening the sd card with root access.
Open the terminal and type:
Code:
sudo nautilus /media/
Then just select one of your sd cards.
If this works to access them then you need to change the permissions to allow ubuntu to access them with read and write without root.
Click to expand...
Click to collapse
this is not working for me
aksoutherland said:
It also works just fine for me. It may have to do with permissions on the folders when mounted. From a cli you may try running this command with the phone not connected:
sudo chown -R user:user /media
Just replace "user" with your username.
Then connect the phone and see what happens.
Click to expand...
Click to collapse
nothign when i enter command
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
lqaddict said:
In the phone's USB settings what do you have it set to?
Run
tail -f /var/log/messages
while connecting your phone, and when connected
ls -ltra /media
Post here and we will take a closer look
Click to expand...
Click to collapse
nothing again.....i have it set to ask on connection, then i swithced to mass storage mode....... what else should i do?
error message : "could not display" "the file location is not a folder "
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.
lqaddict said:
Install android-sdk for linux, enable USB debugging under Development settings, try connecting with adb
Code:
/path/to/android-sdk/tools/adb shell
It will drop you to $ prompt
Post here the output of
mount -a
Use
Code:
tags.[/QUOTE]
thanks, I appreciate the help, I will give this a try in the morning
Click to expand...
Click to collapse

[Q] Moonshine & Revone Questions For New Members That Cant Post In The Dev Forums

Like me I'm sure many of you were very surprised to log in today, as most have been doing everyday for the past month or so to find that not one, but two methods for obtaining s-off on the DNA were released within minutes of each other. First Revone and then, coincidentally enough, Moonshine was released minutes later. Somebody didn't want somebody else stealing their thunder I'm guessing. I'm just kidding...I'm sure both sides worked extremely hard on their respective methods and deserve mad props for the time spent on this and for waving a middle finger in the face of Verizon. Having said that I have tried both methods and have been unsuccessful so far at each one. I have to pose my questions here because I'm a new member and the development threads are off limits to me.
I tried the Revone Method first and like many were saying in the actual thread, my phone kept auto rebooting after the ./revone.dna -P step. I tried everything I could think of including all of the suggestions from the other users who finally got it to work by trying different things. Has anyone figured out what is causing the auto reboot? There has to be something specific causing this. One thing I have noticed with my phone is that USB Debugging has been very unreliable as of late. It turns itself off and on at random times and a lot of times the box is checked to enable it but it's not on. I don't know if this is playing a role in the process not working for me. I got the "success" message after every step several times but never actually achieved s-off.
I finally gave up on Revone to try Moonshine. I really didn't want to have to fo this route since I don't know a thing about Linux. I decided to go the boot from flash drive route so I downloaded 32 bit Ubuntu 13.04 iso and used universal USB installer to put it on my drive. I am using an external hard drive that is already formatted to fat32. I did NOT format the drive because I didn't think I had to since it was already fat32. Universal USB Installer was successful in putting Ubuntu on the external drive. I then went into my bios and changed the boot sequence to boot from the external drive first but when I rebooted it just loaded up Windows like normal. What am I doing wrong here? I'm running Windows 7 64bit but it was my understanding that this should not be a problem. Do I have to format and/or partition the external hard drive even though it is already fat32 before putting Ubuntu on it?
I'm dying to get one of these methods working but I'm currently stuck. Any newbies like me that can't post in the Development forums have any ideas as to what is going wrong here or would anyone else like to chime in with their own issues? Thanks in advance. I'm sure I'll get there eventually. :good:
Follow this guide for using an external USB device.
Modify the boot sequence like you were doing before, hopefully you'll get in to Ubuntu.
You say you don't have Linux experience, so I'll simplify the process for you:
Once at the desktop, press Control + Shift + T. This will open the Terminal, which is basically the Linux version of Windows' cmd.exe. Once inside, open up Mozilla Firefox (included) by using the side bar, the icon should be there. Download the version of Moonshine for the DNA, and then switch back to the terminal.
Type in these commands:
cd /home/Downloads
tar -zxf moonshine_dlx_2.06.605.1.tgz
sudo ./distiller
Click to expand...
Click to collapse
And then let Moonshine do its thing.
Modify the boot sequence like you were doing before said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
Oh and one other thing I forgot to mention regarding the revone method...the directory \data\local\temp did not exist on my device prior to me creating it when I pushed the revone.dna to my phone. Should I have had that directory on my phone already?
Sent from my HTC6435LVW using xda premium
I am in a similar boat. I am trying to use revone as I can't get ahold of linux. I downloaded the sdk and revone, moved adb to my C: with the revone file. Everything goes smoothly until i reach the -P step. Every single time it reboots after saying success. If I try to run the -s 0 -u command after that I get failed to map memory, success, revone failed = -1. If I try the -P command again, I get the same message with error code 2. If I try to reboot the bootloader, I get error device not found. I've been at this for hours, and Jerry from Android central even walked me through it, everything ended up successful ans when the bootloader rebooted, it was still locked and s on. Help please?
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Gorilla* said:
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Click to expand...
Click to collapse
I moved adb and its two counterparts in a folder named ADB_WIN, in my C: drive. From there, I typed cmd.exe in the search bar, it opened the command box. I typed in adb push revone.dna /data/local/tmp/ ENTER adb shell ENTER cd /data/local/tmp ENTER chmod 755 revone.dna ENTER ./revone.dna -P and that's where my error started coming in. You can try this, not sure if this right, but if its not, hopefully someone will correct me.
Krispenwah said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
32 bit should work fine. You need a DVD because a CD is too small. ~/Downloads directory is just the current user's downloads folder. So most likely it would get downloaded to there anyway.
Sent from my DNA using Tapatalk 2
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
michaelrager said:
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
Click to expand...
Click to collapse
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
michaelrager said:
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
Click to expand...
Click to collapse
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
michaelrager said:
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
Click to expand...
Click to collapse
add adb.exe to your command, instead of just adb
Gorilla* said:
add adb.exe to your command, instead of just adb
Click to expand...
Click to collapse
Thanks, but the same type of error came up.
michaelrager said:
Thanks, but the same type of error came up.
Click to expand...
Click to collapse
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Krispenwah said:
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
michaelrager said:
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
Click to expand...
Click to collapse
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Krispenwah said:
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Click to expand...
Click to collapse
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
michaelrager said:
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
Click to expand...
Click to collapse
Yeah looks like the file pushed successfully. Now u do "adb shell" then "cd data/local/tmp" then "chmod 755 revone.dna" ....and so forth. Make sure ur adding the extension ".dna" to revone (revone.dna) each time u type it. If u just put revone it won't work ull just get an error

[Q] making bootable usb with dd command

What i'm trying to do is making an ubuntu bootable USB using the terminal:
DD if=/mnt/sdcard/ubuntu.ISO of=/mnt/USB_storage/
When i do that the terminal says : "cannot open for write: is a directory"
what is the solution please?
You may wonder why am i doing this? believe me i have a reason i'm not just playing, i really need to do that
Thank you for your help.

[SCRIPT] ADB, Fastboot and mFastboot directly in Terminal - MacOSX

Hello all
So here I am in my first topic :laugh:
For Mac users can be tough to work with commands, which most of it has to be done in order to perform stuff in our Moto X.
Instead of having to mount virtual machines in order to have access to Windows' stuff. Or the Android SDK has to be installed, browse to specific folders to run commands from them, etc.
We can work directly in our precious Terminal! :victory:
So, I made a little script that will allow Mac users to work directly on Terminal, no matter which folder we are working on. I've included the following files:
adb
fastboot
mfastboot (Motorola's modified version of fastboot)
To Install
Run Terminal (/Applications/Utilities/Terminal.app)
Browse to the folder in which the script resides, i.e., if it’s in Desktop, then type in Terminal “cd Desktop/ADBInstall” (without quotes).
To run the script type “./install.sh” (without quotes).
You will see input on the screen.
That’s it
To Uninstall
You can safely remove the 3 files in one command, just run the uninstall.sh script by following step 1 and 2 from the Install section. Instead of following step 3, type the following in Terminal: “./unistall.sh” (without quotes).
Hope you like it
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
HeroOfTime said:
Hey, thanks for creating this script. However, I am running into a problem. I run ./install.sh, it runs through the install text, but when I try to run an adb command to test it out, I get the following error: -bash: ./adb: No such file or directory. I went into /usr/bin/ and adb, fastboot and mfastboot all show up there and can run when I'm in the directory, but if I'm outside of the directory, it won't run. Any suggestions? Cheers.
Click to expand...
Click to collapse
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
MoisesPerez said:
It's weird, though.
Did it ask for your password? You can force root access by typing: "sudo ./install.sh" instead.
Can you show me your input screen on Terminal after running the installer?
Click to expand...
Click to collapse
Thanks for looking into this for me. Yes, it did ask for my password. Here is what I get after running the installer:
Jareds-MBP:ADBinstall Jared$ ./install.sh
This will install ADB, Fastboot and mFastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/Jared/Desktop/ADBinstall
Copying ADB...
ADB copied to /usr/bin/adb
Copying Fastboot...
Fastboot copied to /usr/bin/fastboot
Copying mFastboot...
mFastboot copied to /usr/bin/mfastboot
You may now run Android Debug Bridge, Fastboot and mFastboot commands
Have a nice day
I'm attaching a screenshot of the output as well, but that is the output I get, which seems correct.
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
MoisesPerez said:
Np! Yes, it seems correct.
So, if you run, let's say, "adb devices" you get the bash error?
Did you try to close session and open a new one?
Regards
Click to expand...
Click to collapse
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
HeroOfTime said:
Exactly. adb devices has been my test command. Yeah, I tried closing out the session, I logged off using the 'exit' command and quit Terminal.
Just odd that it installs fine and shows up in /usr/bin, but I can't get it to work. I am running the beta of OS X Yosemite, but I doubt that would impact anything, since it installs.
Hmmm... Weird stuff.
Click to expand...
Click to collapse
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
MoisesPerez said:
Really weird! I'm using Mavericks, but I also doubt this may cause the script not to work.
Here's my Terminal window running from my user's main folder.
I don't know what else to try man. The only option is to take them out of usr/bin and just create a "work" folder to use them. That's how I started
Best
Click to expand...
Click to collapse
Well thanks a lot for your help. Still a great resource. I will keep playing around with things and maybe get it to work.
Thanks again!
Not a problem my friend. Good luck!
worked great for me on 10.9!
worked for me as well on Yosemite 10.10.1. thanks!
Glad it did! Regards.

ADB + Linux error: device unauthorized

Hi
First of all, sorry for my bad english.
It has been several hours that i'm trying to find a solution to my problem.
I want to wake my nvidia shield via adb command throught network.
I installed android tools on my raspberry pi, and when i connect to it via command line everything work, i can wake up the Shield.
But when i put my command line in a bash script
Code:
#!/bin/bash
adb kill-server
adb start-server
adb connect 192.168.1.38:5555
adb shell input keyevent KEYCODE_WAKEUP
adb kill-server
i have this error :
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I dont know why, when i am execute the command line in a bash script it can't find the rsa key, who is there and should be used.
Any ideas
Thanks in advance.
darkouz said:
Hi
First of all, sorry for my bad english.
It has been several hours that i'm trying to find a solution to my problem.
I want to wake my nvidia shield via adb command throught network.
I installed android tools on my raspberry pi, and when i connect to it via command line everything work, i can wake up the Shield.
But when i put my command line in a bash script
Code:
#!/bin/bash
adb kill-server
adb start-server
adb connect 192.168.1.38:5555
adb shell input keyevent KEYCODE_WAKEUP
adb kill-server
i have this error :
Code:
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I dont know why, when i am execute the command line in a bash script it can't find the rsa key, who is there and should be used.
Any ideas
Thanks in advance.
Click to expand...
Click to collapse
Normally on Windows the first time you turn on usb debugging it will pop up and ask you to accept the adb key. This is what is preventing you, I haven't had to resolve this in Linux, but essentially you need to go to C:\\Users\You\.android\ (in Windows, path will be different in Linux) and copy the file adbkey. Now you need to move it to data/misc/adb/
This will most likely require root or TWRP. Good luck, my friend.
Sent from my KYOCERA-C6745 using Tapatalk
Hi
Thanks for your quick response.
I couldn't make the connection via USB my adb tells me that there is no emulated device. But it work with network And yeah the first time I made the connection, the authorization pop up appeared on my shield. I checked, always authorized this device.
I have the key in /root/.android on my raspberry pi
I don't think I have the access to the /data/ folder in my shield.
But what I don't understand is why when I execute the command in a terminal like that, it work and when it's from the bash script it won't work anymore
darkouz said:
Hi
Thanks for your quick response.
I couldn't make the connection via USB my adb tells me that there is no emulated device. But it work with network And yeah the first time I made the connection, the authorization pop up appeared on my shield. I checked, always authorized this device.
I have the key in /root/.android on my raspberry pi
I don't think I have the access to the /data/ folder in my shield.
But what I don't understand is why when I execute the command in a terminal like that, it work and when it's from the bash script it won't work anymore
Click to expand...
Click to collapse
Option B would be to dump your boot.img and use Assayed's kitchen to add insecure kernel and adb direct root, then the adbkey doesn't need to be on the device.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Option B would be to dump your boot.img and use Assayed's kitchen to add insecure kernel and adb direct root, then the adbkey doesn't need to be on the device.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Yeah as you said in your previous post, i think the solution is to root the nvidia shield cause the rsa key doesny copy itself on the device.
But would you able to explain to me why if i execute those command individually in the terminal it works.
But if i put them all in a bash script that i execute it doesnt work anymore, what's the difference between those two procedure ?
darkouz said:
Yeah as you said in your previous post, i think the solution is to root the nvidia shield cause the rsa key doesny copy itself on the device.
But would you able to explain to me why if i execute those command individually in the terminal it works.
But if i put them all in a bash script that i execute it doesnt work anymore, what's the difference between those two procedure ?
Click to expand...
Click to collapse
How are you executing the script? There's some (hopefully) helpful info here.
https://community.spiceworks.com/topic/433656-command-not-running-in-batch-but-will-run-in-cmd
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
How are you executing the script? There's some (hopefully) helpful info here.
https://community.spiceworks.com/topic/433656-command-not-running-in-batch-but-will-run-in-cmd
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
i m doing : sh script.sh
i m gonna read that, thanks
I found the solution.
I don't really understand why, but adding
Code:
sleep 1
before
Code:
adb shell input keyevent KEYCODE_BACK
resolved the problem, maybe the script execution was to fast for adb to adjust, dont know.
All i know is, that works
darkouz said:
I found the solution.
I don't really understand why, but adding
Code:
sleep 1
before
Code:
adb shell input keyevent KEYCODE_BACK
resolved the problem, maybe the script execution was to fast for adb to adjust, dont know.
All i know is, that works
Click to expand...
Click to collapse
Glad you got it.
Sent from my KYOCERA-C6745 using Tapatalk
sudo rm -rf /home/(username)/.android
that worked with my kde neon machine

Categories

Resources