Flash Lenovo Tab M10 TB-X605L LTE with Stock Image Android 8 Oreo - Thinkpad Tablet General

Dear all,
Background: I’ve bought a brand new Lenovo Tab M10 TB-X605L LTE. It’s for my grandma, so that she can video-call her great-grandchildren during the Corona crises, and I learned that I require to have Android 8 Oreo on it, as Teamviewer Host has to run on it and start automatically (my grandma is almost 90 years and she can operate a toaster, but not a tablet). Unfortunately, I’ve upgraded to Android 9 Pie, which by design doesn’t support Teamviewer host.
The problem is: I need to get back to Android 8 Oreo, but I almost bricked my Lenovo Tab M10 by trying to do so. I’ve already spent a few days and read/tried tons of instructions/suggestions/forum discussions, and I’m completely stuck. I would really enjoy some help or the decisive tip – and especially my grandmother would really enjoy seeing her four great-grandchildren after three weeks of quarantine.
This works:
I managed to get a M10 TB-X605L stock ROM Android 8 Oreo: techswizz com/lenovo-tab-tb-x605l-stock-rom-firmware-flash-file/
I can reboot to fastflash mode (reboot and hold Volume-Down), and I can use ADB and Fastboot.
I can install TWRP recovery mode (by flashing recovery.img) and start/use TWRP (reboot and hold Volume-Up+Down).
I think I’ve unlocked the bootloader, but I’m not sure how to verify it.
I have installed the Qualcomm_USB_Driver_v1.0 and the tablet gets a COM port (can be seen in Device Manager).
This doesn’t work:
General
I cannot boot in normal mode (device stops or constantly reboots when I try).
I managed to install Magisk (in TWRP), but the devices still can’t boot in normal mode afterwards, so I cannot start Magisk.
Lenovo Moto Smart Assistant
I can start it, download the stock image. When I try to flash the device, the progress bar jumps to 33% immediately, and after a few seconds a “FAIL” button appears without any further information.
Fastboot
I can flash boot.img and recovery.img, but system.img is splitted in system_1.img, system_2.img, etc., and when I connect these files with packsparseimg.exe, the resulting system.img seems to be invalid (devices doesn’t start).
QFIL
I can see the devices on the COM Port. I can load rawprogram_unsparse.xml and patch0.xml.
When the device comes online, I try to hit Download immediately, and I either get the following error:
[*]ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
[*]ERROR: function: sahara_main:924 Sahara protocol error
[*]ERROR: function: main:303 Uploading Image using Sahara protocol failed
[*]Download Fail:Sahara Fail:QSaharaServer Failrocess fail
[*]or it says the device is not in EDL mode (which is easy to fix by booting in EDL mode from TWRP, but then the sahara error comes up).​
QPST
I can connect the phone via QPST Configuration (COM3, Q/QCPP-XXX (Sarah Download), USB)-
When I open the “eMMC Software Download app”, I can open the Sahara XML file rawprogram_unsparse.xml – I hope, that’s the right one.
When I “Load XML def…”, I don’t know which xml file to open:
[*]rawprogram_unsparse.xml and rawprogram0.xml.bak show an error “Document error on element type ‘raw program’ and name/value ‘true’”.
[*]Patch0.xml shows no error, but I think it’s the wrong file for “Load XML def”.​
Dowloading with “Patch0.xml” leads to an error “Timeout waiting for device”
QcomDLoader.exe (1.3.2.0)
I can „load“ the stock image directory, and set the settings (eMMC programmer: prog_emmc_firehose_8953_lite.mbn, Raw program: rawprogram_unsparse.xml, patch0: patch0.xml).
Wenn I press ‘Start’ the Step/Status “Sahara/Flashing” appears for 5 seconds, followed by messages “failed.
Any help or suggestion is highly appreciated.
Kind regards,
Walter

Hey,
i have the same device and a similar situation - any news on this?
@OP: How did you proceed? Different device, any alternative to teamviewer?

Solution for flashing Qualcomm based Android devices
Dear all,
please find the solution for for flashing Qualcomm based Android devices (sahara_rx_data error) here: https://android.stackexchange.com/questions/224369/cannot-flash-qualcomm-with-stock-image-lenovo-tab-m10-tb-x605l-lte-android-8-o?noredirect=1#comment291391_224369
Kind regards
PS: I'm not allowed to post links here. Can someone please copy-paste the link and add it here?

