WARNING: NOT FOR F1S or F1PLUS (MEDIATEK CHIPSETS). PLEASE DON'T USE THIS METHOD IF YOU OWN THOSE DEVICES! QFIL IS STRICTLY FOR QUALCOMM DEVICES.
Don't blame me if anything goes wrong, DWYOR. I'll ignore and laugh at you if you start blaming me. You're here in XDA which means you understand the risks.
I'm writing this guide for F1f/w users who cannot unlock their bootloader, cannot even access fastboot or even can't flash uberlaggydarwin's magictricks.zip because the F1f/w stock ColorOS has been updated to a version that is above magictricks.zip's script. All credit's go to uberlaggydarwin, because he's the man behind it all, whom enabled F1f/w's fastboot mode.
*This needs a PC*
Prerequisites:
QFIL (Qualcomm Flash Image Loader, file attached)
QDLoader drivers & the knowledge to install those drivers to Windows (attached, if not working, google it)
The zip containing the files for unlocking fastboot (attached)
A computer (duh) with a USB cable.
Developers Options enabled and OEM Unlocking enabled (a total must).
Step-by-steps:
Download all of the zips attached
Extract all of the zips
Install the QDLoaderDrivers by right clicking qcser.inf then find & press "install" (the drivers attached are for Windows 10, if they aren't compatible then Google them drivers for your current OS)
Open QFIL.exe
Find "Select Build Type" and choose Flat Build
In "Select Programmer", press "Browse" and go to the directory that contains the extracted files of the "F1F-Fastboot-QFIL.zip" and choose the file named "prog_emmc_firehose_8936.mbn"
In "Select Build", press "Load Content" and FIRST select the file "rawprogram0_aboot.xml" then after the second window pops up, select "patch0.xml".
Power off your F1f/w
Reboot to download mode by inserting the USB cable to your F1f/w while holding Volume + (Volume up) button
Open your PC's "Device Manager" and expand "Ports", If the driver "Qualcomm HS-USB QDLoader 9008" shows up it means you've successfully installed the QDLoader drivers and you can continue to the next step
Go back to QFIL, now the text "No Port Available" has changed to "Qualcomm HS-USB QDLoader 9008", if it does now press "Download"
If everything goes right, there would be an ANSI text that shows the word "SUCCESS".
Unplug your phone and force reboot it by holding the power button (it'll take a while just wait patiently).
Once your F1f/w has booted, power it off again. Boot to fastboot by pressing power button and holding volume+/up.
Voila! Congratulations you've just enabled fastboot mode and now you can unlock your phone by typing "fastboot oem unlock" via ADB cmd.
*Credit goes to uberlaggydarwin for his magictricks and the android community for sharing tons of knowledge that can be acces 24/7
Hit 'Thanks' if this helped. Cheers. :highfive: :good:
*If the QFIL here doesn't work on your device, try "this" version provided by AmineHadef (Thanks mate!)
oppo f7 2018
ezrawk said:
Don't blame me if anything goes wrong, DWYOR. I'll ignore and laugh at you if you start blaming me. You're here in XDA which means you understand the risks.
I'm writing this guide for F1f/w users who cannot unlock their bootloader, cannot even access fastboot or even can't flash uberlaggydarwin's magictricks.zip because the F1f/w stock ColorOS has been updated to a version that is above magictricks.zip's script. All credit's go to uberlaggydarwin, because he's the man behind it all, whom enabled F1f/w's fastboot mode.
*This needs a PC*
Prerequisites:
QFIL (Qualcomm Flash Image Loader, file attached)
QDLoader drivers & the knowledge to install those drivers to Windows (attached, if not working, google it)
The zip containing the files for unlocking fastboot (attached)
A computer (duh) with a USB cable.
Developers Options enabled and OEM Unlocking enabled (a total must).
Step-by-steps:
Download all of the zips attached
Extract all of the zips
Install the QDLoaderDrivers by right clicking qcser.inf then find & press "install" (the drivers attached are for Windows 10, if they aren't compatible then Google them drivers for your current OS)
Open QFIL.exe
Find "Select Build Type" and choose Flat Build
In "Select Programmer", press "Browse" and go to the directory that contains the extracted files of the "F1F-Fastboot-QFIL.zip" and choose the file named "prog_emmc_firehose_8936.mbn"
In "Select Build", press "Load Content" and FIRST select the file "rawprogram0_aboot.xml" then after the second window pops up, select "patch0.xml".
Power off your F1f/w
Reboot to download mode by inserting the USB cable to your F1f/w while holding Volume + (Volume up) button
Open your PC's "Device Manager" and expand "Ports", If the driver "Qualcomm HS-USB QDLoader 9008" shows up it means you've successfully installed the QDLoader drivers and you can continue to the next step
Go back to QFIL, now the text "No Port Available" has changed to "Qualcomm HS-USB QDLoader 9008", if it does now press "Download"
If everything goes right, there would be an ANSI text that shows the word "SUCCESS".
Unplug your phone and force reboot it by holding the power button (it'll take a while just wait patiently).
Once your F1f/w has booted, power it off again. Boot to fastboot by pressing power button and holding volume+/up.
Voila! Congratulations you've just enabled fastboot mode and now you can unlock your phone by typing "fastboot oem unlock" via ADB cmd.
*Credit goes to uberlaggydarwin for his magictricks and the android community for sharing tons of knowledge that can be acces 24/7
Hit 'Thanks' if this helped. Cheers. :highfive: :good:
Click to expand...
Click to collapse
I am Asking, its work in oppo f7 with color os v5 ?
savan bhavani said:
I am Asking, its work in oppo f7 with color os v5 ?
Click to expand...
Click to collapse
Oh my friend please refrain from quoting the first post. Second I know you are desperate my friend, but please, have common sense, this whole forum is for Oppo F1 & F1s. Not F7.
So does it work on F7? No! They are different devices for crying out loud. This thread is just for Oppo F1f/w, a QUALCOMM device, whereas F7 is a MTK device. Even if they are both Oppo devices, cross-device development is just totally impossible.
Yeah I know you want a simple answer, but I mean come on....... be a little bit rational please.
I'm using Mac... Omy how will I gonna do this?
i cannot unlock my bootloader.
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
OppoMac said:
I'm using Mac... Omy how will I gonna do this?
Click to expand...
Click to collapse
Honestly I don't know for Mac users.. QFIL is a windows based program itself... I'm sorry man. Why not borrow a Windows PC or Laptop from a friend to do this?
musashiro said:
i cannot unlock my bootloader.
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Click to expand...
Click to collapse
What Windows version are you using bro? Have the drivers been installed correctly (No exclamation mark sign in the driver)? I've tested my method in 4 different PC's and they all work. 3 Windows 10 devices (including my laptop) & 1 Windows 7 PC.
Usually if that (Download Fail:Sahara Fail:QSaharaServer Failrocess fail) shows up, it's driver issues. If you're using Win 10, try to reboot to advanced startup, then go to troubleshoot, then pick advanced start-up (the ones with safe-mode, etc.) and continue. Then select disable "disable driver signature enforcement" and then continue with the reboot. Then try flashing it one more time.
Can this step be installed on Oppo A37F which has a Qualcom Snapdragon 8916 Chipset ...? because a37f there are also those who don't have fastboot so I want to build it ... thank you
Download Fail:FireHose Fail FHLoader Fail:The system cannot find the file specified.
Hi, Ezrawk. I found that I can't flash magictrick as my OS version has been upgraded, so I deciced to use your solution.
Previously, I got the err msg saying: "QSaharaServer Fail: The directory name is invalid", so I googled it.
It turned out that the path was too long, and I solved it by move all the files needed to the root path of the disk "C:".
Yet, another problem got in the way, and for that, I really have no idea how to solve it.
"Download Fail:FireHose Fail FHLoader Fail:The system cannot find the file specified."
May you help me?
My phone's OS is not modified.
Model number: F1f
ColorOS: V2.1.0i
Android: 5.1.1
Build Num: F1fTW_11_171125
Here's the log:
Code:
Image Search Path: C:\
RAWPROGRAM file path: C:\rawprogram0_aboot.xml
PATCH file path:C:\patch0.xml
Start Download
Program Path:C:\firehose_8936.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\QFIL\QSaharaServer.exe -p \\.\COM10 -s 13:C:\firehose_8936.mbn 'Current working dir: C:\Users\holle\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\firehose_8936.mbn
22:19:37: Requested ID 13, file: "C:\firehose_8936.mbn"
22:19:38: 95292 bytes transferred in 0.063000 seconds (1.4425MBps)
22:19:38: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
22:19:38: Sahara protocol completed
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
[COLOR="Red"]Download Fail:FireHose Fail FHLoader Fail:The system cannot find the file specified[/COLOR]
Finish Download
roniethea said:
Can this step be installed on Oppo A37F which has a Qualcom Snapdragon 8916 Chipset ...? because a37f there are also those who don't have fastboot so I want to build it ... thank you
Click to expand...
Click to collapse
What you're trying to say is can you flash this on an A37F that has 8916 chipset using these files that are meant for an 8936 chipset? No! It'll brick your phone, bro.
But if what you're saying is can you use the QFIL method to flash firmware files to your A37F.. The answer is yes you can, as long as you have the correct files for your chipset. QFIL is strictly for qualcomm chipsets anyway, and that is if you can access QCOM download mode.
About how to unlock your phone or how to access download mode, I have no idea how, because I don't have or own an A37F. Sorry, kang.
hollen9 said:
Hi, Ezrawk. I found that I can't flash magictrick as my OS version has been upgraded, so I deciced to use your solution.
Previously, I got the err msg saying: "QSaharaServer Fail: The directory name is invalid", so I googled it.
It turned out that the path was too long, and I solved it by move all the files needed to the root path of the disk "C:".
Yet, another problem got in the way, and for that, I really have no idea how to solve it.
"Download Fail:FireHose Fail FHLoader Fail:The system cannot find the file specified."
May you help me?
My phone's OS is not modified.
Model number: F1f
ColorOS: V2.1.0i
Android: 5.1.1
Build Num: F1fTW_11_171125
Here's the log:
Click to expand...
Click to collapse
What Windows OS are you using? Windows 10?
I advise you to put all of those files inside an empty folder in C:\
For example: "C:\UBL"
About the character restrictions of a address path, you could google the way to disable that restriction.
Are you sure the unlock files are not in a seperate folder and have you placed the files together in the same directory? Because your log shows that QFIL can't find the file mentioned, which means that the file that's gonna be flashed isn't in the mentioned directory of the rawprogram0_aboot.xml.
Extra note: I just unlocked a friends bootloader a week ago with his Windows PC, using only the files from this thread of mine, which I downloaded to his PC. Didn't plan on unlocking his phone, but he insisted because he's starting to hate his F1-F. Successfully flashed it using his Win 10 PC, nothing went wrong, my files are working. His F1 is now on khannz7's RR Oreo.
Example screenshot (these files have to be in the same directory for it to work):
Thank you ... for the info ... friend ... for the flashing firmware method a37f I have been able to downgrade or upgrade ... via MsM tools. exe for Qualcom. now I am stuck to unlock the bootloader a37f .. the tool opposing tool on this device does not work .. fastbot mode does not exist .. once again thank you for the info a little info from friends ... a lot of knowledge we can ... Cmiwww ...
Still failed to flash rawprogram0_aboot.xml
Thank you, ezrawk, for your willingness to assist and fast reply. :angel:
ezrawk said:
What Windows OS are you using? Windows 10?
Click to expand...
Click to collapse
I am using: Windows 10 Home 64-bit (17134)
PC OS Interface Language: English
F1f Interface Language: English
ezrawk said:
I advise you to put all of those files inside an empty folder in C:\
For example: "C:\UBL"
About the character restrictions of a address path, you could google the way to disable that restriction.
Are you sure the unlock files are not in a seperate folder and have you placed the files together in the same directory? Because your log shows that QFIL can't find the file mentioned, which means that the file that's gonna be flashed isn't in the mentioned directory of the rawprogram0_aboot.xml.
Click to expand...
Click to collapse
I did what you suggested, that is to put all the files required under the same folder located in "C:", but the problem persists. :crying:
Perhaps I missed something, I guess? If you'd like to check the whole process done by me, check the video:
youtu.be/VlsnPHK8WHA
ezrawk said:
Extra note: I just unlocked a friends bootloader a week ago with his Windows PC, using only the files from this thread of mine, which I downloaded to his PC. Didn't plan on unlocking his phone, but he insisted because he's starting to hate his F1-F. Successfully flashed it using his Win 10 PC, nothing went wrong, my files are working. His F1 is now on khannz7's RR Oreo.
Click to expand...
Click to collapse
I believe this solution works under most situation, yet I just failed again and again (actually it was about 6 times) on my environment. I tried with my main spec PC and laptop, but to no avail. I once doubted it could be caused by locale setting on my phone and Windows. However, After booting all those device with English settings, things didn't change.
Maybe I will grab another PC to proceed if I have chance, because the Power Supply Unit of my main spec burned out last night. :silly:
Again, thank you ezrawk for taking your time to help.
I cannot unlock my bootloader.
My phone model: F1f
ColorOS: V2.1.0i
Android: 5.1.1
Build Num: F1fEX_11_171125
Saved log:
Code:
Start Download
Program Path:C:\QFIL\prog_emmc_firehose_8936.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\QFIL\QSaharaServer.exe -p \\.\COM3 -s 13:C:\QFIL\prog_emmc_firehose_8936.mbn 'Current working dir: C:\Users\a\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\QFIL\prog_emmc_firehose_8936.mbn
15:21:48: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
15:21:48: ERROR: function: sahara_main:854 Sahara protocol error
15:21:48: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
I am using Windows 7 32-bit
Please help unlock my bootloader :crying:
---------- Post added at 04:14 PM ---------- Previous post was at 03:49 PM ----------
Next, I tried to rename the file prog_emmc_firehose_8936.mbn -> firehose_8936.mbn
And got a log:
Code:
Start Download
Program Path:C:\QFIL\firehose_8936.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\QFIL\QSaharaServer.exe -p \\.\COM3 -s 13:C:\QFIL\firehose_8936.mbn 'Current working dir: C:\Users\a\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: C:\QFIL\firehose_8936.mbn
15:55:06: Requested ID 13, file: "C:\QFIL\firehose_8936.mbn"
15:55:06: 95292 bytes transferred in 0.062000 seconds (1.4658MBps)
15:55:06: File transferred successfully
NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!
15:55:06: Sahara protocol completed
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
Download Fail:FireHose Fail FHLoader Fail:Не удается найти указанный файл
Finish Download
Error identical to that described here - https://forum.xda-developers.com/showpost.php?p=78589920&postcount=8
---------- Post added at 04:20 PM ---------- Previous post was at 04:14 PM ----------
hollen9 said:
Here's the log:
Click to expand...
Click to collapse
My log is completely similar to yours. Did you manage to unlock the bootloader?
---------- Post added at 04:26 PM ---------- Previous post was at 04:20 PM ----------
ezrawk said:
Don't blame me if anything goes wrong, DWYOR. I'll ignore and laugh at you if you start blaming me. You're here in XDA which means you understand the risks.
I'm writing this guide for F1f/w users who cannot unlock their bootloader, cannot even access fastboot or even can't flash uberlaggydarwin's magictricks.zip because the F1f/w stock ColorOS has been updated to a version that is above magictricks.zip's script. All credit's go to uberlaggydarwin, because he's the man behind it all, whom enabled F1f/w's fastboot mode.
Click to expand...
Click to collapse
Is your manual exactly working? I am already the second person with a similar problem!
is its work in Oppo A3s , CPH1803..?
Because as per google , The oppo had been lock the the fastboot binary ...
hollen9 said:
Thank you, ezrawk, for your willingness to assist and fast reply. :angel:
I am using: Windows 10 Home 64-bit (17134)
PC OS Interface Language: English
F1f Interface Language: English
I did what you suggested, that is to put all the files required under the same folder located in "C:", but the problem persists. :crying:
Perhaps I missed something, I guess? If you'd like to check the whole process done by me, check the video:
youtu.be/VlsnPHK8WHA
I believe this solution works under most situation, yet I just failed again and again (actually it was about 6 times) on my environment. I tried with my main spec PC and laptop, but to no avail. I once doubted it could be caused by locale setting on my phone and Windows. However, After booting all those device with English settings, things didn't change.
Maybe I will grab another PC to proceed if I have chance, because the Power Supply Unit of my main spec burned out last night. :silly:
Again, thank you ezrawk for taking your time to help.
Click to expand...
Click to collapse
qwas.ru said:
I cannot unlock my bootloader.
My phone model: F1f
ColorOS: V2.1.0i
Android: 5.1.1
Build Num: F1fEX_11_171125
I am using Windows 7 32-bit
Please help unlock my bootloader :crying:
---------- Post added at 04:14 PM ---------- Previous post was at 03:49 PM ----------
Next, I tried to rename the file prog_emmc_firehose_8936.mbn -> firehose_8936.mbn
Error identical to that described here - https://forum.xda-developers.com/showpost.php?p=78589920&postcount=8
---------- Post added at 04:20 PM ---------- Previous post was at 04:14 PM ----------
My log is completely similar to yours. Did you manage to unlock the bootloader?
---------- Post added at 04:26 PM ---------- Previous post was at 04:20 PM ----------
Is your manual exactly working? I am already the second person with a similar problem!
Click to expand...
Click to collapse
It works, if it doesn't why would I post it? Here's the deal, try googling if my response is late. It's not like I own the device. I'm just sharing this in hopes it could help F1 users. It's full of trials and errors, try searching for other guides. It's a snapdragon device ffs, lots of guides everywhere to search for.
Btw you can try other versions of QFIL, just try downloading them one by one. Try other drivers. Because most of the time failing in flashing via QFIL is caused by drivers or the program itself.
anyways both of you try this xml. if it works, report back so I can change the attachments from first post.
akshayakbari said:
is its work in Oppo A3s , CPH1803..?
Because as per google , The oppo had been lock the the fastboot binary ...
Click to expand...
Click to collapse
Bro sorry, it does not work. Because the bootloader is purely for oppo f1.
i cant open my oppo f1s in download mode
Aman Jhagrolia said:
i cant open my oppo f1s in download mode
Click to expand...
Click to collapse
Sorry mate, this isn't for F1s. F1s is Mediatek, where F1f is Qualcomm. QFIL method is strictly for Qualcomm devices only.
Bro, please tell me that does this method erases files or not.
I believe the last times I used this method it didn't erase anything.
i tried the steps, but the step for clicking download, it fails, how to troubleshoot that?
Hi,
I had the same issue as @hollen9 and @qwas.ru and not sure if @Supladang_Rae is getting the same error too...
I was getting this message as well.
Code:
"Download Fail:FireHose Fail FHLoader Fail"
But I managed to solve it , here is what I did:
I used QFIL v1.0.0.2 instead
Extracted the contents to "C:\Q" (the QFIL.exe and all files there, not under another folder)
Copied the "emmc_appsboot.mbn" and the other 3 files to "C:\O"
Ran "QFIL.exe" as administrator and followed the instructions given in this thread.
Then, all went good, and the last message I got was "Waiting for reset done". (see attachements)
So, I pressed the power button to start the phone, it booted normally, removed the cable and turned it off, then tried the volume up & power button and it booted to fastboot, from here I followed the other instructions from the other GUIDE thread and everything worked fine.
My Oppo F1f was on the latest firmware and it's rooted now.
Thanks ezrawk. :good:
Related
Hi all i have new Lenovo PB1 770m I attempted to root it the TWRP was installed but it was not rooted
then I tried to update the firmware to the latest 151111 and no go, in the end i managed to delete the operating system so now I can boot to recovery mode only, When I try to restart it comes up with No OS Installed, I have tried to install xposed v79 sdk21 arm64zip no go, Ok now I know that I am an IDIOT for
not making a backup of original system and not cheking the firmware was the same as the root guide,
On the top of recovery screen is :- 2.8.7.7 SevenMaxs and TeamWin Recovery Project, I guess this could
be an expensive lesson, I have been looking for an original ROM with no luck so any help would be very
much appreciated, Thanks pluto1956, Mike
ps used info and files from here to try and root. http://forum.xda-developers.com/andr...oting-t3290347
UPDATE I managed to get a ROM from Russian site PB1-770M_S000156_150930_ROW_fastboot.7z 1.8gig
instructions say to be installed from computer via usb my problem is I can only access the internal storage or external SD card not the Usb-otg so it seems I can only update from the sd or internal memory
tried putting the rom on both but no go
Hi is there anybody that knows where and how to install the stock firmware for the phab PB1-770M
HELP
Same as above. need a stock rom. formatted internal storage mistakenly. HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
naeemdurrani said:
Same as above. need a stock rom. formatted internal storage mistakenly. HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Thanks brother, yesterday i downloaded one russian rom in zip format and there was a .bat file included in it. i only double clicked and it flashed through adb and fastboot and it was successfull. i got the operating system 5.0.2 but WLAN is not working, tried flashing several time but no luck. i learned that it is still under warranty ..so sent it to warranty. in a week it will be back with be for testing again hopefully.
well i will try your method as soon as i get my beast again. Thank you so much for helping out in timely manner, really appreciate it brother.
jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
---------- Post added at 08:10 AM ---------- Previous post was at 08:06 AM ----------
it is very easy my friend just look into the only topic/thread about Phab plus in xda. it will guide you well.
if you get any error in recovery like footer is wrong/signature verification failed. connect your phone and first check if your device in being tracked by adb. use adb devices.
if your device appear in the list of devices ..use fastboot oem unlock then flash sevenmax twrp again after entering into temporary twrp as per phab plus thread.
0verdaflow said:
How can you root this damn phones.... i was trying like for 2 days....
Click to expand...
Click to collapse
jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
Could you please elucidate more? I downloaded the ROM and the flash program. However, I've no clue how to get going. I don't even see the xml files anywhere (as mentioned by you).
Just don't want to screw it up bad so being little more cautious.
jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
im getting this error
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
cant flash the stock rom
man dont use Qfil program.
the rom which you downloaded should be in zip format, unzip it, there is a file download_with_partiotion.bat.
run it and sit back until it is finished.
Wakatsik said:
im getting this error
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
cant flash the stock rom
Click to expand...
Click to collapse
naeemdurrani said:
man dont use Qfil program.
the rom which you downloaded should be in zip format, unzip it, there is a file download_with_partiotion.bat.
run it and sit back until it is finished.
Click to expand...
Click to collapse
i cant use the .bat cause my phone is already bricked...it wont be recognize by the app...the only way is thru QFIL but the problem is that i always get the error above
Hi, same here. I tried using QFIL and getting Sahara Fail. Then tried clicking on the bat file but its not working since the phone is not recognized. Please help.
EDIT : I got the QFIL working just now and my phone is working. Flashed the stock rom and I think it will be just fine.
whiskey_1388 said:
Hi, same here. I tried using QFIL and getting Sahara Fail. Then tried clicking on the bat file but its not working since the phone is not recognized. Please help.
EDIT : I got the QFIL working just now and my phone is working. Flashed the stock rom and I think it will be just fine.
Click to expand...
Click to collapse
My phone was wiped by me . I have TWRP and my phone is read as ADB interface (when in recovery mode). I tried adb devices and it returned 1f82f24b recovery. I also can access my phone memory from PC when in TWRP recovery which enables me to transfer files.
My problem is it is only read as ADB interface not as Qualcom COM port device. When I try Download_with_partition.cmd I get the error that it can not distinguish devices and to try. Any solution by those managed to install it successfully?
For everyone landing in this page due to wiping his OS of Lenovo Phab Plus by mistake (like I did), please refer to this thread:
Lenovo Phab Plus PB1-770M Stock ROM needed
Thanks!
jotade said:
Well i did it. Is really simple but it seems nobody has this problem before. You need
- Download Stock Firmware from russian lenovo site
- The Tool i used is QPST_2.7.422 QFIL it cames with the Drivers (i used Win8.1)
- Put phone in Download mode (press vol up and down same time and connect phone to PC)
- Open QFIL program and select flat build
- In select programmer you select prog_emmc_firehose_8936.mbm
- In load xml i selected rawprogram_unsparse and path0
- After that you click download and wait like 4 min and when say finish succesfully you start phone manually
I hope this helps.
Click to expand...
Click to collapse
I was not doing the 8936.mbn part!
By default it is 8916 so it doesnt work. but after changing that setting, it work!:highfive::good:
I can't unbrick
Hi!
I have a Lenovo Phab PB1-770M, this phone won't turn on, only Lenovo logo, or fastboot or flashmode.
With Flashtool i can't flash. In Fastboot i flash a recovery or operating system, i reboot the phone and again only the Lenovo screen, operating system not starting.
What can i do?
naeemdurrani said:
man dont use Qfil program.
the rom which you downloaded should be in zip format, unzip it, there is a file download_with_partiotion.bat.
run it and sit back until it is finished.
Click to expand...
Click to collapse
this is what i get running the .bat command >
'adb' is not recognized as an internal or external command,
operable program or batch file.
╟δ╚╖▒ú╩╓╗·─▄╣╗╩╢▒≡adb╔Φ▒╕!╟δ╓╪╩╘úí
please ensure the phone can distinguish adb devices! Please retry!
Press any key to continue . . .
We will see here, how we can restore the device Lenovo P8 8703F (wifi) to the factory condition if stucks on the logo or after a brick ...There are several ways , for example ( Qfil, Qpst, eMMC DL, Qcom phone download tool,Qualcomm SW downloader, GNQC etc)
for devices with Qualcomm ,but we will see here an easy way with a tool known as QFIL (recomended) ...Before than all must we have the PC ready, with the appropriate drivers Installed ...
1)Disable driver signature enforcement on Windows 10 permanently/temporarily: a: https://windowsreport.com/driver-signature-enforcement-windows-10/
b: https://www.howtogeek.com/167723/how...igned-drivers/
_ How to disable Driver Signature Enforcement-Video:
(Windows 8, 8.1 & 10)
* _ OR : https://gsmusbdriver.com/fix-driver-signature-error
**(In windows 10,you may need to disable the "secure boot" from BIOS in some cases,before to do this)
( Or, just download this and follow the instructions : https://mega.nz/file/5rphEShJ#-VGvFPM0hZICZC28VQ6zqwHXLA9EEfv_8thiTXla1dY )
2)Qualcomm drivers : https://androiddatahost.com/nbyn6 (how to Install Qualcomm drivers >
)
tutorial & here : https://forum.hovatek.com/thread-16965.html
__Qualcomm drivers (MEGA Cloud) : https://mega.nz/file/0yRDmCYC#e-cadgzqeBcjlO7ThzF148q_dW8i_AATshC35nXbX8Y
__Qualcomm_USB_Driver_1.00.40.5_Setup.exe : https://mega.nz/#!Zq5C3K7A!7I3W9jh79-UbgvJ1dGIYCuj8cbxYtiXAXf4i-mO-VAQ
[Qualcomm usb drivers windows xp,7,8,8.1,10 32bit : https://mega.nz/file/JzAAHBBD#VOlN8HjgFqWfkD8LJafgJxKje18_l6o_vP9gmrja_JU ]
3)_[Important : [Qualcomm HS-USB QDLoader 9008 - Windows XP / 2000 / Vista / 7/8 / 8.1 / 10 x64 : http://www.mediafire.com/file/u3mrk0qan6qz5sq/Qualcomm_USBDriver_2.1.0.5_x64.cab
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-32-bit-windows/
4) QFIL ALL VERSIONS : https://androidmtk.com/download-qualcomm-flash-image-loader-qfil
5) THE STOCK FIRMWARE Lenovo P8 TB-8703F (wifi) : https://www.mediafire.com/file/nvdo3hq0r6mnoqs/TB-8703F_S000031_170616_ROW_QPST.7z
__MEGA CLOUD : https://mega.nz/#!NipTRSiJ!E5Ej-PWNOllLSfFLla7o_YOTkCkbbLR92Y_aZmMRJYo [FONT=source_sans_proregular](TB-8703F_S000030_170307_ROW_QFIL.7z)[/FONT]
(Source): http://lenovo-forums.ru/files/file/1831-tab3-a8-plus-proshivka-tb-8703f_s000031_170616_row_qpst/
[ For the tools we will use, if a code is requested pass : androidmtk.com / For Stock Firmware pass: lenovo-forums.ru ]
_[* https://firmwarefile.com/lenovo-tb-8703f > (three firmwares tb-8703f USR_S000032/34/35 + tutorials) ]
*For Lenovo P8 TB 8703X (3g-lte) STOCK ROM you can see post #2
__* IMPORTANT ! : Solution to the known problem (sometimes) : " Download Fail:Sahara Fail:QSaharaServer Fail Process fail error" - (Known as the "Sahara Fail Error")
1) disable driver signature ( See the link above )
_ a) Download and try with this version QPST (qfil included) : https://androiddatahost.com/np4wq
_b) Try to another USB port (?) [Try to connect device-pc on usb 2.0 & no on usb 3.0]
_ c) update your drivers : https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/ how to-Quide: https://www.gizmoadvices.com/qualcomm-hs-usb-qdloader-9008-driver/
_d) you must to press power button at the same time you plug in usb cable.....keep trying and your computer will start installing drivers for Port 9008
*_[Maybe you need to Install - update Microsoft NET Framework 4 : https://www.microsoft.com/en-US/download/details.aspx?id=17851
....If you already have instaled, skip this step]
[ The way through Qfil is recommended, has been successfully tested many times by many users & me...Download button will only become active when your device is connected properly! CONNECTED THE DEVICE TO THE COMPUTER BY HOLDING THE VOLUME UP KEY ! Take special care with steps 6,7,8 in tutorial Qfil here ! : https://androidmtk.com/use-qualcomm-flash-image-loader-qfil ....as most mistakes are made here ! Read carefully ....
_Your personal data will be deleted after flashing the stock firmware via Qfil ...
[ Charge your phone to at least 70% before use Qfil ! ]
__ do not hesitate to ask for help from other users , & read carefully before doing anything on your device...
__ please, be kind with everyone ! Tell your opinion freely or your problems for your device etc...
Via QFIL :
1) Download & extract QFIL on your PC...After extracting you will be able to see the Files > Screenshot 1
2)Now,open QFIL.exe > Screenshot 2 (as administrator)
3)Once QFIL is launched you will be able to see the following screen > Screenshot 3
4)Now,Switch OFF your Tablet > Screenshot 7
5)Once your device is Switched OFF, Press & Hold VOLUME UP KEY & CONNECT THE DEVICE TO PC, using USB Cable (attention to this step)
6)Now,in QFIL click on browse button & locate the Firmware (.mbn) > Screenshots 4+5
7)Once you have added the Firmware File, QFIL will automatically load the rest of the Firmware data (qfil detect your device in 9008 mode) > Screenshot 8
8)Now,click on the download button to begin the flashing process > Screenshot 6
9)Flashing process may take 10-15 min to complete (or less)
10)Once flashing process is completed your device will be reboot automatically...thats it , done!
__ All Steps are described & here in detail, read carefully without hurry & everything will be fine : https://androidmtk.com/use-qualcomm-flash-image-loader-qfil
[ QPST (qfil included) ] { https://androiddatahost.com/np4wq } Use this Version QPST if you have problem / error
** "Download Fail:Sahara Fail: QSaharaServer Fail: Process fail error" !
QPST ALL VERSIONS : https://androidmtk.com/download-qpst-flash-tool
Via QPST :
1. Download firmware, drivers and utilities Lenovo Tab P8 TB-8703F (wifi)
2. Unzip the archive contents and install the drivers and QPST utility
3. Run the QFIL utility (included)
4. In the "Select Build Type" set to "Flat Build"
5. Click "Browse" and from the folder with firmware (Images) select the file "prog_emmc_firehose_8953_ddr.mbn"
6. Click "Load XML" and select the file "rawprogram0.XML" and then "patch0.XML"
7. Switch the device off completely
8. Insert one end of the usb cable into the PC, hold down the device buttons to decrease and increase the volume and connect the other end of the usb cable to the device
9. The program must determine the phone, at the top instead of "No Port Available" should appear the name of your device and in brackets the port number (QFIL should detect your device in 9008 mode) > Screenshot 8
10. Press the "Download" button and wait for the operation to be completed
11. After the operation is completed, disconnect the device from the PC and turn it on
12. If everything is done correctly, the device will boot in about few minutes ..(if not, try again, you have made a mistake)
[ before the first start you can try wipe cache-wipe data/factory reset from stock recovery ]
_{ Important! : Press the volume up and plug the USB cable that is already connected to the USB port of your computer without releasing it.! Most mistakes are made here ! the "Qualcomm / Lenovo HS-USB QDLoader 9008" will appear at the top > Screensot 8 }
__Before starts download : Open device Manager in pc & make sure the QFIL program recognizes your device as the "Qualcomm Lenovo HS-USB QDLoader 9008 (com27 for example)" {screenshot 8 }
*[ Recommended: On PC, Latest VC ++ runtime environment / Net 4.0 or higher / Ram at least 2 GB + ]
[ Optionally: _Useful tools ... Lenovo MOTO Smart Assistant / windows7/10, 32&64 bit : https://support.lenovo.com/gr/el/downloads/ds101291
Lenovo site TAB3 8 Plus Tablet (TB-8703F, TB-8703X) Software (connect device-pc) :
https://pcsupport.lenovo.com/gr/el/products/tablets/a-series/tab3-8-plus?linkTrack=Caps:Body_SearchProduct&searchType=3&keyWordSearch=TAB3 8 Plus Tablet (TB-8703F, TB-8703X
_ *Lenovo TB-8703F Usb drivers(Qualcomm & ADB): https://gsmusbdriver.com/lenovo-tab-3-8-plus-tb-8703f
*TB-8703X(Qualcomm&ADB): https://gsmusbdriver.com/lenovo-tab-3-8-plus-tb-8703x
_ Threads about Lenovo P8 xda : https://forum.xda-developers.com/t/lenovo-p8
_ Find various drivers here : https://gsmusbdrivers.com/
_* How to flash stock firmware 8703F/X using QcomDloader Tool : https://androidmtk.com/use-qcomdloader-tool
* stock firmware : 8703F: https://firmwarefile.com/lenovo-tab-3-8-plus-tb-8703f
* 8703X : https://firmwarefile.com/lenovo-tab-3-8-plus-tb-8703x
__ [ Latest TWRP 3.2.3-0308 for TB-8703F & TB-8703X : https://forum.xda-developers.com/android/development/links-t3764658 ]
Lenovo P8 threads: https://forum.xda-developers.com/tags/lenovo-p8/
_[Be careful with the various tools and especially USB drivers, there may be newer versions now, from the time this article was written!]_
( I hope that several users will find help in this thread )
sry for english & GL to all
[ I have no responsibility for what does anyone on his device,nor I can be have responsible for the mistakes done by you]
Lenovo P8 TB 8703X (3g-lte) ONLY!
For the users with Lenovo P8 TB 8703X (3g-lte) ONLY! file TB-8703X_S000034_170525_ROW_QPST.7z
here : http://www.mediafire.com/file/4lg92szdza6coi2/TB-8703X_S000034_170525_ROW_QPST.7z
( pass: lenovo-forums.ru )
TB-8703X_S000036_171207_ROW / 07.12.2017 / 36.5mb - OTA Update! - (Only TB-8703X / 3g-lte) - [TB-8703X_S000035_170919_ROW_TO_TB-8703X_S000036_171207_ROW_WCD2C52B4F.zip
http://www.mediafire.com/file/pqyou...TO_TB-8703X_S000036_171207_ROW_WCD2C52B4F.zip
( pass: lenovo-forums.ru )
[source: http://lenovo-forums.ru/topic/25111...35_170919_row-to-tb-8703x_s000036_171207_row/ ]
__ 21-4-2018 OTA-update for Lenovo P8 TB-8703X (Lte,3g) ONLY! - TB-8703X_S000036_171207_ROW To: TB-8703X_S000037_180404_ROW : mediafire : http://www.mediafire.com/file/3s2bm...TO_TB-8703X_S000037_180404_ROW_WC39DCDC66.zip
(update Via Factory Recovery !)
__* Or, flash stock firmware 8703X using QcomDloader Tool : https://firmwarefile.com/lenovo-tab-3-8-plus-tb-8703x
__ For TWRP 3.2.1-0 & TWRP 3.2.3 Lenovo P8 (F+X) QPST & IMG Files , go to this thread:
https://forum.xda-developers.com/android/development/links-t3764658
__ 4/4/2018 TB-8703X_S000037_180404_ROW :
[MEGA CLOUD] TB-8703X (3g-Lte) - 39.8 Mb
https://mega.nz/file/h2gg1YhK#DkvZqOca0oBHbhViOBNWuHg1ojVZ7SVtprkilI4Fm4k
☆☆__Source : All updates for Lenovo Tab3 TB-8703X (3g-Lte) & Lenovo Tab3 TB-8703F (wifi)
Here : http://lenovo-forums.ru/files/category/152-lenovo-tab3-a8-plus-tb3-8703/
* For the quality - purity of the files I have no responsibility since I am not the developer of the files
Ty sir.. I have no problem until now but I like to have a way to save my device if needed
I'm afraid of the problem with updates .I see many users have the same problem
what does Lenovo for this?
Sonbd said:
Ty sir.. I have no problem until now but I like to have a way to save my device if needed
I'm afraid of the problem with updates .I see many users have the same problem
what does Lenovo for this?
Click to expand...
Click to collapse
Yes is true.I do not know what Lenovo is doing,I don't think he not knows the problem
device perhaps has a problem with bootloader or & recovery also (or maybe with partitions sizes) ..let us hope,Lenovo to fix it,the device has good features & in good price .he policy followed by Lenovo is unacceptable (do not allow unlocking of the bootloader ! )
sry for english
Many Thanks to Assistant Forum Admin / Moderator @ the_scotsman for his help ....Now we have all the device Lenovo P8 threads in a space ,and all users can find what they want very easily !
bravo, good job, man. thanks so much for this post!
i've done this flash thing already. and be careful that your wifi&bluetooth mac address gonna changed.
and also, it's better to backup Qcn file first.
---------- Post added at 10:09 PM ---------- Previous post was at 10:03 PM ----------
oh, there is question, i wanna make a full backup of the stock rom entirely, there is a post about it, https://forum.xda-developers.com/general/rooting-roms/how-to-backup-qualcomm-phone-root-t3570178,
im not pretty sure about the process, have you done it or know how to do it?
not download to the tab, but read from the tab, can qfil do this job?
not download to the tab, but read from the tab, can qfil do this job?[/QUOTE]
Full backup via qfil No! I do not know what he wants to do, but stay away, it is very dangerous all this for hard brick !
For full backup needed or custom recovery (nandroid backup) or rooted device & use some tool from playstore for backup etc..
You can flash twrp : https://forum.xda-developers.com/ge...vo-p8-tb-8703f-tb-8703x-t3689442#post74281359
and after you can get a full nandroid backup ..
except all this, backup for stock rom? and how to restore the backup? also, even if you have the twrp probably will not be able to restore a factory image backup...
sry for english
daitalos said:
not download to the tab, but read from the tab, can qfil do this job?Full backup via qfil No!
Click to expand...
Click to collapse
TB-8703F_S000031_170616_ROW_QPST.7z
I just want to know how is this file dumped or where did the Russians got this file.
Before I downloaded this file into my tablet, I flashed trwp recovery, and made a full backup of the Chinese version ROM . BUT the ORIGINAL lenovo recovery WAS GONE , RIGHT?
SO ..... without the original recovery the backup cannot be called a full backup right
Before I downloaded this file into my tablet, I flashed trwp recovery, and made a full backup of the Chinese version ROM . BUT the ORIGINAL lenovo recovery WAS GONE , RIGHT?
SO ..... without the original recovery the backup cannot be called a full backup right[/QUOTE]
I told you...custom recovery can not flash (or reset) factory image backup (this version twrp decrypt device because Lenovo P8 has a locked bootloader etc..)
backup of stock rom is useless in this device, you can flash stock rom if you want, via Qfil
daitalos said:
If after an ota update the device sticks and it does not start , try it first ! wipe cache - wipe data/factory reset from stock recovery before using Qfil...
In most cases the device starts - boot normally
[ optional - I recommend , Install on your pc this powerful tool : minimal adb & fastboot from here : https://forum.xda-developers.com/showthread.php?t=2317790 & read carefully before Installing ]
For the users with Lenovo P8 TB 8703X (3g-lte) ONLY! file TB-8703X_S000034_170525_ROW_QPST.7z
here : http://www.mediafire.com/file/4lg92szdza6coi2/TB-8703X_S000034_170525_ROW_QPST.7z
Click to expand...
Click to collapse
Hello Friend This File is Password Protected....
need its password Plzz..
Ok i found the password.. the password is " lenovo-forums.ru "
DanishAlnoor said:
Hello Friend This File is Password Protected....
need its password Plzz..
Ok i found the password.. the password is " lenovo-forums.ru "
Click to expand...
Click to collapse
before posting Read first ! keep the thread clean please
Hi to all,
I managed to brick my lenovo TB-8703F after updating Magisk through the TWRP recovery mode.
At first it got into a boot loop and I tried to recover it by flashing the stock rom with the instructions found on this thread.
Unfortunately No luck.....
The tablet was recognized in Qloader Mode and flashed with QFIL but after the flash completed successfully it hanged at lenovo logo boot screen.
Tried wipe data - factory reset without luck.
Now after many attempts with QFIL and different settings it is only recognized in Qualcomm HS-USB Diagnostics 900E mode and cannot be flashed with QFIL, no access to recovery mode, fast boot or anything else....
Do you thing I have a chance of recovering it?
Thanks
panmark said:
Now after many attempts with QFIL and different settings it is only recognized in Qualcomm HS-USB Diagnostics 900E mode and cannot be flashed with QFIL, no access to recovery mode, fast boot or anything else....
Do you thing I have a chance of recovering it?
Thanks
Click to expand...
Click to collapse
Qualcomm drivers are installed correctly; you can try with QPST version from link of OP (Qfil included)
(Disable driver signature?)
daitalos said:
Qualcomm drivers are installed correctly; you can try with QPST version from link of OP (Qfil included)
(Disable driver signature?)
Click to expand...
Click to collapse
Drivers must be OK. (they worked before the hard brick.)
I tried with a deep flash cable but I had no luck.....
Then I opened the case and removed the battery left it for two minutes and tried again. No luck....
I thing I now have a nice paper weight for my office.....
The strange think is that before the hard brick I successfully managed to complete the flashing process for ten or more times but the tablet refused to boot.
panmark said:
Drivers must be OK. (they worked before the hard brick.)
I tried with a deep flash cable but I had no luck.....
Then I opened the case and removed the battery left it for two minutes and tried again. No luck....
I thing I now have a nice paper weight for my office.....
The strange think is that before the hard brick I successfully managed to complete the flashing process for ten or more times but the tablet refused to boot.
Click to expand...
Click to collapse
Does anybody know the test points that have to be shorted in order to force it to connect to EDL 9008 mode?
panmark said:
Does anybody know the test points that have to be shorted in order to force it to connect to EDL 9008 mode?
I've seen it...tools are needed,and there is always a risk of error...I think there is a video with details..
I do not know how much credibility it can be this method....
Click to expand...
Click to collapse
panmark said:
Does anybody know the test points that have to be shorted in order to force it to connect to EDL 9008 mode?
Click to expand...
Click to collapse
Badly translated from Russian
A test point is detected (wi-fi version of the tablet, it may work on lte).
So, install QPST, drivers, download firmware, prepare QFIL for firmware (the instruction is in the subject), when connecting, the brick is defined as HS-USB Diagnostics 900E, disconnect usb cable, disassemble the tablet, turn off the acb, tweeze the pin specified in the photo on the iron frame, hold, do not release the jumper and connect usb, then connect the acb, as soon as the computer determines HS-USB Qdloader 9008
release the jumper and click download in QFIL.
Click to expand...
Click to collapse
obvious said:
Badly translated from Russian
Click to expand...
Click to collapse
thanks!!!!
I will give it a try and lets you know!
---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------
panmark said:
thanks!!!!
I will give it a try and lets you know!
Click to expand...
Click to collapse
It Works!!!!!!!!!!!
Thanks!!!!!
Know back to QFIL.
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
panmark said:
thanks!!!!
I will give it a try and lets you know!
---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------
It Works!!!!!!!!!!!
Thanks!!!!!
Know back to QFIL.
Click to expand...
Click to collapse
Flashed Successfully with QSTP (QFIL) according to the instructions!!!!!!
You are the man my friend!!!!!!!
panmark said:
thanks!!!!
I will give it a try and lets you know!
---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------
It Works!!!!!!!!!!!
Thanks!!!!!
Know back to QFIL.
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
Flashed Successfully with QSTP (QFIL) according to the instructions!!!!!!
You are the man my friend!!!!!!!
Click to expand...
Click to collapse
Haha, I'm glad it worked
panmark said:
thanks!!!!
I will give it a try and lets you know!
---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------
It Works!!!!!!!!!!!
Thanks!!!!!
Know back to QFIL.
---------- Post added at 08:59 PM ---------- Previous post was at 08:46 PM ----------
Flashed Successfully with QSTP (QFIL) according to the instructions!!!!!!
You are the man my friend!!!!!!!
Click to expand...
Click to collapse
I post a better quality photo for everyone
Hello all, so long story short I had bought a BLU G9 Pro which came with Android 9 Pie. The only device-specific guide I could find online about obtaining root was: https://www.getdroidtips.com/root-blu-g9-pro/
The information on that guide is trivial and can be applicable to almost any device. The root method worked, however, there was an OTA update to Android 10 (and then later a security update) which I took. I then attempted to re-root the device utilizing the same method. However, now it seems that everytime I flash a Magisk modded boot.img my device gets stuck in a bootloop and will not go past the bootloader. I believe that this device may be uncharted territory but it is a great phone and I would love to have both Magisk root and the latest Android 10 firmware. I have found that Magisk supports both Android 10 and A-only devices so I do not see what is causing the problem. Additionally, I attempted to flash an AOSP GSI of Android 10 which refused to boot before I even installed Magisk. I am new to modern Android devices with Project Treble so please forgive me if there is something obvious I am missing. Any help is appreciated, thanks in advance!
@eLatErbI
Try flashing GSI like said in https://source.android.com/setup/build/gsi#flashing-gsis
May be vbmeta flashing is required for your device.
You can get vbmeta.img from your stock firmware.
It seems that Verified Boot could definitely be getting in the way. Could this possibly explain why Magisk is working on the Android 9.0 version of the stock ROM but not Android 10? However, I thought Magisk disabled verified boot in the kernel (boot.img) also I do not have a vbmeta.img in any stock firmware for this phone. Any other means of disabling verified boot? Thanks in advance!
Hi, I have the same problem with my G9 PRO, I tried to boot all kinds of GSI roms with and without magisk and it doesn't work (bootloop). I cannot find the vbmeta partition anywhere so I am hesitant to try to flash it without a backup. There is a mention of it in the fstab of the boot partition, however it is not in the stock firmware or in my own backups. Magisk did also work for me before the Android 10 update. Does anyone have an idea of how AVB works without a vbmeta partition or a verity file?
You can extract the boot.img from your phone if you updated to 10. I updated and used SP Flash to read the boot.img and WwR_MTK to get the partition length and starting value for the boot.img and patched it using Magisk and reflashed it over fastboot. I know this thread is a bit old but if anyone is interested, reply and I will post the link that explains. I have Android 10 running on my Blu G9 pro rooted.
tuffasagong said:
You can extract the boot.img from your phone if you updated to 10. I updated and used SP Flash to read the boot.img and WwR_MTK to get the partition length and starting value for the boot.img and patched it using Magisk and reflashed it over fastboot. I know this thread is a bit old but if anyone is interested, reply and I will post the link that explains. I have Android 10 running on my Blu G9 pro rooted.
Click to expand...
Click to collapse
Hi. Please post the link. It will be very helpful for me. I have the BLU_G0231WW android 10.
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
Thank tuffasagong.
I now have my blu g9 pro magisk rooted on Android 10. I added viper4Android, Adaway and more tweaks.
Have you noticed the desktop mode when screen casting to second display? I wonder if there is a way to reduce lag when using bluetooth mous.
&oot4peace said:
Thank tuffasagong.
I now have my blu g9 pro magisk rooted on Android 10. I added viper4Android, Adaway and more tweaks.
Have you noticed the desktop mode when screen casting to second display? I wonder if there is a way to reduce lag when using bluetooth mous.
Click to expand...
Click to collapse
flashed magisk but bricked phone Does anyone happen to have g9 pro v10 firmware G0230WW or G0231WW readback rom? please i need to unbrick and firmware on web wont work. Please help..
Tesh3180 said:
flashed magisk but bricked phone Does anyone happen to have g9 pro v10 firmware G0230WW or G0231WW readback rom? please i need to unbrick and firmware on web wont work. Please help..
Click to expand...
Click to collapse
Search here: BLU Stock Firmware Repository (Mediafire)
lopestom said:
Search here: BLU Stock Firmware Repository (Mediafire)
Click to expand...
Click to collapse
thanks but already tried that file and wont work..
Tesh3180 said:
thanks but already tried that file and wont work..
Click to expand...
Click to collapse
Which version were you on? The latest at the time? A little more info did you flash a Magisk patched boot image?
Blu pushed out a new update 10.0.04.08 a couple weeks ago. Reflash the stock Boot image to update. Boot image has the same length and start addresses. I just reflashed the magisk Boot image I made with 10.0.04.07 and works fine.
tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
I've followed this and have gotten quite far but I can't seem to find any working fastboot drivers for the G9 pro, I have tried several different ones and with every one I get absolutely no hits on "fastboot devices" and upon any attempts to flash, it leaves me at "waiting for device" I just want to know if you had a specific driver or if it's different issue
Cathedralruins said:
I've followed this and have gotten quite far but I can't seem to find any working fastboot drivers for the G9 pro, I have tried several different ones and with every one I get absolutely no hits on "fastboot devices" and upon any attempts to flash, it leaves me at "waiting for device" I just want to know if you had a specific driver or if it's different issue
Click to expand...
Click to collapse
Use the Platform Tools for A9 or A10.
Downloads - Read and accept the terms.: platform-tools-latest-windows.zip
Device need OEM Unlock & USB Debugging enable.
Maybe your PC need USB Drivers: drivers USB OEM
Maybe need MTK USB driver: MTK Driver
lopestom said:
Use the Platform Tools for A9 or A10.
Downloads - Read and accept the terms.: platform-tools-latest-windows.zip
Device need OEM Unlock & USB Debugging enable.
Maybe your PC need USB Drivers: drivers USB OEM
Maybe need MTK USB driver: MTK Driver
Click to expand...
Click to collapse
First off, thank you for your really speedy assistance with this, I appreciate it.
A couple things, to note, the device has already had OEM unlocking and usb debugging enabled, it works with adb, but is not recognized at all by fastboot itself, I'm definitely going to try those drivers and that version of the platform tools. Is there any log, device list, or any other info I can dump that would be useful in troubleshooting this?
Thanks again for your assistance, lopestom.
Cathedralruins said:
First off, thank you for your really speedy assistance with this, I appreciate it.
A couple things, to note, the device has already had OEM unlocking and usb debugging enabled, it works with adb, but is not recognized at all by fastboot itself, I'm definitely going to try those drivers and that version of the platform tools. Is there any log, device list, or any other info I can dump that would be useful in troubleshooting this?
Thanks again for your assistance, lopestom.
Click to expand...
Click to collapse
Bootloader unlocked?
Authorization PC vs device already has with USB debugging?
If yes so look drivers.
Hello there,
My technical skills when comes to android phones is next to zero, but I have been running linux (Fedora, Endeavour, currently Debian 11), I am not affraid of the terminal.
I have bought a Blu g9 pro, like 3 months ago, it came out of the box with android 9, then It updated to android 10.
It is very close to stock android, and I am ok with it, exept for a few creepy apps that I would like to remove,
I would like your input on what is the safest aproach, can I just 'debloat' the current system? or might as well replace it with something else?
Thank you.
I attempted to flash the patched boot image from Magisk but my G9 Pro started boot looping. I've tried to flash every firmware that I can find for this model but I keep getting an error message from the Flash tool.
Any guidance?
tuffasagong said:
Here is the link: https://forum.hovatek.com/thread-21970.html
This is what I did to root the phone:
Download WwR_MTK 2.30 and SP Flash (I used version 5.2112)
**Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G9 Pro is MT6771. Click create and save as - I saved all files in one folder.
**Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it.
**Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0 (once again I saved it in the same folder as the scatter file) -- the Start Address is in the scatter file as "physical_start_addr:" it should be 0x0 and the length is "partition_size:" and the value should be 0x80000. Keep the Region as EMMC_USER unless you want the preloader but to get the boot.img we don't need that. Turn off your phone and press the Read Back button with the Arrow and plug your phone into the computer. It will read the file and give you a big Green Check to let you know it completed succesfully.
**Once you have the ROM_0 open it up in WwR_MTK 2.30 Under Step 3 (Choose the EMMC_USER partition in the prepared backup) you will get an error that says "The file size is smaller than the start position of the LK (uboot)" press OK -- You will get another error that says "To determine the ype of process and memory.... blah blah blah" Press OK
**Click the Scatter File tab -- Under the Name field find boot. We now get the starting value of the boot.img and the partition length. We need these values to put back into SP Flash.
**Go to SP Flash and Readback tab again. Press add. Double Click the new add and save it as boot.img -- Region is EMMC_USER and the start address is going to be the HEX value next to Boot and length the length address next to boot. For the BLU_G0231WW_V10.0.04.07_GENERIC Build these addresses are:
Start: 0x20C00000 and Length: 0x2000000
Push ok when you put the start address and length for the boot.img and once again push Readback and connect your phone while off. The File size I got was a boot.img of 32,768 KB in size which is much bigger than the boot.img of the Android 9 (which was like 9 MB in size).
**Install Magisk on the phone and patch the boot.img and flash it with fastboot and boom, you have a rooted BLU G9 Pro with the latest Update. Keep your stock boot.img as I rooted my phone with the 10.0.04.04 update and could not update to 10.0.04.07 until I reflashed the stock boot.img in case there is another update.
That is all there is to it and you should be able to use this tutorial to root if BLU pushes anymore updates.
Click to expand...
Click to collapse
Saved me - TY. This worked for me for Mintt Ultramintt Y3 - basically an Aussie rebadged Blu G9 Pro. I used this method for it with Pie 9 (before allowing update to 10). Cheers
Hello team,
Recently I bought the Lenovo p11 from a well known China online store. It came with a pretty old non-OTA rom so I decided to flash a new one. However, the flashing failed and my tablet is stuck now in the fastboot mode. It can be recognised by fastboot but not from adb. So, I cannot reflash it. All options return to the fastboot. Bootloader is locked and I see that Device state is locked. Is there any idea how to unbrick it?
Thanks in advance
skarapost said:
Bootloader is locked and I see that Device state is locked. Is there any idea how to unbrick it?
Thanks in advance
Click to expand...
Click to collapse
It;s not brick. QFIL can flash full firmware,
skarapost said:
Hello team,
Recently I bought the Lenovo p11 from a well known China online store. It came with a pretty old non-OTA rom so I decided to flash a new one. However, the flashing failed and my tablet is stuck now in the fastboot mode. It can be recognised by fastboot but not from adb. So, I cannot reflash it. All options return to the fastboot. Bootloader is locked and I see that Device state is locked. Is there any idea how to unbrick it?
Thanks in advance
Click to expand...
Click to collapse
Did you fix it? I have the same issue now.
Thanks!
Hello,
my lenovo tap11 totall bricked
but i have a unlocked bootloader and a stock recovery
i tried many time to flash stock rom with QFIL i have the right drivers it connect edl mode
but every time the flash failed can not make new partitions and wipe the orginal ones
and i had have a twrp recovery on it but also gone and can not flash it back in fastboot mode also fails
i have the right rom for the p11 orginal
what i need is the right way to flash the stock rom,there is info enough but no option works
can some one help me out?
thanks
solved tje problem tablet boots up again with stock rom
flashed with rescue software from lenovo
fv1ede said:
solved tje problem tablet boots up again with stock rom
flashed with rescue software from lenovo
Click to expand...
Click to collapse
Hi there.
You can provide the drivers and some instructions for unbrick
Thanks.
Sorry for my English.
The tablet that they have left me only starts in fastboot mode and I can only communicate with it using fastboot commands. Can I do something to get it back?
Thanks and sorry for my English.
arturito109 said:
The tablet that they have left me only starts in fastboot mode and I can only communicate with it using fastboot commands. Can I do something to get it back?
Thanks and sorry for my English.
Click to expand...
Click to collapse
you need the qualcom driver its in the flash software,and you must set the tablet in edl mode.
EDLmode Shutt off tablet when off only push volume up and connect tablet with pc .
then if you have the qualcomm driver installed you see the connection in the device manager of windows.
After that the rescu software did for me the job, and the p11 boots up again.
i have allready unlocked the bootloader,and flash the twrp recovery again after that i root the p11 with magisk all done.
fv1ede said:
you need the qualcom driver its in the flash software,and you must set the tablet in edl mode.
EDLmode Shutt off tablet when off only push volume up and connect tablet with pc .
then if you have the qualcomm driver installed you see the connection in the device manager of windows.
After that the rescu software did for me the job, and the p11 boots up again.
i have allready unlocked the bootloader,and flash the twrp recovery again after that i root the p11 with magisk all done.
Click to expand...
Click to collapse
Hi! can i ask how to do the EDL mode? also will it work even if i forgot to OEM unlock in the developer mode before flashing? Although i did the USB debugging. Thanks!
skarapost said:
Hello team,
Recently I bought the Lenovo p11 from a well known China online store. It came with a pretty old non-OTA rom so I decided to flash a new one. However, the flashing failed and my tablet is stuck now in the fastboot mode. It can be recognised by fastboot but not from adb. So, I cannot reflash it. All options return to the fastboot. Bootloader is locked and I see that Device state is locked. Is there any idea how to unbrick it?
Thanks in advance
Click to expand...
Click to collapse
My P11 is same situation .
https://imgur.com/a/J9Eyi7I
Download with the Smart Assistant Tool from Lenovo latest firmware version TB_J606F_S320029_210923_ROW.
If you have the chinese version you can download it here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Start Qfil.
The Qfil file is where the new firmware by Rescue and Smart Assistant is stored.
For me it was in the folder c:/ProgramData/RSA/Download/RomFiles/ToolFiles/Qfil
1: The tablet must not be connected to the computer and must be off.
2: Now start Qfil, at the top of the screen is now "No Port Available" start now the tablet by holding down the Volume + button and at the same time connecting the USB
cable to the computer or laptop, You will feel a slight vibration in the tablet.
3: Now you see in the screen that a port is present, so you are now in contact with the Qfil programmer.
4: In the Qfil screen you will see "Select Build Type" choose "Flat Build"
5: At "Select Programmer" press "Browse" choose there prog_firehose_ddr.elf
6: Now press "Load XML" and choose rawprogram_unsparse0 and patch0
7: Now press "Download" the installation will now start so wait until it is finished
8: After the installation is finished, disconnect the USB connection and restart the tablet:
9: The tablet may start up with the FFBM mode screen, then turn the tablet off again by holding the power button for longer seconds.
10: Start the tablet by pressing the volume - button and the power button.
11: In the screen choose with the volume buttons "Recovery" then in de next screen "Reboot system", the tablet will now start up normally again, this will take a while so wait patiently.
12: Then you come to the welcome screen, this was it and the tablet should now work properly again with the new Android 11 version, good luck!
comtech2005 said:
Download with the Smart Assistant Tool from Lenovo latest firmware version TB_J606F_S320029_210923_ROW.
Start Qfil.
The Qfil file is where the new firmware by Rescue and Smart Assistant is stored.
For me it was in the folder c:/ProgramData/RSA/Download/RomFiles/ToolFiles/Qfil
1: The tablet must not be connected to the computer and must be off.
2: Now start Qfil, at the top of the screen is now "No Port Available" start now the tablet by holding down the Volume + button and at the same time connecting the USB
cable to the computer or laptop, You will feel a slight vibration in the tablet.
3: Now you see in the screen that a port is present, so you are now in contact with the Qfil programmer.
4: In the Qfil screen you will see "Select Build Type" choose "Flat Build"
5: At "Select Programmer" press "Browse" choose there prog_firehose_ddr.elf
6: Now press "Load XML" and choose rawprogram_unsparse0 and patch0
7: Now press "Download" the installation will now start so wait until it is finished
8: After the installation is finished, disconnect the USB connection and restart the tablet:
9: The tablet may start up with the FFBM mode screen, then turn the tablet off again by holding the power button for longer seconds.
10: Start the tablet by pressing the volume - button and the power button.
11: In the screen choose with the volume buttons "Recovery" then in de next screen "Reboot system", the tablet will now start up normally again, this will take a while so wait patiently.
12: Then you come to the welcome screen, this was it and the tablet should now work properly again with the new Android 11 version, good luck!
Click to expand...
Click to collapse
All was going right, but after finishing all these steps, got this message:
Is it possible to solve this issue?
I think you have the chinese version which has different hardware.
Download the chinese firmware version here:
https://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F
fdMO12 said:
All was going right, but after finishing all these steps, got this message:
Is it possible to solve this issue?
Click to expand...
Click to collapse
Check Region Unlock!! P11 [TB-J606F/L/N]
This method was shared by Koreans at the Ppomppu Forum. When Check Region Unlock is performed, firmware downgrade and update are free. Chinese ROM ZUI(12.6) check region introduce Global ROM 210805 check region introduce How To Guide (Check...
forum.xda-developers.com
I tried to unbrick my P11 and QFIL had this error in the log:
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the SDCC Device slot 0 partition 0" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 0 partition 0'
08:38:00: DEBUG: XML FILE (131 bytes): CharsInBuffer=480-131=349
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device:1 slot:0 partition:0 error:0" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:0 partition:0 error:0'
08:38:00: DEBUG: XML FILE (123 bytes): CharsInBuffer=349-123=226
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: OPEN handle NULL and no error, weird 344370596" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 344370596'
08:38:00: DEBUG: XML FILE (132 bytes): CharsInBuffer=226-132=94
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3'
08:38:00: DEBUG: XML FILE (94 bytes): CharsInBuffer=94-94=0
Anything I can do to fix this?
JiiJii said:
I tried to unbrick my P11 and QFIL had this error in the log:
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the SDCC Device slot 0 partition 0" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: Failed to open the SDCC Device slot 0 partition 0'
08:38:00: DEBUG: XML FILE (131 bytes): CharsInBuffer=480-131=349
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open the device:1 slot:0 partition:0 error:0" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: Failed to open the device:1 slot:0 partition:0 error:0'
08:38:00: DEBUG: XML FILE (123 bytes): CharsInBuffer=349-123=226
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: OPEN handle NULL and no error, weird 344370596" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: OPEN handle NULL and no error, weird 344370596'
08:38:00: DEBUG: XML FILE (132 bytes): CharsInBuffer=226-132=94
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3" /></data>
-------------------------------------------------------------------------------------------
08:38:00: INFO: TARGET SAID: 'ERROR: Failed to open device, type:eMMC, slot:0, lun:0 error:3'
08:38:00: DEBUG: XML FILE (94 bytes): CharsInBuffer=94-94=0
Anything I can do to fix this?
Click to expand...
Click to collapse
Did you install Qualcom USB drivers?
mardon85 said:
Did you install Qualcom USB drivers?
Click to expand...
Click to collapse
Yes, and the connection works. There's something wrong with the partitions i think.
Me too, help me
comtech2005 said:
Download with the Smart Assistant Tool from Lenovo latest firmware version TB_J606F_S320029_210923_ROW.
If you have the chinese version you can download it here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Start Qfil.
The Qfil file is where the new firmware by Rescue and Smart Assistant is stored.
For me it was in the folder c:/ProgramData/RSA/Download/RomFiles/ToolFiles/Qfil
1: The tablet must not be connected to the computer and must be off.
2: Now start Qfil, at the top of the screen is now "No Port Available" start now the tablet by holding down the Volume + button and at the same time connecting the USB
cable to the computer or laptop, You will feel a slight vibration in the tablet.
3: Now you see in the screen that a port is present, so you are now in contact with the Qfil programmer.
4: In the Qfil screen you will see "Select Build Type" choose "Flat Build"
5: At "Select Programmer" press "Browse" choose there prog_firehose_ddr.elf
6: Now press "Load XML" and choose rawprogram_unsparse0 and patch0
7: Now press "Download" the installation will now start so wait until it is finished
8: After the installation is finished, disconnect the USB connection and restart the tablet:
9: The tablet may start up with the FFBM mode screen, then turn the tablet off again by holding the power button for longer seconds.
10: Start the tablet by pressing the volume - button and the power button.
11: In the screen choose with the volume buttons "Recovery" then in de next screen "Reboot system", the tablet will now start up normally again, this will take a while so wait patiently.
12: Then you come to the welcome screen, this was it and the tablet should now work properly again with the new Android 11 version, good luck!
Click to expand...
Click to collapse
not work, bootloop. help me
mklevi said:
My P11 is same situation .
https://imgur.com/a/J9Eyi7I
Click to expand...
Click to collapse
me too
Info about procedure
We will be flashing a bootloader taken from development firmware which contains all the normal fastboot commands and is signed with the production key. This allows us to properly unlock the bootloader the standard way.
This has only been tested on PB-6505M and PB-6505NC !
There is a very good chance of this this working on PB-6505MC and PB-6505Y but it has not been confirmed, be warned if the debug PB-6505M bootloader is not compatible it will likely brick the device. Please contact me before attempting it.
How to flash the debug bootloader
(Windows) QFIL
Download and install the Qualcomm drivers from here
Download the debug bootloader flash package from below
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Unplug and turn off your tablet
Hold vol+ and then plug in your tablet
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete make sure your phone is off and then hold vol+ and power until it vibrates and then let go of power but keep holding vol+ until fastboot screen appears
Now you can "fastboot flashing unlock" the standard way
(Windows) EMMCDL
Download and install the Qualcomm drivers from here
Download and unpack emmcdl tool from here
Download the debug bootloader flash package from below
Extract the firmware to a folder
Run the flash.bat file in the emmcdl and fill in what it asks for
(Linux, Mac, Advanced Windows)
Use Bkerler's Amazing EDL Toolkit Here
Downloads
Debug Bootloader flash package
here
Stock Lenovo Firmware can be found
here
S000046 Engineering/Factory Testing firmware (Designed for developers, limited features DO NOT USE)
here
Thanks @AndyYan for testing PB-6505NC
I will only be responding to discussion directly related to the flashing and unlock procedure or questions related to the engineering firmware. Please have twrp, rooting, mods discussion in other threads.
Astronomical man. Another hit out of space. More research!! Im just kidding.
thanks for your information, I unlocked my Lenovo PB-6505MC successfully using your method. when checking device unlock status, it returned some info like:
DM variety counter:0.
Device tampered: false,
Device cretical unlocked: false
((what these mean?))
I want to install magisk, and then patch boot file, but as it is Android 9 device, do I need some steps for disabling DM variety? if so what is the code and when to write these codes?
OK, after few trials, I could root my device successfully.
Здравствуйте!
Нельзя ли более подробную инструкцию по этой программе
(Windows) EMMCDL
Пытаюсь понять эту последовательность "fill in what it asks for" но не могу ))
Download and install the Qualcomm drivers from here
Download and unpack emmcdl tool from here
Download the debug bootloader flash package from below
Extract the firmware to a folder
Run the flash.bat file in the emmcdl and fill in what it asks for
deadman96385 said:
Info about procedure
We will be flashing a bootloader taken from development firmware which contains all the normal fastboot commands and is signed with the production key. This allows us to properly unlock the bootloader the standard way.
This has only been tested on PB-6505M and PB-6505NC !
There is a very good chance of this this working on PB-6505MC and PB-6505Y but it has not been confirmed, be warned if the debug PB-6505M bootloader is not compatible it will likely brick the device. Please contact me before attempting it.
How to flash the debug bootloader
(Windows) QFIL
Download and install the Qualcomm drivers from here
Download the debug bootloader flash package from below
Extract the firmware to a folder that you can easily access them from like your desktop
Download and install QPST from here
Open the QFIL application (Find it in your start menu)
In the "Select Build Type" field select Flat Build
In the "Select Programmer" field navigate to the folder you extracted the firmware and support files to and select the prog_emmc_firehose_8953_ddr.mbn file
Select the "Load XML" button and navigate to the folder you extracted the firmware and support files to and select the rawprogram_unsparse.xml and then the patch0.xml when prompted.
Unplug and turn off your tablet
Hold vol+ and then plug in your tablet
If the text at the top of the QFIL application mentions qdloader move on to next step. If it says "No Port Available" click the "Select Port..." option and pick your device. If your device isn't showing up there you most likely didn't install the drivers properly.
Click the Download Button to begin flashing your device
Once complete make sure your phone is off and then hold vol+ and power until it vibrates and then let go of power but keep holding vol+ until fastboot screen appears
Now you can "fastboot flashing unlock" the standard way
(Windows) EMMCDL
Download and install the Qualcomm drivers from here
Download and unpack emmcdl tool from here
Download the debug bootloader flash package from below
Extract the firmware to a folder
Run the flash.bat file in the emmcdl and fill in what it asks for
(Linux, Mac, Advanced Windows)
Use Bkerler's Amazing EDL Toolkit Here
Downloads
Debug Bootloader flash package
here
Stock Lenovo Firmware can be found
here
S000046 Engineering/Factory Testing firmware (Designed for developers, limited features DO NOT USE)
here
Thanks @AndyYan for testing PB-6505NC
I will only be responding to discussion directly related to the flashing and unlock procedure or questions related to the engineering firmware. Please have twrp, rooting, mods discussion in other threads.
Click to expand...
Click to collapse
qfil download fail:sahara fail;Qsaharaserver failrocess fail
kurdiak said:
thanks for your information, I unlocked my Lenovo PB-6505MC successfully using your method. when checking device unlock status, it returned some info like:
DM variety counter:0.
Device tampered: false,
Device cretical unlocked: false
((what these mean?))
I want to install magisk, and then patch boot file, but as it is Android 9 device, do I need some steps for disabling DM variety? if so what is the code and when to write these codes?
Click to expand...
Click to collapse
can you teach me
shairol said:
qfil download fail:sahara fail;Qsaharaserver failrocess fail
Click to expand...
Click to collapse
I also cannot get past this , ts can you help with this error
voidsanz said:
I also cannot get past this , ts can you help with this error
Click to expand...
Click to collapse
no
Hi everyone!
My PB-6505M is brick. I was flash stock firmware and it boot normally. But i have a new problem.
My device have no imei ( it show 0000000000000000), detect sim card but not have signal can't call and message.
I need QCN file to restore and try fix that problem. If you have same device, please help me.
Thank you very much.
(Sorry my bad english)