Error failed to initialize open whole lun ufs device slot 0 partition 1

let me know how you like the device. If you can figure out how to instal the google play store on it and the display is bright i’ll get one to use for my drone and to read comics on it.

let me know how you like the device. If you can figure out how to instal the google play store on it and the display is bright i’ll get one to use for my drone and to read comics on it.

Will do. I’m hoping mine has the Google Play store already integrated. I’ll also test to see if I can unlock the bootloader & throw Magisk on it.

I have to wait another week or two due to pre-order backorder. Lucky me.

Looks pretty interesting at that price point. I wonder if there will be community builds since there is TWRP for it as I can’t imagine that it will be supported for more than a year by the manufacturer.

I’m hoping someone ports, at the very least, LineageOS. I’m not too fond of the vanilla AOSP builds w/ barely any updates.

I have received today the X Neo. I hope somebody can find a way to unlock the bootloader, flash TWRP and root the device with Magisk.

Once I figure that out, I’ll post my findings.

This is what I like about AllDoCube:
The selling point of the ALLDOCUBE X Neo is the display – a 10.5-inch organic It’s an EL display with a high resolution of 2560 x 1600. With an OLED display of this site, you can enjoy beautiful images and video for watching videos and playing games. You will enjoy that However, there was no mention of a “display-embedded fingerprint sensor”. Or rather, the fingerprint sensor of this product is not even visible in the product images, so it’s not a fingerprint sensor, to begin with. It’s not clear if it will be supported.

There is no FP reader from anything I’ve read or watched.

I’ll have to make a full guide once I have time & all of my thoughts together.

Great news. I’m liking the stock ROM, maybe I’ll keep It. But having a LineageOS ROM available is wonderful.
When you have the time please tell us how to unlock the bootloader, root with Magisk and install TWRP. It seems that «fastboot flashing unlock» is the right command to unlock the device.
I see that the X Neo is a A/B treble device, the previous X is A only.

The bootloader is already factory unlocked, so complete freedom right away. Due to my frustration with the screen lock security getting garbled after being set, I’ll be switching back to stock AOSP.

I’m quite irked with how it’s gone so far & I’m hoping I don’t have to contact Alldocube or Bangood to get it replaced.

Thanks for all your hard work on this! I just received an X Neo yesterday, and found this thread while looking for a rooting/lineage method.

Would you be willing to write a brief step by step on getting twrp, magisk, and lineage going? Just the highlights, I can figure most things out contextually.

Yeah, that’s something I can work on tomorrow. It’ll be a rough draft for sure, especially when anyone can contribute to it. I might have to make it a web document for easier access & updating.

Yeah, that’s something I can work on tomorrow. It’ll be a rough draft for sure, especially when anyone can contribute to it. I might have to make it a web document for easier access & updating.

Great! I’m happy to expound upon the documentation when I go through the process myself. Anything to help bootstrap this project. If it’s assessible to more people, perhaps one day we may even have custom ROMs and kernels.

Guide posted on original post. Please send me screenshots & changes through this thread or PM. With screenshots, use «Alt+Print Scrn» with the window selected & then use your preferred image or cloud app to properly capture.

I’m going through the process today. Notes as I go along:

1. The link in step one to «Chinese 20200522 firmware» is a copy of the link for QPST before it. (I did find it in your Mega folder however)
2. A step should be added just before #11, mentioning powering down the device before holding all three buttons.

Alas, I received an error on Step #12. I see my Neo show up as «Qualcomm HS-USB QDLoader 9008 (COM3)» and with all the proper files loaded into QFIL, I clicked «Download» to start the process. However in just a few seconds, it fails. Below is a clip of the bottom part of the log, which seems most relevant. Lmk if you want to see the whole thing.

13:32:25: DEBUG: XML FILE (144 bytes): CharsInBuffer=835-144=691
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0"/>
</data>
-------------------------------------------------------------------------------------------

13:32:25: INFO: TARGET SAID: 'ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0'
13:32:25: DEBUG: XML FILE (123 bytes): CharsInBuffer=691-123=568
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device 3 slot 0 partition 0"/>
</data>
-------------------------------------------------------------------------------------------

13:32:25: INFO: TARGET SAID: 'ERROR: Failed to open the device 3 slot 0 partition 0'
13:32:25: DEBUG: XML FILE (119 bytes): CharsInBuffer=568-119=449
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Device type 3, slot 0, partition 0, error 0"/>
</data>
-------------------------------------------------------------------------------------------

