• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

CHUWI Hi9 Air 64GB MT6797 X20 Deca Core 10.1 Inch 2K Screen Android 8 Dual 4G Tablet

My Chuwi Hi9 Air is running the _____ ROM?


  • Total voters
    142
Search This thread

Tinimark

New member
May 7, 2017
3
1
First of all, welcome! :)

Gearlabs is a ROM based on our stock system in Aug/2018 version. It has some improvements and is also pre-rooted with Magisk. You can check this post to download it. This other post has the link for the Gearlabs post and other ROMs/tutorials.

About GSIs, yeah, phhusson's AOSP is the best in terms of performance and compatibility; you can install v222 (just follow the tutorial to install Android 10 GSIs) or any v3xx (based on Android 11, you can follow the tutorial for Android 9 but you'll need to flash an encryption disabler zip to be able to boot).

But in fact, a lot of GSIs will boot and work well, like andyyan's LOS 17.1 and 18.1, eremitein's CAOS, LOSQ/LiR, Bless and CrDRom, braia's Nitrogen, and so on. The better, if you can, is trying the most GSIs you can to feel what's the best for you!

Also check out the most recent posts, in which we have been talking a little about these new GSIs, and feel free to ask and share your experiences with us :D
Hi,

I have two of these devices on factory firmware and they both become unresponsive after a few days of uptime requiring hard reset to reboot. I'm hoping this can be fixed with a newer firmware.

In your link to that guide it states Please make sure you have the stock firmware installed August 2018. Mine has July 2018 on it and It can't find any updates.

Any advice on how to proceed highly appreciated. :)
 

amg314

Senior Member
Feb 7, 2017
534
220
Kharkov
Hi,

I have two of these devices on factory firmware and they both become unresponsive after a few days of uptime requiring hard reset to reboot. I'm hoping this can be fixed with a newer firmware.

In your link to that guide it states Please make sure you have the stock firmware installed August 2018. Mine has July 2018 on it and It can't find any updates.

Any advice on how to proceed highly appreciated. :)
Look at 'Downloads' tab in Opening Post:

 
Aug 21, 2021
5
0
I am currently using android 9 gsi v123 phh treble vanilla
Tried it because I thought it would fix the oversaturated and oversharpened screen but it didn't. Also tried flashing v300l vanila but got stuck on android screen for very long....still didn't boot.....I tried the overlay @santosst gave in 9.0 gsi but the navigation bar disappeared so removed that......and flashed gapps pico but some apps with security concerns don't work....what should I do ? I have twrp installed and want to fix the screen and other app issues. Is there anything like we get in pixel experience plus rom to adjust screen saturation and any fix for the overlay issue?
 
Last edited:

santosst

Senior Member
Oct 7, 2020
67
31
Sao Paulo
Moto G
Xiaomi Mi A1
Also if the screen issue remains....what should I prefer on this device for now? To get everything working like the apps with security concerns?

I'd recommend you to test the newer Android 11 GSIs, especially the eternityson's ones, since they have an inbuilt option to pass SafetyNet, checking "SafetyNet" and "Spoof Pixel 5" in Phh Treble Settings -> Misc Features. With this feature, you should be able to use all apps in Play Store (I'm used to use NikGapps).

Only be sure you've flashed dm-verity and force encrypt disabler before booting to the GSI for the first time. Probably the issue you faced in v300l is related to the encryption (which is partially broken in A11 for some MTK devices including ours).

For me, the best GSI at this moment is Bless, the battery life is stunning and the only bug I've found is the upside-down front camera (what's a common issue since the latest A10 GSIs). I didn't notice any screen issue, however, I always use low brightness. Btw can you explain this screen issue, please?
 
Last edited:

santosst

Senior Member
Oct 7, 2020
67
31
Sao Paulo
Moto G
Xiaomi Mi A1

santosst

Senior Member
Oct 7, 2020
67
31
Sao Paulo
Moto G
Xiaomi Mi A1
Please let know URL for download in your posts.
I find out Bless TrebleGSI for a/b architrcture only

Oh, of course! We can use any of the arm64_a*Z builds here.

For example, this one (avZ) is vanilla, so we can install any gapps we want (or don't use them lol).

By the way, for some reason, when I did a factory reset, I'm not able to pass SafetyNet anymore using "SafetyNet"+"Spoof Pixel 5" options, and I really don't know why. If anyone can test, I'd appreciate it.

EDIT: Several custom ROM development teams have commented on the issue of SafetyNet failing with Pixel 5 spoofing due to a new Google certification algorithm strategy. In fact, several ROMs have already fixed it, such as PE, Descendant, and CAOS. Unfortunately Bless hasn't been updated for a while, but maybe we can be able to use some updated version of Gapps with Spoofing (I know NikGapps does that, but there's no updated stable version since mid-August, maybe a Canary Release can help us).
 
Last edited:
  • Like
Reactions: amg314

santosst

Senior Member
Oct 7, 2020
67
31
Sao Paulo
Moto G
Xiaomi Mi A1
Hey guys, some awesome news!

I was able to repartition my Hi9 Air, increasing the system partition to about 3.9 GB (4000 MB). The process was a bit tricky but I succeeded on my first try. Then I installed Pixel Experience 11 Unofficial by ponces (about 3.1 GB), and it's running almost perfectly (only flashlight and front camera aren't working, like the LOS-based ROMs* - Check EDIT). By the way, here are some screenshots:

Screenshot_20210921-191514.png Screenshot_20210921-190504.png Screenshot_20210921-190404.png

I'll probably make a tutorial soon, but my reference was this site: https://forum.hovatek.com/thread-32750.html

The only con is that the SP Flash tool doesn't work anymore if you repartition the device, only if you use "format all", but I fear that IMEI can be lost if using this option. For me, it's not a problem, but I should warn you.

EDIT: I rebooted the tablet and now flashlight and front camera works well (front camera is upside down, but it's a known bug related to cam2api).
 
Last edited:
  • Like
Reactions: cali34

thecoolkid

Senior Member
May 20, 2014
426
205
Hey guys, some awesome news!

I was able to repartition my Hi9 Air, increasing the system partition to about 3.9 GB (4000 MB). The process was a bit tricky but I succeeded on my first try. Then I installed Pixel Experience 11 Unofficial by ponces (about 3.1 GB), and it's running almost perfectly (only flashlight and front camera aren't working, like the LOS-based ROMs). By the way, here are some screenshots:

View attachment 5415649 View attachment 5415651 View attachment 5415653

I'll probably make a tutorial soon, but my reference was this site: https://forum.hovatek.com/thread-32750.html

