View Single Post
Old 05-24-2022, 05:14 AM   #67
brianting
Junior Member
brianting began at the beginning.
 
Posts: 3
Karma: 10
Join Date: May 2022
Device: none
hello Renate

Quote:
Originally Posted by Renate View Post
Hi @amghwk - sorry that I didn't notice your earlier post.
Edit: Your problem may be different, but you might try my way anyway.
There are also mysterious cases where "fastboot boot" does not work but "fastboot flash" and then regular boot does work. If you have backups you should be able to play safely.

Hi @Machinus

If you have access to a (real, not virtual) Windows box, I can probably help you. I have an EDL utility for Windows. What you are trying to do is very simple, and it should be simple.

Go to the website in my signature and navigate to the EDL page. It's a bit of a beta, but I'm willing to work with anybody that is having problems.

Step 0: Download edl.exe, it's 132kB with no dependencies.
Step 1: Get into EDL (05c6/9008) mode
Step 2: Got a driver for it? If not download "Zadig" and give it one.
Step 3: Got a loader for it? If not download this, it should be the correct one if you have the same model as the OP:
https://github.com/bkerler/Loaders/r...4665_FHPRG.bin
Oh, you were looking forward to downloading 100 Megs of loaders that you will never use. Sorry to disappoint you.
Step 4: Rename the file something sensible.
Step5:
Code:
C:\>edl.exe /lsomething-sensible
He, he, I was only kidding about something sensible, don't forget the "/l" before it.
Step 6: Since you're running A/B you have to know which boot_x is the right one:
Code:
C:\>edl.exe /u /g
Step 7: One of them is inactive, choose the other one:
Code:
C:\>edl.exe /u /r /pboot_a boot.img /t
And the result should be the (correct) ~20Megs and not 20Megs + 80Megs of zeroes.
Step 8: If you are in doubt what you have just downloaded, get my ImgUtil.exe and do:
Code:
C:\>imgutil.exe /v boot.img
Header:           596 (00000254)
Kernel:    12,937,496 (00C56918) @ 00008000
  Payload: 12,636,840 (00C0D2A8)
  DTB:        300,656 (00049670)
Ramdisk:            0 (00000000) @ 01000000
Second:             0 (00000000) @ 00F00000
(Or something similar, the numbers will be different for you.)

Good luck!
my problem is after the sahara protocol, the firehose one came out with this error

C:\Users\Administrator\Desktop\edl thing>edl.exe /lprog_ufs_firehose_sdm855_ddr.elf /u /g
Found EDL 9008
Serial: e3fc032c
HWID: 000a50e100290025, QC: 000a50e1, OEM: 0029, Model: 0025
Hash: 7e5acfff90370967-edd2bdf205a9ebc9-035abca140b3ab9b-b7771bd7c27057cb
Sending prog_ufs_firehose_sdm855_ddr.elf 100% Ok
Waiting for Firehose... Ok
Configuring... Ok
Requesting GPT 0 header...
<log value="ERROR: Failed to initialize (open whole lun) UFS Device slot 0 partition 0" />
<log value="ERROR: Failed to open the device:3 slot:0 partition:0 error:0" />
<log value="ERROR: OPEN handle NULL and no error, weird 344384084" />
<log value="ERROR: Failed to open device, type:UFS, slot:0, lun:0 error:3" />
Nope
brianting is offline   Reply With Quote