13:32:25: INFO: TARGET SAID: 'INFO: Device type 3, slot 0, partition 0, error 0'
13:32:25: DEBUG: XML FILE (130 bytes): CharsInBuffer=449-130=319
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="WARN: Get Info failed to open 3 slot 0, partition 0, error 0"/>
</data>
-------------------------------------------------------------------------------------------

13:32:25: INFO: TARGET SAID: 'WARN: Get Info failed to open 3 slot 0, partition 0, error 0'
13:32:25: DEBUG: XML FILE (118 bytes): CharsInBuffer=319-118=201
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="storage_device_get_num_partition_sectors FAILED!"/>
</data>
-------------------------------------------------------------------------------------------

13:32:25: INFO: TARGET SAID: 'storage_device_get_num_partition_sectors FAILED!'
13:32:25: DEBUG: XML FILE (122 bytes): CharsInBuffer=201-122=79
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="parseSectorValue could not handle start_sector value"/>
</data>
-------------------------------------------------------------------------------------------

13:32:25: INFO: TARGET SAID: 'parseSectorValue could not handle start_sector value'
13:32:25: DEBUG: XML FILE (79 bytes): CharsInBuffer=79-79=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" />
</data>
-------------------------------------------------------------------------------------------

13:32:25: DEBUG: Response was 'NAK'


     _____             
    |  ___|             
    | |__ _ __ _ __ ___  _ __
    |  __| '__| '__/ _ | '__|
    | |__| |  | | | (_) | |
    ____/_|  |_|  ___/|_|


