Alldocube X Neo

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,374
Okay, but how can TWRP corrupt the device? I flashed my tablet with new TWRP without problems.

Btw., here is an explanation for the boot error with g.co/ABH. Based on the red colour in the above picture this is a dm-verity corruption. Anyone familar with this? :)
Yes, that's the main reason for why I keep recommending using Magisk since it allows the kernel to boot to a custom ROM.

Installation:Magisk and MagiskHide Installation and Troubleshooting guide (didgeridoohan.com)

The other way around this is to use Universal DM-Verity, ForceEncrypt, Disk Quot… | Android Development and Hacking (xda-developers.com)


See my reply below
 
Last edited:

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
Thank to all of you who care and try to help. I'm still fighting, but not winning yet. I already managed the LOS 17.1 to boot as well as the CAOS. But had a problem even with 2.4GHz WiFi, was not able to switch it on. So again went through flashing the int. ROM, Chinese ROM, opening bootloader and flashing LOS 17.1. Now I'm not able to boot to LOS again (from any A/B slot). I must be doing something terribly wrong (repetitively) or my device could be somehow broken. As soon as I have at least some idea what might be wrong, I will let you know. Till then I continue fighting...
 
Last edited:

taro4

n00b
Joined
Sep 7, 2020
Messages
35
sunarowicz To avoid possible complications with the new chinese rom I would do the first flash with the chinese rom from May. For that base flashing with Qfil or Miflash be sure to use only the emmc ddr firehose from the guide (prog_emmc_firehose_Sdm660_ddr.elf) and do NOT use the modified xml from post #125 (rawprogram_unsparse_mod.xml).

Does your wifi still work with the original rom?
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
sunarowicz To avoid possible complications with the new chinese rom I would do the first flash with the chinese rom from May. For that base flashing with Qfil or Miflash be sure to use only the emmc ddr firehose from the guide (prog_emmc_firehose_Sdm660_ddr.elf) and do NOT use the modified xml from post #125 (rawprogram_unsparse_mod.xml).
I did not try May Chinese ROM yet. I understand it as my last chance if anything else fails. Still trying to make my setup running on the October Chinese version. BTW: are you aware of any particular complications regarding the October version?

Does your wifi still work with the original rom?
Yes, it works on original ROM. 2.4GHz only as one would expect. I do have problems with 2.4GHz on LOS 17.1 with TWRP. It cannot be switched on. So no WiFi at all... On LOS 16.0 without TWRP it works (can be switched on).
 

taro4

n00b
Joined
Sep 7, 2020
Messages
35
I did not try May Chinese ROM yet. I understand it as my last chance if anything else fails. Still trying to make my setup running on the October Chinese version. BTW: are you aware of any particular complications regarding the October version?
No, but the May version is known for a working result in several cases, including me. I think you are the first one (in this thread) who unlocks the bootloader with the October version, all others used it only to update the kernel etc.

Yes, it works on original ROM. 2.4GHz only as one would expect. I do have problems with 2.4GHz on LOS 17.1 with TWRP. It cannot be switched on. So no WiFi at all... On LOS 16.0 without TWRP it works (can be switched on).
There is a reset wifi option in the system settings / advanced / reset options, maybe worth a try.
 
Last edited:

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
No, but the May version is known for a working result in several cases, including me. I think you are the first one (in this thread) who unlocks the bootloader with the October version, all others used it only to update the kernel etc.
It's good to know that I've probably spent two days trying for something that isn't working yet. But I'm not giving up yet!:)
There is a reset wifi option in the system settings / advanced / reset options, maybe worth a try.
Hmm, it doesn't help. The WiFi cannot be switched on right after the first boot to the flashed ROM. So there is nothing to reset.
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
Here is my first conclusion from flashing ROMs after opening the bootloader in October Chinese ROM. TWRP (file TWRP-CUBE_X_Neo-20201028.img) breaks the 2.4GHz WiFi. If this TWRP (boot image) is flashed, the 2.4GHz WiFi cannot be turned on. More precisely, shortly after turned on it turns off by its own. If other recovery is used (I'm using LOS 16.0 recovery in my testing) it doesn't happen. I proved this behavior on CAOS 221, LOS 16.0 and LOS 17.1.

I also tried to flash Magisk and the WiFi Bonding module. It didn't help.

Without flashing this TWRP all these ROMs seems to work. But I didn't tested them much. The WiFi has been my biggest concern. In order to make the ROM booting, the Magisk has to be flashed sometimes. Always in case the TWRP is flashed. The warning screen is shown always if TWRP is flashed. But pressing the Power makes booting to continue.

I tried to boot the TWRP from fastboot
Code:
fastboot boot TWRP-CUBE_X_Neo-20201028.img
but it didn't work. I guess this syntax can be used on A slot only devices. But didn't find how it could work on A/B device. If this would work I believe it wouldn't be needed to flash the TWRP into the device. Sure, not optimal, but one could live with that. At least for now.

BTW: The 5GHz WiFi is not available in any ROM. I tried the WiFi5GhzDisabler Magisk Module hoping it eventually enables 5GHz when it is "disabled" by default, but it turned out to be a false assumption.

Edit:
FINALLY SUCCESS!
Today I decided to give it last chance before I switch to Chinese May version. I realized that I mostly used MiFlash for flashing the international and October Chinese ROMs so far as it seemed to me a bit easier (I have the EMMC device). So today I decided to use QFIL only in the bootloader unlocking process. After I went through the whole process I reached the bootable LOS 17.1 with 2.4GHz WiFi that remains switched on! I was really surprised, because (as far as I can tell) using the QFIL instead of MiFlash was the only difference in the process I went though many many times before. So my current working process looks as follows:
1. Flash the international ROM XNeo(T1009)-EN-20200709.rar (if not already flashed on device) using QFIL.
2. Flash the October Chinese ROM XNeo(T1009)-Android9.0-201028-固件&教程.rar using QFIL.
3. Unlock the bootloader.
4. Flash the 17.1 lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS.img to both system_a and system_b using the fastboot.
5. Flash the TWRP-CUBE_X_Neo-20201028.img to both boot_a and boot_b using fastboot.
6. Try to boot LOS 17.1 from either slot. It won't boot.
7. Boot to TWRP and install Magisk-v20.4.zip to both slots (note: this zip is being installed to the current active slot). The alternate way is ADB sideload.
8. Finally boot to LOS 17.1.
9. Check if 2.4GHz WiFi can be turned on.

One interesting finding. There is no more warning screen during booting. I think it appears only when different recovery (or maybe boot image in general) is flashed to each A/B slot. If the same (like in my current setup), no warning out there.
 
Last edited:

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,374
TWRP doesn't alter anything in the Vendor image which has the drivers. Doesn't work that way.

I might just revert the guide back to the older firmware & keep the upgrade part for anyone that wants to use it.
 

taro4

n00b
Joined
Sep 7, 2020
Messages
35
alldocube-award.jpg


Actually CrimsonKnight13 deserves this award, but at least he doesn't have to change back the guide now. :)
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
Actually CrimsonKnight13 deserves this award, but at least he doesn't have to change back the guide now. :)
That's nice, thank you!:) But I agree that CrimsonKnight13 and some others here should receive an award instead of me.

Not needed to change the guide, but maybe at least some note that MiFlash seems not to be so reliable as QFIL would be useful. Would be nice if someone else could confirm my experience too. At least he or she already knows what to focus on and not be totally lost in problems that make no sense as was I at the beginning of my struggling.;)
 
