yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

yup the steps are right so far, with the addition that u need to change the custom.bin also. It contains the "region", u can extract it from the oeminfo, after u are done with the changes.

-

About the edits, for the build change u need to modify:

ID: 18 (region) should be currently something like: [B]vodafone/de[/B] must be [B]hw/eu[/B]
ID: 97 (model) should be [B]WAS-LX1A[/B] must be [B]WAS-L21A[/B] for dual-SIM

ID: 78 (build) should be [B]WAS-LX1AC02BXXX[/B] must be for example [B]WAS-LX1AC432B160[/B]
ID: 101 (last build) should be [B]WAS-LX1AC02BXXX[/B] must be for example [B]WAS-LX1AC432B130[/B]
ID: 68 (rescue) should be [B]WAS-LX1AC02BXXX[/B] must be for example [B]WAS-LX1AC432B130[/B]

ID: 166 (OTA-Token) if present, it should be deleted/formatted on an MM build. The N builds will add it again but with a different token

And very important, u should keep an eye on the "length" of the changes... Because, if u change for example C02 to C432 u need to align this parameter in the head of the oeminfo entry. (For a deeper explain have a look at the "How-To.txt" beside the OEMInfo-Tools.)

If u need some help, just send me a PM via Telegram at "k1ll3r8e".

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] danmrak:
Oeminfo version

Hello, is there a way to see which oeminfo version is installed in the phone with the toolkit?
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

nope, the only way to get the info's u're looking for, is, to get an backup of the oeminfo. This u can do with the toolkit "Dual-/Single-SIM -> Export", after that u can open the file with the OEMInfo-Tools (can be found a few posts ago).

Hope i could help u ;)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] danmrak:
Thank you very much for your reply! I have one more question: my phone is currently c150b367 but it is installed via firmware finder. I want to downgrade to MM and then update to c432 Nogat so I can get OTA updates. My question is: at which point do i need to to upload the c432 oeminfo : before or after installing downgrade firmware (one with ndrm90 test keys) I understand that downgrade firmware is midpoint before MM instalation but order of oemimfo flashing is confusing me.

This was a lenghty post but I hope I didn't took too much of your time..
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] tw1st3d83:
You flash oeminfo and custom bin first then corresponding system.

So if you flash for example b160c432 your update.app in dload folder must be b160c432.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] danmrak:
Thanks for your explanation!
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
OEMInfo-Tools 0.0.0.12

Heyho,

here is the new version of my OEMInfo-Tools.

-

From now on, i'll only share the link to my gdrive, where all the previous and upcoming versions are stored. The same archive can be found on my FTP, links to this are in the 1st post.

-

The new version has the following abilities:

* New context-menu entry "Open in HEX-View" which will open the oeminfo in the editor and scroll to the desired position.

* HEX-Editor - The viewer is now an editor.

* A HEX/Ansi search function and a "Found-List" with jump support.

G-Drive: Download

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
Hi Sebastian,

I can successfully backup and restore the original vodafone oeminfo on my DE P10 Lite.

I modified my original oeminfo with your tool and i see the file is the same as the oeminfo eu dsim that is posted in one of the forums.

However, when TWRP is used to restore the modified oeminfo, i see the "Build number" in the about box is "NRD90M test-keys" which happens to be in the directory name of TWRP gives to the backup.

I have tried all ways to try and get WAS-LX1AC432B182 to install, but with 3 button method for example, it comes up with the error after "installing update" straight away with "software install failed".
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] vovan1982:
Thank you for the new release.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
Hi Sebastian,

The original build I had on the phone after last OTA was WAS-LX1AC02B137.

- I put TWRP on and did full backup before anything else.

- I modified oeminfo with your tool for WAS-LX1AC432B182 , and put back oeminfo per my post above.

- this is where the problem starts (i believe)

* i used hauwei extractor to get the recovery.img for the build i wanted to flash

* the file is extracted but when flashed, doesn't boot into recovery.

(the phone continues to boot normally with WAS-LX1AC02B137 but no software update option. shows 0 as 2nd IMEI and dual sim menu enabled)

