Alldocube X Neo

I didn't know there was also a new chinese firmware. Looking forward to your testing, maybe we can use the kernel and vendor of this new firmware.
 
Last edited:
Last edited:
i need a qcn file.
my qcn backup is only 180kb in size. the imei appears in hexeditor, but not on the tablet.
other qcn backups are around 500kb in size. I've tried different ones and all of them connect to the phone provider, but you can't make a phone call or receive any data. the message 'turn off flight mode' appears. the qcn files are probably device-specific and also of different sizes.
hopefully someone can provide me with a qcn file.
many thanks!!!
 
I have success with flashing all but the system & userdata partitions for the Chinese 201028 firmware.

TWRP based on the new kernel (flashed the new kernel in TWRP & backed up the resulting modified image) - https://mega.nz/file/rk1nyITT#10HtfLGZTA_az9oqMlxpdDsUJxDHTN8q8vobbtagfnA
Modified XML for flashing all but system & userdata - https://mega.nz/file/z9k3UaxC#GK-gnRfcTm-YBbdpvM8OGPqS-09_q2ZsmHZkm8j8Dvo

Steps for upgrading the firmware. I might add an additonal step due it complaining about corruption at boot. It might have to do with the vbmeta paritions & GSI.
  1. Flash the modified XML plus the patch0.xml with QFIL
  2. Boot to the bootloader/fastboot
  3. Flash the new TWRP file to boot_a & boot_b
  4. Flash newest debug Magisk on both slots from TWRP
  5. (Optional) Remove the locksettings.db due to the vendor image change. If you don't, you won't be able to unlock the screen after boot.
    Code: 
    adb shell rm /data/system/locksettings.db
  6. Boot into your chosen Android
New kernel & vendor do not allow 5GHz WiFi on GSI. Not sure if there any other limitations.
MS Edge works great w/o crashing. Chrome most likely will work fine as well.

Request: If anyone wants to test my guide fully with the new firmware, please do. If it works, I'll replace the links to reflect the new version in the guide.
 
Last edited:
CrimsonKnight13 said:
Request: If anyone wants to test my guide fully with the new firmware, please do. If it works, I'll replace the links to reflect the new version in the guide.
Click to expand...
Thank you, worked for me (QFIL emmc mode) on Qidroid 223. I used the last Magisk release (20.4), do you mean the beta with debug Magisk? Vivaldi Browser (Chrome) now runs, great! I had to update the Magisk module Riru EdXposed to get the Xposed framework back running. I have no active lockscreen, so did not do the unlock option. E-compass still seems to be absent. :)
 
taro4 said:
Thank you, worked for me (QFIL emmc mode) on Qidroid 223. I used the last Magisk release (20.4), do you mean the beta with debug Magisk? Vivaldi Browser (Chrome) now runs, great! I had to update the Magisk module Riru EdXposed to get the Xposed framework back running. I have no active lockscreen, so did not do the unlock option. E-compass still seems to be absent. :)
Click to expand...
Magisk has release, beta & debug (canary) versions. I've had the best luck with the debug versions on the GSI ROMs.

Guide has been updated to v0.6.
 
  • Like
Reactions: taro4
like this
I have also managed to install the new firmware using MiFlash. Everything seems to work fine, even Chrome.
I see that the new kernel is 4.4.153 October 29. And we have a new vendor image.
I'm in latest LineageOS 17.1 and everything seems stable.
Thanks to CrimsonKnight13 for giving us the new firmware without having to wipe the tablet.
 
Quick question: Has anyone achieved 5ghz WiFi on any custom ROMs yet?

I see CrimsonKnight mention that the "New kernel & vendor do not allow 5GHz WiFi on GSI", should I interpret that as no GSI ROM will (probably) ever allow 5ghz WiFi?
 
Last edited:
fawkesyeah said:
Quick question: Has anyone achieved 5ghz WiFi on any custom ROMs yet?

I see CrimsonKnight mention that the "New kernel & vendor do not allow 5GHz WiFi on GSI", should I interpret that as no GSI ROM will (probably) ever allow 5ghz WiFi?
Click to expand...
Not sure. I've tested it on QiDroid 224. Might need to be tested across different ROMs from various devs. I was making an educated guess but I'll gladly be corrected if a ROM is found to work.
 
Today I unpacked my new Neo X. There are three issues that concern me (still on the stock ROM):
- 5GHz WiFi doesn't work. So I'm afraid it might be the device HW issue, not the custom ROM issue.
- AptX does't work, just the basic SBC do. Also discussed here: https://www.alldocube.com/en/forums/topic/no-aptx-bluetooth-connection-with-alldocube-x-neo/
- Sometimes the screen does't respond to touches. Seems that changing the tablet orientation does help.

Could anyone please check whether AptX works on the custom ROM?
Does anybody have the touchscreen issues too?
 
