Database Users

invalid rsync error - rsync not found in path

[Thread edited and changed, because partially solved]
Device: asus Nexus 7
Android Version: 4.2.2
Build: JDQ39
rooted
I have installed SSHDroidPro (v1.9.6) - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroidpro and Terminal IDE (v2.02) - https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Code:
/storage/emulated/legacy # which rsync
/storage/emulated/legacy # which mkdir
/data/data/berserker.android.apps.sshdroidpro/home/bin/mkdir
Code:
-rwx------ 1 u0_a86 u0_a86 1012309 Dec 5 2011 /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync
What do I have to do, that _this_ rsync is used by SSHDroidPro? I would like to use all shell.commands from Terminal IDE with SSHDroidPro.
It helped to copy rsync set the permissions to 755 and link it:
Code:
cp /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync /data/data/berserker.android.apps.sshdroidpro/dropbear
ls -l /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
-rwxr-xr-x 1 root root 1012309 Mar 10 01:37 /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
ls -l /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
lrwxrwxrwx 1 root root 60 Mar 10 01:38 /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync -> /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
And then:
Code:
/storage/emulated/legacy # which rsync
/data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
The rest of the posting was deleted, because it was a bug in my script. But what can I do, so the ssh-server can use the commands ot the IDE-Terminal?

Wifi don't work? Flash this! /Persist Repair

Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!

Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Bro how to flash it ?
I flashed with twrp v3.0
it gave an error at the end. unable to mount something.
wifi is not working on my mot g2013. I have tried 5-6 roms.
Pls help

does it work?

No it dint.
Twrp gave error. Also the file whicg have to copy in that persist folder gets deleted automatically.

This works
OK, this works but not exactly by flashing.
First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.
Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code:
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code:
adb shell
7.
Code:
mount -o rw,remount /persist
8.
Code:
exit
- we are exiting shell now
9.
Code:
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code:
adb shell
12.
Code:
mount -o ro,remount /persist
13.
Code:
exit
14. Reboot your phone
If you have unsufficient permissions or something, try
Code:
chmod 777 /persist
after point 7 and
Code:
chmod 771 /persist
after point 11
Tell me if it works, was ok for me.

zyzioziom said:
OK, this works but not exactly by flashing.
First of all, this file is a WLAN Qualcom driver which is somehow missing after flashing errors.
Step by step:
1. Enable root for ADB in developer settings in your phone
2. Connect your phone with USB
3.
Code:
adb root
4. Now adb will reconnect as root. Enter command above again to make sure it's done (you will receive confirmation)
5. /persist is not accessible by default (read-only) so we must mount it as writable partition
6.
Code:
adb shell
7.
Code:
mount -o rw,remount /persist
8.
Code:
exit
- we are exiting shell now
9.
Code:
adb push WCNSS_qcom_wlan_factory_nv.bin /persist/
- we are copying driver to phone
10. OK, drivers are now saved on our phone. Let's remount /persist again to be read only:
11.
Code:
adb shell
12.
Code:
mount -o ro,remount /persist
13.
Code:
exit
14. Reboot your phone
If you have unsufficient permissions or something, try
Code:
chmod 777 /persist
after point 7 and
Code:
chmod 771 /persist
after point 11
Tell me if it works, was ok for me.
Click to expand...
Click to collapse
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.
I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "
Would you help me please?

norte112 said:
Zyzoom Hello, first of all sorry for my poor English, I have a XT1032 with the same problem, after installing TWRP recovery and CM13 Nightly 3.0.0, and was unable to enable Wi-Fi.
I followed your steps, but in step 9 out "Read-only file system", so I resume the steps from 6 (adb shell), then "mount -o rw, remount / persist" I write "chmod 777 / persist" but I back out the error " Read-only file system. "
Would you help me please?
Click to expand...
Click to collapse
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows

zyzioziom said:
norte112, you need to write commands exactly like I wrote. Do not put space between "/" and "persist" and between "rw," and "remount".
The best is to copy them directly to terminal, I think it's CTRL+INSERT or SHIFT+INSERT on Windows
Click to expand...
Click to collapse
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.

