Realme_X2_RMX1991_11_A.11_191026_f9fe8ec3_RMX1991_prog_firehose_ddr.elf
Realme_X2_RMX1991_11_F.23_210903_RFT_prog_firehose_ddr.elf
These are original files and cannot be used directly in QFIL because of the manufacturer's verification signature.
Related
I had to start a new thread since no-one is reading
http://forum.xda-developers.com/showthread.php?t=393370&highlight=Ranju_SD_Flash.rar
it's about updating the Rom from an SD card (when unable to connect to a PC because of a broken USB socket on the mobile)
To comnplete this innovative update, you need the Ranju_SD_Flash.rar file, which is a "SD-Rom image tool" but the the file has been removed from the download site indicated on the above mentioned page.
Perhaps Tomal is feeling underappreciated.
Well I certainly appreciate his efforts and will carry out his instructions to the letter, at my own risk.
But where can I get the Ranju_SD_Flash.rar file now?
SD Rom Image tool
I located the SD-ROM image tool: Ranju_SD_Flash.zip and attach it here (it was known before as Ranju_SD_Flash.rar.)
I contains the 5 files
DisAsm.dll
g3.bin
HTC64_Extended_ROM_Tool.exe
SDFlash_G3.cmd
SDImage.exe
Hi all, having a strange issue with a signed update zip file.
i have an update i need to modify, i made the changes and signed it properly, but update failed.
to make sure, i just unzipped the original file and zipped it again (no changes and all signatures shouldn't change) - update failed AGAIN.
(BTW i also tried to sign after zipping, that didn't help as well).
the original zip and the new one aren't the same size, but when extracted all files are identical.
would appreciate any direction here..
some specific info - i'm trying to modify a connected car (FlyAudio) update file, the recovery is proprietary so there's little info on why it fails.
bigfoot2047 said:
Hi all, having a strange issue with a signed update zip file. i have an update i need to modify, i made the changes and signed it properly, but update failed. to make sure, i just unzipped the original file and zipped it again (no changes and all signatures shouldn't change) - update failed AGAIN. (BTW i also tried to sign after zipping, that didn't help as well). the original zip and the new one aren't the same size, but when extracted all files are identical. would appreciate any direction here.. some specific info - i'm trying to modify a connected car (FlyAudio) update file, the recovery is proprietary so there's little info on why it fails.
Click to expand...
Click to collapse
Typically, update.zip files are recovery flash files and ODIN doesn't flash zip files in that manner.
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [d2vzw] from the Bridge of the U.S.S. Enterprise.
ok, so the problem is that the update.zip (it has a different name but it's an 'update.zip' file) wasn't signed.
after extracting, zipping, signing i'm getting a file that's ~1K smaller than the original and identical up to that point.
the tool i'm using to sign uses test keys so i assume it's a keys issue.
--------------------------
update - needed to sign with -w (signapk option) that added the required footer.
thanks all
Hi,
i need the Stock ROM and the specific Combination File for A505FNXXU1ASC7.
I used the wrong Files: A505FDDU1ASBD
There is a combination File which does not work, because of error "Please get the approval to use factory binaries (PIT)"
i dont know if there are solutions yet
there's many ways to extract the ofp file, but u need some tools like jtag, this post its to find someone who have it or know how to extract it without them.
In the ofp file are the files on mbn and xml format, used to flash devices with QFIL, so thats why i need it cause the device its bricked without recovery and bootloader, so, the only option left is the QFIL
good
Please send me a tool where I can repair the file with Android software in the KDZ file or in the TOT file.
I have a LG G4 H815 smartphone failure and I still have a problem because my firmware upload tool - LGUP - detects damage to the software file.
KDZ firmware file - is damaged.
My guess is that the kdz file with Android firmware is damaged - according to what Google says. I have it like this.
Look this screen.
I have the error code: 0x2000 -
So it means that the software file has got damaged. I have sent information on this topic what Google says about this error code.
Please send me a file repair tool.
0x2000 Error Codes are caused in one way or another by misconfigured system files in your windows operating system. So, If you got 0x2000 Error then We strongly recommend that you Download (TechUtilities) Repair Tool.
> https://www.google.com/search?q=0x2...0.69i59j0l7.4198j0j7&sourceid=chrome&ie=UTF-8
With kind regards LukeSlovian