Alldocube X Neo

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
63
More on flashing (or should I rather say installing?) the TWRP. I searched for some info and have found the recommended way of doing that on A/B devices, see:
https://androidmore.com/install-twrp-on-android/
https://www.droidwin.com/flash-files-a-b-partition-devices/

They both use the same way:
1. Boot to TWRP image using the fastboot boot twrp.img command.
2. Install the TWRP.zip from booted image.

Maybe our TWRP issues are not caused by the older TWRP version (please note that both instructions use the 3.3.1 version for A/B device), but the way we are flashing the twrp.img directly into both slots from fastboot. Maybe TWRP configures itself for the A/B environment when installed (not flashed) from the booted TWRP image in order to work properly. The question is where we get the right twrp.zip for NeoX?
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
More on flashing (or should I rather say installing?) the TWRP. I searched for some info and have found the recommended way of doing that on A/B devices, see:
https://androidmore.com/install-twrp-on-android/
https://www.droidwin.com/flash-files-a-b-partition-devices/

They both use the same way:
1. Boot to TWRP image using the fastboot boot twrp.img command.
2. Install the TWRP.zip from booted image.

Maybe our TWRP issues are not caused by the older TWRP version (please note that both instructions use the 3.3.1 version for A/B device), but the way we are flashing the twrp.img directly into both slots from fastboot. Maybe TWRP configures itself for the A/B environment when installed (not flashed) from the booted TWRP image in order to work properly. The question is where we get the right twrp.zip for NeoX?
Truly, I've not had issues but it seems like you're overthinking it. TWRP was installed to the new boot.img within TWRP. With the new version, it can be done just the same. I'll have to update my own & see where it goes.
 

kyen

n00b
Joined
Dec 5, 2020
Messages
2
Truly, I've not had issues but it seems like you're overthinking it. TWRP was installed to the new boot.img within TWRP. With the new version, it can be done just the same. I'll have to update my own & see where it goes.
HI,

So do you have 5ghz wigi on your custom rom or i misunderstand :) ?

I tried some rom with no success to have 5ghz wifi:
- losq-v224-201017-arm64-bvN
- losq-v224-201017-arm64-bgN
- RR: system-190406-arm64-ab-vanilla-nosu
- lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS

I had 5ghz wifi 1 time on lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS after flashing chinese rom to unlock the bootloader, but after trying some rom, i do not have 5ghz wifi on lineage-17.1 anymore
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
63
I had 5ghz wifi 1 time on lineage-17.1-20201114-UNOFFICIAL-treble_arm64_bvS after flashing chinese rom to unlock the bootloader, but after trying some rom, i do not have 5ghz wifi on lineage-17.1 anymore
What do you mean by not having 5GHz WiFi? You do not see and/or cannot connect to any 5GHz network? Or you can connect, but the WiFi performance is bad? I have found two problems with 5GHz according to my experience so far:
1.
NeoX doesn't work with each 5GHz channel to me. This should depend on your location (local regulations) and your router capabilities. In my case (based on my location) NeoX reports these 5GHz frequencies it can operate with in the log:
Code:
5Ghz non-DFS frequencies: 5180 5200 5220 5240
5Ghz DFS frequencies: 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700
Despite this I cannot connect to all these freqs/channels. I guess it is because of my router (Linksys running OpenWrt and suffering from the closed source WiFi driver). So at the end I can connect to these 5GHz channels only: 56, 60, 64, 100, 108, 112, 116, 120, 124 and 128. The thing is you should find the right channel that works for you.
2.
When finally connected to 5GHz WiFi, I still suffer from the poor performance in terms of transfer rates and signal sensitivity. Both these are OK on stock (and Chinese) ROMs. Even on custom LOS 16.0 too. But not on any (Android 10 based) GSI ROM I have tested. It seems there is no solution for this yet. Me and taro4 (and others for sure) have been trying to resolve this, but without any success yet.
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
63
Truly, I've not had issues but it seems like you're overthinking it. TWRP was installed to the new boot.img within TWRP. With the new version, it can be done just the same. I'll have to update my own & see where it goes.
My point was that it's (maybe) not good idea to flash the same (single) TWRP patched boot.img into both slots. I mean doing so we are flashing the boot.img coming from slot A to slot B too or the boot.img coming from slot B to slot A too (depends on what boot.img from these two you provide in the guide). Maybe these both images are not (bitwise) identical. I can imagine to myself that during installing the TWRP into both slots (in the right way you follow), one is configured to work well in slot A and the other to work well in slot B. It can maybe work well in the other slot for most purpose, but not for all. But my guess only.
 
