Today I also flashed modified_Global_stock_6GB_with_twrp_v3, after that newest crDroid, Magisk and Opengapps instead of Nik Gapps, because I had trouble with TTS-services in Nik Gapps. Works fine apart from some hangings in the first configuration dialogue in crDroid, maybe caused bei OpenGapps...
The modified XML will probably destroy (parts of) my data-partition because of the dfferent size of vendor_5.img. I will reflash the whole system if a well working GSI-rom with A12L is available.
Thanks for your work, Allexbast and CrimsonKnight13, but at the moment I don't see any reason to change my crDRom11 (with older TWRP), it runs without any problems. Never missed 5 GHz Wifi. :)
Thanks! In rawprogram_unsparse_upgrade_keepuserandsystem.xml I found a minor difference compared to xmls in older firmwares - the current num_partition_sectors in vendor_5.img is 229016, but in older roms it was 228872. So if QFIL writes a slightly larger partition, this should have effects to...
Thank you. Is it possible to flash modified_global_stock with rawprogram_unsparse_mod.xml to update only the vendor / firmware part?
And what does the update_image_EDL.bat?
CrimsonKnight13 Can you please explain what is modified in this rom? Has probably already been described in the deleted posts, but I don't remember. :) And why should one flash a rom from the year before last?
Did you format data? Afaik there is still an incompatibility depending encryption at A12 and TWRP. Going from A11 to A12 my phone did not boot without formatting data .
Allexbast, has someone taken over your account? A GSI rom is the best thing that could have happened to the X Neo, I am happy with these roms since September 2020.
You can create an free account at mega.nz or try any free file service like ufile.io. I think CrimsonKnight13 will publish the files later at his mega-drive.
NeoMarkster It seems that doing the initial flashing with newer chinese firmwares can lead to broken systems. Some users had this problem last year, see post #425 ff.
After upgrading crDRom to 21.10.13 I had several issues depending a not responding system_ui, but after deleting the cache of the app system_ui this was gone.
Phh-setting "Double tap to wake" does not work for me.
A new version of crDRom is available.
Changes
crDRom R 21.10.13
October 2021 SPL
crDroid 7.11 base
latest available phh patches
removed commit for A12 style QS media plugin, on the tablet devices it looks very bad
picked patches from Andy Yan: "always render windows into notch cutouts" and...
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...
Great. Did you flash different firmware & TWRP versions before?
Possible, but why should older firmware work with different hardware, but not newer firmware?
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.
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...
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?
The max size of our...
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).
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...
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...
FYI, Eremitein (developer of many GSI roms, e.g. qidroid and crdrom) wrote at XDA, that the build server he used was damaged and all his work is suspended.
I randomly tried this again yesterday with the newer version crdrom-v307-210513 and now it passed the safety net check (unlike the previous version). Nothing else has changed.
I was about 6 month on qiDroid and now on crDRom/crDroid (Android 11), don't see a difference in stability. But crDRom has more options, I can even do without using GravityBox. And Swift Backup works with sdcards in regular mode, not experimental.
Then your needs have become at least three...
I just updated crDRom to the newest version (crdrom-v307-210513-arm64-bvZ), but was not able to flash NikGapps-basic-arm64-11-20210514-signed.zip, flash always terminated with an error. The older NikGapps-basic-arm64-11-20210130-signed.zip worked without error.
Afaik the size of the system partition is 3069 MB, if you want to flash bigger roms, you have to change the partition layout. Or flash a rom without gapps and a nano/pico gapps package afterwards (this normally needs a resize of the system partition file-system).
It can be skipped, but you should use the TWRP version matching the original firmware version (e.g. TWRP 2020.10.28 with Alldocube firmware 2020.10.28) to avoid differences between kernel and vendor.
When a GSI Rom is already installed and Alldocube publishes a new firmware, with the modified XML file it is possible to flash only the new kernel and vendor parts and the GSI system partition will not be overwritten.
Then perhaps you don't have your tablet in bootloader-mode. :) It must look like the picture below. If you use Windows, what kind of device is shown in the device-manager after the tablet in bootloader-mode is connected? It should show "Android Bootloader Interface" or similar.