Last edited:

taro4

n00b
Joined
Sep 7, 2020
Messages
35
Has anyone noticed that the automatic brightness control does not work? At least on my QiDroid. The light sensor itself does work.
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
Has anyone noticed that the automatic brightness control does not work? At least on my QiDroid. The light sensor itself does work.
Yes, I did. In my LOS 17.1 the automatic brightness setting is even missing. Not sure if sensor works in LOS 17.1. But it worked in stock ROM. Automatic brightness setting was available too.
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
Could someone owning the UFS device share some storage benchmarks (e.g. Androbench Storage)? Just curious if there is any benefit over the EMMC device.
 
Last edited:

taro4

n00b
Joined
Sep 7, 2020
Messages
35
Okay, the SD660 supports both standards (emmc and ufs), so Qfil does too. But are there really two types of X Neo?
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,374
Okay, the SD660 supports both standards (emmc and ufs), so Qfil does too. But are there really two types of X Neo?
Not sure... I've never had success with UFS through QFIL for the X Neo. I see that many others can only get EMMC to work. Major mystery for sure.
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
My NeoX shows poor 2.4GHz WiFi performance. The first problem is that it connects to WiFi slowly. After restart (or after turning WiFi on), it takes very long time until my home WiFi appears in the list of visible networks. It sometimes takes several dozens of seconds, even up to minute or two. Other networks around are shown immediately. I observe this behavior right now on LOS 17.1, but observed already on stock ROM and all other custom ROMs I tried earlier. So not LOS related. My other devices connecting to the same network doesn't have this problem.

The other issue is the WiFi speed. The highest transfer rate (receive/download speed from NeoX perspective) during the operation (as shown by WiFi router) is some 59MBit/s. But most of the time lower. Even falls down to only 6MBit/s. The real live transfer (download) tests correspond to these figures. According to the router, the device on RX (download) stream uses only 20MHz channel width, while full 40MHz on TX (upload) stream. But the download performance is bad even for the 20MHz channel width. I tried to change some WiFi settings on router that might affect the speed, but without any luck. I have to say, that really very old cheap Lenovo phone performs better.

Anyone else with the same experience?
 

taro4

n00b
Joined
Sep 7, 2020
Messages
35
My NeoX shows poor 2.4GHz WiFi performance. The first problem is that it connects to WiFi slowly. After restart (or after turning WiFi on), it takes very long time until my home WiFi appears in the list of visible networks. It sometimes takes several dozens of seconds, even up to

The other issue is the WiFi speed. The highest transfer rate (receive/download speed from NeoX perspective) during the operation (as shown by WiFi router) is some 59MBit/s. But most of the time lower. Even falls down to only 6MBit/s. The real live transfer (download) tests
I have speeds around 50-200 Mbit/sec. and the tablet connects immedeately after wifi is switched on. My router says "n/Wi-Fi 4, 40 MHz, WPA2, 2 x 2, 256QAM, 11k, 11v".
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,374
Does that mean you included the UFS-method in the guide because Qfil has this UFS-option?
I included the UFS options since ALLDOCUBE only released that version for both Chinese & International. I had to provide the EMMC firehose file since that's not included by them. It's really perplexing.
 
  • Like
Reactions: taro4
like this

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
25
I have speeds around 50-200 Mbit/sec. and the tablet connects immedeately after wifi is switched on. My router says "n/Wi-Fi 4, 40 MHz, WPA2, 2 x 2, 256QAM, 11k, 11v".
Sounds really nice. What ROM are you running? Do you have installed the WiFi bonding Magisk module?
 
Top