Last edited:

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
My point was that it's (maybe) not good idea to flash the same (single) TWRP patched boot.img into both slots. I mean doing so we are flashing the boot.img coming from slot A to slot B too or the boot.img coming from slot B to slot A too (depends on what boot.img from these two you provide in the guide). Maybe these both images are not (bitwise) identical. I can imagine to myself that during installing the TWRP into both slots (in the right way you follow), one is configured to work well in slot A and the other to work well in slot B. It can maybe work well in the other slot for most purpose, but not for all. But my guess only.
With Treble, the boot images are identical for quick failover during a bad boot.
 

kyen

n00b
Joined
Dec 5, 2020
Messages
2
What do you mean by not having 5GHz WiFi? You do not see and/or cannot connect to any 5GHz network? Or you can connect, but the WiFi performance is bad? I have found two problems with 5GHz according to my experience so far:
1.
NeoX doesn't work with each 5GHz channel to me. This should depend on your location (local regulations) and your router capabilities. In my case (based on my location) NeoX reports these 5GHz frequencies it can operate with in the log:
Code:
5Ghz non-DFS frequencies: 5180 5200 5220 5240
5Ghz DFS frequencies: 5260 5280 5300 5320 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700
Despite this I cannot connect to all these freqs/channels. I guess it is because of my router (Linksys running OpenWrt and suffering from the closed source WiFi driver). So at the end I can connect to these 5GHz channels only: 56, 60, 64, 100, 108, 112, 116, 120, 124 and 128. The thing is you should find the right channel that works for you.
2.
When finally connected to 5GHz WiFi, I still suffer from the poor performance in terms of transfer rates and signal sensitivity. Both these are OK on stock (and Chinese) ROMs. Even on custom LOS 16.0 too. But not on any (Android 10 based) GSI ROM I have tested. It seems there is no solution for this yet. Me and taro4 (and others for sure) have been trying to resolve this, but without any success yet.
I mean I cannot see AND connect to any 5ghz wifi with a custom room.

I try Havoc in this moment, Havoc-OS-v3.1-20200111-ARM64AB-GSI.img... and I can connect to 5ghz wifi now... Don't know it's because the rom Havoc or maybe my manipulations to passing from a rom to others...
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
63
With Treble, the boot images are identical for quick failover during a bad boot.
Hmm, I wonder how it knows which system partition to boot up, whether system_a or system_b, if both boot images are identical. It has to contain some logic which decides based on current active boot slot (A or B) then.
 

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
63
I try Havoc in this moment, Havoc-OS-v3.1-20200111-ARM64AB-GSI.img... and I can connect to 5ghz wifi now... Don't know it's because the rom Havoc or maybe my manipulations to passing from a rom to others...
How compares the 5GHz WiFi performance in Havoc to 5GHz performance of other devices in your 5GHz network? I mean how compares the transfer rates and signal sensitivity? I just installed Havoc-OS-v3.8-20200821-Official-arm64-ab.img into one slot and can confirm that 5GHz WiFi works. But performs as badly as in other GSIs I tried...

But thank you for pointing at other nice GSI ROM working with NeoX!
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494

sunarowicz

