Related
Hello all! I'm sorry for my english.
I am trying to port CWM into my device Huawei Vision U8850, 'recovery mode' compiling from a source code Cyanogen
and i have some errors when starting RecoveryMode
1) E: can't find misc
2) E; Can't mount /cache/recovery/command
3) E: Can't moun( and open) /cache/recovery/log
4) E: Can't mount (and open) /cache/recovery/last_log
My recovery.fstab
Code:
# mount point<->fstype device <-->[device2]
/boot mtd boot
/cache ext3 /dev/block/mmcblk0p11
/data ext3 /dev/block/mmcblk0p8
/misc emmc /data/misc
/recovery mtd recovery /dev/block/mmcblk0p1
/sdcard vfat /dev/block/mmcblk1p1
/system ext3 /dev/block/mmcblk0p7
#/sd-ext ext4 /dev/block/mmcblk0p2
in device "misc" in /data/misc
When i mount "misc ext3 /data/misc" - E: unknown fs type
"misc mtd /data/misc" - E: can't found misc
"misc emmc /data/misc" - Can't open misc
Mounts from device
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,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/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /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:33 /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-0 /mnt/asec/ru.dublgis.dgismobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
My partitions
Code:
major minor #blocks name
7 0 24980 loop0
7 1 27660 loop1
179 0 1867776 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 253952 mmcblk0p7
179 8 1122304 mmcblk0p8
179 9 81920 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 204800 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 32 3929088 mmcblk1
179 33 3924992 mmcblk1p1
254 0 24979 dm-0
Can be corrected in the boot init.rc section, but then what rights the user and group, options set?
Please help me. Thanks...
Cant help you but good luck for you, i have that phone and i really would like cwm
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 http://yadi.sk/d/R4p2T6b30Edt
GriefNorth said:
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 http://yadi.sk/d/R4p2T6b30Edt
Click to expand...
Click to collapse
Anyone confirm this is working?
Anyone confirm this is working?
Click to expand...
Click to collapse
Only russian users from http://4pda.ru/forum/index.php?showtopic=257207&st=2320 and http://4pda.ru/forum/index.php?showtopic=358221&st=280 May be problem if you device sim-lock.
Ok, thanks. Im MAYBE trying this
Sent from my Vision
in this firmware original bootloader. and the possibility of obtaining brick is zero %
GriefNorth said:
in this firmware original bootloader. and the possibility of obtaining brick is zero %
Click to expand...
Click to collapse
really? have you installed it?
Sent from my Vision
yes
so is it for 2.3.5 version or 2.3.7 , cos i have 2.3.5
Sent from my Vision
this is full firmware 2.3.7
GriefNorth said:
this is full firmware 2.3.7
Click to expand...
Click to collapse
and its based china version? because on not chinese
Sent from my Vision
Yes it's china version, after installing change language. China because file system ext4 switch off on my official firmware (russian), but in chaina firmware ext4 switch on in kernel and used. CWM recovery not working with ext3.
GriefNorth said:
Yes it's china version, after installing change language. China because file system ext4 switch off on my official firmware (russian), but in chaina firmware ext4 switch on in kernel and used. CWM recovery not working with ext3.
Click to expand...
Click to collapse
ok, but can i change back to original if i dont like that?
Sent from my Vision
Yes...
GriefNorth said:
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 ...... ...
Click to expand...
Click to collapse
I have many problems with this firmware. Keyboard isn't contained and every keyboard I install won't work - it disappears every time i write one letter.
And the second problem is that CWM is not working for me. It is there, but I can't do anything in it, because back button is not working.
Is there anybody else having the same problem?
i'm sorry, this firmware not have a keyboard, you should install any keyboard from google market. And in recovery going on the last position and press Vol+andVol- (at the same time) then show @Back button menu [email protected]
GriefNorth said:
i'm sorry, this firmware not have a keyboard, you should install any keyboard from google market. And in recovery going on the last position and press Vol+andVol- (at the same time) then show @Back button menu [email protected]
Click to expand...
Click to collapse
Thanks, I'll give it a second try.
try it's all works, without keyboard *sorry* )))
Oh, the "back button" I ment was the one used for confirming an action in recovery, that one is not working for me, when I use it, the selected action will not perform, nothing will happen, so I canť do anything in it, because there's no working button for confirming actions. Do you know what I mean? I'm not that good at english, so I don't know how to express some things
Hope this is the right place to post, I've been lurking around the forums since I got my first smart phone a few years ago but never posted as I've usually found what I'm looking for through googling and rtfm'ing, only reason I came out of the shadows was to get my Kobo Arc 7 rooted. No way I could live without it, I had been watching this thread http://forum.xda-developers.com/showthread.php?t=2507886, checking it every few days to see if there was any development when I saw development was pretty much abandoned on the Arc 7. So this all started with a pm that made me try getting root myself with a little help from dazza9075.
Basically was told to trade in the arc 7 for an arc 7hd, barring that I could try the new cydiaimpactor update and see if it worked. It went something like this. I followed the instructions for the 7hd:
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Click to expand...
Click to collapse
Everything went fine until plugging in the device to let it install a USB composite device. As expected it did fail on the third but when trying to install Google USB drivers it couldn't find any for the device. Just for kicks I opened up Impactor and pressed "Start" it did nothing, I then clicked "USB Scan" and let it complete, then pushed "Start" again. Quick popup on the screen, so I swiped the screen and ran Root Checker Basic and voila I had root.
Since then I've pretty much been badgering dazza9075 through pm to see about getting a recovery for it, I'm an old school linux guy, but never spent much time doing any development, so trying to figure things out myself is usually not an issue but this is new to me. I've been utilizing my google fu to try getting a recovery image made and had some success. Basically started with the instructions for dumping the partition info via dazza's instructions. Turned out to be a little more frustrating than anything, all the commands were turning up nothing, then finally I checked chipset specific stuff, it's running an MTK8125 so after getting nowhere with:
cat /proc/mounts
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
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/secure tmpfs rw,relatime,mode=700 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
tmpfs /storage/emulated tmpfs rw,relatime,mode=705,uid=1023,gid=1023 0 0
/[email protected] /system ext4 ro,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=or
dered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_all
oc,commit=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:97 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
cat /proc/partitions
Code:
[email protected]:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
179 0 7523456 mmcblk0
179 1 1 mmcblk0p1
179 2 10240 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 6144 mmcblk0p4
179 5 786432 mmcblk0p5
179 6 524288 mmcblk0p6
179 7 6145664 mmcblk0p7
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
So trying to find the ls -al /dev/block/platform/dw_mmc/by-name was the first hurdle as there was no "by-name"
Code:
ls -al /dev/block/platform/dw_mmc/by-name
ls -al /dev/block/platform
drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.0
drwxr-xr-x root root 2014-01-29 20:33 mtk-msdc.1
ls -al /dev/block/platform/mtk-msdc.0
drwxr-xr-x root root 2014-01-29 20:33 by-num
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot0 -> /dev/block/mmcblk0boot0
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0boot1 -> /dev/block/mmcblk0boot1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk0p7 -> /dev/block/mmcblk0p7
ls -al /dev/block/platform/mtk-msdc.1
drwxr-xr-x root root 2014-01-29 20:33 by-num
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2014-01-29 20:33 mmcblk1p1 -> /dev/block/mmcblk1p1
but an ls -l revealed:
Code:
[email protected]:/ # ls -l
ls -l
drwxr-xr-x root root 2014-01-31 08:16 acct
-rw-r--r-- root root 16927 1969-12-31 18:00 advanced_meta_init.rc
drwxrwx--- system cache 2014-01-28 19:01 cache
dr-x------ root root 2014-01-31 08:16 config
-rw-r--r-- root root 4 1969-12-31 18:00 custom_build_verno
lrwxrwxrwx root root 2014-01-31 08:16 d -> /sys/kernel/debug
drwxrwx--x system system 2014-01-31 08:17 data
-rw-r--r-- root root 185 1969-12-31 18:00 default.prop
drwxr-xr-x root root 2014-01-31 08:16 dev
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_f -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_s -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 18:00 [email protected]_ro -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 18:00 [email protected] -> /dev/block/mmcblk0p7
So I focused on googling emmc partition tables and stumbled upon this thread http://forum.xda-developers.com/showthread.php?t=2450045 which again I followed with little success. I had already tried way 1 and way 2 and way 3 couldn't read the partition table. So I followed the comments and #3 mentioned "cat /proc/emmc", so:
Code:
[email protected]:/ # cat /proc/emmc
cat /proc/emmc
partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00000002 "ebr1"
emmc_p2: 00006800 00005000 "protect_f"
emmc_p3: 0000b800 00005000 "protect_s"
emmc_p4: 00016c00 00003000 "sec_ro"
emmc_p5: 00020c00 00180000 "android"
emmc_p6: 001a0c00 00100000 "cache"
emmc_p7: 002a0c00 00bb8d00 "usrdata"
Still not giving me a good picture of the partition table so I followed that thread till the end which took me to this thread, http://forum.xda-developers.com/showthread.php?t=1959445. So in fashion I started following that. So
Using fdisk:
Code:
[email protected]:/ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Disk /dev/block/mmcblk0: 7704 MB, 7704018944 bytes
1 heads, 16 sectors/track, 940432 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1665 2944 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2945 4224 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5825 6592 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8385 106688 786432 83 Linux
parted:
Code:
[email protected]:/ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Error: Can't have a partition outside the disk!
gdisk:
Code:
[email protected]:/ # gdisk -l /dev/block/mmcblk0
gdisk -l /dev/block/mmcblk0
GPT fdisk (gdisk) version 0.8.4
EBR signature for logical partition invalid; read 0x0000, but should be 0xAA55
Error reading logical partitions! List may be truncated!
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************
Disk /dev/block/mmcblk0: 15046912 sectors, 7.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): E01B69E6-D822-467F-B1D2-97C0B7BA9ABA
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15046878
Partitions will be aligned on 1024-sector boundaries
Total free space is 13420733 sectors (6.4 GiB)
Number Start (sector) End (sector) Size Code Name
2 26624 47103 10.0 MiB 8300 Linux filesystem
3 47104 67583 10.0 MiB 8300 Linux filesystem
4 93184 105471 6.0 MiB 8300 Linux filesystem
5 134144 1707007 768.0 MiB 8300 Linux filesystem
Still no love. So I read on to the emmc section of that thread and understand nothing, more google fu gets me here: https://github.com/ameer1234567890/OnlineNandroid/wiki/How-To-Gather-Information-About-Partition-Layouts. So now I'm looking at the emmc stuff thinking this really doesn't help me, but remembering I'm running an mtk chip I was pretty happy when I got:
Code:
[email protected]:/ # cat /proc/dumchar_info
cat /proc/dumchar_info
Part_Name Size StartAddr Type MapTo
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pmt 0x0000000000400000 0x0000000000100000 2 /dev/block/mmcblk0
pro_info 0x0000000000300000 0x0000000000500000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000800000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000d00000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001700000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000002100000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000002120000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000002180000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002780000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002d80000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000003380000 2 /dev/block/mmcblk0
resv 0x0000000000080000 0x0000000003400000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003480000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003780000 2 /dev/block/mmcblk0
android 0x0000000030000000 0x0000000004180000 2 /dev/block/mmcblk0p5
cache 0x0000000020000000 0x0000000034180000 2 /dev/block/mmcblk0p6
usrdata 0x00000001771a0000 0x0000000054180000 2 /dev/block/mmcblk0p7
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
Part_Name:Partition name you should open;
Size:size of partition
StartAddr:Start Address of partition;
Type:Type of partition(MTD=1,EMMC=2)
MapTo:actual device you operate
Bingo, so finally, root, partition info, next recovery. Again I'm green here so I searched and searched and searched until finally I found the lenovo has the same chip that someone else had managed to get a recovery installed. So I've spent most of my day with this page, trying to get a recovery installed http://forum.xda-developers.com/newthread.php?do=postthread&f=613. So I managed to get everything done, booted into CWM recovery, finished up all excited, then started testing CWM first reboot and I'm back to the stock android recovery. So I ended up finding the recovery.img that was created through the steps in the above link and did:
Code:
adb shell
mount -o remount,rw /system
mv /system/recovery-from-boot.p /system/recovery-from-boot.p-orig
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-orig
As this was apparently a known problem with some samsung devices. Then:
Code:
fastboot flash recovery "path to recovery"
Which I cut and pasted the path, then rebooted the Arc 7 into fastboot by holding down the Volume up and power slider for aproximately 30 seconds. Fastboot was successful but hung after installing the recovery.img so I hard rebooted and got back into the arc. So I've tested it a few times and now it's booting into CWM recovery, I had two backups made during the image creation process and have been able to restore from both backups, tried creating a backup which completed with an error, can't remember what it is at this point though I will try again later. Only thing I'm noticing is when I boot into recovery it throws the following errors.
Code:
CWM automade 03.02.2014 11:23:02
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last-log
E:Can't open /cache/recovery/last_log
At this point I'm not sure if this is a problem or not as so far everything seems to be working, I will continue testing this recovery out then hopefully post it to dazza9075's original thread. At this point I really don't know what to do from here and any input would be greatly appreciated, dazza has been a great help but I'm at the mercy of being in different countries and timezones, so the pm process is always a little hurry up and wait. Apologies again if this is the wrong place to post, and thanks to all the people in the other posts above for all the hard work they have put in. Hopefully having some of this information in one place will help others with Microtek Chips.
Good work mate!
Have you tried creating a backup yet? and can you post the contents of your FSTAB?
The important one for you is probably to get the SD card mounted, with the internal storage quite low backups will be tricky, so we need to be able to mount an external SD card and use that for the backup.
I wouldn't be to worried about the other partitions that haven't mounted yet, lets concentrate on the important ones, /system /cache /recovery /boot
once we can confirm that you can back then restore we can tidy up the other issues.
Good work mate!
Here is my fstab:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/[email protected] /system ext4 ro,noatime wait
/[email protected] /cache ext4 noatime,nosuid,nodev,noauto_da_alloc wait
/[email protected] /data ext4 noatime,nosuid,nodev,noauto_da_alloc wait,encryptable=footer
It appears that my external sdcard is getting mounted for backups anyways as my backups are all being found in /storage/sdcard1/clockworkmod/backup/. Here is the output from CWM during the backup:
Code:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
SD Card space free: 7225MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No /sdcard/.android_secure found. Skipping backup of applications on external storage.
Backing up cache...
Can't mount /cache!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Checking the new backup folder created only yields boot.img, data.ext4.tar, recovery.img and system.ext4.tar
Pretty much looks like we just need to get the /cache mounting properly then it should go off without a hitch.
Correction, just tried wiping the cache from CWM rebooted to delete the failed backups off the device, booted back into recovery and was greeted by the stock android recovery.
Okay so after getting the stock android recovery after wiping the cache 3 times I decided to start fresh.
Factory reset
Selected english
Forced to update
Rooted with impactor
Installed SU
Installed rom toolbox
fastboot flash recovery "path-to"\recovery.img
power down the volume up powerslider til menu pops up
select fastboot
image flashes and says complete, hold power slider to power down and
rebooted into cwm (volume up and power slider till menu pops up then restore) and this is what I got:
Code:
rua1 autoCWM v5.5.0.4 for arc 7
-reboot system now
-install zip from sdcard
-wipe data/factory reset
-wipe cache partition
-backup and restore
-mounts and storage
-advanced
CWM automade 03.02.2014 11:23:02
SD Card space free: 7852MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Backing up data...
No sd-ext found. Skipping backup of applications on external storage.
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum...
Backup complete!
Rebooted
From rom toobox "Rom Management"
selected custom cwmr
swiped to backups
selected backup I just made and rebooted into cwm from rom toolbox
Code:
CWM automade 03.02.2014 11:23:02
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
#############################
# ROM Toolbox Lite v. 5.9.8 #
# Feb 04, 2014 #
#############################
E:unknown volume for path [/storage/sdcard1/clockworkmod/backup/2014-02-04.17.00.21]
Can't mount backup path
/tmp/recovery.log was copied to /sdcard/clockworkmod/revoery.log. Please open ROM Manager to report the issue.
So for kicks I tried to restore the backup manually from /storage/sdcard1/clockworkmod/backup/*
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore complete!
rebooted kobo, everything seems to be in place. Boot back into recovery to make sure it's cwm not stock android.
Rom Toolbox Lite -> Rebooter -> Reboot Recovery. Bam, back into CWM.
So it is backing up to the external sdcard and can restore from there it just can't do it automagically!?
Regardless aside from not finding ext-sd everything seemed to work.
Have you disabled the auto recovery repair thing? I'm away from my computer at mo but if you kook at the arc recovery rom process there is a file you need too delete, that stops custom recovery getting replaced at boot
Sent from my GT-I8750 using XDA Windows Phone 7 App
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard.
I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
howlinwolf430 said:
I renamed those files as I had read they were causing similar issues on Samsung devices. Now they are renamed and moved to another folder. I'm flashing http://forum.xda-developers.com/showthread.php?t=1916098 right now. it backed up okay, but couldn't find the file. The zip was saved to /sdcard/downloads but its reading my sdcard which is /storage/sdcard1 as /sdcard.
I did a wipe to flash that and when it couldn't find it it rebooted to factory. I'm back in CWM doing a system restore from the backup it just made. So it is working, just seems to be issues with paths. I am able to flash manually once in CWM though.
Click to expand...
Click to collapse
your Fstab is very odd looking, it does look exactly like what you find within android but the recovery ones I have been using are a little different
here is mind
Code:
/system ext4 /dev/block/mmcblk0p3
/sdcard datamedia /dev/block/mmcblk0p8 /dev/block/platform/mmcblk0
/cache ext4 /dev/block/mmcblk0p4
/data ext4 /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p1
/boot emmc /dev/block/mmcblk0p2
/misc emmc /dev/block/mmcblk0p5
/staging emmc /dev/block/mmcblk0p6
/metadata emmc /dev/block/mmcblk0p7
That is for the 10HD, /SDcard in this case is an internal chip, there is no external chip, I have to have it set at "data media" but on the original Arc I have it set to "vfat". For the 10HD I cant manually mount /SDCARD, but it does do it itself when backing up and restoring but on the Arc it works fine, I can manually mount and unmount. Im a little unsure why its not working on the 10HD, a chap was going to have a look for me but hasn't yet got back to me.
format is
/mount_point Mount_type /location
below is the fstab of Astrali, his been a good help with mine
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p16
/cache ext4 /dev/block/mmcblk0p18
/data ext4 /dev/block/mmcblk0p21 length=-16384
/recovery emmc /dev/block/mmcblk0p13
/misc emmc /dev/block/mmcblk0p11
[B]/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B]
/system ext4 /dev/block/mmcblk0p17
/sys_boot vfat /dev/block/mmcblk0p3
/FOTA emmc /dev/block/mmcblk0p19
[B]/sdcard1 vfat /dev/block/mmcblk0p20[/B]
[B]/sd-ext auto /dev/block/mmcblk1p2[/B]
#added sd-ext support by Astrali
[B]/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1[/B]
#added for rom manager support
Here we can see /external_SD and /sdcard are actually the same thing (?) mounted from blk1p1 (likely an external Sdcard) I don't know why there is two mounts, perhaps different software looking for the same thing but in different places?
/SDcard1 is mounted from blk0p20 so probably internal storage,
/sd-ext however is mounted from blk1p2, likely a second partition on an external card
/boot mtd boot
/cache yaffs2 cache
/data yaffs2 userdata
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/system yaffs2 system
/sd-ext ext4 /dev/block/mmcblk0p2
keep this in mind, im just building a recovery img just now based on this...
Can you please upload kobo arc 7 stock rom or system.img
Firstly, mods, please! Move me to a different forum if this thread is in the wrong place, I'm not used to posting on xda (usely searching is sufficient.)
Updates: Method to restore your ME170C* from a brick! See below for the guide.
I just picked up a ME170CX at a local Meijers in the Thanksgiving sale. It has pretty decent hardware and the default UI is pretty nice, overall. However, the previous tablet I used (and still do) was the Acer Iconia A500, which has the good luck of a custom bootloader, a 4.4.4 OmniRom port as well as a bunch of other stuff, and an extremely recent CWM. Long story short, I'm spoiled on .bat scripts and a convenient APX flashing utility by NVidia.
Since I'm essentially blazing the trail, I'd really like a few ideas to get started. Again, my plan is to compile CWM, make a flashable root package, and to (eventually) put together a custom ROM. So far, this is the info I've collected to that end:
Running Android 4.4.2
build # KVT49L.WW_MeMO_Pad-11.2.3.21-20141111 release-keys
Kernel version: 3.10.20 [email protected] #1
Intel USB drivers confirmed to work for both ADB/fastboot.
Includes DROIDBOOT (ie: fastboot)
MMC partition layout
Partition Info
/proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 48128 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 21504 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 21504 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 428032 mmcblk0p8
179 9 1187840 mmcblk0p9
259 0 13633519 mmcblk0p10
179 40 4096 mmcblk0rpmb
179 30 8192 mmcblk0gp0
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 3872256 mmcblk1
179 51 3870720 mmcblk1p1
"$ mount" results
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=700,uid=1023,gid=1023 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/intel/by-label/system /system ext4 ro,seclabel,noatime,data=
ordered 0 0
/dev/block/platform/intel/by-label/factory /factory ext4 ro,seclabel,noatime 0 0
/dev/block/platform/intel/by-label/cache /cache ext4 rw,seclabel,nosuid,nodev,no
atime,data=ordered 0 0
/dev/block/platform/intel/by-label/config /config ext4 rw,seclabel,nosuid,nodev,
noatime,data=ordered 0 0
/dev/block/platform/intel/by-label/firmware /firmware ext4 ro,seclabel,noatime,d
ata=ordered 0 0
/dev/block/platform/intel/by-label/data /data ext4 rw,seclabel,nosuid,nodev,noat
ime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/intel/by-label/gauge /gauge ext4 rw,seclabel,nosuid,nodev,no
atime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p7 /ADF ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
none /pstore pstore rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:51 /mnt/media_rw/MicroSD vfat rw,dirsync,nosuid,nodev,noexec
,relatime,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:51 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/MicroSD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/platform/intel/by-label contents
lrwxrwxrwx root root 2014-11-28 17:29 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 cache -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 config -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 data -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-28 17:29 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 firmware -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 gauge -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 system -> /dev/block/mmcblk0p9
/dev/block/platform/intel/by-guid contents
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000000 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000001 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000002 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000003 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000004 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000005 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000006 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000007 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000008 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000009 -> /dev/block/mmcblk0p10
Parted info for partitions
Model: MMC 016GE2 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 49.3MB 49.3MB reserved boot
2 49.3MB 57.7MB 8389kB panic boot
3 57.7MB 59.8MB 2097kB ext2 factory
4 59.8MB 81.8MB 22.0MB ext4 config
5 81.8MB 82.9MB 1049kB ext2 gauge
6 82.9MB 105MB 22.0MB ext4 firmware
7 105MB 138MB 33.6MB ext4 ADF
8 138MB 577MB 438MB ext4 cache
9 577MB 1793MB 1216MB ext4 system
10 1793MB 15.8GB 14.0GB ext4 data
Instructions
Recover from a failed root attempt -
Follow this excellent guide by sevensvr who was kind enough to do what I was too busy at the time to do. Thanks, bro!
Thread
Progress Report:
Very bad news! Atom processors are actually running the x86 architecture (32bit for PC users.) Although I should have guessed this, the Intel support page did not indicate the arch and I ended up checking on Wikipedia. As soon as a saw that the processor was a x86, my hopes of a generic BOOT.IMG were dashed. Sure enough, after pulling off images of all the partitions of the device I found that the two flagged boot are neither a .tar file of any recognizable type, nor a partition type I'm familar with. After mounting the system directory I can't find anything useful. As far as I can tell the device doesn't have a standard issue bootloader/recovery setup but somehow has the two interlocked. Either that or the recovery is in the panic partition and I just can't identify it as such. The recovery-from-boot.p file still exists, so that's a little comfort.
As a side note, fastboot has a custom file format for use with the .img flash system and has kindly neglected to post any documentation that I can find on the format. Without that the raw imgs I have of partitions are essentially worthless.
Does this mean the project is going to fail? No, I just have to begin warming myself up to arguing with ASUS over releasing source, something I don't relish. If anyone has some familarity to dealing with manufacturers' over source, I'd love to talk to you!
Basically, after my updates, what I need to begin is a few good ideas of where to go next with these:
Root - Completed
Method to deduce the partitions' actual uses or names - Aborted for the present, focusing on getting ASUS source
A link or explanation of how exactly FASTBOOT installs images so that the system image file can flashed properly.
Device tree for the ME170C or ME170CX.
Expert guidance.
Downloads:
Windows Intel Drivers
linux fastboot binary for asus devices - Thanks to the person who first compiled this with ASUS compatibility!
raw system.img with SU (NOT fastboot compatible!)
Thankee very much, sorry for my ignorance on some things. Hey, everyone has to learn!
Update: Root found and partition progress has been made!
Thanks so much! Worked perfectly!! Glad i have root. Ill be following this thread. A custom rom would be nice:good:
Thanks
Thanks for all your work.
I'm posting to let you know I'm following the progress. My skills are too basics to be useful but know that your work is appreciated.
A beer on me.
Cheers
Thanks for the support, everyone! I'll keep pushing.
Updates: Architecture turns out to be x86, no conventional BOOT.IMG seems to be surfacing. Trying to get ahold of the ASUS support for the source tree.
m27frogy said:
Thanks for the support, everyone! I'll keep pushing.
Updates: Architecture turns out to be x86, no conventional BOOT.IMG seems to be surfacing. Trying to get ahold of the ASUS support for the source tree.
Click to expand...
Click to collapse
I wish i was more help all i can really do is offer support and test easy things lol
P.s. I also picked this up on thanksgiving day sale. At hhgregg
Thanks for starting the thread...
Already bricked one, but I have another. Tell me, would resetting after five seconds had elapsed (as opposed to exactly five seconds) after applying the root exploit corrupt this process?
Still willing to root the second one... for science.
Thanks!
Genius4Hire said:
Already bricked one, but I have another. Tell me, would resetting after five seconds had elapsed (as opposed to exactly five seconds) after applying the root exploit corrupt this process?
Still willing to root the second one... for science.
Thanks!
Click to expand...
Click to collapse
I'm about positive that the app tells you to wait 10 seconds not 5. For the bricked one I added a guide which should hopefully revive it.
Bricked memopad...
m27frogy said:
I'm about positive that the app tells you to wait 10 seconds not 5. For the bricked one I added a guide which should hopefully revive it.
Click to expand...
Click to collapse
That could be true! If that is the case I am probably closer, as I waited a few extra seconds. I got distracted for a few seconds and proceeded to reboot. Just let me know when/if I should try on the other device, I can't wait to root this thing.
My eventual goal is to run multiple various Linux live images from th SD card.
Thanks for the response.
Update: More bad news. My tablet's battery for no reason at all failed and won't recharge. There will be some delay on further progress while I RMA it. Sorry, guys! :crying:
m27frogy said:
Update: More bad news. My tablet's battery for no reason at all failed and won't recharge. There will be some delay on further progress while I RMA it. Sorry, guys! :crying:
Click to expand...
Click to collapse
Let us know how the rma process goes. Ive heared mixed reviews with asus
root asus memo pad7 me170cx
I bought it Christmas eve went to the asus website got the latest we update mental installed it had 4.4.2 . then went and got zenphone 1.4.6 from asus followed instructions received root 10 in.total. is I need can recovery any body gay ideas
m27frogy said:
Firstly, mods, please! Move me to a different forum if this thread is in the wrong place, I'm not used to posting on xda (usely searching is sufficient.)
Updates: Root found and partitions have been ironed out more thoroughly, although I still need help figuring out what partition is the recovery.
Root method is in the apk below, follow it's instructions very carefully, I will not be responsible if you brick your device! Thanks, RootZenfone!
Updates: Lots of new discoveries, some of which are great and others are rather depressing, check the bottom of the page for new downloads!
I just picked up a ME170CX at a local Meijers in the Thanksgiving sale. It has pretty decent hardware and the default UI is pretty nice, overall. However, the previous tablet I used (and still do) was the Acer Iconia A500, which has the good luck of a custom bootloader, a 4.4.4 OmniRom port as well as a bunch of other stuff, and an extremely recent CWM. Long story short, I'm spoiled on .bat scripts and a convenient APX flashing utility by NVidia.
Since I'm essentially blazing the trail, I'd really like a few ideas to get started. Again, my plan is to compile CWM, make a flashable root package, and to (eventually) put together a custom ROM. So far, this is the info I've collected to that end:
Running Android 4.4.2
build # KVT49L.WW_MeMO_Pad-11.2.3.21-20141111 release-keys
Kernel version: 3.10.20 [email protected] #1
Intel USB drivers confirmed to work for both ADB/fastboot.
Includes DROIDBOOT (ie: fastboot)
MMC partition layout
Partition Info
/proc/partitions
major minor #blocks name
179 0 15392768 mmcblk0
179 1 48128 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 21504 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 21504 mmcblk0p6
179 7 32768 mmcblk0p7
179 8 428032 mmcblk0p8
179 9 1187840 mmcblk0p9
259 0 13633519 mmcblk0p10
179 40 4096 mmcblk0rpmb
179 30 8192 mmcblk0gp0
179 20 4096 mmcblk0boot1
179 10 4096 mmcblk0boot0
179 50 3872256 mmcblk1
179 51 3870720 mmcblk1p1
"$ mount" results
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/media_rw tmpfs rw,seclabel,relatime,mode=700,uid=1023,gid=1023 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /Removable tmpfs rw,seclabel,relatime,mode=751,gid=1028 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/intel/by-label/system /system ext4 ro,seclabel,noatime,data=
ordered 0 0
/dev/block/platform/intel/by-label/factory /factory ext4 ro,seclabel,noatime 0 0
/dev/block/platform/intel/by-label/cache /cache ext4 rw,seclabel,nosuid,nodev,no
atime,data=ordered 0 0
/dev/block/platform/intel/by-label/config /config ext4 rw,seclabel,nosuid,nodev,
noatime,data=ordered 0 0
/dev/block/platform/intel/by-label/firmware /firmware ext4 ro,seclabel,noatime,d
ata=ordered 0 0
/dev/block/platform/intel/by-label/data /data ext4 rw,seclabel,nosuid,nodev,noat
ime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/intel/by-label/gauge /gauge ext4 rw,seclabel,nosuid,nodev,no
atime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/mmcblk0p7 /ADF ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime,mode=755 0 0
none /pstore pstore rw,relatime 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_i
d=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:51 /mnt/media_rw/MicroSD vfat rw,dirsync,nosuid,nodev,noexec
,relatime,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,
iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:51 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1023,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocha
rset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/MicroSD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1
023,default_permissions,allow_other 0 0
/dev/block/platform/intel/by-label contents
lrwxrwxrwx root root 2014-11-28 17:29 ADF -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 cache -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 config -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 data -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-28 17:29 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 firmware -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 gauge -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 system -> /dev/block/mmcblk0p9
/dev/block/platform/intel/by-guid contents
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000000 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000001 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000002 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000003 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000004 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000005 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000006 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000007 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000008 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-28 17:29 80868086-8086-8086-8086-000000000009 -> /dev/block/mmcblk0p10
Parted info for partitions
Model: MMC 016GE2 (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 49.3MB 49.3MB reserved boot
2 49.3MB 57.7MB 8389kB panic boot
3 57.7MB 59.8MB 2097kB ext2 factory
4 59.8MB 81.8MB 22.0MB ext4 config
5 81.8MB 82.9MB 1049kB ext2 gauge
6 82.9MB 105MB 22.0MB ext4 firmware
7 105MB 138MB 33.6MB ext4 ADF
8 138MB 577MB 438MB ext4 cache
9 577MB 1793MB 1216MB ext4 system
10 1793MB 15.8GB 14.0GB ext4 data
Instructions
Recover from a failed root attempt -
First, you're going to need to install the Intel drivers at the bottom of the page.
Next, follow the instructions to setup fastboot in this guide. (Make sure you setup your PATH right)
Next, you're going to need a copy of the system partition, which you can find at the bottom of the page.
Once you have the system.img downloaded, turn on your tablet while holding both volume buttons down and the power key. Release the power key after three seconds and wait for it to boot.
Once you're in recovery mode plug the tablet into your computer with the handy MicroUSB cable.
Open up a command prompt and navigate to the directory you downloaded the file to. (Google for some guides on the command line)
Run the command fastboot devices. Three things could happen: 1. "fastboot is not a recognized command", you didn't install fastboot properly. 2. Nothing happens in which case the Intel drivers aren't working or your device isn't connected properly. 3. A bunch of random numbers, a space, and then a smaller name.
If the previous command worked out to #3, run fastboot flash system system.img. If it appears to be doing something, let it sit and don't disturb it. If it just says something about system.img not existing, you didn't go to the right directory.
If the command prompt comes back and tells you it worked then unplug your tablet. (If it didn't work, send me a PM with info.)
Next, use the volume keys to highlight "Wipe Your Device" and use the power key to select it. Select Yes and wait. Then shut off your tablet and reboot.
Hopefully, everything worked and you have a working tablet!:fingers-crossed:
Progress Report:
Very bad news! Atom processors are actually running the x86 architecture (32bit for PC users.) Although I should have guessed this, the Intel support page did not indicate the arch and I ended up checking on Wikipedia. As soon as a saw that the processor was a x86, my hopes of a generic BOOT.IMG were dashed. Sure enough, after pulling off images of all the partitions of the device I found that the two flagged boot are neither a .tar file of any recognizable type, nor a partition type I'm familar with. After mounting the system directory I can't find anything useful. As far as I can tell the device doesn't have a standard issue bootloader/recovery setup but somehow has the two interlocked. Either that or the recovery is in the panic partition and I just can't identify it as such. The recovery-from-boot.p file still exists, so that's a little comfort.
Does this mean the project is going to fail? No, I just have to begin warming myself up to arguing with ASUS over releasing source, something I don't relish. If anyone has some familarity to dealing with manufacturers' over source, I'd love to talk to you!
Basically, after my updates, what I need to begin is a few good ideas of where to go next with these:
Root - Completed
Method to deduce the partitions' actual uses or names - Aborted for the present, focusing on getting ASUS source
A way to get an image of the device that I could flash from fastboot if something were to go wrong - Should work, can't think why it wouldn't
Device tree for the ME170C or ME170CX.
Expert guidance.
Downloads:
Windows Intel Drivers
linux fastboot binary for asus devices - Thanks to the person who first compiled this with ASUS compatibility!
system.img with SU
Thankee very much, sorry for my ignorance on some things. Hey, everyone has to learn!
Click to expand...
Click to collapse
Don't know the if there is any differences between the ME170C and ME170CX.
the ME170C src, and the firmware are available at Asus support site.
pda12 said:
Don't know the if there is any differences between the ME170C and ME170CX.
the ME170C src, and the firmware are available at Asus support site.
Click to expand...
Click to collapse
only difference i can see is the amount of memory they have. Every thing else is the same looking at the specs.
it seems that we *might* have been given a way to unlock the bootloader?
So I was looking into the Asus firmware/rom update
what in the ifwi.zip (in the update package) appear most interesting
it seems that we *might* have been given a way to unlock the bootloader
Code:
fastboot flash dnx dnx_fwr_*
in the similar way as with the Dell Venue, especially that of the ZenFone
pda12 said:
So I was looking into the Asus firmware/rom update
what in the ifwi.zip (in the update package) appear most interesting
it seems that we *might* have been given a way to unlock the bootloader
Code:
fastboot flash dnx dnx_fwr_*
in the similar way as with the Dell Venue, especially that of the ZenFone
Click to expand...
Click to collapse
That's good news! That would be awesome to see lollipop and custom kernels on this thing. Just gotta get together with some smarter people than I
well this is my new project, downloading the kernel source and newest firmware now.... still no cwm or twrp / no way to flash it if we did right?
daavvis said:
well this is my new project, downloading the kernel source and newest firmware now.... still no cwm or twrp / no way to flash it if we did right?
Click to expand...
Click to collapse
As far as I know you are correct. No way to flash. Only root as far as I know. Far from a dev but glad to hear its being worked on, thank you!
Sent from my Nexus 6
Just to clarify, this is the way things are panning out:
1. It's unknown exactly how the ME170CX boots into flashboot. It could either be bundled with the boot.img or somehow a part of the panic partition.
2. I was unaware that .img files required a specific format in fastboot (I just assumed that when a "*nix" system makes an .img file it's an .img file not a .customformattedpartitionwithanunneccessarydescriptorimg) It'll be a while as I try to figure out how to take the raw image of the system partition and turn it into something that fastboot will accept.
3. Projects in RL are making it rather difficult to keep up with things so updates won't come quickly.
4. If someone is able to make a breakthrough with the boot system or with the fastboot img, I will be glad to add their post to the OP.
Thanks, hang in there guys! We'll get there eventually. :crying:
A hopeful bump. :thumbup:
Sent from my Nexus 6
Good news. Root is on the way. I have found an exploit (namely the dirty cow exploit to gain root access), only problem is my root lasts for 1 command and I am trying to work out a way to transfer over the su binary itself. I will update this post once I have more info.
ALSO, AND THIS IS IMPORTANT. IF YOU WANT ROOT, DO NOT UPDATE TO ZV6 WHEN IT DROPS. ZV6 WILL LIKELY PATCH THIS EXPLOIT.
Reserved
Following!
Noticed on another forum, ZV6 has appeared.
I cannot remember if you are given a choice whether to install these or not...turned off wifi/data just in case, lol.
It will download the update, but it won't install without your permission. As an update on root. I have a root shell, but I cannot do anything thanks to SELinux. I need to find an exploit to get around SELinux.
Code:
λ adb -d shell
[email protected]:/ $ run-as exec whoami
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
root
[email protected]:/ $ run-as exec dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
dd: /dev/block/bootdevice/by-name/boot: Permission denied
I knew about ZV6 because I saw the kernel sourrces when I went to download the ZV5 source
if this helps........
EagerestWolf said:
Reserved
Click to expand...
Click to collapse
https://mega.nz/#!6BMlmIZB!CBKqxLvGl3c2EfYXj6_hIbdUKxPtbfWzgoglQb0d5aA
thats the ZV5 update for the LGLS775ABB that popped up on my LGLS775ABB ZVZ4!
454.4mb.zip, unzips to 1.02gb..............
If you can get any way to recovery from a predicament out of it, please share!
zach
---------- Post added at 11:16 PM ---------- Previous post was at 11:10 PM ----------
EagerestWolf said:
It will download the update, but it won't install without your permission. As an update on root. I have a root shell, but I cannot do anything thanks to SELinux. I need to find an exploit to get around SELinux.
Code:
λ adb -d shell
[email protected]:/ $ run-as exec whoami
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
root
[email protected]:/ $ run-as exec dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/boot.img
Warning: setcon transition to 'u:r:init:s0' failed (is SELinux Enforcing?)
dd: /dev/block/bootdevice/by-name/boot: Permission denied
Click to expand...
Click to collapse
Definitely no dev here, but using a selenix mode changer app, in 5.1.1, linking su binaries from su/bin to system/xbin allowed it to set selenix to permissice on the Samsung Galaxy J3 (2016) SM-J320P until we got a permissive kernel. That phone has one messed up os hyrbid odex & deodex mix..............
zach...........
---------- Post added at 11:21 PM ---------- Previous post was at 11:16 PM ----------
EagerestWolf said:
I knew about ZV6 because I saw the kernel sourrces when I went to download the ZV5 source
Click to expand...
Click to collapse
If your kdz's available you can't be talking about the BOOST Mobile Stylo 2........... only one LG's not coughing up software for........ oh well, damn, thought I had found something going somewhere for this device..............
Yes that link above is for BOOST LG Stylo 2! The update was waiting right out of the box, it was already on ZV4 so factory reset hooked it up immediately and run a log cat until it acquired the update again. Then spent about 20 minutes going through all the https links until finding the one the update was coming from and downloaded to the Windows machine.
zach
If you go to LG's Open Source Website. They have all the kernel sources there. ZV6 is listed so it's coming. As for your update package, I looked and I wasn't sure if I saw a recovery image, but I did see a LAF image, which is also helpful.
As for bypassing SELinux, I have a few leads on that one. Once we have root, we will have recovery and ROM's, but we need root first to fix fastboot.
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
!!!!!!!
EagerestWolf said:
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
Click to expand...
Click to collapse
Coolbeans!!! Its signed, can't remember the name but do remember seeing the signature verification. I used winrar so nothing should be messed up with it as well.
Any help, anything, just let me know! I cannot understand why another excellent phone for this price is drifting str8 past any development. Went to Asus after I first got into modding and my HTC burnt..... left them due to their never unlocking bootloaders, etc.... Samsung next, the J3, one messed up piece of os there but we modded the hell out of it, now LG............ every variant of this device has the kdz available if I'm not mistaken. If temp root had to be forced onto this phone, to dd it it would just about be worth the $119 it cost me!
zach
TWRP
EagerestWolf said:
I am actually going to try injecting a modified kernel into your update an flashing it. Since this is an official FOTA. It may work.
Click to expand...
Click to collapse
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
That won't work, we need root, and before we can do anything related to TWRP, we need fastboot, so this is all in vain.
Sent from my LGLS775 using Tapatalk
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
I can provide a stock boot.img I have for LS775 ZV5 build, but cat /proc/cmline is useless right now. I do get some output with cat /proc/partitions and cat /proc/mounts
Code:
major minor #blocks name
253 0 485204 zram0
179 0 15388672 mmcblk0
179 1 512 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 1536 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 512 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 512 mmcblk0p14
179 15 1536 mmcblk0p15
179 16 1536 mmcblk0p16
179 17 24576 mmcblk0p17
179 18 24576 mmcblk0p18
179 19 24576 mmcblk0p19
179 20 24576 mmcblk0p20
179 21 1536 mmcblk0p21
179 22 512 mmcblk0p22
179 23 512 mmcblk0p23
179 24 512 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 512 mmcblk0p27
179 28 512 mmcblk0p28
179 29 8192 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 10240 mmcblk0p31
259 0 8192 mmcblk0p32
259 1 8192 mmcblk0p33
259 2 65536 mmcblk0p34
259 3 1024 mmcblk0p35
259 4 2560 mmcblk0p36
259 5 2048 mmcblk0p37
259 6 6144 mmcblk0p38
259 7 40960 mmcblk0p39
259 8 3207168 mmcblk0p40
259 9 921600 mmcblk0p41
259 10 10915840 mmcblk0p42
259 11 8175 mmcblk0p43
179 32 4096 mmcblk0rpmb
Code:
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
/dev/pstore /dev/pstore pstore rw,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/bootdevice/by-name/system /system ext4 ro,seclabel,noatime,data=ordered 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/bootdevice/by-name/carrier /carrier ext4 rw,seclabel,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
EagerestWolf said:
That won't work, we need root, and before we can do anything related to TWRP, we need fastboot, so this is all in vain.
Sent from my LGLS775 using Tapatalk
Click to expand...
Click to collapse
Have you been able to achieve some progress? If you need to try I have some time and one of these phone to try. I really need root on this version.
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
You can get your cmdline from unpacked boot
Sent from my SM-J320P using Tapatalk
coolbeans2016 said:
terminal:
cat /proc/cmdline
trying to get kernel cmd line
& arguments
also stock boot.img
but keep getting perm denied
Can you get any of this so TWRP can be ported?
The person who did TWRP for the Stylo 2 + says he can port TWRP for Stylo 2 LGLS775ABB (my device) if whats listed above can be provided.
Any ideas?
Click to expand...
Click to collapse
rick.wardenburg said:
You can get your cmdline from unpacked boot
Sent from my SM-J320P using Tapatalk
Click to expand...
Click to collapse
This is cmdline from unpacked boot image.
Code:
cmdline = console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=ph1 user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 vmalloc=600m
Any progress on this or is it a another dead end for us?
Sent from my LGLS775 using Tapatalk
can someone pm me when you do obtain root permanently
....will keep checking...also i can make a stock dimp of my zv4 if ne one needs it since lg likes to keep everything tight....does anyone know how to enter download mode??
Doctur said:
can someone pm me when you do obtain root permanently
....will keep checking...also i can make a stock dimp of my zv4 if ne one needs it since lg likes to keep everything tight....does anyone know how to enter download mode??
Click to expand...
Click to collapse
And if someone tells you, please tell me. : )
I was going to root my friends Android, however after further discovery --- thus far--- it looks like this device has not been rooted yet.
Is anyone able to create a partion.xml for use with tool studio eMMC download tool. Im trying to figure it out myself and having a little trouble but I believe it should allow us to flash the v3 firmware.
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ć?