[ROOT/UNLOCK BOOTLOADER/RECOVERY]LG-D320/N/L70 devices - Android General

Quick guide for people having trouble rooting/unlocking bootloader and custom recovery LG-D320/N/L70 devices running 4.4.2 with a new 3.4.0+ kernel
This way is easier then any root method and NO PC is required
Simple, straight forward, takes not even 5 minutes.
First download and install these 3 apps.
CPU Benchamark
Terminal Emulator
KingoRoot.apk
Second, download this zip file and extract the "mrw" folder to your phones internal memory(/sdcard)
ReplaceKingoRoot.zip
Third, open CPU Benchtest app and press the "stress test" box, then minimize the app and open Kingo ROOT app and press the "ROOT" bubble
Fourth, Kingo ROOT says your device is rooted open Terminal Emulator and type the following
Code:
su
Your device will ask if Terminal Emulator can be granted root permissions, allow it then proceed to type the following
Code:
sh /sdcard/mrw/root.sh
Then SuperSU will automatically open and ask to update SuperSU binaries, select the "update" box and when it asks you how you want to update it select the "normal" box
Five, Restart your phone when SuperSU says you need to restart for the update to take effect
Now, unlocking the bootloader and flashing a custom recovery, fortunately i made a tool for this with the required files.
simply download this, unzip it onto the desktop and run LGTOOL.BAT by double clicking it and follow the instructions.
LG TOOL BY RICKY DIVJAKOVSKI
ENJOY GUYS
Credits:
jeffta74
wanako1
MrW0lf

updated.

I'm AndroidAddict aka MikeHoncho at AF btw. Glad to see someone post something even though we never got a forum here

AndroidAddict||AA said:
I'm AndroidAddict aka MikeHoncho at AF btw. Glad to see someone post something even though we never got a forum here
Click to expand...
Click to collapse
every device should be able to gain full flexibillity, no matter how old, how new, how popular or unpopular and device i get my hands on will gain full access
time to make a custom rom now

I think everything is done "custom ROM" wise. AOSP, cm11, cm12, carbon (by me) and other ROMs

AndroidAddict||AA said:
I think everything is done "custom ROM" wise. AOSP, cm11, cm12, carbon (by me) and other ROMs
Click to expand...
Click to collapse
ofcoarse its done custom rom wise, you can modify a rom with root access but to safely modify a rom and test recovery is mandatory

Terminal emulator not working
Thx for this guide.
terminal emulator can't install SuperSU.
Here's the log, whats wrong?
Tried also to install supersu manually, but can't update it so is absolutely useless.
[email protected]:/ $ su
l_SD/ReplaceKingoRoot/mrw/root.sh <
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
---------------------------------------
----- UPDATED BY RICKY DIVJAKOVSKI ----
---------------------------------------
Failure
Failure
rm failed for /system/app/KingoUser, No such file or directory
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[20]: cat: sdcard/mrw/busybox: No such file or directory
rm failed for /system/xbin/ku.sud, No such file or directory
rm failed for /system/xbin/su, Operation not permitted
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[33]: can't create /system/xbin/su: Permission denied
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[35]: cat: /sdcard/mrw/su: No such file or directory
Unable to chown /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
daemonsu: invalid option -- d
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
rm failed for /data/data-lib/com.kingoapp.root, No such file or directory
rm failed for /data/data-lib/com.kingouser.com, No such file or directory
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, No such file or directory
rm failed for /data/data-lib/com.kingroot.kinguser, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/su, Operation not permittedrm failed for /system/bin/ddexe, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_INVALID_URI]
rm failed for /system/usr/iku, No such file or directory
rm failed for /dev/reportroot, No such file or directory
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
rm failed for /sdcard/Kingroot, No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
[email protected]:/ #ll