n00b
Joined
Nov 17, 2020
Messages
63
I tried to change data partition filesystem to f2fs in TWRP 3.3.1. The change command went well without any error. But right afterwards (still in TWRP) errors on data cannot be mounted has appeared. After restarting to recovery again, data is declared to be formatted to ext4. Any idea why changing data to f2fs doesn't work?
 

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
Happy new year. :) I bought the original Alldocube keyboard, but unfortunately the mapping of the top row (multimedia keys etc.) is not correct with my Rom (QiDroid). Is there any way to change the key assignments there? I already tried a few apps, but that does not work.
 

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
CrimsonKnight13 How did you manage to add the TWRP to the original kernel last year? I tried this like you've written in post #125 (flashed the new kernel in TWRP & backed up the resulting modified image), renamed boot.emmc.win from the backup to img, but after flashing this file with fastboot the recovery was the original recovery.

Btw. the December-kernel is 4.4.153 like in October.

And with kernel from October and vendor from December wifi won't work, at least with qiDroid.
 
Last edited:

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
CrimsonKnight13 How did you manage to add the TWRP to the original kernel last year? I tried this like you've written in post #125 (flashed the new kernel in TWRP & backed up the resulting modified image), renamed boot.emmc.win from the backup to img, but after flashing this file with fastboot the recovery was the original recovery.

Btw. the December-kernel is 4.4.153 like in October.

And with kernel from October and vendor from December wifi won't work, at least with qiDroid.

In TWRP, you need to install the recovery RAM disk from the old TWRP img file. It will give you a working December kernel with TWRP. After that, you can use QFIL partition manager to dump the new boot.img.
 
  • Like
Reactions: taro4
like this

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
In TWRP, you need to install the recovery RAM disk from the old TWRP img file. It will give you a working December kernel with TWRP. After that, you can use QFIL partition manager to dump the new boot.img.
That worked, thank you. In TWRP I flashed the boot.img from the new rom archive as boot-image and then the older TWRP.img as recovery ram disk. After that I made a backup within TWRP and also with QFIL, but TWRP- and QFIL-files are identical.

TWRP based on kernel 2020.12.16: https://mega.nz/file/mBEk0RTJ#rYu3ASyM_Td5kHPqlQSOs8UsGout74Z7gKMPx_Rv4O4

With new kernel and vendor I have working 5 GHz - directly after boot. My router says ac/Wi-Fi 5, 80 MHz, WPA2, 2 x 2, 11k, 11v, MU-MIMO and 433 Mbit/s on channel 100. But I also had working 5 GHz with October-kernel/vendor some hours ago after first reboot, so this should be treated with caution...

Where did you find that new rom?
 
Last edited:

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
That worked, thank you. In TWRP I flashed the boot.img from the new rom archive as boot-image and then the older TWRP.img as recovery ram disk. After that I made a backup within TWRP and also with QFIL, but TWRP- and QFIL-files are identical.

TWRP based on kernel 2020.12.16: https://mega.nz/file/mBEk0RTJ#rYu3ASyM_Td5kHPqlQSOs8UsGout74Z7gKMPx_Rv4O4

With new kernel and vendor I have working 5 GHz - directly after boot. My router says ac/Wi-Fi 5, 80 MHz, WPA2, 2 x 2, 11k, 11v, MU-MIMO and 433 Mbit/s on channel 100. But I also had working 5 GHz with October-kernel/vendor some hours ago after first reboot, so this should be treated with caution...

Where did you find that new rom?

Thanks for providing the new boot.img. I have added it to my Mega profile.

I found it here: https://pan.baidu.com/s/1zHLMeIa9bjXE-VKvAQEeQA
pw is md8y

