FliphoneBochurLevel 5 - Gold Elite Member
aapost Thanks! I'll try to practice while I anxiously wait for [Login to see the link] 's firmware.
aapost Thanks! I'll try to practice while I anxiously wait for [Login to see the link] 's firmware.
FliphoneBochur My phones are using lower firmware versions and I'd rather not update it. I think aapost should try sending his rom, as you already tried getting the f019 firmware from Kazuna's site, and couldn't boot. The f119 often works with the f019 as seen in the OP (I've done it myself).
Biden2020prez The whole problem was caused by uploading a rom from the F119. Are you really sure it’ll work?
aapost When I run the backup command, I get this:
Traceback (most recent call last):
File "C:\Users\Admin\Desktop\edl-master\edl", line 130, in <module>
from docopt import docopt
ModuleNotFoundError: No module named 'docopt'
lgexalter1 thats assuming he has pip... otherwize download this script [Login to see the link] and run it, then run lgexalter1's command.
FliphoneBochur I am very much unsure it would work, but... you flashed the f019 and are still in a brick. I think you need to be flashing a newer firmware version, which can possibly be a f119. You are bricked already, so doesn't hurt to try. if that doesnt work, I will software update my f019 and give you that rom (even though id prefer not).
FliphoneBochur requirements.txt for edl lists:
wheel
pyusb>=1.1.0
pyserial>=3.4
docopt>=0.6.2
pylzma>=0.5.0
pycryptodome
lxml>=4.6.1
colorama
usb
capstone
keystone-engine
you might need to do a pip install for a few of those, and any others that pop up until the No module messages go away.
lgexalter1 Thanks! Now after connecting to edl, my computer spat all this back (sorry for posting the whole thing, I just don't know what's important):
Traceback (most recent call last):
File "C:\Users\Admin\Desktop\edl-master\edl", line 391, in <module>
base.run()
File "C:\Users\Admin\Desktop\edl-master\edl", line 299, in run
conninfo = self.doconnect(loop)
^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\Desktop\edl-master\edl", line 193, in doconnect
self.cdc.connected = self.cdc.connect(portname=self.portname)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\Desktop\edl-master\edlclient\Library\Connection\usblib.py", line 226, in connect
self.configuration = self.device.get_active_configuration()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 921, in get_active_configuration
return self._ctx.get_active_configuration(self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 113, in wrapper
return f(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 249, in get_active_configuration
self.managed_open()
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 113, in wrapper
return f(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\core.py", line 131, in managed_open
self.handle = self.backend.open_device(self.dev)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\backend\libusb1.py", line 804, in open_device
return _DeviceHandle(dev)
^^^^^^^^^^^^^^^^^^
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\backend\libusb1.py", line 652, in __init__
_check(_lib.libusb_open(self.devid, byref(self.handle)))
File "C:\Users\Admin\AppData\Local\Programs\Python\Python311\Lib\site-packages\usb\backend\libusb1.py", line 600, in _check
raise NotImplementedError(_strerror(ret))
NotImplementedError: Operation not supported or unimplemented on this platform
I don't know if this has anything to do with this long nonsense (to me), but Zadig says it reinstalled the driver, but it keeps disconnecting the device during installation, and when I manually reboot it into edl and plug it back in the driver is still listed as libusb0, not libusb-win32.
What do I do about both of these?
aapost Thanks! That's exactly what I did
Biden2020prez A) I have pip
B) Now I'm waiting on [Login to see the link] for his thoughts
C) What do you have to say about that long meshugas?
Biden2020prez if they have an f019 hardware model, a firmware for an f019 would be preferable regardless of version.
Running the edl rl command would pull the images without altering the phone, so there is no need to update or alter a phone that is working.
I would recommend that the images you use be pulled using edl to assure compatibility with a push back using edl.
of course remembering to exclude those 5 files mentioned.
lgexalter1 I installed it, but I didn't restart my computer. I just restarted my computer and I didn't get that whole long megillah, but after cmd said Device detected :)
it just went to the next command input, and nothing showed up in my output folder. [Login to see the link] any suggestions?
FliphoneBochur Hmm yes, it appears to be a driver issue with windows... On linux you can change some udev rules, but someone else with experience in getting phones/drivers working together on windows will have to assist with that one (I assume that would probably need to occur regardless of what program you used to interact with the phone in edl mode)
So would anybody who knows how to work with that be able to help me with:
FliphoneBochur Zadig says it reinstalled the driver, but it keeps disconnecting the device during installation, and when I manually reboot it into edl and plug it back in the driver is still listed as libusb0, not libusb-win32.
? [Login to see the link] any ideas?
aapost if they have an f019 hardware model, a firmware for an f019 would be preferable regardless of version.
He already tried doing the one on Kazuna's site, and is still within his brick.
aapost Running the edl rl command would pull the images without altering the phone, so there is no need to update or alter a phone that is working.
true. I was saying that I've had many experiences with many of these devices and I think the issues happen when flashing newer devices with the older firmware's on Kazuna's site. By the way, there is also a benefit of flashing the f119 firmware (1. Its factory Unlocked 2. its working with adb). but i guess its worth a try for me to pull my firmware, but its also worth a try for yours. lets both upload it.
FliphoneBochur what is the full output after running edl rl your_dump_folder_name --genxml --loader=path/to/prog_emmc_firehose_8909.mbn?
make sure your current working directory has a folder you want the files to go in to and that you replace your_dump_folder_name with the name of the folder, and make sure the path after = on loader points to the location where you saved the firehose file prog_emmc_firehose_8909.mbn.
FliphoneBochur Use Bkerler's the one that lgexalter1 linked to. thats the source and its the best try.
C:\Users\Admin\Desktop\edl-master>py edl rl "C:\Users\tzvib\Desktop\Yoni Test" --genxml --loader=prog_emmc_firehose_8909.mbn
No module named 'Crypto'
Qualcomm Sahara / Firehose Client V3.60 (c) B.Kerler 2018-2022.
main - Using loader prog_emmc_firehose_8909.mbn ...
main - Waiting for the device
main - Device detected :)
C:\Users\Admin\Desktop\edl-master>
(I put the loader in the edl folder, just clarifying, and if I try pip install crypto
, it outputs this:
Requirement already satisfied: crypto in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (1.4.1)
Requirement already satisfied: Naked in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from crypto) (0.1.32)
Requirement already satisfied: shellescape in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from crypto) (3.8.1)
Requirement already satisfied: requests in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from Naked->crypto) (2.28.2)
Requirement already satisfied: pyyaml in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from Naked->crypto) (6.0)
Requirement already satisfied: charset-normalizer<4,>=2 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (3.0.1)
Requirement already satisfied: idna<4,>=2.5 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (3.4)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (1.26.14)
Requirement already satisfied: certifi>=2017.4.17 in c:\users\admin\appdata\local\programs\python\python311\lib\site-packages (from requests->Naked->crypto) (2022.12.7)
Biden2020prez That's what I've been using the whole time.
FliphoneBochur you can also probably just use qfil if this is too hard, but this is better
Biden2020prez How do I backup in qfil? And what do you mean by better?
Open QFIL and connect your device to your computer
Select "Rawprogram0.xml" and "Patch0.xml" under "Programmer Path"
Click on "Load XML" button
Click on "Rawprogram0.xml" and then click on "Edit" button
Locate the files that you want to exclude from the backup and delete them from the "Rawprogram0.xml" file
Repeat step 5 for "Patch0.xml" file
Click on "Save" button
Click on "Download" button to start the firmware backup process