The only con is that the SP Flash tool doesn't work anymore if you repartition the device, only if you use "format all", but I fear that IMEI can be lost if using this option. For me, it's not a problem, but I should warn you.

I have been playing with the same tutorial and successfully repartitioned 2 tablets, but I haven't had the time to post about it. The process is pretty straight forward and indeed you can't use SP Flash Tool afterwards except "format all" option, so I made myself a couple of tools to backup all the partitions that can't be flashed with SP Flash Tool and another one for restore. Another tool is to set up parted while you are in TWRP and to format vendor, system, cache and userdata afterwards (optional), because I was resizing vendor to 500 MB (there's some wasted space left by CHUWI, no harm in reclaiming it since there are no updates), system to 4 GB (4096 MB), cache to 100 MB (as per Google recommendation on AOSP site: 50-100 MB) and userdata to whatever's left. In the future I might write a tool for automatic repartitioning of the tablet, we'll see ;)

Some tips:
Follow the Hovatek guide, but remember:
1. Don't delete sdrpmb and flashinfo partitions, they are at the end of memory, but contrary to the guide you don't have to delete last partitions
2. You can remove just 28-31 partitions (vendor, system, cache, userdata) and the newly created partitions will "fall into place".
3. In parted you can switch units by a "unit" command followed by a unit (MB: 1000 MB = 1GB, MiB: 1024 MiB = 1 GiB, B: Bytes). I recommend using MiB for vendor, system, cache if you're pedantic like me ;) and then switching to Bytes for userdata partition to fit it exactly in the free space left.
4. I advise you to make a TWRP backup in case smth goes wrong (not partition image, compressed file backup) of boot, para (restore for recovering from bootloops, it contains a flag of unsuccessful boot and will reboot you to recovery even if you have a working system), vendor and system and also all device specific partitions that can't be flashed with SPFTool (you can use my tool for that).
5. You'll need vendor backup to restore it into smaller partition since the image backup won't fit. Offload the TWRP backup onto the computer. You'll lose access to all data stored on removed partitions!
6. I advise you to save parted output (partition list with their sizes, starts and ends) as text in a text file for multiple units (MB, MiB, B) for reference later, both before and after repartition. It'll make your life easier ;)
7. Your newly repartitioned device is best enjoyed with Modern Boots :D

FYI: My tools require PATH system variable to be set up to include ADB tool, so it can be executed from any folder as simply "adb [command]", if you don't have that edit the scripts to fit your environment. You have to be booted into TWRP with ADB enabled to use the tools. If you formated your whole memory with SPFTool, first flash all partitions in SPFT then flash TWRP then boot to TWRP and finally you can restore IMEI and DRM keys or whatever there is using restore tool ;)

FYI 2: Usefull terminal commands (prefix with adb shell if executing from adb):
# sgdisk --print /dev/block/mmcblk0
list all partitions in TWRP without parted

# parted /dev/block/mmcblk0 [unit MiB]
list all partitions in parted in automatic units [optional unit change, you can also change units later]

Have fun! ;)
 

Attachments

  • setup_parted.rar
    841.6 KB · Views: 9
  • backup_restore.rar
    817 bytes · Views: 4
Last edited:
  • Like
  • Love
Reactions: cali34 and santosst

santosst

Senior Member
Oct 7, 2020
67
31
Sao Paulo
Moto G
Xiaomi Mi A1
I have been playing with the same tutorial and successfully repartitioned 2 tablets, but I haven't had the time to post about it. The process is pretty straight forward and indeed you can't use SP Flash Tool afterwards except "format all" option, so I made myself a couple of tools to backup all the partitions that can't be flashed with SP Flash Tool and another one for restore. Another tool is to set up parted while you are in TWRP and to format vendor, system, cache and userdata afterwards (optional), because I was resizing vendor to 500 MB (there's some wasted space left by CHUWI, no harm in reclaiming it since there are no updates), system to 4 GB (4096 MB), cache to 100 MB (as per Google recommendation on AOSP site: 50-100 MB) and userdata to whatever's left. In the future I might write a tool for automatic repartitioning of the tablet, we'll see ;)

Some tips:
Follow the Hovatek guide, but remember:
1. Don't delete sdrpmb and flashinfo partitions, they are at the end of memory, but contrary to the guide you don't have to delete last partitions
2. You can remove just 28-31 partitions (vendor, system, cache, userdata) and the newly created partitions will "fall into place".
3. In parted you can switch units by a "unit" command followed by a unit (MB: 1000 MB = 1GB, MiB: 1024 MiB = 1 GiB, B: Bytes). I recommend using MiB for vendor, system, cache if you're pedantic like me ;) and then switching to Bytes for userdata partition to fit it exactly in the free space left.
4. I advise you to make a TWRP backup in case smth goes wrong (not partition image, compressed file backup) of boot, para (restore for recovering from bootloops, it contains a flag of unsuccessful boot and will reboot you to recovery even if you have a working system), vendor and system and also all device specific partitions that can't be flashed with SPFTool (you can use my tool for that).
5. You'll need vendor backup to restore it into smaller partition since the image backup won't fit. Offload the TWRP backup onto the computer. You'll lose access to all data stored on removed partitions!
6. I advise you to save parted output (partition list with their sizes, starts and ends) as text in a text file for multiple units (MB, MiB, B) for reference later, both before and after repartition. It'll make your life easier ;)
7. Your newly repartitioned device is best enjoyed with Modern Boots :D

FYI: My tools require PATH system variable to be set up to include ADB tool, so it can be executed from any folder as simply "adb [command]", if you don't have that edit the scripts to fit your environment. You have to be booted into TWRP with ADB enabled to use the tools. If you formated your whole memory with SPFTool, first flash all partitions in SPFT then flash TWRP then boot to TWRP and finally you can restore IMEI and DRM keys or whatever there is using restore tool ;)

FYI 2: Usefull terminal commands (prefix with adb shell if executing from adb):
# sgdisk --print /dev/block/mmcblk0
list all partitions in TWRP without parted

# parted /dev/block/mmcblk0 [unit MiB]
list all partitions in parted in automatic units [optional unit change, you can also change units later]

Have fun! ;)
Wow, great, thank you very much! Everything I'd like to tell are in your tips (including Modern Boots 😁 )
Furthermore, thanks for sharing your tools, I'll probably take a backup of all partitions right now lol, and if you manage to write the re-partitioning tool, it'd be amazing :D
 
  • Like
Reactions: thecoolkid

ULAMSS5

