[Q] Electrify on ubuntu, sbf_flash - Motorola Photon 4G

I reached this screen and rebooted to the bootloader and it doesnt seem to be doing anything just wondering what I'm supposed to do now
[email protected]:/home/brendon/Downloads# ./sbf_flash derpunlock.sbf
SBF FLASH 1.24 (mbm)
=== derpunlock.sbf ===
00: RDL03 0x00000000-0x002FFFFF AFD0 AP
01: RDL01 0x00800000-0x008407FF 1C15 BP
02: CG02 0x00000010-0x0000580F D439 AP
03: CG03 0x000000A0-0x0008009F A51D AP
04: CG39 0x00000020-0x0030001F 4C9F AP
05: CG42 0x00000050-0x0030004F 13F2 AP
06: CG47 0x00000070-0x0008006F C8A2 AP
!! Reboot phone into bootloader.

well I figured out to go to RSD from the boot screen and now I got this message
Code:
[email protected]:/home/brendon/Downloads# ./sbf_flash derpunlock.sbf
SBF FLASH 1.24 (mbm)
=== derpunlock.sbf ===
00: RDL03 0x00000000-0x002FFFFF AFD0 AP
01: RDL01 0x00800000-0x008407FF 1C15 BP
02: CG02 0x00000010-0x0000580F D439 AP
03: CG03 0x000000A0-0x0008009F A51D AP
04: CG39 0x00000020-0x0030001F 4C9F AP
05: CG42 0x00000050-0x0030004F 13F2 AP
06: CG47 0x00000070-0x0008006F C8A2 AP
>> waiting for phone: FAILED: Could not claim usb interface
(Are you root?)
and as you can see I am root

alright now just from trying it again I get yet another error
Code:
[email protected]:/home/brendon/Downloads# ./sbf_flash derpunlock.sbf
SBF FLASH 1.24 (mbm)
=== derpunlock.sbf ===
00: RDL03 0x00000000-0x002FFFFF AFD0 AP
01: RDL01 0x00800000-0x008407FF 1C15 BP
02: CG02 0x00000010-0x0000580F D439 AP
03: CG03 0x000000A0-0x0008009F A51D AP
04: CG39 0x00000020-0x0030001F 4C9F AP
05: CG42 0x00000050-0x0030004F 13F2 AP
06: CG47 0x00000070-0x0008006F C8A2 AP
>> waiting for phone: Connected.
>> uploading RDL03: 0.0%usb_bulk_write -110
>> uploading RDL03: failed at 00000000/00300000
!! failed
>> rebooting
usb_bulk_write -110
it didnt reboot the phone either

SO close restarted the phone and then this happened
Code:
[email protected]:/home/brendon/Downloads# ./sbf_flash derpunlock.sbf
SBF FLASH 1.24 (mbm)
=== derpunlock.sbf ===
00: RDL03 0x00000000-0x002FFFFF AFD0 AP
01: RDL01 0x00800000-0x008407FF 1C15 BP
02: CG02 0x00000010-0x0000580F D439 AP
03: CG03 0x000000A0-0x0008009F A51D AP
04: CG39 0x00000020-0x0030001F 4C9F AP
05: CG42 0x00000050-0x0030004F 13F2 AP
06: CG47 0x00000070-0x0008006F C8A2 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
usb_bulk_write -110
!! failed
>> rebooting
It seems to fail when a message appears on my phone "sec_exception: b655, eddc, eb"
after that appears on the phone it stops making progress

Related

[Q]QDL Tool not working for me...phone wont boot

