Alldocube X Neo

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
I'll look through your screenshots & see what can be added or help improve the guide.

Generally speaking, I'm glad that my struggles (many hours of anger & angst) have helped many. My original intent was to document everything I went through & add what people had discovered with my guide.
It certainly helped me (y)
But I can't help but find it curious that I run into issues at practically every turn. Did other run into the same ones and just powered through without comment or am I truly that unlucky?
Some of the ROM images do that but can still be bootable. You'll have to test them out.
Sadly thats a no. Neither caos nor crdrom boot. I tried flashing from TWRP as well (A -reboot- B).
Maybe I'll have to try https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/
But no one reported any trouble flashing in this thread so why should it be necessary?

Maybe I should try one of the confirmed-to-work roms first.
Once you flash any system image, expanding the system partition is highly recommended in order to flash any TWRP-based ZIPs like gapps.
You mean wipe/advanced/repair+change/resize file system on /system?

I'll have to update it with the last released Chinese firmware version, too. I've just been lazy about doing so.
There is a more recent one? https://www.51cube.com/firmware/t1009-firmware/ still has the "XNeo(T1009)-Android9.0-201028-固件及教程" but I might have missed something due to not being able to read chinese :d
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
It certainly helped me (y)
But I can't help but find it curious that I run into issues at practically every turn. Did other run into the same ones and just powered through without comment or am I truly that unlucky?
I had many issues, so you're going down a similar path. Luckily, you have the guide & tools at your disposal without having to scour the web.

Sadly thats a no. Neither caos nor crdrom boot. I tried flashing from TWRP as well (A -reboot- B).
Maybe I'll have to try https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/
But no one reported any trouble flashing in this thread so why should it be necessary?
I don't think that tool works. I tried a bunch with no dice.

Maybe I should try one of the confirmed-to-work roms first.
Yes, stick with the tried & true.

You mean wipe/advanced/repair+change/resize file system on /system?
Yes

There is a more recent one? https://www.51cube.com/firmware/t1009-firmware/ still has the "XNeo(T1009)-Android9.0-201028-固件及教程" but I might have missed something due to not being able to read chinese :d
Yep. I'm not sure if its on my MEGA drive or not though. If you see one with Qucii, that's the newest one. If not, I'll upload it & update the guide with new links & file names.
 

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
I had many issues, so you're going down a similar path. Luckily, you have the guide & tools at your disposal without having to scour the web.
True. Without that I'd have thrown in the towel by now.
Yep. I'm not sure if its on my MEGA drive or not though. If you see one with Qucii, that's the newest one. If not, I'll upload it & update the guide with new links & file names.
201028 is there and the one I used for everything. Not sure what Qucii is.

Flashing qidroid 224 gives no error during flash. But does not boot either.
(Your device is corrupt, blah)

So maybe that wasn't even the issue. Maybe my fastboot driver did not work?
I don't have that much to choose from though and stuff like getvar device and reboot works.
samsung adb.png


Also I can flash from TWRP and that shouldn't matter there. Hm...

Code:
FLASHING qidroid-v224-201021-arm64-bvN.img


E:\2106AllDCube\platform-tools>fastboot flash system_a "..\qidroid-v224-201021-arm64-bvN.img"
Sending sparse 'system_a' 1/4 (524284 KB)          OKAY [ 11.675s]
Writing 'system_a'                                 OKAY [  0.001s]
Sending sparse 'system_a' 2/4 (524284 KB)          OKAY [ 11.833s]
Writing 'system_a'                                 OKAY [  0.000s]
Sending sparse 'system_a' 3/4 (524284 KB)          OKAY [ 11.841s]
Writing 'system_a'                                 OKAY [  0.000s]
Sending sparse 'system_a' 4/4 (359324 KB)          OKAY [  8.286s]
Writing 'system_a'                                 OKAY [  0.002s]
Finished. Total time: 43.692s

E:\2106AllDCube\platform-tools>fastboot flash system_b "..\qidroid-v224-201021-arm64-bvN.img"
Sending sparse 'system_b' 1/4 (524284 KB)          OKAY [ 11.630s]
Writing 'system_b'                                 OKAY [  0.001s]
Sending sparse 'system_b' 2/4 (524284 KB)          OKAY [ 11.852s]
Writing 'system_b'                                 OKAY [  0.000s]
Sending sparse 'system_b' 3/4 (524284 KB)          OKAY [ 11.812s]
Writing 'system_b'                                 OKAY [  0.000s]
Sending sparse 'system_b' 4/4 (359324 KB)          OKAY [  8.245s]
Writing 'system_b'                                 OKAY [  0.000s]
Finished. Total time: 46.234s