Senior Member
Apr 7, 2012
168
23
I have been playing with the same tutorial and successfully repartitioned 2 tablets, but I haven't had the time to post about it. The process is pretty straight forward and indeed you can't use SP Flash Tool afterwards except "format all" option, so I made myself a couple of tools to backup all the partitions that can't be flashed with SP Flash Tool and another one for restore. Another tool is to set up parted while you are in TWRP and to format vendor, system, cache and userdata afterwards (optional), because I was resizing vendor to 500 MB (there's some wasted space left by CHUWI, no harm in reclaiming it since there are no updates), system to 4 GB (4096 MB), cache to 100 MB (as per Google recommendation on AOSP site: 50-100 MB) and userdata to whatever's left. In the future I might write a tool for automatic repartitioning of the tablet, we'll see ;)

Some tips:
Follow the Hovatek guide, but remember:
1. Don't delete sdrpmb and flashinfo partitions, they are at the end of memory, but contrary to the guide you don't have to delete last partitions
2. You can remove just 28-31 partitions (vendor, system, cache, userdata) and the newly created partitions will "fall into place".
3. In parted you can switch units by a "unit" command followed by a unit (MB: 1000 MB = 1GB, MiB: 1024 MiB = 1 GiB, B: Bytes). I recommend using MiB for vendor, system, cache if you're pedantic like me ;) and then switching to Bytes for userdata partition to fit it exactly in the free space left.
4. I advise you to make a TWRP backup in case smth goes wrong (not partition image, compressed file backup) of boot, para (restore for recovering from bootloops, it contains a flag of unsuccessful boot and will reboot you to recovery even if you have a working system), vendor and system and also all device specific partitions that can't be flashed with SPFTool (you can use my tool for that).
5. You'll need vendor backup to restore it into smaller partition since the image backup won't fit. Offload the TWRP backup onto the computer. You'll lose access to all data stored on removed partitions!
6. I advise you to save parted output (partition list with their sizes, starts and ends) as text in a text file for multiple units (MB, MiB, B) for reference later, both before and after repartition. It'll make your life easier ;)
7. Your newly repartitioned device is best enjoyed with Modern Boots :D

FYI: My tools require PATH system variable to be set up to include ADB tool, so it can be executed from any folder as simply "adb [command]", if you don't have that edit the scripts to fit your environment. You have to be booted into TWRP with ADB enabled to use the tools. If you formated your whole memory with SPFTool, first flash all partitions in SPFT then flash TWRP then boot to TWRP and finally you can restore IMEI and DRM keys or whatever there is using restore tool ;)

FYI 2: Usefull terminal commands (prefix with adb shell if executing from adb):
# sgdisk --print /dev/block/mmcblk0
list all partitions in TWRP without parted

# parted /dev/block/mmcblk0 [unit MiB]
list all partitions in parted in automatic units [optional unit change, you can also change units later]

Have fun! ;)
For anyone else getting:
parted /dev/block/mmcblk0 /sbin/sh: parted: Permission denied

I solved it by doing another factory reset in TWRP, un-checking all mounts (since it has rebooted), and "Disable MTP" (apparently not needed).

@thecoolkid your .bat tool appears to only delete the partitions 28-31, but does not re-create the system partition? Am i reading it wrongly? Or does the system partition not have to be manually re-created?

Also, which PixelExperience did you flash? I tried "PixelExperience_arm64-aonly-11.0-20211009-UNOFFICIAL.img.xz" but it does not work for me. Still boots back into TWRP.



I had a lot of trouble understanding the instructions, but finally got it to work. For anyone else confused, this is the set of commands I used after entering parted.

Your exact locations may differ from mine, please double check your factory settings and re-align. Best to print after every mkpart x... to check.

rm 28 rm 29 rm 30 rm 31 mkpart vendor ext4 241 741 name 28 vendor set 28 msftdata on mkpart system ext4 741 4837 name 29 system set 29 msftdata on mkpart cache ext4 4837 4937 name 30 cache set 30 msftdata on mkpart userdata ext4 4937 100% name 31 userdata set 30 msftdata on quit mkfs.ext4 /dev/block/mmcblk0p31
 
Last edited:

thecoolkid

Senior Member
May 20, 2014
426
205
@thecoolkid your .bat tool appears to only delete the partitions 28-31, but does not re-create the system partition? Am i reading it wrongly? Or does the system partition not have to be manually re-created?

My tool does not create or delete any partitions on it's own. It boots parted and when parted exits it asks if you want to format partitions 28-31 as EXT4, because they need to be formatted before they can be used and parted doesn't do that even if you flag newly created partitions as EXT4. You can skip that process and format manually in TWRP, my tool just makes it easier and faster, but it assumes all necessary partitions are already created.

From you instructions I noticed you're leaving unallocated space between partitions, you don't have to do that. Read through my tips and change unit to MiB and use the same number as end of one partition and a start of the next one, parted will fit them nicely and then again change unit for userdata to B and then fit it exactly in the leftover space.
 
  • Like
Reactions: ULAMSS5

ULAMSS5

Senior Member
Apr 7, 2012
168
23
My tool does not create or delete any partitions on it's own. It boots parted and when parted exits it asks if you want to format partitions 28-31 as EXT4, because they need to be formatted before they can be used and parted doesn't do that even if you flag newly created partitions as EXT4. You can skip that process and format manually in TWRP, my tool just makes it easier and faster, but it assumes all necessary partitions are already created.

From you instructions I noticed you're leaving unallocated space between partitions, you don't have to do that. Read through my tips and change unit to MiB and use the same number as end of one partition and a start of the next one, parted will fit them nicely and then again change unit for userdata to B and then fit it exactly in the leftover space.

Thanks, I've edited my post above to fit.

Do mind sharing instructions and which specific files needed to flash PixelExperience? When I tried it it only boots me to TWRP. Should I flash back to OEM with SPFT?
 
Last edited:

thecoolkid

Senior Member
May 20, 2014
426
205
Thanks, I've edited my post above to fit.

Do mind sharing instructions and which specific files needed to flash PixelExperience? When I tried it it only boots me to TWRP. Should I flash back to OEM with SPFT?

If you read my tips you'll know that you can't use SPFT after repartitioning, it'll format whole memory block. By now, you should've made a backup using my tool and a twrp backup of system, vendor, boot and para partitions. After repartitioning you have to restore vendor and para in twrp. Then PE should work.
 
Last edited:

ULAMSS5

Senior Member
Apr 7, 2012
168
23
If you read my tips you'll know that you can't use SPFT after repartitioning, it'll format whole memory block. By now, you should've made a backup using my tool and a twrp backup of system, vendor, boot and para partitions. After repartitioning you have to restore vendor and para in twrp. Then PE should work.
Sorry some of your tips are not very clear... especially with the Hovatek guide, steps are all over the place.