sunarowicz said:
Today I unpacked my new Neo X. There are three issues that concern me (still on the stock ROM):
- 5GHz WiFi doesn't work. So I'm afraid it might be the device HW issue, not the custom ROM issue.
- AptX does't work, just the basic SBC do. Also discussed here: https://www.alldocube.com/en/forums/topic/no-aptx-bluetooth-connection-with-alldocube-x-neo/
- Sometimes the screen does't respond to touches. Seems that changing the tablet orientation does help.

Could anyone please check whether AptX works on the custom ROM?
Does anybody have the touchscreen issues too?
Click to expand...
I've not had any touchscreen issues, but as of late it's been weird battery draining issues. Hopefully I don't have a faulty one since I doubt I'll great support.

For AptX, someone more familiar with it will have to test it. Has it been tested with any of the Magisk modules dealing with AptX?
 
There is something wrong with latest TWRP. I used it to install a new LineageOS release as usual (install img file in system image partition) and my tablet became corrupted and couldn't boot. After a lot of struggling I could make it work again flashing latest international firmware to reformat the internal partitions, flashing May chinese firmware, unlocking the bootloader and finally flashing latest chinese firmware and latest TWRP. I could install LineageOS using fastboot and restored the data partition from a recently created nandroid.
 
It was similar to pjrodriguez at the end of September, but with the old TWRP. I lost the IMEI. Something is wrong with the qcn backup I made earlier so that I can no longer use the tablet to make phone calls. I would like to ask you again for a qcn backup. Of course you can also edit the IMEI's beforehand.
Something like this can happen to you very quickly, a qcn backup would be recommended for everyone.
Thanks again!!!
 
sunarowicz said:
Does anybody have the touchscreen issues too?
Click to expand...
I have this issue too, especially when swiping from the screen edges in fullscreen mode. There are reviewers on youtube who have also mentioned this issue. It is an issue across multiple ROMs, so I believe it to be hardware related.
 
fawkesyeah said:
I have this issue too, especially when swiping from the screen edges in fullscreen mode. There are reviewers on youtube who have also mentioned this issue. It is an issue across multiple ROMs, so I believe it to be hardware related.
Click to expand...
I'm still on the stock ROM. Today I performed two OTA updates. The latest one dated to 2020-11-3 declared in the changelog: "Optimized touchscreen and enhanced user experience". I had not enough time to check, but as far as I can tell it really get improved. So hopefully not hardware related.

Edit:
It definitely get improved. I would say there is no touchscreen issue anymore.
 
Last edited:
One interesting finding on the 5GHz WiFi issue here. Despite the 5GHz is not working on the stock ROM too, I tried to set the WiFi hotspot on stock ROM and switched it into 5GHz mode. Surprisingly it works. Other devices did connect to this 5GHz hotspot on Neo X. So maybe some hope here.
 
pjrodriguez said:
There is something wrong with latest TWRP. I used it to install a new LineageOS release as usual (install img file in system image partition) and my tablet became corrupted and couldn't boot. After a lot of struggling I could make it work again flashing latest international firmware to reformat the internal partitions, flashing May chinese firmware, unlocking the bootloader and finally flashing latest chinese firmware and latest TWRP. I could install LineageOS using fastboot and restored the data partition from a recently created nandroid.
Click to expand...
I'll have to do more testing with it. I prefer doing img flashes via fastboot rather than TWRP.
 
sunarowicz If you are still on stock rom, can you please check with a sensor test app if an e-compass is present? Thank you.
 
I just updated my Qidroid from 223 to 224 with new TWRP without problems, incl. file system resize and flashing gapps and magisk.
 
I do follow the X Neo Modification Guide (thank a lot to all of you who have contributed to it!), but I'm not sure if I do need to proceed the step "Upgrade base firmware to newest version(for GSI-based ROMs)" when I do move from the stock ROM and have TWRP already flashed in the previous step called "TWRP". Yesterday I did not proceed this step and reached the corrupted and not bootable state as pjrodriguez reported earlier (thx pjrodriguez for a hint how to resolve this situation). But this was maybe because of a different reason. Could someone please let me know if proceeding the step "Upgrade base firmware to newest version(for GSI-based ROMs)" is needed? My goal is to flash the GSI LOS 17.1.

Edit:
So I did skip the "Upgrade base firmware to newest version(for GSI-based ROMs)" as yesterday and did reached the corrupted and not bootable state after flashing the LOS 17.1 GSI image to both slots via fastboot again. Pressing power button doesn't make booting to continue.
IMG_20201120_111324.jpg
 
Last edited:
I think the displayed message means that your bootloader is not unlocked / still locked.
 
taro4 said:
I think the displayed message means that your bootloader is not unlocked / still locked.
Click to expand...
Thank you for trying to help, but unfortunately this is not the case. Fastboot getvar unlocked says "unlocked: yes".

