[Nick]

Carlos – what was the process you used to modify the boot.img? Something like this: http://whiteboard.ping.se/Android/Rooting? I am trying to root another tab (TBook 10) that doesn’t have root so might give this a try.

Thanks!

[Nick]

Nicolas Giraud wrote:

On the latest image posted by Chuwi team (http://forum.chuwi.com/thread-1973-1-1.html), build images-factory-chuwi_hi12_d-2.0-5.1.1-B2016053001-signed.zip, wifi works for me, it did not work on the previous build.

Same for me. I managed to download it directly from the yunpan link and it worked with this build – looks like if you have any wifi issues this is the build to use

[Nick]

Bill Christiansen wrote:

Nick wrote:

Got it installed with root…but no Wifi from the Chuwi build that was posted. Has anyone had any issues with wifi on the Chuwi release? Everything else is working fine (sound, touchscreen)

Wi-Fi should be fine, it’s working on mine

Hmm ok. Strange, mine either doesn’t let me switch on Wifi or with a reboot lets me activate the switch but has the jumping … and never actually shows any available networks. Still running fine in Windows though so maybe a different wifi module that the driver isn’t there for?

[Nick]

Got it installed with root…but no Wifi from the Chuwi build that was posted. Has anyone had any issues with wifi on the Chuwi release? Everything else is working fine (sound, touchscreen)

[Nick]

I think it could be a battery calibration issue. I was using mine yesterday evening and it was running down fairly steadily until it 21% where it remained for a while. Picked it up this morning and it was still at 21% but running ok. Will keep an eye on it and see how it pans out.

[Nick]

aab444 wrote:

Hi, I got the following error : adb server is out of date. killing… ADB server didn’t ACK * failed to start daemon * error: unknown host service Any hints please.

• intel driver installed
• USB Debugging enabled

I’m using windows 10 64bit

Make sure you don’t have any other flash tools running in the background, I got the same error when I had the Intel Platform flash tool open

[Nick]

Hi Pete,

 

I have one. Build is great and it looks fantastic with the small bezels. Both Windows and Android performance is decent – I haven’t run any benchmarks but they are both fluid. My only complaint is the terrible Android battery life, I was losing something like 40% in an hour of use and 60% overnight with screen off. Windows battery life is far better so I can only assume a software update should sort that issue.

If you are a Windows user mainly I wouldn’t hesitate to recommend it. If you use Android then I would wait for a fix or look at a different tab – the battery is just that bad. The Hibook may be worth a look?

[Nick]

HellMatt wrote:

Same for me, battery drains too fast, I lost 40% in 1 hour, it’s really bad

Thanks for responding. Windows seems a lot better which is a relief since that suggests a software issue rather than faulty hardware. Hopefully we will get an Android update or Custom ROM in future.

Interested to see how others are doing with battery on the tablet (which I’ve found great apart from the battery problem!)

 

 

[Nick]

Just to confirm the SuperSU updated binaries break this. Don’t try to update through the app or manually just yet. I tried the latest binaries from XDA but they cause the issue with getting stuck on the Android logo. Hopefully we can get a fix soon, but for now we can just try to ignore the notification!

[Nick]

Good news! This works. I was undeterred by bricking my Windows only Hi12 and gave the script a go. It didn’t work straight away – there were a couple of steps that I had to run manually (the final busybox installation step) but it works and I have a fully rooted Hi12.

High level steps:

1. Download and install intel driver
2. Download and extract the install_my_root.zip (I put it in root of C: just to make it easier)
3. Enable USB Debugging on the tablet and plug into PC via usb
4. Open Command Prompt – I run as Admin just to be sure
5. Simply run the 1_ROOT_my_Chuwi_Hi12_FIRST_TIME.bat file
6. Hopefully you should have root – as I mentioned I had to do some fiddling with the script to get it to root and was unable to boot once (restore via the thread in the forum if this happens)

[Nick]

Konstantin Matvievsky wrote:

Hibook-ToolBox by kostyamat <span style=”color: #ff0000;”>Attention! Whatever you do, you do it at your own risk!</span> For first – to write my english is bad, bad, very bad… But I understand english <noscript></noscript> I allowed myself to write a few batch files to help newcomers, as well as other users, under common title “Hibook-Toolbox”. Русскоязычная версия: http://4pda.ru/forum/index.php?s=&showtopic=741766&view=findpost&p=49156807
<p style=”text-align: center;”>It allows you to: Unlock the new tablet Bootloader. Unprotect system partition from changing (remove “Verity Boot”). Install TWRP-recovery ver-2.8.7.0, which I have ported to this tablet. Get the correct ROOT in the right way. Flash custom firmware (which do not have to wait long, I think so) And other…. I will add if still need to be. Download (needrom.com): http://www.needrom.com/download/unlocktwrproot/ Preparation: Unzip the archive to PC, but try not to use special characters or folder names with space in the paths to files. Better way is unzip to a folder in the root of drive C: or D: Turn on ADB-debugging: “Settings” – “About Tablet” -> Taps under the item “build number” until the caption appears “you became a developer” -> Return one step back -> enter the item for developers ” -> Enable” USB debugging “. Connect the device to the PC. Install the Intel driver IntelAndroidDrvSetup1.10.0.exe</p>

• Usage: 1.Unlock_Bootloader.bat – <span style=”color: red;”>Run first. </span>It will unlock the bootloader. Carefully follow the prescriptions of the script and on the screen of the tablet. <span style=”color: red;”>ATTENTION! All settings, programs, as well as all data on internal SDCard will be destroyed!</span> <span style=”color: seagreen;”>Data on external MicroSD and Windows will not suffer</span>. After unlocking the device will reboot in factory recovery, which does not display anything (stupidly black screen with backlight), the process may take up to 10 minutes (I’m shocked, but it’s true), then the device will reboot in Android pristine clean. 2.Unlock_Verity-boot.bat – <span style=”color: red;”>Run second.</span> It will unlocking the System partition to can be changed. Carefully follow the prescriptions of the script and on the screen of the tablet. The device will reboot. <span style=”color: seagreen;”>Data on external MicroSD and Windows will not suffer. </span> After all unlock actions, be sure to enter the option for developers and turn ON the item “Factory unlock”. 3.Outside_boot-TWRP-recovery.bat – (It is optional. For obtain ROOT access). The device will be rebooted into the temporary session of TWRP-recovery, to Internal sdcard will be placed UPDATE-SuperSU.zip – install it using TWRP. Previously, you can make TWRP backup (recommended!). 4.Flash-TWRP-recovery.bat – (It is optional) TWRP-recovery will be permanently flashed into the Tablet. (Not recommended! Some time firmware will update, TWRP cannot install OTA-update) 5.Flash-ORIGINAL-recovery.bat – (It is optional) Flash back to the original Recovery. ADB_shell.bat – Just a comfortable CMD-window for ADB-debugging and work with Android Shell. Flash-Custom_FW.bat – My flasher to flash custom firmware, which I am sure will appear in future.

<p style=”text-align: center;”>Useful console commands (ADB_shell.bat): ADB reboot bootloader – reboot to FastbootDroidboot (flashing) mode ADB reboot recovery – reboot to TWRP or native Recovery mode. ADB root – restart ADB-debug service as ROOT. ADB remount – remounting Android system partition to write (you need root-adb mode see adb root) ADB shell – run Android-console (ash) through which you can run Linux-scripts, internal system commands, etc. fastboot boot * *.img – run user-compiled boot.img or recovery.img fastboot reboot – reboot to system from DroidbootFastboot (flashing) mode. fastboot flash [boot, recovery, system, data] [boot, recovery, system, data]. img – In DroidbootFastboot mode, It will flash specific image to specific partition, example: fastboot flash system c:\Custom_FW\system.img – will flash only system.img to Android system partition. <span style=”color: red;”>PS. Under any circumstances, when using TWRP, never do not wipe system partition! Also make sure the TWRP-settings option “Use rm-R instead of formatting” is ON and never leave it. The fact of the matter is that “Verity Boot” marked System partition itself. Withing format the label disappears – the tablet won’t boot to Android! This problem can be solved, but why You would make a problem?</span> <span style=”color: seagreen;”>If You like may work, buy me a coffee. </span>

</p>
<p style=”text-align: left;”>Looks good – would this work on a Chuwi Hi12 doyou know? I’ve been trying to figure out how to get root.</p>
<p style=”text-align: left;”>Thanks</p>

[Nick]

I would definitely buy again – I did in fact after bricking my first Hi12 trying the Dual OS BIOS I now have my second Hi12. As other comments have said it is a bit of a lottery but I think if you get a working unit, nothing even comes close for the price. Have to add that the Android build on the Dual bot model is great, minima bloat and smooth. There were a few Chinese apps but they could all be uninstalled easily

[Nick]

winston smith wrote:

You need the original system image. The point is to modify the filesystem on an linux machine before repack it and flash it in the tablet with fastboot. That’s the only way to do since there is not custom recovery for intel tablet. Does Chuwi published the firmwire ?

Do you have a guide to do this? The recently posted OS files from Chuwi has the full Android OS included with the boot.img and system.img files – keen to give it a try if you can point in the right direction

[Nick]

spzjulien supercowz wrote:

wait before try, flash fail on mine, trying with hardware flasher and test the dualboot bios, if not work i will revert back to single os bios wait for report

Let us know how it goes – are you using the  C341a flasher? I ordered one so hope to try this too once it arrives. Can you post your steps if you succeed?

[Nick]

Guys I tried this and it has bricked my Hi12 – I would wait until Chuwi verify what models this is for as evidently it is not for all Hi12s!!

[Author]

Posts