As a professional manufacturer Alldocube should spoil their customers with a changelog... Is there any download alternative? I was not able to get it from Baidu.Since we're working with the Chinese FW, I'll be using the new version XNeo(T1009)-Android9.0-201028-固件及教程 - 酷比魔方官网 (51cube.com) for testing.
I'll make it available as a repack of just the FW on MEGA soon, since downloading from Baidu is a PITA.As a professional manufacturer Alldocube should spoil their customers with a changelog... Is there any download alternative? I was not able to get it from Baidu.
adb shell rm /data/system/locksettings.db
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.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.
Magisk has release, beta & debug (canary) versions. I've had the best luck with the debug versions on the GSI ROMs.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.
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.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?
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.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?
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.Does anybody have the touchscreen issues too?
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.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.
I'll have to do more testing with it. I prefer doing img flashes via fastboot rather than TWRP.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.
Thank you for trying to help, but unfortunately this is not the case. Fastboot getvar unlocked says "unlocked: yes".I think the displayed message means that your bootloader is not unlocked / still locked.
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.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.
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.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.
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?I recommend flashing Magisk to get around any such issues.
This is me, I am ariadnejro at xda.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.