Rooting a dual boot tablet with no cwm !!

Hi guys hope someone can help, i found a guide on dual booting my tablet its a linx 7
32 gb win 8.1 , I've spent the past two days reading and flashing having all sorts of problems lol but at least now ive managed to get it into a workable state.

At the minute its only booting android 4.4.4 as i deleted the windows.old folder and will probably have to do a full reinstall.

The problem with rooting android it seems is due to the usb otg part of the tablet and the ported version of the android version comes from the cube i7. The usb debugging is disabled due to the tablet only being designed for usbotg but there seems to be other versions of the android with root available from the manufacturer but due to using google translate and dead links im having no joy.

I found this using translate and google cache

You try to disguise iWork7 to Nexus7

Famous place in Arigasu such Pazudora is is, the domestic application There are many apps that limit such as carrier restrictions and ROOT limit is provided. Do not be able to start these apps from iWork7 it is currently being adjusted.


1. Look at the source
[GitHub]


2. Check item
the following values ​​of the defualt.prop is NG
ro.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb



Replaced iodide
ro.secure = 1
ro.allow.mock.location = 0
ro.debuggable = 0
persist.sys.usb.config = mtp


When the following exists NG (compatible with root switching of SuperSu)
· /system/app/Superuser.apk
· / System / bin / su
· / System / xbin / su
· / Sbin / su