QDLTool: M 2.7.4.8, Build ID: 1.301.20101022, SW: 12-5035-AUSB1AM-09
Report:
HW:
Board ID:
Comment:
--
LOG
--
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Sat Jan 22 19:15:11 2011
Check image DBL: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Streak\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/01/22 19:15:52
Elapsed Time: 40.56 sec
Any ideas? I did this process way to many times (this is because i tried to update to 1.6.1 from 1.6.0 and i got to many error messages..
and yes i am using ADB r288920
i was getting the same issues yesterday, flash 1.5.1 again, and make a factoty reset using clockwork then boot in recovery mode and make a factory reset agaion using the dell recovery option 1. and your phone should boot again, once booted u can flash 1.6.0 and 1.6.1.
Make sure you have the right driver installed, I was having the same issue. Head over to the streaksmart forums, there is a thread about QDL. I belive the 2nd or 3rd reply has the steps to fix the issue.
Sent from my Dell Streak using XDA App

Error switching phone to BP Pass through mode(0x70BE)

Error switching phone to BP Pass through mode
(0x70BE)
Index[2]: Unexpected chip 13
00: RDL03 0x00000000-0x002FFFFF 53DA AP
01: RDL01 0x00800000-0x008407FF 3A93 BP
Data[2]: Checksum error (Expected 0x1e96, Got 0x4029)
02: CG05 0x00000000-0x0139FF07 1E96 AP
!! failed
I'm trying to find a way around this too. But I do know when this first happened to me I got the 0x1000 error also that said I had no OS. I found a way to get around that at this thread http://forum.xda-developers.com/showthread.php?t=1182871 .

[Q] Can't install recovery (00180002), bootloader still locked

I tried each and every hint i found on the net, but i cannot install clockwork recovery and thus not install CM.
I followed the instructions from the cyanogenmod wiki for this phone.
After flashing the bootloader and "fastboot oem unlock" i cannot install the recovery file (recovery-clockwork-5.0.2.0-olympus.img). On the display the error "00180002" appears. So i suppose the bootloader isn't really unlocked.
What i have tried so far:
Flashing from Windows XP, using RSD Lite, fastboot and moto-fastboot ==> no success
Flashing from Ubuntu 14.04 x64, using sbf_flash, fastboot and moto-fastboot ==> no success
Any hints? Or can't this phone be unlocked? Can this be recognize it by the serial number?
Phone info:
System version 45.31.0.MB860.Vodafone.EU
Android version 2.3.4
Webtop version WT-1.2.0-133_41
Kernel 2.6.32.9 [email protected]#2
APFlex version
GAS_EMEA_USAOLYPGBVFDE_P020
GAS_EMEA_USAOLYPGBVFDE_M001
GAS_EMEA_USAOLYPVFCEOREEU_M001
Build number 4.5.2AA-74_OLE-31
Details:
./sbf_flash intl-fix-try1.sbf
SBF FLASH 1.23 (mbm)
http colon slash slash opticaldelusion dot org
=== intl-fix-try1.sbf ===
Index[5]: Unexpected chip 16
Index[6]: Unexpected chip 16
00: RDL03 0x00000000-0x002FFFFF 7F75 AP
01: RDL01 0x00800000-0x008407FF 3556 BP
02: CG02 0x00000010-0x0000580F 4615 AP
03: CG03 0x000000A0-0x0008009F 2135 AP
04: CG42 0x00000020-0x0030001F F03C AP
05: CG44 0x00000050-0x0030004F 0C66 AP
06: CG47 0x00000070-0x0008006F E7CB AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG02: 100.0%
-- OK
>> uploading CG03: 100.0%
-- OK
>> uploading CG42: 100.0%
-- OK
>> uploading CG44: 100.0%
-- OK
>> uploading CG47: 100.0%
-- OK
>> rebooting
moto-fastboot devices
TA74409TE0 fastboot
moto-fastboot oem unlock
... INFOOEM unlock is not implemented
OKAY [ 0.002s]
./moto-fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img
sending 'recovery' (4824 KB)... OKAY [ 0.395s]
writing 'recovery'... FAILED (remote: (00180002))
How old is your device? Was it serviced recently?
Allegedly there are some newer devices (or ones serviced recently) that have the newer bootloader which cannot be unlocked.
OEM unlock is not implemented means the sbf flash didn't actually work, that's why I suspect you might have that kind of bootloader. Unexpected chip 16 seems suspicious too...
I have no other suggestions/ideas, you seem to have done the procedure correctly.
Kind of (very) far fetched, but maybe you could try using sbf_flash on x86 Ubuntu.
Also, questions should go into Q&A, not Development.
ravilov said:
How old is your device? Was it serviced recently?
Click to expand...
Click to collapse
The phone is three years old.
ravilov said:
Allegedly there are some newer devices (or ones serviced recently) that have the newer bootloader which cannot be unlocked.
OEM unlock is not implemented means the sbf flash didn't actually work, that's why I suspect you might have that kind of bootloader. Unexpected chip 16 seems suspicious too...
Click to expand...
Click to collapse
Hmpf, looks very much like it ...
ravilov said:
I have no other suggestions/ideas, you seem to have done the procedure correctly.
Kind of (very) far fetched, but maybe you could try using sbf_flash on x86 Ubuntu.
Click to expand...
Click to collapse
I'll give it a shot. Thanks so far ...

lenovo k5 (a6020a40) bootloader unlock

Hi,
i have lenovo vibe k5 (a6020a40) ROW.it it bricked so i only can access fastboot
QFIL shows edl failed.so help me to boot edl...
fastboot oem unlock
fastboot flashing unlock
fastboot oem reboot-edl
are tried
"fastboot oem device-info" shows
device tampered: false
device unlocked: false
thankss
Here is y output.
xagar said:
Hi,
i have lenovo vibe k5 (a6020a40) ROW.it it bricked so i only can access fastboot
QFIL shows edl failed.so help me to boot edl...
fastboot oem unlock
fastboot flashing unlock
fastboot oem reboot-edl
are tried
"fastboot oem device-info" shows
device tampered: false
device unlocked: false
thankss
Click to expand...
Click to collapse
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
I would like to fully back up the phone and have a safe procedure, before tampering like:
OEM Unlock, Changing Recovery to TWRP, Rooting, checking custom ROM's e.t.c.
I've just bought the phone and I'm still reasrching, but I think that I can provide You with the firmware, but please prowide me with the necessary tools and how to.
A6020a40 can't flash QFIL please help me...Help me...
Validating Application Configuration
Load APP Configuration
COM:26
PBLDOWNLOADPROTOCOL:0
PROGRAMMER:True
PROGRAMMER:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8936.mbn
RESETSAHARASTATEEMACHINE:False
SEARCHPATH:C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM:
rawprogram_unsparse.xml
PATCH:
patch0.xml
ACKRAWDATAEVERYNUMPACKETS:False
ACKRAWDATAEVERYNUMPACKETS:100
MAXPAYLOADSIZETOTARGETINBYTES:False
MAXPAYLOADSIZETOTARGETINBYTES:49152
DEVICETYPE:UFS
PLATFORM:8x26
VALIDATIONMODE:0
RESETAFTERDOWNLOAD:True
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: C:\Program Files (x86)\Qualcomm\QPST\bin
RAWPROGRAM file path: C:\Program Files (x86)\Qualcomm\QPST\bin\rawprogram_unsparse.xml
PATCH file path:C:\Program Files (x86)\Qualcomm\QPST\bin\patch0.xml
Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8936.mbn
Process Index:0
Start Download
Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8936.mbn
***** Working Folder:C:\Users\Pasan Apasara\AppData\Roaming\Qualcomm\QFIL\COMPORT_26
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\Pasan Apasara\AppData\Roaming\Qualcomm\QFIL\COMPORT_26
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:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8936.mbn
05:32:45: Requested ID 13, file: "C:\Program Files (x86)\Qualcomm\QPST\bin\prog_emmc_firehose_8936.mbn"
05:34:15: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
05:34:15: ERROR: function: sahara_main:924 Sahara protocol error
05:34:15: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download

Unlocked bootloader, fastboot not exist

Hey, I have a problem, I spend 2 days on it and can't find solution. So in the past I unlocked bootloader, used Qfil, everything was fine but few months ago i switch to Z fold 3 and stop using my G8X, now I have a buyer for that phone and I can't lock bootloader at all.
So manual pressing buttons not working, I tried hundred times. adb reboot bootloader/fastboot just restarting my phone. I have access to recovery, EDL mode etc, my phone is visible as adb devices.
Choosing option restart to bootloader in recovery just restarting my phone. I tried every f**cking thing to do it with Qfil and do it again with switching abl_a etc but It's always sahara fail doesn't matter what version qfil or QPST is. I even installed clear windows 7 and still same problem (on my main PC I'm using windows 11). adb, fastboot, qualcomm 9008, lg drivers, everything is installed.
I installed different OS with KDZ with android 9/10/11, Canadian/US, no different
I beg you, please give me something what I can try cause I'm going crazy here. Like it's unlocked, it's not a phone what you can't unlock. I was hoping to write fastboot oem lock and that's it.
With unlocked bootloader fingerprint reader not working. Guy is waiting with money, I said I need few days to fix it but I feel I tried everything.
Thanks everyone who will answer here.
You can try use ADB,adb reboot fastboot.If can't enter fastboot,that may be because boot or abl does not support FastBoot,you can try using adb reboot bootloader.
Like I said adb reboot fastboot and adb reboot bootloader just restarting my phone
SiNec said:
Like I said adb reboot fastboot and adb reboot bootloader just restarting my phone
Click to expand...
Click to collapse
If you cant get into qfil, then why are u expecting to get fastboot mode????
First load eng abl. For sahara error, use a different usb port, or restart to edl when you are connected to qfil or use a different pc.
lefttobleed said:
If you cant get into qfil, then why are u expecting to get fastboot mode????
First load eng abl. For sahara error, use a different usb port, or restart to edl when you are connected to qfil or use a different pc.
Click to expand...
Click to collapse
In 2 days of struggling I tried everything even if obviously it was stupid and not possible but that actually was answer to guy who said to try use that commends
I tried my PC and my laptop. Both of them had windows 11, I even installed Windows 7 on my laptop after many fails on both devices, all usb port on PC and laptop checked with 5 cables, with PC on tower cases and motherboard, on laptops i tried even usb type C, no results. Cable and PC exactly same what few month ago I used to unlocked it.
I'm always in edl mode cause with booted phone is just says "switch to edl -> fail to switch into emergency download mode"
I'm not good at English, hope you understand: how to lock bootloader
edl mode -> use QFIL load image abl_a, abl_b by abl unlock file ( this step help you get in to fastboot mode).
get into fastboot mode: using fastboot command
fastboot flash abl_a xxx (xxx = your stock abl_a file)
fastboot flash abl_b xxx (xxx = your stock abl_b file)
fastboot flash boot_a xxx (xxx = your stock boot_a file)
fastboot flash boot_a xxx (xxx = your stock boot_b file)
fastboot oem lock
but lock bootloader doesn't fix fingerprint scanner working, have to downgrade to android 9 and fix by hide code *#546368#*xxx# example:
KillerOpen said:
edl mode -> load image abl_a, abl_b by abl unlock file, get into fastboot mode: using fastboot command
fastboot flash abl_a xxx (xxx = your stock abl_a file)
fastboot flash abl_b xxx (xxx = your stock abl_b file)
fastboot flash boot_a xxx (xxx = your stock boot_a file)
fastboot flash boot_a xxx (xxx = your stock boot_b file)
fastboot oem lock
but lock bootloader doesn't fix fingerprint scanner working, have to downgrade to android 9 and fix by hide code *#546368#*xxx# example:
Click to expand...
Click to collapse
Thanks for reply. Its almost 3am for me and still fighting with it Fingerprint is one thing but my guy want locked bootloader cause he is scared of stuff like that and it shows warning when boot up.
But could you explain more your way with edl mode? I dont get it. Im trying for the whole day make rawprogram and patch so I could finally use QFIL, without it it's sahara problem. But all methods online are old. Most of it not supporting new KDZ files, python way not working, linux way not working. My phone is in 9008 drivers when in EDL mode and its not visible for adb. It's only visible with normal mode.
Is your way skip qfil and load modified adl files straight into device?
SiNec said:
Thanks for reply. Its almost 3am for me and still fighting with it Fingerprint is one thing but my guy want locked bootloader cause he is scared of stuff like that and it shows warning when boot up.
But could you explain more your way with edl mode? I dont get it. Im trying for the whole day make rawprogram and patch so I could finally use QFIL, without it it's sahara problem. But all methods online are old. Most of it not supporting new KDZ files, python way not working, linux way not working. My phone is in 9008 drivers when in EDL mode and its not visible for adb. It's only visible with normal mode.
Is your way skip qfil and load modified adl files straight into device?
Click to expand...
Click to collapse
if you want lock bootloader, enter edl mode, use QFIL load image abl_a and abl_b by a abl file (using to unlock), it help you can get intro fastboot ( press -vol and power until you hear sound on windows, release power, keep hold -vol ), when you get intro fastboot mode (status: unlocked) flash your stock abl_a abl_b boot_a boot_b by fastboot command before you lock bootloader by command: fastboot oem lock
But I cant use Qfil, All ways to get rawprogram and patch0 not works anymore. Some of them not supporting new KDZ, some of them have problems in general. I tried python way, linux way etc. All youtube videos are outdated. Idk how I can get that files for my g8x. without that(I think) I'm getting Sahara fail error and cant open partition menager. Last year when I was unlocking my bootloader everything work perfect, I rooted like 10lg before, first time in my life I have such a big problem with that phone.
SiNec said:
But I cant use Qfil, All ways to get rawprogram and patch0 not works anymore. Some of them not supporting new KDZ, some of them have problems in general. I tried python way, linux way etc. All youtube videos are outdated. Idk how I can get that files for my g8x. without that(I think) I'm getting Sahara fail error and cant open partition menager. Last year when I was unlocking my bootloader everything work perfect, I rooted like 10lg before, first time in my life I have such a big problem with that phone.
Click to expand...
Click to collapse
QFIL -> Flat Build > Browse > choose G8x firehose > Tools > Partition manager
Did it work ?
KillerOpen said:
QFIL -> Flat Build > Browse > choose G8x firehose > Tools > Partition manager
Did it work ?
Click to expand...
Click to collapse
I'm still getting sahara fail error. 2 computers, trying windows 11, windows 8, windows 7, bunch of different drivers, 5 cables, still nothing. It's still "unable to read packet header" error :/
SiNec said:
I'm still getting sahara fail error. 2 computers, trying windows 11, windows 8, windows 7, bunch of different drivers, 5 cables, still nothing. It's still "unable to read packet header" error :/
Click to expand...
Click to collapse
Unistall your QFIL, try this: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file
If it wont work, I give in.
KillerOpen said:
Unistall your QFIL, try this: https://www.mediafire.com/file/220h5xaxi1gd55m/QPST_2.7.496.zip/file
If it wont work, I give in.
Click to expand...
Click to collapse
I have a QPST from the beginning. I tried all different kinds, and qfill standalone, nothing helps :/ Thank you anyway for help
KillerOpen said:
QFIL -> Flat Build > Browse > choose G8x firehose > Tools > Partition manager
Did it work ?
Click to expand...
Click to collapse
This is log:
2022-06-29 03:07:44.989 Image Search Path: C:\Users\Kopec\Downloads\firehose\
2022-06-29 03:07:45.004 Start Download
2022-06-29 03:07:45.004 Program Path:C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:07:45.017 ***** Working Folder:C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.465 Binary build date: Jun 25 2019 @ 03:16:15
2022-06-29 03:09:15.469 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.475 Sahara mappings:
2022-06-29 03:09:15.477 2: amss.mbn
2022-06-29 03:09:15.482 6: apps.mbn
2022-06-29 03:09:15.485 8: dsp1.mbn
2022-06-29 03:09:15.488 10: dbl.mbn
2022-06-29 03:09:15.491 11: osbl.mbn
2022-06-29 03:09:15.493 12: dsp2.mbn
2022-06-29 03:09:15.495 16: efs1.mbn
2022-06-29 03:09:15.496 17: efs2.mbn
2022-06-29 03:09:15.498 20: efs3.mbn
2022-06-29 03:09:15.499 21: sbl1.mbn
2022-06-29 03:09:15.500 22: sbl2.mbn
2022-06-29 03:09:15.501 23: rpm.mbn
2022-06-29 03:09:15.502 25: tz.mbn
2022-06-29 03:09:15.504 28: dsp3.mbn
2022-06-29 03:09:15.505 29: acdb.mbn
2022-06-29 03:09:15.515 30: wdt.mbn
2022-06-29 03:09:15.516 31: mba.mbn
2022-06-29 03:09:15.517 13: C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:09:15.517
2022-06-29 03:09:15.518 03:09:15: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2022-06-29 03:09:15.519
2022-06-29 03:09:15.519 03:09:15: ERROR: function: sahara_main:982 Sahara protocol error
2022-06-29 03:09:15.520
2022-06-29 03:09:15.521 03:09:15: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-06-29 03:09:15.522
2022-06-29 03:09:15.522
2022-06-29 03:09:15.523 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-06-29 03:09:15.529 Finish Get GPT
SiNec said:
This is log:
2022-06-29 03:07:44.989 Image Search Path: C:\Users\Kopec\Downloads\firehose\
2022-06-29 03:07:45.004 Start Download
2022-06-29 03:07:45.004 Program Path:C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:07:45.017 ***** Working Folder:C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.465 Binary build date: Jun 25 2019 @ 03:16:15
2022-06-29 03:09:15.469 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.475 Sahara mappings:
2022-06-29 03:09:15.477 2: amss.mbn
2022-06-29 03:09:15.482 6: apps.mbn
2022-06-29 03:09:15.485 8: dsp1.mbn
2022-06-29 03:09:15.488 10: dbl.mbn
2022-06-29 03:09:15.491 11: osbl.mbn
2022-06-29 03:09:15.493 12: dsp2.mbn
2022-06-29 03:09:15.495 16: efs1.mbn
2022-06-29 03:09:15.496 17: efs2.mbn
2022-06-29 03:09:15.498 20: efs3.mbn
2022-06-29 03:09:15.499 21: sbl1.mbn
2022-06-29 03:09:15.500 22: sbl2.mbn
2022-06-29 03:09:15.501 23: rpm.mbn
2022-06-29 03:09:15.502 25: tz.mbn
2022-06-29 03:09:15.504 28: dsp3.mbn
2022-06-29 03:09:15.505 29: acdb.mbn
2022-06-29 03:09:15.515 30: wdt.mbn
2022-06-29 03:09:15.516 31: mba.mbn
2022-06-29 03:09:15.517 13: C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:09:15.517
2022-06-29 03:09:15.518 03:09:15: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2022-06-29 03:09:15.519
2022-06-29 03:09:15.519 03:09:15: ERROR: function: sahara_main:982 Sahara protocol error
2022-06-29 03:09:15.520
2022-06-29 03:09:15.521 03:09:15: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-06-29 03:09:15.522
2022-06-29 03:09:15.522
2022-06-29 03:09:15.523 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-06-29 03:09:15.529 Finish Get GPT
Click to expand...
Click to collapse
have you switch emmc to ufs on QFIL ?
KillerOpen said:
have you switch emmc to ufs on QFIL ?
Click to expand...
Click to collapse
Yes, all that basic stuff, I done
KillerOpen said:
I'm not good at English, hope you understand: how to lock bootloader
edl mode -> use QFIL load image abl_a, abl_b by abl unlock file ( this step help you get in to fastboot mode).
get into fastboot mode: using fastboot command
fastboot flash abl_a xxx (xxx = your stock abl_a file)
fastboot flash abl_b xxx (xxx = your stock abl_b file)
fastboot flash boot_a xxx (xxx = your stock boot_a file)
fastboot flash boot_a xxx (xxx = your stock boot_b file)
fastboot oem lock
but lock bootloader doesn't fix fingerprint scanner working, have to downgrade to android 9 and fix by hide code *#546368#*xxx# example:
Click to expand...
Click to collapse
Friend I have a problem with my g8x and the fingerprint sensor, since I did a bad flashed to a11 it does not work for me it gives me an error, do you think that downloading a9 can fix it?
I have blocked the network and error in nt code but I have understood that in another problem and it is fixed through server
mclarenf195 said:
Friend I have a problem with my g8x and the fingerprint sensor, since I did a bad flashed to a11 it does not work for me it gives me an error, do you think that downloading a9 can fix it?
I have blocked the network and error in nt code but I have understood that in another problem and it is fixed through server
Click to expand...
Click to collapse
I've tried A9 (the indian variant given that's the one people say works) to fix my fp scanner and had no luck, but that's the only solution people give so maybe on yours it will work.
mclarenf195 said:
Friend I have a problem with my g8x and the fingerprint sensor, since I did a bad flashed to a11 it does not work for me it gives me an error, do you think that downloading a9 can fix it?
I have blocked the network and error in nt code but I have understood that in another problem and it is fixed through server
Click to expand...
Click to collapse
I tried with Android 9 UM version and it works. Test will fail but when you go to the settings it will let you to scan fingerprint. After that you need to update phone from the phone, not installing new KDZ. when you will update to androind 10/11(yours prefers) it's still working. I even did factory reset and it still works fine
SiNec said:
This is log:
2022-06-29 03:07:44.989 Image Search Path: C:\Users\Kopec\Downloads\firehose\
2022-06-29 03:07:45.004 Start Download
2022-06-29 03:07:45.004 Program Path:C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:07:45.017 ***** Working Folder:C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.465 Binary build date: Jun 25 2019 @ 03:16:15
2022-06-29 03:09:15.469 QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.ex'Current working dir: C:\Users\Kopec\AppData\Roaming\Qualcomm\QFIL\COMPORT_6
2022-06-29 03:09:15.475 Sahara mappings:
2022-06-29 03:09:15.477 2: amss.mbn
2022-06-29 03:09:15.482 6: apps.mbn
2022-06-29 03:09:15.485 8: dsp1.mbn
2022-06-29 03:09:15.488 10: dbl.mbn
2022-06-29 03:09:15.491 11: osbl.mbn
2022-06-29 03:09:15.493 12: dsp2.mbn
2022-06-29 03:09:15.495 16: efs1.mbn
2022-06-29 03:09:15.496 17: efs2.mbn
2022-06-29 03:09:15.498 20: efs3.mbn
2022-06-29 03:09:15.499 21: sbl1.mbn
2022-06-29 03:09:15.500 22: sbl2.mbn
2022-06-29 03:09:15.501 23: rpm.mbn
2022-06-29 03:09:15.502 25: tz.mbn
2022-06-29 03:09:15.504 28: dsp3.mbn
2022-06-29 03:09:15.505 29: acdb.mbn
2022-06-29 03:09:15.515 30: wdt.mbn
2022-06-29 03:09:15.516 31: mba.mbn
2022-06-29 03:09:15.517 13: C:\Users\Kopec\Downloads\firehose\prog_ufs_firehose_sm8150_lge.elf
2022-06-29 03:09:15.517
2022-06-29 03:09:15.518 03:09:15: ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
2022-06-29 03:09:15.519
2022-06-29 03:09:15.519 03:09:15: ERROR: function: sahara_main:982 Sahara protocol error
2022-06-29 03:09:15.520
2022-06-29 03:09:15.521 03:09:15: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2022-06-29 03:09:15.522
2022-06-29 03:09:15.522
2022-06-29 03:09:15.523 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2022-06-29 03:09:15.529 Finish Get GPT
Click to expand...
Click to collapse
The elf file is corrupt

Categories

Resources