Ggcost said:
Thx for this guide.
terminal emulator can't install SuperSU.
Here's the log, whats wrong?
Tried also to install supersu manually, but can't update it so is absolutely useless.
[email protected]:/ $ su
l_SD/ReplaceKingoRoot/mrw/root.sh <
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
---------------------------------------
----- UPDATED BY RICKY DIVJAKOVSKI ----
---------------------------------------
Failure
Failure
rm failed for /system/app/KingoUser, No such file or directory
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[20]: cat: sdcard/mrw/busybox: No such file or directory
rm failed for /system/xbin/ku.sud, No such file or directory
rm failed for /system/xbin/su, Operation not permitted
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[33]: can't create /system/xbin/su: Permission denied
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[34]: can't create /system/xbin/daemonsu: Text file busy
/storage/external_SD/ReplaceKingoRoot/mrw/root.sh[35]: cat: /sdcard/mrw/su: No such file or directory
Unable to chown /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
daemonsu: invalid option -- d
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
--daemon start the su daemon agent
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-u display the multiuser mode and exit
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
rm failed for /data/data-lib/com.kingoapp.root, No such file or directory
rm failed for /data/data-lib/com.kingouser.com, No such file or directory
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.kinguser, No such file or directory
rm failed for /data/data-lib/com.kingroot.kinguser, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
rm failed for /system/bin/.usr/.ku, No such file or directory
rm failed for /system/bin/rt.sh, No such file or directory
rm failed for /system/bin/su, Operation not permittedrm failed for /system/bin/ddexe, No such file or directory
rm failed for /system/bin/install-recovery.sh, No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Failure [INSTALL_FAILED_INVALID_URI]
rm failed for /system/usr/iku, No such file or directory
rm failed for /dev/reportroot, No such file or directory
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
rm failed for /sdcard/Kingroot, No such file or directory
Error type 3
Error: Activity class {eu.chainfire.supersu/eu.chainfire.supersu.MainActivity} does not exist.
[email protected]:/ #ll
Click to expand...
Click to collapse
Yea i have the same problem with this i've done everything right step by step but seems cant find the location of the root can anyone help me or the topic is dead ?

Related

[Resolved] [Q] adb install results in "/sbin/sh: pm: not found"

I am using a rooted HTC G2 with Clockwork recovery and Cyanogenmod 6.1.1.
I broke my launcher, ADW EX, using Ninjamorph; the phone now gets stuck on the boot animation.
My planned solution was to use adb install to restore a backup of ADW EX.
Using adb pull I pulled a backup of ADW EX and placed in C:\
I mounted /system and /data in recovery
Using adb from recovery I entered adb shell and removed the broken ADW EX with:
rm /data/app/org.adwfreak.launcher-2.apk
Next, I exited adb shell and entered:
adb install C:\org.adwfreak.launcher-2.apk
This generated the error:
/sbin/sh: pm: not found
I cannot get past this error and successfully install the application. I am learning as I go, any direction or assistance is welcome. I miss my Android
Solved
In case any other doofus' run into this situation.
As I have now learned, the "adb install" command will not work from recovery.
Because I had broken my launcher, and I had no alternative launchers installed, there was no launcher to hand-off to after booting; the result was an endless boot animation. Calls and notifications could still be received, etc. Most importantly, the phone was no longer in recovery and "adb install" could be used.
adb install C:\org.adwfreak.launcher-2.apk
Press "home"
Fixed.
hi,
in adb shell type:
cd /system/bin
cp pm ap_process /sbin/
exit
and now try again to install/uninstall the app.
hosseinb said:
hi,
in adb shell type:
cd /system/bin
cp pm ap_process /sbin/
exit
and now try again to install/uninstall the app.
Click to expand...
Click to collapse
I am getting error at second command
/system/bin >> cp pm ap_process /sbin/
cp pm ap_process /sbin/
cp: can't stat 'pm': No such file or directory
cp: can't stat 'ap_process': No such file or directory
can you tell why
nialexme said:
I am getting error at second command
/system/bin >> cp pm ap_process /sbin/
cp pm ap_process /sbin/
cp: can't stat 'pm': No such file or directory
cp: can't stat 'ap_process': No such file or directory
can you tell why
Click to expand...
Click to collapse
Sorry for my delay;
It's because the files (pm & ap_process) do not exist in /system/bin , try to locate them by "find" command:
adb shell
#find / -name ap_process
good luck
~ # find / -name ap_process
find: /sys/kernel/slab/L2TP/IP: No such file or directory
~ # exit
and now ?!!
kb667 said:
~ # find / -name ap_process
find: /sys/kernel/slab/L2TP/IP: No such file or directory
~ # exit
and now ?!!
Click to expand...
Click to collapse
Do you have root access? Have you installed busybox?

How to temp root nextbook 7p running 2.3.3

