TechTablets › Forums › Chuwi Forums › Chuwi Hi12 Forum › Installing Remix OS on the Chuwi Hi12 (While keeping Windows)
- This topic has 114 replies, 36 voices, and was last updated 9 years, 4 months ago by
Bill Christiansen.
-
AuthorPosts
-
July 31, 2016 at 2:38 am #45155
I’m trying to extract system.img using RMXtools v1.7, but I get an error “Can’t open as archive.” Trying manually with 7zip I get the same results. Is anyone else running into this issue? The same file flashed onto my tablet just fine, so I can’t imagine it’s corrupted.
It’s an ext4 file system. You can extract in Windows using: EXT4 imagefile unpacker https://sourceforge.net/projects/androidicsjbext/?source=typ_redirect
but you would need other tools to repack. I think it’s easier to do in linux.
July 31, 2016 at 6:27 am #45163root is rly needed, cant live without adaway 🙂 hopefully @Carlos will have time for up his file and make some quick tut soon 🙂
July 31, 2016 at 6:51 pm #45214One minor issue since I re-installed Remix: when I’m listening to music on Play and I switch off the screen, the CPU goes into a low mode that can’t handle playback so the audio breaks up. If I plug in the charger it’s fine but so far I haven’t found a way of playing audio with screen off and not charging. Even setting WiFi to always on didn’t help.
It’s wierd, tried again this morning and can’t reproduce it. Play is playing normally with screen off and no power, maybe needed a reset for some of the changes. I feel silly now.
August 2, 2016 at 7:09 am #45316Tried rooting it… so I unpacked system.img in Ext4 linux, moved the system folder to NTFS, rooted with RMX tools 1.7, moved system folder back to Ext4 in linux, repacked as system.img with yaffs2, and then tried flashing it in Intel PFT and it failed =/
any ideas?
August 2, 2016 at 9:42 am #45324I think there’s some incompatibility with latest version of RMXtools as the older 1.5 can extract the system.img.
https://mega.nz/#!ClgFRZZa!2hKWWLpgDRQrDo_4RjSBJyvPvoH9MfSnEYgSTgaVUS0
I will wait for someone with a bit more experience before I try reflashing anything
August 2, 2016 at 7:05 pm #45356I think there’s some incompatibility with latest version of RMXtools as the older 1.5 can extract the system.img. https://mega.nz/#!ClgFRZZa!2hKWWLpgDRQrDo_4RjSBJyvPvoH9MfSnEYgSTgaVUS0 I will wait for someone with a bit more experience before I try reflashing anything
got it unpacked and rooted again, but 1.5 will not repack. Considering that I had this step completed when I unpacked in linux, I doubt re-packing with yaffs2 in linux would yield different results, so I guess I’ll wait patiently as well
August 3, 2016 at 7:00 am #45418Remix OS 20160530 installed and rooted! Works better than default android rom (I will post root method later if anybody interested)
@Paternick (Carlos) I’ve been experimenting a lot with this, and I’m dying to know how you were able to get a verified boot enabled (user) build of android to accept a modified system file at startup by simply flashing it in Intel Phone Flash Tool.From my crash course in android over the past few days, i don’t think this is happening unless a userdebug version of the ROM gets released. The reason why we were able to root the last version of Android is because Chuwi released it as a userdebug version out of the box, so we were able to disable verity (verified boot) through fastboot. using a simple adb command adb disable-verity
Plus, even if KingRoot or some other soft root method worked, it would just chmod back to a read only file system the next time the tablet booted…
I really hope I’m wrong and that Carlos comes back with a working system.img to prove it, but from where I’m standing and with my limited experience, I think our best chance of getting root is to urge Chuwi to release a userdebug build build of Remix OS like they did with the Android build the Dual Boot shipped with.August 3, 2016 at 11:11 am #45432If you flash boot.img from stock android, you can disable-verity
August 3, 2016 at 11:14 am #45433From my crash course in android over the past few days, i don’t think this is happening unless a userdebug version of the ROM gets released. The reason why we were able to root the last version of Android is because Chuwi released it as a userdebug version out of the box, so we were able to disable verity (verified boot) through fastboot. using a simple adb command adb disable-verity
If you flash boot.img from stock android, you can disable-verity (sorry for doublepost)
August 3, 2016 at 9:15 pm #45507Anonymous
Inactive- Posts: 49
someone from chuwi forum found root method http://forum.chuwi.com/thread-2022-1-1.html
August 3, 2016 at 9:44 pm #45509someone from chuwi forum found root method http://forum.chuwi.com/thread-2022-1-1.html
)))) “found”. read my post and take tutorial from here
August 3, 2016 at 9:56 pm #45511Well the steps are plain copy pasted from my tutorial on rooting stock Android… Looks kinda fishy, but there’s a boot.img in the provided archive, the rest is the HiBook Toolbox.
August 3, 2016 at 11:54 pm #45529Remix OS 20160530 installed and rooted! Works better than default android rom (I will post root method later if anybody interested)
@paternick (Carlos) I’ve been experimenting a lot with this, and I’m dying to know how you were able to get a verified boot enabled (user) build of android to accept a modified system file at startup by simply flashing it in Intel Phone Flash Tool. From my crash course in android over the past few days, i don’t think this is happening unless a userdebug version of the ROM gets released. The reason why we were able to root the last version of Android is because Chuwi released it as a userdebug version out of the box, so we were able to disable verity (verified boot) through fastboot. using a simple adb command adb disable-verity Plus, even if KingRoot or some other soft root method worked, it would just chmod back to a read only file system the next time the tablet booted… I really hope I’m wrong and that Carlos comes back with a working system.img to prove it, but from where I’m standing and with my limited experience, I think our best chance of getting root is to urge Chuwi to release a userdebug build build of Remix OS like they did with the Android build the Dual Boot shipped with.
Yes, you are right. But unpacking boot.img and editing the default.prop file that protection can be removed.
Sorry, I’m on vacation and don’t have good internet access here. I’ll try to upload the modified boot.img.
[Edit:uploaded on mega] https://mega.nz/#!RUJznLxC!rl623H5slopBW8XOye9U789lGlqBtYYD98gUpaalzu0
It’s the original remix boot.img modified to be prerooted. No need to disable verity. Just unlock the bootloader, flash this boot.img and install SuperSU using the hibook recovery posted on this thread.
Optionally, you can replace the original boot file in the remix folder and then edit in the file flash-no-erase.json the lines with “OEM verified” to “OEM unlock” to do the above steps with the Intel flash tool.
Sorry again for the delay. I wanted to pack everything and make an user friendly script but didn’t find the time to do it. I’ll upload it if I find the time.
August 4, 2016 at 12:05 am #45531P.s. For those stuck with a blank screen at boot after flashing SuperSU, there’s no need to reflash remix again…just flash this boot.img and reboot. No more blank screens.
August 4, 2016 at 12:17 am #45534It’s nice we have a working root, thanks to all who contributed!
I must say I’m really enjoying this Remix ROM.
-
AuthorPosts
- You must be logged in to reply to this topic.

