i want to return to stock that matches my IMEI and that's the only vendor (VKY-L09C55) that does, i need the OEMinfo or at least where i can extract it because i couldn't find inside UPDATE.APP of B140 FullOTA-MF and B120 Fullota-MF-PV.
anything that can force the phone to stock would be ok with be that is VKY-L09C55
right now flashing VKY-L09C55 on VKY-L09C432 OEMinfo corrupts the thing and camera isn't installed and brand is something test key
thank you in advance
Related
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?
this might sound like a daft question but is there any way to use oeminfo.img from the update.app file? I need to rebrand my uk O2 phone which is currently at c432 and I did not take a backup of the oeminfo and custom.ini files before. The only one I can find is c02 which is Vodafone and not O2, I believe O2 is C40 which i have found the ROM.
Whilst I have extracted the file from update.app when I compare it to other rebranding OEMINFO files the compressed version is significantly larger even though the actual file size reports to be the same. When I flash it it does not change the rom code and I get a red,green, blue boot up screen before the splash screen.
Anyone have any ideas?
i'm not sure about that, but try to look for the huawei update extractor, get the any rom of the oeminfo you want to be on and extract the img.
Can a LLD-AL00 (C00) device be rebranded to a LLD-L31 device? I tried to search for it but didn't find any threads covering this.
Just start mess up with the phone so still have a locked boot but it can be fixed. So far, I just tried to flash the full-OTA update.app (C432B130) and it does not work, system img fails to load (well honestly I didn't expect it to but still had to try..)
Try LLD-L31C432B131 or LLD-L31C432B132 full ota's. Do not flash Al00 to a L31 it doesn't end well.
Sent from my LLD-L31 using Tapatalk
MSandstrom said:
Can a LLD-AL00 (C00) device be rebranded to a LLD-L31 device? I tried to search for it but didn't find any threads covering this.
Just start mess up with the phone so still have a locked boot but it can be fixed. So far, I just tried to flash the full-OTA update.app (C432B130) and it does not work, system img fails to load (well honestly I didn't expect it to but still had to try..)
Click to expand...
Click to collapse
Your phone's varient depends mainly on the motherboard inside so your phone might not work properly if you flash firmware of other varients. If you wanna go back to stock your best option is to flash the correct firmware using HuRupdater tool.
Hello I'm the proud owner of a VTR-L09 P10 with the oreo based VTR-L09 8.0.0.364(c530) firmware and an unlocked bootloader. I have tried many tutos across the internet but I still can't downgrade it to nougat in order for rebranding to VTR-29.
Can someone with matching conf or a close one who has succeeded in rebranding can help me with a working tuto.
Thanks in advance and....
HAPPY NEW YEAR !!!!
First, you twist nougat and Oreo. Your phone is on Oreo and you wanted to downgrade to Nougat.
I don't know, why the downgrade didn't work for you, but maybe now it does with the correct understanding of versions (nougat is the older one).
If you're a bit experiment friendly, you can try something for me - but I really can't guarantee you that this will work without brick!
You need an SD card for this, don't try it without!
- Download your desired firmware from Firmware Finder. I recommend 8.0.0.382 for L29-C432, which I installed on my rebranded P10 yesterday.
Here are the links:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2323/g1699/v202186/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L29_hw_eu/update_full_VTR-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
- Download my oeminfo file and put it on SD.
- Download and flash this TWRP. It will ask you for a password at boot, type your phone PIN.
- Backup your oeminfo with TWRP on SD AND internal memory, just to be sure.
- Now flash my oeminfo file with TWRP via Install/Use Image.
- Go to my guide and follow now Tutorial #2, Oreo to Oreo, exactly. You can use the TWRP version you already installed, but everything has to be like in the tutorial.
It should work, but, as I mentioned above, I can't guarantee it.
The worst thing which can happen is that you brick your firmware. For this, you should be able to reinstall an L09 firmware after restoring your oeminfo file via eRecovery.
But I think the recovery will stop installing L29 if it didn't work with the oemfile - if so, you just need to restore the oeminfo backup.
Don't boot into your L09 firmware with L29 oeminfo!
Jannomag said:
First, you twist nougat and Oreo. Your phone is on Oreo and you wanted to downgrade to Nougat.
I don't know, why the downgrade didn't work for you, but maybe now it does with the correct understanding of versions (nougat is the older one).
If you're a bit experiment friendly, you can try something for me - but I really can't guarantee you that this will work without brick!
You need an SD card for this, don't try it without!
- Download your desired firmware from Firmware Finder. I recommend 8.0.0.382 for L29-C432, which I installed on my rebranded P10 yesterday.
Here are the links:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2323/g1699/v202186/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...l/VTR-L29_hw_eu/update_full_VTR-L29_hw_eu.zip
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
- Download my oeminfo file and put it on SD.
- Download and flash this TWRP. It will ask you for a password at boot, type your phone PIN.
- Backup your oeminfo with TWRP on SD AND internal memory, just to be sure.
- Now flash my oeminfo file with TWRP via Install/Use Image.
- Go to my guide and follow now Tutorial #2, Oreo to Oreo, exactly. You can use the TWRP version you already installed, but everything has to be like in the tutorial.
It should work, but, as I mentioned above, I can't guarantee it.
The worst thing which can happen is that you brick your firmware. For this, you should be able to reinstall an L09 firmware after restoring your oeminfo file via eRecovery.
But I think the recovery will stop installing L29 if it didn't work with the oemfile - if so, you just need to restore the oeminfo backup.
Don't boot into your L09 firmware with L29 oeminfo!
Click to expand...
Click to collapse
Hello
I tried it and now I'm stuck in and endless reboot loop with only Huawei logo
Can you help me please ?
Did you do the factory reset via eRecovery?
The update with my script worked without any errors?