Figured out how to temp root my friends nextbook and get titanium backup working. Basically i followed this thread
http://forum.xda-developers.com/showthread.php?t=1173690
Download the htc flyer 16/32gb file and use that one. After you run the Run_ME_fre3vo_Root.bat File go to terminal and type su then hit enter.
You will get the notice that terminal has been granted superuser permission and you will be all set. Download titanium backup and install it .But remember everytime you reboot you will have to run the .bat again.
Thanks to Eugene373 for creating this tool. And thanks to #Teamwin
Htc Evo 4g rooted s-off cyanogenmod 7
Htc Flyer 16gb wifi rooted s-off Flyhigh rom
If i helped in anyway feel free to hit the thanks button
Or just use z4root. That's what I did on my Next6 while dumping the stock image.
By chance could I get a copy of the Next7's stock image?
temp root
tried z4root, i had no luck with gingerbread.
temp root
here is the system dump for nextbook7p
http://www.multiupload.com/6BY8BVS5BJ
Ok i followed the steps on there but im kinda confused on hoqw you managed to get it to work. The next book 7p always shows as a mountable disk when connected to my computer. On the link it says u need to change it to charge only. I tried ignoring that because the nexbook 7p cant charge via usb. But when i click run_me_fr3vo_root the terminal opens and it says wait-for-devices and thats all. So would u kind giving a more detailed explanation? Id aporeciate it alot cause ive been wanting to root this thing foreverrrrr (3 months lol)
krisf29 said:
Figured out how to temp root my friends nextbook and get titanium backup working. Basically i followed this thread
http://forum.xda-developers.com/showthread.php?t=1173690
Click to expand...
Click to collapse
This method did not work with my NextBook 7:
Code:
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb push fre3vo /data/local/tmp
3188 KB/s (9796 bytes in 0.003s)
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /data/local/tmp/fre3vo
C:\RW_HTC_Flyer(1)>adb shell /data/local/tmp/fre3vo
fre3vo by #teamwin
Please wait...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell /data/local/tmp/fre3vo
fre3vo by #teamwin
Please wait...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell sleep 5
C:\RW_HTC_Flyer(1)>adb remount
remount failed: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell mount -o rw,remount rootfs /
mount: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell mount -o remount,suid /dev/block/mmcblk0p29 /data
mount: Operation not permitted
C:\RW_HTC_Flyer(1)>adb shell rm -r /vendor
rm failed for /vendor, Read-only file system
C:\RW_HTC_Flyer(1)>adb shell mkdir /system/vendor
mkdir failed for /system/vendor, Read-only file system
C:\RW_HTC_Flyer(1)>adb shell mkdir /system/vendor/bin
mkdir failed for /system/vendor/bin, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /system/vendor
Unable to chmod /system/vendor: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 777 /system/vendor/bin
Unable to chmod /system/vendor/bin: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/bin/sh
Unable to chmod /system/bin/sh: Read-only file system
C:\RW_HTC_Flyer(1)>adb push sqlite3 /system/vendor/bin
failed to copy 'sqlite3' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push libext4_utils.so /system/lib
failed to copy 'libext4_utils.so' to '/system/lib/libext4_utils.so': Read-only f
ile system
C:\RW_HTC_Flyer(1)>adb push libfuse.so /system/lib
failed to copy 'libfuse.so' to '/system/lib/libfuse.so': Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 655 /system/lib/libext4_utils.so
Unable to chmod /system/lib/libext4_utils.so: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 000 /system/lib/libfuse.so
Unable to chmod /system/lib/libfuse.so: No such file or directory
C:\RW_HTC_Flyer(1)>adb push default.prop /default.prop
failed to copy 'default.prop' to '/default.prop': Read-only file system
C:\RW_HTC_Flyer(1)>adb push init.rc /init.rc
failed to copy 'init.rc' to '/init.rc': Read-only file system
C:\RW_HTC_Flyer(1)>adb push init.flyer.rc /init.flyer.rc
failed to copy 'init.flyer.rc' to '/init.flyer.rc': Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /default.prop
Unable to chmod /default.prop: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /init.rc
Unable to chmod /init.rc: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /init.flyer.rc
Unable to chmod /init.flyer.rc: No such file or directory
C:\RW_HTC_Flyer(1)>adb push fixit /system/vendor/bin
failed to copy 'fixit' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push su /sbin
failed to copy 'su' to '/sbin/su': Permission denied
C:\RW_HTC_Flyer(1)>adb push su /system/vendor/bin
failed to copy 'su' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb push busybox /system/vendor/bin
failed to copy 'busybox' to '/system/vendor/bin': No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /sbin
Unable to chmod /sbin: Read-only file system
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /sbin/su
Unable to chmod /sbin/su: Permission denied
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/su
Unable to chmod /system/vendor/bin/su: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/fixit
Unable to chmod /system/vendor/bin/fixit: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 4755 /system/vendor/bin/busybox
Unable to chmod /system/vendor/bin/busybox: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell chmod 755 /system/vendor/bin/sqlite3
Unable to chmod /system/vendor/bin/sqlite3: No such file or directory
C:\RW_HTC_Flyer(1)>adb shell /system/vendor/bin/busybox --install -s /system/ven
dor/bin
/system/vendor/bin/busybox: not found
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/ls
rm failed for /system/vendor/bin/ls, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/reboot
rm failed for /system/vendor/bin/reboot, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/chmod
rm failed for /system/vendor/bin/chmod, No such file or directory
C:\RW_HTC_Flyer(1)>adb shell rm -r /system/vendor/bin/chown
rm failed for /system/vendor/bin/chown, No such file or directory
C:\RW_HTC_Flyer(1)>adb install Superuser.apk
5818 KB/s (196640 bytes in 0.033s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\RW_HTC_Flyer(1)>adb install androidterm.apk
6039 KB/s (92780 bytes in 0.015s)
pkg: /data/local/tmp/androidterm.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
C:\RW_HTC_Flyer(1)>adb shell ln -s /system/vendor /vendor
link failed File exists
C:\RW_HTC_Flyer(1)>adb wait-for-device
C:\RW_HTC_Flyer(1)>adb shell sync
C:\RW_HTC_Flyer(1)>pause
Press any key to continue . . .
Same here. I tried all of the methods that I could come across on the web with no luck. You would think that it would be a way to root the original factory rom and just flash the device with the rooted rom. That seems to be the only way.
pls help me to get it rooted
i tried Zroot and gingerbreak without sucess
after i tried superoneclick
without sucess
i have a bextbook next8P
pls help

[Q] Unable to install Ubuntu on rooted Nook (1.3)

I have been unable to properly load Ubuntu on my rooted Nook (1.3). I have searched the forum and found similar questions, but the resolution appeared to be using the "su" command (which I have done at all times). I have followed all of the instructions from the "How To Install Ubuntu Linux On Your Nook Color" link at addictivetips. However, I receive the errors below:
--------------------------------------------
# sh ./ubuntu.sh
modprobe: chdir(/lib/modules): No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
rm failed for -f, No such file or directory
mkdir failed for /data/local/mnt, File exists
rm failed for -/system/bin/mountonly, No such file or directory
chmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at NexusOneHacks.net
To enter the Debian Linux console just type 'bootubuntu'
-------------------------------------------------------
After this oocurs, when I type "bootubuntu," everything appears to function correctly -- until I attempt to use "apt-get update" or "apt-get install tightvncserver." I receive several "Failed to fetch" errors. The same happens for "apt-get install lxde." When I use the command "vncserver –geometry 1024x600," I receive the error message "bash: vncserver: command not found"
My nook is properly rooted with manualnooter-4-6-16, and I have been able to run CM7 from an SD card. However, this issue has me perplexed. I believe there is something simple going on -- maybe my permissions are not properly set for the folders back at the "sh ./ubuntu.sh" stage?
Has anyone encountered this issue? As I previously mentioned, using the "su" command does not help (although my nook does indicate the "Superuser" status). Your help is greatly appreciated.

[Q] Unable to root Huawei MediaPad 7

hi all,
I am trying very hard to root my huawei mediapad but not getting success.
Following are my setup -
My device - Huawei MediaPad 7
OS - Android 4.0.3
I have enabled USB debugging mode
My PC is on Windows 7 Home Premium.
I following so many posts for rooting this device. I followed the following posts.
Link1
Link2
In link1, i downloaded the zip file and run the Install Root.cmd script. But it shows me following errors
Code:
failed on '/data/local/tmp' - Permission denied
link failed File exists
ÅÑαѺáúαπªáѼ (1/3)
/system/bin/sh: cannot create /data/local.prop: Permission denied
ÅÑαѺáúαπªáѼ (2/3)
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
/system/bin/sh: cannot create /system/xbin/install_bb: Read-only file system
sh: /system/xbin/install_bb: No such file or directory
rm failed for /system/xbin/install_bb, No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
ÅÑαѺáúαπªáѼ (3/3)
éßÑ ú«Γ«ó«!!!
Press any key to continue . . .
On Link2 - the download link does not work and shows error as follows
Code:
Oops! Google Chrome could not connect to depositfiles.com
Suggestions:
Access a cached copy of depositfiles.*com/*files/*9f8mfimjz
Try reloading: depositfiles.*com/*files/*9f8mfimjz
Search on Google:
Someone please help.

[Q] /system/bin/sh: tcpdump: No such file or directory

I have generated a **tcpdump** file to run on an Android device using [this guide][not able to post the link here]. Instead of `Fedora`, I made this file on `Ubuntu 12.04` .
Everything worked smoothly and **tcpdump** file was produced correctly. I copied `tcpdump` file at `/system/bin/` on Nexus-5 and ran following commands.
> adb shell
# ln -s /system/bin/tcpdump /system/xbin/tcpdump
# chmod 06755 /system/xbin/tcpdump
# reboot
After restarting computer, when I run `> adb shell tcpdump -h` , I get following error:
/system/bin/sh: tcpdump: No such file or directory
Can someone help me figure out the problem? Thanks!

Categories

Resources