norte112 said:
The commands were copied and pasted as contained in the post directly to cmd, for an error when writing this query, add spaces, but just confirm again (no spaces) and still gives the same error message.
Click to expand...
Click to collapse
Code:
adb shell
ls -al
And paste the results here
Also, try whole process again but after each "adb shell" add another command: "su"

zyzioziom said:
Code:
adb shell
ls -al
And paste the results here
Also, try whole process again but after each "adb shell" add another command: "su"
Click to expand...
Click to collapse
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):
D:\xt1032\ABD-fastboot>adb root
adbd is already running as root
D:\xt1032\ABD-fastboot>adb shell su
[email protected]:/ #

norte112 said:
Deputy results:
D:\xt1032\ABD-fastboot>adb shell
←7←[r←[999;999H←[6nls -al
←[email protected]:/ $
I also tried adding SU command after SHELL, but after giving intro but does not allow me to enter any other line or command (attached results):
D:\xt1032\ABD-fastboot>adb root
adbd is already running as root
D:\xt1032\ABD-fastboot>adb shell su
[email protected]:/ #
Click to expand...
Click to collapse
You have strange results here :/
Here is my console:
Code:
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1 device
Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
[email protected]:/ # ls -al
total 2382
drwxr-xr-x 19 root root 0 1970-06-28 19:00 .
drwxr-xr-x 19 root root 0 1970-06-28 19:00 ..
drwxr-xr-x 44 root root 0 1970-06-28 19:00 acct
drwxrwx--- 6 system cache 4096 2016-03-05 03:28 cache
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ 2 root root 0 1970-06-28 19:00 config
lrwxrwxrwx 1 root root 17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x 35 system system 4096 2016-03-09 18:37 data
-rw-r--r-- 1 root root 555 1970-01-01 01:00 default.prop
drwxr-xr-x 15 root root 15300 1970-06-28 19:00 dev
lrwxrwxrwx 1 root root 11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r-- 1 root root 53465 1970-01-01 01:00 file_contexts
drwxr-xr-x 4 root root 4096 1970-01-01 01:00 firmware
drwxr-xr-x 3 root root 1024 1970-01-01 01:00 fsg
-rw-r----- 1 root root 2468 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 639808 1970-01-01 01:00 init
-rwxr-x--- 1 root root 8581 1970-01-01 01:00 init.cm.rc
-rwxr-x--- 1 root root 983 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x--- 1 root root 4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x--- 1 root root 29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26983 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 319 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- 1 root root 2764 1970-01-01 01:00 init.target.rc
-rwxr-x--- 1 root root 1921 1970-01-01 01:00 init.trace.rc
-rwxr-x--- 1 root root 9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5339 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x 9 root system 200 1970-06-28 19:00 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxr-xr-x 12 root root 1024 1970-01-01 01:01 pds
drwxrwx--x 4 system system 4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root root 0 1970-01-01 01:00 proc
-rw-r--r-- 1 root root 6049 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-03-05 03:29 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 2182 1970-01-01 01:00 seapp_contexts
-rw-r--r-- 1 root root 69 1970-01-01 01:00 selinux_version
-rw-r--r-- 1 root root 258562 1970-01-01 01:00 sepolicy
-rw-r--r-- 1 root root 14812 1970-01-01 01:00 service_contexts
drwxr-xr-x 4 root root 80 2016-03-09 11:57 storage
dr-xr-xr-x 14 root root 0 1970-06-28 19:00 sys
drwxr-xr-x 16 root root 4096 2016-03-08 21:09 system
lrwxrwxrwx 1 root root 16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-06-28 19:00 vendor -> /system/vendor
Your "ls -al" displayed nothing, am I right?

zyzioziom said:
You have strange results here :/
Here is my console:
Code:
Patryks-MacBook-Air:platform-tools patryk$ ./adb devices
List of devices attached
TA9290KDJ1 device
Patryks-MacBook-Air:platform-tools patryk$ ./adb root
adbd is already running as root
Patryks-MacBook-Air:platform-tools patryk$ ./adb shell
[email protected]:/ # ls -al
total 2382
drwxr-xr-x 19 root root 0 1970-06-28 19:00 .
drwxr-xr-x 19 root root 0 1970-06-28 19:00 ..
drwxr-xr-x 44 root root 0 1970-06-28 19:00 acct
drwxrwx--- 6 system cache 4096 2016-03-05 03:28 cache
lrwxrwxrwx 1 root root 13 1970-01-01 01:00 charger -> /sbin/healthd
dr-x------ 2 root root 0 1970-06-28 19:00 config
lrwxrwxrwx 1 root root 17 1970-06-28 19:00 d -> /sys/kernel/debug
drwxrwx--x 35 system system 4096 2016-03-09 18:37 data
-rw-r--r-- 1 root root 555 1970-01-01 01:00 default.prop
drwxr-xr-x 15 root root 15300 1970-06-28 19:00 dev
lrwxrwxrwx 1 root root 11 1970-06-28 19:00 etc -> /system/etc
-rw-r--r-- 1 root root 53465 1970-01-01 01:00 file_contexts
drwxr-xr-x 4 root root 4096 1970-01-01 01:00 firmware
drwxr-xr-x 3 root root 1024 1970-01-01 01:00 fsg
-rw-r----- 1 root root 2468 1970-01-01 01:00 fstab.qcom
-rwxr-x--- 1 root root 639808 1970-01-01 01:00 init
-rwxr-x--- 1 root root 8581 1970-01-01 01:00 init.cm.rc
-rwxr-x--- 1 root root 983 1970-01-01 01:00 init.environ.rc
-rwxr-x--- 1 root root 3816 1970-01-01 01:00 init.mmi.boot.sh
-rwxr-x--- 1 root root 4562 1970-01-01 01:00 init.mmi.touch.sh
-rwxr-x--- 1 root root 29483 1970-01-01 01:00 init.qcom.rc
-rwxr-x--- 1 root root 4561 1970-01-01 01:00 init.qcom.ssr.sh
-rwxr-x--- 1 root root 11797 1970-01-01 01:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 26983 1970-01-01 01:00 init.rc
-rwxr-x--- 1 root root 1399 1970-01-01 01:00 init.recovery.qcom.rc
-rwxr-x--- 1 root root 319 1970-01-01 01:00 init.superuser.rc
-rwxr-x--- 1 root root 2764 1970-01-01 01:00 init.target.rc
-rwxr-x--- 1 root root 1921 1970-01-01 01:00 init.trace.rc
-rwxr-x--- 1 root root 9283 1970-01-01 01:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5339 1970-01-01 01:00 init.usb.rc
-rwxr-x--- 1 root root 342 1970-01-01 01:00 init.zygote32.rc
drwxr-xr-x 9 root system 200 1970-06-28 19:00 mnt
drwxr-xr-x 2 root root 0 1970-01-01 01:00 oem
drwxr-xr-x 12 root root 1024 1970-01-01 01:01 pds
drwxrwx--x 4 system system 4096 2016-03-09 12:01 persist
dr-xr-xr-x 220 root root 0 1970-01-01 01:00 proc
-rw-r--r-- 1 root root 6049 1970-01-01 01:00 property_contexts
drwx------ 2 root root 0 2016-03-05 03:29 root
drwxr-x--- 2 root root 0 1970-01-01 01:00 sbin
lrwxrwxrwx 1 root root 21 1970-06-28 19:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 2182 1970-01-01 01:00 seapp_contexts
-rw-r--r-- 1 root root 69 1970-01-01 01:00 selinux_version
-rw-r--r-- 1 root root 258562 1970-01-01 01:00 sepolicy
-rw-r--r-- 1 root root 14812 1970-01-01 01:00 service_contexts
drwxr-xr-x 4 root root 80 2016-03-09 11:57 storage
dr-xr-xr-x 14 root root 0 1970-06-28 19:00 sys
drwxr-xr-x 16 root root 4096 2016-03-08 21:09 system
lrwxrwxrwx 1 root root 16 1970-06-28 19:00 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 12478 1970-01-01 01:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 7606 1970-01-01 01:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-06-28 19:00 vendor -> /system/vendor
Your "ls -al" displayed nothing, am I right?
Click to expand...
Click to collapse
I found the problem, after writing the adb shell command, the console brings me the following result: ← 7 ← [r ← [999; ← 999H [6n
I just click on INTRO and I recently enabled the line: ← 8root @ falcon: / #
After that, I entered the commands and could properly install the drivers !!!
Problem solved.
Thank you very much for the support, help and above all, patience.

Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Worked perfect with flashify and twrp (copy first to a safe location)
Many thanks!

Didn't work for me
I tried flashing the zip, copying manually in CM file explorer and twrp and adb.
The driver is present in /persist but my Mac is stil 02:00:00:00:00
edit:
it's working after doing this:
http://forum.xda-developers.com/showpost.php?p=64771901&postcount=6

My wifi bug is kinda weird.
When I turn on and off my wifi 2-3times,the wifi I connected previously disappear.
Solution is to wipe everything including internal storage to have it working.But still I don't know what's the problem...

I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator

NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse
I faced same problem after flashed custom rom; searching high and low, tried many method, and finally, bumped this thread, and specifically NoobByn-tek post. I followed exactly what your have done (but with different version CM13 [cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J1-falcon] because could not find the version you used), and multiple flashed with TWRP 3.0.2. With only one attempt, wifi connection is back.:victory:
Big thank you all.:good::good:

NoobByn-tek said:
I had trouble installing the file no matter how it I flash the wifi did not return to work until I found a solution that apparently functioned normally every time I performed the procedure.
1. Make a full wipe on your smartphone (System / data / cache / dalvik and internal storage) I did the procedure using TWRP 3.0.2-0 on my bike G XT1033
2. Then copy the file persist_repair.zip and some version of CM13 I used (cm 13.0-20160708-NIGHTLY-falcon)
3. After placing the files in the memory of the first flash persist_repair.zip phone and then the CM13 (You can do using the option to install multiple zips the TWRP also the right)
4. Restart your phone and its wifi should resume functioning
Note: I performed the procedure 4 times here and it worked perfectly.
Sorry for the English I used the google translator
Click to expand...
Click to collapse
tried this still no luck...:crying::crying:

Boss442 said:
Well, many people have problems on the /persist partition, maybe because some bad rom, or maybe because by a mistake you formatted them on a recovery (a bad recovery without forbid partitions).
Before this zip, you have to copy the "WCNSS_qcom_wlan_factory_nv.bin" to /persist manually, but some file managers don't mount well /persist.
But now, only flashing this zip, it will copy the file to /persist and Wifi go back to work.
:highfive:
Download from:
MEDIAFIRE!
MEGA!
Click to expand...
Click to collapse
Holy cow!!! After 2 weeks of trying everything under the sun this actually worked!!! I really really appreciate you posting this. Thank you so much!!!
My mac address was 00:00:00:00:02 or whatever it was and nothing would work. I simply flashed this and was back up and running. THANK YOU!

update link please

HELP PLEASE Lg L2 Lost memory 32 go after bad flash 16go kdz

After flashing a 16go kdz in my lg g2 d802 I lost my 32go memory, I followed this tuto http://forum.xda-developers.com/showthread.php?t=2470207&page=3
What I did ; used lg flash tools 2014 to flash 32 go kdz [doesn't solve the problem, just 10.7go] then I rooted my phone with iroot25,check root with root checker, copy files and overwrite by Total Commander to system/bin after making it RW, but when I set permissions to 755 and apply doesn't saved check again and found 602 so I can't use ADB to modify partitions and got permissions denied also I lose my root.
if I reboot phone I lose network
where is the problem??
I really appreciate your help, thank you very much
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
07459cead6cc4ddf device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # adb devices
adb devices
List of devices attached
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC 032G96 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 15.7GB 11.6GB ext4 userdata
36 15.7GB 15.8GB 37.7MB grow
(parted) quit
quit
quit
@ANDROID:/system # quit
quit
sh: quit: not found
127 @ANDROID:/system # ./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512
seek=61071327 conv=notrunc
of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: ./dd: not found
127 @ANDROID:/system # dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 se
ek=61071327 conv=notrunc
=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: dd: can't execute: Permission denied
126 @ANDROID:/system # /dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 s
eek=61071327 conv=notrunc
f=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc <
sh: /dd: not found
127 @ANDROID:/system #
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
/system/bin/sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
/system/bin/sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ $ su
su
sh: /system/etc/mkshrc[9]: getprop: can't execute: Permission denied
sh: /system/etc/mkshrc[10]: id: can't execute: Permission denied
@ANDROID:/ # cd /system
cd /system
@ANDROID:/system # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print

Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.

Goona work hhh
Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Yes very true I learned a lot but this solution works for a lot of users, im just struggling with system/bin permissions, I know something wrong with SU or root or kdz or lg tools 2014, so im looking for the generosity of experts or people who had the same issue, im very sure its gonna work, in the same time, im trying to be familiar with android/Linux, lol, thank you for your reply

Yoinx said:
Unfortunately, it sounds like you've just learned a hard lesson about flashing the wrong tot/kdz files.
If you can't re-flash a kdz/tot of the right size and fix it, there's probably not much anyone's going to be able to do fix it.
Click to expand...
Click to collapse
Everything is possible with Linux, you may learn something new from this thread too, lol

thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?

RE
Yoinx said:
Yeah, it's possible.
Tbh... it looks like you're either on the stock rom without busybox installed. Or your permissions are hosed as you suspect.
If you type busybox while in your adb shell, what do you get?
Click to expand...
Click to collapse
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man

thequietman1979 said:
Everything is possible with Linux, you may learn something new from this thread too, lol
Click to expand...
Click to collapse
thequietman1979 said:
Yes right, im in stock coz this solution doesn't work for others roms, rooted and busybox, when I type it in adb it gives me busybox 1.20.0 installed and all the commands and functions but when I make changes in system/bin I lose adb access and lose also root.
thank u man
Click to expand...
Click to collapse
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.

Solved
Yoinx said:
make sure that you're allowing root access for adb in your phone's developer options and/or the security settings for your phone.
restart adb as root: adb root
remount your system as r/w: adb remount
see if that makes a difference.
Click to expand...
Click to collapse
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here

thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Yes Thanks for mentioning that : su in folder xbin and not system/bin
kindly try with this last 2 commands
2.
adb shell
su
cd /system
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc

where can i find the files to download?

http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/

Hello! Please help!!! I try to paste the last two lines
./dd if=/system/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
and when press enter it says : sh: ./dd: not found
I also try and these :
./dd if=/system/xbin/sgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=61071327 conv=notrunc
./dd if=/system/xbin/pgpt32g.img of=/dev/block/mmcblk0 bs=512 seek=0 conv=notrunc
but with the same results!!

Which link process is the final? And where is a link with the finally sdparted-recovery-all-files?
Which firmware can i use before process? 4.2.2 or 4.4.2?
Which root i can use? With SuperSU or Superuser?
Which programe to use? Total commander or Root explorer??
PLease help me!

if i flash the correct kdz without doing anything else does it fix the problem ??

Please explain
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
thequietman1979 said:
Thank you very much, I solved the problem, was very easy, had to copy files to xbin where my su is installed, and then change the 2 last commands, some root app install su in bin and other is xbin both folders are executables, so mine had to choose xbin and got my memory back 25go
im happy
thank you again for your support, any info im here
Click to expand...
Click to collapse
How you root your phon, thats my biggest problem

Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
You need to root it before following the tutorial to get back 32go
http://forum.xda-developers.com/showthread.php?t=2470207&goto=newpost
To root your phone use iroot

Ebaharloo said:
Please explain me what you done? I've same problem for month
---------- Post added at 09:34 PM ---------- Previous post was at 09:25 PM ----------
How you root your phon, thats my biggest problem
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2448887

thequietman1979 said:
http://forum.xda-developers.com/showthread.php?t=2448887
Click to expand...
Click to collapse
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me

Ebaharloo said:
I tired many methods, iroot, towelroot,... But no result.
After flashing my g2 to stock lollipop i lost root and recovery also 32 gb phon become 10gb.
So i tried many method to root and try methods which is available to solve 10gb problem but all if them need root.
You wrote you had same problem.please help me
Click to expand...
Click to collapse
What s the model of your lg g2?
If its d802 try to flash it back to kitkat using lg flash tool 2014 than root it using iroot or iroot 10, than follow the tuto, u gonna restore your memory
Root lg g2 d802 : http://forum.xda-developers.com/lg-...ols-how-to-install-twrp-bump-d80230a-t3072186.
Manual method: http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772

[ROOT][TWRP][v500] Lineage OS

Hi
I was finally able to root my device, install TWRP on it and install lineageOS.
The methods that I found before don't fully work due to the latest firmware versions, but I found a way around it. You can find the necessary files in a zip file. Unfortunately I have few posts so I can't post links... is there a way to post a link to the zip file?
The file is in dropbox with path:
dropbox.com/s/s1vcd8z3c2chf4o/v500.zip?dl=0
unzip and follow the commands described in root.sh they are a bit succint but it worked for me.
Afterwards, just use TWRP to flash the lineageos image + gapps
The commands that I executed are:
adb reboot recovery
# Sideload kk_root.zip
adb push twrp-3.1.1-0-v500.img /sdcard/
adb push ./aboot.img /sdcard/flash_tmp/aboot.img
adb push ./recovery.lok /sdcard/flash_tmp/recovery.lok
dd if=/sdcard/flash_tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/flash_tmp/recovery.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
# Copy stuff to /mnt/asec chmod a+x
# update super su
/mnt/asec # cp /storage/emulated/0/flash_tmp/* .
/mnt/asec # ls -l
-rw------- root root 524288 2017-09-13 01:52 aboot.img
-rw------- root root 524288 2017-09-13 01:52 aboot2.img
-rwxr-xr-x root root 1085140 2017-09-13 01:50 busybox
-rwxr-xr-x root root 76540 2017-09-13 01:52 loki_tool
-rw------- root root 11597824 2017-09-13 01:52 recovery.img
-rw------- root root 11001856 2017-09-13 01:52 recovery.lok
/mnt/asec # ./loki_tool
Loki tool v2.1
Usage
> Patch partition file image:
./loki_tool [patch] [boot|recovery] [aboot.img] [in.img] [out.lok]
> Flash loki image to boot|recovery:
./loki_tool [flash] [boot|recovery] [in.lok]
> Find offset from aboot image:
./loki_tool [find] [aboot.img]
> Revert Loki patching:
./loki_tool [unlok] [in.lok] [out.img]
/mnt/asec # ./loki_tool patch recovery aboot.img recovery.
recovery.img recovery.lok
/mnt/asec # ./loki_tool patch recovery aboot.img recovery.img recovery.lok
Loki tool v2.1
[+] Detected target International LG G Pad 8.3 build V50010a
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to recovery.lok
/mnt/asec # ./loki_tool flash recovery recovery.lok
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
/mnt/asec # ./loki_tool patch recovery aboot.img /st
/mnt/asec # ls -l /storage/emulated/0/twrp-3.1.1-0-v500.img
-rw-rw---- root sdcard_r 14444560 2017-09-13 01:18 twrp-3.1.1-0-v500.img
/mnt/asec # ./loki_tool patch recovery aboot.img /storage/emulated/0/twrp-3.1.1-
0-v500.img recovery.lok
Loki tool v2.1
[+] Detected target International LG G Pad 8.3 build V50010a
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to recovery.lok
/mnt/asec # ls -l
-rw------- root root 524288 2017-09-13 01:52 aboot.img
-rw------- root root 524288 2017-09-13 01:52 aboot2.img
-rwxr-xr-x root root 1085140 2017-09-13 01:50 busybox
-rwxr-xr-x root root 76540 2017-09-13 01:52 loki_tool
-rw------- root root 11597824 2017-09-13 01:52 recovery.img
-rw------- root root 14446592 2017-09-13 01:54 recovery.lok
/mnt/asec # ./loki_tool flash recovery recovery.lok
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!

can't find boot partition while trying to install usb host-mode on nook simple touch

Hello,
I am trying to install USB host-mode on my rooted nook simple touch so that I can use a keyboard or a mouse as a page turner. I am running 1.2.1, and rooted the nook using nook manager https://forum.xda-developers.com/showthread.php?t=2040351. This completed successfully. Then I installed a terminal app (can't find the link but it's called jackpal.androidterm.apk, can attach if needed) by putting it on a micro sd card and installing the file using relaunch (a file explorer app that appeared after rooting). Then I followed the instructions on https://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Replacing_boot_files writing
su
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
into the terminal app. It asked for permissions after su, which I granted and the other lines produced no errors but also no outputs. Now I am trying to find the /boot partition to replace uImage, as per the instructions, but I can't find /boot. It appears nowhere in the file explorer, and under advanced functions, the nook lists the following disks/partitions: /rom, /system, /data, /cache, /sdcard, /media, but no /boot
Any ideas? Really unsure as to why it's not showing up, because the commands that are supposed to create it seemed to complete without issue.
p.s. I also checked show hidden files in folders in the advanced settings

I dunno. Your "File Explorer" may be leading you astray.
Just do an ls -l in terminal and check.

ls -l produces:
drwxrwx--- system system 1969-12-31 16:00 rom
drwxrwxrwt root root 2018-02-26 11:11 sqlite_stmt_journals
d---rwxr-x system sdcard_rw 1969 -12-31 16:00 sdcard
drwxrwxr-x system sdcard_rw 1969 -12-31 16:00 media
drwxrwx--- system cache 2018-02-15 11:23 cache
drwxrwxrwx root root 2018-02-26 11:11 tmp
lrwxrwxrwx root root 2018-02-26 11:11 etc -> /system/etc
-rw-r--r-- root root 118 2018-02-15 12:03 init.rc.orig
-rw-r--r-- root root 118 2018-02-15 12:19 default.prop.orig
drwxr-xr-x root root 2018-02-05 12:19 system
drwxr-xr-x root root 1969-12-31 16:00 sys
drwxr-x--- root root 2018-02-15 12:03 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 1677 2018-02-15 12:03 init.goldfish.rc
-rwxr-x--- root root 128000 2018-02-15 12:03 init
-rwxr-x--- root root 324 2018-02-15 12:03 env.txt
drwxrwx--x system system 2018-02-15 11:24 data
-rw-r--r-- root root 118 2018-02-15 12:03 default.prop
-rwxr-x--- root root 19284 2018-02-15 12:03 init.rc
drwx------ root root 2012-12-07 14:34 root
drwxr-xr-x root root 2018-02-26 11:11 dev
Further, I tried to copy uImage into /boot using the terminal and it acted as if /boot didn't exist, so I'm pretty sure that it isn't there for some reason.
Thanks

Well, something you're doing isn't working.
The commands are correct.
Code:
su
Did this work? Do you get a # prompt? Type "id", does it say you're root?
Code:
mount -o rw,remount rootfs /
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
Code:
mkdir /boot
Apparently this didn't work because you should see an empty directory at least.
Code:
mount -t vfat /dev/block/mmcblk0p1 /boot
Apparently this didn't work.

Did this work? Do you get a # prompt? Type "id", does it say you're root?
su produces a # prompt, and id produces: uid=0(root) gid=0(root), so i think this part worked.
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
mount produces: rootfs / rootfs rw 0 0, and then a bunch of other stuff, so i think this worked too.
mkdir /boot
this produces nothing, just another # prompt, so this might be the problem
mount -t vfat /dev/block/mmcblk0p1 /boot
this also produces nothing, just another # prompt.
Any idea why mkdir /boot would fail?
Thanks for being so helpful!

Well, the mkdir should have created an empty directory.
You should be able to "ls -l /" it.
If not, you could mkdir and mount anywhere.
Code:
cd /data/local/tmp
mkdir mybooty
mount -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mybooty
There's nothing special about the name "boot".

Okay,
That solved the problem. Thanks for all your help!