So for someone coming in fresh (or with a semi-bricked device):
1. SPFT back to OEM, boot in to enable OEM unlock... USB Debugging... fastboot unlock oem... flash twrp
2. Do the repartioning stuff above
3. "restore vendor and para in twrp", is this just steps 21-22 in the Hovatek guide? Also, what is "para"? I've never seen this partition before.
4. Flash Pixel Arm64 AONLY? Any need for other stuff like "no-verity-opt-encrypt" or "permissiver" or anything like that?
 

thecoolkid

Senior Member
May 20, 2014
426
205
Sorry some of your tips are not very clear... especially with the Hovatek guide, steps are all over the place.

So for someone coming in fresh (or with a semi-bricked device):
1. SPFT back to OEM, boot in to enable OEM unlock... USB Debugging... fastboot unlock oem... flash twrp
2. Do the repartioning stuff above
3. "restore vendor and para in twrp", is this just steps 21-22 in the Hovatek guide? Also, what is "para"? I've never seen this partition before.
4. Flash Pixel Arm64 AONLY? Any need for other stuff like "no-verity-opt-encrypt" or "permissiver" or anything like that?

1. If you format with SPFT and don't have IMEI backup you'll lose all the keys of your device. Make a backup first. After flashing stock, unlock bootloader, flash twrp.
3. No. You need to restore data to vendor partition after you deleted it's data, this is where all the drivers are. Para is a partition that holds a flag that will prevent booting even on a working system after a bootloop. You need to restore it to be able to boot.
4. You don't need permissiver, but of course you need to flash disable verity and optional encrypt, encryption is not supported in TWRP and GSI's and verity needs to be disabled to be able to boot any custom ROM.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hey guys, some awesome news!

    I was able to repartition my Hi9 Air, increasing the system partition to about 3.9 GB (4000 MB). The process was a bit tricky but I succeeded on my first try. Then I installed Pixel Experience 11 Unofficial by ponces (about 3.1 GB), and it's running almost perfectly (only flashlight and front camera aren't working, like the LOS-based ROMs). By the way, here are some screenshots:

    View attachment 5415649 View attachment 5415651 View attachment 5415653

    I'll probably make a tutorial soon, but my reference was this site: https://forum.hovatek.com/thread-32750.html

    The only con is that the SP Flash tool doesn't work anymore if you repartition the device, only if you use "format all", but I fear that IMEI can be lost if using this option. For me, it's not a problem, but I should warn you.

    I have been playing with the same tutorial and successfully repartitioned 2 tablets, but I haven't had the time to post about it. The process is pretty straight forward and indeed you can't use SP Flash Tool afterwards except "format all" option, so I made myself a couple of tools to backup all the partitions that can't be flashed with SP Flash Tool and another one for restore. Another tool is to set up parted while you are in TWRP and to format vendor, system, cache and userdata afterwards (optional), because I was resizing vendor to 500 MB (there's some wasted space left by CHUWI, no harm in reclaiming it since there are no updates), system to 4 GB (4096 MB), cache to 100 MB (as per Google recommendation on AOSP site: 50-100 MB) and userdata to whatever's left. In the future I might write a tool for automatic repartitioning of the tablet, we'll see ;)

    Some tips:
    Follow the Hovatek guide, but remember:
    1. Don't delete sdrpmb and flashinfo partitions, they are at the end of memory, but contrary to the guide you don't have to delete last partitions
    2. You can remove just 28-31 partitions (vendor, system, cache, userdata) and the newly created partitions will "fall into place".
    3. In parted you can switch units by a "unit" command followed by a unit (MB: 1000 MB = 1GB, MiB: 1024 MiB = 1 GiB, B: Bytes). I recommend using MiB for vendor, system, cache if you're pedantic like me ;) and then switching to Bytes for userdata partition to fit it exactly in the free space left.
    4. I advise you to make a TWRP backup in case smth goes wrong (not partition image, compressed file backup) of boot, para (restore for recovering from bootloops, it contains a flag of unsuccessful boot and will reboot you to recovery even if you have a working system), vendor and system and also all device specific partitions that can't be flashed with SPFTool (you can use my tool for that).
    5. You'll need vendor backup to restore it into smaller partition since the image backup won't fit. Offload the TWRP backup onto the computer. You'll lose access to all data stored on removed partitions!
    6. I advise you to save parted output (partition list with their sizes, starts and ends) as text in a text file for multiple units (MB, MiB, B) for reference later, both before and after repartition. It'll make your life easier ;)
    7. Your newly repartitioned device is best enjoyed with Modern Boots :D

    FYI: My tools require PATH system variable to be set up to include ADB tool, so it can be executed from any folder as simply "adb [command]", if you don't have that edit the scripts to fit your environment. You have to be booted into TWRP with ADB enabled to use the tools. If you formated your whole memory with SPFTool, first flash all partitions in SPFT then flash TWRP then boot to TWRP and finally you can restore IMEI and DRM keys or whatever there is using restore tool ;)

    FYI 2: Usefull terminal commands (prefix with adb shell if executing from adb):
    # sgdisk --print /dev/block/mmcblk0
    list all partitions in TWRP without parted

    # parted /dev/block/mmcblk0 [unit MiB]
    list all partitions in parted in automatic units [optional unit change, you can also change units later]

    Have fun! ;)
    2
    Sorry some of your tips are not very clear... especially with the Hovatek guide, steps are all over the place.

    So for someone coming in fresh (or with a semi-bricked device):
    1. SPFT back to OEM, boot in to enable OEM unlock... USB Debugging... fastboot unlock oem... flash twrp
    2. Do the repartioning stuff above
    3. "restore vendor and para in twrp", is this just steps 21-22 in the Hovatek guide? Also, what is "para"? I've never seen this partition before.
    4. Flash Pixel Arm64 AONLY? Any need for other stuff like "no-verity-opt-encrypt" or "permissiver" or anything like that?

    1. If you format with SPFT and don't have IMEI backup you'll lose all the keys of your device. Make a backup first. After flashing stock, unlock bootloader, flash twrp.
    3. No. You need to restore data to vendor partition after you deleted it's data, this is where all the drivers are. Para is a partition that holds a flag that will prevent booting even on a working system after a bootloop. You need to restore it to be able to boot.
    4. You don't need permissiver, but of course you need to flash disable verity and optional encrypt, encryption is not supported in TWRP and GSI's and verity needs to be disabled to be able to boot any custom ROM.
    1
    Hey guys, some awesome news!

    I was able to repartition my Hi9 Air, increasing the system partition to about 3.9 GB (4000 MB). The process was a bit tricky but I succeeded on my first try. Then I installed Pixel Experience 11 Unofficial by ponces (about 3.1 GB), and it's running almost perfectly (only flashlight and front camera aren't working, like the LOS-based ROMs* - Check EDIT). By the way, here are some screenshots:

    Screenshot_20210921-191514.png Screenshot_20210921-190504.png Screenshot_20210921-190404.png

    I'll probably make a tutorial soon, but my reference was this site: https://forum.hovatek.com/thread-32750.html

    The only con is that the SP Flash tool doesn't work anymore if you repartition the device, only if you use "format all", but I fear that IMEI can be lost if using this option. For me, it's not a problem, but I should warn you.

    EDIT: I rebooted the tablet and now flashlight and front camera works well (front camera is upside down, but it's a known bug related to cam2api).
    1
    I have been playing with the same tutorial and successfully repartitioned 2 tablets, but I haven't had the time to post about it. The process is pretty straight forward and indeed you can't use SP Flash Tool afterwards except "format all" option, so I made myself a couple of tools to backup all the partitions that can't be flashed with SP Flash Tool and another one for restore. Another tool is to set up parted while you are in TWRP and to format vendor, system, cache and userdata afterwards (optional), because I was resizing vendor to 500 MB (there's some wasted space left by CHUWI, no harm in reclaiming it since there are no updates), system to 4 GB (4096 MB), cache to 100 MB (as per Google recommendation on AOSP site: 50-100 MB) and userdata to whatever's left. In the future I might write a tool for automatic repartitioning of the tablet, we'll see ;)

    Some tips:
    Follow the Hovatek guide, but remember:
    1. Don't delete sdrpmb and flashinfo partitions, they are at the end of memory, but contrary to the guide you don't have to delete last partitions
    2. You can remove just 28-31 partitions (vendor, system, cache, userdata) and the newly created partitions will "fall into place".
    3. In parted you can switch units by a "unit" command followed by a unit (MB: 1000 MB = 1GB, MiB: 1024 MiB = 1 GiB, B: Bytes). I recommend using MiB for vendor, system, cache if you're pedantic like me ;) and then switching to Bytes for userdata partition to fit it exactly in the free space left.
    4. I advise you to make a TWRP backup in case smth goes wrong (not partition image, compressed file backup) of boot, para (restore for recovering from bootloops, it contains a flag of unsuccessful boot and will reboot you to recovery even if you have a working system), vendor and system and also all device specific partitions that can't be flashed with SPFTool (you can use my tool for that).
    5. You'll need vendor backup to restore it into smaller partition since the image backup won't fit. Offload the TWRP backup onto the computer. You'll lose access to all data stored on removed partitions!
    6. I advise you to save parted output (partition list with their sizes, starts and ends) as text in a text file for multiple units (MB, MiB, B) for reference later, both before and after repartition. It'll make your life easier ;)
    7. Your newly repartitioned device is best enjoyed with Modern Boots :D

    FYI: My tools require PATH system variable to be set up to include ADB tool, so it can be executed from any folder as simply "adb [command]", if you don't have that edit the scripts to fit your environment. You have to be booted into TWRP with ADB enabled to use the tools. If you formated your whole memory with SPFTool, first flash all partitions in SPFT then flash TWRP then boot to TWRP and finally you can restore IMEI and DRM keys or whatever there is using restore tool ;)

    FYI 2: Usefull terminal commands (prefix with adb shell if executing from adb):
    # sgdisk --print /dev/block/mmcblk0
    list all partitions in TWRP without parted

    # parted /dev/block/mmcblk0 [unit MiB]
    list all partitions in parted in automatic units [optional unit change, you can also change units later]

    Have fun! ;)
    Wow, great, thank you very much! Everything I'd like to tell are in your tips (including Modern Boots 😁 )
    Furthermore, thanks for sharing your tools, I'll probably take a backup of all partitions right now lol, and if you manage to write the re-partitioning tool, it'd be amazing :D
    1
    Wow, great, thank you very much! Everything I'd like to tell are in your tips (including Modern Boots 😁 )
    Furthermore, thanks for sharing your tools, I'll probably take a backup of all partitions right now lol, and if you manage to write the re-partitioning tool, it'd be amazing :D
    Haha Thx! :p I guess I needed a gentle nudge to write this guide :p
  • 22
    TWRP 3.2.2-0

    Fully working TWRP 3.2.2-0 (updated on the 03rd of September 2018) based on "O00623 release-keys 20180809" (August 2018 update)

    Download Folder: https://www.androidfilehost.com/?w=files&flid=281733

    ####
    ## TWRP 3.2.2-0 brief installation guide for the CHUWI Hi9 Air (Hi9Air)
    ## Developed and Written by Alberto96 (GearLabs)
    ####


    NOTE: For those who want to keep the bootloader locked, follow the SP Flash Tool guide.

    Flashing via SP Flash Tool (noob-friendly):

    1) Download the latest SP Flash Tool software for your preferred OS (Windows/Linux)
    2) Proceed as shown in my guide linked here: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk/edit

    Flashing via Fastboot (minor skills required):

    WARNING: If your bootloader is not unlocked already, then it is time to do it otherwise you won't be able to flash any custom binary. DO NOT untick the "OEM Unlock" option in the "Developer Options" menu after having flashed the custom recovery.


    1) Reboot into fastboot mode (using the Volume Up + Power keys combo or just by executing "adb reboot bootloader" via ADB or a Terminal on the device)
    2) Execute this command: "fastboot flash recovery recovery.img"
    3) Now you can reboot the device by executing "fastboot reboot" or by long-pressing the power button for a while

    IMPORTANT: Be sure to root your device using Magisk (recommended for SafetyNet) or SuperSU (classic and permanent) right after having installed the custom recovery (before even rebooting into Android!) otherwise, as a security feature, Android will overwrite it with the Stock Recovery thus you will have to repeat the procedure. DO NOT blame the recovery for this since you have been warned.

    // Any procedure shown here has been tested but, obviously, you do it at your own risk. If you don't mess with anything indicated above, the chance to run into issues is almost inexistent. Good luck! //

    Device Tree: https://github.com/GearLabs/android_device_CHUWI_Hi9Air
    21
    GearLabs ROM (v3 20180917)

    GearLabs ROM

    This is just a modified Stock ROM containing some improvements and fixes in order to provide the best user experience possible, until GSIs get a proper documentation to replace completely, and properly, the stock software. Basically, this is how CHUWI should have released the software by default.

    Download Folder:: https://www.androidfilehost.com/?w=files&flid=279461

    Please make sure to have the latest August 2018 Stock ROM installed on your device before proceeding.

    Install it via fastboot (fastboot flash boot boot.img & fastboot flash system system.img), remember to unlock the BL first if you haven't already. The installation process may take up to 20 minutes depending on your PC and USB connection stability, then reboot the device (fastboot reboot).
    You can install it via SP Flash Tool too if you use the original scatter file from the Stock ROM if you prefer to keep your bootloader locked.

    What has been changed/improved:
    - Pre-patched using Magisk v17.1 to pass SafetyNet even with the bootloader unlocked
    - 90% of MTK apps have been replaced with better Google variants
    - Most pre-installed Google Apps have been updated to the latest version (mid-September 2018)
    - Removed Adups FOTA updater

    Bugs:
    - None noticed, please tell me if there is any.

    Changelog (v3 20180917):
    - Fixed issues with Google Photos
    - Based on the GMS-certified August 2018 release
    - Switched to a proper Pixel boot animation
    - All sounds have been replaced with Google Pixel ones

    Feature requests that require framework modifications won't be accepted, but i am open to any possible improvement if can be made to the ROM.
    NOTE: Before you ask me, no, it isn't possible to reduce the saturation level without major modifications. I won't be touching the vendor partition neither adding any software as a workaround.
    20
    CHUWI Hi9 Air 64GB MT6797 X20 Deca Core 10.1 Inch 2K Screen Android 8..0 Dual 4G Tablet

    Specifications

    Model CHUWI Hi9 Air
    CPU MTK6797 Helio X20 Deca Core 20nm
    A72*2 2.3 GHz
    A53*4 1.4 GHz
    A53*4 1.85 GHz
    GPU ARM Mali-T880 780MHz
    System Android 8.0
    RAM 4GB DDR3
    Capacity 64GB EMMC
    Screen 10.1 Inch IPS Capacitive Screen
    Resolution 2560*1600
    299 PPI Pixel Density
    OGS One Glass Solution Fully Laminated
    Camera Front is 5.0MP Rear is 13.0MP
    Microphone Built-in
    Speaker Built-in
    WIFI 802.11 a/b/g/n/ac(support 2.4GHz and 5.0 GHz)
    Bluetooth 4.2
    GPS Support
    G-sensor Support
    Brand(Network)
    GSM: (Please see pictures below)
    WCDMA: (Please see pictures below)
    LTE:1/2/3/4/5/7/8/12/17/20/28/38/39/40/41
    OTG Support
    TF Card Support (Maximum support 128G)
    Audio AAC,AMR,MP3,OGG,WAV,ACC,M4A,FLAC
    Picture JPEG,GIF,BMP,PNG,JPG
    Video 3GP,AVI,MKV,MP4,M4V,WEBM,MPEG4
    Language Multi-language
    I/O Port 1 x Micro USB port
    1 x 3.5mm Earphone port
    1 x TF card slot(Max Support 128G)
    2 x Micro SIM Card slot
    Battery 8000mAh
    Weight 550g
    Size 241.7*172*7.9mm

    In Box
    1 x CHUWI Hi9 Air Tablet PC
    1 x USB Cable
    1 x Charger
    1 x Adapter (the adapter depends on the country of the buyer.)


    Home page https://en.chuwi.com/
    Image of Front
    attachment.php

    Image of Back
    attachment.php

    Image of Buttons
    attachment.php


    Videos
    Chuwi Hi9 Air, Unboxing, Review, Gaming and Root https://youtu.be/6jnJSHE5lck
    00.00 Unboxing from Banggood
    02.04 Throw away screen protector
    02.58 Fitting Sims and MicroSD
    04.03 Powering On
    04.40 Screen
    05.48 Android 8.0.0
    06.15 System Update
    06.27 Factory Reset
    06.57 UI Stock Android
    07.47 Gapps including Play Store
    08.26 Uncertified Device
    08.51 Brightness not adjustable (Solved) https://forum.xda-developers.com/showpost.php?p=76505791&postcount=22
    10.13 Battery
    10.46 Build Quality, dimensions and thickness
    12.14 4G/LTE Bands
    13.36 Phone Calls
    14.36 Whatsapp
    15.13 Cameras
    15.35 Boot Safe Mode
    16.29 Haptic feedback supported
    16.46 Photo and video quality
    17.58 GPS
    18.17 Wifi
    18.41 Teamviewer supported
    19.07 Benchmarks, Ice Storm, Geekbench, Battery,
    20.26 Antutu
    20.40 Androbench eMMC
    21.00 Treble
    21.47 Stock Apps
    21.52 Large PDF performance
    22.32 Web browsing
    23.13 Thermals and reboots
    23.50 Gaming, Asphalt 8
    24.59 Pubg
    26.04 Conclusion
    26.58 Root


    Review by @Alberto96

    How to Update
    Android Security Updates go to Settings >System >System Update >Check for update
    Wireless Update (OTA) go to Settings >System >About Tablet >Wireless Update >Check for updates >Download >Install now >OK and System reboot.
    Backup NVRAM/IMEI http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html

    Downloads



    How to Flash Stock Rom
    Download and extract stock ROM
    Download and extract flashtool and install mtk driver (disable driver signature enforcement)
    Get rid of any chinese characters in directory names
    Download da file to flashtool directory
    Open flashtool and open da file and open scatter file in stock ROM directory
    Click download
    Plug in powered off tablet
    Wait for ok

    Flash not working? Troubleshoot
    Ignore any errors
    Use flashtool in link
    Get rid of any chinese characters in directory names
    Open and close flashtool a few times before you click download
    attachment.php


    How to Root
    There are three ways to root.
    1. Install twrp then install supersu with zip.
    2. Install twrp then install magisk with zip.
    3. Flash magisk modified boot.img.
    How to install Twrp https://www.xda-developers.com/how-to-install-twrp/
    TWRP Custom Recovery created by @Alberto96
    SuperSU Download SuperSU TWRP Zip
    Install supersu or magisk with zip file using twrp> install

    Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
    Download Magisk TWRP Zip
    MTK Drivers and ADB required
    How to install magisk with modified boot.img ;
    Backup your data, tablet will be wiped
    download patched_boot.img Stock Rom Build number O00623 release-keys 20180506
    OR patched_boot.img Stock Rom Build number O00623 release-keys 20180604
    OR patched_boot.img Stock Rom Build number O00623 release-keys 20180809
    to adb directory in PC
    enable developer options, settings, system, about tablet, build number, tap until developer
    connect cable to pc
    settings, system, developer options, enable oem unlocking
    settings, system, developer options, enable usb debugging
    allow usb devices
    adb reboot bootloader or shutdown and then press power + volume up, select fastboot
    fastboot oem unlock
    press volume up (yes)
    fastboot flash boot patched_boot.img
    OKAY
    fastboot reboot OR cycle power to reboot, erasing device is normal
    restore tablet (copy your data)
    Install latest Magisk Manager
    run magisk manager
    Check for Root with Root Checker
    Your Hi9 Air is rooted with Magisk!

    Time to Boot 30s

    Available space first boot 56.5 GB
    7.47/64 GB MB Used
    Pre-installed bloat NONE!

    How to take a screenshot
    Press Power + Volume Down at the same time.

    Support. Install latest build before requesting support.

    How to enable Split Screen
    Open two apps
    Tap and hold android menu or overview button, select second app
    You can drag the middle point

    Apps tested and working
    Advanced Power Menu [ROOT]
    Buffer
    Control Screen Orientation
    Duo
    Find My Device
    Fitbit
    GMD Immersive (hides soft keys)
    IFTTT
    MacroDroid
    Mr. Number
    Netflix (qHD 960x540)
    Open Camera
    Phone Check
    Prey
    Rolo
    Shazam
    Signal
    Skype
    Uber
    Waze
    Whatsapp
    YouTube (Up to 1440p)



    Accessories
    Cases

    Benchmarks
    Antutu Pass 1
    attachment.php

    Antutu Pass 2
    attachment.php

    3DMark Ice Storm Extreme and Sling Shot Extreme
    attachment.php

    Geekbench Single Core
    attachment.php

    Geekbench Multi-core
    attachment.php

    Geekbench Compute
    attachment.php

    Geekbench Battery
    attachment.php

    Androbench (Storage Benchmark)
    attachment.php

    GPS
    attachment.php

    Home Screen
    attachment.php

    Teamviewer
    attachment.php

    Wifi
    attachment.php

    2G/3G/4G/LTE Cat 6 Bands (Support for LTE:1/2/3/4/5/7/8/12/17/20/28/38/39/40/41)
    attachment.php

    attachment.php

    Stock Apps
    attachment.php

    Treble Supported but A-System partition only
    attachment.php

    Battery Performance Normal Use 7-8 hours
    attachment.php


    Updates
    09/04/2018 I Ordered / pre-ordered
    13/04/2018 New video
    06/05/2018 Received my Chuwi Hi9 Air yesterday Saturday 05/05/18
    10/05/2018 Review posted to youtube see above
    11/05/2018 More pictures and info
    25/05/2018 Link to cases
    04/06/2018 Added links to downloads
    05/06/2018 Added how to flash, how to install magisk and updated known issues
    18/06/2018 Added alternate download link and updated known issues
    20/06/2018 Added TWRP
    01/09/2018 Added links to Build 20180809
    03/11/2018 Added O00623 release-keys 20180905 Update Bugs
    08/11/2018 Download OTA 20181010
    28/11/2018 Download 20181122
    28/11/2018 All CHUWI tablets with Helio X20, X23, X27(or higher verison) will be updated to Android 9.0 in 2019
    14/02/2020 New link to download twrp
    14
    LineageOS 15.1

    This post will be dedicated to all releases. Please read everything carefully before proceeding with the install.

    LineageOS-15.1-1.png


    Downloads:
    v0.1 Fastboot ROM: https://www.androidfilehost.com/?fid=5862345805528051928
    v0.2 Fastboot ROM: https://www.androidfilehost.com/?fid=5862345805528055015
    Magisk for Treble: https://github.com/Jerry981028/Magisk
    Google Apps (choose ARM64 and 8.1, the package variant is up to you): https://opengapps.org/
    The ROM includes my TWRP 3.2.2 by default

    HOW-TO Install:
    1. If you are a Windows User, be sure to have all ADB/Fastboot drivers and tools installed. For Linux, just the tools.
    2. Flash the latest Stock ROM using SP Flash Tool and unlock the bootloader.
    3. Turn on (or reboot, as you prefer) the tablet into fastboot mode (Volume up + Power, a boot menu will appear, choose fastboot mode and confirm with the Volume down button)
    4. Connect it to your PC/Laptop/Whatever (of course)
    5. Run the included script (flash_all.sh for Linux, flash_all.bat for Windows) to start the installation process
    6. Done, the tablet will reboot automatically into LineageOS.
    7. NOTE: If you need Google Apps and/or Magisk, just reboot into recovery mode, wipe data/factory reset, install what you need, and reboot again. No extra steps required in between, just follow the order.

    Current bugs:
    - Animations are not 100% smooth just like the whole UI
    - Default orientation is in portrait mode but the touchscreen and accelerometer will handle it properly
    - Sometimes it glitches during the setup wizard requiring an hard reboot
    - Built-in LineageOS Browser doesn't work
    - Current builds cause a partition size bug (userdata, 4GB only). Please "Format /data" (no wipe) after installation in order to fix it
    - Several issues with Google Apps (Play Services keeps crashing due to library issues). Any variant (like pico, nano...) that doesn't include Webview causes Google Setup Wizard to get into a ~ black screen.

    Changelog:
    v0.2:
    - Massive performance improvements
    - Enabled FM Radio (untested)
    - Disabled animations by default in order to avoid any possible glitch
    - Fixed Open Gapps Stock package installation bug (no space left message)
    - Other minor fixes here and there

    Additions made to improve the device:
    - Certified Fingerprint to pass SafetyNet (as long as you also install Magisk)
    10
    Review

    Unboxing


    1Nmngjjl.jpg


    34A6eijl.jpg



    Following all recent CHUWI products (like the Lapbook Air), this one comes in a eco-friendly packaging with not many accessories included: 1x 5V/2A USB Charger, 1x Micro-USB Cable, 1x Warranty Card and other paperwork.


    w2IXVxGl.jpg



    Something sure is that CHUWI requires a good translator, since the User Manual says something weird in the title: "The User Manual of Poly nuclear series Tablet PC". Okay...:facepalm:


    OCNqcdQl.jpg




    The device features a full metal body with a plastic band on the top where antennas and SIM/MicroSD slots are located. From a design prospective, it looks great on the back, but on the front there is a slight loss of space caused by thick bezels. I am noy saying the bezel-less would be better, on a tablet they are required, but just slightly slimmer would have been nicer.


    H2t3RC0l.jpg



    Its weight is just fine, ~560g, just consider to use it with two hands. Nothing to complain about its thickness, but i would consider to use a case due to the slippery back metal.


    Sp2fq0zl.jpg



    On the front there is the gorgeous 10.1" WQXGA (or wider 2K if you prefer) that looks just excellent except from one thing: the brightness. I read online that its brightness has been limited via software with the latest update. Unfortunately mine was updated out of the box so i can't confirm that, but if that's real, i hope it can be restored via a framework patch to get its full brightness back.

    Anyway, excluding the brightness issue, it looks perfect with great colors (don't trust the photo attached below, reflections destroy it), high pixel density and excellent viewing angles. Also, on the upper center zone, there is a front-facing camera. No sensors (light/proximity) or Notification LEDs are there.


    zHWl41Ql.jpg



    The upper rear side of the device features the Antenna/Slots area together with a camera sensor supported by a Flashlight. It is possible to use 2x Micro-SIMs and 1x MicroSD, with separate slots for each one.


    cQKAdwHl.jpg



    Device

    Camera

    As regards the Camera, it is as good/bad as you can probably expect from a Tablet. Even though the rear camera looks, on paper, quite decent, colors are washed-out. It is probably a 8MP camera sensor interpolated to 13MP, but i was not able to get any detail about the sensor so i may add more details later.

    Here are some samples, judge by yourself. Luckily it supports auto-focus so it is possible to get some interesting macro shots.


    lOcXOpFl.jpg
    vMLixRzl.jpg


    I4g6Gucl.jpg
    1sTDaszl.jpg


    ebpeibMl.jpg
    nVOwG4kl.jpg



    I won't be posting any front-facing camera sample since the quality is even worse, barely enough for video-calls.


    Audio

    The way speakers have been implemented on this device is quite intelligent and never seen before in person. They are positioned on the top, where the charging port and headphone jack are located.

    Quality-wise they are decent, probably identical to what you can get from a smartphone, just doubled since this is a stereo configuration. Perfectly usable in my opinion.


    502yYku.jpg



    The microphone instead is located on the side, just below the volume buttons. It works decently, but due to the placement it is easy to get one hand on it.


    4zbDiKgl.jpg



    GPS & Location

    GPS quality is excellent for a tablet, able to lock satellites almost everywhere with high accuracy.


    R3sG8seh.png



    Telephony, Mobile Network & WiFi

    The same can't be said for the 4G antenna. For some reason (and this is not an isolated case, just search online to know more), the signal is much lower than what i get on my smartphone, and speed tests definitely confirm that (two different mobile operators tested, same crappy result)


    iRLuqj1h.png
    9XevJiQh.png



    This is a bit disappoting because unlike other Chinese tablets i have found online, this comes with full 4G bands support for my country (and also others) including Band 20, so not being able to use it properly is not that great. Here you can see all the supported bands, i have the European model.


    y91yjTph.png
    aNfJqeZh.png



    Just some extra details about the network cell i was connected too, for geeks.


    ETGOwIsh.png



    Nothing to complain about the WiFi signal reception, pretty average, similar to some smartphones i have reviewed in the past. It is nice to see that it supports WiFi AC networks with speeds up to 433mbps, at least it hasn't been locked via software.


    Y9uMkUWh.png


    Battery Life

    Battery Life is OK, the 8000mAh battery can't do miracles in handling such a beefy Chipset and Screen, and the PCMark Battery Life test confirms it (lowest brightness, WiFi on, Sync on).


    7hrs2Lch.png
    u0CUuaLh.png
    tgsQkk0h.png
    xkYwA2ah.png



    It can be probably improved, but not that much. The Helio X20 chipset is known to be a bit power-hungry.

    Something i am not really okay with is the time required to charge the battery. For some reason, even though the Helio X20 chipset supports it, they have not chosen to not enable it, thus you need to wait over 4 hours for a fully charge.


    Software

    Software-wise i must say that i am impressed with CHUWI's work. This Hi9 Air runs on Android Oreo 8.0 with Project Treble support (but not Google Certified!), but other than that, it is 100% clean, with no bloatware or custom apps unlike most Chinese tablets.

    The beefy screen resolution is noticeable though while scrolling menus or switching between apps. There is a noticeable lack of smoothness, but it doesn't stutter. Some extra GPU power would have solved this.


    C4bNotzh.png
    J2SWZwGh.png


    OfqcERWh.png
    mYbq7Lgh.png


    5wAdwD0h.png
    E3YHQZXh.png


    D2GnfdIh.png



    Benchmarks

    For all benchmark lovers, here you can taste some runs ;)

    Confirming what i have already said before, the GPU power is slightly lacking, but CPU performance can match last-year flagships.


    LrtYlvyh.png
    NegutCQh.png


    rFcMGmph.png


    N8KBGJ6h.png
    xLFg1z8h.png


    xSJ3dkDh.png
    Puw249Rh.png


    p4S0qb3h.png
    lsKcSG8h.png


    UgHxF3Ch.png
    38GDarMh.png


    q7umpLKh.png
    xwUIzVXh.png



    Conclusions

    What to say about this tablet...it is great but doesn't lack its flaws. Build quality is excellent, the design is pretty good, the screen is awesome and the software is clean. With a few tweaks, it should be possible to make this tablet excellent, except for the 4G antenna that, well, is hardware related.

    Do i recommend it? It depends on what you are looking for and, most important, the possible deal you can find online. If you need a tablet that is able to take great photos, avoid it, otherwise, you can consider it. I will be working on it for dev. and try to squeeze the most out of it.

    Pros:

    Impressive screen quality
    Excellent build quality
    Nice design even if a bit outdated
    Clean software with Treble Support
    WiFi AC support and great GPS signal reception

    Cons:

    Lack of GPU performance for such high resolution
    Limited Screen brightness
    Still Micro-USB and no Quick Charging
    Disappointing 4G signal quality
    Barely usable front-facing camera (and the rear one is not that better)


    Rating: 8.3

    Packaging and Accessories: 7.5
    Design and Materials: 9.5
    Performance and Heat Dissipation: 8
    Screen: 9
    Camera: 5
    Sound: 8
    Battery Life: 8.5
    Software: 10
    OEM Support: ?
    Price: 9


    You can find full-res images (I know, Quality isn't excellent) here: https://imgur.com/a/MH6kEeJ

    Official Website: https://en.chuwi.com/product/items/Chuwi-Hi9-Air.html

    You can buy it on many online shops. Official, and authorized, Retailers are listed in the CHUWI website.