E:\2106AllDCube\platform-tools>fastboot -w
Erasing 'userdata'                                 OKAY [  0.303s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 12990459 4k blocks and 3252224 inodes
Filesystem UUID: 34643f7e-efb3-11eb-806e-d785ed472177
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'userdata' (316 KB)                        OKAY [  0.015s]
Writing 'userdata'                                 OKAY [  0.000s]
Finished. Total time: 3.355s

E:\2106AllDCube\platform-tools>fastboot reboot
Rebooting                                          OKAY [  0.001s]
Finished. Total time: 0.007s


Update:
I formated dalik system data cache and flashed qidroid-v224 from TWRP.
Now I cannot go anywhere but FastBoot Mode. Button presses/Fastboot Mode Options (like Boot to FFBM or QMMI)/Fastboot reboot recovery via console.
Nothing gets me anywhere else. Back to QFIL and step 1 it is. Flashing now ^^

Any idea where I might have screwed up?
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
Use Magisk in TWRP to get it to boot.

Use the newest TWRP file & boot to it with fastboot boot <filename>
 

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
Use Magisk in TWRP to get it to boot.

Use the newest TWRP file & boot to it with fastboot boot <filename>
Sorry I was perhaps not clear here. I already did the QFIL procedure and am back to flashing roms, leading to
'Your device is corrupt. It cant be trusted'.

Thanks for your prompt assistance!
But I need a break :(
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
Sorry I was perhaps not clear here. I already did the QFIL procedure and am back to flashing roms, leading to
'Your device is corrupt. It cant be trusted'.

Thanks for your prompt assistance!
But I need a break :(
Magisk needs to be reapplied every time you clear the user data with "fastboot -w" or in TWRP. Thus needing to be in TWRP with Magisk fully installed before booting again.
 
Last edited:

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
Magisk needs to be reapplied every time you clear the user data with "fastboot -w" or in TWRP. Thus needing to be in TWRP with Magisk fully installed before booting again.

I wasn't aware Magisk is mandatory?
The guides TWRP section point 6. states "Magisk **can** be flashed. Since this is a Treble device, both slots A & B need to be flashed."
That might be something to clarify then.

And since it apparently does not work without - whats the proper order here?

Code:
Slot A: flash ROM to system
Slot A: flash Magisk zip
switch to Slot B + reboot recovery
Slot B: flash ROM to system
Slot B: flash Magisk zip
switch to Slot A + reboot system

Does not currently work for me. Seeing as QFIL flashing the chinese rom gets me 'device corrupt' errors too there might be another issue though.

Do I perhaps need to start over from the beginning once I get a 'device corrupted'? Instead of going into recovery to (re)flash something I mean?


Use the newest TWRP file & boot to it with fastboot boot <filename>
I use:
Code:
set TWRP=TWRP-CUBE_X_Neo-20201028.img
platform-tools\fastboot flash boot_a "%TWRP%"
platform-tools\fastboot flash boot_b "%TWRP%"
platform-tools\fastboot reboot "%TWRP%"

Flashing A/B works. Then I get "fastboot: usage: unknown reboot target TWRP-CUBE_X_Neo-20201028.img"

fastboot reboot recovery does not work either. Using the bootloaders 'recovery mode' does work.



Is it possible to flash without TWRP? I find the slot switching cumbersome compared to console commands...

Theoretically something like
Code:
set TWRP=TWRP-CUBE_X_Neo-20201028.img
set ROMFILENAME=qidroid-v224-201021-arm64-bvN.img

fastboot flash system_a "..\%ROMFILENAME%"
fastboot flash system_b "..\%ROMFILENAME%"
fastboot -w
fastboot flash boot_a "..\%TWRP%"
fastboot flash boot_b "..\%TWRP%"
fastboot reboot recovery

Then activating adb and installing Magisk via adb install ..\Magisk-ef9d077c-phh.zip

Should work, no? (But currently doesn't for me)

I feel it should be easier to share scripts for debugging than compare fuzzy directions about buttons to be pressed in a certain order.
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
I wasn't aware Magisk is mandatory?
The guides TWRP section point 6. states "Magisk **can** be flashed. Since this is a Treble device, both slots A & B need to be flashed."
That might be something to clarify then.

Some ROMs cause this issue. The other way is clearing the vbmeta partition. Magisk isn't mandatory but really helps.

And since it apparently does not work without - whats the proper order here?

Code:
Slot A: flash ROM to system
Slot A: flash Magisk zip
switch to Slot B + reboot recovery
Slot B: flash ROM to system
Slot B: flash Magisk zip
switch to Slot A + reboot system

Does not currently work for me. Seeing as QFIL flashing the chinese rom gets me 'device corrupt' errors too there might be another issue though.

When flashing from slot A, it's flashing to slot B & vice versa.

Try this & see if you get anywhere.
Code:
Slot A: flash ROM to system B
switch to Slot B + reboot recovery
Slot B: flash ROM to system A
Slot B: flash Magisk zip to boot A
switch to Slot A + reboot recovery
Slot A: flash Magisk zip to boot B
Reboot system

Do I perhaps need to start over from the beginning once I get a 'device corrupted'? Instead of going into recovery to (re)flash something I mean?

I use:
Code:
set TWRP=TWRP-CUBE_X_Neo-20201028.img
platform-tools\fastboot flash boot_a "%TWRP%"
platform-tools\fastboot flash boot_b "%TWRP%"
platform-tools\fastboot reboot "%TWRP%"

Flashing A/B works. Then I get "fastboot: usage: unknown reboot target TWRP-CUBE_X_Neo-20201028.img"

fastboot reboot recovery does not work either. Using the bootloaders 'recovery mode' does work.

Try the following:
Code:
set TWRP=TWRP-CUBE_X_Neo-20201028.img
platform-tools\fastboot flash boot_a "%TWRP%"
platform-tools\fastboot flash boot_b "%TWRP%"
platform-tools\fastboot boot "%TWRP%"

"fastboot help" should show you all of the commands available.

Is it possible to flash without TWRP? I find the slot switching cumbersome compared to console commands...

Theoretically something like
Code:
set TWRP=TWRP-CUBE_X_Neo-20201028.img
set ROMFILENAME=qidroid-v224-201021-arm64-bvN.img

fastboot flash system_a "..\%ROMFILENAME%"
fastboot flash system_b "..\%ROMFILENAME%"
fastboot -w
fastboot flash boot_a "..\%TWRP%"
fastboot flash boot_b "..\%TWRP%"
fastboot reboot recovery

Then activating adb and installing Magisk via adb install ..\Magisk-ef9d077c-phh.zip

Should work, no? (But currently doesn't for me)

I feel it should be easier to share scripts for debugging than compare fuzzy directions about buttons to be pressed in a certain order.

I personally prefer fastboot flashing over TWRP but when it's a ZIP you need to use it instead.

adb install won't work with it due to needing recovery root privileges or a superuser method while in the booted OS like the Magisk Manager with root already installed.

Yes, scripting with fastboot can work wonders. I'm fine with adding more command line steps to the guide if that will help.
 

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
Some ROMs cause this issue. The other way is clearing the vbmeta partition. Magisk isn't mandatory but really helps.
TWRP does not show that one?

I've got:
Dalvik/Art Cache
System
Vendor
Data
Internal Storage
Micro SD Card
USB OTG

From what google tells me not every device has one. There is also this:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.bin

Should I perhaps have flashed my rom with that?

Btw - should I wipe Data/cache/Dalvik when flashing from TWRP?

When flashing from slot A, it's flashing to slot B & vice versa.

Try this & see if you get anywhere.
Code:
Slot A: flash ROM to system B
switch to Slot B + reboot recovery
Slot B: flash ROM to system A
Slot B: flash Magisk zip to boot A
switch to Slot A + reboot recovery
Slot A: flash Magisk zip to boot B
Reboot system

Will try. But what's the thinking here?
No matter which slot gets flashed first as long as I switch I'll have flashed both, no?
.IMG roms get flashed as 'System Image'. So they shouldn't even touch boot and it therefore shouldn't matter if I flash Magisk first or last?

This is confusing.

Edit: Did not work. But again I feel I might have a deeper issue. When using QFIL to flash the original chinese rom I now also get a 'your device is corrupt, ...' boot-loop.
On the other hand I shouldn't need to have to reflash that every time right?

Try the following:
Code:
set TWRP=TWRP-CUBE_X_Neo-20201028.img
platform-tools\fastboot flash boot_a "%TWRP%"
platform-tools\fastboot flash boot_b "%TWRP%"
platform-tools\fastboot boot "%TWRP%"

"fastboot help" should show you all of the commands available.
My bad! I read 'boot' and every time substitute *RE*boot in my mind :(

Code:
E:\2106AllDCube>set TWRP=TWRP-CUBE_X_Neo-20201028.img

E:\2106AllDCube>platform-tools\fastboot flash boot_a "%TWRP%"
Sending 'boot_a' (65536 KB)                        OKAY [  1.449s]
Writing 'boot_a'                                   OKAY [  0.460s]
Finished. Total time: 2.490s

E:\2106AllDCube>platform-tools\fastboot flash boot_b "%TWRP%"
Sending 'boot_b' (65536 KB)                        OKAY [  1.442s]
Writing 'boot_b'                                   OKAY [  0.465s]
Finished. Total time: 2.447s

E:\2106AllDCube>platform-tools\fastboot boot "%TWRP%"
Sending 'boot.img' (65536 KB)                      OKAY [  1.402s]
Booting                                            FAILED (remote: 'unknown command')
fastboot: error: Command failed

E:\2106AllDCube>platform-tools\fastboot boot %TWRP%
Sending 'boot.img' (65536 KB)                      OKAY [  1.403s]
Booting                                            FAILED (remote: 'unknown command')
fastboot: error: Command failed

E:\2106AllDCube>platform-tools\fastboot boot TWRP-CUBE_X_Neo-20201028.img
Sending 'boot.img' (65536 KB)                      OKAY [  1.405s]
Booting                                            FAILED (remote: 'unknown command')
fastboot: error: Command failed

E:\2106AllDCube>platform-tools\fastboot --version
fastboot version 31.0.3-7562133
Installed as E:\2106AllDCube\platform-tools\fastboot.exe

So that does upload the TWRP image but then fails?

I personally prefer fastboot flashing over TWRP but when it's a ZIP you need to use it instead.

adb install won't work with it due to needing recovery root privileges or a superuser method while in the booted OS like the Magisk Manager with root already installed.
That explains that. Thanks!

Yes, scripting with fastboot can work wonders. I'm fine with adding more command line steps to the guide if that will help.
Will for some I imagine.

To verify: the "Upgrade base firmware to newest version (for GSI-based ROMs)" part of the guide is not relevant in my case. It's for upgrading the underlying firmware (=non treble part) when/if a new one comes out. Right?

I note I get E:Unable to decrypt FBE device on ROM flash in twrp sometimes.
Just now it worked without error on slot A but errored on slot B (before Magisk). If I reflash without reboot there is no more error though. Just the first time. To clarify: Everything else seems to be the same: [IMAGE FLASH COMPLETED]/Image Flashed Successful. Sadly there is not a lot of information when flashing.
Edit: This actually is already in the log BEFORE I flash. Next line reads "Updating partition details..."
 
Last edited:
Joined
Jul 30, 2021
Messages
2
I just got this tablet and love it, the screen is fantastic (reminds me of my Google Pixel laptop), its light and fast, and I thought I'd chime in about something I noticed.

Thanks to the tutorial flashing was easy, I followed it and flashed but noticed something with the WiFi. I flashed in this order using fastboot, using TWRP to flash anything other than gapps and magisk phh failed.

1) Chinese rom to unlock bootloader as per tutorial
2) flashed TWRP
3) flashed GSI rom https://sourceforge.net/projects/an...3-UNOFFICIAL-treble_arm64_bvS.img.xz/download (i dont think ive seen much comments on using lineage 18x here).
4) flashed the Magisk phh from the mega repo.
5) wipe-advanced-resize system partition, then rebooted (it says this failed in TWRP but after a reboot I had 500mb free)
6) flashed nano gapps from https://opengapps.org/
7) reflashed boot.img from the chinese ROM to get rid of TWRP so that WiFi would work again
8) to get superuser working i downloaded https://www.cyanogenmods.org/downloads/phh-superuser-android-11/ (as i already applied the patched magisk from the repo, all i needed was the sprusr.apk from the zip file, do not try to apply the entire patch again), just install this apk in android.

