I need EVA-L09C464 oeminfo. Can anyone please share it?
I need the oeminfo and custom.bin of EVA-L09C635 variant
Thank you,
*deleted*
Last week I tried to de-brand from C34 to C636. No matter what I did, I always ended up with the C900 firmware.
Managed to flash back to C34 and in the process flashed the "optus/au" AND "hw/normal" folders to /CUST/
The result was a successful flash back to C34, build number reading correctly, Optus branding on startup and everything sorted. But I'm still trying to get to the bottom of how this all works.
What I noticed last night is that the Project Menu is now usable (*#*#2846579#*#*) previously blocked by the Optus build. On further inspection, I am also missing 'custom.bin' that by my understanding tells the phone where to look for build-specific files on the CUST partition.
Questions:
1. Without custom.bin - how does the phone know which folders to access in CUST?
2. If I were to add a custom.bin that directed to the /hw/normal folder on CUST, how will this affect my Optus firmware.
3. Still trying to work out why the de-brand didn't work to C636 and my best guess is that the oeminfo I flashed didn't match the exact build of the firmware OR I didn't flash it right- can anyone confirm how specific oeminfo is to the firmware version?
Any help is appreciated. Just trying to learn.
Thanks.
halliday77 said:
3. Still trying to work out why the de-brand didn't work to C636 and my best guess is that the oeminfo I flashed didn't match the exact build of the firmware OR I didn't flash it right- can anyone confirm how specific oeminfo is to the firmware version?
Click to expand...
Click to collapse
Where did you get the C636 oeminfo and custom.bin from?
Z-Blade said:
Where did you get the C636 oeminfo and custom.bin from?
Click to expand...
Click to collapse
oeminfo from this post.
Custom.bin I copied from the SKR tool files. Technically the C636 files on the SKR tool are for the dual sim variant - so I can't use the oeminfo, but the actual contents of custom.bin are a single file path, so it shouldn't matter.
halliday77 said:
oeminfo from this post.
Custom.bin I copied from the SKR tool files. Technically the C636 files on the SKR tool are for the dual sim variant - so I can't use the oeminfo, but the actual contents of custom.bin are a single file path, so it shouldn't matter.
Click to expand...
Click to collapse
I see, I did something similar but ultimately I just went to C432 and now I am rather happy I did change it to C432. I am getting updates much sooner and I have no issues at all with this firmware.
Also, when I backed up my oeminfo and custom.bin using the SRK and then restoring it, this broke my P9, so I dont trust the backup feature of the SRK tool.
How would you add a custom.bin manually? I've bricked my phone, but I have the backed up oeminfo and custom.bin and root access via the terminal in twrp. I found out where to flash the oeminfo but not the custom.bin. Thanks in advance!
CanIHelp said:
How would you add a custom.bin manually? I've bricked my phone, but I have the backed up oeminfo and custom.bin and root access via the terminal in twrp. I found out where to flash the oeminfo but not the custom.bin. Thanks in advance!
Click to expand...
Click to collapse
I have same problem...
Did You found solution?
Hi all, would anyone be able to help me with the oeminfo and custom.bin files for a UK 02 phone. I tried to extract the one from the ROM but even though it says it flashes OK in TWRP when I load the full ROM it stays at c432. I am also assuming that the O2 rom is eva_l09c40. The only change is the Google Chrome default loader page is O2. Co.uk.
Any help much appreciated
Hi all, i know i have asked this before but can anyone help me get the custom.Bin and oeminfo for my p9 as, like a plank i didn't back then up before debranding.
I would be really grateful for any help.