Dear Bios-mods community,
I bricked my Dell xps17 l702x. The chip is currently on a external board for flashing purposes, but I can't seem to find a proper bios dump on the web.
Can someone please provide me with a dump? I am willing to pay a compensation for the effort.
Best regards,
rmn
I'll grab it for you... And I'll edit here, wait
try this
https://hostr.co/CO0ORqINGzsT
I think the right one is the 2.5Mb one, BIOS.CAP, but try both.
Report.
Thanks fjfc.
Are these actual dumps, or an extraction of the .exe? I got a .bin on another forum.
Can you please discribe your method of acquiring the files? I can't test right now. The chip is being sended to me and will be here within a few days. If your files are not encryted and work as they should, I will donate.
(03-04-2014, 11:05 AM)rmn Wrote: [ -> ]Thanks fjfc.
Are these actual dumps, or an extraction of the .exe? I got a .bin on another forum.
Can you please discribe your method of acquiring the files? I can't test right now. The chip is being sended to me and will be here within a few days. If your files are not encryted and work as they should, I will donate.
these are from a recovery disk... send me that bin for me to check if it is valid to flash direct to the bios, also, have you tried recovery steps?
Those from recov disk are most likely encrypted. This has already proven to be a problem.
Already tried recov steps, did not work. When de device is back I will try again, just to be sure. Maybe I need to clearify this. The laptop was sent to a hardware reapairshop, since I don't have any experience with desoldering chips and was too scared to completely destroy the board. This hardwaredude went for holiday, just today, and told me has sent back the device. So atm I can't actually do anything until the device is back.
Can I e-mail you the .bin? It contains serial numbers etc. so I am bit reluctant of sharing it publicly. It got it from some guy on forum and I don't think he'd appreciate it.
Edit: I'll PM it. Ok?
(03-04-2014, 01:46 PM)fjfc Wrote: [ -> ]ok man
It's UEFI encapsulated You know what it means when Recovery is done with Encapsulated Bios ? You have tried !
You tried give it in eating to PMTool ? Try and You'll get an error.
Remove 0xB0 bytes from file starting position BIOS1.WPH :
BD86663B760D3040B70EB5519E2FC5A05000000000000100500050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000D954937A68044A4481CE0BF617D890DF00005000000000005F465648FF8EFFFF4800134C00000001500000000000010000000000000000007F363EF3D24101429CB7AFA63DCCEEC9B1350140181042F8
Save it and let PMTool eat it ! I don't know if It works and its effect, but I could not be quite to use these files.
If I am an breaking balls let me know I will not interfering yet, friend.
reagrds
(03-05-2014, 06:53 AM)BDMaster Wrote: [ -> ] (03-04-2014, 01:46 PM)fjfc Wrote: [ -> ]ok man
It's UEFI encapsulated You know what it means when Recovery is done with Encapsulated Bios ? You have tried !
You tried give it in eating to PMTool ? Try and You'll get an error.
Remove 0xB0 bytes from file starting position BIOS1.WPH :
BD86663B760D3040B70EB5519E2FC5A05000000000000100500050000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000D954937A68044A4481CE0BF617D890DF00005000000000005F465648FF8EFFFF4800134C00000001500000000000010000000000000000007F363EF3D24101429CB7AFA63DCCEEC9B1350140181042F8
Save it and let PMTool eat it ! I don't know if It works and its effect, but I could not be quite to use these files.
If I am an breaking balls let me know I will not interfering yet, friend.
reagrds
Thanks for all the help BDMaster, you can interferr in my experiments when you want as I take you as my mentor same way as you take donovan
You're right, I tried it already, I didn't knew how to extract phoenyx so thanks, but the user PM'ed me with a .bin that he got in another place for me to verify and it is valid 4MB with Descriptor, ME and BIOS regions, he'll be flashing it with external EEPROM programmer.
I recognize my mistake and already removed the file.