Edit:
BTW this is the bootloader screen. Not sure whether the missing BOOTLOADER and BASEBAND versions mean anything suspicious.
dsBuffer.jpg
 
Last edited:
Okay. But because pjrodriguez also had issues with LOS, I would try another custom rom at first. I did the whole unlocking thing with the chinese firmware from May several times and had no issues with different GSI roms, but did never try LOS.

Bootloader and Baseband Version are also empty at my bootloader screen.

If your bootloader is unlocked, maybe LOS aknowledges it as locked (for what reason ever).
 
Right after getting into this corrupted state I flashed the CAOS GSI image. Nothing has changed, still corrupted. But I did not restored the working state (by flashing international stock ROM and the Chinese then) in between flashing the LOS and CAOS. Maybe I should try to unlock the bootloader with the May Chinese ROM. All my attempts so far were done with the October ROM.
 
Last edited:
The screen saying "your device is corrupted" is the same I had trying to update LOS 17.1 using latest TWRP. Believe me, the only way to resurrect the tablet is the one I described in my previous post.
 
The warning screen is nothing to worry about. Boots perfectly fine into GSI-based ROMs. I still need to see about correcting that issue though.
 
CrimsonKnight13 said:
The warning screen is nothing to worry about. Boots perfectly fine into GSI-based ROMs. I still need to see about correcting that issue though.
Click to expand...
Unfortunately it doesn't boot. It stucks at this screen and doesn't continue in booting. Pressing the power button just reboots into this same screen again.

Edit:
To be more specific, pressing the power buton makes the ALLDOCUBE powered by Android screen to be shown and then it powers off the tablet.
 
Last edited:
pjrodriguez said:
The screen saying "your device is corrupted" is the same I had trying to update LOS 17.1 using latest TWRP. Believe me, the only way to resurrect the tablet is the one I described in my previous post.
Click to expand...
I know your resurrect way and I already passed it once successfully. Now I will have to for the second time. I'm just thinking to use the May instead of October Chinese ROM which I was using so far. I did not flashed LOS with TWRP, but with fastboot. Despite this I ran into the same problem as you did.
 
sunarowicz said:
Unfortunately it doesn't boot. It stucks at this screen and doesn't continue in booting. Pressing the power button just reboots into this same screen again.
Click to expand...
I recommend flashing Magisk to get around any such issues.
 
CrimsonKnight13 said:
I recommend flashing Magisk to get around any such issues.
Click to expand...
Thank you for trying to help. But flashing Magisk 20.4 (to both slots) did not helped. I'm still getting to stuck at the warning screen. So I need to follow the pjrodriguez resurrection path again. Now I will try the May Chinese version and will skip the "Upgrade base firmware to newest version(for GSI-based ROMs)" step in the guide again. Or shouldn't I?
 
Guys, it seems that all my pain is caused by the wrong version of LOS 17.1. I use the lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS.img downloaded from the GitHub's Generic System Image (GSI) list.

I followed the taro4's hint and flashed the Chinese October version with Qfil. Then (after opening the bootloader) the above mentioned LOS 17.1 to both slots again. And again reached the warning screen from which it was not booting any further. I went to TWRP immediately and flashed the lineage-16.0-20200516-UNOFFICIAL-t1009.zip downloaded from CrimsonKnight13's Mega share. Only to one slot for now and did the reboot. And again got the warning screen. But after pressing the power buton it finally booted to LOS 16.0 (as CrimsonKnight13 expected earlier today)! So now I do have bootable LOS 16.0 in one slot and not bootable LOS 17.1 in the second slot. I would like to flash 17.1 to both slots and have them bootable too. Should I use a different LOS 17.1 image?
 
In the LOS-thread at XDA there are several complaints about not booting devices, so this seems to be a negative combination of X Neo and LOS rom and has nothing to do with Qfil or Miflash. Anyway arm64_bvs is the right one. If you are an "optioneer" I can recommend the QiDroid rom.

On the other hand here is someone who seems to have a working LOS 17.1 on X Neo.
 
Last edited:
taro4 said:
In the LOS-thread at XDA there are several complaints about not booting devices, so this seems to be a negative combination of X Neo and LOS rom and has nothing to do with Qfil or Miflash. Anyway arm64_bvs is the right one. If you are an "optioneer" I can recommend the QiDroid rom.

On the other hand here is someone who seems to have a working LOS 17.1 on X Neo.
Click to expand...
This is me, I am ariadnejro at xda.
Maybe I didn't make myself clear, I have been using LOS 17.1 for many months working as a charm. What I also managed is to boot LOS 18 with only some minor issues. In fact I think I will try again with different GApps and different versions of Magisk.
When my X Neo became corrupted it was in my opinion due to latest TWRP, from now on I will flash LOS using fastboot.
 
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? :)
 
You must log in or register to reply here.
Back
Top