* i re-flashed twrp and restored the backup (phone working as purchased except with twrp as recovery)

- i used the file downloaded from one of the other threads. WAS-LX1AC432B182_DS_4G_oeminfo.zip

(i checked it with oemtool and it is the same as the one i created based on your instructions)

- once again i flashed the recovery.img from WAS-LX1AC432B182

- got same results as the first round, then decided to go back to the original version completely and really f.cked up.

- I extracted the recovery.img from WAS-LX1AC02B137

* same thing, doesn't boot into recovery

* then i did something really dumb, and flashed the boot, system and cust.img files (and erased the data)

* phone was completely bricked and just kept in the repeat trying to boot

* i managed get twrp back on and restored the original backup but the phone is like a raw android without any huawei/vodafone screen settings / apps / screens

Importantly, at every stage i tried both the *#*#... to initiate the sdcard/dload update which forces a reboot into the process of volup+voldwn+power.

in either case i got software installed failed or stuck at 5% for the forced mode. (i am guessing this is because the recovery.img is no good)

also the eRecovery completely fails as well this was throughout the process i checked it.

so current status is,

it has the last OTA version WAS-LX1AC02B137 with TWRP as loader.

phone can function as basic phone but has no EMUI, Vodafone customisations.

Thanks for your support/time
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] tw1st3d83:
If you want to get all Vodafone garbage back, just download full was-lx1ac02b137 system (I'm guessing that's around 2gb or more), put update.app in dload folder on your sd card and do a 3-button method to reinstall that system. It will put back all missing files and apps and lock your bootloader again.

Then you can try all steps for changing oeminfo (changing region) again. Changing region is like debranding your device so you will loose all Vodafone apps and bloatware and you will have pure EMUI on your device.

I didn't understand why you flashed old OEMinfo back after you successfully got c432 build on your device?
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
you misunderstand. i did not get c432 on there. 3-button method (forced and normal) does NOT work with any firmware using dload folder. eRecovery also does NOT work.

I am currently stuck with vodafone TWRP restore, but something is still wrong because not all screens, apps, EMUI are restored. It is like plain android
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] tw1st3d83:
Oh, now i think i get it. You have installed c432 oeminfo but system you restored is from old oeminfo. So now you need to download MM build of c432, do a 3-button method with it (im pretty sure that it will work this time) and later update to latest Nougat build. If OTA doesn't work, use Firmware Finder.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

hmm that sounds really strange...

-

Maybe it's a problem with that specific version... Try the WAS-L21AC432B130 it's a pretty old version maybe this will install fine. On my L31 the B370 ++ build can't be flashed via dload u have to trick the updater since that version with an modified zip archive.

-

About the problems to boot into the recovery... That's normally a problem based on different operating system... For example: On L31 u can't flash a recovery from MM on N and also not from N on MM... The recovery can't boot in that case.

-

About the erecovery, well, for me it never worked to restore anything...

-

About the oeminfo, if u flash the oeminfo via TWRP and u boot back into the system to call "*#*#..." u write the old entry back to the oeminfo... In short, all build changes are normally wiped after an boot... Because the system will write the last build into the entry. So u have to flash the oeminfo and DIRECTLY after that u must flash the update.app.

-

About the 5% prob., are u sure that there was no cable connected during the flash?

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
you still don't get it my friend.

a) i use matching oeminfo i.e. original vf oeminfo + WAS-LX1AC02B137

b) i use matching WAS-LX1AC432B182_DS_4G_oeminfo + WAS-LX1AC432B182

the point is sdcard\dload and erecovery do not work at all any more after flashing bad recovery.img from hauwei update extractor tool.

I can restore original vodafone backup from twrp but this does not include the recovery image.

I can't go forward or backwards at this moment.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

u also restored on any try the matching custom.bin?

Because the custom.bin contains a folder link... the "hw/eu" or "vodafone/de" part... without the correct custom.bin the system will always try to load the wrong localisation. (Like any stock apps, which would explain why u have no apps on ur vodafone restore.)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
Hi Sebastian,

