[Carlos]

You can modify the partition table file (gpt.bin) and then reflash android with Intel Flash Tool.

 

You can set android_data partition to anything up to 55GB (maximum). By default it’s set to 10GB.

 

I could modify that file for you if you don’t know how.

Attachments:

You must be logged in to view attached files.

[Carlos]

I’ve uploaded on mega the new B2016071401 build from Chuwi. I’ve replaced stock recovery with twrp and modified the new boot.img again to be able to root.

For those in previous builds of Remix OS, you can open the flash-no-erase-all.json file (modified to keep the bootloader unlocked) on Intel Platform Tool and select ‘update’. After that boot to recovery, flash supersu.zip and reboot. No loss of data.

https://mega.nz/#!wAwEGQxA!cX4lvayPJHCqX7ljfe4tTf1shrFOZquTlBTuOUi851cc

ENJOY!

[Carlos]

P.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.

[Carlos]

Richard Russell wrote:

Carlos wrote:

Remix 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.

[Carlos]

Anonymous wrote:

ofcurse someone is interested

Lee wrote:

Yes we are interested post man, post the details

The method was no big mystery.. just modified boot.img and system.img files and flashed them using Intel Flash Tool

I will upload the modified files here when I get back home

[Carlos]

Remix OS 20160530 installed and rooted!

Works better than default android rom

(I will post root method later if anybody interested)

[Author]

Posts