For WiFi, I still get 2.4GHz. Not sure why it's stuck but qiDroid doesn't want to budge with 5GHz.
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
Hello I am a newbie here and also intersted for some mods. I like the work of You all. I would like to ask You how to proceed if I want the TWRP and Magisk but would like to use international latest stock ROM. I already tried the unlocking the bootloader with flashing_critical but it is still Locked. I know that there was some informations already in comments before but If it is possible to get as little bit more instant waY I will be thankfull :)
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
Hello I am a newbie here and also intersted for some mods. I like the work of You all. I would like to ask You how to proceed if I want the TWRP and Magisk but would like to use international latest stock ROM. I already tried the unlocking the bootloader with flashing_critical but it is still Locked. I know that there was some informations already in comments before but If it is possible to get as little bit more instant waY I will be thankfull :)
I don't think it's possible with the full international ROM. Testing might need to be done with the Chinese bootloader, international system image, international boot image & international vendor image.
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
I don't think it's possible with the full international ROM. Testing might need to be done with the Chinese bootloader, international system image, international boot image & international vendor image.
Thank You very much for the first hint. I Will start with reflashing with Chinese FW (is it possible only reflash bootloader to left everything else untouched ?) than I Will flash TWRP and Magisk. What should I do after that? Thank You very much for your support.
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
Thank You very much for the first hint. I Will start with reflashing with Chinese FW (is it possible only reflash bootloader to left everything else untouched ?) than I Will flash TWRP and Magisk. What should I do after that? Thank You very much for your support.
Yes, you'll need to use fastboot to flash abl_a & abl_b from the Chinese FW (QFIL partition manager can do so as well). I'm not sure if the bootloader requires any other files to be flashed like vbmeta, frp, and/or ftm.

Code:
fastboot flash abl_a abl_a.img
fastboot flash abl_b abl_b.img
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
Yes, you'll need to use fastboot to flash abl_a & abl_b from the Chinese FW (QFIL partition manager can do so as well). I'm not sure if the bootloader requires any other files to be flashed like vbmeta, frp, and/or ftm.

Code:
fastboot flash abl_a abl_a.img
fastboot flash abl_b abl_b.img
I already flashed Chinese FW and also TWRP easily using your guide, Therefore I am happy. Thank You. Now I would like to flash stock internatinal ROM but only system and vendor. I roughly compared the sizes of files contained in Chinese and International Packages of the same “October” release. There was multiple sub- images for system, vendor and user. There are only differences in one vendor sub-image and few system sub-images. Also one XML file different. Is it possible to proceed with only flash the sub-files with different sizes? If yes, how can I do that? Is it possible to flash using fastboot and use the particular images names or is need to somehow merge them? Do I need before this procedure somehow modify the size of some partitions to fit the image /sub-images? Thank You for your valuable response.
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
I already flashed Chinese FW and also TWRP easily using your guide, Therefore I am happy. Thank You. Now I would like to flash stock internatinal ROM but only system and vendor. I roughly compared the sizes of files contained in Chinese and International Packages of the same “October” release. There was multiple sub- images for system, vendor and user. There are only differences in one vendor sub-image and few system sub-images. Also one XML file different. Is it possible to proceed with only flash the sub-files with different sizes? If yes, how can I do that? Is it possible to flash using fastboot and use the particular images names or is need to somehow merge them? Do I need before this procedure somehow modify the size of some partitions to fit the image /sub-images? Thank You for your valuable response.
Creating a modified xml file is possible, as I've done before. I recommend you remove all but the boot_a, boot_b, system_a, system_b, vendor_a, & vendor_b parts for the International ROM (newest one recommended). Save that as a new file in the same folder (such as adding _mod to the end of the file name) & try using it in QFIL. If that works, please share it here.
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
Creating a modified xml file is possible, as I've done before. I recommend you remove all but the boot_a, boot_b, system_a, system_b, vendor_a, & vendor_b parts for the International ROM (newest one recommended). Save that as a new file in the same folder (such as adding _mod to the end of the file name) & try using it in QFIL. If that works, please share it here.
Do You mean to use the Chinese december FW from post #255 and TWRP image from taro4s post #258? Do You know where can I get the december version of internatinal FW? I only found the October internatinal FW at official web. But previously I have the december internatinal version via OTA update on stock ROM.
 