You want to Nexus7 beetle the build.prop
Tablet classic [Nexus Factory Image
· Au of IntelAtom machine [ASUS MemoPad 8]


ro.build.id = KTU84P
# Ro.build.display.id = U67GT_v1.0__20150117
ro.build.display.id = KTU84P
# Ro.build.version.incremental = user.jim.20150117.113528
ro.build.version.incremental = 1227136
ro.build.version.sdk = 19
ro.build.version.codename = REL
ro.build.version.release = 4.4.4
# Ro.build.date = Sat Jan 17 11:37:11 CST 2015
ro.build.date = Fri Jun 13 07:23:23 UTC 2014
# Ro.build.date.utc = 1421465831
ro.build.date.utc = 1402644203
ro.build.type = user
# Ro.build.user = jim
ro.build.user = android-build
# Ro.build.host = build-168
ro.build.host = vpbs2.mtv.corp.google.com
# Ro.build.tags = dev-keys
ro.build.tags = release-keys
# Ro.product.model = U67GT
ro.product.model = Nexus 7
# Ro.product.brand = intel
ro.product.brand = google
# Ro.product.name = CUBE
ro.product.name = razor
# Ro.product.device = U67GT
ro.product.device = flo
# Ro.product.board = baylake
ro.product.board = flo
ro.product.cpu.abi = x86
ro.product.cpu.abi2 = armeabi-v7a
# Ro.product.manufacturer = intel
ro.product.manufacturer = asus
ro.product.locale.language = ja
persist.sys.language = ja
persist.sys.country = JP
ro.product.locale.region = JP
persist.sys.timezone = Asia / Tokyo
ro.wifi.channels =
ro.board.platform = baytrail
# Ro.build.product is obsolete; use ro.product.device
# Ro.build.product = CUBE
ro.build.product = flo
# Do not try to parse ro.build.description or .fingerprint
# Ro.build.description = em_i8270_64-user 4.4.4 KTU84P user.jim.20150117.113528 dev-keys
ro.build.description = razor-user 4.4.4 KTU84P 1227136 release-keys
# Ro.build.fingerprint = intel / em_i8270_64 / em_i8270: 4.4.4 / KTU84P / user.jim.20150117.113528: user / dev-keys
ro.build.fingerprint = google / razor / flo: 4.4.4 / KTU84P / 1227136: user / release-keys
ro.build.characteristics = nosdcard, tablet

*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
Dynamically edit the Defualt.prop on Android

It seems possible to edit the defualt.prop under Android-root environment when you use the setpropex, quite amazing tool ,,,. (On reboot)


----------------------------------------

su -c "setpropex ro.secure 1"

---------------------------------------

(Ro.allow.mock.location = also the same format 1 and ro.debuggable = 1)
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 without deleting the Windows area, to rewrite the image of Android !!

The standard recovery procedures, it is the initialization of the inescapable Windows, but it became a rewritable only favorite area of ​​Android by step on this procedure. (Mr. SpecialThanks dia-sea)

Download the required files
· XDA bootimg_tools_7.8.13.zip [HP] [Download]


As basic knowledge, organize the recovery boot order
1. BIOS -> Lanch EFI Shell file filesystem device
2. Shell.efi (Shellx64.efi can not move because it does not correspond to 64bitEFI)
3. startup.nsh -> efilinux.efi -f droidboot.img
4. installer.cmd
※ seemed to make re-partition is performed when you run the droidboot.img, require modification of droidboot.img.



modification of droidboot.img
Information display
# ./boot_info Droidboot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x80000000
RAMDISK ADDRESS: 0x81000000
CMDLINE: 'loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor g_android.fastboot = 1 droidboot.minbatt = 0 droidboot.use_installer = 1 droidboot.installer_usb = / dev / block / sda1 droidboot.installer_file = installer. cmd '


dismantling of droidboot.img
# Split_boot droidboot.img


Editing of partition table
# Cp /droidboot/ramdisk/system/etc/partition.tbl /droidboot/ramdisk/system/etc/partition.tbl.bk
# Vi /droidboot/ramdisk/system/etc/partition.tbl


We want to only two lines
partition_table = gpt
reload / dev / block / mmcblk0


repack of ramdisk
# .././repack_ramdisk Ramdisk /


Creating droidboot.img
# .././mkbootimg --kernel Droidboot.img-kernel --ramdisk new-ramdisk.cpio.gz --cmdline "loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor g_android.fastboot = 0 droidboot.minbatt = 0 droidboot.use_installer = 1 droidboot.installer_usb = / dev / block / sda1 droidboot.installer_file = installer.cmd "--base 0x80000000 --pagesize 2048 --ramdiskaddr 0x81000000 --output droidboot_not_clear.img



Creating a Boot USB
Prepare a USB memory that was formatted with FAT32, to copy the contents of AnTaku folder of the USB memory to the root.
You have created so far, system_rootja.img the system.img, boot_adbon.img the boot.img, and rename and droidboot_not_clear.img the droidboot.img,, with the same copy of the USB memory to the root.
and it rewrites the partition.tbl the same content as the droidboot.img you just created.
partition_table = gpt
reload / dev / block / mmcblk0


editing of startup.nsh, change to start the droidboot_not_clear.img.
efilinux.efi -f droidboot_not_clear.img


modification of installer.cmd
And comment out the partition fix part
factory, cache, system, config, logs, the data is initialized,
Fixed boot.img, recovery.img, droidboot.img, the writing of system.img appropriate.
Below, mount the / system in rw, boot_adbon.img the adb effectiveness of boot.img
root of, example of Japanese, as system_rootja.img unwanted apps deleted system.img, it has saved to a USB memory.
oem start_partitioning
REM oem partition /installer/partition.tbl
erase: factory
erase: cache
erase: system
erase: config
erase: logs
erase: data
oem stop_partitioning
REM oem wipe ESP
REM flash: ESP # / installer / esp.img
REM flash: boot # / installer / boot.img
flash: boot # / installer / boot_adbon.img
flash: recovery # / installer / recovery.img
flash: fastboot # / installer / droidboot.img
REM flash: system # / installer / system.img
flash: system # / installer / system_rootja.img
continue



Now, without initialization of Android image the Widnows became the all-you-can-****. Hail and Hail.
Incidentally is the recovery manual wrote by making full use of the translation site. [DL]

*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 Rooted !! full version!

We were successful in perfect Root acquired in iWork7. Correct the previous steps and re-published as a full version. (Mr. SpecialThanks dia-sea)



1. Download the necessary environment and file
Windows7 and (even 8.1) in a virtual environment we will proceed in the Linux (VMPalyer & Ubuntu14.10).
· Ubuntu14.10 Japanese 64bit [HP] [Download]
· VMWare Player [HP] [Download]
· IWork7 factory image [HP] [Download]
· Ext4_utils_cygwin_fixed [HP] [Download]
· SuperSu 2.46 [HP] [Download]
· Busybox [HP] [Download]
· Sgs2toext4 [HP] [Download] for people who system.ext4.img does not make well. (JAVA)
· USB memory space is available formatted with NTFS of about 8GB
· USB memory space is available formatted with FAT32 of more than 2GB
· USB keyboard, OTGHUB

2. Building a home directory
Once you start the ubuntu, to make a [iwork7] directory to the home directory,
and rename ext4_utils_cygwin_fixed.zip, system.img, copy the busybox, the directory name to unzip the UPDATE-SuperSU-v2.46.zip [updatesu].
After this it will be operation in the linux console.
In order to comfortable operation with the administrative authority, operation and after you to live do not put sudo passwords many times is easy.

$ Sudo $ {SHELL}
[Sudo] password for username:
Or, it will switch to the root user with su.
$ Sudo su -



3. Mount of system.img
System.img of factory image because it is a file that was cut wasteful part (0?) At the simg format, you will need to convert it to the format of the raw image ext4.

It wants to install the zlib1g-dev necessary to ext4_utils of make.
# Apt-get install zlib1g-dev

ext4_utils of thawing
# Unzip ext4_utils_cygwin_fixed.zip

make of ext4_utils
# Cd ext4_utils
# Make

to copy to make to the finished file to iwork7 directory.
The ones where you unzipped the SuperSu to updatesu directory, to just below iwork7 your own build.prop.

Examples of Japanese correspondence build.prop
ro.product.locale.language = ja
ro.product.locale.region = JP
persist.sys.language = ja
persist.sys.country = JP
persist.sys.timezone = Asia / Tokyo

Creating system.ext4.img
# Simg2img system.img system.ext4.img
System.img remove because it is unnecessary at this point

iWorkt-Root02.png
copy of busybox
# Cp busybox-x86_64 sys / xbin / busybox
# Chown root: root sys / xbin / busybox
# Chmod 0755 sys / xbin / busybox

4. Mount of system.img
# Umount msys

# Rm -f system.img
# Rm -rf msys
# Rm -rf sys

# Mkdir msys
# Mkdir sys

# Mount -o loop system.ext4.img msys

# Cp -a msys /. Sys

# Umount msys



5. root setting
Clear root
# Rm -rf sys / bin / .ext
# Rm -rf sys / etc / init.d
# Rm -f sys / bin / su
# Rm -f sys / xbin / su
# Rm -f sys / xbin / daemonsu
# Rm -f sys / bin / .ext / .su
# Rm -f sys / etc / install-recovery.sh
# Rm -f sys / etc / init.d / 99SuperSUDaemon
# Rm -f sys / etc / .installed_su_daemon
# Rm -f sys / app / Superuser.apk
# Rm -f sys / app / Superuser.odex
# Rm -f sys / app / SuperUser.apk
# Rm -f sys / app / SuperUser.odex
# Rm -f sys / app / superuser.apk
# Rm -f sys / app / superuser.odex
# Rm -f sys / app / Supersu.apk
# Rm -f sys / app / Supersu.odex
# Rm -f sys / app / SuperSU.apk
# Rm -f sys / app / SuperSU.odex
# Rm -f sys / app / supersu.apk
# Rm -f sys / app / supersu.odex


root acquisition start
# Mkdir sys / bin / .ext
# Cp updatesu / x86 / su sys / xbin / daemonsu
# Cp updatesu / x86 / su sys / xbin / su
# Cp updatesu / x86 / su sys / bin / .ext / .su
# Cp updatesu / common / Superuser.apk sys / app / Superuser.apk
# Cp updatesu / common / install-recovery.sh sys / etc / install-recovery.sh
# Mkdir sys / etc / init.d /
# Cp updatesu / common / 99SuperSUDaemon sys / etc / init.d / 99SuperSUDaemon
# Echo 1> sys / etc / .installed_su_daemon

# Chown root: root sys / bin / .ext
# Chown root: root sys / bin / .ext / .su
# Chown root: root sys / xbin / su
# Chown root: root sys / xbin / daemonsu
# Chown root: root sys / etc / install-recovery.sh
# Chown root: root sys / etc / init.d / 99SuperSUDaemon
# Chown root: root sys / etc / .installed_su_daemon
# Chown root: root sys / app / Superuser.apk

# Chmod 0777 sys / bin / .ext
# Chmod 06755 sys / bin / .ext / .su
# Chmod 06755 sys / xbin / su
# Chmod 0755 sys / xbin / daemonsu
# Chmod 0755 sys / etc / install-recovery.sh
# Chmod 0755 sys / etc / init.d / 99SuperSUDaemon
# Chmod 0644 sys / etc / .installed_su_daemon
# Chmod 0644 sys / app / Superuser.apk


Unnecessary apps (Chinese market, etc.) Delete
# Rm -f sys / preinstall / 91hiapk_AndroidPhone_1008443.apk
# Rm -f sys / preinstall / AnZhi_KuBiMoFangFuFei_V5.4_20141002.apk
# Rm -f sys / preinstall / BaiduNaviHD_d4033_20140523.apk
# Rm -f sys / preinstall / baidusearch_Android_1_3_0_7_1009249a.apk
# Rm -f sys / preinstall / cn.keyshare.course_ku_bi.apk
# Rm -f sys / preinstall / CUBE_UgameStore_V210_20141128.apk
# Rm -f sys / preinstall / Mediaplayer.apk
# Rm -f sys / preinstall / ninegameclienthd_v2.2.0_android_release.apk
# Rm -f sys / preinstall / Tudou_Android_phone_4.2_yingyue1.apk
# Rm -f sys / preinstall / wandoujia_kubimofang_oem_fa.apk


One line below if unnecessary copy your own bulid.prop may not run
# Cp build.prop sys / build.prop


Root, installation of busybox
# Mv sys / system
# Rm / system / bin / cp
# Rm / system / bin / mv
# / System / xbin / su --install
# / System / xbin / busybox --install -s / system / bin
# Mv / system sys




6. writing of system.img
When you root reduction, to create the following command implantation system.img. (Note the space)
# ./mkuserimg.sh -s Sys system.img ext4 system 896M
Copy the file to Windows, it will overwrite the system.img to where you copied the Android system to a USB memory that was formatted with FAT32.



6. Rooted !!
To complete the installation of the Android system open the BIOS menu from the ESC key to turn on the power. All after the completion of Android has become the Root state.
iWork7-BootBIOS.png



Finally, Do not you forget the installation of Windows.
Windows will cause is initialized in the above procedure.
In the next section we will learn the steps to rewrite only Android, leaving the Windows.
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 adb daemon configuration of (tcp)

It is iWork7 ~ is the first place impossible to connect with adb in USB debugging on, but can be connected by TCP.
If editing the /ramdsik/default.prop I may, but does not use the ramdisk.img, it uses the ramdisk in the boot.img. (Mr. SpecialThanks dia-sea)



1. File downloading
· XDA bootimg_tools_7.8.13.zip [HP] [Download]


2. It will copy the necessary files
Unzip the bootimg_tools_7.8.13.zip, is located in the following
Home directory / iwork7 / bootimg_tools
Copy the boot.img to bootimg_tools.


3. information display of boot.img
# Cd boot
# Boot_info boot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x80000000
RAMDISK ADDRESS: 0x81000000
CMDLINE: 'loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor '


4. dismantling of boot.img
# Split_boot boot.img


5. adb setting
# Cd boot / ramdisk
# Vi default.prop

persist.nomodem_ui = 1
ro.arch = x86
ro.com.google.clientidbase = android-google
ro.secure = 0
ro.adb.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb


Creating 6.boot.img
# Cd boot
# .././repack_ramdisk Ramdisk /
# .././mkbootimg --kernel Boot.img-kernel --ramdisk new-ramdisk.cpio.gz --cmdline "loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor "--base 0x80000000 --pagesize 2048 --ramdiskaddr 0x81000000 --output boot.img
# Mv boot.img ../.



iwork7 to the connected with tcp / ip after adb Enable
on the command prompt of windows
# Adb connect "iwork7 of ip address"
# Adb shell
# Su - (Since root permission prompt SuperSU exits click allowed on the tablet!)
# Ps

# Root @ U67GT: / # ps

*
| 2015-04-28 |
Mobile
*| Comments: 0



And im not sure if this helps or not.

Am i able to add root to the rom myself ?
Just to add the usb-debugging is not enabled from the way the rom is designed, when you click the build/ model number to enable it then dev options it only offers the option to revoke the rights .

Show Accepted Answer

Guest Quick Reply (No URL, BBcode or HTML)

Last post by rprohaska
4 hours ago
Last post by ykulas
1 hour ago
Last post by tod.breitenberg
4 hours ago
Texting App
Started by ostroman
Last post by tiara94
1 hour ago
Last post by elnora63
54 minutes ago
Last post by audreanne88
4 hours ago
Last post by jovany.schroeder
2 hours ago
Last post by kshlerin.tito
1 hour ago
Last post by kayleigh.lubowitz
36 minutes ago
Last post by ernest43
2 hours ago
Last post by annabell20
1 hour ago