Related
I have been trying to downgrade my android 2.3.4 Mytouch 4g
using the following guide:\
http://forum.xda-developers.com/showthread.php?t=1178912
but i get an message sayin misc version permission denied.
Here is my command prompt:
C:\android-sdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
push: fre3vo/__MACOSX/._fre3vo -> /data/local/tmp/__MACOSX/._fre3vo
push: fre3vo/fre3vo -> /data/local/tmp/fre3vo
2 files pushed. 0 files skipped.
305 KB/s (10025 bytes in 0.032s)
C:\android-sdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Scanning region fbb70000...
Potential exploit area found at address fbb80e00:200.
Exploiting device...
C:\android-sdk\platform-tools>adb shell
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
push: misc_version/misc_version_01/misc_version.c -> /data/local/tmp/misc_versio
n/misc_version_01/misc_version.c
push: misc_version/misc_version_01/misc_version -> /data/local/tmp/misc_version/
misc_version_01/misc_version
push: misc_version/misc_version_01/gopt.h -> /data/local/tmp/misc_version/misc_v
ersion_01/gopt.h
push: misc_version/misc_version_01/gopt.c -> /data/local/tmp/misc_version/misc_v
ersion_01/gopt.c
push: misc_version/misc_version.c -> /data/local/tmp/misc_version/misc_version.c
push: misc_version/misc_version -> /data/local/tmp/misc_version/misc_version
push: misc_version/gopt.h -> /data/local/tmp/misc_version/gopt.h
push: misc_version/gopt.c -> /data/local/tmp/misc_version/gopt.c
8 files pushed. 0 files skipped.
420 KB/s (62798 bytes in 0.146s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
push: flashgc/flashgc -> /data/local/tmp/flashgc/flashgc
1 file pushed. 0 files skipped.
1965 KB/s (712688 bytes in 0.354s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#
please help i have followed all the steps but i get the same message, i even tried resetting the phone and trying again.
supa9274 said:
I have been trying to downgrade my android 2.3.4 Mytouch 4g
using the following guide:\
http://forum.xda-developers.com/showthread.php?t=1178912
but i get an message sayin misc version permission denied.
Here is my command prompt:
C:\android-sdk\platform-tools>adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length
C:\android-sdk\platform-tools>adb push fre3vo /data/local/tmp
push: fre3vo/__MACOSX/._fre3vo -> /data/local/tmp/__MACOSX/._fre3vo
push: fre3vo/fre3vo -> /data/local/tmp/fre3vo
2 files pushed. 0 files skipped.
305 KB/s (10025 bytes in 0.032s)
C:\android-sdk\platform-tools>adb shell
$ chmod 777 /data/local/tmp/fre3vo
chmod 777 /data/local/tmp/fre3vo
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 80
width: 48
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region faa90000...
Scanning region fab80000...
Scanning region fac70000...
Scanning region fad60000...
Scanning region fae50000...
Scanning region faf40000...
Scanning region fb030000...
Scanning region fb120000...
Scanning region fb210000...
Scanning region fb300000...
Scanning region fb3f0000...
Scanning region fb4e0000...
Scanning region fb5d0000...
Scanning region fb6c0000...
Scanning region fb7b0000...
Scanning region fb8a0000...
Scanning region fb990000...
Scanning region fba80000...
Scanning region fbb70000...
Potential exploit area found at address fbb80e00:200.
Exploiting device...
C:\android-sdk\platform-tools>adb shell
# exit
exit
C:\android-sdk\platform-tools>adb push misc_version /data/local/tmp/misc_version
push: misc_version/misc_version_01/misc_version.c -> /data/local/tmp/misc_versio
n/misc_version_01/misc_version.c
push: misc_version/misc_version_01/misc_version -> /data/local/tmp/misc_version/
misc_version_01/misc_version
push: misc_version/misc_version_01/gopt.h -> /data/local/tmp/misc_version/misc_v
ersion_01/gopt.h
push: misc_version/misc_version_01/gopt.c -> /data/local/tmp/misc_version/misc_v
ersion_01/gopt.c
push: misc_version/misc_version.c -> /data/local/tmp/misc_version/misc_version.c
push: misc_version/misc_version -> /data/local/tmp/misc_version/misc_version
push: misc_version/gopt.h -> /data/local/tmp/misc_version/gopt.h
push: misc_version/gopt.c -> /data/local/tmp/misc_version/gopt.c
8 files pushed. 0 files skipped.
420 KB/s (62798 bytes in 0.146s)
C:\android-sdk\platform-tools>adb push flashgc /data/local/tmp/flashgc
push: flashgc/flashgc -> /data/local/tmp/flashgc/flashgc
1 file pushed. 0 files skipped.
1965 KB/s (712688 bytes in 0.354s)
C:\android-sdk\platform-tools>adb shell chmod 777 /data/local/tmp/*
C:\android-sdk\platform-tools>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version: permission denied
#
please help i have followed all the steps but i get the same message, i even tried resetting the phone and trying again.
Click to expand...
Click to collapse
First of all,man this is not Mytouch 4G section.Go to that & post your problem.Then MT4G users & devs see your post & will help.
I also downgrade to froyo from that thread & I did not got any problem.When you typing
# ./misc_version -s 1.00.000. 0
what you got for the result? Is./misc_version -s 1.00.000.0?
Hello, I am wondering deciding whether or not I will buy the Fujitsu Arrows X, and it depends on whether I can have root on the phone or not.
I read on the internet that Goroh_Kun got root on the phone, but I am not experienced at rooting phones and ADB, so I cannot understand the source code and binary posted online, nor can I understand a guide of how he got root.
All I could tell was that root was gained for the phone through a vulnerability in "aeswipe" aka the fingerprint scanning thing. However, I cannot follow along with the steps, because I cannot understand it.
I don't know how to use the source code or binary for anything.
Will someone read the pages and summarize the steps for rooting the phone so I can understand it?
I cannot post URLs, so please reply if you need the URLs.
Sarcasticphoenix
Bump
Bumped post, need a reply.
!!!!!!!!!! Caution rooting can be risk your devices. !!!!!!!!!!!
!!!!!!!!!! CAUTION ROOTING CAN BE RISK YOUR DEVICES. !!!!!!!!!!!
YOU MUST HAVE TO KNOW WHAT YOU DO. BEFORE YOU MAKE A THING.
obtain root privileges on the f-10d
Things Require
1. Root Kit
2. ADB Driver For F-10D
3. PC With android SDK
4. Little Knowledge with linux command line
Things to do
Right click on folded you save extract of root kit. that you download
(1) On command prompt put command "adb restore f-10d_2.ab" without "…"
Press OK certification will appear on the screen
(2) You must verify that
(3) after restore is finished. Put command
> adb shell
$ cd / data / data / com.android.settings / a /
$ ls -l-d
drwxrwxrwx system system a
⇒ a directory that exists and is world readable, writable to
$ ls -l
⇒ up to file00 ~ file99 directory exists
(4) Once removed file00 ~ file99
> adb shell
$ cd /data/data/com.android.settings/
$ rm -r a
(Please go but out ※ error)
(5) Make /data permissions to 777. Input command.
$ while:; do ln -s /data a/file99; done
On your screen should infinite run.While doing this, open new command line. Don't closed running windows.
Now input command in new windows
>adb restore f-10d_2.ab
Confirm on your f-10d to complete the restore
After you have finished, exit the old infinite running windows
(6) Check the permissions on the /data
> adb shell
$ ls -l-d /data
drwxrwxrwx system system data
(7) Execute the following command
> adb push mkdevsh /data/local.org/tmp/mkdevsh
> adb shell chmod 777 /data/local.org/tmp/mkdevsh
(8) On or Off Wifi, and then execute
> echo /data/local.org/tmp/mkdevsh>/sys/kernel/uevent_helper
> adb shell
$ ls -l /dev/sh
-rwsr-sr-x root root 151964 2012-08-06 19:34 sh
$ /Dev/sh
# ************ Tempolary insecure root shell ************
(9) Copy lsm_disabler.ko and f10dunlock to /data/local
>adb push f10dunlock /sdcard
>adb push lsm_disabler.ko /sdcard
>dab shell
# dd if=/mnt/sdcard/f10dunlock of=/data/local/f10dunlock
# dd if=/mnt/sdcard/lsm_disabler.ko of=/data/local/lsm_disabler.ko
(10) release LSM lock
********* "x" and "y" is option for f10dunlock
For x=0 if you're on F-10D Build number V16R45C
x=1 if you're ISW13D Device
x=2 if you're on F-10D Build number V18R46F
IF you can't insert module lsm_disabler.ko after execute f10dunlock "x" you can add option "y" at last one example f10dunlock 0 2 or f10dunlock 0 1 and then try to insert module lsm_disabler.ko **********
# cd /data/local
# chmod 777 f10dunlock
# chown root.root / data/local/f10dunlock
# /data/local/f10dunlock x y
/data/local/f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
use new F-10D address
# /data/local/f10dunlock 2
/data/local/f10dunlock 2
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# ./f10dunlock
./f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# lsmod
# mount-o rw, remount / system
mount-o rw, remount / system
# cd /system
cd /system
# chmod 777 / system
chmod 777 / system
# mkdir test
mkdir test
# ls-al
(11) Set su busybox
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/bin/su
dd if=/mnt/sdcard/su of=/system/bin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.079 secs (4816860 bytes / sec)
# chown root.shell /system/bin/su
chown root.shell /system/bin/su
# chmod 06755 /system/bin/su
chmod 06755 /system/bin/su
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/xbin/su
dd if=/mnt/sdcard/su of=/system/xbin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.034 secs (11192117 bytes / sec)
# chown root.shell /system/xbin/su
chown root.shell /system/xbin/su
# chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
# sync; sync; sync
sync; sync; sync
# dd if = /data/local.org/tmp/busybox of=/system/xbin/busybox
dd if=/data/local.org/tmp/busybox of=/system/xbin/busybox
2099 +1 records in
2099 +1 records out
1075144 bytes transferred in 0.085 secs (12648752 bytes / sec)
# chown root.shell /system/xbin/busybox
chown root.shell /system/xbin/busybox
# chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/busybox
# ls-al
ls-al
drwxr-xr-x root root 2012-09-01 03:31 app
drwxrwxrwx root shell 2012-09-01 23:59 bin
-rw-r - r - root root 4093 2012-09-01 03:31 build.prop
drwxr-xr-x root shell 2012-09-02 01:05 xbin
# cd /system/xbin
cd /system/xbin
# ls -al
ls -al
-rwxr-xr-x root shell 10028 2012-07-07 21:17 agent
-rwsr-xr-x root shell 1075144 2012-09-02 01:05 busybox
-rwxr-xr-x root shell 9780 2012-07-07 21:17 dbus-monitor
-rwxr-xr-x root shell 5708 2012-07-07 21:17 sdptest
-rwsr-sr-x root shell 380532 2012-09-02 01:03 su
#
(12) Set up SuperUser
Install from the market SuperSU etc..
k you must have permission to launch the app root, root authorization confirmation screen will appear if
Remark form me(yes, me not goroh_kun) : if you reboot your device. It's has re-lock /system. Even you have root access you can't remount /system to r/o until you re-execute f10dunlock. So you should think and plan by carefully that you want to move SuperSU.apk form /data/app to/system/app for more safer factory reset in future or not.
Thank you for the dear goroh_kun.
Ugh...what a convoluted process... I'm really on the edge about doing this.
I also heard that this causes the fingerprint reader to stop working. Can anyone confirm this? I use the fingerprint reader a lot so I'd hate to lose that functionality.
Hi,
thanks for the explanation.
But I am stuck at some point:
A. step (8) says on or off WiFi - what does this mean?
B. next, cannot output from mkdevsh to /sys/kernel/udev_helper: permission denied
mkdevsh cannot be executed, says error "syntax error: '^A' unexpected and /bin/sh is not available
C. lsm_disabler.ko is not supplied in ZIP file
Can you please help?`
Thanks
tuxsurfer said:
Hi,
thanks for the explanation.
But I am stuck at some point:
A. step (8) says on or off WiFi - what does this mean?
B. next, cannot output from mkdevsh to /sys/kernel/udev_helper: permission denied
mkdevsh cannot be executed, says error "syntax error: '^A' unexpected and /bin/sh is not available
C. lsm_disabler.ko is not supplied in ZIP file
Can you please help?`
Thanks
Click to expand...
Click to collapse
You manage to get this working? Just wondering as I have an F-10D on the way. I know you can disable a decent bit of bloatware with the ICS disable feature, but I want to disable all of the bloat, if possible.
Anyway, the process does seem simple enough, but the things pointed out above will keep me hesitant on this matter. Does "on or off WiFi", mean turn on and then off?
Thanks
tuxsurfer said:
Hi,
thanks for the explanation.
But I am stuck at some point:
A. step (8) says on or off WiFi - what does this mean?
Ohhhh, Excuse me right thing is " ON and then OFF WIFI" this the hole on android from Sony Ericsson X10
B. next, cannot output from mkdevsh to /sys/kernel/udev_helper: permission denied
mkdevsh cannot be executed, says error "syntax error: '^A' unexpected and /bin/sh is not available
Make sure "echo /data/local.org/tmp/mkdevsh > /sys/kernel/uevent_helper" without quote " " and this can operate after WIFI Hole step
C. lsm_disabler.ko is not supplied in ZIP file
for lsm_disabler.ko not required for the new method just unlocked
Can you please help?`
Thanks
Click to expand...
Click to collapse
I'm So Busy,Sorry for late answer.
tum.osx said:
!!!!!!!!!! CAUTION ROOTING CAN BE RISK YOUR DEVICES. !!!!!!!!!!!
YOU MUST HAVE TO KNOW WHAT YOU DO. BEFORE YOU MAKE A THING.
obtain root privileges on the f-10d
Things Require
1. Root Kit
2. ADB Driver For F-10D
3. PC With android SDK
4. Little Knowledge with linux command line
Things to do
Right click on folded you save extract of root kit. that you download
(1) On command prompt put command "adb restore f-10d_2.ab" without "…"
Press OK certification will appear on the screen
(2) You must verify that
(3) after restore is finished. Put command
> adb shell
$ cd / data / data / com.android.settings / a /
$ ls -l-d
drwxrwxrwx system system a
⇒ a directory that exists and is world readable, writable to
$ ls -l
⇒ up to file00 ~ file99 directory exists
(4) Once removed file00 ~ file99
> adb shell
$ cd /data/data/com.android.settings/
$ rm -r a
(Please go but out ※ error)
(5) Make /data permissions to 777. Input command.
$ while:; do ln -s /data a/file99; done
On your screen should infinite run.While doing this, open new command line. Don't closed running windows.
Now input command in new windows
>adb restore f-10d_2.ab
Confirm on your f-10d to complete the restore
After you have finished, exit the old infinite running windows
(6) Check the permissions on the /data
> adb shell
$ ls -l-d /data
drwxrwxrwx system system data
(7) Execute the following command
> adb push mkdevsh /data/local.org/tmp/mkdevsh
> adb shell chmod 777 /data/local.org/tmp/mkdevsh
(8) On or Off Wifi, and then execute
> echo /data/local.org/tmp/mkdevsh>/sys/kernel/uevent_helper
> adb shell
$ ls -l /dev/sh
-rwsr-sr-x root root 151964 2012-08-06 19:34 sh
$ /Dev/sh
# ************ Tempolary insecure root shell ************
(9) Copy lsm_disabler.ko and f10dunlock to /data/local
>adb push f10dunlock /sdcard
>adb push lsm_disabler.ko /sdcard
>dab shell
# dd if=/mnt/sdcard/f10dunlock of=/data/local/f10dunlock
# dd if=/mnt/sdcard/lsm_disabler.ko of=/data/local/lsm_disabler.ko
(10) release LSM lock
********* "x" and "y" is option for f10dunlock
For x=0 if you're on F-10D Build number V16R45C
x=1 if you're ISW13D Device
x=2 if you're on F-10D Build number V18R46F
IF you can't insert module lsm_disabler.ko after execute f10dunlock "x" you can add option "y" at last one example f10dunlock 0 2 or f10dunlock 0 1 and then try to insert module lsm_disabler.ko **********
# cd /data/local
# chmod 777 f10dunlock
# chown root.root / data/local/f10dunlock
# /data/local/f10dunlock x y
/data/local/f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
use new F-10D address
# /data/local/f10dunlock 2
/data/local/f10dunlock 2
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# ./f10dunlock
./f10dunlock
fdaes = -1
open aeswipe error, so try to disable LSM without recovery g_lptsAuthContext
fdaes2 = 3
# lsmod
# mount-o rw, remount / system
mount-o rw, remount / system
# cd /system
cd /system
# chmod 777 / system
chmod 777 / system
# mkdir test
mkdir test
# ls-al
(11) Set su busybox
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/bin/su
dd if=/mnt/sdcard/su of=/system/bin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.079 secs (4816860 bytes / sec)
# chown root.shell /system/bin/su
chown root.shell /system/bin/su
# chmod 06755 /system/bin/su
chmod 06755 /system/bin/su
# sync; sync; sync
sync; sync; sync
# dd if=/mnt/sdcard/su of=/system/xbin/su
dd if=/mnt/sdcard/su of=/system/xbin/su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.034 secs (11192117 bytes / sec)
# chown root.shell /system/xbin/su
chown root.shell /system/xbin/su
# chmod 06755 /system/xbin/su
chmod 06755 /system/xbin/su
# sync; sync; sync
sync; sync; sync
# dd if = /data/local.org/tmp/busybox of=/system/xbin/busybox
dd if=/data/local.org/tmp/busybox of=/system/xbin/busybox
2099 +1 records in
2099 +1 records out
1075144 bytes transferred in 0.085 secs (12648752 bytes / sec)
# chown root.shell /system/xbin/busybox
chown root.shell /system/xbin/busybox
# chmod 04755 /system/xbin/busybox
chmod 04755 /system/xbin/busybox
# ls-al
ls-al
drwxr-xr-x root root 2012-09-01 03:31 app
drwxrwxrwx root shell 2012-09-01 23:59 bin
-rw-r - r - root root 4093 2012-09-01 03:31 build.prop
drwxr-xr-x root shell 2012-09-02 01:05 xbin
# cd /system/xbin
cd /system/xbin
# ls -al
ls -al
-rwxr-xr-x root shell 10028 2012-07-07 21:17 agent
-rwsr-xr-x root shell 1075144 2012-09-02 01:05 busybox
-rwxr-xr-x root shell 9780 2012-07-07 21:17 dbus-monitor
-rwxr-xr-x root shell 5708 2012-07-07 21:17 sdptest
-rwsr-sr-x root shell 380532 2012-09-02 01:03 su
#
(12) Set up SuperUser
Install from the market SuperSU etc..
k you must have permission to launch the app root, root authorization confirmation screen will appear if
Remark form me(yes, me not goroh_kun) : if you reboot your device. It's has re-lock /system. Even you have root access you can't remount /system to r/o until you re-execute f10dunlock. So you should think and plan by carefully that you want to move SuperSU.apk form /data/app to/system/app for more safer factory reset in future or not.
Thank you for the dear goroh_kun.
Click to expand...
Click to collapse
Anything for F-02E??
the same problem
Rudeyllah said:
Anything for F-02E??
Click to expand...
Click to collapse
I have the same problem with the same phone model,i tried to root but i'm stuck at 7.-permision denied and 8.-on and off wifi...i try all but i can't pass this steps......maybe the tutorial need more detail or maybe it is about diferences between versions of phone.
Build
The Root for F-10D has different Command for Rooting,depending BUILD on Device..
Option is different depending on the version and model.
F-10D build number V16R45C: → 0
ISW13D: → 1
F-10D build number V18R46F: → 2
F-10D build number V20R47F: → 3
My Device is V20R47F and the Following Command for V16R45C ... Cannot be use on V20R47F.. i always get Error after -7 ..
Can anyone help for V20R47F ?
CMD
C:> adb restore f-10d_2.ab
~ ~ ~ To allow restore ~ ~ ~ Android terminal
C:> adb shell
shell @ android :/ $ cd / data / data / com.android.settings / a /
cd / data / data / com.android.settings / a /
shell @ android :/ data / data / com.android.settings / a $ ls-l-d
ls-l-d
drwxrwxrwx system system 2011-01-01 09:09.
shell @ android :/ data / data / com.android.settings / a $ ls-l
ls-l
drwxrwxrwx system system 2011-01-01 09:09 file00
drwxrwxrwx system system 2011-01-01 09:09 file01
drwxrwxrwx system system 2011-01-01 09:09 file02
~ ~ ~ ~ ~ ~ Omitted
~ ~ ~ ~ ~ ~ Omitted
drwxrwxrwx system system 2011-01-01 09:09 file97
drwxrwxrwx system system 2011-01-01 09:09 file98
drwxrwxrwx system system 2011-01-01 09:09 file99
shell @ android :/ data / data / com.android.settings / a $ cd / data / data / com.android.settings /
com.android.settings / <
shell @ android :/ data / data / com.android.settings $ ls-l
ls-l
drwxrwxrwx system system 2011-01-01 09:09 a
drwxr-xr-x system system 2011-01-01 09:00 lib
shell @ android :/ data / data / com.android.settings $ rm-ra
rm-r a
rm failed for a, Permission denied
255 | shell @ android :/ data / data / com.android.settings $ while:; do ln-s / data a/file99; done
ln-s / data a/file99; done <
link failed File exists
link failed File exists
link failed File exists
~ ~ ~ Leaving the ~ ~ ~ endlessly
~ ~ ~ Leaving the ~ ~ ~ endlessly
~ ~ ~ ↓ ↓ ↓ ~ ~ ~ to open and run one more command line
C:> adb restore f-10d_2.ab
~ ~ ~ To allow restore ~ ~ ~ Android terminal
~ ~ ~ ↑ ↑ ↑ ~ ~ ~ to open and run one more command line
I made a restore link failed No such file or directory ← here
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed No such file or directory
link failed File exists
link failed File exists
link failed File exists
~ ~ ~ Leaving the ~ ~ ~ endlessly
~ ~ ~ Leaving the ~ ~ ~ endlessly
^ I interrupted by C ← CTRL + C.
C:>
C:> adb shell
shell @ android :/ $ ls-l-d / data
ls-l-d / data
drwxrwxrwx system system 2011-01-01 09:11 data
shell @ android :/ $ exit
exit
C:> adb push mkdevsh / data / local / tmp /
2702 KB / s (648486 bytes in 0.234s)
C:> adb shell
shell @ android :/ $ ls-l-d / data / local
ls-l-d / data / local
drwxr-x - x root root 2011-01-01 09:00 local
shell @ android :/ $ ls-l-d / data / local / tmp
ls-l-d / data / local / tmp
drwxrwx - x shell shell 2011-01-01 09:12 tmp
shell @ android :/ $ ls-l / data / local / tmp
ls-l / data / local / tmp
-Rw-rw-rw-shell shell 648486 2012-09-01 03:47 mkdevsh
shell @ android :/ $ chmod 777 / data / local / tmp / mkdevsh
chmod 777 / data / local / tmp / mkdevsh
shell @ android :/ $ ls-l / data / local / tmp /
ls-l / data / local / tmp /
-Rwxrwxrwx shell shell 648486 2012-09-01 03:47 mkdevsh
shell @ android :/ $ mv / data / local / data / local.org
mv / data / local / data / local.org
shell @ android :/ $ ls-l / data / local.org / tmp
ls-l / data / local.org / tmp
-Rwxrwxrwx shell shell 648486 2012-09-01 03:47 mkdevsh
shell @ android :/ $ mkdir / data / local
mkdir / data / local
shell @ android :/ $ ls-l-d / data / local /
ls-l-d / data / local /
drwxrwxrwx shell shell 2011-01-01 09:12
shell @ android :/ $ ln-s / sys / kernel / uevent_helper / data / local / tmp
ln-s / sys / kernel / uevent_helper / data / local / tmp
shell @ android :/ $ ls-l / data / local / tmp
ls-l / data / local / tmp
lrwxrwxrwx shell shell 2011-01-01 09:12 tmp -> / sys / kernel / uevent_helper
shell @ android :/ $ exit
exit
C:> adb push su / data /
2972 KB / s (380532 bytes in 0.125s)
C:> adb reboot
C:> adb wait-for-device shell
echo / data / local.org / tmp / mkdevsh> / sys / kernel / uevent_helper
echo / data / local.org / tmp / mkdevsh> / sys / kernel / uevent_helper
sh> / sys / kernel / uevent_helper <
shell @ android :/ $
shell @ android :/ $ ls-l / sys / kernel / uevent_helper
ls-l / sys / kernel / uevent_helper
-Rwxrwx - x shell shell 4096 2011-01-01 09:00 uevent_helper
shell @ android :/ $ ls-l / dev / sh
ls-l / dev / sh
-Rwsr-sr-x root root 151964 2011-01-01 09:00 sh
shell @ android :/ $ ls-l / data / su
ls-l / data / su
-Rw-rw-rw-shell shell 380532 2008-02-29 02:33 su
shell @ android :/ $ / dev / sh
/ Dev / sh
# ← root Kita! (It takes a permanent root in the rewritable system area by the mount rw)
# Mount-o rw, remount / system / system
mount-o rw, remount / system / system
# Ls-l / system / bin / su
ls-l / system / bin / su
/ System / xbin / su: No such file or directory
# Dd if = / data / su of = / system / bin / su
dd if = / data / su of = / system / bin / su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.047 secs (8096425 bytes / sec)
# Chown root.root / system / bin / su
chown root.root / system / bin / su
# Chmod 06755 / system / bin / su
chmod 06755 / system / bin / su
# Ls-l / system / bin / su
ls-l / system / bin / su
-Rwsr-sr-x root root 380532 2011-01-01 09:01 su
# Ls-l / system / xbin / su
ls-l / system / xbin / su
/ System / xbin / su: No such file or directory
# Dd if = / data / su of = / system / xbin / su
dd if = / data / su of = / system / xbin / su
743 +1 records in
743 +1 records out
380532 bytes transferred in 0.045 secs (8456266 bytes / sec)
# Chown root.root / system / xbin / su
chown root.root / system / xbin / su
# Chmod 06755 / system / xbin / su
chmod 06755 / system / xbin / su
# Ls-l / system / xbin / su
ls-l / system / xbin / su
-Rwsr-sr-x root root 380532 2011-01-01 09:02 su
# Mount-o ro, remount / system / system
mount-o ro, remount / system / system
# Dd if = / data / su of = / system / bin / su
dd if = / data / su of = / system / bin / su
/ System / bin / su: cannot open for write: Read-only file system
# Rm / data / local / tmp
rm / data / local / tmp
# Mv / data / local / data / local.ln
mv / data / local / data / local.ln
# Mv / data / local.org / data / local
mv / data / local.org / data / local
# Ls-l-d / data / local *
ls-l-d / data / local *
drwxr-x - x root root 2011-01-01 09:00 local
drwxr-x - x root root 2011-01-01 09:02 local.ln
# Sync; sync; sync
sync; sync; sync
# Reboot
reboot
Click to expand...
Click to collapse
any significant improvements in battery life after rooting?
spec-wise it is a very good phone but i really regret the decision of buying this phone cos it heats up so fast and battery life is non-existent.
Rudeyllah said:
Anything for F-02E??
Click to expand...
Click to collapse
Can you please review this phone F-02E? I am really thinking of buying it.
How is the camera, battery life, screen, is the processor capable of working smoothly even with the full HD display, does it get unneccesarily hot, how is the build quality?
lapucele said:
any significant improvements in battery life after rooting?
spec-wise it is a very good phone but i really regret the decision of buying this phone cos it heats up so fast and battery life is non-existent.
Click to expand...
Click to collapse
I am in the same shoe as you with my F-02E, heat so fast and it restarts from 44 degrees centigrade.
Booting Fujitsu F-10D not powering on
My phone suddenly dosent power on. I tested the battery with a tester and it's fully charged. Anyone had a power problem with an Arrows X? Please help me!
The weird thing is I bought my phone at the same time as a friend and his phone stopped working a week ago also!!
When I press the power button, the red charging light blinks 3 time. Any debugging idea?Help me
Thanks
lythekhang said:
My phone suddenly dosent power on. I tested the battery with a tester and it's fully charged. Anyone had a power problem with an Arrows X? Please help me!
The weird thing is I bought my phone at the same time as a friend and his phone stopped working a week ago also!!
When I press the power button, the red charging light blinks 3 time. Any debugging idea?Help me
Thanks
Click to expand...
Click to collapse
I have the same problem too, mobile doesn't start.
When I press the power button, the red charging light blinks 3 time too.
Don't know what a problem, and how this fix.
can anyone confirm if this is working?
Using F-02E ones may work but don't do this. You can never get back when system files go wrong. I already turned mine to paperweight after reboot.
try this
Hi folks
I have Arrows X F-10D , I tried all methods to root it but no hope, I think the build number V22R49C is unrootable
Anyway I suggest to try this lovely program which I found in this site. http://www.mgyun.com/vroot
I have already attached the program, you can download it and give it a try if your build number is lower than above
try this too
Here is another program I have download it from here
help please
Guys help me please
I need DoCoMo apps system
I lost one app by mistake which is for DoCoMo account numbers
When I create new contact it shows me only Google account to save in, but no phone contacts
Please help
Somebody upload this app for me
I am creating a list of the reservedodm fuse settings. its a set of numbers that refer to the programmable fuses embedded in moto phones (that i know of) that controls your ability to downgrade to different versions of android and can even list if your phone is currently unlocked.
at the moment this is purely for reference for possible future projects
if your willing to contribute to the thread please list the following in your post
*last sbf used including the version of android
*the newest sbf that has been applied to your phone at any time
*the highest version of android & moto version that has ever been on your phone
*version of android with moto version
*any update.zips used at any time
*specify whether phone is DX2 or MX2
*the print out from the reservedodm file
*system version
*kernel version
*anything else you wish to contribute
how to get reservedodm
Code:
[email protected]:/home/lrs# adb shell
$ su
# cat /sys/firmware/fuse/ReservedOdm
40000000000040006000100000000
you can also send me the contents of the fuse file (compress and upload or email to me)
please include the above information including sbfs, update.zips, system versions, kernel versions
example code to copy the fuses folder
Code:
# cp /sys/firmware/fuse /sdcard-ext/keep/
cp: /sys/firmware/fuse is a directory (not copied).
# cp -r /sys/firmware/fuse /sdcard-ext/keep/
# exit
$ exit
[email protected]:/home/lrs# mkdir fuses
[email protected]:/home/lrs# adb pull /sdcard-ext/keep/fuse /home/lrs/fuses
pull: building file list...
pull: /sdcard-ext/keep/fuse/ReservedOdm -> /home/lrs/fuses/ReservedOdm
pull: /sdcard-ext/keep/fuse/SecBootDeviceSelectRaw -> /home/lrs/fuses/SecBootDeviceSelectRaw
pull: /sdcard-ext/keep/fuse/SkipDevSelStraps -> /home/lrs/fuses/SkipDevSelStraps
pull: /sdcard-ext/keep/fuse/SwReserved -> /home/lrs/fuses/SwReserved
pull: /sdcard-ext/keep/fuse/SpareBits -> /home/lrs/fuses/SpareBits
pull: /sdcard-ext/keep/fuse/sku -> /home/lrs/fuses/sku
pull: /sdcard-ext/keep/fuse/SecureBootKey -> /home/lrs/fuses/SecureBootKey
pull: /sdcard-ext/keep/fuse/SecBootDeviceSelect -> /home/lrs/fuses/SecBootDeviceSelect
pull: /sdcard-ext/keep/fuse/SecBootDeviceConfig -> /home/lrs/fuses/SecBootDeviceConfig
pull: /sdcard-ext/keep/fuse/KeyProgrammed -> /home/lrs/fuses/KeyProgrammed
pull: /sdcard-ext/keep/fuse/JtagDisable -> /home/lrs/fuses/JtagDisable
pull: /sdcard-ext/keep/fuse/DeviceKey -> /home/lrs/fuses/DeviceKey
pull: /sdcard-ext/keep/fuse/kfuse_raw -> /home/lrs/fuses/kfuse_raw
pull: /sdcard-ext/keep/fuse/OdmProduction -> /home/lrs/fuses/OdmProduction
14 files pulled. 0 files skipped.
0 KB/s (633 bytes in 0.972s)
sbf used 2.3.6 ntelos (newest)
update.zip 45.0.23 ntelos (latest)
MX2
system: 45.0.43.MB867.ACG-nTelos.en.US
kernel: 2.6.32.9-00011-gbc368b9 [email protected] #2
reservedodm: 40000000000040006000100000000
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
birdie said:
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
Click to expand...
Click to collapse
Hello. Is it possible to edit this file on Android giving some editor root privileges?
Yes but you'll have to reboot your phone after that.
Registered just to thank you for this! I was trying to get used to the buttons being flipped in comparison to my previous phones, but just couldn't
In case anyone comes here and is as newbie as I am:
If you're unrooted/don't want to root and are worried by the previous post, I did it with an unrooted phone just fine. Just needed twrp and adb. That post is asking about editing directly on the phone, while OP's outlined method has you using your desktop and... I used notepad++ but I assume regular notepad will work too, just right click and "open with..." to edit the .kl file. By RW mode, OP means having system mounted in read/write mode, which twrp will do by default at least in the version I'm using which is 3.1.1-0-x2. Just don't check off the option to make it read only. By the way, it wouldn't over-write for me, so I deleted synaptics_dsx.kl in twrp then pushed the edited file.
Can someone help me do this!
In simpler terms can someone explain this to me?
Clarification of explanation
Dear birdie,
Could you perhaps elaborate on the "mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl " instruction?
I am trying to disable the "recent apps" button on the Moto G3 in LineageOS 14.1, and I think if I map Home twice, (once more on `key 580` {or what the number on my type of device will be}), i have obtained that goal.
Any suggestions are appreciated, kind regards.
birdie said:
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
Click to expand...
Click to collapse
Explicit intended steps.
After doing some research I think
mount system in RW (rewritable) mode and fetch(1) $/system/usr/keylayout/synaptics_dsx.kl$ and edit it.
Click to expand...
Click to collapse
can be performed with the following steps:
0. Commanders intend: mount system in RW (rewritable) mode:
1. Download minimal ADB and Fastboot.
2. Install TWRP and root on your phone
3. Steps: open adb on pc. Current location = \url{E:\somefolder\Minimal ADB and Fastboot_techbeasts\py.cmd
4. connect the phone with usb to pc.
5. Select mount in TWRP:
6. select \textbackslash system
7. press mount.
8. source for next step: \url{https://forum.xda-developers.com/xperia-z2/help/help-to-mount-rw-twrp-recovery-t3376485}
9. \url{https://askubuntu.com/questions/175739/how-do-i-remount-a-filesystem-as-read-write}
10. \url{https://stackoverflow.com/questions/28009716/how-can-i-remount-my-android-system-as-read-write-in-a-bash-script-using-adb}
11. finally the last link, the following command sequence appears to solve the issue:
Code:
# Script to mount Android Device as read/write.
# List the Devices.
adb devices;
# Run adb as root (Needs root access).
adb root;
# Since you're running as root su is not required
adb shell mount -o rw,remount /;
12. Commanders intend: fetch(1) $/system/usr/keylayout/synaptics_dsx.kl$ and edit it.
13. Source used to execute commanders intend: \url{https://forum.xda-developers.com/shield-tv/general/change-3rd-party-remote-key-layout-root-t3548871}
14. steps: adb shell \textgreater enter \textless
15. That shows
Code:
~ # <-[6
\end{verbatim}
\item ignore that weird stuff and just immediately after enter:
\begin{verbatim}
cat /proc/bus/input/devices
16. Now you will have a list of connected remote/controller, take a note of the Vendor number and the Product number.
17. ctrl+c to get out of the to me uknown, ~\# thingy
18. adb pull $/system/usr/keylayout$
19. that yielded for my moto G3:
Code:
E:\somefolder\Minimal ADB and Fastboot_techbeasts>adb pull /system/usr/keylayout
pull: building file list...
pull: /system/usr/keylayout/qwerty.kl -> ./qwerty.kl
pull: /system/usr/keylayout/Vendor_2378_Product_100a.kl -> ./Vendor_2378_Product_100a.kl
pull: /system/usr/keylayout/Vendor_2378_Product_1008.kl -> ./Vendor_2378_Product_1008.kl
pull: /system/usr/keylayout/Vendor_22b8_Product_093d.kl -> ./Vendor_22b8_Product_093d.kl
pull: /system/usr/keylayout/Vendor_1d79_Product_0009.kl -> ./Vendor_1d79_Product_0009.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f036.kl -> ./Vendor_1bad_Product_f036.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f027.kl -> ./Vendor_1bad_Product_f027.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f023.kl -> ./Vendor_1bad_Product_f023.kl
pull: /system/usr/keylayout/Vendor_1bad_Product_f016.kl -> ./Vendor_1bad_Product_f016.kl
pull: /system/usr/keylayout/Vendor_1949_Product_0401.kl -> ./Vendor_1949_Product_0401.kl
pull: /system/usr/keylayout/Vendor_18d1_Product_5018.kl -> ./Vendor_18d1_Product_5018.kl
pull: /system/usr/keylayout/Vendor_18d1_Product_2c40.kl -> ./Vendor_18d1_Product_2c40.kl
pull: /system/usr/keylayout/Vendor_1689_Product_fe00.kl -> ./Vendor_1689_Product_fe00.kl
pull: /system/usr/keylayout/Vendor_1689_Product_fd01.kl -> ./Vendor_1689_Product_fd01.kl
pull: /system/usr/keylayout/Vendor_1689_Product_fd00.kl -> ./Vendor_1689_Product_fd00.kl
pull: /system/usr/keylayout/Vendor_1532_Product_0900.kl -> ./Vendor_1532_Product_0900.kl
pull: /system/usr/keylayout/Vendor_12bd_Product_d015.kl -> ./Vendor_12bd_Product_d015.kl
pull: /system/usr/keylayout/Vendor_1038_Product_1412.kl -> ./Vendor_1038_Product_1412.kl
pull: /system/usr/keylayout/Vendor_0b05_Product_4500.kl -> ./Vendor_0b05_Product_4500.kl
pull: /system/usr/keylayout/Vendor_05ac_Product_0239.kl -> ./Vendor_05ac_Product_0239.kl
pull: /system/usr/keylayout/Vendor_0583_Product_2060.kl -> ./Vendor_0583_Product_2060.kl
pull: /system/usr/keylayout/Vendor_054c_Product_0268.kl -> ./Vendor_054c_Product_0268.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c532.kl -> ./Vendor_046d_Product_c532.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c299.kl -> ./Vendor_046d_Product_c299.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c294.kl -> ./Vendor_046d_Product_c294.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c21f.kl -> ./Vendor_046d_Product_c21f.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c21d.kl -> ./Vendor_046d_Product_c21d.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c219.kl -> ./Vendor_046d_Product_c219.kl
pull: /system/usr/keylayout/Vendor_046d_Product_c216.kl -> ./Vendor_046d_Product_c216.kl
pull: /system/usr/keylayout/Vendor_046d_Product_b501.kl -> ./Vendor_046d_Product_b501.kl
pull: /system/usr/keylayout/Vendor_045e_Product_0719.kl -> ./Vendor_045e_Product_0719.kl
pull: /system/usr/keylayout/Vendor_045e_Product_028e.kl -> ./Vendor_045e_Product_028e.kl
pull: /system/usr/keylayout/Vendor_0079_Product_0011.kl -> ./Vendor_0079_Product_0011.kl
pull: /system/usr/keylayout/Generic.kl -> ./Generic.kl
pull: /system/usr/keylayout/AVRCP.kl -> ./AVRCP.kl
35 files pulled. 0 files skipped.
37 KB/s (49818 bytes in 1.285s)
20. All those files are for pre-built in controllers that you can connect the the phone, eg xbox 360 controller, snes controller etc. Except for AVRCP.kl and Generic.kl, these are used for the normal phone.
21. Change Generic.kl as AVRCP.kl says AVRCP.kl is not used anymore.
22. Copy the Generic.kl back:
Code:
adb root
adb disable-verity
adb reboot
(power down, boot into twrp again)
adb root
adb remount
adb push "layout file" /system/usr/keylayout (becomes in this case:)
adb push Generic.kl /system/usr/keylayout
adb reboot
birdie said:
Here's how it can be done.
Reboot into TWRP, mount /system in RW mode, fetch(1) /system/usr/keylayout/synaptics_dsx.kl and edit it.
Originally it looks like
Code:
key 158 BACK VIRTUAL
key 172 HOME VIRTUAL
key 580 APP_SWITCH VIRTUAL
You need to change it to
Code:
key 158 APP_SWITCH VIRTUAL
key 172 HOME VIRTUAL
key 580 BACK VIRTUAL
and then upload(2) back to your phone.
Code:
1. adb pull /system/usr/keylayout/synaptics_dsx.kl
2. adb push synaptics_dsx.kl /system/usr/keylayout/
Hopefully this feature will be implemented at the user level.
Click to expand...
Click to collapse
Thanks. This is the hint I needed to make APP_SWITCH work on a device I'm playing with (SM-T113NU)
Hi there,
The device is rooted.
But
Code:
adb shell ls -l /dev/block/bootdevice/by-name
It returned
Code:
/dev/block/bootdevice/by-name: Permission denied
However,
Code:
adb shell su -c 'ls -l /dev/block/bootdevice/by-name'
It returned
Code:
lrwxrwxrwx root root 1970-01-21 16:08 DDR -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-21 16:08 DRIVER -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-21 16:08 LOGO -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-21 16:08 aboot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-21 16:08 abootbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-21 16:08 apdp -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-21 16:08 bluetooth -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-21 16:08 boot -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-21 16:08 cache -> /dev/block/mmcblk0p41
lrwxrwxrwx root root 1970-01-21 16:08 config -> /dev/block/mmcblk0p40
lrwxrwxrwx root root 1970-01-21 16:08 devinfo -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-21 16:08 dpo -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-21 16:08 fsc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-21 16:08 fsg -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-21 16:08 hyp -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-21 16:08 hypbak -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-21 16:08 keystore -> /dev/block/mmcblk0p39
lrwxrwxrwx root root 1970-01-21 16:08 limits -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-21 16:08 misc -> /dev/block/mmcblk0p38
lrwxrwxrwx root root 1970-01-21 16:08 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-21 16:08 modemst1 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-21 16:08 modemst2 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-21 16:08 msadp -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-21 16:08 oem_dycnvbk -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-21 16:08 oem_stanvbk -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-21 16:08 param -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-21 16:08 persist -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 1970-01-21 16:08 pmic -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-21 16:08 pmicbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-21 16:08 recovery -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-21 16:08 reserve1 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-21 16:08 reserve2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-21 16:08 rpm -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-21 16:08 rpmbak -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-21 16:08 sbl1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-21 16:08 sbl1bak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-21 16:08 sdi -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-21 16:08 sec -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-21 16:08 ssd -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-21 16:08 system -> /dev/block/mmcblk0p42
lrwxrwxrwx root root 1970-01-21 16:08 tz -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-21 16:08 tzbak -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-21 16:08 userdata -> /dev/block/mmcblk0p43
In addition,
Code:
adb pull /dev/block/mmcblk0p43 43.img
It returned
Code:
adb: error: remote object '/dev/block/mmcblk0p43' does not exist
How to resolve the issue of "permission denied"?
Why are there differences in terms of results between adb shell ls -l /dev/block/bootdevice/by-name and adb shell su -c 'ls -l /dev/block/bootdevice/by-name'?
Why adb pull failed to create a disk image?
Is mmcblk0p43 recognized as a file so adb pull could copy it out of /dev/block/?
Thanks in advance.
--- Solution ---
Install adbd insecure and check "Enable insecure adbd" and"Enable as boot", these two boxes;
However, it ensued another problem that the device is no more recognised by adb. And this issue is solved by
- installing SELinux Switch and choosing "Permissive".
And both
Code:
adb shell ls -l /dev/block/bootdevice/by-name
and
Code:
adb pull /dev/block/mmcblk0p43 43.img
worked.
But how come that adbd insecure could enable the 2 commands above?
Apparently the device's bootloader is locked.
Code:
fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.072s]
wenyendev said:
Hi there,
The device is rooted.
But
Code:
adb shell ls -l /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
There are 2 ways:
1. Use adb shell su instead. And then copy everything from root dir into internal storage after that you can pull files from internal storage using adb pull
2. Disable selinux enforcing with setenforce 0
'adb root' done?
CXZa said:
'adb root' done?
Click to expand...
Click to collapse
After adb root, it returned
Code:
adbd cannot run as root in production builds
Solved.. okay, I just leave this to this thread then. One more option...
Code:
adb exec-out "su -c cat /dev/block/mmcblk0p43" > [full path\]43.img
Above should work but there is quite many cases that it doesn't, i.e. \n are replaced with \r\n corrupting the file. Then below should fix the problem. If exec-out doesn't work, shell can be used too...
Code:
adb exec-out "su -c cat /dev/block/mmcblk0p43" | dos2unix -f > [full path\]43.img
More info...
Read binary stdout data like screencap data from adb shell?
Is it possible to read binary stdout from an adb shell command? For example, all examples of how to use screencap include two steps: adb shell screencap -p /sdcard/foo.png adb pull /sdcard/foo.png
stackoverflow.com
@CXZa dos2unix does not solve it, will mess up even more. best workaround so far is compress/decompress (for example gzip) also take care about exec-out stderr is mixed up with stdout.
btw @wenyendev the answer applies to all your following questions:
adbd cannot run as root in production builds. you have three options. 1) use adb root in TWRP recovery mode. 2) use insecure adbd daemon 3) use adb shell su shell instead. that's it.
https://forum.xda-developers.com/t/...as-root-in-production-builds-adb-root.4528831
https://forum.xda-developers.com/t/permission-denied-following-ls-dev-block.4530681
https://forum.xda-developers.com/t/permission-denied-cat-proc-partitions.4494267
https://forum.xda-developers.com/t/...wing-partition-identification-command.4528373
https://forum.xda-developers.com/t/...rtition-on-an-unrooted-android-device.4528247
https://forum.xda-developers.com/t/...ied-under-adb-shell-after-granting-su.4528815
https://forum.xda-developers.com/t/dd-versus-adb-pull.4535577
https://forum.xda-developers.com/t/closed-how-to-pull-partition-to-external-disk.4537667
Btw original SELinuxModeChanger by @MrBIMC occupied by SELinux Toggler (which is basically same as Selinux Switch) will work only on kernel that support developer mode.
[APP][Root][4.2+]SELinuxModeChanger v10.0 :: [24.07.2017]
Now opensourced under gplv3! GITHUB Get it in f-droid F-DROID page (v10 probably won't be there until release of stable gradle 4.0 and buildtools 26) Now available on the XDA Labs! XDA Labs page (UPD: somebody released a fork without changing...
forum.xda-developers.com
aIecxs said:
dos2unix does not solve it, will mess up even more.
Click to expand...
Click to collapse
No it doesn't. It is explained in the comments in the link I gave...
I know that link (and comments)
please try your own
https://pastebin.com/Z5ptLhqM
Various tests there. Tried with cache too in Windows using the latest dos2unix version mentioned there. Works if one has that problem, if not might make a mess. But in your case it looks like the file sizes aren't the same even when the command is the same. Odd...
Edit: I actually used shell too with the cache... exec-out also with some smaller files. So the exec-out can give different outputs... Edit2: As well as dos2unix it seems. Odd...
it works best with compressed streams as the decompression algorithm can handle minor encoding issues (such as CR CR LF)
Code:
C:\Android> adb exec-out su -c "cat /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/cache 2> /dev/null | gzip" > cache.img.gz
after unpacking gzip (7-zip) I recommend checksum (if possible) but might not work "online"
Code:
CUBOT_KING_KONG:/ # md5sum /dev/block/platform/mtk-msdc.0/11120000.msdc0/by-name/cache
C:\Android> certutil.exe -hashfile cache.img MD5
@wenyendev does not concern you as afaik you're on darwin/macOS
You did a lot of tests indeed. BTW, not the best partition that cache of yours for testing dos2unix. Nothing to do for it as it didn't change a thing in those last files that worked.
So, many things might not work and shell is probably better option to use, and linux and compression. Still, if one doesn't have enough space i.e. sd card, it's an option...
Tested again. For me shell and exec-out work the same way. Both need the dos2unix treatment. Repeated it and it messed the file as there was still "leftovers" in it...
Code:
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" > C:\bin\adb\cache_aaa.img
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_bbb.img
C:\bin\adb>adb exec-out "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_ccc.img
C:\bin\adb>adb shell "su -c md5sum /dev/block/mmcblk0p47"
a87484dff7370bf71a253ee9af6baedf /dev/block/mmcblk0p47
C:\bin\adb>md5sum C:\bin\adb\cache_*.img
\2922f7f1ab51fa650779586e291e6783 *C:\\bin\\adb\\cache_aaa.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_bbb.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_ccc.img
C:\bin\adb>dos2unix -f -n cache_ccc.img cache_ddd.img
dos2unix: converting file cache_ccc.img to file cache_ddd.img in Unix format...
C:\bin\adb>md5sum C:\bin\adb\cache_ddd.img
\de27ad05c61510f4847651c44ab9922e *C:\\bin\\adb\\cache_ddd.img
results may differ between Win 7 10 11 cmd PowerShell platform tools and adb version
CXZa said:
Tested again. For me shell and exec-out work the same way. Both need the dos2unix treatment. Repeated it and it messed the file as there was still "leftovers" in it...
Code:
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" > C:\bin\adb\cache_aaa.img
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_bbb.img
C:\bin\adb>adb exec-out "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_ccc.img
C:\bin\adb>adb shell "su -c md5sum /dev/block/mmcblk0p47"
a87484dff7370bf71a253ee9af6baedf /dev/block/mmcblk0p47
C:\bin\adb>md5sum C:\bin\adb\cache_*.img
\2922f7f1ab51fa650779586e291e6783 *C:\\bin\\adb\\cache_aaa.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_bbb.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_ccc.img
C:\bin\adb>dos2unix -f -n cache_ccc.img cache_ddd.img
dos2unix: converting file cache_ccc.img to file cache_ddd.img in Unix format...
C:\bin\adb>md5sum C:\bin\adb\cache_ddd.img
\de27ad05c61510f4847651c44ab9922e *C:\\bin\\adb\\cache_ddd.img
Click to expand...
Click to collapse
Apparently it did not work out for me.
CXZa said:
Tested again. For me shell and exec-out work the same way. Both need the dos2unix treatment. Repeated it and it messed the file as there was still "leftovers" in it...
Code:
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" > C:\bin\adb\cache_aaa.img
C:\bin\adb>adb shell "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_bbb.img
C:\bin\adb>adb exec-out "su -c cat /dev/block/mmcblk0p47" | dos2unix -f > C:\bin\adb\cache_ccc.img
C:\bin\adb>adb shell "su -c md5sum /dev/block/mmcblk0p47"
a87484dff7370bf71a253ee9af6baedf /dev/block/mmcblk0p47
C:\bin\adb>md5sum C:\bin\adb\cache_*.img
\2922f7f1ab51fa650779586e291e6783 *C:\\bin\\adb\\cache_aaa.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_bbb.img
\a87484dff7370bf71a253ee9af6baedf *C:\\bin\\adb\\cache_ccc.img
C:\bin\adb>dos2unix -f -n cache_ccc.img cache_ddd.img
dos2unix: converting file cache_ccc.img to file cache_ddd.img in Unix format...
C:\bin\adb>md5sum C:\bin\adb\cache_ddd.img
\de27ad05c61510f4847651c44ab9922e *C:\\bin\\adb\\cache_ddd.img
Click to expand...
Click to collapse
Apparently it did not work on my device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The environment is adb on Macintosh High Sierra.
Whether I enabled adbd insecure & Selinux, it produced the same result.
aIecxs said:
@CXZa dos2unix does not solve it, will mess up even more. best workaround so far is compress/decompress (for example gzip) also take care about exec-out stderr is mixed up with stdout.
btw @wenyendev the answer applies to all your following questions:
adbd cannot run as root in production builds. you have three options. 1) use adb root in TWRP recovery mode. 2) use insecure adbd daemon 3) use adb shell su shell instead. that's it.
https://forum.xda-developers.com/t/...as-root-in-production-builds-adb-root.4528831
https://forum.xda-developers.com/t/permission-denied-following-ls-dev-block.4530681
https://forum.xda-developers.com/t/permission-denied-cat-proc-partitions.4494267
https://forum.xda-developers.com/t/...wing-partition-identification-command.4528373
https://forum.xda-developers.com/t/...rtition-on-an-unrooted-android-device.4528247
https://forum.xda-developers.com/t/...ied-under-adb-shell-after-granting-su.4528815
https://forum.xda-developers.com/t/dd-versus-adb-pull.4535577
Btw original SELinuxModeChanger by @MrBIMC occupied by SELinux Toggler (which is basically same as Selinux Switch) will work only on kernel that support developer mode.
[APP][Root][4.2+]SELinuxModeChanger v10.0 :: [24.07.2017]
Now opensourced under gplv3! GITHUB Get it in f-droid F-DROID page (v10 probably won't be there until release of stable gradle 4.0 and buildtools 26) Now available on the XDA Labs! XDA Labs page (UPD: somebody released a fork without changing...
forum.xda-developers.com
Click to expand...
Click to collapse
What do you mean by using adb root in recovery TWRP mode?
The command above was run in the "Terminal" <- "Advanced" in TWRP.
wenyendev said:
What do you mean by using adb root in recovery TWRP mode?
Click to expand...
Click to collapse
Just connect the usb cable and try it in mac's terminal.
CXZa said:
Just connect the usb cable and try it in mac's terminal.
Click to expand...
Click to collapse
Ok, adb root worked only when adbd insecure is enabled.
in TWRP recovery, adb root is already enabled by default. no need to type 'adb root'
on macOS one have to install dos2unix
Code:
brew install dos2unix
aIecxs said:
in TWRP recovery, adb root is already enabled by default. no need to type 'adb root'
on macOS one have to install dos2unix
Code:
brew install dos2unix
Click to expand...
Click to collapse
After installation of dos2unix,
Code:
./adb shell "su -c cat /dev/block/mmcblk0p43" | dos2unix -f /Users/wenyuan/Desktop/android/adb/43.img
still did not work.
Now you need that ">"...
Code:
./adb shell "su -c cat /dev/block/mmcblk0p43" | dos2unix -f > /Users/wenyuan/Desktop/android/adb/43.img
But do you have that \n replacing problem? If not dos2unix is not needed.
Code:
./adb shell "su -c cat /dev/block/mmcblk0p43" > /Users/wenyuan/Desktop/android/adb/43.img