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
Related
For some reason my sd-card partition can't be mounted anymore by cwm after I followed this guide http://forum.xda-developers.com/showthread.php?t=1601942 to stop cwm boot loop into recovery.
My CM10 doesn't boot anymore after I flashed latest version (2012-08-06) and I'm trying to manually adb shell into the tf201 to try and mount the partition myself.
What's the block device for sdcard?
I have:
Code:
# ls /dev/block
loop0 loop4 mmcblk0 mmcblk0p3 mmcblk0p7 sda
loop1 loop5 mmcblk0p1 mmcblk0p4 mmcblk0p8 sda1
loop2 loop6 mmcblk0p10 mmcblk0p5 mmcblk0p9
loop3 loop7 mmcblk0p2 mmcblk0p6 platform
and the following is mounted:
Code:
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p1 on /system type ext4 (rw,nodev,noatime,nodiratime,user_xattr,acl,barrier=1,data=ordered)
fstab
Code:
# cat /etc/fstab
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p1 /system ext4 rw
and trying to mount mmcblk0p8:
Code:
# mount /dev/block/mmcblk0p8 /data
mount: mounting /dev/block/mmcblk0p8 on /data failed: Invalid argument
help?
Ok, RaYmAn on the irc channel helped me out! I cleared my mmcblk0p8 partition with fastboot:
Code:
fastboot -i 0xb05 erase userdata
And voila! Now I can use /data to copy my roms to and use CWM to flash them.
Thanks all! Peace!
can u please elaborate more on this? how to fastboot and stuff? i cannot flash other roms after i flashed recovery v5.5.0.4 because in recovery my sd card is not seen
dimushor said:
can u please elaborate more on this? how to fastboot and stuff? i cannot flash other roms after i flashed recovery v5.5.0.4 because in recovery my sd card is not seen
Click to expand...
Click to collapse
Go into the dev thread, look at the twrp thread there, it explains how to use fastboot. If I were you I would seriously consider installing twrp, isn't that an old version of cwm your using?
http://forum.xda-developers.com/showthread.php?t=1615990 TWRP external sd card support
http://forum.xda-developers.com/showthread.php?t=1533697 CWM 5.8.2.0
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.
Update:
I've successfully compiled CWM Recovery for my device. If anyone is inquiring on how PM and I will create a post for it. Because of the lack of support getting to that point I will hold on to it for now.
Now that I've compiled this I really dont know what do next.
---------------------
So I've spent a majority of the day looking at this device (hipstreet flare HS-9DTB4-8GB).
What I'd like to do is compile my own ClockworkMod for this device.
I've spend most of the day working on discovering where everything is and backing up everything using ADB.
Information From Device
Current Rom: Softwinerf900_V1.1.7_20121225r587_27d8028 (Found in Current Chinese Recovery, Option 2, Displayed in Center)
Model-Number: HS-9DTB4
Android version: 4.0.4
Baseband version: 1.4rc3
Kernel version: 3.0.8+ (Tue Dec 25 18:20:41 CST 2012)
Build number: 20130118 F900
Memory: 353MB (Supposed to be 512 and is but I've read there is issues with kernel support.)
Processor: ARMv7 Proccessor rev 2 (v71) 1200MHz
Partition Layout and Confirmed Partitions
cat /proc/partitions
major minor #blocks name
Code:
93 0 16384 nanda bootloader
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd system
93 32 1048576 nande data
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 16384 nandj
93 80 5799936 nandk sdcard (Mounted by vold as /mnt/sdcard and /mnt/secure/asec)
Partition Layout from what I can see follows Allwinner as described in second table on this site:
http://linux-sunxi.org/Android/partitions
Code:
[email protected]:/ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 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
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:80 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,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/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I've backed up nanda, nandb, nandc, nandd, nandg just incase with ADB.
(If anyone would like them I have no issue with sharing. Only thing I've done so far is added ROOT and fixed Keyboard issue, which both can be reversed.)
Like I said, what I'd like to do is Compile CWM for this device. I'm currently setting up Ubuntu as a dual boot so I can do this.
My question is what exactly do I need to do to do this. I understand there are many guides on the steps envolved to do this but if someone could provide the links that are rather structured. Also I'd be interested in working on taking this to the next step to work on making a rom for this.
Update: Stage One
I'm currently following mithun46 guide to build my enviroment (installing linux) I'm installing on a tower that I was using to grow my dust farm...
Now when I get to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
What should I actually be using so I can build CWM Recovery?
CWM for Hipstreet
I have the same tablet as you Hispstreet Flare 9" ics 4.0 ...... I would love to be able to flash the CWM recovery to my device and thus be able to install custom rom ...could you please help me out
Thanks its would be much appreciated
Did anyone get anywhere with this? Would love a simple way to root and install custom rom on this. Launchers just don't give me quite the flexibility that I want and it's very laggy when I get too many apps open but hardware specs should allow this to run better. I'm not a dev and knowledge is limited but I can follow steps in order and send feedback if that would help, as long as it's not going to brick it LOL - Hubby would kill me but I am just itching to do more with it.
Lost On Off Switch Function
I was cleaning up some old installs and somehow deleted the file that controls the on off switch. You would not know which file that would be would you? (And where I might find it?)
Regards,
tsb
stock roms
tsbrownie said:
I was cleaning up some old installs and somehow deleted the file that controls the on off switch. You would not know which file that would be would you? (And where I might find it?)
Regards,
tsb
Click to expand...
Click to collapse
Does anyone know where to find stock roms for the hip street devices? Would be greatly appreciated! thanks
Help with stock rom
cr3at1ve said:
Does anyone know where to find stock roms for the hip street devices? Would be greatly appreciated! thanks
Click to expand...
Click to collapse
I have been looking for a stock rom as well as my issue is that it will not boot past the hipstreet flare 2 logo, i'm really not sure what to do now I have tried to contact customer support with no avail.
Any help would be great!!
Thanks in advance
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.