--SOLUTION TO FLASHING QUALCOMM BASED ANDROID DEVICES-----
Cannot flash Qualcomm with Stock Image (Lenovo Tab M10 TB-X605L LTE, Android 8 Oreo)
Background I’ve bought a brand new Lenovo Tab M10 TB-X605L LTE. It’s for my grandma, so that she can video-call her great-grandchildren during the Corona crises, and I learned that I require to have
android.stackexchange.com

Related

[How-To] All-In-One Guide For Yoga Tablet 2[Closed]

@MikeChannon Content deleted, please close
Tethered CWM or TWRP and Root KitKat or Lollipop. And temp_root
deleted
Reserved
reserved
Downgrade Lollipop Firmware (Return to stock KitKat from Lollipop)
deleted
Repair Lollipop upgrade - entered bios error
deleted
Yoga Tab 2 (830,1050,1380) - unlocking the bootloader
deleted
Partition layouts
deleted
AoL - Android ON Linux
deleted
YT2 Firmware and Various Tools
Removed
workdowg said:
Enter bios to install alternate OS's (Windows/Linux) or run from USB - Coming soon?
Click to expand...
Click to collapse
I had seen the linux was working on tablet, do you know how to achieve it?
tang1331726 said:
I had seen the linux was working on tablet, do you know how to achieve it?
Click to expand...
Click to collapse
I've seen nothing on the 1050F or any of the Android based tablets (even numbers). The Russian forum has a guide for the Windows tablets (odd numbers). I'm trying to keep up on what they are doing. I'm collecting files to help us later on...
I'm proud to have contributed to this tip section .
Note that this trip works on majority of 5.0x devices.
One question : is there a 830f version with windows, as suggests :
http://shop.lenovo.com/fr/fr/yoga-tablet-2/
It's in french but selecting 8" let me thinl there's a windows 8 version
I'd ne happy to give it a try... after having succesfully rooted my 830, as i'm stuck with the E: error
http://forum.xda-developers.com/thinkpad-tablet/general/yoga2-official-830f-lollipop-update-20-t3161448/page2
pregis said:
I'm proud to have contributed to this tip section .
Note that this trip works on majority of 5.0x devices.
One question : is there a 830f version with windows, as suggests :
http://shop.lenovo.com/fr/fr/yoga-tablet-2/
It's in french but selecting 8" let me thinl there's a windows 8 version
I'd ne happy to give it a try... after having succesfully rooted my 830, as i'm stuck with the E: error
http://forum.xda-developers.com/thinkpad-tablet/general/yoga2-official-830f-lollipop-update-20-t3161448/page2
Click to expand...
Click to collapse
Android models:
Code:
YOGA Tablet 2-830F
YOGA Tablet 2-830L
YOGA Tablet 2-1050F
YOGA Tablet 2-1050L
YOGA Tablet 2 Pro-1380F
YOGA Tablet 2 Pro-1380L
Windows models:
Code:
YOGA Tablet 2-851F
YOGA Tablet 2-851L
YOGA Tablet 2-1051F
YOGA Tablet 2-1051L
When downgrading from 5.0 to 4.4 but fails to enter into the UEFI interface, how to return from UEFI interface to the Android interface.
1, if the BIOS settings have changed, please return all changes, so you need to write down what options were changed.
2, long press the power button to shut down, press and hold the volume + and volume - and power on, enter the FastBoot mode, using data cable connection computer.
3, extract droidboot.img and bootx64 from 5.0 OTA update package, this forum post has given the web link of the firmware, please download it.
4, create a folder named “flash” in the desktop, and then put the extract bootx64 and droidboot.img into the folder, and then create a text document, input “CMD” in the text document and then save, Modify text file txt suffix for bat. Turn off all the useless software!
5, open the new text document.bat, then there will be CMD interface, input
fastboot flash osloader bootx64.efi
and then input
fastboot boot droidboot.img
6, Then the tablet into the driodboot interface, and then in accordance with the downgrade tutorial directly degraded. Be sure to remember to delete a little something in the flash-LtoKK-PVT-810.xml:
Code:
<command>
<string>fastboot erase data</string>
<timeout>120000</timeout>
<retry>2</retry>
<description>Erasing 'data' image.</description>
<mandatory>1</mandatory>
</command>
<command>
<string>fastboot format data</string>
<timeout>120000</timeout>
<retry>2</retry>
<description>Formating 'data' image.</description>
<mandatory>1</mandatory>
</command>
, and then flash flash-LtoKK-PVT-810.xml use flash-LtoKK-PVT-810.xml,
7, when flashed (flash-LtoKK-PVT-810.xml), you will find that the tablet restart card in the logo interface, neglect it and forced shutdown, then press the volume+ and volume- and power to reenter the fastboot mode,
8, and then flash flash.xml, you will return to 4.4.
Thanks Tang1331726 for this detailled tutorial !!
I'm downloading the 1.15GB file over a poor wifi link... but as I understand you are proposing me to downgrade to kitkat.
As I've never rooted my 830F before when in 4.X nor mdified the bios of it, and updated only thru OTA to 5.01 last week, I'm a little confused about what you propose me.
I should use the proposed rooting technique for 5.0
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Using T4 option...
don't you think ?
Thanks Workdowg for the information.
I browsed XDA and google, and ain't find any information about going from Android version to windows and back...
Too bad as my sun wants to try the lenovo concept (form factor is just perfect in my oppinion), but he wants Windows (8-( ...
tang1331726 said:
1? if the BIOS settings have changed, please return all changes, so you need to write down what options were changed.
2? long press the power button to shut down, press and hold the volume + and volume - and power on, enter the FastBoot mode, using data cable connection computer.
3? extract droidboot.img and bootx64 from 5.0 OTA update package, this forum post has given the web link of the firmware, please download it.
4? create a folder named “flash” in the desktop, and then put the extract bootx64 and droidboot.img into the folder, and then create a text document, input “CMD” in the text document and then save, Modify text file txt suffix for bat. Turn off all the useless software!
5? open the new text document.bat, then there will be CMD interface, input
fastboot flash osloader bootx64.efi
and then input
fastboot boot droidboot.img
6?Then the tablet into the driodboot interface, and then in accordance with the downgrade tutorial directly degraded. Be sure to remember to delete a little something in the flash-LtoKK-PVT-810.xml:
fastboot erase data
120000
2
Erasing 'data' image.
1
fastboot format data
120000
2
Formating 'data' image.
1
, and then flash flash-LtoKK-PVT-810.xml use flash-LtoKK-PVT-810.xml,
7?when flashed (flash-LtoKK-PVT-810.xml), you will find that the tablet restart card in the logo interface, neglect it and forced shutdown, then press the volume+ and volume- and power to reenter the fastboot mode,
8?and then flash flash.xml, you will return to 4.4.
Click to expand...
Click to collapse
To be clear. This is to fix the bios error when you upgrade to Lollipop and try to downgrade to KitKat? Also this worked on your 830F?
What's the fuss?!
workdowg said:
Known supported devices:
5) Tick "force sparcing" and change size to 500mb
Click to expand...
Click to collapse
This. I had rooted kitkat on a pal's 830LC. He update to an OTA (lollipop according to him) and got stuck in vicious boot loop. I downloaded YT2-830LC_S0184_150422_ROW and whatever I'd do, flashing system image would fail. Finally, changed force sparcing to 500MB, and suddenly, it's what's all the fuss?!? By the way, Windows 10 x64, used IntelAndroidDrvSetup1.9.0.
Thanks a ton :good:
workdowg said:
To be clear. This is to fix the bios error when you upgrade to Lollipop and try to downgrade to KitKat? Also this worked on your 830F?
Click to expand...
Click to collapse
yes, I had do it three times, all of tried are succeed
workdowg said:
To be clear. This is to fix the bios error when you upgrade to Lollipop and try to downgrade to KitKat? Also this worked on your 830F?
Click to expand...
Click to collapse
Thanks Workdowg, and Thanks tang1331726 for your patience.
My english might be incorrect, but as I per my understanding this fix is when you are stuck and only solution is downgrading from KK to LL.
My situation is somewhat different as I've succesfully ugraded, without any glitch, thanks to the timming Tip warnig (this is a gold one, I wonder how many RMA Lenovo will have to deal with !!)
My exact situation :
830-F
Lollipop OTA succesfully installed (5.01 July 10 2015)
Problem occur using SuperSU (2,40, 2,46, 2,49) after successfully booted tethered recovery.
Can you confirm me that I've to do the process described by tang1331726 to fix the E: signature error, and that I'll still be under Lollipop ?
ps: I guess there's noway to get Windows 8 or 10 on my 830F, altough 851F seems very, not to say tottally, hardawre similar.
pregis said:
Thanks Workdowg, and Thanks tang1331726 for your patience.
My english might be incorrect, but as I per my understanding this fix is when you are stuck and only solution is downgrading from KK to LL.
My situation is somewhat different as I've succesfully ugraded, without any glitch, thanks to the timming Tip warnig (this is a gold one, I wonder how many RMA Lenovo will have to deal with !!)
My exact situation :
830-F
Lollipop OTA succesfully installed (5.01 July 10 2015)
Problem occur using SuperSU (2,40, 2,46, 2,49) after successfully booted tethered recovery.
Can you confirm me that I've to do the process described by tang1331726 to fix the E: signature error, and that I'll still be under Lollipop ?
ps: I guess there's noway to get Windows 8 or 10 on my 830F, altough 851F seems very, not to say tottally, hardawre similar.
Click to expand...
Click to collapse
You are very welcome!
As far as the "E: signature error" please try posting in the Intel tethered recovery thread. Those guys should be able to help. Some people had luck by placing the SuperSU zip on the MicroSD and installing from there. Also try using the another recovery. I use TWRP on my 1050F.
We are trying to get Windows and/or Linux running on these Android based YT2's. Keep looking back here for more info...

yoga 2 1050F can only access BIOS, let's go to RMA?

Hello everybody, I was trying to revert to a 4.x rom because bluetooth tethering was not working... anyway I used Intel Phone Flash Tool and it seems like he failed to flash boot.bin but restarted anyway
SO I only have the Intel BIOS, I can access all the settings, but I cannot start it in Fastboot mode (it just hangs on FastBoot Starting...) or anything that resembles Android.
Still this BIOS seems more a PC to me than a tablet so I am posting here because maybe there is someway to attach an USB OTG (for example) and boot something from there.
@ionioni is working on a safe downgrade path. We did mine but it could be a disaster if not followed correctly. Your other choice is Lenovo repair support. When i bricked mine, it only took 6 days to get it back in my hands. You could also try the steps here... http://forum.xda-developers.com/showpost.php?p=62237383&postcount=5
Sent from my YOGA Tablet 2-1050F
Thank you very much @workdowg, I passed by that thread, just "DNX" mode does not work on my tablet.
So Repair Support it is.
It's very sad such an awesome tablet has so poor ROM that people has to downgrade it...
Mr.Gamer said:
................but I cannot start it in Fastboot mode (it just hangs on FastBoot Starting...) ..............
Click to expand...
Click to collapse
that is DNX mode!!! that message translates to: i DNX have started and now i am waiting for YOU to give me a (fast)boot image to start... so that message is exactly the message indicating that you ARE in dnx mode.
updated: read this http://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-2-830-1050-1380-to-kitkat-t3240487
edit:
before anything:
1. download/extract the files attached to this post, now start your tablet (using the Pwr+VolUp+VolDown) to get to that somehow confusing "Fastboot starting..." message = DNX mode (you must get to that message before continuing!)
2. run the extracted tmp-root-1050F-lollipop.exe file (i am assuming you are on the X64 = Lollipop firmware as that screen pictures you attached shows), should do some stuff and in the end if all well will drop you to a root shell (in that post theres a PrtScr for reference), just follow the messages it's pretty easy. should the exe get stuck/not work put your tablet again in DNX mode and try the other file tmp-root-1050F-kitkat.exe. (this means somehow the bios got downgraded partially on your attempt to return to kitkat). this is just a test to see how to move on, it will not fix nor change anything on your tab, after you reboot it will be in the same state as before (that is if you don't do stuff in that root shell of course)
- report back which one worked (gived you a shell)
- also do you want to go back on kitkat or do you want to stay on lollipop? is important to know as the steps are different