I modified my original vf oeminfo WAS-LX1AC02B137 to be WAS-LX1AC02B132, so it is showing this for last build, build and rescue. original showed 137 for last build and build and 132 for rescue.

I use twrp to restore but and

- about phone - build number still shows as was-lx1ac02b137

- system update - current version shows as was-lx1ac02b137

I also notice in the original oeimfo file

s1-18 = vodafone/default

s2-18 = vodafone/de

s1-68 = rescue:WAS-LX1AC02B132

s1-78 = WAS-LX1AC02B137

s1-s91 = WAS-LX1A

s1-101 = WAS-LX1AC02B137

s2-101 = WAS-LX1AC02B133

s1-111 = WAS-LX1AC02B137

s2-111 = WAS-LX1AC02B133

s1-166 & s2-166 tokens are different

two things;

About the 5% prob., are u sure that there was no cable connected during the flash? - are you saying it should or should not have cable?

So u have to flash the oeminfo and DIRECTLY after that u must flash the update.app. - how can you flash update.app without rebooting?
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

yup that's what i mentioned in my earlier posts, while the system boots up, it writes the "current" values from the "build.prop" in the "cust" mount back to oeminfo. That's exactly what happens ;)

-

Let me explain:

U restored ur old build + oeminfo but not the custom.bin, right?

Because, s1-18 = vodafone/default, has been changed to "default", that's because the system couldn't mount the "hw/eu" folder, so the fallback was "vodafone/default".

This, s2-18 = vodafone/de, is the backup of the old section 1.

This, s1-68 = rescue:WAS-LX1AC02B132, gets so far i know, only changed during build install.

The following values have been changed during boot...

s1-78 = WAS-LX1AC02B137

s1-s91 = WAS-LX1A <- (here i'm not sure, if it got changed from L21A to LX1A, then it's based on some checks in the vodafone FW)

s1-101 = WAS-LX1AC02B137

s2-101 = WAS-LX1AC02B133 <- (backup of old section 1)

s1-111 = WAS-LX1AC02B137

s2-111 = WAS-LX1AC02B133 <- (backup of old section 1)

The changes on s1-166 & s2-166 are made, so far i could see, after an successful update and sometimes after an "update check".

-

About how to flash the update.app without "reboot", normally with an working recovery, u do the following things:

1) copy the update.app to [internal storage/dload] - the dload folder on the sd-card u have to delete/rename

2) flash the oeminfo

2.1) in rooted android

2.2) or twrp

3) turn the device off

4) with connected cable, hold [Vol-] to boot into fastboot

5) flash the stock recovery

6) turn the device off - holding [power] until it shuts off

7) !IMMEDIATELY! after the screen turns black and u hear the usb-DC sound, disconnect the cable, and start pressing [Vol+ Vol- Power] to start the update mode

8) wait until it's done

Hope i could help u ;)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
Hey there, thanks for all the support.

for 1st step, i would like to restore the default build to prove the process is working. then i would have another go at changing to 432.

made the oeminfo s1 to equal s2 i.e. B133

In engineering mode, vendor country info shows as vodafone, de - so matches oeminfo (this is the custom.bin right)

followed your instructions to the t, but still get software install failed.

i will try to do the 432 again, but how to restore the custom.bin please?

thanks again
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

the info can be found in the 2cd post [Q:4]...

-

The custom.bin is stored under "/data/custom.bin".

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
So i figured out you can copy the custom.bin via twrp (and set chmod 777).

I did that and followed your instructions to the letter, but she still refused to load from either the internal sdcard/dload or external sdcard/dload

interestingly though, after failing that. the unit automatically does a factory reset.

The About Build Number shows: NRD90M test-keys

Dual SIM settings are visible

no Software Update appears

Engineering Vendor shows hw, eu

Engineering Veneer Info Version info shows Parameter Version C432 & EMUI solution B115

IMEI 2 shows 00000

I was using WAS-LX1AC432B182 FullOTA firmware, but then i downloaded the service firmware from the link enclosed

https://xdaforums.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097

boom....she works like a charm and gave me back all the huawei screens, groups, etc i had lost.

I got the 2nd IMEI number from hauwei who confirmed the phone had two numbers based on the primary i gave them.

