Alldocube X Neo

So that means after flashing A12 rom you are able to boot into TWRP the normal way?
 
taro4 said:
Is your RQ2A.210405.005 a different version of crDroid from another maintainer? On Eremiteins download site there is no version from 2021.04.05. If yes, you should make a clean flash. Depending gapps, I always used the vanilla-roms and flashed gapps after that because you can mostly choose the package size and do not have to install every google app.
Click to expand...
Sorry, i have meant: release 2021.04.25 and it is there.

So how can i make a dirty flash to keep my apps? Any way for this?
Just flash .img files in slot A/B in fastboot? CrimsonKnight13 i would also need your help.
Thanks guys
 
taro4 said:
So that means after flashing A12 rom you are able to boot into TWRP the normal way?
Click to expand...
I just double checked and I think I'm having the same issue as you now. I was able to reboot to TWRP 3.5.2_9-0 with no issue, even after installing A12 rom but before creating a PIN code to unlock. But after doing that, now TWRP just bootloops. So it does appear that the encryption in A12 causes this version of TWRP to not be bootable. Darn. So anyway, word of warning to anyone flashing A12, be sure to flash Magisk in TWRP before you set a PIN code during initial setup (that's when the data partition is officially encrypted).

Edit: Well now I am stuck in TWRP bootloop it seems. I tried using 'adb reboot system' and 'adb reboot bootloader' then selecting Start, but it always boots into TWRP. Any idea how I can force it to boot into System again?
 
Last edited:
emrah_tr said:
Sorry, i have meant: release 2021.04.25 and it is there.

So how can i make a dirty flash to keep my apps? Any way for this?
Just flash .img files in slot A/B in fastboot? CrimsonKnight13 i would also need your help.
Thanks guys
Click to expand...
As you are on CrDroid, you can simply flash a newer version over the older one from within TWRP and after that Magisk again, without erasing data etc. All to both slots. If you use a bgz version now you should dirty flash the same. If you want to change to bvz version without Google apps I think it will be better to do a clean flash.
 
fawkesyeah I'm still at A11 and I think I will not update to A12 due to the difficulties TWRP still has with A12 up to version 3.62 even with not encrypted partitions. Some days ago version 3.70 was released with encryption support for A12, but this won't help us at the moment.
 
Btw., I just noticed that Eremitein's last login at XDA was 2022.06.25, so it seems he has to solve other problems and his CrDroid will not be continued.
 
Last edited:
fawkesyeah said:
Edit: Well now I am stuck in TWRP bootloop it seems. I tried using 'adb reboot system' and 'adb reboot bootloader' then selecting Start, but it always boots into TWRP. Any idea how I can force it to boot into System again?
Click to expand...
I figured it out. While the TWRP screen was bootlooping, I used a USB cable and ADB command "adb reboot bootloader" to get into bootloader mode. Then the only thing I found that would kick me out of the recovery bootloop was to select "Boot to FBMI" which I am not sure what that is, but it did actually boot system finally. Whew, I was afraid I would have to use the firehoses to start all the way back at international again.

taro4 said:
fawkesyeah I'm still at A11 and I think I will not update to A12 due to the difficulties TWRP still has with A12 up to version 3.62 even with not encrypted partitions. Some days ago version 3.70 was released with encryption support for A12, but this won't help us at the moment.
Click to expand...
That's a legit concern for some people. I used to use TWRP all the time, but these days I don't take backups or flash much anymore. As long as I have Magisk working, I can use SwiftBackup for 99% of what I need. This being mostly just an eReader and Youtube device for me, at any rate.
 
  • Like
Reactions: taro4
like this
taro4 said:
Has someone tested with one of the A13-roms?
Click to expand...
Not yet, but I can only imagine how laggy it would be. I'm on A12 PixelExperience right now, and planning to roll back to the previous ROM because the UI is just too unresponsive in comparison.

Update: Good news, you can easily downgrade to A11 again from A12. I reverted to crDroid v316, it was the most stable I found prior to A12. Also the preexisting TWRP that was not loading due to A12 works automatically with A11 again, didn't have to reflash at all. Since the Xneo is getting on in age and probably will start struggling to keep up after A12, I'm probably going to sunset it on crDroid A11 v316 until the end of its days. Which for me as an eReader and occasional Moonlight streamer, ought to still be years ahead, given it is well taken care of physically.

If anyone tries A13 roms and finds that it is very stable and has snappy responsiveness, let us know and I'll consider upgrading then.
 
Last edited:
  • Like
Reactions: taro4
like this
Never had performance issues with the X-Neo (and this crDroid), so I also think this device will last for some more years. Security patches are overrated. :)

And it won't be easy to replace the X-Neo either, since no tablet of the lower price segments has an Amoled screen anyway.
 
Hello guys! Every time I try to flash modified global with qfil I see "your device is corrupt..."
Can enyone tell me what's wrong?
 
Please specify the rom you tried to flash and how (UFS or EMMC). Which rom did you have on it before?
 
taro4 said:
Please specify the rom you tried to flash and how (UFS or EMMC). Which rom did you have on it before?
Click to expand...
Tried to flash modified global stock 6gb with twrp via qfil, emmc.
Before and now I have T1009_V2.0_20201216
 
Hm, is your bootloader unlocked? If not, please follow the modification guide in post 1. I recommend to do it with chinese rom 20200522. After unlocking you should be able to flash the modified global rom. If your bootloader is already unlocked, I don't know any advice now, but search this thread for "corrupt", I remember there were some posts depending this issue years ago.
 
taro4 said:
Hm, is your bootloader unlocked? If not, please follow the modification guide in post 1. I recommend to do it with chinese rom 20200522. After unlocking you should be able to flash the modified global rom. If your bootloader is already unlocked, I don't know any advice now, but search this thread for "corrupt", I remember there were some posts depending this issue years ago.
Click to expand...
Thank you for reply. I'll try again.
 
I've installed cr droid v3.16 successfully.
Is there any fix for TWRP to work with A12 decryption?
 
Afaik no. You can try to flash a 3.7.0 TWRP for similar SDM660 devices (Xiaomi Mi Pad 4, Redmi Note 7 etc.), there are some official versions at the TWRP site. But due to different drivers in the kernel or other differences it is possible that some parts of the X Neo don't work after that (e.g. wifi). But please give it a try and report here. :)
 
taro4 said:
Afaik no. You can try to flash a 3.7.0 TWRP for similar SDM660 devices (Xiaomi Mi Pad 4, Redmi Note 7 etc.), there are some official versions at the TWRP site. But due to different drivers in the kernel or other differences it is possible that some parts of the X Neo don't work after that (e.g. wifi). But please give it a try and report here. :)
Click to expand...
Thanks. I'll try)
 
What version of Android are you on? Is it decently snappy? I won a T20 and it's good, but not very quick.
 
I am still using crDroid 7.16 (A11), which is fast and reliable. And 1,5 years old, but that doesn't matter for me.
 
You must log in or register to reply here.
Back
Top