Joined
Jul 21, 2020
Messages
34
I wanted to tell you that I've been using an Android 11 GSI for some days with almost zero issues and it has become my daily driver. It's latest phhusson release. I had to do a full wipe (data, dalvik and cache) to get a fully working experience.

https://github.com/phhusson/treble_....m/system-roar-arm64-ab-vndklite-gapps.img.xz

Almost everything is working. Magisk doesn't seem to work but it has built-in superuser. Prime Video crashes when it worked in LineageOS 17.1. Great battery life and HW+ decoding. I'm not going back to Android 10.
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
Creating a modified xml file is possible, as I've done before. I recommend you remove all but the boot_a, boot_b, system_a, system_b, vendor_a, & vendor_b parts for the International ROM (newest one recommended). Save that as a new file in the same folder (such as adding _mod to the end of the file name) & try using it in QFIL. If that works, please share it here.
I did it. I changed xml file like You said, flashed with QFIL and it works. Within a first booting there was some minor problem About some corrupted data but can be easily fixed within Factory reset. Device remains unlocked and also international 20201028 FW working. After that I tried to reflash the taro4’s TWRP 20201216 Image from post #258 (only to see If New kernel image Will work with older system) and also I installed latest magisk and magisk manager. This leads to complete wifi brick and also locked screen. Locked screen Can be fixed according guide. I reflashed than TWRP image from the guide (based on Chinese 20201028) but this dont fix the wifi brick. After that I reflashed Chinese FW according a guide and also International 20201028 with changed xml file like previously and also did the Factory reset. Wifi works again and everyrhing else. So this unlocking of Internatinal FW works. Unfortunately If I after that flashed the Chinese TWRP 20201028 from guide and also latest magisk this leads again to bricked wifi. So bricking a Wifi is not related to version of kernel (TWRP image) but it have something with flashing TWRP image or TWRP image + latest Magisk 21.4. I dont know. I did this still together. I Will continue with experiments today and I Will share here. If You have any idea About compatible version of Magisk or some idea around this wifi brick behaviour please also share with me. In TWRP I saw some error message: Unable to decrypt FBE Device. Do You already know this error? Thanks
 

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
I wanted to tell you that I've been using an Android 11 GSI for some days with almost zero issues and it has become my daily driver. It's latest phhusson release. I had to do a full wipe (data, dalvik and cache) to get a fully working experience.

https://github.com/phhusson/treble_....m/system-roar-arm64-ab-vndklite-gapps.img.xz

Almost everything is working. Magisk doesn't seem to work but it has built-in superuser. Prime Video crashes when it worked in LineageOS 17.1. Great battery life and HW+ decoding. I'm not going back to Android 10.
Great news! What version of Magisk did you try? And does the rom support automatic brightness control and 5 GHz wifi?

I tried to find a xda-thread for this rom but wasn't successful.
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
Great news! What version of Magisk did you try? And does the rom support automatic brightness control and 5 GHz wifi?

I tried to find a xda-thread for this rom but wasn't successful.
Yes. It is interesting. Maybe I Will switch to also later. :)
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
Btw., why that? :)
Hello. I would like to wait for some official update which Will have everyrhing working. Brightbess sensor, wifi 2.4G also 5G , aptx HD...until that time I would like to have at least standard functionality like brightness but I am missing aptx HD very much. This is reason why I want modify. I want to install Magisk aptx HD module. If there Will be not progress from official alldocube FW update I Will switch to any fully working ROM :)
 

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
Hello. I would like to wait for some official update which Will have everyrhing working. Brightbess sensor, wifi 2.4G also 5G , aptx HD...until that time I would like to have at least standard functionality like brightness but I am missing aptx HD very much. This is reason why I want modify. I want to install Magisk aptx HD module. If there Will be not progress from official alldocube FW update I Will switch to any fully working ROM :)
I just installed the Magisk aptx-module, no errors, but I can't really test due to missing aptx-devices. If you can live without 5 GHz wifi and automatic brightness for the moment, you should perhaps use an Android 10 GSI rom. I can recommend qiDroid, runs with Magisk etc. on kernel/vendor 20201216 and has many options included.
 