The only thing left now is to set the 2nd IMEI number to the one HW gave me.

Do you know how to do that please?

Thanks for staying with me on this Sebastian. It helped me to narrow the issue down.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

sounds great! ;)

-

About the IMEI change, i personally never needed to add/edit the IMEI's... So i can't help u at this point, the only thing i know is, that if the 2cd IMEI is 16x0 it's also changed in the modem settings... And for this u need AT commands to communicate with the modem. This is also a really easy way to fully brick the device, because via AT commands u speak directly to the HW of the device. (That's also the reason why i never wrote a tool for this nor tested different commands on my device, because i haven't a 2cd one :p)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] gwaitsi:
I think there are some other particularities using this method;

- IMEI2 = 0

- SIM2 shows the Tele # of SIM1 (dual sim menu)

- engineering menu other info does not show any IMEI numbers (or title)

I don't know if these have any effect, the SIM2 concerns me. SIM1 = DE and SIM2 = CZ - so this is funny that SIM2 shows a DE number

I use this config to avoid int'l call costs..as this is a loop hole in the EU.

- If you roam in CZ and call DE on DE SIM = DE call cost

- if you stay in DE and call CZ on DE SIM = Intl call cost

use

- CZ SIM in DE to call CZ = CZ call cost

- DE SIM in DE to call DE = DE call cost

- DE SIM in CZ to call DE = CZ call cost

I was paying a fortune in int'l call costs, which is why i am sure they close down the 2nd SIM
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

hehe sound really nice ;)

-

But back to ur problem, well, have a look at this thread, there is explained how u can try to restore ur IMEI, seems that u need the "HCU Client".

Hope the link helps u solve ur problem.

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
Hi,

I have a VNS-L31 in C109B350... What is my first step to make it to dual sim?

In the Toolkit, "Dual-/Single- SIM" tab, and "Firmware-Update", I copied the L31C432B161 to the sd card, but I get "Software install failed".

Thanks.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

u need to:

1) unlock the bootloader

2) flash the TWRP

3) root the device

4) flash the oeminfo + custom.bin (L31C432B160)

5) copy the update.app to [internal storage/dload] (L31C432B160)

6) flash the stock recovery (From ur current build or similar, if u are currently on N u need a N stock recovery)

7) proceed with the update - turn the device off, DC the cable, press and hold [Vol+ Vol- Power]

8) wait until the update is done

9) update back to N

Hope i could help u ;)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
Many thanks for your quick answer!

You mean L31C432B161 (instead of L31C432B160)?
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

it doesn't matter, u can flash both, the dual-SIM is based on the oeminfo u flash, not on the build. I only mentioned the B160 because it's the most used build to downgrade to MM. ;)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
The bootloader is unlocked (sure of that), but fastboot gives "Command not allowed" when I try to flash TWRP...

By the way, which one should I use (I tried the one in your toolkit and TWRP 3.1.1)?

---------- Post added at 05:16 PM ---------- Previous post was at 04:57 PM ----------

The "FASTBOOT&RESCUE MODE" screen says:

PHONE Unlocked <--- bootloader unlock, right?

FRP Lock <--- what is that?
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

that looks like an "relocked" bootloader^^ - It's the "OEM-Unlock"... Have a look on the "Toolkit -> Help" there is everything explained with images.

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
Hi,

I finally succeed in getting to the end of the procedure, but after "update back to N", I have now build number= "NRD90M test-keys"...

Do you have an idea why?

Thanks.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
Hi!

I did the procedure one more: I am back again with EMUI 4.1.1 (L31-C432B161).

Now, I would like to upgrade to Nougat, but I fear to end with build number= "NRD90M test-keys"... I did not the system update.

Do you know how I should upgrade to Nougat? dload folder in sdcard? with which update.app?

Thanks.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] vovan1982:
I know how to upgrade. Will Download Firmware Finder, will select the model and will send the update.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
I know how to do it too... But this is the third time my p9 lite ends in "NRD90M test-keys"...

I tried with system update, Firmware Finder...
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

seems that u install the update to N via dload, right?

