Database Info

Working download link for stock Firmware India LG P 500

Model LG P 500
I have successfully put my phone on emergency mode so will give it a try to boot by flashing the stock Firmware couldn't find any Working download link for stock Firmware India...
Kindly share the instructions to boot it back and with the working download link....got fed up googling
LG P 500

here we go...
[email protected] said:
Model LG P 500
I have successfully put my phone on emergency mode so will give it a try to boot by flashing the stock Firmware couldn't find any Working download link for stock Firmware India...
Kindly share the instructions to boot it back and with the working download link....got fed up googling
LG P 500
Click to expand...
Click to collapse
Code:
USING KDZ IS SKILLFULL ART AND IMPROPER USE CAN LEAD TO PERMENENT HARD BRICKED PHONE
Someone sad that following worked, someone that not. You must try and you will see...
1) Get serial number of your phone
2) Enter it in URL csmg.lgmobile.com:9002/svc/popup/model_check.jsp?model=<model_of_phone>&esn=<serial_number>
Code:
csmg.lgmobile.com:9002/svc/popup/model_check.jsp?model=[COLOR=Red]LGP500[/COLOR]&esn=[COLOR=Red]000KPPB001234[/COLOR]
3) Show page that you get in source-code view
Code:
<?xml version='1.0' encoding='utf-8' ?>
<response req_cmd='check_model' status='ok'>
<auth>
<model>LGP500</model>
<suffix>ASEABK</suffix>
<esn>[COLOR=Red]123456789012345[/COLOR]</esn>
<msn>000KPPB001234</msn>
<esndate>20101201</esndate>
<buyer>SEA</buyer>
<esnoutgodate>20101203</esnoutgodate>
<ULocationcode>N</ULocationcode>
<buyername>HUB</buyername>
<csn>LG0000440022331</csn>
</auth> </response>
4) select & copy number between <esn> elements (123456789012345)
5) Enter this number to csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=<enter_esn_number_here>
Code:
csmg.lgmobile.com:9002/svc/popup/model_check.jsp?esn=[COLOR=Red]123456789012345[/COLOR]
If it won't work, you can try new link provided by kutysam (make thanks him on some of his post please)
Code:
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=[COLOR=Red]123456789012345[/COLOR]
6) Show page as source-code view
Code:
<?xml version='1.0' encoding='utf-8' ?>
<response req_cmd='auth_model_check' status='OK'>
<auth_model_check>
<result>OK</result>
<esn>123456789012345</esn>
<model>LGP500</model>
<suffix>ASEABK</suffix>
<msn>000KPPB001234</msn>
<esn_date>20101201</esn_date>
<sw_version>V10E_00</sw_version>
<sw_url>http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ASEABK/V10e_00/V10E_00.kdz</sw_url>
<sw_locale_url>[B]http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/ASEABK/V10e_00/V10E_00.kdz[/B]</sw_locale_url>
<sw_recommand_uri>GLOBAL/GLOBAL</sw_recommand_uri>
<app_version></app_version>
<app_url></app_url>
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type>EG</chip_type>
<prod_type>GSM</prod_type>
</auth_model_check> </response>
Here u will get url for firmware package (~117 mb)
download it on pc .
How To Flash With KDZ
1. Download KDZ updater and uncompress it
http://www.4shared.com/file/UleS4dP3/
KDZ_FW_UPD_EN.html
2. Install msxml.msi from the uncompressed
directory
3. Charge your battery to almost full state (I'm
not sure, but it can be reason if phone
doesn't start)
4. Turn phone off somehow (remove battery
etc.)
5. Install drivers properly
Get rid of all usb drivers like Nokia,
microsoft visual ++ run time environments
Install the LG drivers by selecting the update
manager from the lg site
Disable LGE Virtual Modem. In your Windows
operating system, go to Control Panel >
System > Hardware > Device Manager >
Modems > Right click on LGE Virtual Modem
and click Disable.
6. Enter emergency mode and connect ur device with USB cable to PC.
7. Yellow screen with text emergency mode
should appeared
8.Btw use good quality stock usb cable.
9.run KDZ_FW_UPD.exe (Has administrator).
Select Type : 3GQCT (I have one report that
CDMA mod works too )
Select PhoneMode : DIAG (in case of fail try
EMERGENCY, and as last chance use
CS_EMERGENCY)
10. I Recommend do not switch phone off. There
was some people, which done it and after
they were not be able to turn it on again. If
flashing failed, just select some another
mode and try it again, again, try shake/
connect disconnect, again, again....
11. In KDZ file : Choose the ROM file you
downloaded in the first step
12. Press Launch software update
13. If it fails , try again and again and again till you get success !
14. Make sure that all update was done
successfully. Phone should restart itself
automatically
15. Disconnect the USB cable from the phone
16. Press the three button combo for HW reset
of device i.e volume up + home + power
button
U r done !!!
If you get success , add [SOLVED] as prefix to this thread name.
&
Hit Thanks for @The_ERROR (Original source for KDZ links) @GPadmanabh

[Guide] [Testpoint] Unbrick Redmi 5 (rosy)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this thread is for Flashing/Unbricking Redmi 5 with Test Points. This thread will let you know step by step process to the Flashing/Unbricking Redmi 5 with Test Points.
WARNING !!! You're doing all of the above at your responsibility!!! No one here will be responsible if you haven't read the guide completely and then you have damaged your phone beyond repair!!! You have been warned!!!​
Important: - Before flashing, it is advised to take the backup of data and make sure that your phone battery is charged enough.
Note: This method will work with every ROM, Upgrade/Downgrade, Locked BL/Unlocked BL. Don't ask queries before reading the whole guide.
When you can use Test Point for Flashing:
1. If a phone is totally dead, No Fastboot, No recovery.
2. If you are stuck in Qualcomm USB 900e mode.
3. The bootloader is locked and a device is in bootloop.
4. You need to Flash Developer or Stable ROM on Locked BL.
Steps on how to take off the back cover from Redmi 5 are described in this video https://youtu.be/ibkTKQ-SBig
You need a twizzer or Piece of wire to Short/connect the test points to Enter EDL mode.
here is the picture where u have to short
Follow the below steps for effective results.
1.Disconnect the Battery Connector from Main Board. Keep Device Manager Opened on PC and wait for hardware changes when you will short Test Points.
2.First Connect USB cable to Phone only and Place Phone on stable position.(Battery should be disconnected).
3.Short the Test Points with Twizzer or Wire and now Connect USB to PC. When PC detects new hardware, Remove Twizzer/Wire from Test Points.
4.You will get a new device in Device Manager, It can be QHUSB_BULK or Qualcomm HS-USB.
Note: - Driver Signature Enforcement: It's recommended to disable. Reboot your PC in Advanced Mode and Choose Disable Driver Signature.
5.Choose Browse My Computer for Driver Software.
6. Choose the Path of Xiaomi Folder. Most of the users will find it like this.
Note: - If Folder does not exist, Install MI Flash and check C:\XiaoMi\XiaoMiFlash
7.The driver will be installed Successfully and you can see added in Ports as Qualcomm HS-USB.
You are ready to flash any ROM
You will need Fastboot ROM. Recovery ROM will not work. If you have already downloaded Fastboot ROM, there is no need to download again.
(File Extension with.Zip file is Recovery ROM, .tgz or .tar file is Fastboot ROM, if it is .tar after download, Rename to .tgz for easy extraction)
You can download latest Fastboot ROM and MI Flash
Steps to Flash ROM:
1. Download ROM from the above link (Which one you want to Flash) and extract it to Desktop or any location on PC (Use Winrar Software to extract).
(Please check if the file suffix is '.tgz'. Please rename it to '.tgz' if the suffix is '.gz or .tar')
2. Download flashing tool from the above link and install it. Once the installation is complete, Run MiFlash application. Click on browse and Select ROM folder from Desktop(From the location where ROM is saved)
Note: Use latest Mi Flash Tool only, it will work on both 32 and 64 Bit windows.
3. Press Refresh button to see your device in flashing tool.After pressing refresh button you will see a connected device.
Warning: Don't select flash_factory.bat if you are flashing ROM using Fastboot Method, it will wipe IMEI
Note: Clean All, Save User data options will not work in EDL Mode.
4. Click on Flash and it will start flashing ROM on your device
5. Once flashing process completes, you will see Success Message.
6. Remove the cable and Connect the Battery connector to the phone and Re-Assemble Phone in Power off Mode.
7. Power it on by holding Power Button for 10 Seconds.
The device will start, wait until completion, it can take up to 10-20 minutes.
have fun
source: mi.com, youtube

ias it possible to flash only twrp with this method?

astrakid said:
ias it possible to flash only twrp with this method?
Click to expand...
Click to collapse
since u boot into edl with this method which is a usable fastboot ,it shure should work with command: fastboot flash recovery recovery.img

.`

Thanx for great instruction!

can someone provide fastboot rom? xiao mi site is under manteinance and my brand new phone is not booting

moses_dx said:
can someone provide fastboot rom? xiao mi site is under manteinance and my brand new phone is not booting
Click to expand...
Click to collapse
https://androidfilebox.com/download/1842/

how much time I'm supposed to have the test point shorted? I've been trying to do it but the phone just keeps vibrating over and over. BTW my phone does enter into fastboot, just keeps failing to boot

I managed to flash it using another method successfully, but when I put the Sim it just fails and doesn't boot again. I will try again, but maybe my phone it's just broken
Enviado desde mi ONEPLUS A5000 mediante Tapatalk

Is there any difference between testpoint EDL flash & fastboot flash?
Reason for me to ask is that I have been using TP EDL flash on my bootlooping Mi Max 2 using stable global as well as China ROMs but the device could not boot past the Android logo. I cld not use fastboot as my bootloader is locked.
So, for fastboot flash, does it do any extra steps internally vs the TP EDL flash?
Thks

Hello,
I have used the Testpoint EDL flash, it show flash done (success). But when i powered on the phone it still takes me back to MI-Recovery 3.0 mode. Which other methods is available for to use?

Stuck on Recovery
ive got stuck on recovery mode. and i using this method with china stable rom since it was the recommendation for this kind of problem. It showed success on flashing tools but when i try to turn on the phone, it still on recovery mode but the difference just this time, in china language. can anyone help me with this problem

Hi, I have a Redmi 5 Plus and it was stuck in bootloop and its bootloder is locked, I tried all of the steps above but it displays an error:
:resdump:<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 131072, num 172032" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Read back verify failed at sector -807616340,num sectors 131072" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 131072" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
This was taken from the log, due to this error, the flashing process was unsuccessful. I used MIFlash Tool 2020.3.14.0, and a China ROM because the phone originally has China ROM. The phone underwent EDL Mode and was flashed with fastboot ROM, but to no avail. There's no problem in its driver (Qualcomm HS-USB QDLoader 9008 (COM3) when it was connected to the laptop because it was detected by the computer.
Attached here is the log, and the screenshot of the log of the flashing process. I hope you can help me this issue

bhoux said:
Hi, I have a Redmi 5 Plus and it was stuck in bootloop and its bootloder is locked, I tried all of the steps above but it displays an error:
:resdump:<?xml version="1.0" encoding="UTF-8" ?><data><log value="start 131072, num 172032" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Read back verify failed at sector -807616340,num sectors 131072" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 131072" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
This was taken from the log, due to this error, the flashing process was unsuccessful. I used MIFlash Tool 2020.3.14.0, and a China ROM because the phone originally has China ROM. The phone underwent EDL Mode and was flashed with fastboot ROM, but to no avail. There's no problem in its driver (Qualcomm HS-USB QDLoader 9008 (COM3) when it was connected to the laptop because it was detected by the computer.
Attached here is the log, and the screenshot of the log of the flashing process. I hope you can help me this issue
Click to expand...
Click to collapse
Verify problem

Cicada_3301 said:
Verify problem
Click to expand...
Click to collapse
verify what?

bhoux said:
verify what?
Click to expand...
Click to collapse
Rollback checker, try some of those modded miflash

Cicada_3301 said:
Rollback checker, try some of those modded miflash
Click to expand...
Click to collapse
Can you further elaborate pleases?

So essentially, xiaomi will check your device firmware info to prevent you from downgrading without permission, so one way to get around this is actually modding the loader file and the flash program to bypass this check

Cicada_3301 said:
So essentially, xiaomi will check your device firmware info to prevent you from downgrading without permission, so one way to get around this is actually modding the loader file and the flash program to bypass this check
Click to expand...
Click to collapse
How can I perform the process of: "modding the loader file and the flash program to bypass this check?"
What I am doing is through MI Flash, I am flashing the firmware I got from the Internet

bhoux said:
How can I perform the process of: "modding the loader file and the flash program to bypass this check?"
What I am doing is through MI Flash, I am flashing the firmware I got from the Internet
Click to expand...
Click to collapse
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz

[GUIDE] [F1f/w] Unlock fastboot mode via QFIL for F1f/w

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:

[GUIDE][03 OCT][10or.E][Bootloader Unlocking Without IMEI Loss]

Before you start reading note that no spoon-feeding is done here and its a bit tricky if you are flashing Stock ROMs for the first time.
REQUIREMENTS:
-PC/laptop
-ADB-Fastboot / Qualcomm Drivers must be installed
-QFST tool / QFIL tool anyone required (QSFT RECOMMENDED)
-notepad ++
-Platform Tools
-Stock Nougat v82/v99 Firmware File
-And A working Brain
Process:
First, install all the drivers and Flashing Tool then Extract the V82/V99 rom.
Then go where you have extracted the rom then go to the firmware folder there find (rawprogram_unsparse/rawprogram0) anyone and open that file with notepad ++ NOW HERE COMES THE DIFFICULT PART you need to delete some lines from that file so that it doesn't create any NULL IMEI issue when flashing the rom.
**NOTE YOU NEED TO CHANGE THE (rawprogram_unsparse/rawprogram0) FILE. BELOW LINES MUST BE CHANGE FROM BOTH FIRMWARE V82 as well as from V99 firmware. or else it will give null IMEI error.
After opening the file in notpad ++ find this lines:
filename="st1" label="modemst1" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0xd682400" start_sector="439314" />
filename="st2" label="modemst2" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0xd802400" start_sector="442386" />
[FROM THIS TWO LINE YOU NEED TO REMOVE THE "st1" and "st2" ] THEN
filename="fs_image.tar.gz.mbn.img" label="fsg" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0x10008000" start_sector="524352" />
[FROM HERE YOU NEED TO REMOVE "fs_image.tar.gz.mbn.img" ] THEN
filename="persist_1.img" label="persist" num_partition_sectors="9608" physical_partition_number="0" start_sector="10485760" />
[FROM HERE REMOVE "persist_1.img" ] THEN SAVE THE FILE
**NOTE- REMEMBER IN WHICH FILE YOU MAKE THE CHANGES.
(either rawprogram_unsparse or rawprogram0).
**NOTE**
Make sure USB debugging is turned on from developer option,
Now boot your device is in EDL Mode.
To Boot in EDL Mode just Power OFF your device and then press (volume up + volume down button simultaneously) when 10or. logo popup just connects the data cable... and your notification LED will start blinking...
**MAIN PROCESS**
**FIRST NEED TO FLASH V82 FACTORY FIRMWARE FOR UNLOCKING BOOT LOADER.
Now open QPST Tool/ QFIL Tool, anyone you prefer then select Flat Build then in programmer path, go to browse and from the V82 firmware folder select "prog_emmc_firehose_8937_ddr.mbn" file Then click on load XML And select the .xml File in which you have made the changes (otherwise if you select the wrong .xml file the IMEI will be NULL) After selecting the .xml file another window will be popup just select the [patch0] and then it's done...
Now you can flash your 10or. Device By just Clicking on the Download Button.
Let the flashing process to be finished...
After the flashing complete boot your phone it will show a start option just start it by power key, then your phone will boot into test mode then just click on Reboot --> Reboot To Android --> Ok, then again click on start by the power button, after the phone boots again enable the USB debugging option and power off your device.
Now we need to boot our phone into fastboot mode for that (press power button + volume down simultaneously) and then click on start again by the power button. then some options will be shown just select fastboot mode by the volume rockers and the power button.
As now your device is booted into fastboot mode just connect the USB cable and you can now unlock the bootloader by typing this commands
OPEN FASTBOOT/PLATFORM TOOLS and use this following commands
fastboot devices
(it will show if your device is connected or not)
then type fastboot oem unlock
then there will be a popup on the phone just select "yes" by the volume rockers and power button.
After the phone reboot, your phone bootloader will be unlocked Now you need to flash the V99 rom for that just power off your phone and boot it again to EDL mode and flash the V99 rom by the using same process use to flash the V82 ROM.

[GUIDE][04oct][10or.E][Bootloader Unlocking]And Installing [Custom Recovery]

Before you start reading note that no spoon-feeding is done here and its a bit tricky if you are flashing Stock ROMs for the first time.
REQUIREMENTS:
-PC/laptop
-ADB-Fastboot Drivers / Qualcomm Drivers must be installed
-QFST tool / QFIL tool anyone required (QSFT RECOMMENDED)
-notepad ++
-Platform Tools
-Stock Nougat v82/v99 Firmware File
-AIO Tool for 10or.E Download AIo Tool Kit
-And A working Brain
Process:
First, install all the drivers and Flashing Tool then Extract the V82/V99 rom.
Then go where you have extracted the rom then go to the firmware folder there find (rawprogram_unsparse/rawprogram0) anyone and open that file with notepad ++ NOW HERE COMES THE DIFFICULT PART you need to delete some lines from that file so that it doesn't create any NULL IMEI issue when flashing the rom.
**NOTE YOU NEED TO CHANGE THE (rawprogram_unsparse/rawprogram0) FILE. BELOW LINES MUST BE CHANGE FROM BOTH FIRMWARE V82 as well as from V99 firmware. or else it will give null IMEI error.
After opening the file in notpad ++ find this lines:
filename="st1" label="modemst1" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0xd682400" start_sector="439314" />
filename="st2" label="modemst2" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0xd802400" start_sector="442386" />
[FROM THIS TWO LINE YOU NEED TO REMOVE THE "st1" and "st2" ] THEN
filename="fs_image.tar.gz.mbn.img" label="fsg" num_partition_sectors="3072" physical_partition_number="0" size_in_KB="1536.0" sparse="false" start_byte_hex="0x10008000" start_sector="524352" />
[FROM HERE YOU NEED TO REMOVE "fs_image.tar.gz.mbn.img" ] THEN
filename="persist_1.img" label="persist" num_partition_sectors="9608" physical_partition_number="0" start_sector="10485760" />
[FROM HERE REMOVE "persist_1.img" ] THEN SAVE THE FILE
**NOTE- REMEMBER IN WHICH FILE YOU MAKE THE CHANGES.
(either rawprogram_unsparse or rawprogram0).
**NOTE**
Make sure USB debugging is turned on from developer option,
Now boot your device is in EDL Mode.
To Boot in EDL Mode just Power OFF your device and then press (volume up + volume down button simultaneously) when 10or. logo popup just connects the data cable... and your notification LED will start blinking...
**MAIN PROCESS**
**FIRST NEED TO FLASH V82 FACTORY FIRMWARE FOR UNLOCKING BOOT LOADER.
Now open QPST Tool/ QFIL Tool, anyone you prefer then select Flat Build then in programmer path, go to browse and from the V82 firmware folder select "prog_emmc_firehose_8937_ddr.mbn" file Then click on load XML And select the .xml File in which you have made the changes (otherwise if you select the wrong .xml file the IMEI will be NULL) After selecting the .xml file another window will be popup just select the [patch0] and then it's done...
Now you can flash your 10or. Device By just Clicking on the Download Button.
Let the flashing process to be finished...
After the flashing complete boot your phone it will show a start option just start it by power key, then your phone will boot into test mode then just click on Reboot --> Reboot To Android --> Ok, then again click on start by the power button, after the phone boots again enable the USB debugging option and power off your device.
Now we need to boot our phone into fastboot mode for that (press power button + volume down simultaneously) and then click on start again by the power button. then some options will be shown just select fastboot mode by the volume rockers and the power button.
As now your device is booted into fastboot mode just connect the USB cable and you can now unlock the bootloader by typing this commands
OPEN FASTBOOT/PLATFORM TOOLS and use this following commands
fastboot devices
(it will show if your device is connected or not)
then type fastboot oem unlock
then there will be a popup on the phone just select "yes" by the volume rockers and power button.
After the phone reboot, your phone bootloader will be unlocked Now you need to flash the V99 rom for that just power off your phone and boot it again to EDL mode and flash the V99 rom by the using same process use to flash the V82 ROM.
**Recovery Installation**
Now you have unlocked the bootloader and installed the V99 ROM now the final process came to install any custom recovery you want for that just extract the AIO Tool kit (password for extract: vishalsmagic) just open the file and go to the TWRP kit section then from flash section select the one you preferred to flash then just Double click on "VISHALSMAGIC" and enter password (vishalsmagic) then just type the com port no. and hit Enter to flash.But before flashing make sure your device is in EDL mode.
After the flashing complete just press the (power button and volume up) to boot into twrp..
And boooom you have installed custom recovery on your 10or.E
If you want you can install "no verity opt encrypt'' zip(optional) and "Magisk" for Root (optional).

can you explain why we are again flashing V 1_0_99 stock rom.
could we have not unlocked bootloader by flashing V 1_0_82 only.

Please, update link for AIO Toolkit.