Related
Could someone upload the C636 oeminfo for L09 variant? Because I'm live in Australia, the L09 Single Sim version is the only available one officially.
I simply want to debrand the operator version of P9, to prevent any possible compatibility issue, I want convert it to the local stock variant. If someone can upload it, or PM me instead, that really appreciate.
Addition resources:
Firmware of EVA-L09C636B168
http;//update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v55680/f1/full/update.zip
Due to my post limitation, please change the ; to : after http to download the package.
hajuuk said:
Could someone upload the C636 oeminfo for L09 variant? Because I'm live in Australia, the L09 Single Sim version is the only available one officially.
I simply want to debrand the operator version of P9, to prevent any possible compatibility issue, I want convert it to the local stock variant. If someone can upload it, or PM me instead, that really appreciate.
Addition resources:
Firmware of EVA-L09C636B168
http;//update.hicloud.com:8180/TDS/data/files/p3/s15/G1079/g104/v55680/f1/full/update.zip
Due to my post limitation, please change the ; to : after http to download the package.
Click to expand...
Click to collapse
I think SRK tool has it now: [TOOL] SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility (STABLE - 20160717)
Milamber said:
I think SRK tool has it now: [TOOL] SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility (STABLE - 20160717)
Click to expand...
Click to collapse
Actually, Not.
The version of SRK tool is EVA-L19C636 not EVA-L09C636, which is for Dual SIM Edition of P9 not Single SIM Edition.
EVA-L09 Single SIM (with NFC) 3G/32G
EVA-L19 Dual SIM (without NFC) 3G/32G
EVA-L29 Dual SIM (without NFC) 4G/64G
hajuuk said:
Actually, Not.
The version of SRK tool is EVA-L19C636 not EVA-L09C636, which is for Dual SIM Edition of P9 not Single SIM Edition.
EVA-L09 Single SIM (with NFC) 3G/32G
EVA-L19 Dual SIM (without NFC) 3G/32G
EVA-L29 Dual SIM (without NFC) 4G/64G
Click to expand...
Click to collapse
It's the same oeminfo.
Mostar088 said:
It's the same oeminfo.
Click to expand...
Click to collapse
Can I use that oeminfo for my EVA-AL10? Because I want to flash to EVA-AL29.
Mostar088 said:
It's the same oeminfo.
Click to expand...
Click to collapse
I think you may be right, but when the L09 is changed to L19, OTA updates don't work. I think that's the OP's issue.
I used SRKtool to convert mine, and that's what happened.
Until it has an update to include L09C636, or someone can upload that oeminfo, the best bet is to convert to EU. You can then get OTAs until you unlock, re-root, etc. and still be totally de-branded. This is where I am currently.
Hope this helps!
Here you go - stock L09C636 oeminfo from Australia, backed up before I switched to C432 (because I thought it might get Nougat sooner hmm...)
TommyGEB said:
Can I use that oeminfo for my EVA-AL10? Because I want to flash to EVA-AL29.
Click to expand...
Click to collapse
Hi,
any luck with getting oeminfo for EVA-AL29? I am looking to reflash my AL10 over to AL29 too.
Thanks.
azgooon said:
Hi,
any luck with getting oeminfo for EVA-AL29? I am looking to reflash my AL10 over to AL29 too.
Thanks.
Click to expand...
Click to collapse
U have oeminfo for L29 in SrkTool.
Sent from my VIE-L29 using XDA Labs
Mostar088 said:
U have oeminfo for L29 in SrkTool.
Sent from my VIE-L29 using XDA Labs
Click to expand...
Click to collapse
Thanks for your quick response, yes, I have seen oeminfos in SrkTool but they are for:
1. Change to oeminfo and custom.bin - cn (AL10) - my current oeminfo
2. Change to oeminfo and custom.bin - eu (L09C432) - 32GB version only
3. Change to oeminfo and custom.bin - meafnaf(L19C185) - 32GB version only (dual sim)
4. Change to oeminfo and custom.bin - asia (L19C636) - 32GB version only (dual sim)
or alternatively for P9 Plus i can see 4 options for VIE series:
1. Change to oeminfo and custom.bin - cn (AL10)
2. Change to oeminfo and custom.bin - eu (L09C432) - 64GB single sim
3. Change to oeminfo and custom.bin - meafnaf(L29-C185) -
4. Change to oeminfo and custom.bin - asia (L29C636)
which I am worries may cause some incompatibilities issues?
Or do i get it wrong in my head and oeminfo is one think but then i can set the actual model in build.prop?
Thanks.
azgooon said:
Hi,
any luck with getting oeminfo for EVA-AL29? I am looking to reflash my AL10 over to AL29 too.
Thanks.
Click to expand...
Click to collapse
Sorry that I made a mistake. It should be EVA-L29.
And still, haven't found the oeminfo for L29 yet..
I'm not sure if I could try the oeminfo of L09.. I don't want take the high chance to brick my phone :s
TommyGEB said:
Sorry that I made a mistake. It should be EVA-L29.
And still, haven't found the oeminfo for L29 yet..
I'm not sure if I could try the oeminfo of L09.. I don't want take the high chance to brick my phone :s
Click to expand...
Click to collapse
Hi,
No, sadly I couldn't find anyone with that oeminfo I even emailed droidth but he responded 8h ago saying that he doesn't have EVA-L29 oeminfo and custom.
I have therefore decided to rebrand EVA-AL10 to EVA-L09.. I was worried that it will not detect all 4GB of memory and internal storage will be shrinked however down to 32GB... good news, this is not the case!
I will however create a seperate thread to see if there is anyone with EVA-L29 who will be keen to download custom and oeminfo for us...
Let's keep fingers crossed.
Regards.
Tom.
azgooon said:
Hi,
No, sadly I couldn't find anyone with that oeminfo I even emailed droidth but he responded 8h ago saying that he doesn't have EVA-L29 oeminfo and custom.
I have therefore decided to rebrand EVA-AL10 to EVA-L09.. I was worried that it will not detect all 4GB of memory and internal storage will be shrinked however down to 32GB... good news, this is not the case!
I will however create a seperate thread to see if there is anyone with EVA-L29 who will be keen to download custom and oeminfo for us...
Let's keep fingers crossed.
Regards.
Tom.
Click to expand...
Click to collapse
Hi, when you debrand EVA-AL10 to L09, could you manage dual sim (i.e set default sim for call and defalt for data?)
I stuck on AL-10 with some issues, especially to GG services and apps, then I hope I could change it to EU version.
Thanks for your experiences.
azgooon said:
Hi,
No, sadly I couldn't find anyone with that oeminfo I even emailed droidth but he responded 8h ago saying that he doesn't have EVA-L29 oeminfo and custom.
I have therefore decided to rebrand EVA-AL10 to EVA-L09.. I was worried that it will not detect all 4GB of memory and internal storage will be shrinked however down to 32GB... good news, this is not the case!
I will however create a seperate thread to see if there is anyone with EVA-L29 who will be keen to download custom and oeminfo for us...
Let's keep fingers crossed.
Regards.
Tom.
Click to expand...
Click to collapse
Hi, is there any issues with rebranding EVA-AL10 to EVA-L09? If itś fine, Iĺl give a try too.
Hello! Did stupid thing, changed oeminfo from L19 to L09, and didnt create backup.
Can someone, who using EVA-L19C432B161 or b182, and who are rooted his phone, create oeminfo backup file with SRK Tools (here , and put files here? Please, it wulda be nice, if i culda change it back from l09 to l19
how backup it?
Open srk, conect phone, in skr chose 5 option Backup
Then 1 oeminfo and 2 custom.bin
thease files will be in "Restore-oeminfo-custombin" folder at SRK tools folder..
ok, dont need anymore.. Find it in this site. Used custom.bin what was in SRK Tools and this file, worked as planed
Oeminfo and custom.bin from EVA-L19:
https://uloz.to/!KaCfQNJ9SJ36/oeminfo-eva-l19-zip
hello, did you know debrand from L09 to L19? If so, how would you guide me?
Arnys said:
Hello! Did stupid thing, changed oeminfo from L19 to L09, and didnt create backup.
Can someone, who using EVA-L19C432B161 or b182, and who are rooted his phone, create oeminfo backup file with SRK Tools (here , and put files here? Please, it wulda be nice, if i culda change it back from l09 to l19
how backup it?
Open srk, conect phone, in skr chose 5 option Backup
Then 1 oeminfo and 2 custom.bin
thease files will be in "Restore-oeminfo-custombin" folder at SRK tools folder..
ok, dont need anymore.. Find it in this site. Used custom.bin what was in SRK Tools and this file, worked as planed
Click to expand...
Click to collapse
cuchuoizanh said:
hello, did you know debrand from L09 to L19? If so, how would you guide me?
Click to expand...
Click to collapse
if i remember correct, you need to be on marshmalow, android 6, then you can do it with srk tools
but before somthing change, create backup..
Arnys said:
if i remember correct, you need to be on marshmalow, android 6, then you can do it with srk tools
but before somthing change, create backup..
Click to expand...
Click to collapse
Can you be more specific? I'm in mm. Do you need to flash oeminfo through twrp before? please help
cuchuoizanh said:
Can you be more specific? I'm in mm. Do you need to flash oeminfo through twrp before? please help
Click to expand...
Click to collapse
i dont know how debrand from L09 to L19, my phone alredy are L19.
you need custom.bin and oeminfo from l19 marshmalow, i got nuget b398, and cant help you.
you can download it - hanniSK gived link.
downlod srk tools, copy downloaded files to srk tools forlder Restore-oeminfo-custombin, open srk tools ,go restore, and restore thease files, then,download eve-l19c432b161 or any other C, depends what you want, and with dload method upload it .. maybe i will mising somthing, i dont know, but if you will not use dc phoenix what cost 15€, i cant help you, because all thease things i did when was bricekd hard my phone, and with 72 hours I played with phone, to see what i can, and cant!
cuchuoizanh said:
hello, did you know debrand from L09 to L19? If so, how would you guide me?
Click to expand...
Click to collapse
Look at this thread
https://forum.xda-developers.com/showpost.php?p=75418876&postcount=8
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 Guys,
is it possible to rebrand from VTR-L29 to VTR-AL00?
Let me know
Thank you in advance
Yes
---------- Post added at 10:26 AM ---------- Previous post was at 10:25 AM ----------
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
It's possible, but you need to find the oeminfo for VTR-AL00 and the correct firmware.
With this files you can follow the tutorials for rebranding here on xda.
Jannomag said:
It's possible, but you need to find the oeminfo for VTR-AL00 and the correct firmware.
With this files you can follow the tutorials for rebranding here on xda.
Click to expand...
Click to collapse
yes, the problem is where to find oeminfo of VTR-AL00
Does anyone has oeminfo of VTR-AL00?
yangsong2000 said:
yes, the problem is where to find oeminfo of VTR-AL00
Does anyone has oeminfo of VTR-AL00?
Click to expand...
Click to collapse
The thing is, that AL00 is a special chinese model. May I ask, why you want to rebrand to VTR-AL00?
VTR-L29C636 is the generic Asian version and should be better for you than VTR-AL00.
You need to find someone with an VTR-AL00 and installed TWRP. Inside TWRP this person can make a backup of the oeminfo partition and give it to you. After this, you have to restore his backup on your phone, than you should be able to install via Huawei Recovery or HWOTA (with rewritten script, because HWOTA doesn't support AL00 officially).
Jannomag said:
The thing is, that AL00 is a special chinese model. May I ask, why you want to rebrand to VTR-AL00?
VTR-L29C636 is the generic Asian version and should be better for you than VTR-AL00.
You need to find someone with an VTR-AL00 and installed TWRP. Inside TWRP this person can make a backup of the oeminfo partition and give it to you. After this, you have to restore his backup on your phone, than you should be able to install via Huawei Recovery or HWOTA (with rewritten script, because HWOTA doesn't support AL00 officially).
Click to expand...
Click to collapse
I want to use the Chinese version because it has more features and the updates are more frequent. I tried to look for VTR-AL00 oem info in internet but nothing... can't find it
If you have it or know how to find it (actually I don't know anyone who has P10 VTR-AL00), please let me know!
yangsong2000 said:
I want to use the Chinese version because it has more features and the updates are more frequent. I tried to look for VTR-AL00 oem info in internet but nothing... can't find it
If you have it or know how to find it (actually I don't know anyone who has P10 VTR-AL00), please let me know!
Click to expand...
Click to collapse
I got one AL00, but I have a problem on getting TWRP installed.
When I go into the developer mode, there is no "OEM unlocking" toggle to open.
whaledandan said:
I got one AL00, but I have a problem on getting TWRP installed.
When I go into the developer mode, there is no "OEM unlocking" toggle to open.
Click to expand...
Click to collapse
As far as i know, you just have to enable usb debugging on developper mode.
Then you can root and install twrp following guide.
If you succeed, dont forget to backup your al00 oem info for me
If you need any help, just ask me
deffernt betwen VTR-L29 & VTR-AL00 Google Service (Ply store,chrome,etc) if you in Oreo just flash with vtr-al00 Oreo firmware all be OK
Hello xda folks, actually my question is not about how to root or bad oeminfo or etc, actually, the question is this;: does our P10 has DRM keys?
second one, after unlocking my bootloader, i did a twrp backup of all partitions, system,data,oeminfo,cust,boot,etc, but while i was rebranding at first i did some steps really bad and i finished with a ONYX D88, then reading again i fixed and now i have the precious and delightfull L29 , but the real question is, what if i want to rebrand to my original VTR-L09C25 (this one is Latin America PERU ) and flash the original rom(btw i cant find it anywhere) and i tried to restore it via TWRP and didnt work, is there something im missing?
BTW: im not trying to go back, just in case who knows, warranty , thanks in advances dear xda folks <3