Need help for bricked oneplus two

Hi,
I had updated my oneplus two with cyanogenmod 13 successfully. I had been running this for more than 5 months.
Yesterday i had downloaded an update of CM13 and was trying to install the update, the phone just went blank with a black screen so i restarted the phone. Since then the phone is not loading into the OS, when i try restarting the phone the oneplus logo screen just flashes and then the phone just displays black screen or switches off.
I am not able to enter into recovery mode which is the biggest problem i am facing due to which i am not able to even perform other recovery options.
I connect the phone to computer using usb and when i use any command such as adb devices, i dont see any device in the list. i get error: no devices when i use other adb commands.
I tried using QFIL from quallcom, but i get the below error when i click the download button:
Process Index:0
Programmer Path:E:\8675_W00\prog_emmc_firehose_8936.mbn
Image Search Path:E:\8675_W00
Please select the XML file
Invalid image search path, ignored
Start Download
Program Path:E:\8675_W00\prog_emmc_firehose_8936.mbn
COM Port number:11
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
---------------------------------------
Please help me in unbricking the oneplus two.
Solved?
Hi md vasi, you can try the methond on the oneplus community search for "unbrick Oneplus 2", choose "[Q&A] The Ultimate OnePlus 2 Guide - Solutions e.t.c.", go to "how to unbrick".
I've also a bricked OP2 that has same issues as yours, happened exactly the same way it happened to you but while updating Resurrection Remix Mod. I've unfortunately not managed to unbrick my device. Hope you it will work for you, please follow the procedure step by step and keep me posted if you can unbrick your OP2 and tell me how you did it. Ok?
Good luck buddy:good:
axaman943 said:
Hi md vasi, you can try the methond on the oneplus community search for "unbrick Oneplus 2", choose "[Q&A] The Ultimate OnePlus 2 Guide - Solutions e.t.c.", go to "how to unbrick".
I've also a bricked OP2 that has same issues as yours, happened exactly the same way it happened to you but while updating Resurrection Remix Mod. I've unfortunately not managed to unbrick my device. Hope you it will work for you, please follow the procedure step by step and keep me posted if you can unbrick your OP2 and tell me how you did it. Ok?
Good luck buddy:good:
Click to expand...
Click to collapse
were you able to unbrick your OPT?
phorcus said:
were you able to unbrick your OPT?
Click to expand...
Click to collapse
Yep, the most important is that you find the right driver for Snapdragon 810, i can't recall where i found the link, it took me a while, wait... i got it, i've found the right driver's link on a website named Android brick or something, with the right driver the flash tool from OP2 will recognise your device and flash stock build.
good luck
axaman943 said:
Yep, the most important is that you find the right driver for Snapdragon 810, i can't recall where i found the link, it took me a while, wait... i got it, i've found the right driver's link on a website named Android brick or something, with the right driver the flash tool from OP2 will recognise your device and flash stock build.
good luck
Click to expand...
Click to collapse
gfil is giving me this error:
COM Port number:5
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:Unable to download Flash Programmer using Sahara Protocol
Download Fail:Sahara FailSahara Fail
Finish Download
and msm tool is also giving me error but since its in chinese i cannot understand them, do you have any other ways to unbrick OPT

