Related
Hi Forum.
When i try to mount and push apk´s from my PC, i get an error, but i can´t figure out how to get past that, so pleace help me, as i´m proberbly not the only one with that problem...
When checking permissions i get:
-rwsr-xr-x root root 178 2010-11-07 17:19 sh
And that looks allright i think ?
But when i then try to mount and push with:
@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
@adb push content/Phonebook.apk /sdcard/Phonebook.apk
I get this in return:
mount: Operation not permitted
2219 KB/s (3195743 bytes in 1.406s)
/system/app/Phonebook.apk: cannot open for write: Read-only file system
I have installed app2sd, and jit002, and the phone is rooted (with the alternative rooting metod) and it works fine i think, no crashing or anything.
The only problem is that i can´t mount and push...
Here is what i get when i try to see what is mounted on the phone:
D:\>adb shell
$ mount
mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block//vold/179:2 /system/sd ext2 rw,errors=continue 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,gr
oup_id=0,allow_other 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
If you install Root Explorer then you can toggle RO/RW for the system folder.
And when you start Root Explorer, Superuser should say that Root Explorer has been granted superuser rights (or something like that).
Make sure you have superuser and busybox installed, that debugging is activated in the phone and also checkmark 'keep display on' in the debugging options so you can see popups from superuser.
good luck!
mattiL said:
If you install Root Explorer then you can toggle RO/RW for the system folder.
And when you start Root Explorer, Superuser should say that Root Explorer has been granted superuser rights (or something like that).
Click to expand...
Click to collapse
This didn't work for me when trying to install a theme.
mattiL said:
Make sure you have superuser and busybox installed, that debugging is activated in the phone and also checkmark 'keep display on' in the debugging options so you can see popups from superuser.
good luck!
Click to expand...
Click to collapse
Correct and...
when you enter "@adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" on your PC, check your mobile and click OK at the message that ask for su access.
I don't know if it is anything to do with it, but if I
Adb kill-server and then
Adb start-server
Everything works fine. Without I always get 'permission denied'
sent from my rooted 2.1 X10i (+JIT) using XDA App
Anybody with a Sony Tablet S, a few minutes to spare, and some basic ADB knowledge, can you please run the following command for me?
Code:
adb shell mount > sony-tablet-s-mounts.txt
Then simply upload the text file called sony-tablet-s-mounts.txt that is in your adb tools folder or whatever directory you ran that command from.
Also please run.
Code:
adb shell cat /proc/mounts/ > sony-tablet-s-proc-mounts.txt
Then again upload that file that was outputted.
Here we go:
mount
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.bbb.btr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.polarbit.rthunderlite-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
proc/mounts
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p1 /configs ext2 ro,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p3 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p9 /log ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/svold/179:17 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/vold/179:11 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.bbb.btr-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.polarbit.rthunderlite-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,batch_sync,utf8,comp_uni,avoid_dlink,errors=remount-ro 0 0
Anything else?
Also tried proc/mtd but that had no output.
Sent from my Sony Tablet S using Tapatalk
manually push busybox to /data/tmp/local/ and try to remount /system as RW
then try to push su binary to /system/bin/ (give it permission 06755)
then try to push Superuser.apk to /system/app/
btw does this tablet have some sort of recovery mode? what abt bootloader status?
Code:
[email protected] ~/data/Android/exploits $ adb push busybox /data/tmp/local/
failed to copy 'busybox' to '/data/tmp/local/': No such file or directory
[email protected] ~/data/Android/exploits $ adb push busybox /data/local/
1322 KB/s (1062992 bytes in 0.784s)
[email protected] ~/data/Android/exploits $ adb shell
$ chmod 777 /data/local/busybox
$ /data/local/busybox su
su: must be suid to work properly
$ /data/local/busybox sulogin
sulogin: no password entry for root
$ /data/local/busybox mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: permission denied (are you root?)
$ mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: Operation not permitted
$ /data/local/busybox whoami
whoami: unknown uid 2000
So... stuck at remounting with rw permissions. no permissions
There is a recovery mode (power + volume-up key at boot).
abt bootloader status? Don't know what that is, and how to check.
Elkan85 said:
Code:
[email protected] ~/data/Android/exploits $ adb push busybox /data/tmp/local/
failed to copy 'busybox' to '/data/tmp/local/': No such file or directory
[email protected] ~/data/Android/exploits $ adb push busybox /data/local/
1322 KB/s (1062992 bytes in 0.784s)
[email protected] ~/data/Android/exploits $ adb shell
$ chmod 777 /data/local/busybox
$ /data/local/busybox su
su: must be suid to work properly
$ /data/local/busybox sulogin
sulogin: no password entry for root
$ /data/local/busybox mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: permission denied (are you root?)
$ mount -o remount,rw -t yaffs2 /dev/block/mmcblk0p3 /system
mount: Operation not permitted
$ /data/local/busybox whoami
whoami: unknown uid 2000
So... stuck at remounting with rw permissions. no permissions
There is a recovery mode (power + volume-up key at boot).
abt bootloader status? Don't know what that is, and how to check.
Click to expand...
Click to collapse
why are u remounting as yaffs2?
just use:
Code:
busybox mount -o remount, rw /system
is adb active in recovery? if yes then try pushing su/busybox when in recovery mode...
ADB ain't active in recovery mode.
in fact we only have 3 choices in recovery mode:
- reboot
- update from sd-card
- return to factory settings
try to find a fastboot bin for linux, maybe can use it to
fastboot into bootloader(?)
Code:
$$ /data/local/busybox mount -o remount, rw /system
mount: permission denied (are you root?)
$$ mount -o remount, rw /system
mount: Operation not permitted
Elkan85 said:
ADB ain't active in recovery mode.
in fact we only have 3 choices in recovery mode:
- reboot
- update from sd-card
- return to factory settings
try to find a fastboot bin for linux, maybe can use it to
fastboot into bootloader(?)
Code:
$$ /data/local/busybox mount -o remount, rw /system
mount: permission denied (are you root?)
$$ mount -o remount, rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
There should be generic update.zip to flash via recovery for SU. Try if that works
Sent from my GT-I9100 using XDA App
DooMLoRD said:
There should be generic update.zip to flash via recovery for SU. Try if that works
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
found some...
But with all i get:
signature verification failed
anyway to avoid that?
Posted on the sony forum a request for the original update.zip
hope i can get something...
hi
i cant see anyway to go in fastboot.
boot with vol+ there are stop in the stock recovery "Android system recovery <Rev.7 <3e>"
3 Option in recovery:
1. cancel ans restart device
2. Update system from sd card.
3. Reset to factory setting
But with sdcard update there comes E:signature verfication fail i try this file http://forum.xda-developers.com/showthread.php?t=1288348
adb works with debugging is enable, but the remount of the /system dosnt work.
how we become root ?
The Sony Tablet has a 3e recovery, isn't this the same issue as with this >> http://forum.xda-developers.com/showthread.php?t=833423
here some infos
Code:
cat /proc/partitions
major minor #blocks name
179 0 15629312 mmcblk0
179 1 2048 mmcblk0p1
179 2 393216 mmcblk0p2
179 3 393216 mmcblk0p3
179 4 524288 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 49152 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 393216 mmcblk0p8
179 9 16384 mmcblk0p9
179 10 4194304 mmcblk0p10
179 11 9368576 mmcblk0p11
179 16 31702016 mmcblk1
179 17 31697920 mmcblk1p1
$
edit: add dmesg.txt
is there any way to make temporary root ?
jhepoy said:
The Sony Tablet has a 3e recovery, isn't this the same issue as with this >> http://forum.xda-developers.com/showthread.php?t=833423
Click to expand...
Click to collapse
Tried that, this aint gonna work because it try to mount /system rw.
Sent from my Sony Tablet S using Tapatalk
Elkan85 said:
Tried that, this aint gonna work because it try to mount /system rw.
Click to expand...
Click to collapse
You have /system in rw ? then you can make root.
PeterPan6754 said:
You have /system in rw ? then you can make root.
Click to expand...
Click to collapse
I wish i had rw in /system..
Still trying to exploit this ****..
Elkan85 said:
I wish i had rw in /system..
Still trying to exploit this ****..
Click to expand...
Click to collapse
hello
have you make chances in the instal.lbat file ?
and use the su from the honeycomb superuser files ?
im not at home and cant test it.
Code:
ECHO Installing modified recovery
%adb% start-server >nul
%adb% -d wait-for-device >nul
%adb% -d shell mount -o rw,remount /dev/block/mmcblk0p3 /system
%adb% -d push %su% /system/bin/su
%adb% -d shell chmod 06755 /system/xbin/su
GOTO :finished
Thanks for trying so hard guys, if you can crack this and bring root to the tablet s you will be legends. I will happily donate via paypal as a thank you.
PeterPan6754 said:
hello
have you make chances in the instal.lbat file ?
and use the su from the honeycomb superuser files ?
im not at home and cant test it.
Code:
ECHO Installing modified recovery
%adb% start-server >nul
%adb% -d wait-for-device >nul
%adb% -d shell mount -o rw,remount /dev/block/mmcblk0p3 /system
%adb% -d push %su% /system/bin/su
%adb% -d shell chmod 06755 /system/xbin/su
GOTO :finished
Click to expand...
Click to collapse
That doesn't work either..
Because we have no mountain permissions..
Sent from my HTC Desire using XDA App
Elkan85 said:
That doesn't work either..
Because we have no mountain permissions..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
yes it dosnt work
Getting temporary root.
> Starting adb server: Success
Checking for temporary root.
Installing rageagainstthecage.
> Uploading rageagainstthecage: Success
> chmod rageagainstthecage: Success
> Running rageagainstthecage: Success
Checking for temporary root.
> Stopping adb server: Success
> Starting adb server: Success
> Checking for root: Error: timed out
temp root failed! install cannot continue.
Click to expand...
Click to collapse
Hi to all. I'm Abe Wayer.
I'm dreaming to start changing at first my own mobile OS end maybe going to develop a day.
Today it's just all the afternoon that i google....
I became root, I partitioned my sd and installing sdk & adb tools in a couple of days.
something goes quickly something not.
I have a galaxy ace with 2.3.6
I thought to start my develop time using adb.
first at all adb push.
So i made:
adb push test.txt /sdcard/test.txt
And i have: permission denied
I googled a lot and nothing worked:
Debug usb is on.
I umounted sdcard from /media (I use linux)
I've tried this as well:
mount -o remount , rw /dev/block/void/179:9 /sdcard
or
mount -r -w -o remount -t vfat /dev/block/void/179:9 /sdcard
But nothing work!
If im not able to push a file on a sd what i dream for?
My sdcard has two partition linux call them sdc1 & sdc2 first is 1500 Mib second 400
Thanks for your help
No Links too?
Please give me a hand!:crying:
Dont you have a guide ive not fought?
Please.....
News:
I've tried:
adb shel => su =>fdisk -l
and i've got the device name but if do:
# mount rw -o remount, rw -t fat32 /dev/stl10 /sdcard
I always have:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
But is there somewhere on the web an adb shel man complete with examples?
How do i obtain -w permission on my sd card?
adb pull works so i can read....
if i try ls -l /sdcard i got: lrwxrwxrwx root root 2012-12-18 02:01 sdcard -> /mnt/sdcard
So root can write.
Have i to change owner to the card?
Or simply with adb i'd say i'm root?
have i to umount sdcard?
Please!
Abe Wayer said:
# mount rw -o remount, rw -t fat32 /dev/stl10 /sdcard
Click to expand...
Click to collapse
Wrong usage, correct usage (provided that the device is correct):
Code:
mount -o rw, remount -t fat32 /dev/stl10 /sdcard
RoberGalarga said:
Wrong usage, correct usage (provided that the device is correct):
Code:
mount -o rw, remount -t fat32 /dev/stl10 /sdcard
Click to expand...
Click to collapse
Doesn't work as well.
my fdisk -l output is this:
# fdisk -l
Disk /dev/bml10: 41 MB, 41943040 bytes
255 heads, 63 sectors/track, 5 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/bml10 doesn't contain a valid partition table
Disk /dev/stl10: 37 MB, 37748736 bytes
255 heads, 63 sectors/track, 4 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Abe Wayer said:
if i try ls -l /sdcard i got: lrwxrwxrwx root root 2012-12-18 02:01 sdcard -> /mnt/sdcard
So root can write.
Click to expand...
Click to collapse
You don't know that. This is just a symbolic link, not the volume itself. Do:
$ ls -l /mnt/sdcard
This will show you if the card is mounted properly. Also issue a "mount" command, no parameter. But you should not need to remount it, the sdcard is handled by magic via the vold daemon. As soon as you remove it from the GNU/Linux machine, vold will mount it in Android.
kuisma said:
Y
Do: $ ls -l /mnt/sdcard
.
Click to expand...
Click to collapse
With ls - /mnt I have:
# ls -l /mnt/
drwxr-xr-x root system 2012-12-18 02:01 obb
drwxr-xr-x root system 2012-12-19 14:27 asec
drwx------ root root 2012-12-18 02:01 secure
d--------- system system 2012-12-18 02:01 sdcard
So sdcar has not permissions?
mount about sdcard says
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
It goes to be mounted rw but for some errors it came to be remounted ro?
I've proved with:
mount -o rw, remount -t vfat /dev/block/vold/179:9 /sdcard , And
mount -o rw, remount -t vfat /dev/block/vold/179:9 /mnt/sdcard
but the answer's always:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
any ideas?
/dev/block/vold/179:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0702,dmask=0702,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
Your sdcard is mounted just fine, no need to try to change anything there. Don't confuse the sdcard with its mount point, different things.
Make sure you've got read access to your test file, and push it to some place you know you are allowed to write. And use the full path /mnt/sdcard/file.name just to be sure.
Also, again, do a "ls - l /mnt/sdcard" to see its really there.
I had the same problem when I didn't root correctly, check if you have root correctly by using a root app. (like root checker or root explorer)
Hello,
I picked up a Meizu MX2 while I was in Hong Kong last week. I've succesfully rooted the device, but now I'm trying to compile CWM for it and need to save a boot.img file.
Unfortunately, I can't seem to find the boot partition at all. Any ideas would be appreciated.
Code:
1|[email protected]:/ # cat /proc/partitions
major minor #blocks name
7 0 34335 loop0
7 1 13545 loop1
7 2 34335 loop2
7 3 9387 loop3
179 0 31162368 mmcblk0
179 1 27951104 mmcblk0p1
179 2 778240 mmcblk0p2
179 3 2097152 mmcblk0p3
179 4 204800 mmcblk0p4
254 0 34335 dm-0
254 1 13545 dm-1
254 2 34335 dm-2
254 3 9387 dm-3
Code:
127|[email protected]:/ # mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/dm-0 /mnt/asec/com.ea.games.nfs13_row-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.touchtype.swiftkey-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.vectorunit.green-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-3 /mnt/asec/com.wordsmobile.musichero-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 929M 32K 929M 4096
/mnt/asec 929M 0K 929M 4096
/mnt/obb 929M 0K 929M 4096
/system 748M 289M 458M 4096
/data 1G 629M 1G 4096
/cache 196M 10M 186M 4096
/mnt/asec/com.ea.games.nfs13_row-1 32M 31M 1M 4096
/mnt/asec/com.touchtype.swiftkey-1 13M 10M 2M 4096
/mnt/asec/com.vectorunit.green-1 32M 31M 1M 4096
/mnt/sdcard 26G 2G 24G 16384
/mnt/secure/asec 26G 2G 24G 16384
/mnt/asec/com.wordsmobile.musichero-1 9M 7M 1M 4096
Code:
[email protected]:/ # ls -la
drwxr-xr-x root root 2013-01-07 18:28 acct
drwxrwx--- system cache 2013-01-07 06:16 cache
dr-x------ root root 2013-01-07 18:28 config
lrwxrwxrwx root root 2013-01-07 18:28 d -> /sys/kernel/debug
drwxrwx--x system system 2012-12-29 08:14 data
-rw-r--r-- root root 125 1970-01-01 07:00 default.prop
drwxr-xr-x root root 2013-01-07 18:28 dev
lrwxrwxrwx root root 2013-01-07 18:28 etc -> /system/etc
-rwxr-x--- root root 105152 1970-01-01 07:00 init
-rwxr-x--- root root 2344 1970-01-01 07:00 init.goldfish.rc
-rwxr-x--- root root 7139 1970-01-01 07:00 init.mx2.rc
-rwxr-x--- root root 2145 1970-01-01 07:00 init.mx2.usb.rc
-rwxr-x--- root root 19772 1970-01-01 07:00 init.rc
-rwxr-x--- root root 1637 1970-01-01 07:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 07:00 init.usb.rc
drwxrwxr-x root system 2013-01-07 18:28 mnt
dr-xr-xr-x root root 1970-01-01 07:00 proc
drwx------ root root 2012-12-19 16:28 root
drwxr-x--- root root 1970-01-01 07:00 sbin
lrwxrwxrwx root root 2013-01-07 18:28 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-07 18:28 sys
drwxr-xr-x root root 2012-12-30 23:01 system
-rw-r--r-- root root 272 1970-01-01 07:00 ueventd.goldfish.rc
-rw-r--r-- root root 1703 1970-01-01 07:00 ueventd.mx2.rc
-rw-r--r-- root root 3879 1970-01-01 07:00 ueventd.rc
lrwxrwxrwx root root 2013-01-07 18:28 vendor -> /system/vendor
Any luck with this?
finding boot image partition
[
QUOTE=bakedjake;36394241]Hello,
I picked up a Meizu MX2 while I was in Hong Kong last week. I've succesfully rooted the device, but now I'm trying to compile CWM for it and need to save a boot.img file.
Unfortunately, I can't seem to find the boot partition at all. Any ideas would be appreciated.
179 1 27951104 mmcblk0p1
179 2 778240 mmcblk0p2
179 3 2097152 mmcblk0p3
179 4 204800 mmcblk0p4
/dev/block/mmcblk0p2 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p4 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
Click to expand...
Click to collapse
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
mccabet said:
[
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
Click to expand...
Click to collapse
download the boot partition app from google play and click on the middle lower button after open then you can click on the partitions to tell you the label number and what it is ass boot or recovery or sbl1
michaelway67 said:
download the boot partition app from google play and click on the middle lower button after open then you can click on the partitions to tell you the label number and what it is ass boot or recovery or sbl1
Click to expand...
Click to collapse
What is the name of the app?
mccabet said:
[
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
Click to expand...
Click to collapse
I agree. This is the correct method. No need for crappy apps from the playstore for such a simple proceedure. And you remain in control.
yes but some rather play it safe and not mess with commands but the app is partition table
here
mccabet said:
[
Based on the information you have provided, you have four visible partitions on the flash. With three used by system, data, and cache, I would expect the remaining partition to be boot ( mmcblk0p1 ). I would do a dump of all partitions as back-ups for a future restore if necessary.
dump the partitions with "cat /dev/block/mmcblk0p1 > /sdcard/mmcblk0p1.img"
substitute the names of the partitions accordingly. I recommend you install an external sdcard larger than the built in and save the images there.
If you do look at the image files with a hex editor, the boot image partition will have the boot command string usually in the beginning of the file.
Good luck
Click to expand...
Click to collapse
This seems a pretty difficult way to go about this.
The easiest way is to use adb:
Code:
adb pull /tmp/recovery.log
If using Windows and you want to pull out to your desktop
Code:
adb pull /tmp/recovery.log C:\Users\Your Name\Desktop
Open the recovery text file using notepad++ (you can use notepad but it's not at all organized) and the first dozen lines or so tell you specifically which each partition is (boot, data, system, cache, etc) relative to it's mmcblk0p_ . This was the only way I could find my boot partition after trying every cat /proc, fdisk, parted, command I could think of. Hope it helps!
Try looking at /proc/mtd , on some devices it usually contains names and descriptions of each MTD device present on the system.
Hi,
I have been on this community for the past 4 days and i wanted to give back. I cant code or do anything significant but i can patch boot.imgs to change ro.security to 0.
Just post your boot.imgs and i can patch it with ro.security = 0 and possibly magisk too.
Hi,
what a great offer!
I can't get it to work, always ending up either in boot loop (https www youtube com/watch?v=oZD2jkkKX_E) or with vbmeta-Error (https androidbiits com/root-samsung-galaxy-xcover-pro-sm-g715fn-europe-easily/), other methods like Kingo ROOT or dr.fone didn't work either (I didn't realy expect that, but I wanted to give it a try)
Here is my boot.img from https www . sammobile . com/samsung/galaxy-xcover-pro/firmware/SM-G715FN/DBT/download/G715FNXXS6ATJ2/503241/ :
http www mediafire com/file/h82hrs3m9zem63r/boot.img.lz4/file
It's a Samsung Galaxy XCover Pro (SM-G715FN) in Germany.
Sadly I can't find a firmware with One UI 2.1 (It's also not redistributed via Update process).
Edit: What a pitty, I can't post links because I have too less posts.
Thanks in advance!
rund3
Hi. Do you have ramdisk in this kernel or is system-as-root?
If ramdisk..so add this your line ro.security=0 at the end of default.prop or prop.default file, next rebuild boot.img again via aik kitchen or superr and flash..
If system-as-root ... you have to copy your init.rc file to sone folder... add this line ro.security=0 to inside init.rc ...maje zip for flash this file via twrp with mounted system_root and will be always added at start...
On mine works with ramdisk and system-as-root.
A lot of ppl made zips for flash system as root so pls google it on xda.
Good luck.
Wysłane z mojego SM-G973F przy użyciu Tapatalka
I think there is a big knowledge gap between what I managed to do with magisk tutorials and what you are expecting I can do.
>> Do you have ramdisk in this kernel or is system-as-root
I don't know. It's Android 10 (phone was initially deliverd with it), Is it always the same there? If not, where can I get this information from?
I don't expect I can access /etc/fstab without root, there this may be stated.
>> If ramdisk..so add this your line ro.security=0 at the end of default.prop or prop.default file
I guess what I would have to do is something like unpack my boot.img in a Linux environment edit files and repack or recompile something?
Never don this. No idea yet. Without a good tutorial I need ages to figure out how and I have only limited time because I need this phone for my work (it's my only working phone from touchscreen age) and can't do endless fectory resets for weeks.
rund3 said:
I think there is a big knowledge gap between what I managed to do with magisk tutorials and what you are expecting I can do.
>> Do you have ramdisk in this kernel or is system-as-root
I don't know. It's Android 10 (phone was initially deliverd with it), Is it always the same there? If not, where can I get this information from?
I don't expect I can access /etc/fstab without root, there this may be stated.
>> If ramdisk..so add this your line ro.security=0 at the end of default.prop or prop.default file
I guess what I would have to do is something like unpack my boot.img in a Linux environment edit files and repack or recompile something?
Never don this. No idea yet. Without a good tutorial I need ages to figure out how and I have only limited time because I need this phone for my work (it's my only working phone from touchscreen age) and can't do endless fectory resets for weeks.
Click to expand...
Click to collapse
So if Android 10 - system-as-root, so no ramdisk in boot.img.
Send me pls init.rc file from root foldel.
Put it here on xda attachment.
I will try make zip file for you.
Do you have root?
Wysłane z mojego SM-G973F przy użyciu Tapatalka
nalas said:
So if Android 10 - system-as-root, so no ramdisk in boot.img.
Send me pls init.rc file from root foldel.
Put it here on xda attachment.
I will try make zip file for you.
Do you have root?
Wysłane z mojego SM-G973F przy użyciu Tapatalka
Click to expand...
Click to collapse
OK, got the file with adb pull:
http www mediafire.com/file/rezljbzyhjvzu5u/init.rc/file
(Don't have/couldn't find a attachment option on this forum, maybe also because I have too less posts?)
I don't have root (yet). Thats what I'm trying to achive.
Hi,
I've added in line 1712 and 1713 security = 0
# Security
setprop ro.security 0
Unzip , Copy this file via adb to the same where You got this and set permissions at 0755 or chmod 0755.
next reboot and test.
View attachment init.rc.zip
nalas said:
Hi,
I've added in line 1712 and 1713 security = 0
# Security
setprop ro.security 0
Unzip , Copy this file via adb to the same where You got this and set permissions at 0755 or chmod 0755.
next reboot and test.
View attachment 5128663
Click to expand...
Click to collapse
Thanks, that at least helps me to understand how it may be possible to set the "props" without having a dedicated file for that.
But I can't simply push the init.rc back to root, because file system is read only:
"adb: error: failed to copy 'D:\Setup\Samsung Galaxy XCover Pro\manual_patched\init.rc' to '/init.rc': couldn't create file: Read-only file system"
I also can't do a remount:
"xcoverpro:/ $ mount -o remount,rw /
mount: '/dev/block/dm-4' not user mountable in fstab"
And I can't do setprop on adb shell:
"xcoverpro:/ $ setprop ro.security 0
setprop: failed to set property 'ro.security' to '0'"
In the meantime I managed to unpack boot.img and compare it with magisk modified version.
Magisk did some changes to binary file "init" in initramfs. Doesn't look like I can deviate additional options for my root from that...
rund3 said:
Thanks, that at least helps me to understand how it may be possible to set the "props" without having a dedicated file for that.
But I can't simply push the init.rc back to root, because file system is read only:
"adb: error: failed to copy 'D:\Setup\Samsung Galaxy XCover Pro\manual_patched\init.rc' to '/init.rc': couldn't create file: Read-only file system"
I also can't do a remount:
"xcoverpro:/ $ mount -o remount,rw /
mount: '/dev/block/dm-4' not user mountable in fstab"
And I can't do setprop on adb shell:
"xcoverpro:/ $ setprop ro.security 0
setprop: failed to set property 'ro.security' to '0'"
In the meantime I managed to unpack boot.img and compare it with magisk modified version.
Magisk did some changes to binary file "init" in initramfs. Doesn't look like I can deviate additional options for my root from that...
Click to expand...
Click to collapse
Why you dont want root the phone?
You can edit build.prop too in system/system/ folder.
Maybe can bd via adb or adb tools? Like all in one tools... you can find on XDA.
In build.prop fike you have to add at the end of file: ro.security=0
Wysłane z mojego SM-G973F przy użyciu Tapatalka
nalas said:
Why you dont want root the phone?
Click to expand...
Click to collapse
You mean, why I want it, right?
Because after my old phone broke, the only way I could backup files was to copy them from twrp.
Now I can't copy data back because I don't have access to data directory, because of missing root.
I've already written a 300 lines Perl script to convert SQLite-DB of old address book to cvf files, but it's the only application, where that kind of workaround can be applied.
But also to get rid of (partly periodically reinstalling) bloatware directly (without ADB).
And of course for next backup (without having to store stuff on google/samsung data centers)
nalas said:
You can edit build.prop too in system/system/ folder.
Click to expand...
Click to collapse
There is a /system/build.prop, but I don't even have read access to it.
Also /system is not a separate partition, so it is also read-only.
/system:
Code:
1|xcoverpro:/system $ ls -l
ls: ./info.extra: Permission denied
total 9640
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 apex
drwxr-xr-x 123 root root 4096 2008-12-31 16:00 app
drwxr-x--x 4 root shell 8192 2008-12-31 16:00 bin
-rw------- 1 root root 3371 2008-12-31 16:00 build.prop
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 cameradata
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 container
drwxr-xr-x 17 root root 4096 2008-12-31 16:00 etc
drwxr-xr-x 2 root root 12288 2008-12-31 16:00 fonts
drwxr-xr-x 5 root root 4096 2008-12-31 16:00 framework
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 hidden
drwxr-xr-x 7 root root 24576 2008-12-31 16:00 lib
drwxr-xr-x 8 root root 28672 2008-12-31 16:00 lib64
-rw-r--r-- 1 root root 280 2008-12-31 16:00 lkm_sec_info
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 media
drwxr-xr-x 189 root root 8192 2008-12-31 16:00 priv-app
lrw-r--r-- 1 root root 8 2008-12-31 16:00 product -> /product
-rw-r--r-- 1 root root 9711940 2008-12-31 16:00 recovery-from-boot.p
drwxr-xr-x 9 root root 4096 2008-12-31 16:00 saiv
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 tee
-rw-r--r-- 1 root root 257 2008-12-31 16:00 tima_measurement_info
drwxr-xr-x 4 root root 4096 2008-12-31 16:00 tts
drwxr-xr-x 7 root root 4096 2008-12-31 16:00 usr
lrw-r--r-- 1 root root 7 2008-12-31 16:00 vendor -> /vendor
drwxr-xr-x 3 root root 4096 2008-12-31 16:00 voicebargeindata
drwxr-xr-x 2 root root 4096 2008-12-31 16:00 vramdiskddata
/proc/mount:
Code:
/dev/block/dm-4 / ext4 ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1812700k,nr_inodes=453175,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /mnt tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=1812700k,nr_inodes=453175,mode=755,gid=1000 0 0
tmpfs /apex tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=1812700k,nr_inodes=453175,mode=755 0 0
/dev/block/platform/13520000.ufs/by-name/metadata /metadata ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/dm-5 /vendor ext4 ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/dm-6 /product ext4 ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/dm-7 /odm ext4 ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/dm-8 /prism ext4 ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/dm-9 /optics ext4 ro,seclabel,relatime,block_validity,discard,delalloc,barrier,user_xattr,acl,i_version 0 0
none /dev/cg2_bpf cgroup2 rw,nosuid,nodev,noexec,relatime 0 0
none /dev/cpuctl cgroup rw,nosuid,nodev,noexec,relatime,cpu 0 0
none /acct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct 0 0
none /dev/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent 0 0
none /dev/memcg cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
none /dev/stune cgroup rw,nosuid,nodev,noexec,relatime,schedtune 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /config configfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /mnt/secure/asec tmpfs rw,seclabel,relatime,size=1812700k,nr_inodes=453175,mode=700 0 0
tmpfs /mnt/sde tmpfs rw,seclabel,relatime,size=1812700k,nr_inodes=453175,mode=700 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime 0 0
pstore /sys/fs/pstore pstore rw,seclabel,nosuid,nodev,noexec,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
tracefs /sys/kernel/debug/tracing tracefs rw,seclabel,relatime 0 0
/dev/block/by-name/omr /omr ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/platform/13520000.ufs/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/platform/13520000.ufs/by-name/efs /mnt/vendor/efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
/dev/block/platform/13520000.ufs/by-name/sec_efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc,i_version 0 0
tmpfs /storage tmpfs rw,seclabel,nosuid,nodev,noexec,relatime,size=1812700k,nr_inodes=453175,mode=755,gid=1000 0 0
/dev/block/platform/13520000.ufs/by-name/userdata /data f2fs rw,lazytime,seclabel,nosuid,nodev,noatime,background_gc=on,discard,no_heap,user_xattr,inline_xattr,acl,inline_data,inline_dentry,extent_cache,mode=adaptive,active_logs=6,reserve_root=9477,reserve_core=1280,resuid=0,resgid=5678,usrquota,grpquota,alloc_mode=reuse,fsync_mode=nobarrier 0 0
/dev/block/loop2 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop2 /apex/com.android.media ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop3 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop3 /apex/com.android.resolv ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop4 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop4 /apex/com.android.tzdata ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop5 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop5 /apex/com.android.media.swcodec ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop6 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop6 /apex/com.android.apex.cts.shim ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop7 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop7 /apex/com.android.conscrypt ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop8 /apex/[email protected] ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
/dev/block/loop8 /apex/com.android.runtime ext4 ro,dirsync,seclabel,nodev,noatime,block_validity,delalloc,barrier,user_xattr,acl,i_version 0 0
none /dev/freezer cgroup rw,relatime,freezer 0 0
/data/knox/secure_fs/enc_media /mnt/shell/enc_emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1000,fsgid=1000,gid=9997,multiuser,derive_gid,default_normal,reserved=20MB 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=20MB 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid,default_normal,reserved=20MB 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid,default_normal,reserved=20MB 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=20MB 0 0
/data/media /mnt/runtime/full/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid,default_normal,reserved=20MB 0 0
nalas said:
Maybe can bd via adb or adb tools? Like all in one tools... you can find on XDA.
Click to expand...
Click to collapse
bd?
All in one tool also doesn't work (at least the "Recovery Flasher and Device Rooter"-Button).
.NET-Error (.NET Framework 4.5 already installed):
Code:
System.ArgumentOutOfRangeException: InvalidArgument=Value mit dem Wert 3 ist für index ungültig.
Parametername: index
bei System.Windows.Forms.ListViewItem.ListViewSubItemCollection.get_Item(Int32 index)
bei TOOL_ALL_IN_ONE.Main.ReadDeviceInfo(Int32 membro)
bei TOOL_ALL_IN_ONE.Main.RecoveryFlasher_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Edit: Button works on a different PC, but only offers to flash TWRP (or other recovery), which is not available for my device and most likely would also cause vbmeta error on boot.
nalas said:
In build.prop fike you have to add at the end of file: ro.security=0
Click to expand...
Click to collapse
OK, thanks, noted if I ever get access to that file.
Oki, try then change build.prop permission via adb commands like chmod 0644, next copy/pull to sdcard, next edit , push back to the phone via adb.
Ofc set debug_adb in rom dev settings..first...
Try install only twrp will be easier...
Wysłane z mojego SM-G973F przy użyciu Tapatalka
dzień dobry ,może mógłby ktoś już patchowany bot wysłać?