CrimsonKnight13

Lord Stabington of [H]ard|Fortress
Joined
Jan 8, 2008
Messages
7,494
I did it. I changed xml file like You said, flashed with QFIL and it works. Within a first booting there was some minor problem About some corrupted data but can be easily fixed within Factory reset. Device remains unlocked and also international 20201028 FW working. After that I tried to reflash the taro4’s TWRP 20201216 Image from post #258 (only to see If New kernel image Will work with older system) and also I installed latest magisk and magisk manager. This leads to complete wifi brick and also locked screen. Locked screen Can be fixed according guide. I reflashed than TWRP image from the guide (based on Chinese 20201028) but this dont fix the wifi brick. After that I reflashed Chinese FW according a guide and also International 20201028 with changed xml file like previously and also did the Factory reset. Wifi works again and everyrhing else. So this unlocking of Internatinal FW works. Unfortunately If I after that flashed the Chinese TWRP 20201028 from guide and also latest magisk this leads again to bricked wifi. So bricking a Wifi is not related to version of kernel (TWRP image) but it have something with flashing TWRP image or TWRP image + latest Magisk 21.4. I dont know. I did this still together. I Will continue with experiments today and I Will share here. If You have any idea About compatible version of Magisk or some idea around this wifi brick behaviour please also share with me. In TWRP I saw some error message: Unable to decrypt FBE Device. Do You already know this error? Thanks
TWRP can be installed into any boot image with a previously available file. You were seeing errors with mismatched boot & vendor images. It has to be TWRP/Boot (Chinese) + Vendor (Chinese) or TWRP/Boot (International) + Vendor (International). You can't mix & match.

Install Recovery Ramdisk
Follow step 8 @ https://oneplus.gadgethacks.com/how-to/install-twrp-recovery-your-oneplus-7-pro-0199340/
 
Last edited:

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
Nice, I have a working automatic brightness control on my qiDroid. Found this thread at XDA and although the thread is some years old and the overlay-apk was made for Android 8, it also works with Android 10.

With a terminal or adb shell make /vendor writeable:

Code:
su
mount -o rw,remount /vendor

Copy the apk to /vendor/overlay. Then activate the apk in terminal / adb shell:

Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk

Reboot the tablet and switch on auto brightness in the settings.

In post #51 in the XDA-thread there is an optimized overlay-apk with more dimming levels, but that does not work for me.
 

OFaceSIG

2[H]4U
Joined
Aug 31, 2009
Messages
2,603
Aldocube really seems to be pushing their products to influencers hard. Trying to break into the white people markets. Australia, US, etc. Products seem pretty solid but for whatever reason they can't get that Wine cert l1 whatever it is for Netflix, Amazon HD playback. I'd order one tomorrow if they had that.
 

GabiOneKey

n00b
Joined
Feb 7, 2021
Messages
8
TWRP can be installed into any boot image with a previously available file. You were seeing errors with mismatched boot & vendor images. It has to be TWRP/Boot (Chinese) + Vendor (Chinese) or TWRP/Boot (International) + Vendor (International). You can't mix & match.

