-
-
Notifications
You must be signed in to change notification settings - Fork 349
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this an edl loader for 001970E1 / QCM6490? #477
Comments
You don't need to redact the PK_HASH. There is nothing secret about it. |
AGM G2 firehose for shure will not work on FP5 because different HWID: 0x001970e100430000 on AGM G2 and 0x001970e100420002 on FP5. Even PK HASH is same. |
The Qualcomm SoCs are the same. The OEMs are different, but the fact that they are using the same PK_HASH indicates that they are not dissimilar. |
Must be same: SoC Id Including OEM, Model Id's and PK_HASH |
And even More, RollBack (RB) in SW_ID must be Higher or same. But unfortunatelly SW_ID is not readable by Sahara |
OEM and model are just footnotes as far as Sahara and Firehose are concerned. |
No, you are wrong, just try it in pratics and you will see. |
Yup, you are right. |
yes from CERT version 6.5 them hide HW id's only can see in firehose/xbl for example IMAGE_VARIANT_STRING: SocLanaiLAA for |
while using edl with OnePlus 10T india i am getting |
Actually there are devices that aren't fused. For these, the oem id doesn't really matter as long as the firehose loader supports it. Not everything that's in the documentation is right btw. With Sahara 3 a lot of things have changed in a very bad and user unfriendly way. |
Just for the record and because the FP5 got bricked AGAIN by a faulty flashing process I share the full hashes here – hopefully the elf file will be publicly available soon so people can unbrick their phone without sending this piece of hardware to a repair center... What a waste of resources :/ Fairphone 5 (FP5)
|
@codiflow Thanks for the hash. It's incompatible with the 3 loaders you had in your first post.
|
I've also been running into a bricked FP5 recently. Unfortunately I couldn't find any matching EDL/QFIL file on the internet by now. FP3 seems to work without firehose signatures, FP4 seems to require signatures and there also doesn't seem to be any public EDL files. Just found this curated list: http://www.temblast.com/ref/loaders.htm As there have been several cases with bricked Fairphone 5 devices during the last weeks it would be awesome to have an option to recover them by ourselves. |
I can say that currently (and as long as we don't get the EDL loader) there's NO other way to unbrick a FP5 apart from sending it back to the Fairphone repair center in France and let them swap / unbrick the phone. |
How are you calculating these hashes? |
|
While looking for an edl loader which can be used to unbrick a Fairphone 5 / AGM G2 Guardian I stumbled upon these files:
https://privatebin.io/?4695438c4fd49b2c#7D5sKyfxzNb8TiBrjL2Dqf5QomXyFebi31mFJs4nHQVG (there's a tar.gz attached)
The origin of the files seems to be here: https://xdaforums.com/t/agm-g2-guardian-5g-unlocked-qualcomm-qcm6490-long-range-thermal-monocular-android-12-108mp-7000-mah.4571873/page-5
Unfortunately none of the three files was working with my FP5 – but as I'm not really into this "edl thing" I thought maybe some of you is able to see if those files are real loaders and what device they are for.
While I tried to use them with a FP5 I always got this error:
Maybe someone of you has a hint? The USB cable is fine – I tried the whole process with a OP3 and it was all fine 😎
The text was updated successfully, but these errors were encountered: