Q&A for [GUIDE][K920] Unlock bootloader on Lenovo VIBE Z2 Pro
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][K920] Unlock bootloader on Lenovo VIBE Z2 Pro. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Great guide, Electry.
I just used the QFil to unbrick my phone.
My phone hung at the bootup logo after the latest update. I think it was because I didn't unroot before update.
Nice to see some development on this great phone.
Tried to unlock bootloader but its not success
Hi supporter!
I tried to unlock bootloader my K920 China mobile version (OTA to 5.0.2, vibeUI2.5)
but i can't dial *#*#8899#*#* because it not appear pop-up dialog
I was setup driver, but Device Manager is not have the "Modem" to show "Lenovo HS-USB modem phone", the "Port" is not show "Lenovo HS-USB Diagnostics" and "Lenovo HS-USB NMEA" too.
pls help!
Thanks!
ps. sorry about my English
buidinhhai said:
Hi supporter!
I tried to unlock bootloader my K920 China mobile version (OTA to 5.0.2, vibeUI2.5)
but i can't dial *#*#8899#*#* because it not appear pop-up dialog
I was setup driver, but Device Manager is not have the "Modem" to show "Lenovo HS-USB modem phone", the "Port" is not show "Lenovo HS-USB Diagnostics" and "Lenovo HS-USB NMEA" too.
pls help!
Thanks!
ps. sorry about my English
Click to expand...
Click to collapse
You could try skipping step 8. and 9. in "Preparation" section, as I'm not sure if enabling diagnostic mode is really needed. Simply continue with the guide and let me know how it worked
I don't know unlocked BL or not
Electry said:
You could try skipping step 8. and 9. in "Preparation" section, as I'm not sure if enabling diagnostic mode is really needed. Simply continue with the guide and let me know how it worked
Click to expand...
Click to collapse
I press volume- and plug in the cable, the Device Manager show all port such as the upon post. But when i tried to flash , the QFil show this :
Start Download
COM Port number:6
Switch To EDL
Download Fail:Switch To EDL FailSystem.Exception: Fail to find QDLoader port after switch
в QFIL.Tech.DownloadTech.GetPortAfterReset(String description, Int32 timeoutInSec)
в QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Then i've tried to unlock
(press volume + and plug in the cable to see Qualcomm HS-USB QDloader 9008)
the QFil show this :
Process Index:0
Programmer Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
Image Search Path:C:\VibeZ2Pro_UnLock_BootLoader_L
Please select the XML file
Start Download
Program Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:3
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Request payload size 0xc000 is not the same as support payload size, change to 0x20000
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0xB1EA0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x54c
PROGRAM: Partition 0, Sector: 264232, Length: 1356 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\emmc_appsboot.mbn
PROGRAM: Written Bytes 0xa9800 (64)
Program Size: 0.66 MB
Total Size: 0.69 MB
Total Size: 0 Seconds
PATCH: Partition 0, Sector: 7, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 0,6948242MB
Throughput: 0M/s
Reset Phone
Waiting for reset done...
Let me know was i unlocked bootloader ?
is there the code or other method to test the Lenovo-phone's status of the bootloader?
buidinhhai said:
Let me know was i unlocked bootloader ?
is there the code or other method to test the Lenovo-phone's status of the bootloader?
Click to expand...
Click to collapse
It looks like you did it
If you have Lollipop, you can check it by doing "One-Time boot" into TWRP recovery. It should boot without an error.
Guide here: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-6-1-sevenmaxs-t3086999
thanks to Electry
Electry said:
It looks like you did it
If you have Lollipop, you can check it by doing "One-Time boot" into TWRP recovery. It should boot without an error.
Guide here: http://forum.xda-developers.com/android/development/recovery-twrp-2-8-6-1-sevenmaxs-t3086999
Click to expand...
Click to collapse
Finally, i unlocked bootloader and up rom 4.4.2. Now, my phone has google service and my language - Vietnamese.
Thanks for your help, @Electry.
I have the same message, but my problem is that, That I have problem with OS. They not loaded. Telephone booting until logo, vibration and rebooting.
Was lolipop 5.0.2 untill it. Errors the same
PATCH: Partition 0, Sector: 7, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 2051,244MB
Throughput: 15,
Great giude friend
Hello to everybody !!
Also my Lenovo S856 is bricked. This happened because the recovery did not allow to make mods (backup, restore ..) but only wipes, and I thought it depended on the locked bootloader. At that point, I used the app EzUnlock and yet the phone is bricked, it does not turn on, no recovery, no sign of life, and it is seen as Qualcomm HS-USB Dignostics 9006 (COM3).
My seller sent me a rom to make the flash with MiFlash but the process crashes after 4 seconds. I also tried the QFIL tools and even then the process crashes with the message "Download Fail: Switch To FailFireHose Fail.
Any suggestions ?
Thanks for help
Electry said:
You could try skipping step 8. and 9. in "Preparation" section, as I'm not sure if enabling diagnostic mode is really needed. Simply continue with the guide and let me know how it worked
Click to expand...
Click to collapse
Am stuck in an error
Reset Phone
Waiting for reset done...
Download Fail:FireHose Fail Fail to find QDLoader port after switch
Finish Download
then phone boots in normal mode. Please help.
Supersu needs binary update and i also cant update it. Plz Help
Hello,
Everytime I try this method I am getting the below error
Process Index:0
Programmer Path:C:\Users\user\Downloads\UnlockBootloader_LP_ROW\UnlockBootloader_LP_ROW\prog_emmc_firehose_8974.mbn
Image Search Path:C:\Users\user\Downloads\UnlockBootloader_LP_ROW\UnlockBootloader_LP_ROW
Please select the XML file
Start Download
COM Port number:7
Switch To EDL
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Please let me know what can be done.
Note : I am on Lenovo Vibe z2 Pro Stock rom build S288[rooted]
Issue resolved.. Thank you
Any idea how to unlock bootloader of lenovo vibe P1 with mm6.0.1
Sent from my Lenovo P1a42 using XDA-Developers mobile app
buidinhhai said:
I press volume- and plug in the cable, the Device Manager show all port such as the upon post. But when i tried to flash , the QFil show this :
Start Download
COM Port number:6
Switch To EDL
Download Fail:Switch To EDL FailSystem.Exception: Fail to find QDLoader port after switch
в QFIL.Tech.DownloadTech.GetPortAfterReset(String description, Int32 timeoutInSec)
в QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Then i've tried to unlock
(press volume + and plug in the cable to see Qualcomm HS-USB QDloader 9008)
the QFil show this :
Process Index:0
Programmer Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
Image Search Path:C:\VibeZ2Pro_UnLock_BootLoader_L
Please select the XML file
Start Download
Program Path:C:\VibeZ2Pro_UnLock_BootLoader_L\prog_emmc_firehose_8974.mbn
COM Port number:3
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Ack Raw Data:False
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:3
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
Request payload size 0xc000 is not the same as support payload size, change to 0x20000
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
Total Bytes To Program 0xB1EA0
Download Image
PROGRAM: Partition 0, Sector: 0, Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_backup0.bin
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\gpt_main0.bin
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Replace the partition sectors number 0x1000 to file size in sector 0x54c
PROGRAM: Partition 0, Sector: 264232, Length: 1356 Sectors, Sector Size: 512 Bytes
File: C:\VibeZ2Pro_UnLock_BootLoader_L\emmc_appsboot.mbn
PROGRAM: Written Bytes 0xa9800 (64)
Program Size: 0.66 MB
Total Size: 0.69 MB
Total Size: 0 Seconds
PATCH: Partition 0, Sector: 7, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 168 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 0, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
PATCH: Partition 0, Sector: 0, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,3072)
PATCH: Partition 0, Sector: 0, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,3072)
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: 0
PATCH: Partition 0, Sector: 0, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
Total download file size: 0,6948242MB
Throughput: 0M/s
Reset Phone
Waiting for reset done...
Let me know was i unlocked bootloader ?
is there the code or other method to test the Lenovo-phone's status of the bootloader?
Click to expand...
Click to collapse
Dear after that remove the cable & also remove the battery of phone . put any ota zip "Hungary2Default.ota" OR better "HongKong2Default.ota" in Sd Card & apply update from sd card option
this worked for me
adithebratt said:
Issue resolved.. Thank you
Click to expand...
Click to collapse
able to share how you resolved that?
i sort of unlocked bootloader (based on the comment from the earlier posts) but I failed to flash TWRP to the phone, always "waiting for device"
Issued resolved with another USB cable (my 3rd USB cable that I hardly use)
Hi all,
First of all I wanted to thank baikal0912 from lenovo-forums.ru , without Him this guide haven’t been possible, so all the glory and kudos go to Him in first place. (baikal0912 if You’re reading this – Thank You once again)
THIS GUIDE IS FOR LENOVO YOGA TAB 3 YT3-850L! AS ALWAYS I’M NOT RESPONSIBLE FOR DAMAGED DEVICES AND LOST DATA! ALWAYS MAKE BACKUP! (DON’T MAKE MY MISTAKES)
SOME HISTORY (read if You want to know how I bricked my device)
I had stock 5.1.1 Android on my Yoga, tablet has been updated to 6.0.1 in which i had problems with writing to SDCard (permissions), so I managed to unlock bootloader, flash TWRP, install Xposed and SDFix. Sadly after some time I saw that randomly applications disappeared (like Google Play Store).
So I was searching for 5.1.1 ROM (because I didn’t had any backup), only 2 ROM’s where available to download and it was for „M” model (YT3-850M) not „L”. First ROM was 785MB – it was only Chinese/English language, after flashing my device I saw that my LTE didn’t work, WIFI, BT, GPS and Sound doesn’t work either.
So I tried second ROM downloaded for „M”, It was 1,2GB and there were all languages available, but still LTE, WIFI, BT, GPS and Sound didn’t work.
I was searching for some info about my problem and manager to go to lenovo-forums.ru where I find out It’s because missing/damaged NVRam data (the data where tablet stores IMEI, Mac address and other stuff)
Surely It was my fault because I didn’t do any backup in first place (and yes, I’m an idiot)
Trying to find NVRam backup (in .QCN file) I ended in lenovo-forums.ru talking with baikal0912, He shared with me stock „L” ROM and trying to help me flash the device back again, so I made this topic because there is a problem finding „L” ROM and so everyone know how I flashed my device (which tools and drivers are needed, which mode to enter to flash device.
So let’s get started….
First, if Your tablet boots to Android make sure it has ADB debugging enabled (If You want to know how to enable ADB debug search the forum, there are plenty of answers)
Second make sure You grab SIMCard from device (You’ll gonna insert it later at end of my guide)
GRAB ALL THE NEEDED FILES: (ROM is 1GB 7zip compressed)
Code:
https://drive.google.com/drive/folders/0B2EmK9gw0mTdYUdJUGlDUm0zTW8?resourcekey=0-1iw6MlGugBOz6J5sDQRcaw&usp=sharing
You will need ROM (YT3-850L_S000026_151217_ROW_qpst.7z), QPST v2.7.429 (QPST_2.7.429.7z), drivers (Qualcomm USB Drivers For Windows.zip and Qualcomm_USBDriver_2.1.0.5_x64.cab), IMEI writing software (A100_WriteDualIMEI(W+G_eMMC).rar).
Also You are going to need ADB tools, search for them here at XDA (minimal ADB and fastboot).
NOTE: I’ve been trying to restore ROM with other QPST version and drivers without any success.
Install QPST, extract ROM to „C:\Lenovo” then connect turned on Yoga to PC, there should be 3 new devices shown in device manager named YT3-850M (in my case it was „M”, Yours can be „L”), install drivers from „Qualcomm USB Drivers for Windows.zip”, Windows should install two of them (modem fails to install, just ignore), the most important is device installed as „Lenovo HS-USB Diagnostics (COMx)” where X is Your COM port numer needed LATER.
ENTER FLASHING MODE
For now run ADB command to check if Your device is recognized:
Code:
adb devices
If It’s recognized then command will show You some numbers, if You’re ready to go then run this command:
Code:
adb reboot edl
Above command will change Android to something I call „Flashing Mode” (the screen on tablet will be black), for now tablet is waiting for flashing, You should now see that device manager in Windows shows only one new devices o install from „Qualcomm_USBDriver_2.1.0.5_x64.cab”, the device manager should install „Qualcomm HS-USB QDLoader 9008 (COMx)”, note the COM port X needed to flash.
Others at forums tell me to enter „Diagnostic Mode” to start flashing but they were wrong, „Diagnostic Mode” is something else needed later.
FLASH THE DEVICE
Run QFIL.exe from installed QPST directory (c:\Program Files (x86)\Qualcomm\QPST\bin\), make sure to run with Administrator privileges (from right click context menu).
Code:
- Make sure that QFIL recognized Your device showing „Qualcomm HS-USB DQLoader 9008” with COM port numer at top of QFIL screen.
- Select FLAT BUILD
- In „Programmer Path” choose „Browse”, go to extracted ROM directory and choose file named „prog_emmc_firehose_8909_ddr.mbn”
- Click on „LoadXML” below on right, choose „rawprogram0” file, then choose „patch0” file
If You are 100% sure You want to flash then press blue „Download” button and wait to finish flashing (don’t disconnect or turn off tablet before it ends).
You should notice that in „Status” window in QFIL there should be LOG, here’s my example of LOG file (shortened, doesn't fit all):
Start Download
Program Path:C:\lenovo\prog_emmc_firehose_8909_ddr.mbn
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
FireHose Log: [email protected] [email protected]
Request payload size 0xc000 is not the same as support payload size, change to 0x100000
Request payload size 0x100000 is too big, reduce to 0x20000
FireHose Log: [email protected] [email protected]
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x86846CA0
Download Image
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1e3
PROGRAM: Partition 0, Sector: 40, Length: 483 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\sbl1.mbn
FireHose Log: start 40, num 483
FireHose Log: Finished sector address 523
PROGRAM: Written Bytes 0x3c600 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1e3
PROGRAM: Partition 0, Sector: 1064, Length: 483 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\sbl1.mbn
.......
.......
.......
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 7799808, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_8.img
FireHose Log: start 7799808, num 16
FireHose Log: Finished sector address 7799824
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 7800712, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_9.img
FireHose Log: start 7800712, num 16
FireHose Log: Finished sector address 7800728
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8061952, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_10.img
FireHose Log: start 8061952, num 16
FireHose Log: Finished sector address 8061968
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8324096, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_11.img
FireHose Log: start 8324096, num 16
FireHose Log: Finished sector address 8324112
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8325000, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_12.img
FireHose Log: start 8325000, num 16
FireHose Log: Finished sector address 8325016
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8586240, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_13.img
FireHose Log: start 8586240, num 16
FireHose Log: Finished sector address 8586256
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8848384, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_14.img
FireHose Log: start 8848384, num 16
FireHose Log: Finished sector address 8848400
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8849288, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_15.img
FireHose Log: start 8849288, num 16
FireHose Log: Finished sector address 8849304
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9110528, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_16.img
FireHose Log: start 9110528, num 16
FireHose Log: Finished sector address 9110544
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9372672, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_17.img
FireHose Log: start 9372672, num 16
FireHose Log: Finished sector address 9372688
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9634816, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_18.img
FireHose Log: start 9634816, num 16
FireHose Log: Finished sector address 9634832
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9896960, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_19.img
FireHose Log: start 9896960, num 16
FireHose Log: Finished sector address 9896976
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9901032, Length: 218048 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_20.img
FireHose Log: start 9901032, num 218048
FireHose Log: Finished sector address 10119080
PROGRAM: Written Bytes 0x6a78000 (64)
Program Size: 106.47 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\gpt_main0.bin
FireHose Log: start 0, num 34
FireHose Log: Finished sector address 34
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: NUM_DISK_SECTORS-33., Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\gpt_backup0.bin
FireHose Log: start 30535647, num 33
FireHose Log: Finished sector address 30535680
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
Total Size: 2155.12 MB
Total Time: 265 Seconds
Throughput: 8.13 MB/Seconds
PATCH: Partition 0, Sector: 9, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 9 with 01D1EFDE
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-26., Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 30535654 with 01D1EFDE
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 1 with 01D1EFDE
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 30535679 with 01D1EFDE
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 1 with 01D1EFFF
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 30535679 with 01D1EFFF
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
FireHose Log: Patched sector 30535679 with 01D1EFDF
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,4096)
FireHose Log: crc start sector 2, over bytes 4096
FireHose Log: Patched sector 1 with 7315C503
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,4096)
FireHose Log: crc start sector 30535647, over bytes 4096
FireHose Log: Patched sector 30535679 with 7315C503
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 1 with 00000000
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
FireHose Log: crc start sector 1, over bytes 92
FireHose Log: Patched sector 1 with 2EB8C0BF
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 30535679 with 00000000
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
FireHose Log: crc start sector 30535679, over bytes 92
FireHose Log: Patched sector 30535679 with B8615551
Total download file size: 2155,119MB
Total download time: 4 Min 26 Sec
Throughput: 8,096117MB/s
FireHose Log: Set bootable drive to 0.
Download Succeed
Finish Download
If there’s „Download Succeed” and „Finish Download” in LOG You could try to boot new ROM holding POWER button, the first boot should take some time, after boot don’t install any apps, we need to change IMEI before we use tablet.
CHECK IMEI
After booting check Your IMEI numer if exists in NVRam, go to „CONTACTS”, click „Search” magnifier button, enter:
Code:
*#06#
If IMEI is good, skip to „Region Change” guide.
If IMEI is 0 then note Your IMEI from the „Standing Plate” of Your tablet.
WRITING IMEI
First shut down tablet, boot with holding „POWER” „+” and „-„ buttons, there should show something I call „Diagnostic Mode”, there will be some tests like:
Code:
1 SYSTEM INFO
2 KEYPAD BACKLIGHT
3 LCD BACKLIGHT
…..
…..
You should connect tablet to PC, and if You previously installed „Qualcomm USB Drivers For Windows.zip” drivers, then run WriteDualIMEI(W+G_eMMC).exe as Administrator.
Program will auto detect COM port, there will be two fileds (IMEI1, IMEI2), just insert Your IMEI in BOTH FIELDS, click START, wait to program show PASS.
If it pass, disconnect tablet from USB, click on REBOOT in „Diagnostic Mode”, choose „(3) Reboot to Android”, hit „OK”
After booting check IMEI number as mentioned above, if it’s ok then last thing to do is…
CHANGE REGION CODE
To change region code, to the same as checking IMEI but with other code, so go to „CONTACTS”, click „Search” magnifier button, enter:
Code:
####682#
Region changing settings should appear, at top there is Your currently selected region, below You can choose new region, note that after changing region Android should reboot.
For now shut down Android, insert SIMCard, and enjoy.
That’s all, thanks for reading, I hope this guide will help someone like baikal0912 :good: helped me.
Regards.
P.S. If someone know how to enter „Flashing Mode” in other way than „adb reboot edl” let me know so I can update this guide (maybe there is someone who can’t boot device and enter „Flashing Mode” via ADB)
P.S.2. Flashing done under Windows 10 Home 64 bit, connected to USB 2.0
P.S.3. I haven't done Serial Number (SN) writing to tablet, don't know how.
P.S.4. Sorry for my bad English
I cant install the drivers automaticly because I dont have a working Yoga Tab. I just can boot into fastboot mode. I run "fastboot devices" and therre it is, but not with "adb devices". My device manager knows my tablet and tell me "Android Bootloader Interface" when I connect the tablet. If I try to update the driver it says they are allready installed.
Rookie1919 said:
I cant install the drivers automaticly because I dont have a working Yoga Tab. I just can boot into fastboot mode. I run "fastboot devices" and therre it is, but not with "adb devices". My device manager knows my tablet and tell me "Android Bootloader Interface" when I connect the tablet. If I try to update the driver it says they are allready installed.
Click to expand...
Click to collapse
Have You try "fastboot boot recovery.img" to boot recovery?
Do You have recovery.img?
If You have problem entering "Flashing Mode" (via "adb reboot edl"), You can try this link with patched fastboot to support rebooting to edl, I didn't test it, someone can try....
https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
I connected the pad while i pressed Vol-. Then I used the exe in the new fastboot thing. Then I did this:
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb reboot edl
error: no devices/emulators found
Rookie1919 said:
I connected the pad while i pressed Vol-. Then I used the exe in the new fastboot thing. Then I did this:
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb reboot edl
error: no devices/emulators found
Click to expand...
Click to collapse
So if You maneged to run new fastboot exe to boot to edl, the screen should be black on Yoga (and device is in "Flashing Mode", check device manager in Windows, You should install driver from „Qualcomm_USBDriver_2.1.0.5_x64.cab”, the device manager should install „Qualcomm HS-USB QDLoader 9008 (COMx)” device.
Next You should do the flashing by QFIL as described in my tutorial above.
In my tutorial I was using adb to boot to edl ("Flashing Mode") because my tablet was booting, as I understand Your tablet don't boot anywhere beside fastboot, so You must enter edl ("Flashing Mode") via fastboot without using adb (adb should work only if You boot tablet)
Doestn work. I booted to recovery and tried a factory reset. Then the message "couldnt mount system" appears. Could this be the problem? And how coult I solve this?
Hmmm, I think its because of damaged system, dont know how to help (Im not Android pro), if internal storage isnt damaged then only way I know is to flash ROM via QFIL, and for that You must enter edl ("Flashing Mode") either with adb, fastboot or booting with some magic key combination.
Unless You enter edl You couldnt flash device, try in recovery mode if adb is working to boot edl.
I don't know exactly where to post I just need the plain stock image of the yt3 x50f ROW so I can put it on the tablet I somehow got a PRC CN ROM on it and now no Google apps or anything just the zip file I need to place on the SD card is all I need I've looked everywhere spent all night I'm surprised I havnt bricked it I found 1 but qfil or qdloader wouldn't put it on the tablet I just want my tablet back.....
Dont know exactly why, but i managed it to run. Now all is fine. Thx 4 your help.
tapayn02 said:
I don't know exactly where to post I just need the plain stock image of the yt3 x50f ROW so I can put it on the tablet I somehow got a PRC CN ROM on it and now no Google apps or anything just the zip file I need to place on the SD card is all I need I've looked everywhere spent all night I'm surprised I havnt bricked it I found 1 but qfil or qdloader wouldn't put it on the tablet I just want my tablet back.....
Click to expand...
Click to collapse
Hi, I think flashing with only update.zip can cause bricked device like I bricked mine, fast search on lenovo-forums.ru gives me a link and another link to ROM flashed via QPST/QFIL, don't know if flashing can be done exacly with tools I unbricked mine YT3-850L, for details ask them at lenovo-forums.ru (You could use translate.google.com if You don't know Russian language, just as I did)
That's how I got the Chinese version on the tablet just putting it on the SD card
tapayn02 said:
That's how I got the Chinese version on the tablet just putting it on the SD card
Click to expand...
Click to collapse
The links above that I gave You isn't for flashing via SD-Card (dont flash It via Android recovery), It's mean to flash from PC via QFIL application.
When I was searching for ROM for my YT3-850L I found Chinese version too, i dont think You can find any update.zip with full ROM for Your Lenovo, there are only ROW's which are only updates from one version to another (not full android).
If You wish to try something i recommend backing up to .QNC file via QPST (it's NVRAM which stores IMEI, WIFI Mac, BT Mac, GPSID and other settings - for me it was additional sound not working).
The ROM's flashed via QFIL/QPST are full android backups, I don't think that in lenovo-forums.ru are Chinese versions.
If You go to lenovo-forums.ru there is at top on right on site button to choose language and translate so it's easy to read.
OK Thanks I'll give it a shot
hi wpinacz
i have lenovo yt3-850M tab and i install chines rom from through the sd card please give row version of qpst rom and very very thank for giveing yt3-850l row rom
i am very trbul this time if you help i feel greatful
thank you
rj3689 said:
hi wpinacz
i have lenovo yt3-850M tab and i install chines rom from through the sd card please give row version of qpst rom and very very thank for giveing yt3-850l row rom
i am very trbul this time if you help i feel greatful
thank you
Click to expand...
Click to collapse
Here's the link , be sure to READ INSTRUCTIONS before flashing, as I read it's mean to flash from PC not from SCDARD.
For all to know, I don't have any other ROM than for YT3-850L, different models (like "M" or "Y") are using different ROM than mine, the tools and drivers could be different to flash, the steps to flash device could be different too. So if anyone else got other version than "L" should be searching on other xda topics like here , or at lenovo-forums.ru
Thanks for help.
wpinacz said:
Hi all,
First of all I wanted to thank baikal0912 from lenovo-forums.ru , without Him this guide haven’t been possible, so all the glory and kudos go to Him in first place. (baikal0912 if You’re reading this – Thank You once again)
THIS GUIDE IS FOR LENOVO YOGA TAB 3 YT3-850L! AS ALWAYS I’M NOT RESPONSIBLE FOR DAMAGED DEVICES AND LOST DATA! ALWAYS MAKE BACKUP! (DON’T MAKE MY MISTAKES)
SOME HISTORY (read if You want to know how I bricked my device)
I had stock 5.1.1 Android on my Yoga, tablet has been updated to 6.0.1 in which i had problems with writing to SDCard (permissions), so I managed to unlock bootloader, flash TWRP, install Xposed and SDFix. Sadly after some time I saw that randomly applications disappeared (like Google Play Store).
So I was searching for 5.1.1 ROM (because I didn’t had any backup), only 2 ROM’s where available to download and it was for „M” model (YT3-850M) not „L”. First ROM was 785MB – it was only Chinese/English language, after flashing my device I saw that my LTE didn’t work, WIFI, BT, GPS and Sound doesn’t work either.
So I tried second ROM downloaded for „M”, It was 1,2GB and there were all languages available, but still LTE, WIFI, BT, GPS and Sound didn’t work.
I was searching for some info about my problem and manager to go to lenovo-forums.ru where I find out It’s because missing/damaged NVRam data (the data where tablet stores IMEI, Mac address and other stuff)
Surely It was my fault because I didn’t do any backup in first place (and yes, I’m an idiot)
Trying to find NVRam backup (in .QCN file) I ended in lenovo-forums.ru talking with baikal0912, He shared with me stock „L” ROM and trying to help me flash the device back again, so I made this topic because there is a problem finding „L” ROM and so everyone know how I flashed my device (which tools and drivers are needed, which mode to enter to flash device.
So let’s get started….
First, if Your tablet boots to Android make sure it has ADB debugging enabled (If You want to know how to enable ADB debug search the forum, there are plenty of answers)
Second make sure You grab SIMCard from device (You’ll gonna insert it later at end of my guide)
GRAB ALL THE NEEDED FILES: (ROM is 1GB 7zip compressed)
Code:
https://drive.google.com/drive/folders/0B2EmK9gw0mTdYUdJUGlDUm0zTW8?usp=sharing
You will need ROM (YT3-850L_S000026_151217_ROW_qpst.7z), QPST v2.7.429 (QPST_2.7.429.7z), drivers (Qualcomm USB Drivers For Windows.zip and Qualcomm_USBDriver_2.1.0.5_x64.cab), IMEI writing software (A100_WriteDualIMEI(W+G_eMMC).rar).
Also You are going to need ADB tools, search for them here at XDA (minimal ADB and fastboot).
NOTE: I’ve been trying to restore ROM with other QPST version and drivers without any success.
Install QPST, extract ROM to „C:\Lenovo” then connect turned on Yoga to PC, there should be 3 new devices shown in device manager named YT3-850M (in my case it was „M”, Yours can be „L”), install drivers from „Qualcomm USB Drivers for Windows.zip”, Windows should install two of them (modem fails to install, just ignore), the most important is device installed as „Lenovo HS-USB Diagnostics (COMx)” where X is Your COM port numer needed LATER.
ENTER FLASHING MODE
For now run ADB command to check if Your device is recognized:
Code:
adb devices
If It’s recognized then command will show You some numbers, if You’re ready to go then run this command:
Code:
adb reboot edl
Above command will change Android to something I call „Flashing Mode” (the screen on tablet will be black), for now tablet is waiting for flashing, You should now see that device manager in Windows shows only one new devices o install from „Qualcomm_USBDriver_2.1.0.5_x64.cab”, the device manager should install „Qualcomm HS-USB QDLoader 9008 (COMx)”, note the COM port X needed to flash.
Others at forums tell me to enter „Diagnostic Mode” to start flashing but they were wrong, „Diagnostic Mode” is something else needed later.
FLASH THE DEVICE
Run QFIL.exe from installed QPST directory (c:\Program Files (x86)\Qualcomm\QPST\bin\), make sure to run with Administrator privileges (from right click context menu).
Code:
- Make sure that QFIL recognized Your device showing „Qualcomm HS-USB DQLoader 9008” with COM port numer at top of QFIL screen.
- Select FLAT BUILD
- In „Programmer Path” choose „Browse”, go to extracted ROM directory and choose file named „prog_emmc_firehose_8909_ddr.mbn”
- Click on „LoadXML” below on right, choose „rawprogram0” file, then choose „patch0” file
If You are 100% sure You want to flash then press blue „Download” button and wait to finish flashing (don’t disconnect or turn off tablet before it ends).
You should notice that in „Status” window in QFIL there should be LOG, here’s my example of LOG file (shortened, doesn't fit all):
Start Download
Program Path:C:\lenovo\prog_emmc_firehose_8909_ddr.mbn
COM Port number:5
Sahara Connecting ...
Sahara Version:2
Start Sending Programmer
Sending Programmer Finished
Switch To FireHose
Wait for 3 seconds...
Max Payload Size to Target:49152 Bytes
Device Type:eMMC
Platform:8x26
Disable Ack Raw Data Every N Packets
Skip Write:False
Always Validate:False
Use Verbose:False
COM Port number:5
Sending NOP
FireHose NOP sent successfully
Sending Configuration
Device Type:eMMC
Platform:8x26
FireHose Log: [email protected] [email protected]
Request payload size 0xc000 is not the same as support payload size, change to 0x100000
Request payload size 0x100000 is too big, reduce to 0x20000
FireHose Log: [email protected] [email protected]
Set TxBuffer 0x20000, RxBuffer 0x4000
Firehose configure packet sent successfully!
ReadBackMode:No_Readback
Disable read back
Total Bytes To Program 0x86846CA0
Download Image
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1e3
PROGRAM: Partition 0, Sector: 40, Length: 483 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\sbl1.mbn
FireHose Log: start 40, num 483
FireHose Log: Finished sector address 523
PROGRAM: Written Bytes 0x3c600 (64)
Program Size: 0.24 MB
PROGRAM: Replace the partition sectors number 0x400 to file size in sector 0x1e3
PROGRAM: Partition 0, Sector: 1064, Length: 483 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\sbl1.mbn
.......
.......
.......
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 7799808, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_8.img
FireHose Log: start 7799808, num 16
FireHose Log: Finished sector address 7799824
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 7800712, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_9.img
FireHose Log: start 7800712, num 16
FireHose Log: Finished sector address 7800728
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8061952, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_10.img
FireHose Log: start 8061952, num 16
FireHose Log: Finished sector address 8061968
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8324096, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_11.img
FireHose Log: start 8324096, num 16
FireHose Log: Finished sector address 8324112
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8325000, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_12.img
FireHose Log: start 8325000, num 16
FireHose Log: Finished sector address 8325016
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8586240, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_13.img
FireHose Log: start 8586240, num 16
FireHose Log: Finished sector address 8586256
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8848384, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_14.img
FireHose Log: start 8848384, num 16
FireHose Log: Finished sector address 8848400
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 8849288, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_15.img
FireHose Log: start 8849288, num 16
FireHose Log: Finished sector address 8849304
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9110528, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_16.img
FireHose Log: start 9110528, num 16
FireHose Log: Finished sector address 9110544
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9372672, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_17.img
FireHose Log: start 9372672, num 16
FireHose Log: Finished sector address 9372688
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9634816, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_18.img
FireHose Log: start 9634816, num 16
FireHose Log: Finished sector address 9634832
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9896960, Length: 16 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_19.img
FireHose Log: start 9896960, num 16
FireHose Log: Finished sector address 9896976
PROGRAM: Written Bytes 0x2000 (64)
Program Size: 0.01 MB
PROGRAM: Partition 0, Sector: 9901032, Length: 218048 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\userdata_20.img
FireHose Log: start 9901032, num 218048
FireHose Log: Finished sector address 10119080
PROGRAM: Written Bytes 0x6a78000 (64)
Program Size: 106.47 MB
PROGRAM: Partition 0, Sector: 0, Length: 34 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\gpt_main0.bin
FireHose Log: start 0, num 34
FireHose Log: Finished sector address 34
PROGRAM: Written Bytes 0x4400 (64)
Program Size: 0.02 MB
PROGRAM: Partition 0, Sector: NUM_DISK_SECTORS-33., Length: 33 Sectors, Sector Size: 512 Bytes
File: C:\lenovo\gpt_backup0.bin
FireHose Log: start 30535647, num 33
FireHose Log: Finished sector address 30535680
PROGRAM: Written Bytes 0x4200 (64)
Program Size: 0.02 MB
Total Size: 2155.12 MB
Total Time: 265 Seconds
Throughput: 8.13 MB/Seconds
PATCH: Partition 0, Sector: 9, Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 9 with 01D1EFDE
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-26., Offset 296 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 30535654 with 01D1EFDE
PATCH: Partition 0, Sector: 1, Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 1 with 01D1EFDE
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 48 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-34.
FireHose Log: Patched sector 30535679 with 01D1EFDE
PATCH: Partition 0, Sector: 1, Offset 32 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 1 with 01D1EFFF
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 24 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-1.
FireHose Log: Patched sector 30535679 with 01D1EFFF
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1, Offset 72 Bytes, Size: 8 Bytes, Value: NUM_DISK_SECTORS-33.
FireHose Log: Patched sector 30535679 with 01D1EFDF
PATCH: Partition 0, Sector: 1, Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(2,4096)
FireHose Log: crc start sector 2, over bytes 4096
FireHose Log: Patched sector 1 with 7315C503
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 88 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-33.,4096)
FireHose Log: crc start sector 30535647, over bytes 4096
FireHose Log: Patched sector 30535679 with 7315C503
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 1 with 00000000
PATCH: Partition 0, Sector: 1, Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(1,92)
FireHose Log: crc start sector 1, over bytes 92
FireHose Log: Patched sector 1 with 2EB8C0BF
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 16 Bytes, Size: 4 Bytes, Value: 0
FireHose Log: Patched sector 30535679 with 00000000
PATCH: Partition 0, Sector: NUM_DISK_SECTORS-1., Offset 16 Bytes, Size: 4 Bytes, Value: CRC32(NUM_DISK_SECTORS-1.,92)
FireHose Log: crc start sector 30535679, over bytes 92
FireHose Log: Patched sector 30535679 with B8615551
Total download file size: 2155,119MB
Total download time: 4 Min 26 Sec
Throughput: 8,096117MB/s
FireHose Log: Set bootable drive to 0.
Download Succeed
Finish Download
If there’s „Download Succeed” and „Finish Download” in LOG You could try to boot new ROM holding POWER button, the first boot should take some time, after boot don’t install any apps, we need to change IMEI before we use tablet.
CHECK IMEI
After booting check Your IMEI numer if exists in NVRam, go to „CONTACTS”, click „Search” magnifier button, enter:
Code:
*#06#
If IMEI is good, skip to „Region Change” guide.
If IMEI is 0 then note Your IMEI from the „Standing Plate” of Your tablet.
WRITING IMEI
First shut down tablet, boot with holding „POWER” „+” and „-„ buttons, there should show something I call „Diagnostic Mode”, there will be some tests like:
Code:
1 SYSTEM INFO
2 KEYPAD BACKLIGHT
3 LCD BACKLIGHT
…..
…..
You should connect tablet to PC, and if You previously installed „Qualcomm USB Drivers For Windows.zip” drivers, then run WriteDualIMEI(W+G_eMMC).exe as Administrator.
Program will auto detect COM port, there will be two fileds (IMEI1, IMEI2), just insert Your IMEI in BOTH FIELDS, click START, wait to program show PASS.
If it pass, disconnect tablet from USB, click on REBOOT in „Diagnostic Mode”, choose „(3) Reboot to Android”, hit „OK”
After booting check IMEI number as mentioned above, if it’s ok then last thing to do is…
CHANGE REGION CODE
To change region code, to the same as checking IMEI but with other code, so go to „CONTACTS”, click „Search” magnifier button, enter:
Code:
####682#
Region changing settings should appear, at top there is Your currently selected region, below You can choose new region, note that after changing region Android should reboot.
For now shut down Android, insert SIMCard, and enjoy.
That’s all, thanks for reading, I hope this guide will help someone like baikal0912 :good: helped me.
Regards.
P.S. If someone know how to enter „Flashing Mode” in other way than „adb reboot edl” let me know so I can update this guide (maybe there is someone who can’t boot device and enter „Flashing Mode” via ADB)
P.S.2. Flashing done under Windows 10 Home 64 bit, connected to USB 2.0
P.S.3. I haven't done Serial Number (SN) writing to tablet, don't know how.
P.S.4. Sorry for my bad English
Click to expand...
Click to collapse
Thanks WPINACZ, you took me out of that PRC rom. now i can use my tab once again. updated the chinese rom while downgrading and then was unable to load gaps or any google apps.
Your elaborate process took me out of the rom.:good::good::good::good:
Only thing to update is, i did it on the Windows 10 Pro. I did not have to install any drivers while following the procedures.
Thanks again.
I'm glad to know that my guide helped someone, I've made it because there wasn't any guide on net and so anyone could flash device fast, I've spent about 1 week to find all that I need to flash device because of work I had only few hours daily to write through translator in Russian language, hopefully I managed to meet baikal0912 who shared with me rom as I share with You, I've tested all drivers, tools and methods to bring back my Yoga to life and figured to write this guide so others can flash without problems.
Regards
Phone featuers not working
wpinacz said:
I'm glad to know that my guide helped someone, I've made it because there wasn't any guide on net and so anyone could flash device fast, I've spent about 1 week to find all that I need to flash device because of work I had only few hours daily to write through translator in Russian language, hopefully I managed to meet baikal0912 who shared with me rom as I share with You, I've tested all drivers, tools and methods to bring back my Yoga to life and figured to write this guide so others can flash without problems.
Regards
Click to expand...
Click to collapse
Dear WPINACZ,
only Q i have is now my tab is with 850L rom, which does not support Phone feature.But my tab earlier was 850M (with phone features). I don't need the phone but because of this few apps which i use regularly cannot be installed (basically because they need the phone permissions) Please if you could help.
Bhaskar1091 said:
Dear WPINACZ,
only Q i have is now my tab is with 850L rom, which does not support Phone feature.But my tab earlier was 850M (with phone features). I don't need the phone but because of this few apps which i use regularly cannot be installed (basically because they need the phone permissions) Please if you could help.
Click to expand...
Click to collapse
Sorry but I don't know any possible way to enable phone on L rom, I was reading how enable phone on other tablets (like Samsung) and the process needs rooted device and .zip patch for device which I don't think will work on Lenovo, messing with low level settings in QPST could damage device too, so I think the easiest and cleanest way is to grab M rom from lenovo-forums.ru
You could try to install some phone .apk from other developers but it won't enable phone permissions, and of course You can't make phone calls.
wpinacz said:
Here's the link , be sure to READ INSTRUCTIONS before flashing, as I read it's mean to flash from PC not from SCDARD.
For all to know, I don't have any other ROM than for YT3-850L, different models (like "M" or "Y") are using different ROM than mine, the tools and drivers could be different to flash, the steps to flash device could be different too. So if anyone else got other version than "L" should be searching on other xda topics like here , or at lenovo-forums.ru
Click to expand...
Click to collapse
thankyou my friend my problem for chines rom in my lenovo tab is solved by Brandon thank you very much