If you notice, step 7 is where I had a lot of problems, as long as I have TWRP installed WiFi either does not work at all (wont turn on, no device shows up) or turns on then disappears at reboot. So I reflashed from step 0 again, had the same problem with a different android 10 GSI rom. I have some experience with ARM linux and uboot and it reminded me that maybe there was a bootloader problem, that's when I realised that the recovery = boot, and found that the boot.img from the chinese rom gives me working 2.4 and 5ghz wifi in Lineage 18.1.

Also, I had bluetooth headphones that were crashing the bluetooth demon and had to perform a reset using the boot.img from the chinese rom after I had installed my GSI rom, and then the headphones we working. This is because as far as I can tell, hd audio is disabled in the chinese rom and if you try to upgrade saving your settings, bluetooth is screwed up. I guess its standard to perform a system reset when upgrading/changing roms, but TWRP just didnt clear the rom properly for me.

I'm using OpenWRT and an older MR16 AP and signal strength is ok/good even in the far corners of my house, only 64Mbps speed though :(.

I have not tried the headphones jack but as soon as I find some headphones I will.

That being said, Crimson thanks for the tutorial, i would have never thought of using the chinese firmware had you not made that great tutorial and repo.

Is anyone else using Lineage 18.x on the Alldocube X neo? I havent found any bugs yet really, I just really wish I had multiwindow/tablet mode like the ASOP based roms i used years ago had, does anyone know if there is a GSI rom with this or a way to mod it to add that?

For me the biggest reason for trying to use a Android 11 GSI rom is that the performance is significantly better in the graphics/UI speed and laggyness compared to 10 and especially compared to the very laggy graphics performance of the stock 9. Its amazing how smooth 11 is on it, but I still feel it could be a bit better, as my phone is also a Qualcomm and I find the graphics drivers Motorola has perform better using nearly identical GPU's.
 
Last edited:
Joined
Jul 30, 2021
Messages
2
Oh wow, lineageos 18 has split screen, I just didnt know you had to hold the apps icon in the recent apps view to be able to select multiwindow!

Also, on lineageos 18 my 3.5mm headphones are working fine with just these options checked.

1627708437785.png

I'm trying to get the FM Radio (FM2.apk) working from the chinese rom now. Didnt have luck with that, so I tried FM Radio 11.apk that the LineageOS team realesed, after fixing a bunch of missing .so libraries, I'm now stuck at
07-31 02:59:04.19 17947 17947 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "vendor.qti.hardware.btconfigstore@1.0.so" not found: needed by /system/lib64/libbtconfigstore.so in namespace classloader-namespace-shared
even though the vendor.qti.hardware.btconfigstore@1.0.so library is in the /product/lib64 folder, etc..

seems that vendor.qti.hardware.btconfigstore is a package that ships with qualcomm snapdragon phones and is used by the FM Radio App.