THATS WRONG, u must as mentioned "send it to the updater" with the proxy method, then the system updater will download the file and install all files not only the 1st update.app...

But all this u would know if u would use the search... Because here are 1251 posts... And nearly each 10th explain this way...

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
Hello

First time, update was done using the system, like a normal update, and the 2th and 3rd time I used Firware Finder with the proxy...

Same result.
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

did u restored each time the oeminfo?

That the device showed for example "L31C432B160" under "About Phone"?

And is the custom.bin content in this case "hw/eu"?

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] micphil:
Thanks for wanting to help me, and for the help you already provided me.

But right now I have a working p9 lite (with Android 6..., but working nevertheless) dual sim (which is the most important for me).

So I think I am leaving it like that (until I have a new phone...).
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
OEMInfo-Tools 0.0.0.13

Heyho,

here is the new build of my OEMInfo-Tools. It includes:

* Search Case-In-/Sensitive for the "Ansi" mode - THX for the idea and translations goes to [MENTION=8420391]vovan1982[/MENTION]

* A few UI tweaks

Download: G-Drive

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] drew_peacock:
So my p9 lite has been giving me (massive) upgrade problems...spent many night on trying to upgrade to Nougat - each time results in EMUI reporting "Software Failed - incompatibility".

So I found this thread & thought I'd solved the problem (my phone had no custom bin, nor oeminfo) - ran this tool to correct (went through the whole sequence - including downloading the firmware from the URLS provided in the tool - no errors), but afterwards when I check via DC Unlocker's HCU tool is shows that my phone thinks it's still on C900 (not C432), here's HCU's output from reading my phone...

Firmware ver.: VNS-C900B161

Vendor: hw

Country: eu

FASTBOOT:Dallas-Trunk_FASTBOOT

BOOT:Dallas-Trunk_BOOT

RECOVERY: (unknow)

SYSTEM: VNS-L31C900B161_SYSTEM

MAINVER: VNS-C900B161

DATAVER: (unknow)

APTIME: Wed Nov 9 18:30:14 CST 2016

CUSTTIME: Wed Nov 9 19:36:24 CST 2016

I reckon the above is why when I come to upgrade to L31C432B371 I get the incompatibility error?

Any ideas?
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] k1ll3r8e:
Heyho,

i can't check my current setup with HCU because i have no account for this, so i can't tell u which values should be shown.

-

What does the system shows under "About Phone"?

-

Have u tried to update in the correct order? Like B160, B210, etc.?

Because, normally, if u flash the oeminfo + custom.bin from the C432B160 and flash the update.app afterwards, u should be on "LxxC432B160". From this build u can then use the offered updates via "Settings -> Update", or try the manual way with "Firmware Finder". If u try it with FF, u should always use the proxy method and do the updates gradually... Not from for example B160 to B380... The only N build i know u can flash directly on B160 is the B370 MF-PV... But this is more like a beta version and i got never a update working on this particular build... (Only with modified zip's via TWRP)

Regards,

Sebastian
[Huawei P9 Lite ROMs, Kernels, Recoveries, & Other ] drew_peacock:
Thanks Sebastian ...my phone actuallt shows VNS-L31C432B161 (which is what I want it to be), but like I say, whenever I try to upgrade to VNS-L31C432B161 EMUI report Software failed - incompatibility ...this is what led me to HCU, which reports the information as per my last post. Incidentally, it is free to have HCU read your phone (you just have to put your phone into USB Maintenance mode & HCU will talk to it & pull information from it)

I've spent several nights trying upgrades in teh correct sequence...very frustrating. Albeit I've only used your tool once, then upgraded in sequence...only for the most important on (to B371) to fail :(

I have had great difficulties with Firmware finder...when I first used it, I selected the wrong version ...& I ended up with the NRD90M test - keys ...now everytime I rebuild my phone that NRD90M test - keys version finds its way into my updater ...I have absolutely no idea how or why it keeps getting back into my updater after me going through the build sequence B131, B161...but as soon as I give the updater access rights in my phone ...it says that B371 is available...but if I install that version I end up with NRD90M test - keys ...it's driving me potty!