13:32:25: {ERROR: handleProgram:9442 program FAILED - Please see log

The error, «Failed to initialize (open whole lun) UFS Device slot 0 partition 0», means that you also have an EMMC device but with a better working USB-C port or chip. I had to fight with mine a lot just to get MiFlash & the edl tool to even work.

Please use the non-UFS ddr firehose file in the MEGA folder. Move the current elf files to another folder & place the non-UFS ddr firehose in the firmware folder. Use QFIL to select the new elf file & fire away.

fawkesyeah Fixes added to the guide. It’s looking like I’ll have to make a non-UFS section soon.

The error, «Failed to initialize (open whole lun) UFS Device slot 0 partition 0», means that you also have an EMMC device but with a better working USB-C port or chip. I had to fight with mine a lot just to get MiFlash & the edl tool to even work.

Please use the non-UFS ddr firehose file in the MEGA folder. Move the current elf files to another folder & place the non-UFS ddr firehose in the firmware folder. Use QFIL to select the new elf file & fire away.

Thanks, so I’ve tried that and ran into a different error this time. Screenshot of setup, and provided whole error log in codeblock below.

2020-08-02 10:21:31.992    Validating Application Configuration
2020-08-02 10:21:31.998    Load APP Configuration
2020-08-02 10:21:32.010    COM:0
2020-08-02 10:21:32.010    PBLDOWNLOADPROTOCOL:0
2020-08-02 10:21:32.010    PROGRAMMER:True
2020-08-02 10:21:32.010    PROGRAMMER:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522prog_emmc_ufs_firehose_Sdm660_ddr.elf
2020-08-02 10:21:32.010    RESETSAHARASTATEMACHINE:False
2020-08-02 10:21:32.010    SAHARAREADSERIALNO:False
2020-08-02 10:21:32.010    SEARCHPATH:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522
2020-08-02 10:21:32.010    RAWPROGRAM:
2020-08-02 10:21:32.010    rawprogram_unsparse.xml
2020-08-02 10:21:32.010    PATCH:
2020-08-02 10:21:32.010    patch0.xml
2020-08-02 10:21:32.010    ACKRAWDATAEVERYNUMPACKETS:False
2020-08-02 10:21:32.010    ACKRAWDATAEVERYNUMPACKETS:100
2020-08-02 10:21:32.010    MAXPAYLOADSIZETOTARGETINBYTES:False
2020-08-02 10:21:32.010    MAXPAYLOADSIZETOTARGETINBYTES:49152
2020-08-02 10:21:32.010    DEVICETYPE:ufs
2020-08-02 10:21:32.010    PLATFORM:8x26
2020-08-02 10:21:32.010    VALIDATIONMODE:0
2020-08-02 10:21:32.010    RESETAFTERDOWNLOAD:False
2020-08-02 10:21:32.010    MAXDIGESTTABLESIZE:8192
2020-08-02 10:21:32.010    SWITCHTOFIREHOSETIMEOUT:30
2020-08-02 10:21:32.010    RESETTIMEOUT:200
2020-08-02 10:21:32.010    RESETDELAYTIME:2
2020-08-02 10:21:32.010    METABUILD:
2020-08-02 10:21:32.010    METABUILD:
2020-08-02 10:21:32.010    FLATBUILDPATH:C:
2020-08-02 10:21:32.010    FLATBUILDFORCEOVERRIDE:True
2020-08-02 10:21:32.010    QCNPATH:C:Temp0000000.qcn
2020-08-02 10:21:32.010    QCNAUTOBACKUPRESTORE:False
2020-08-02 10:21:32.010    SPCCODE:000000
2020-08-02 10:21:32.010    ENABLEMULTISIM:False
2020-08-02 10:21:32.010    AUTOPRESERVEPARTITIONS:False
2020-08-02 10:21:32.010    PARTITIONPRESERVEMODE:0
2020-08-02 10:21:32.010    PRESERVEDPARTITIONS:0
2020-08-02 10:21:32.010    PRESERVEDPARTITIONS:
2020-08-02 10:21:32.010    ERASEALL:False
2020-08-02 10:21:32.010    Load ARG Configuration
2020-08-02 10:21:32.027    Validating Download Configuration
2020-08-02 10:21:32.027    Image Search Path: H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522
2020-08-02 10:21:32.029    RAWPROGRAM file path: H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522rawprogram_unsparse.xml
2020-08-02 10:21:32.029    PATCH file path:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522patch0.xml
2020-08-02 10:21:32.030    Programmer Path:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522prog_emmc_ufs_firehose_Sdm660_ddr.elf
2020-08-02 10:21:32.825    Process Index:0
2020-08-02 10:21:32.836    Qualcomm Flash Image Loader (QFIL) 2.0.2.3
2020-08-02 10:24:50.974    Programmer Path:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522prog_emmc_firehose_Sdm660_ddr.elf
2020-08-02 10:24:59.093    Image Search Path: H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522
2020-08-02 10:24:59.094    RAWPROGRAM file path: H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522rawprogram_unsparse.xml
2020-08-02 10:24:59.094    PATCH file path:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522patch0.xml
2020-08-02 10:25:04.598    Start Download
2020-08-02 10:25:04.606    Program Path:H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522prog_emmc_firehose_Sdm660_ddr.elf
2020-08-02 10:25:04.609    ***** Working Folder:C:UsersprofuAppDataRoamingQualcommQFILCOMPORT_3
2020-08-02 10:26:34.630    Binary build date: Apr 27 2018 @ 03:04:33
2020-08-02 10:26:34.632    QSAHARASERVER CALLED LIKE THIS: 'C:Program Files (x86)QualcommQPSTbinQSaharaServer.ex'Current working dir: C:UsersprofuAppDataRoamingQualcommQFILCOMPORT_3
2020-08-02 10:26:34.634    Sahara mappings:
2020-08-02 10:26:34.635    2: amss.mbn
2020-08-02 10:26:34.636    6: apps.mbn
2020-08-02 10:26:34.638    8: dsp1.mbn
2020-08-02 10:26:34.639    10: dbl.mbn
2020-08-02 10:26:34.640    11: osbl.mbn
2020-08-02 10:26:34.641    12: dsp2.mbn
2020-08-02 10:26:34.643    16: efs1.mbn
2020-08-02 10:26:34.644    17: efs2.mbn
2020-08-02 10:26:34.645    20: efs3.mbn
2020-08-02 10:26:34.646    21: sbl1.mbn
2020-08-02 10:26:34.646    22: sbl2.mbn
2020-08-02 10:26:34.648    23: rpm.mbn
2020-08-02 10:26:34.649    25: tz.mbn
2020-08-02 10:26:34.651    28: dsp3.mbn
2020-08-02 10:26:34.653    29: acdb.mbn
2020-08-02 10:26:34.654    30: wdt.mbn
2020-08-02 10:26:34.655    31: mba.mbn
2020-08-02 10:26:34.656    13: H:[user]{Devices}X NeoRootingFirmwareChinaT1009_20200522prog_emmc_firehose_Sdm660_ddr.elf
2020-08-02 10:26:34.657  
2020-08-02 10:26:34.658    10:26:34: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
2020-08-02 10:26:34.659  
2020-08-02 10:26:34.661    10:26:34: ERROR: function: sahara_main:983 Sahara protocol error
2020-08-02 10:26:34.663  
2020-08-02 10:26:34.664    10:26:34: ERROR: function: main:320 Uploading  Image using Sahara protocol failed
2020-08-02 10:26:34.665  
2020-08-02 10:26:34.666  
2020-08-02 10:26:34.667    Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
2020-08-02 10:26:34.668    Finish Download

I notice it mention that the Sahara protocol failed. I found in the Configuration another protocol. Should I try that? I do not want to brick my tablet, and am not familiar with this particular process, so I’ll just leave it as is for the time being.

You could also try checking «Reset State Machine» for the Download Configuration in QFIL & see where that takes you.

Down the rabbit hole we go… you’ll need to use MiFlash since it’s able to handle that properly (I think). The driver provided with it works quite well for me, especially if I had to force a power cycle back to EDL mode.

You could also try checking «Reset State Machine» for the Download Configuration in QFIL & see where that takes you.

Update: I wrote a post here earlier with an error, but resolved it with a computer reboot. MiFlash did flash the firmware using the settings you posted above.

For the guide on this, if someone encounters any errors with MiFlash, try rebooting, and possibly a different USB port if possible. That made it so MiFlash could proceed.

I successfully made it all the way through the guide, and flashed TWRP.

Also, I’ve taken screenshots along the way, and added a few visual guides to the steps for your guide. I’ve zipped and attached it to this post.

1. I do want the English LineageOS flashed next. Do I need to flash the international version again so that the ROM is in English, or can I go ahead and flash Lineage right now?

2. Going to need Magisk too, I assume I need to boot into a working LineageOS before I can install Magisk? I think this would require manual boot.img patching from within the Magisk Manager app.

3. Is there a button combo when powering up to go straight into TWRP?

Updated above message. New messages below:

1. I do want the English LineageOS flashed next. Do I need to flash the international version again so that the ROM is in English, or can I go ahead and flash Lineage right now?

2. Going to need Magisk too, I assume I need to boot into a working LineageOS before I can install Magisk? I think this would require manual boot.img patching from within the Magisk Manager app.

3. Is there a button combo when powering up to go straight into TWRP?

Thanks for the screenshots. I’ll have to work on that through the week when I have time after work & probably in between gaming & moving watch (family is away for a week).

1. I recommend the LineageOS 17.1 GSI, which is extremely easy to flash (see below). https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/ Also, you’ll need to get your choice of gapps for 10 arm64, like OpenGapps. https://opengapps.org/
fastboot flash system_a <imagename.img>
fastboot flash system_b <imagename.img>
fastboot -w
The above commands allows you to keep the kernel (boot a/b), TWRP, & the vendor a/b images while still utilizing any Treble GSI OS.
2. You can either use Magisk 20.4 or I’ll include the Magisk for phh-based GSIs. No, you only need TWRP to flash it to both boot images.
3. Power + Volume Down should work, otherwise try it with Volume Up. Either you’ll get to TWRP or the bootloader, which can get you to recovery mode.

The above commands allows you to keep the kernel (boot a/b), TWRP, & the vendor a/b images while still utilizing any Treble GSI OS.

Curious, it’s not a good idea to flash LineageOS with TWRP directly? I can do it with fastboot, but if TWRP is not a good idea for a specific reason, I’ll make note to myself in my ROM folder so that I don’t make that mistake in the future.

You can either use Magisk 20.4 or I’ll include the Magisk for phh-based GSIs. No, you only need TWRP to flash it to both boot images.

Excellent, glad to hear it is this easy. I’ve had a pain rooting some ROMs in the past, particularly the Nvidia Shield (2017) is overly complicated.

Either you’ll get to TWRP or the bootloader, which can get you to recovery mode.

Power+VolUp at Off state held for 7 seconds leads to TWRP.

I recommend the LineageOS 17.1 GSI

I am seeing multiple ROM links on this page, which one do I need for the X Neo? I tried the most popular download, the second one below, but upon boot the tablet just died, nothing after the initial boot logo.

• lineage-17.1-20200713-UNOFFICIAL-treble_arm64_bvN.img.xz
• lineage-17.1-20200713-UNOFFICIAL-treble_arm64_avN.img.xz
• lineage-17.1-20200713-UNOFFICIAL-treble_arm_bvN.img.xz
• lineage-17.1-20200713-UNOFFICIAL-treble_arm_avN.img.xz
• lineage-17.1-20200713-UNOFFICIAL-treble_a64_bvN.img.xz
• lineage-17.1-20200713-UNOFFICIAL-treble_a64_avN.img.xz

The original LOS 16.x I have posted has issues with security features, which I can’t recommend but I’m providing in case anyone wants to give it a go anyways.

TWRP does allow image flashing of boot, system, vendor & recovery images (ramdisk in the case of the X Neo).

Use lineage-17.1-20200713-UNOFFICIAL-treble_arm64_bvN.img.xz if you want to use it on both slots. For Treble ROMs, anything marked with «a» means A only, but «b» means A/B. It will definitely require gapps; which means you’ll need to flash it in TWRP on slot b through slot a, then reboot to TWRP on slot b to flash to slot a, & then reboot back to system slot a. I wish they’d just bring out Treble-enabled recovery zips to flash both, including Magisk on this one… Quite frustrating to fight with it since it can be confusing.

To note, I have not tested LOS17.1 GSI, so let me know what you find about it. See this post about my findings of other ROMs.

Which means you’ll need to flash it in TWRP on slot b through slot a, then reboot to TWRP on slot b to flash to slot a, & then reboot back to system slot a. I wish they’d just bring out Treble-enabled recovery zips to flash both, including Magisk on this one… Quite frustrating to fight with it since it can be confusing.

That is certainly confusing lol, but I do grasp what you mean. I’ll give this a try with Magisk and Gapps.

To note, I have not tested LOS17.1 GSI, so let me know what you find about it. See this post about my findings of other ROMs.

I was able to boot into LOS 17.1 GSI just fine. Looking through everything, it seems to work as expected, except for one issue: WiFi seems to only detect 2.4ghz networks. None of my or the neighbors 5ghz networks are showing in the list of connectable networks. Very odd, and frustrating, as I was going to use this tablet primarily as a Moonlight streaming device. I probably wont even need the mSD card slot, at least for a while.

I’m curious to try the CAOS rom you mentioned above, and/or the Quack rom too. Is there a repo link for those that I can use to try?

That is certainly confusing lol, but I do grasp what you mean. I’ll give this a try with Magisk and Gapps.

I was able to boot into LOS 17.1 GSI just fine. Looking through everything, it seems to work as expected, except for one issue: WiFi seems to only detect 2.4ghz networks. None of my or the neighbors 5ghz networks are showing in the list of connectable networks. Very odd, and frustrating, as I was going to use this tablet primarily as a Moonlight streaming device. I probably wont even need the mSD card slot, at least for a while.

I’m curious to try the CAOS rom you mentioned above, and/or the Quack rom too. Is there a repo link for those that I can use to try?

This is the running list that you can reference https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

CAOS has zero issues with Magisk & WiFi for me (but I admit I didn’t check to see if I’m accessing the 2.4 or 5 versions of my SSID). DRM doesn’t work, so I used the Magisk module to disable it. MX Player Pro & Plex work fine w/o out anyways (Plex wouldn’t load any local streaming videos with DRM enabled). Any other official streaming service is a no-go but I don’t really care since I have other devices for such.

This is the running list that you can reference https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

CAOS has zero issues with Magisk & WiFi for me (but I admit I didn’t check to see if I’m accessing the 2.4 or 5 versions of my SSID). DRM doesn’t work, so I used the Magisk module to disable it. MX Player Pro & Plex work fine w/o out anyways (Plex wouldn’t load any local streaming videos with DRM enabled). Any other official streaming service is a no-go but I don’t really care since I have other devices for such.

Thanks, and I agree the DRM is moot for me, with Plex/Zion, and a Shield for my TV that does Netflix, etc. Thanks for the tip on disabling DRM though, I might have ended up scratching my head eventually when I loaded Plex.

I was able to install Gapps and Magisk just fine on LineageOS 17.1 GSI, in case you want to add this to your list. I am going to do a TWRP backup, and try the other ROMs today to see if they have 5ghz working. I’ll report back with my findings.

Should I be looking under Unofficial 10 ROMs > Firmware Collection, and clicking Download beside each one of them until I find CAOS and try that? I found one under «eremitein» for CAOS. I’ve never played with GSI, so this is a bit new to me (most devices I’ve worked with in the past have custom ROMs on XDA)

Thanks, and I agree the DRM is moot for me, with Plex/Zion, and a Shield for my TV that does Netflix, etc. Thanks for the tip on disabling DRM though, I might have ended up scratching my head eventually when I loaded Plex.

I was able to install Gapps and Magisk just fine on LineageOS 17.1 GSI, in case you want to add this to your list. I am going to do a TWRP backup, and try the other ROMs today to see if they have 5ghz working. I’ll report back with my findings.

Should I be looking under Unofficial 10 ROMs > Firmware Collection, and clicking Download beside each one of them until I find CAOS and try that? I found one under «eremitein» for CAOS. I’ve never played with GSI, so this is a bit new to me (most devices I’ve worked with in the past have custom ROMs on XDA)

That’s the one. I acquired it from the XDA thread.