No big deal if i cant get fm radio working...
 

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
I apologize for not answering questions for the last 2 posts...

The guide has been updated with the last Chinese firmware released.

No worries. My system works now :)
Well somewhat. I installed lineage-18.x/lineage-18.1-20210713-UNOFFICIAL-treble_arm64_bvS since that seemed to work for randysbytes.
So far GPS doesn't work, Magisk is wonky in what packets don't fail to install, auto-orientation is spotty as well. I'd try something else but I'm apprehensive when thinking about going through the process again ^^

Anyhow. What do I think solved my problem?
Fastboot flashing a rom, going to recovery first thing after, 'format data' (NOT the standard wipe),
installing magisk and doing a standard cache/data/dalvik wipe (for both A and B).
If the 'your device is untrustworthy' message shows up it's probably time to start over.
Going back to QFIL flashing is NOT necessary.

I did other stuff but I don't think any of it helped. In case I'm wrong, here's the list:
- fastboot lock/unlock / lock_critical / unlock_critical
- made sure ADB drivers by google are used (instead of the samsung ones I had installed for my phone)
- fastboot erase system (a+b) and install rom
- fastboot erase boot (a+b) and install TWRP
- install magisk

If I get fed up/curious enough I'll give another rom a go sometime next week. We'll see.


Here's some things you might add to the guide.

----------------------------------------------
EMMC or UFS - which do I choose?
Boot into bootloader and take note of the VARIANT row. Eg:
PRODUCT_NAME - sdm660
**VARIANT - SDM EMMC***
BOOTLOADER VERSION -
...
DEVICE STATE - unlocked

(I only know what my emmc device looks like - if you have an ufs one please post in the hardforum so this can be amended)
The last line is of note as well to see if you correctly unlocked the device.

----------------------------------------------
Stuck with fastboot? Nowhere else to go?
This is a known problem on Qualcomm devices with chinese TWRP and non-chinese roms.
Doing a factory reset (or fastboot -w or flash (un)lock) on a non-stock (like TWRP) image can also lead to this.
Faily easy to fix just reinstall TWRP via fastboot like so:

fastboot flash boot --slot all TWRP-CUBE_X_Neo-20201216.img

then *shutdown* the device and reboot.



In any event - THANK YOU for your work in making this guide and helping me with my troubles!
 

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
It seems that Alldocube has ended software-support for the X Neo but not the sellings. :)
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
AmberKnave I'll look through all of your posts & see what I can improve with the guide. Having clearer information will definitely help anyone new to it.

Also, qiDroid is the best Android 10 GSI ROM IMHO. The main headache is the WiFi being stuck at 2.4GHz, which I haven't been able to resolve despite many tips/fixes/workarounds in this thread.

taro4 ALLDOCUBE appears to have realized that it may sell well but there are many problems with design choices. They're probably moving forward with many other designs & seeing what sticks to the wall. I'm sad we all got bamboozled for what appeared to be amazing but wound up being mediocre (at least in my opinion).
 

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
CrimsonKnight13 Anyway, I think it's good that new people are still coming to the forum here. Before I bought my X Neo almost a year ago, I knew that Alldocube would probably not bring updates. But it had a very good price-performance ratio and (most important purchase reason for me) it was possible to flash custom roms (mostly your merit).
 

