i Have Lenovo S60-a when i upgrade it to 5.0 then it cause some problem
it load nothing i tried all combinition of button then i tried it through test point and it work it load Qualcomm HS-USB QDLoader 9008 and connected to my pc now when i try to flash it through QFil it give me error
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
And some time it give
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
so i have a LG K20 (mp260) from MetroPCS, and like a fool, i flashed a rom that wasnt compatible...
its now hard bricked. my computer can only recognize it now as "Qualcomm HS-USB QDLoader 9008 (COM3)" in the "Ports" section of the device manager. the device itself cant turn on for nothing, there are no lights, no vibrations. but my computer can read it...
i have minimal knowledge on this stuff and ive been at this for almost a week now and how found nothing but the QFIL program that looked promising. ive installed all the appropriate drivers and give it the appropriate files (i hope):
Programmer: prog_emmc_firehose_8936.mbn
XML: rawprogram0.xml with the patch: patch0.xml
the files were manually extracted from my own phones stock .KDZ
i have seen others use rawprogram files such as "rawprogram_unsparse_without_qcn", and "rawprogram_unsparse". i dont know how to obtain these files and if they would help my problem.
(note: im using QFIL 2.0.1.7 and ive tried numerous previous versions:crying
apon pressing the "download" button, it says:
2018-08-01 21:26:02.821 Start Download
2018-08-01 21:26:02.843 Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\8675_W00\prog_emmc_firehose_8936.mbn
2018-08-01 21:26:02.860 ***** Working Folder:C:\Users\IZACOR\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2018-08-01 21:27:43.158 Binary build date: Nov 21 2017 @ 02:53:37
2018-08-01 21:27:43.160 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\IZACOR\AppData\Roaming\Qualcomm\QFIL\COMPORT_3
2018-08-01 21:27:43.164 Sahara mappings:
2018-08-01 21:27:43.165 2: amss.mbn
2018-08-01 21:27:43.166 6: apps.mbn
2018-08-01 21:27:43.167 8: dsp1.mbn
2018-08-01 21:27:43.168 10: dbl.mbn
2018-08-01 21:27:43.173 11: osbl.mbn
2018-08-01 21:27:43.174 12: dsp2.mbn
2018-08-01 21:27:43.175 16: efs1.mbn
2018-08-01 21:27:43.176 17: efs2.mbn
2018-08-01 21:27:43.178 20: efs3.mbn
2018-08-01 21:27:43.179 21: sbl1.mbn
2018-08-01 21:27:43.180 22: sbl2.mbn
2018-08-01 21:27:43.181 23: rpm.mbn
2018-08-01 21:27:43.182 25: tz.mbn
2018-08-01 21:27:43.183 28: dsp3.mbn
2018-08-01 21:27:43.184 29: acdb.mbn
2018-08-01 21:27:43.186 30: wdt.mbn
2018-08-01 21:27:43.188 31: mba.mbn
2018-08-01 21:27:43.190 13: C:\Program Files (x86)\Qualcomm\QPST\bin\8675_W00\prog_emmc_firehose_8936.mbn
2018-08-01 21:27:43.192
2018-08-01 21:27:43.194 21:27:43: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
2018-08-01 21:27:43.196
2018-08-01 21:27:43.197 21:27:43: ERROR: function: sahara_main:924 Sahara protocol error
2018-08-01 21:27:43.198
2018-08-01 21:27:43.199 21:27:43: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2018-08-01 21:27:43.201
2018-08-01 21:27:43.202
2018-08-01 21:27:43.203 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2018-08-01 21:27:43.205 Finish Download
im getting tired of seeing this log lol. but as you can see the problem (from i can see) is that its getting stuck at the "Sahara" bit. i cant seem to fix this to save my life. and ive littrally tried everything!
yes including putting the firmware files into the "bin" folder of the program and stuff like that...
fastbooting wont work either as the screen is always black and the computer never sees it as a device, but a port.
i turned to creating this post as a last resort, for if i cant find an answer here, im afraid ill just have to use the phone for parts or something:crying:. please! if anyone has suggestion or a solution that i haven't tried yet it would be truly appreciated!
Hi , try this from my post
1. Disable or remove your Antivirus (because sometimes virus can block instaling drivers , ports or running flash tool)
2. Uninstall all the previous drivers you used for flashing or unbrick use free tool called USBDeview
for 32 bit users:
https://www.nirsoft.net/utils/usbdeview.zip
for 64 bit users:
https://www.nirsoft.net/utils/usbdeview-x64.zip
3. Put your windows in Test mode
To put your Windows in test mode just Run As Administrator Command Prompt and insert one of the following command:
bcdedit -set testsigning on ( to enable test mode)
http://s000.tinyupload.com/index.php...66266232947643
bcdedit -set testsigning off ( to disable test mode)
http://s000.tinyupload.com/index.php...26094979151761
Or Disable driver signature
for Windows 7
https://www.youtube.com/watch?v=6gYhHD622AA
for Windows 10 users:
https://www.youtube.com/watch?v=71YAIw7_-kg
After that reboot your PC .
4. Uninstall all flash program from your pc like MiFlash , QPST , Qloader ...
Use Revo Uninstaller for advanced uninstaling that clean leftover files and registry which is stored inside your Windows registry.
https://www.revouninstaller.com/revo..._download.html
After that reboot your PC .
5. Install Microsoft .NET Framework 4 download from here: (if you already have instaled skip this)
https://www.microsoft.com/en-us/down....aspx?id=17851
6. Install Minimal ADB & Fastboot 1.4.2 command tool download from here
(while you start installing tool check to be in desktop is easy )
https://androidfilehost.com/?fid=745425885120698566
in order to install run ADB & Fastboot 1.4.2.exe with Administrator and just write y and hit enter for all .
Now follow this tutorial for unbrick your device : ) .
It must to work
http://lgk20.com/lg-k20-plus-mp260-stock-rom-download-firmware-update-tutorial/
Don't forget to run flash tool with Administrator.
Good Luck and Never give UP
Thank you for these tips! but unfortunately, i cant follow the tutorial because im unable to access download mode or any mode for that matter. my screen is black and isnt recognized by the computer as a normal LG phone anymore...
im trying to find a solution that does not involve download mode, fastboot, or anything involving the phone displaying anything if that makes sense...
You should try to let your battery to dry out and then hold Vol - button and plug usb ,just keep holding for few minutes to see if your pc is detecting your device if not try to replace the battery if that also doesn't help then probably your emmc chip is dead or something other.
Teddy Lo said:
You should try to let your battery to dry out and then hold Vol - button and plug usb ,just keep holding for few minutes to see if your pc is detecting your device if not try to replace the battery if that also doesn't help then probably your emmc chip is dead or something other.
Click to expand...
Click to collapse
i truly appreciate your helpfulness, but my main focus is trying to fix the Sahara error i keep receiving, and/or if im doing something wrong thats causing it.
Izaiah Coronado said:
i truly appreciate your helpfulness, but my main focus is trying to fix the Sahara error i keep receiving, and/or if im doing something wrong thats causing it.
Click to expand...
Click to collapse
Is your PC detecting your device at all ? and like which one ? can you post some photos ?
Also what you can try is to extract that stock firmware on another location like D:/ Firmware/(your extracted firmware) , run Qfil with Administrator , load extracted firmware from D:/Firmware/ in Qfil and make sure that you have 9008 open port .
Teddy Lo said:
Is your PC detecting your device at all ? and like which one ? can you post some photos ?
Also what you can try is to extract that stock firmware on another location like D:/ Firmware/(your extracted firmware) , run Qfil with Administrator , load extracted firmware from D:/Firmware/ in Qfil and make sure that you have 9008 open port .
Click to expand...
Click to collapse
{
"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"
}
its seen only as Qualcomm HS-USB QDLoader 9008 (under ports)and nothing else. i apologize but i cant seem to put up my picture...
i also just tried your suggestion and it didn't work sadly. im having horrible luck with these things lol.
When your PC is detecting your device as Qualcomm HS-USB QDLoader 9008 is good news : ) , it looks like path from firmware which you inserted inside Qfil tool are wrong or firmware at all .
Try again if you are able to put your device in fastboot mode:
Open Minimal ADB & Fastboot , in my case C:\Program Files (x86)\Minimal ADB and Fastboot right click on cmd-here.exe and Run as Administrator .
1. Now take out the battery , and insert again .
2. Next hold just vol - and plug usb cable don't release yet wait few seconds and see if your device is detected like that then release Vol - .
3. Write inside adb & fastboot terminal :
- fastboot device and press Enter
(see if is show up like some numbers or what )
if not try
- adb devices and press Enter
(if your device is available there just write adb reboot bootloader
-write again fastboot devices , and if everything is fine you should see your device
now from stock firmware extract recovery.img , also if you have single system.img , boot.img extract that also to in my case C:\Program Files (x86)\Minimal ADB and Fastboot and write for each one:
fastboot erase cache and press Enter
fastboot erase system and press Enter
fastboot flash recovery recovery.img and press enter
fastboot flash boot boot.img and press enter
fastboot flash system system.img and press enter
If that doesn't help you , try to flash this firmware with LG UP
Example how to flash :
https://www.youtube.com/watch?v=NIHTx6a_kDI
Stock firmware:
https://mega.nz/#!ymZQHI5S!F3x1I0qM_iXNEg9WnqLINkRATUvlBWigmnzfMD5pUZI
If doesn't help you is better to replace new motherboard and save your time .
so i was poking around and found out that the Firehose file i needed is like super specific to the device im using it on (a signed Firehose_emmc). so finding that ever so specific Firehose file could very much possibly be the fix. (i just dont know how to find and obtain it)
im also looking into the new motherboard because...you know...
would it matter the carrier? like if my phone is metroPCS and the new mother board is T-mobile?
Same Issue here.
Validating Application Configuration
Load APP Configuration
COM:5
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0
RAWPROGRAM:
rawprogram0.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:eMMC
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:False
MAXDIGESTTABLESIZE:8192
SWITCHTOFIREHOSETIMEOUT:30
RESETTIMEOUT:200
RESETDELAYTIME:2
FLATBUILDPATH:C:\
FLATBUILDFORCEOVERRIDE:True
QCNPATH:C:\Temp\00000000.qcn
QCNAUTOBACKUPRESTORE:False
SPCCODE:000000
ENABLEMULTISIM:False
AUTOPRESERVEPARTITIONS:False
PARTITIONPRESERVEMODE:0
PRESERVEDPARTITIONS:0
PRESERVEDPARTITIONS:
ERASEALL:False
Load ARG Configuration
Validating Download Configuration
Image Search Path: D:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0
RAWPROGRAM file path: D:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\rawprogram0.xml
PATCH file path:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\patch0.xml
Programmer Path:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
Process Index:0
Start Download
Program Path:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
***** Working Folder:C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
Binary build date: Oct 31 2016 @ 22:51:05
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Administrator\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
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: D:\@SOFTWARES\19. Android&IOS\Firmware\COOLPAD 6\VCR-A0\prog_emmc_firehose_8976_ddr.mbn
22:17:50: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
22:17:50: ERROR: function: sahara_main:924 Sahara protocol error
22:17:50: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
I have a problem
I,ve tried QFIL QPST and recieved
/*invalid image type recieved*/
is_ack_succesfull : 1031 SAHARA_NAK_INVALID_IMAGE_TYPE
sahara protocol error
uploading image using sahara protocol failed
Before that
My emmc card was already formatted to fat32
same issue here
having this same issue tried older version, short paths and lots of retries
BQ Aquarius X5 Plus Sahara Fail
Hi! I have this Fail on QFIL whith BQ Aquarius X5 Plus
I see my phone on Device Manager like: Qualcomm HS-USB QDOWNLOADER 9008 (COM3)
Pls someone...
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Fellow FOOL am I
I also have a K20... and a Stylo 4 with the same problem... (me) Flashed different variant of firmware (KDZ) and get QUALCOMM HS-USB QDLoader 9008
following this thread
For those still having ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
Please use older Qfil version, I flash successfully with version 2.0.0.0 after latest version giving above error..
handasan10 said:
For those still having ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
Please use older Qfil version, I flash successfully with version 2.0.0.0 after latest version giving above error..
Click to expand...
Click to collapse
Tried that thing but no success.
Possible problem with Qfil and network
JoshuaX12 said:
Tried that thing but no success.
Click to expand...
Click to collapse
Depending on how the Qualacom (sp) driver was installed, if you remember, it asked about a network connection type.
I found this problem while searching TONS of possible solutions, and it might work for you as I was getting the same errors with QFIL.
DISCONNECT FROM YOUR NETWORK. That means ALL interfaces, like wired ethernet, and wireless. ALL OF THEM.
Then try running the flash with QFIL.
I have an Essential PH-1 and tried this but of course got the Sahara Fail.
See log here:
2019-05-22 22:51:24.743 Validating Application Configuration
2019-05-22 22:51:24.752 Load APP Configuration
2019-05-22 22:51:24.773 COM:5
2019-05-22 22:51:24.773 PBLDOWNLOADPROTOCOL:0
2019-05-22 22:51:24.773 PROGRAMMER:True
2019-05-22 22:51:24.773 PROGRAMMER:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:51:24.773 RESETSAHARASTATEMACHINE:False
2019-05-22 22:51:24.773 SAHARAREADSERIALNO:False
2019-05-22 22:51:24.773 SEARCHPATH:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00
2019-05-22 22:51:24.773 RAWPROGRAM:
2019-05-22 22:51:24.773 rawprogram0.xml
2019-05-22 22:51:24.773 PATCH:
2019-05-22 22:51:24.773 patch0.xml
2019-05-22 22:51:24.773 ACKRAWDATAEVERYNUMPACKETS:False
2019-05-22 22:51:24.773 ACKRAWDATAEVERYNUMPACKETS:100
2019-05-22 22:51:24.773 MAXPAYLOADSIZETOTARGETINBYTES:False
2019-05-22 22:51:24.773 MAXPAYLOADSIZETOTARGETINBYTES:49152
2019-05-22 22:51:24.773 DEVICETYPE:emmc
2019-05-22 22:51:24.773 PLATFORM:8x26
2019-05-22 22:51:24.773 VALIDATIONMODE:0
2019-05-22 22:51:24.773 RESETAFTERDOWNLOAD:False
2019-05-22 22:51:24.773 MAXDIGESTTABLESIZE:8192
2019-05-22 22:51:24.773 SWITCHTOFIREHOSETIMEOUT:30
2019-05-22 22:51:24.773 RESETTIMEOUT:200
2019-05-22 22:51:24.773 RESETDELAYTIME:2
2019-05-22 22:51:24.773 METABUILD:
2019-05-22 22:51:24.773 METABUILD:
2019-05-22 22:51:24.773 FLATBUILDPATH:C:\
2019-05-22 22:51:24.773 FLATBUILDFORCEOVERRIDE:True
2019-05-22 22:51:24.773 QCNPATH:C:\Temp\00000000.qcn
2019-05-22 22:51:24.773 QCNAUTOBACKUPRESTORE:False
2019-05-22 22:51:24.773 SPCCODE:000000
2019-05-22 22:51:24.773 ENABLEMULTISIM:False
2019-05-22 22:51:24.773 AUTOPRESERVEPARTITIONS:False
2019-05-22 22:51:24.773 PARTITIONPRESERVEMODE:0
2019-05-22 22:51:24.773 PRESERVEDPARTITIONS:0
2019-05-22 22:51:24.773 PRESERVEDPARTITIONS:
2019-05-22 22:51:24.773 ERASEALL:False
2019-05-22 22:51:24.774 Load ARG Configuration
2019-05-22 22:51:24.810 Validating Download Configuration
2019-05-22 22:51:24.811 Image Search Path: E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00
2019-05-22 22:51:24.819 RAWPROGRAM file path: E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\rawprogram0.xml
2019-05-22 22:51:24.820 PATCH file path:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\patch0.xml
2019-05-22 22:51:24.820 Programmer Path:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:51:25.172 Process Index:0
2019-05-22 22:51:25.189 Qualcomm Flash Image Loader (QFIL) 2.0.1.9
2019-05-22 22:51:35.483 Start Download
2019-05-22 22:51:35.494 Program Path:E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:51:35.502 ***** Working Folder:C:\Users\Grant\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
2019-05-22 22:53:05.646 Binary build date: Nov 21 2017 @ 02:53:37
2019-05-22 22:53:05.647 QSAHARASERVER CALLED LIKE THIS: 'E:\Users\Grant\Downloads\PH1 Qualcomm\Qualcomm_Flash_Image_Loader_v2.0.1.9\QSaharaServer.ex'Current working dir: C:\Users\Grant\AppData\Roaming\Qualcomm\QFIL\COMPORT_5
2019-05-22 22:53:05.653 Sahara mappings:
2019-05-22 22:53:05.653 2: amss.mbn
2019-05-22 22:53:05.654 6: apps.mbn
2019-05-22 22:53:05.654 8: dsp1.mbn
2019-05-22 22:53:05.655 10: dbl.mbn
2019-05-22 22:53:05.655 11: osbl.mbn
2019-05-22 22:53:05.656 12: dsp2.mbn
2019-05-22 22:53:05.656 16: efs1.mbn
2019-05-22 22:53:05.657 17: efs2.mbn
2019-05-22 22:53:05.657 20: efs3.mbn
2019-05-22 22:53:05.658 21: sbl1.mbn
2019-05-22 22:53:05.658 22: sbl2.mbn
2019-05-22 22:53:05.659 23: rpm.mbn
2019-05-22 22:53:05.659 25: tz.mbn
2019-05-22 22:53:05.660 28: dsp3.mbn
2019-05-22 22:53:05.660 29: acdb.mbn
2019-05-22 22:53:05.661 30: wdt.mbn
2019-05-22 22:53:05.661 31: mba.mbn
2019-05-22 22:53:05.662 13: E:\Users\Grant\Downloads\PH1 Qualcomm\8675_W00\8675_W00\prog_emmc_firehose_8936.mbn
2019-05-22 22:53:05.662
2019-05-22 22:53:05.663 22:53:05: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
2019-05-22 22:53:05.663
2019-05-22 22:53:05.664 22:53:05: ERROR: function: sahara_main:924 Sahara protocol error
2019-05-22 22:53:05.664
2019-05-22 22:53:05.665 22:53:05: ERROR: function: main:303 Uploading Image using Sahara protocol failed
2019-05-22 22:53:05.665
2019-05-22 22:53:05.666
2019-05-22 22:53:05.667 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2019-05-22 22:53:05.668 Finish Download
hi guys, sorry if this post or my comment is out of date, been awhile for too long
simple solution for Sahara Fail is just as simple as rename your image folder with alphanumeric characters without space and put it in your root directory (e.g. D drive) because Sahara can't recognize your folder if it use space in it's name
bapakerwe said:
hi guys, sorry if this post or my comment is out of date, been awhile for too long
simple solution for Sahara Fail is just as simple as rename your image folder with alphanumeric characters without space and put it in your root directory (e.g. D drive) because Sahara can't recognize your folder if it use space in it's name
Click to expand...
Click to collapse
How to do that?
Hi everyone!
Just wanted to share some steps in case you brick your Realme.
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGES
Some prerequisites you will need:
mtkclient + python
spft (sp flash tool)
ofp extractor
Your stock rom in OFP format.
Step 1. Download all of the things mentioned above.
Step 1a. Make sure your device is turned off. DO NOT PLUG IT IN.
Step 2. Install mtkclient using the guide on GitHub.
Step 3. Run
Bash:
$ py mtk payload
in your terminal.
Step 3a. When it says ***waiting for device*** hold both volume buttons and plug in your device.
This will enter BROM mode.
Step 4. Extract and open ofp extractor and extract your ofp.
Step 5. Open SPFT and click DOWNLOAD ONLY (do not I MEAN DO NOT PRESS FORMAT ALL.)
Step 6. In scatter, look for your scatter file. It should be (MTxxxxScatter.txt etc) Then select it.
Step 7. Select your auth file if you have one.
Step 8. Press Download and if the progress bar starts going the flash is going. DO NOT UNPLUG.
Step 9. Reboot after it says 'Download Ok'
Step 10. Enjoy your unbricked device!
NOTE In most cases the rom will be for android 10. Update if required through OZIP.
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MTK Tool
czaroslaw said:
I cannot download with SPFlash. Error 0xC0060001. I'm sure that I have done all steps correctly including this tutorial:
Realme 7 Unbrick
Of corse I'm doing everything with Realme 7 5G RMX2111EU.
I had problems with disabling protection as follows but I think it finally succeeded.
1. bypass_utility-v.1.4.2 gives error
Code:
[2022-05-10 22:53:51.684562] Waiting for device
[2022-05-10 22:53:59.780976] Found port = COM4
[2022-05-10 22:53:59.921376] Device hw code: 0x996
[2022-05-10 22:53:59.921376] Device hw sub code: 0x8a00
[2022-05-10 22:53:59.921376] Device hw version: 0xca00
[2022-05-10 22:53:59.921376] Device sw version: 0x0
[2022-05-10 22:53:59.921376] Device secure boot: True
[2022-05-10 22:53:59.921376] Device serial link authorization: False
[2022-05-10 22:53:59.921376] Device download agent authorization: True
[2022-05-10 22:53:59.921376] Disabling watchdog timer
[2022-05-10 22:53:59.936976] Disabling protection
[Errno None] b'libusb0-dll:err [control_msg] sending control message failed, win
error: A device attached to the system is not functioning.\r\n\n'
[2022-05-10 22:54:01.028978] Payload did not reply
Press any key to continue . . .
2. mtk-client gives error:
Code:
....Preloader
Preloader - [LIB]: ←[31mStatus: Handshake failed, retrying...←[0m
Preloader
3. MTK Meta Utility v37 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
DriverName : MediaTek USB Port_V1633
DriverPath : usb\vid_0e8d&pid_0003\5&278a3c80&0&2
DriverID : wdm_usb
DriverVersion : 3.0.1504.0
DriverDate : 1-22-2015
InfPath : oem28.inf
ProviderName : MediaTek Inc.
Connecting to BootROM......
● Chipset MT6853
● Identifier Dimensity 720/800U 5G
● Info 8A00_CA00_0000_Mouton
● MEID:3EFFEA531AB22A57AB0240D8421E92B4
● SecCFG SBC+SDA
Disable BRom protection...
MTK Auth Disable(SLA/DAA) success!
now you can use SP Flash Tool or any MTK Tool
4. MTK Auth Byoass Tool v6.0.0.1 success
Code:
Waiting for mtk usb device... ok
BootMode : BootRom[COM4]
Sync with bootrom started...
● Chipset MT6853:Dimensity 720/800U 5G
● Code Mouton
● Hw Sub 8A00
● HW Ver CA00
● SW Ver 0000
● SecCFG SBC+SDA
Disable brom protection.
Bypass Payload ACK = 0xa1a2a3a4
MTK Secure Boot Bypasss success!
now you can use SP Flash Tool or any MYKI Tool
Click to expand...
Click to collapse
What more.info about the error code do you have? Also are you on windows because spft buggy on linux
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
czaroslaw said:
BROM ERROR : STATUS_BROM_CMD_STARTCMD_FAIL (0xC0060001)
Windows 7
SP_Flash_Tool_v5.2208_Win
Click to expand...
Click to collapse
Then you haven't bypassed brom, try mtkclient again and don't unplug your device
Mtk client gives error: Preloader - [LIB]: ←[31mStatus: Handshake failed
Install mtk drivers and Libusb, also pyserial
All above mentioned was installed. I tried different pack from droidwin and I get this:
Code:
Port - Device detected :)
Preloader - CPU: MT6853(Dimensity 720 5G)
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - CQ_DMA addr: 0x10212000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x996
Preloader - Target config: 0xe5
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: True
Preloader - SWJTAG enabled: True
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xca00
Preloader - SW Ver: 0x0
Preloader - ME_ID: 3EFFEA531AB22A57AB0240D8421E92B4
Preloader - SOC_ID: DAA82CB9D5E03916132A0BE2A479C0CC0FFD2B10
1E00173F9EA9FCB44C88FC8E
PLTools - Loading payload from mt6853_payload.bin, 0x264 bytes
PLTools - Kamakiri / DA Run
Kamakiri - Trying kamakiri2..
Kamakiri - Done sending payload...
PLTools - Successfully sent payload: D:\Apk\MTK Bypass Tools\mtkclient-main\mtkc
lient\payloads\mt6853_payload.bin
Be sure to use in SPFT, in connection check USB full speed, and in general settings, uncheck the options Check LIB DA Match and Storage Life Cycle Check.
If this doesn't work, try to flash only preloader firstly, and then flash the rest, upload some screenshot if the error persists.
That means it worked
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
do
Code:
fastboot flash --disable-verity --disable-verification vbmeta {your vbmeta.img}
czaroslaw said:
Ok. Bootloader is unlocked but now I have dm-verity corrupted.
I cannot enter recovery mode. Some error flashes on screen and immediately reboot. I cannot even read this. I have found that it might be:
the serial is not matched
fastboot_unlock_verify failed
I cannot enter fastboot mode. It gives:
Orange state
The device is unlocked and cannot be trusted
and then restarts
Normal boot gives:
dm_varity corruption
Your device is corrupted
It won't be trusted and may not work properly
Press power button to continue
Then pressing power button boots into system correctly and the phone is working.
How to get rid of these errors? How to recover access to recovery and fastboot mode? Should I flash some partitions again from stock formware?
Should I install PBRP using mtkclient as in this guide?
Install TWRP Recovery without using Fastboot Mode [MediaTek]
And then should I root it using patched Magisk as follows?
Root MediaTek Devices without using Fastboot Mode [via MTK Client]
There is some info about patched version of Magisk for MTK devices. Should I use it?
Click to expand...
Click to collapse
If it says DM-verity error, reflash with spft and on mtkclient, relock BL by using
Code:
Py mtk da seccfg lock
I cannot enter fastboot mode so I cannot use fastboot flash.
Second advice: I do not want to lock bootloader.
If you are able to boot to stock, do ADB reboot fastboot
Does not work. It gives the same as VolUP+PWR. Orange state message and reboot.
I cannot enter fastboot in any way.
Should I flash something in brom mode? Recovery partition? Something else to get rid of dm_varity?
Reflash firmware then try, idk this hasn't happened to me
Also send the link of the firmware U got
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
czaroslaw said:
I have RMX2111_11_C.11. Updated via OTA. I cannot find such version firmware file.
The newest I found is:
RMX2111GDPR_11_C.09 EDL mode
Click to expand...
Click to collapse
Relock bootloader and try using this to reunlock bl