Install Recovery Ramdisk
Follow step 8 @ https://oneplus.gadgethacks.com/how-to/install-twrp-recovery-your-oneplus-7-pro-0199340/
I think You are right. I tried also another combinations and also another TWRP boot image mentioned here. Nothing works directly flashed by fastboot. I have also Idea to build the proper TWRP ZIP for X-Neo. But as I realised My goal was to have working Bluetooth codec Aptx HD. So The custom ROM not really needed for me for now. But If somebody here have some machine-time, It is not big Deal I think. If anybody have android SDK , it is possible to get TWRP source codes from GitHub and modify the config file according to X-Neo and build one. (Maybe this is already done and is the part of boot.img from guide in the form of Ram-disk..) my next idea was to use the official TWRP ZIP for xiaomi mi pad 4 because the similar platform (snapdragon 660, 64gEMMC, 4G Ram)- can be tried. For now I End up with unlocked bootloader and actual international STock ROM with Newest magisk-patched stock Boot image (I have now installed the aptx hd Magisk module and it works properly and also all the features). BTW after I flashed the whole chinesse FW I realised that not wifi detected (maybe there is some bug directly within the chinesse FW, so maybe Will be also good idea to create the TWRP boot.img based on unlocked international STock FW). Only to be completed I did for me this: flashing complete chinesse FW with qfil emmc version. Unlocking bootloader. Flashing internatinal October stock ROM with qfill and Xml file with Deleted everything but boot_a, boot_b, system_a, system_b, vendor_a, & vendor_b parts. After that I boot up normally (system asked for Factory reset so I confirmed). In this stage I download the latest version of Magisk manager 8.0.7 and send the boot.img from international stock October ROM into X-Neo. I patched than this boot.img using Magisk manager. Patched image I sent to my PC. I reflashed the patched boot.img using fastboot to both partition a and b and after that rebooted normally. In this step I did the OTA (wifi) update to the last official december version of ROM. But be aware to perform the wifi update using special procedure with Magisk (there is some guide how to). So I have now unlocked most uptodated systemless rooted (capable of official updates) Magisk-modifiable Device. But probably I Will switch later also to some newest android 11 or similar. BTW I would like to enable LDAC codec, do anybody here have some clue? pS: sorry for such a long text here.
 
Last edited:

taro4

Weaksauce
Joined
Sep 7, 2020
Messages
92
my next idea was to use the official TWRP ZIP for xiaomi mi pad 4 because the similar platform (snapdragon 660, 64gEMMC, 4G Ram)- can be tried.
That does not work, I tried both Mi Pad 4 and Mi A2 TWRPs combined with boot.img 2020.12.16, but if I booted into that TWRP, there are only 3 partitions shown (system, vendor and data, if I remember right), so these Xiaomis might have a different partition-layout. Since TWRP 3.5.0 is available, I was actually planning to create a suitable TWRP for the X-Neo, but have so far been too lazy to get to grips with it.

And maybe it would be less time consuming to install a custom rom and try the Magisk aptx module there. :)
 
Last edited:

fawkesyeah

n00b
Joined
Jul 30, 2020
Messages
17
I wanted to tell you that I've been using an Android 11 GSI for some days with almost zero issues and it has become my daily driver. It's latest phhusson release. I had to do a full wipe (data, dalvik and cache) to get a fully working experience.

https://github.com/phhusson/treble_....m/system-roar-arm64-ab-vndklite-gapps.img.xz

Almost everything is working. Magisk doesn't seem to work but it has built-in superuser. Prime Video crashes when it worked in LineageOS 17.1. Great battery life and HW+ decoding. I'm not going back to Android 10.

Thanks for sharing this information! I wonder how it is still going for you a month later? Also, what benefit does the HW+ decoder provide?

Update: I flashed the newest crdrom-v302-210315-arm64-bgZ today, and I am seeing that it does detect and join my WiFi 5ghz network. I had trouble with ROMs in the v200 range not seeing 5ghz. Okay update #2, I tested the WiFi signal, and 5ghz is very poor on the other side of my house. And it will not auto-connect after rebooting. However, 2.4ghz is fine. I really like this ROM (I was on CAOS prior) and am going to stick with it. The touch responsiveness seems much better, and there are lots of ROM customizations baked in.
 
Last edited:
  • Like
Reactions: taro4
like this
Top