AmberKnave

n00b
Joined
Jul 27, 2021
Messages
14
AmberKnave I'll look through all of your posts & see what I can improve with the guide. Having clearer information will definitely help anyone new to it. Also, qiDroid is the best Android 10 GSI ROM IMHO. The main headache is the WiFi being stuck at 2.4GHz, which I haven't been able to resolve despite many tips/fixes/workarounds in this thread.

Here's my ROM breakdown so far (keep in mind that I don't have/use 5Ghz because my provider's router is too old):

Did not boot:
qidroid-v224-201021-arm64-bvN
crdrom-v308-210521-arm64-bvZ
caos-v310-210721-arm64-bgZ

Boots. And works with some problems:
lineage-18.1-20210713-UNOFFICIAL-treble_arm64_bvS
(auto-rotation is wonky and gps doesn't work (well))

Works:
Corvus_v16.6-Paradox-treble_arm64_ab_vndklite-12072021-Beta-Official-0800
(gps is poor too, magisk fix here, otherwise it works well.)

I kinda like corvus so far and auto rotation works with it where it didn't reliably in lineage. GPS is very poor too but I think this is my fault for not adjusting ntp servers and/or not having the google location framework installed.
There's more trial and error to come on this.

Generally it seems that sensors don't work well out of the box but unfortunately I didn't do the same tests on stock so I can't compare fairly. Does this thing even have a compass?
GPS test takes ages to get satellites and gets no fix within half an hour.

taro4 ALLDOCUBE appears to have realized that it may sell well but there are many problems with design choices. They're probably moving forward with many other designs & seeing what sticks to the wall. I'm sad we all got bamboozled for what appeared to be amazing but wound up being mediocre (at least in my opinion).

Yeah without treble and your guide I wouldn't have bought it. The AMOLED screen did entice me but not enough to get a device that's got no support.

Main gripe I have is the bad battery consumption. I figured that using a modern chipset with an amoled screen would give me lots of sot when reading books.
Unfortunately that's not so. Compared to my old Note 10.1 2014 its worse. Smaller battery and worse power draw. Where I optimized my old tablet down to 290-310 mA consumption this one I didn't get past 450 no matter what.
(Data collected with AccuBattery. Might not be completely accurate but it's comparable and credible in comparison when looking at percentage loss per hour)

Using kernel adiutor from f-droid to adjust governors helps but I've yet to figure out if I can undervolt, disable big cores or even decrease frequency (little cores only go down to 600 something Mhz). Reading basically equals lowest cpu/gpu usage possible so playing around with governors only does so much.
If anyone has information to share on this, please let me know!
 
Last edited:

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
Here's my ROM breakdown so far (keep in mind that I don't have/use 5Ghz because my provider's router is too old):

Did not boot:
qidroid-v224-201021-arm64-bvN
crdrom-v308-210521-arm64-bvZ
Did all boot here (I'm always flashing with TWRP). Currently on crdrom with Magisk and Niks Gapps and still satisfied (without 5GHz, but I don't miss it).

GPS is very poor too but I think this is my fault for not adjusting ntp servers and/or not having the google location framework installed.
There's more trial and error to come on this.

Generally it seems that sensors don't work well out of the box but unfortunately I didn't do the same tests on stock so I can't compare fairly. Does this thing even have a compass?
GPS test takes ages to get satellites and gets no fix within half an hour.
There is a Magisk module to speed up GPS, but I never tried it. Unfortunately no compass at all. Proximity sensor depends on the rom.

But I never had difficulties with autorotation and also no complaints about battery consumption, usually lasts all day like the tablets I used before (dark mode enabled).

Btw., I didn't read all of your posts completely :) but I think there is a high chance that many of your problems were discussed in the last months of 2020 here in this thread.
 

jo92346

n00b
Joined
Aug 22, 2021
Messages
5
hi guys.
I tried everything in the guide, read all that thread again and again.
All I achieved was the corrupt screen or barely usable android.

Is there any way to root in the chinese rom and simply revert to the global one?
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
hi guys.
I tried everything in the guide, read all that thread again and again.
All I achieved was the corrupt screen or barely usable android.

Is there any way to root in the chinese rom and simply revert to the global one?
You'll need provide a lot more details. 🤔
 

jo92346

n00b
Joined
Aug 22, 2021
Messages
5
Base Firmware Flashing (QFIL EMMC version):done. all is OK.
Bootloader Unlocking–Modified from Source: done. all is OK.
TWRP: done; all is OK.

Then I tried the next steps in different order (after redoing the first basic 3 steps)
Upgrade base firmware to newest version(for GSI-based ROMs) then Flashing GSI ROMs(by fawkesyeah)
or
Upgrade base firmware to newest version(for GSI-based ROMs) then Flashing anything inside TWRP(byfawkesyeah):
or reverting those steps:

I always Get a corrupt screen whatever the rom. Some booted after that but I wasn't happy with any of them: too many issues. Some didn't boot and sent me right back to the corrupt screen.

In the end i don't really care for android 10 or 11 for my usage, but I'd really like the global rom to be rooted.
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
Base Firmware Flashing (QFIL EMMC version):done. all is OK.
Bootloader Unlocking–Modified from Source: done. all is OK.
TWRP: done; all is OK.

Then I tried the next steps in different order (after redoing the first basic 3 steps)
Upgrade base firmware to newest version(for GSI-based ROMs) then Flashing GSI ROMs(by fawkesyeah)
or
Upgrade base firmware to newest version(for GSI-based ROMs) then Flashing anything inside TWRP(byfawkesyeah):
or reverting those steps:

I always Get a corrupt screen whatever the rom. Some booted after that but I wasn't happy with any of them: too many issues. Some didn't boot and sent me right back to the corrupt screen.

In the end i don't really care for android 10 or 11 for my usage, but I'd really like the global rom to be rooted.
You'll need to use Magisk to get past the boot corruption with some ROMs. Also, the global ROM can't be rooted, which IF you read this whole thread, you would have seen that mentioned multiple times.
 

jo92346

n00b
Joined
Aug 22, 2021
Messages
5
forgot to say I tried magisk too, (pph or 20.4 as mentionned in this thread. I tried before flashing GSI, after, and before and after) : didn't change anything.

I've seen the global rom can't be rooted, but I was naively thinking there was maybe a way to flash it as a custom rom after using the chinese one to unlock. (maybe with a custom rawprogram_unsparse.xml like in the step "Upgrade base firmware to newest version(for GSI-based ROMs)" )

I've read all that thread many times. been on that for the last few days.
 
Last edited:

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
Base Firmware Flashing (QFIL EMMC version):done. all is OK.
Bootloader Unlocking–Modified from Source: done. all is OK.
TWRP: done; all is OK.
Base firmware means chinese rom 20200522? After TWRP works you can try wipe all incl. format data partition. And did you flash all roms incl. Magisk to both sloths (flash rom and Magisk, change slot, reboot TWRP, flash rom and Magisk)? Any error messages while flashing?

Then I tried the next steps in different order (after redoing the first basic 3 steps)
Upgrade base firmware to newest version(for GSI-based ROMs) then Flashing GSI ROMs(by fawkesyeah)
or
Upgrade base firmware to newest version(for GSI-based ROMs) then Flashing anything inside TWRP(byfawkesyeah):
or reverting those steps:

I always Get a corrupt screen whatever the rom. Some booted after that but I wasn't happy with any of them: too many issues. Some didn't boot and sent me right back to the corrupt screen.

In the end i don't really care for android 10 or 11 for my usage, but I'd really like the global rom to be rooted.
The max size of our system partition is 3069 MB, so some roms may be bigger and don't work. But if you always get a corrupt screen, there should be something wrong with your base system - I don't think this depends on the GSI-roms. If you have a working TWRP I would not try with different Alldocube firmware-updates etc. but flash the GSI-Rom and Magisk directly afterwards. You can still update firmware later.

Means:
- flash chinese rom 20200522 with QFIL
- unlock bootloader
- flash TWRP (20200522)
- in TWRP wipe all and
- flash GSI and Magisk to both slots

I recommend qidroid (10) or crdrom (11), both worked fine on my X Neo (except 5 GHz Wifi of course).
 
Last edited:

jo92346

n00b
Joined
Aug 22, 2021
Messages
5
Base firmware means chinese rom 20200522? After TWRP works you can try wipe all incl. format data partition. And did you flash all roms incl. Magisk to both sloths (flash rom and Magisk, change slot, reboot TWRP, flash rom and Magisk)? Any error messages while flashing?
I followed the guide: so base firmware was chinese 20201216, flashing A and B like explained in the guide. Got no error message.
Wipe in TWRP didn't change anything.

The max size of our system partition is 3069 MB, so some roms may be bigger and don't work. But if you always get a corrupt screen, there should be something wrong with your base system - I don't think this depends on the GSI-roms. If you have a working TWRP I would not try with different Alldocube firmware-updates etc. but flash the GSI-Rom and Magisk directly afterwards. You can still update firmware later.

Means:
- flash chinese rom 20200522 with QFIL
- unlock bootloader
- flash TWRP (20200522)
- in TWRP wipe all and
- flash GSI and Magisk to both slots

I recommend qidroid (10) or crdrom (11), both worked fine on my X Neo (except 5 GHz Wifi of course).
I didn't try with 20200522: I'm going to give it a try with qidroid-v224-201021-arm64-bvN following your instructions.
 

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
I followed the guide: so base firmware was chinese 20201216, flashing A and B like explained in the guide. Got no error message.
Wipe in TWRP didn't change anything.


I didn't try with 20200522: I'm going to give it a try with qidroid-v224-201021-arm64-bvN following your instructions.
My list with 20200522 describes my approach in the last year, which worked 100%. I used the newer chinese firmwares for updates only (with rawprogram_unsparse_mod.xml, which does not overwrite the system-partition). TWRP version and firmware version should be the same, because TWRP is based in the boot-partition and includes parts of the firmware.

It could be that the base flashing does not work with the newer chinese firmwares, at least i don't remember reading about it here. CrimsonKnight13 Was there any positive feedback that base flashing works with the newer chinese firmwares too or did you test it by yourself?
 
Last edited:

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
8,244
My list with 20200522 describes my approach in the last year, which worked 100%. I used the newer chinese firmwares for updates only (with rawprogram_unsparse_mod.xml, which does not overwrite the system-partition). TWRP version and firmware version should be the same, because TWRP is based in the boot-partition and includes parts of the firmware.

It could be that the base flashing does not work with the newer chinese firmwares, at least i don't remember reading about it here. CrimsonKnight13 Was there any positive feedback that base flashing works with the newer chinese firmwares too or did you test it by yourself?
I'm using the newest version, so if anyone has issues they need to explain in full detail what is wrong. I do believe that others have utilized the newest version as well.
 

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
I'm using the newest version, so if anyone has issues they need to explain in full detail what is wrong. I do believe that others have utilized the newest version as well.
That does not exactly answer my question. :) I'm also using the newest version, but my base flashing was with 20200522 and both newer versions were flashed with rawprogram_unsparse_mod.xml. Because jo92346 has some problems, I was wondering if the base flashing with the newer versions really works.
 

jo92346

n00b
Joined
Aug 22, 2021
Messages
5
That does not exactly answer my question. :) I'm also using the newest version, but my base flashing was with 20200522 and both newer versions were flashed with rawprogram_unsparse_mod.xml. Because jo92346 has some problems, I was wondering if the base flashing with the newer versions really works.
It worked with 2020522. No corrupt screen.
is it possible there is some small difference in hardware with newer tablets?
 