[GUIDE] Unbrick X82x Le Max 2, Factory Restore, Reset, Qualcomm HS-USB QDLoader 9008

Hi all,
After reading on letv.re that some people managed to brick their devices and were looking for a fix, I started to check more and more about the issue. What happened to some was that the phone would switch itself off and enter into Qualcomm Recovery Mode and would be seen when connected to a computer as “Qualcomm HS-USB QDLoader 9008”. For others, by flashing wrong files the phone would end up in the same state. Luckily a fix had been found, and it was shared by ParasiTe_RemiX.
DISCLAIMER
Given that maybe nothing will happen to your warranty and this is an unbricking tool, there are small chances that your device might get bricked for good, and I feel the need to say that I am not responsible for any damage caused by following these instructions. Any modification that you do to your phone you're doing at your OWN RISK.
Keep in mind that if your phone goes by itself in the QDLoader mode, it’s better to try some combinations below before flashing it using this method:
1) Keep the power button pressed for about 2 minutes, or
2) Keep the power button + Vol up pressed for about 2 minutes, or
3) Keep the power button while connecting the phone to a wall charger, or
4) Bring the phone into a bright light and press the power button (or power button + Vol up) for about 2 minutes, or
5) Keep the phone charging for more than 24 hours and repeat all the steps above.
If nothing works and you are willing to fix it and you’ll give up all your files, then this fix is for you. Or if you have flashed some wrong files and there is no Fastboot, nor Recovery, this is to be followed. Or if you want to reset your phone to a “factory state”, this is the way to go, and by that I mean if you want to check that your fingerprint sensor is working, or you have some other issues, it’s good to revert it this way.
What you will need:
a) A Windows computer
b) FlashOne program - the flashing program for the software
c) QFIL files for X820 (looks like some dev software dating April,2016)
IMPORTANT – YOU WILL LOSE ALL YOUR FILES ON THE PHONE, PHOTOS, MUSIC, APP DATA, INTERNAL STORAGE WILL BE WIPED.
So if your phone is in this Qualcomm Recovery mode, you can just connect it to the computer, and jump to step 3, if not, and you simply want to flash it, start from step 1.
1) To enter Qualcomm Recovery mode, first turn off the phone and go to step 2
2) Keep pressed Vol Up (+) and Vol Down (-) together and connect the phone by USB cable to the computer.
3) You will see that the computer will install drivers for "Qualcomm HS-USB QDLoader 9008".
4) Unzip FlashOne and start "main.exe". Once you've opened the flashtool you'll see "Flash Type". Here select "Qualcomm - flash dead phone".
5) Select your phone - "COM ..." from "Select device" - here should be the same COM ... as it shown in Device Manager under Ports (COM & LPT) > "Qualcomm HS-USB QDLoader 9008 (COM ...)"
6) Select File "LeMax2QFIL.zip" from the folder where it is saved
7) Press "Flash" in the lower part of the window
8) Once completed, disconnect the phone and power it up
9) Go to Settings – Storage format the internal storage.
To exit the Qualcomm Recovery mode, keep the Power Button pressed for about 1 minute or until the phone will vibrate and restart into system.
That's it. More info you will find in FlashOne program, actually it's almost like I've described it here.
You will be reverted to a "dev" version of the phone, somewhere with April build date. Keep in mind that it's EUI 5.6 and the kernel is different than EUI 5.8. Update it to latest EUI with stock recovery and then install the custom recovery of your choice.
Most of the guys install a recovery for 5.6 on EUI 5.8 or vice versa and then they get the blue LED. That's why you should read the instructions for each recovery and make sure you know which one you're flashing.
Download files:
Mega:
https://mega.nz/#F!0gwgxbxD!-iud2O-6uZ0F3Geofz-NyA
Google Drive:
FlashOne:
FlashOne1.9.zip
drive.google.com
QFIL:
Lemax2QFIL.zip
drive.google.com
TWRP: https://forum.xda-developers.com/le-max-2/development/twrp-root-14s-rom-x820-t3382221
https://mega.nz/#!Jl4DATLI!Z08l-0SWc98C1qUGDEOcTsj96DlY627B7nHtlKCp6qw
https://mega.nz/#!slYmEJ6K!Onc5pjb3teB9J6AunZnEe-k6mDJwQ2tQwUt0X51AudI
Stock Recovery (not tested) and needs an EUI ROM to be instaled as update.zip:
https://mega.nz/#!B0ZGgSQB!33UG9jpEL6b_zJm4M01yRpI0x4uHA4Q1XzaS0ntXVSI
Edit: Post updated.
Thanks
Hi
First of all I want to thank you for posting this solution. Yesterday I managed to solve it too but it took me a while to find all this info.
Now I have ran into annother problem, I am not able to flash any rom from the stock recovery, it says "file corrupted" every time.
Any solution to this?
rapiteu said:
Hi
First of all I want to thank you for posting this solution. Yesterday I managed to solve it too but it took me a while to find all this info.
Now I have ran into annother problem, I am not able to flash any rom from the stock recovery, it says "file corrupted" every time.
Any solution to this?
Click to expand...
Click to collapse
Honestly, I did this restoration of the phone about a month ago. I encountered some issues with the stock recovery but I can't remember what I did to fix it. I think I installed 017s at that time, directly from the dev software. Restarting the phone to recovery I think didn't work. I believe you should turn it off and then start it to recovery directly. I remember I wanted to download 015s, 016s, and even I gave up and wanted to install TWRP for 5.6 EUI but the stock recovery at some point worked. Try to turn off the phone (not restart) and then switch on in recovery. And check erase data as well.
valy_cta said:
1) To enter Qualcomm Recovery mode, turn off the phone. Keep pressed vol up and vol down and turn on the device by pushing the power button.
Click to expand...
Click to collapse
Hello, I just wanted how does it look to see the phone in its normal state but cannot switch it on againg form normal opration. Is there eny key combination. It looks like bricked just now
regard Filozof71
OK, it works. Need press power button ober one minute. Uff
Leeco X910 brick
Hello, my leeco x910 is bricked...
Black screen, no led, no sound nothing just usb connection is ok for flashing 9008 mode..
Is possible to obtain the good .mbn file for flashing?
Please help me
Best regards
valy_cta;69439085
1) To enter Qualcomm Recovery mode said:
Hello, I'm on Windows 7, I enter #3 point above but I can see only QUSB_BULK device under devices manager but Windows 7 does not have any drivers for it. I tried to dwonload some but withous success. Has anybody runover rhis instruction? Uder which Windows version?
OK. Under Windows 10 it works means it installs the phone as Qualcomm HS-USB QDLoader 9008 and its visible in FlashOne program.
Great appreciation to valy_cta!
regards Filozof71
Click to expand...
Click to collapse
Problem
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
slawin wynterz said:
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
Click to expand...
Click to collapse
The link of this file is corrupted, you could post the site link. where the file is. I'm grateful.
link
bruno araujo said:
The link of this file is corrupted, you could post the site link. where the file is. I'm grateful.
Click to expand...
Click to collapse
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg
UP
UP
slawin wynterz said:
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg
Click to expand...
Click to collapse
slawin wynterz said:
UP
Click to expand...
Click to collapse
He fixed his phone finally.
OP updated.
slawin wynterz said:
drive.google.com/drive/folders/0BzteXVVFgQLpZndPRmhDNDJiXzg[/QUOTE
thank you, now I could install clean ROM
Click to expand...
Click to collapse
hard brick LeEco Le Max 2
hello,
thanks for the guide,
I installed the Lemax2QFIL but then
I can not istall any rom.
I renamed the various rom in update but the system responds file corrupted every time.
beachboys1970 said:
hello,
thanks for the guide,
I installed the Lemax2QFIL but then
I can not istall any rom.
I renamed the various rom in update but the system responds file corrupted every time.
Click to expand...
Click to collapse
Reboot phone, after power on one time flash it.
Did you find a fix for this? I am struggling with Lemax x910
slawin wynterz said:
My phablet give me problem.
Log:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_ddr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
what am I doing wrong?
Click to expand...
Click to collapse
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
valy_cta said:
He fixed his phone finally.
OP updated.
Click to expand...
Click to collapse
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
bil20 said:
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
Reboot phone (long press volume "-"), after power on (long press volume "+" "-" and power) and just one time flash it.
bil20 said:
Hi,
Did you find a fix for this? It seems like you resolved the error somehow. Would you be willing to share how you did that please? I would be extremely grateful. I continue to see the above errors as well.
---------- Post added at 03:27 AM ---------- Previous post was at 03:22 AM ----------
Do you know how he fixed it? I also continue to see the exact same error on the lemax pro x910 and I have pretty much exhausted my options at this point in time. Your help would be extremely appreciated.
the error that I see is as follows:
13: c:\FlashOne1.9\Lemax2QFIL\prog_ufs_firehose_8996_d dr.elf
19:17:45: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:17:45: ERROR: function: sahara_main:854 Sahara protocol error
19:17:45: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
Click to expand...
Click to collapse
I don't think that you can flash a X910 with X820 files, although I never tried and never heard someone to do so, the results might not be too good.
That error was due to the fact that he was not pressing the buttons properly before connecting to computer. Keep Vol up and Vol down and connect the phone. It should be switched off before.
Good luck!
Thanks very much
How would I switch off a hard bricked device? Every time I connect the device, the device manager shows that it's been connected "Qualcomm ------ 90008" so how would I turn it off , especially if the battery is embedded?
Can you press the power button for at least 1 minute?
If you have it connected and it shows in computer as Qualcomm... 9008, it's ok. Maybe the files are detected as not being for your phone.
If you suddenly found the phone in such way and you didn't flash something that broke it, try to restart it as shown in the op. If not, try to discharge the battery fully that to flash something that it doesn't belong.
bil20 said:
How would I switch off a hard bricked device? Every time I connect the device, the device manager shows that it's been connected "Qualcomm ------ 90008" so how would I turn it off , especially if the battery is embedded?
Click to expand...
Click to collapse
I just long press button "-" and it diconnected after 15-20 sec.

Mi A1 QPST Backup file

Hi guys,
Anyone got a full qualcomm backup of their mi A1? I've suffered power failure during Mi Flash and it seems it corrupted the whole memory and altho it's in download mode(I get it to qualcomm 900E and 9008 ports), I think the only solution is full phone factory image backup since if I try with Mi Flash or QPST I get the Sahara error 9 regardless of what programmer (prog_emmc_firehose) I try.
It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.
Kindly do an extend tutorial... And tag me please, if you decide to.
Thanks.

Categories

Resources