Flashing stock rom with QDL tool
-
This thread is meant to help regarding issues with flashing a lenovo stock rom with device in EDL-mode using the QDL-tool for Linux.
I've made a short video, of how I flash the stock rom. Mabe it helps to understand the written steps. I am using a self compiled version, since it was the most reliable way to get the tool running without issues.
Help for compiling and other helpful information regarding QDL is given here: https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md
The video:
https://drive.google.com/file/d/13YKJp5dUKnpD7KKy4_IfuAJCIVFq7_UT/view?usp=sharingThe steps I made in the video in words:
- My file-tree-structure looks like this:
- something/lenovo-flash
- qdl (qdl tool folder)
- x605
- TB-X605L_S210224_200910_ROW (stock rom folder)
- something/lenovo-flash
- I am in the stock rom folder and have to call qdl tool from two parentfolders above, thats why I do:
../../qdl/qdl - I have connected an USB-A to USB-C cable to the computer but NOT YET to the device
- I enter following command in the terminal:
../../qdl/qdl prog_emmc_firehose_8953_ddr.mbn rawprogram_unsparse_upgrade.xml patch0.xml - The message
Waiting for EDL deviceis displayed - I press both volume buttons of the device with my thumb at keep them pressed while I connect the USB-C end of the cable to my device
- The device turns on and shows the Lenovo logo, I still keep the volume buttons pressed
- The device display turns black
- In the terminal, the qdl tool starts to do something -> I release the volume keys
- Now I just need to wait until the tool finished
If you get error messages from the qdl tool, it may be caused by the version of qdl you are using (snap or a specific distro package), thats why I strongly recommend to use a self compiled version.
I fear, I can't provide more help than this^^.
Good luck
- My file-tree-structure looks like this:
-
@luksus ** Update, I made the video-link accessible to everyone.
-
@luksus So the good news is I've successfully loaded the stock ROW and booted the tab to it, enabled developer options, OEM unlock. Amazing!
The bad news is I've subsequently followed the Fastboot instructions and all looks good. The only error I get is......
$ fastboot format:ext4 userdata
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdataAnd subsequently will not boot.
But definitely getting closer!Lee.
-
@luksus after reflashing the boot.img it has indeed booted into ubports!
I am up and running, thank you so much for your help.