taro4

Limp Gawd
Joined
Sep 7, 2020
Messages
128
Okay, crdrom-v313-210921-arm64-bgZ.img with a size of more than 3100 MB is too big for our system partition (3069 MB).

After flashing crdrom-v313-210921-arm64-bvZ.img and resizing the file system of the system partition I had 569 MB free. Since there is now finally also a Android 11 version of opengapps, I wanted to flash open_gapps-arm64-11.0-nano-20210924.zip, but it failed with a space-error. Same with NikGapps-basic-arm64-11-20210918-signed.zip. Only NikGapps-basic-arm64-11-20210130-signed.zip worked like with the former build of crDRom. The archive of this older build of NikGapps is 5MB bigger than the newest - do i need to understand this? o_O
 
Last edited:

PiotrekJ

n00b
Joined
Sep 23, 2021
Messages
2
Okay, crdrom-v313-210921-arm64-bgZ.img with a size of more than 3100 MB is too big for our system partition (3069 MB).

After flashing crdrom-v313-210921-arm64-bvZ.img and resizing the file system of the system partition I had 569 MB free. Since there is now finally also a Android 11 version of opengapps, I wanted to flash open_gapps-arm64-11.0-nano-20210924.zip, but it failed with a space-error. Same with NikGapps-basic-arm64-11-20210918-signed.zip. Only NikGapps-basic-arm64-11-20210130-signed.zip worked like with the former build of crDRom. The archive of this older build of NikGapps is 5MB bigger than the newest - do i need to understand this? o_O
That is why I installed pico gapps.
 
Joined
Jul 21, 2020
Messages
42
I flashed crdrom-v313-210921-arm64-bvZ.img.xz because the bvZ version is too big for our system partition.
I don't know why but the only version of NikGapps that I've been able to flash is NikGapps-core-arm64-11-20210130-signed.zip. It's not a big deal because after booting the core gapps are updated in the background.
 

bazito

n00b
Joined
May 9, 2021
Messages
19
Hi friends. I have a problem with the tablet. I wanted to update the rom and something probably went wrong. When you turn on the tablet, the system does not start, but twrp opens. I tried falsh from cmd and twrp.
 
Top