Database Users

How to get the unlock codes if you have JPC rom

Download the normal unlock files before you do anything!!! You can find them in the forum.
KIES needs to be off...
1 - You need your phoned to be rooted
2 - Put your phone in usb debug mode
3 - Plug in the usb cable (don't use kies or storage mode)
4 - In the run window type CMD
5 - Go to the folder where you extracted the unlock files. Example c:\Generate Unlock Windows\Generate Unlock Windows
Type dir , you should see a file called adb.exe
6 - Type adb kill-server
Type adb shell
Type su (on your phone you should see the root explorer asking if you want to allow access, choose yes xD duh)
Type cp /efs/nv_data.bak /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak /sdcard
Type cp /efs/nv_data.bak.md5 /sdcard !!!IF this doesn't work type this!!!!----> cp /efs/.nv_data.bak.md5 /sdcard
7 - Closed the window.
8 - The file with the code is now on your sdcard, start storage mode and copy the files to the c:\Generate Unlock Windows\Generate Unlock Windows folder (in windows xD)
Be sure that the nv_data.bak and nv_data.bak.md5 are in the same folder as sgux.exe
9 - Edit the Generate_Code.bat
Delete all the code and paste this:
@echo off
cls
echo ===============================================================
echo ===============================================================
echo Generate unlock code for any Samsung Galaxy S
echo ===============================================================
echo ===============================================================
echo Extract code
.\sgux .\.nv_data.bak
.\sgux .\nv_data.bak
echo ===============================================================
echo ===============================================================
echo Please donate to DagentooBoy for the script
echo Please donate to rbnet.it and marcopon for the SGUX utility used in the script
echo ===============================================================
echo ===============================================================
echo Script complete!
pause
10 - Your codes should appear! Save them and send them to you gmail account so you have them for life!
I TAKE NO CREDIT FOR THIS!!!! Just want to help!

Can you please Help me?
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000

I've tried to get the code with : .nv_data.bak, nv_data.bin, nv_jpc and bml3.bak. In each case, I got the code 00000000.

I found this in a forum hope this will help

quiron said:
I flash & reflash several times, and still can´t resolve this.
I don't have any file with *bak* at this moment.
the files that I have:
# find /efs
find /efs
/efs
/efs/.android
/efs/.android/testAndroid1.bin
/efs/.android/testAndroid2.bin
/efs/.android/testAndroid3.bin
/efs/nv_data.bin
/efs/.imei
/efs/imei
/efs/imei/mps_code.dat
/efs/imei/bt.txt
/efs/imei/.nvmac.info
/efs/nv_data.bin.md5
/efs/.nv_state
/efs/nv_data.jpc
/efs/nv_data.jpc.md5
and de result to nv_data.bin:
E:\Generate Unlock Windows>sgux2 nv_data.bin
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.bin>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>sgux2 nv_data.jpc
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <nv_data.jpc>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
Click to expand...
Click to collapse
same result here, followed the procedure, ended up with network code 00000000. any help?

If you need help on unlocking a 2.2 device. Please contact me.

can anybody post a link to which normal unlock files are needed, there are too many unlock files in the forum

rhcp0112345 said:
If you need help on unlocking a 2.2 device. Please contact me.
Click to expand...
Click to collapse
Yes I need it, and I am certainly not the only one.
Can you publish a guide how to proceed ?

I did manage to get rid of this bloody unlocking problem after 9 hours of struggle. I followed the advice here:
http://forum.xda-developers.com/showthread.php?p=7946031#post7946031
I don't know how it worked, I don't care how it worked, its just that now i have a full working sgs with jp3 froyo software installed.
Next rom will definitely be official froyo, no more flic-flacs for me till then.

Fallback after a KOR productcode modification by firmware JPC
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...

gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!

It also means that a simlocked phone can be used with another SIM by modifying the same way the nv_data.bin...
Anyway I wont update this phone to JPC. I'll await the next one... JPD seems to be online but no infos yet on the status of this firmware.

in which line did you find the KOR?
i cant find it? >_<

Greg82uk said:
You sir are brilliant... back to O2U here! ) I only needed to change one key entry as could find only the one KOR in my nv_data.bin... but otherwise... perfect! )
Thank you SOOOO much... had started worrying that I'd not get my product code back!
Click to expand...
Click to collapse
I'm clueless here, would you mind posting a step by step including the software used?

gouroufr2000 said:
I've found a solution to my KOR problem after a JPC firmware upgrade :
History:
I've upgraded my SGS to JPC firmware (2.2). My phone product code has been changed to GT-I9000HKDKOR. Since my phone is simlocked, my local SIM (SFR in France) is not the same model than the phone (KOR), so it asked me an unlock code. I found no code to remove the simlock protection (sgux computed a 00000000 unlock code).
Solution I found :
- Downgrade the SGS to the firmware JM6 (2.1).
- Downloade the file /efs/nv_data.bin to your PC/LINUX/MAC (your phone need to be rooted !).
- Open it in a hexeditor -in fact I've used Windows' notepad++- and search for the "KOR" sequence. This sequence appears 2 times in the bin file. These are nearby each others.
- Change back the KOR sequence to your original product code (this can be found in regedit CURRENT USER / Software / Samsung / Kies / DeviceDB / [a number] / ProductCode). For my personal case, it is a SFR (France) phone, my product code is GT-I9000HKDSFR and a few chars before change KOR by SFR (or whatever your op. code is).
- Then you have to compute a md5sum on the modified nv_data.bin and store the md5 in a file called nv_data.bin.md5. Make sure your md5 file is exactly 32 bytes long, there is no CR/LF at the end of the line. md5sum is available for any plateform, for myself I did it on my Linux box which is my SAN.
- Next step : push back these 2 files in your /efs/ directory and reboot.
To make sure nothing is altered during the reboot process, I've removed the battery to switch off the phone. At the next reboot, no more SIM unlock code request. I've been able to place a call, my phone is back to life !
Can someone takes some time to do this trick on a 2.2 froyo JPC firmware ?
Hope this will help others...
Click to expand...
Click to collapse
Looks promising!
Does it have to be JM6 or can JM7 work as well ?
Can anyone with JPC and a locked phone try this and report if it works ?
If we go back to JM6 do the editing and fix the product code then back it up on the PC, update to JPC and push this back to the phone this should work right ?
Any news if its possible to restore the IMEI ?

Ok I'm stupid and I can't make a md5 file of 32 bytes with md5summer for windows, somebody can help me?

edit de file with notepad and delete the 1st 3 lines and the count 32 bytes and delete all the rest.

I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .

quiron said:
I tried with JM7 with CSC_I9000TMNJM1 and there is no KOR sequence in nv_data.bin FILE. instead was already TMN, but still asking me for de unlock code.
I tried with JPC and still don't work .
Click to expand...
Click to collapse
It means your phone is configured as TMN (dont know which country it is) but if it asks you for unlock code => your SIM is not TMN.
Change TMN to whatever your SIM is... Check in regedit for a history. Anyway downgrade to a previous firmware because JPC is suspected of breaking the nv_data.bin
I don't know if this trick works with another firmware, but theorically it should works the same way...
Nb: do not delete any line in your nv_data.bin ! This is a stupid remark, it can brick your phone.

the solution to 00000000 unlock code
finaly the solution to 00000000 unlock code
http://forum.xda-developers.com/showpost.php?p=7957950&postcount=10
or
http://forum.xda-developers.com/showthread.php?p=7957950&posted=1#post7957950
works to me.

no phone function on my Galaxy S

My details are as follows:
pda i9000ddjg4
phone i9000ddjg4
I downloaded Kalpik and Doc rom and flashed with clockworkmod. I was not satisfied with it and moreover it changed my product code. In Kies I used to get message that my firmware cannot be upgraded. Therefore I copied two files from my original backed up efs folder to the new Efs folder. The files were copied using busybox and terminal emulator. The files were nv_data.bin and nv_data.bin.md5. I got the original product code after rebooting but instead of the phone operator symbol now I get a blue circle . Again I restored, using rom manager, my phone from a previous backup(from my original firmware). But again the same problem. I used Odin and flashed the ddjg4 firmware. That also has not helped. Can somebody guide me how to get back the phone fuction?

Check this thread out:
http://forum.xda-developers.com/showthread.php?t=780509
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse

It worked a charm. My Simcard now works. Thanks a million.

Oh I did not see that when I lost phone functionality when I did it.
Can I use this method to trick KIES?
Although the regedit hack would be easier I guess.

RambJoe said:
Oh I did not see that when I lost phone functionality when I did it.
Can I use this method to trick KIES?
Although the regedit hack would be easier I guess.
Click to expand...
Click to collapse
The hack only tricks Kies, your phone still has the wrong productcode after flashing. Mine did at least. Went from european JM2 to JM8 and then to scandinavian JP6. Had some troubles with it so used the registry hack to go back to the official european JM2. It worked, but in the registry it still listed as a scandinavian JM2. Don't know what the difference is (except for different Samsung Apps).

MultiCSC OXXJK2 - Asian MultiCSC

ok i know, another attempt to learn something from seniors:
Just downloaded the 'GT-P1000-CSC-MULTI-OXXJK2.tar.md5 *' from samfirmware.com attempt to flash asian multicsc and after unzipping, see the tar.md5 extension and feel something have to do with the 'signed' thingy every one now fear of.
This tar.md5 contains 3 files: cache.rfs, dbdata.rfs & moveinand.mst
May i know will i face problem if i flash this csc with Roto's JME firmware?

I just try flashed my tab to the newest asian rom == ZHKA1 with the CSC u mentioned .....
After reboot.......
Do u think I being signed?
HA...HA....HA....
It still unsigned and can flash any rom I like..
I just test it with SGT bootloader check..!!!
So, just go on, without this CSC, the tab even can't boot!!!!!
MY FIRST FLASH in Galaxy TAB...

the mentioned CSC didnt work with Roto's JME flash which i applied to my SGT. Odin1.7 reported checksum not right or something like that and halt the flash. so i am using CPW from JME multiCSC that came with Roto's.
I will try when gingerbread 2.3 is ready for SGT. btw, you're from HK/China to use that ZHKA1?

I from Hong Kong, haven't flash Roto JPE before as it have protected bootloader issue.
Just follow the guide of Chainfire to asure the ROM is safe before flash. I think your tab have be protected as the post stated by Chainfire.
Sent from my GT-P1000 using XDA App

rainbow ng said:
I just try flashed my tab to the newest asian rom == ZHKA1 with the CSC u mentioned .....
After reboot.......
Do u think I being signed?
HA...HA....HA....
It still unsigned and can flash any rom I like..
I just test it with SGT bootloader check..!!!
So, just go on, without this CSC, the tab even can't boot!!!!!
MY FIRST FLASH in Galaxy TAB...
Click to expand...
Click to collapse
Check Fus also notified me of KA1 version available, but could you kindly explain step by step how you upgraded your FW please?

smaragdhk said:
Check Fus also notified me of KA1 version available, but could you kindly explain step by step how you upgraded your FW please?
Click to expand...
Click to collapse
he....he.... "Fus" mean what??
I am not expert, just share my experience to see if it helpful.
When I 1st flash I9000, I lost much thing, like APN (can't use 3G), CSC code( no Samsung Apps to download, market link, can't use KIES to update offical rom, IMEI no), and some app which need password and username as I forgot that anyway. So try to backup everything is the must before you flash, as mentioned by Rotohammer and Chainfire.
Go to your APN setting and write down everything for u to get your 3G connection.
Use Z4Root to root your device and make a full backup with "Titianium Backup".
Use SGS tools to backup ur product code, something like nv_data.bin etc.
Use root explorer to copy the /efs
Use Chainfire root if u can to make a nandroid backup of your current ROM, it is highly recommended in case your TAB being bricked can easily recover to the current stage without pain.
after everything backuped, copy all the file to your computer or external SD card and remember to unmount it.
Flash is simple , backup is painful but MUST do if u don't want to post "my TAB is bricked, help me pls" in the forum. (In actual case , it is really difficult for u to brick your TAB or I9000 permenant if u are not a developer like Chainfire as they always try to make something experimental on the phone that why they are so respective!
Flash procedure:
1. stop the KIES running in your computer, (front or background running is not allowed), terminate it by task manager of window if u don't know how.
2. start the Odin v1.7
click the re-partition box, click the pit and choose p1.pit, click the PDA and choose the ROM file u want to flash,in me case is KA1, which should with .tar as extension, click the CSC and choose the CSC u want to use.
3. power off you TAB , remove SIM and SDcard, press the volume down and the power buttons together for a few seconds, a nice yellow android robot appear on the skin, release the buttons and connect to the computer asap.
4. the Odin window will appear a yellow box if it detect the phone, then click the start button.
5. everything will go on automatically , no need to do anything and pls don't, be patient . The whole process of flashing about 3 to 7 minutes, then the TAB reboot to fresh new ROM.
p.s. if any thing go wrong or missing berfore u connect the phone to computer, just close all restart again, do not click any thing not mentioned. If the phone hv any problem long press the power button for 8 second will reboot. if u failed (odin will tell u), and see "phone-!-computer" ,just re- start the odin again and plug in the phone, u will see the yellow box and click start , the flashing process wil restart once again.
hope helpful. ;-)
Sent from my GT-P1000 using XDA App

rainbow ng said:
Flash procedure:
1. stop the KIES running in your computer, (front or background running is not allowed), terminate it by task manager of window if u don't know how.
2. start the Odin v1.7
click the re-partition box, click the pit and choose p1.pit, click the PDA and choose the ROM file u want to flash,in me case is KA1, which should with .tar as extension, click the CSC and choose the CSC u want to use.
3. power off you TAB , remove SIM and SDcard, press the volume down and the power buttons together for a few seconds, a nice yellow android robot appear on the skin, release the buttons and connect to the computer asap.
4. the Odin window will appear a yellow box if it detect the phone, then click the start button.
5. everything will go on automatically , no need to do anything and pls don't, be patient . The whole process of flashing about 3 to 7 minutes, then the TAB reboot to fresh new ROM.
Click to expand...
Click to collapse
Are you able to root this? I did the same as you before, but error is not enough space for superuser.apk sigh, if you have any info, perhaps enlightening me
EDIT: Nevermind Put in su, busybox, and superuser.apk into /system/app through linux mount, in the process I removed usual stuffs that I dont need Cool!

fastcx said:
EDIT: Nevermind Put in su, busybox, and superuser.apk into /system/app through linux mount, in the process I removed usual stuffs that I dont need Cool!
Click to expand...
Click to collapse
use adb shell
rootsh
mount /system
cd app
ls ~~ to see what is inside and choose some unwanted app
rm
exit
exit
and now u gain space in /system and can install su
Sent from my GT-P1000 using XDA App

rainbow ng said:
use adb shell
rootsh
mount /system
cd app
ls ~~ to see what is inside and choose some unwanted app
rm
exit
exit
and now u gain space in /system and can install su
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
Already rooted it yesterday but thanks anyway, i just edit the factory.rfs in linux b4 I flash it into my tab instead now I dont need to remove anything after flash

fastcx said:
i just edit the factory.rfs in linux b4 I flash it into my tab instead now I dont need to remove anything after flash
Click to expand...
Click to collapse
Out of interest, do you use this Linux shell command ?
#mount -o loop factoryfs.rfs /mnt/rfs
On Mac OS X terminal I normally use the following commands, but I don't think modifications can be written back to the RFS archive:
#sudo mkdir /Volumes/rfs
#sudo hdiutil attach -imagekey diskimage-class=CRawDiskImage -nomount factory.rfs
#sudo mount_msdos /dev/disk{n} /Volumes/rfs
I use Ubuntu for most of my Android hacking, so I guess I will also start using Linux to look inside RFS archives, and to modify them directly

OEMINFO collection

Hello everyone. I have an idea: let's share our oeminfo?
What is oeminfo?
Oeminfo is a partition in Huawei devices that defines what regional settings will be applied on boot.
How does it work?
No one except Huawei knows what exactly this partition contains. It can't be mounted, most likely doesn't contain files and its format is undefined.
The only thing we know is that changing its content to the one from device of another country makes your device think it's from that country.
Also we know that the device somehow reads this partiton and decides what folder from cust partiton to read and link to.
What's all that for?
As we know, Chinese manufacturers often forget to update devices from countries other than China. It makes their owners frustrate and dream of new features they'll possibly never get.
How to know what oeminfo do i have?
First of all, go to "About device" and look at build number. For example, my Russian tablet has BTV-DL09C100B005 number. BTV-DL09 is model, C100 is region my firmware belongs to and B005 is version.
At this moment we can find the newest chinese firmware, which build number is BTV-DL09C233B026. C233 is Chinese region and this firmware brings some new features to EMUI like posibility to hide navigation bar, set screen density to apps etc. Of course if your region differs from C233, you won't see this update with Update menu.
Also, you can type *#*#2846579#*#* in dialer, go to Network Information Query and then to Vendor Country info. My device shows Vendor: hw, Country: ru.
How to backup oeminfo?
I know 3 ways:
1) With TWRP backup feature
2) With dd from TWRP adb shell
3) With ES Explorer.
1) Backup with TWRP is easy and doesn't need an explanation.
2) To backup with dd go to TWRP, connect your device to the computer, type adb shell in command line and you'll be in TWRP console.
Now type dd if=/dev/block/platrofm/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo.img and you'll get a byte-to-byte copy of oeminfo partition in internal storage.
3) To backup with ES Explorer, you'll need root access. If you have if, go to /dev/block/platrofm/hi_mci.0/by-name/ and copy oeminfo to another place.
I don't know which way is the most correct, but owners of another Huawei devices change oeminfo with ES Explorer and sometimes dd.
So, what do you, guys, think? If someone has Chinese DL09 with C233 region, please, share your oeminfo, so other people could get updates.

Wow, great post full of great info...
Just for the sake of trying, I successfully copied my oeminfo file as you advise from /dev/... to SDcard, using ES Explorer in root mode.
For everyone's info that's a mighty 64MB file... my case is vendor=hw, country=eu.
One innocent question: say we get a Chinese oeminfo somehow, how to be sure that swapping around those files in /dev/... directory won't brick the device? (or turn the display to unreadable pinyin characters...)

lolo83560 said:
Wow, great post full of great info...
One innocent question: say we get a Chinese oeminfo somehow, how to be sure that swapping around those files in /dev/... directory won't brick the device? (or turn the display to unreadable pinyin characters...)
Click to expand...
Click to collapse
Well, this method of switching regions is used on many huawei devices like Mate 8, Honor 6, P8 lite, Mediapad M2, Mediapad X2, etc. I can't garantee that it works on M3, but I don't think it's something completely different from other devices where this method works. Anyway, at this moment I want to collect these files from different regions and see if they're at least similar. Its size is really 64MB and it's OK. I also would make a dd backup just in case something goes wrong.
P.S. what's your build number? I'd like to know if other countries have more recent firmware than Russia, cause the reason of all this messing around is just getting as more updates as possible.

P.S. what's your build number? I'd like to know if other countries have more recent firmware than Russia, cause the reason of all this messing around is just getting as more updates as possible.
Click to expand...
Click to collapse
it's BTV-DL09C100B003
by the way I also uploaded my oeminfo file up there so you can play around.... (click the "Valider et telecharger le fichier" button in the middle).
Let us know how it goes...

Got mine through a gray import, and looks like it is a Chinese version:
Model No: BTV-W09
Build No: BTV-W09C233B019
Device not rooted yet and waiting for availability of official recovery before installing TWRP.
Device did have a lot of Chinese app (since uninstalled) but no real issue switching language to English on first boot up. Had to select English (UK) before I can use Australia as region. Selecting English (US) did not give Australia as a country as an option.
Have also replaced the EMUI with stock standard Google interface.

I am not rooting mine yet but my
Modelnumber: BTV-W09
Build Number: BTF-W09C100B003
bought mine officially in Austria

rling said:
Got mine through a gray import, and looks like it is a Chinese version:
Model No: BTV-W09
Build No: BTV-W09C233B019
Click to expand...
Click to collapse
What's different from DL09? Wi-Fi only, no SIM? Is there anything interesting in Settings? Does it see any OTA?

Hi,
from Huawei's specifications page, indeed seems only two models have been released: DL09 (L as LTE) and W09 (W as WIFI).
DL being the same as W with cellphone "Network" features added, i.e. GSM, UMTS, LTE, etc.
Availability of the LTE seems to depend on region, whereas the (cheaper) WIFI model is available everywhere.
eg. in EU we have both, whereas it seems they only get the W in the US.

BTV-DL09
BTV-DL09C100B003
Bought in Germany (LTE Version).

Slavon-93 said:
What's different from DL09? Wi-Fi only, no SIM? Is there anything interesting in Settings? Does it see any OTA?
Click to expand...
Click to collapse
WiFi only. Only had one OTA and that was when I first turned it on. No current update in settings.

This is important stuff since it may help us unlock the 5 GHz WiFi which is disabled in the US versions.
I have been searching and I have found https://pan.baidu.com/s/1nuUWTo1 contains the fastboot roms for the chinese versions this has 4 files boot recovery cust and system
in my preliminary analysis I see that boot and recovery are signed and the signature block is 4K

Looks a good start ... but it's all in Chinese characters. Google translate does a great job but eventually downloading bigger files need the "BaiduNetDisk" utility to be installed, which is all in pinyin too ... unreadable for non-asians and google translate cannot be used to help it.
Any chance you could retrieve this all and upload it for us to another place?
Essentially these two big 1.4GB files cannot be downloaded w/o the utility :
华为_BTV-W09_BTV-W09C233B017_中国(China)_6.0.zip
华为_BTV-W09_BTV-W09C233B010_中国(China)_6.0.zip
and beware, the file MiFlash工具教程.zip is reported by Firefox to contain a virus or malware. Might be true or not, but at least MSE does not flag it as dangerous.

lolo83560 said:
Looks a good start ... but it's all in Chinese characters. Google translate does a great job but eventually downloading bigger files need the "BaiduNetDisk" utility to be installed, which is all in pinyin too ... unreadable for non-asians and google translate cannot be used to help it.
Any chance you could retrieve this all and upload it for us to another place?
Essentially these two big 1.4GB files cannot be downloaded w/o the utility :
华为_BTV-W09_BTV-W09C233B017_ä¸*国(China)_6.0.zip
华为_BTV-W09_BTV-W09C233B010_ä¸*国(China)_6.0.zip
and beware, the file MiFlash工具教程.zip is reported by Firefox to contain a virus or malware. Might be true or not, but at least MSE does not flag it as dangerous.
Click to expand...
Click to collapse
Don't know why, but I can mark these files, press 下载 button and files are being downloaded. The problem is it's very slow.
Also, I have a link to Full OTA firmware for BTV-W09C233B019:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v67974/f1/full/update.zip
PLEASE, BE VERY CAREFUL IF YOU WANT TO INSTALL IT
How-to:
1) Download this file.
2) Open it and assure that it has META-INF folder and UPDATE.APP file inside.
3) Find some kind of Huawei firmware extractor and open UPDATE.APP with it.
4) Extract cust.img and verlist.img
5) Open verlist.img with notepad or any other text editor and assure it has BTV-W09Cxxx inside, where xxx is a number.
6) Find ext4 extractor and extract cust.img. Somewhere in dualcu/cn/prop you will find local.prop. Open it and assure it has ro.build.display_id=BTV-DL09C233B019 inside.
7) Boot into TWRP and make a backup, transfer in to the PC.
8) Make a backup of all partitions with dd from adb shell (still it TWRP):
Code:
for f in 3rdmodem 3rdmodemnvm 3rdmodemnvmbkp boot cache cust dfx dts fastboot frp fw_hifi fw_lpm3 hisitest0 hisitest1 hisitest2 misc modem modem_dsp modem_dtb modem_om modemnvm_backup modemnvm_factory modemnvm_img modemnvm_system modemnvm_update nvme oeminfo persist recovery recovery2 reserved1 reserved2 secure_storage sensorhub splash splash2 system teeos trustfirmware vrl vrl_backup ; do echo "Copying $f"; dd if=$f of=/sdcard/$f.img; done
Please, edit it according to partitions you have, because this script is for BTV-DL09. The easiest way to do it is launch "ls -1" command, copy its output to notepad, delete userdata from the list and put everything in one line.
9) Copy img files to your computer.
10) put update.zip to your tablet's memory and install it with TWRP, just like any other zip file.
11) You will loose TWRP, so boot into fastboot and reinstall it.
I'm not responsible if anything goes wrong. I don't have W09 tablet, but all these have been done by me on a DL09 variant with Chinese C233B026 firmware.
Also, I will try to download these zip files and put them to another site.
Added links to those Chinese ROMS. Please, tell me if you can't download them or can't undestand how to.
Link to Chinese firmware files

BTV-W09
BTV-W09C100B003
European (WiFi Version).

So, well, thanks to all. As I see, there's really no great need in changing OemInfo at this moment.
Here're the reasons:
1) You want OTA -> you don't modify the system. Otherwise it won't install.
2) If you have root and did some modifications, it's better to install Chinese firmware than wait for an OTA which may come or not.
3) This tablet is not a cheap one and still there was no person who'd like to try changing OEMINFO to some other, so we don't know if it can be done at all.
4) Chinese firmware can be successfully installed with TWRP and if you backup your cust partition and restore your original folder structure there after installation, you won't have any problems. Moreover your tablet will behave just like it's from your country, not China.
5) Nobody knows how to manually install OTA updates, because old ways don't work and new ones are not discovered.

Could somebody post a TWRP backup of the Chinese version of oeminfo for the BTV-DL09C233.

TWRP backup image of BTV-DL09C233 (Chinese LTE Version) OEMinfo
bejam said:
Could somebody post a TWRP backup of the Chinese version of oeminfo for the BTV-DL09C233.
Click to expand...
Click to collapse
Hello all, I'm relatively new to this forum but I'd like to make a contribution.
Recently I rebranded my Mediapad M3, changing the oeminfo from C233 to C100.
I made a backup before this change and would like to share it.
Of course, I wouldn't recommend the C233 unless you are Chinese. Because of the Chinese gov't ban on Google products, it removes most standard Google features and replaces them with Chinese versions.
While there are workarounds (installing Google Play) I feel that it significantly alters the Android experience.
I can confirm that changing from C233(China) to C100(Europe) works well, however I am not sure if the same can be said of the converse situation.
Anyway, enjoy!
mega.nz/#!9QFFALgT!ugaSQooJBIRlnHHMq7Abrf6lru3SjLcgnvbV3hglPok
Since I'm a new user I can't post a direct link right now

thanks for the oem info.is there much bloatware on the chinese version

Chinese bloatware
trd_jzx100 said:
thanks for the oem info.is there much bloatware on the chinese version
Click to expand...
Click to collapse
There are maybe about 10 apps in place of google apps, but most of them can be uninstalled. A few can only be disabled

I bought mine in Romania, it has Vendor: hw, Country: eu. The sticker on the back, with the MAC and S/N says Huawei Technologies Netherlands BV. I have a W09C100 version, with Nougat B301 on it right now.

LG VoLTE FIX [ Rooted Stock Based Rom] [JIO]

You are Responsible for what you do to your phone. Don't Blame me for ANYthing. BACKUP before making any changes
NOTE-
-This method consists of Editing Build.prop & Volte configuration file in cust folder.
- This method may not work for all but it will give you some idea about how things are going on.
- Im not a Developer and English is not my native language.
Complete method and explanation-
Step 1- (For fulmics rom you can skip this step as volte in build.prop is already enabled)
Editing build.prop file
GO to build.prop file in System folder via any root explorer and paste this command at last.
Code:
ro.lge.supportvolte=1
After pasting this command , leave a blank line at last and save. Now reboot your phone , it will enable Volte option in call or network setting. Some people achieve volte services only by doing this step but if volte button in setting dont do anything , proceed to step 2.
Step 2(General)-
Editing a file in cust folder.
Go to Cust > open_com >_config > config_open_eu > vo_config.xml
In this file replace MCC and MNC values according to your region and network. Reboot.
Step 2 (For fulmics rom , guided by @xpirt )-
A-Add following 2 lines at the end of build.prop with a blank line at last
Code:
ro.lge.capp_cupss.rootdir=/cust
ro.build.sbp=1
B- Flash the zip in attachment.( It will add cust folder contents with correct permissions. If this method fails or you face any issues you can delete all the files and folders from cust folder)
C- Follow step 2 (General)
Step 2 with Explanation and Guidance
Maximum time we don't have volte services because we are using a phone of different region or with a carrier other than default.
Cust folder consists of settings and configurations related to the region and carrier. Whenever our phone boots up it detects the carrier or region in which we are using our phone and load the settings according to the network or region. For detection and loading desired configuration phone use 2 codes MCC (mobile country code) and MNC (mobile network code ). You can find mcc and mnc from apn setting or just google including your country and carrier.
For example i am having european h850. so the configurations for all the european countries and their carriers are stored in cust folder. Now what if i boot up the phone in the region other than europe or started using a carrier not included in cust folder or delete all files in cust folder. In this case phone loads the " Open Com " configuration which are not specific to any carrier or region.
So for this method our phone must have all files in cust folder ( in fulmics rom cust folder is empty ) and our phone must be booted with 'opencom' configurations . If you are using any customised stock rom (for h850) or if in software version (under 'about phone' ) you see 'euroxx' it may be means your phone is booted up with '' open com '' configurations.
Now via any root explorer go to -> Cust > open_com >_config > config_open_eu > vo_config.xml
In this file replace MCC and MNC values according to your region. and reboot. That's it
All this worked for me on h850. I dont know about other models.. You can use theory in your own way.
Thanks to @xpirt
Hit thanks if helped

Nice explanation.
Im using genisis mm rom with working volte (edited build.prop). I tried to flash fullmics rom & there is no jio network. Edited build.prop as per the steps mentioned but multiple reboots occur.

vignesh_may28 said:
Nice explanation.
Im using genisis mm rom with working volte (edited build.prop). I tried to flash fullmics rom & there is no jio network. Edited build.prop as per the steps mentioned but multiple reboots occur.
Click to expand...
Click to collapse
Thats because you are not on nougat modem.
For coming to fulmics from marshmallow rom... You first have to flash nougat kdz or full 20a nougat zip from autoprime's thread. Instead of flashing full nougat rom you can also try flashing nougat bootloader and modem from same autoprime thread ( but i only tried with flashing full nougat 20a zip when shifting from marshmallow to nouagt )

Volte is just an option to enable from mobile or is it necessary the network should have the support for VoLTE service?
I'm on LTE network, but every time when I receive call it, always shift to 3G or 2G network, but I don't know my network support Volte service.

arfan.chatha said:
Volte is just an option to enable from mobile or is it necessary the network should have the support for VoLTE service?
I'm on LTE network, but every time when I receive call it, always shift to 3G or 2G network, but I don't know my network support Volte service.
Click to expand...
Click to collapse
VoLTE( Voice over LTE)
Volte is an option that can be enabled from handset and it is also necessary that the network should support volte.

Is there any way to obtain volte (reliance jio) in custom roms? Feel stock is heavy.

vignesh_may28 said:
Is there any way to obtain volte (reliance jio) in custom roms? Feel stock is heavy.
Click to expand...
Click to collapse
Not yet.. But i directed some developers to volte patch thread.. At this point all are busy to make custom roms fully stable , once stability is achieved ...they may work to solve volte issue .

akki7636 said:
Not yet.. But i directed some developers to volte patch thread.. At this point all are busy to make custom roms fully stable , once stability is achieved ...they may work to solve volte issue .
Click to expand...
Click to collapse
brother, a long shot im trying this in my g2. It may not work. i understand. but i just dont want to miss the minute chance it might..
the problem is direct flash wouldn`t help as the /cust position is not in /dev/block/bootdevice/by-name/cust. the actual position is in /dev/block/platform/msm_sdcc.1/by-name/ folder. so i changed the flashing script to such a place but it didnt work. besides i tried "dd if= of=" flashing cust.img to /cust. but it didnt help either, now my cust folder seen in root folder in file explorer is empty. i think the mount command is not suitable for g2. please help in changing. thank you

gpkumaran said:
brother, a long shot im trying this in my g2. It may not work. i understand. but i just dont want to miss the minute chance it might..
the problem is direct flash wouldn`t help as the /cust position is not in /dev/block/bootdevice/by-name/cust. the actual position is in /dev/block/platform/msm_sdcc.1/by-name/ folder. so i changed the flashing script to such a place but it didnt work. besides i tried "dd if= of=" flashing cust.img to /cust. but it didnt help either, now my cust folder seen in root folder in file explorer is empty. i think the mount command is not suitable for g2. please help in changing. thank you
Click to expand...
Click to collapse
This method works when volte support is embedded in the rom ( framework). Can you see volte settings in hidden menu ?

akki7636 said:
This method works when volte support is embedded in the rom ( framework). Can you see volte settings in hidden menu ?
Click to expand...
Click to collapse
Yes sir. Cust is also getting flashed with dd command / by your zip. Only problem is the folder doesn't get mounted.I've even tried mount -o remount,rw -t ext4 command. But it doesn't mount. Please help me im a noob in this aspect

gpkumaran said:
Yes sir. Cust is also getting flashed with dd command / by your zip. Only problem is the folder doesn't get mounted.I've even tried mount -o remount,rw -t ext4 command. But it doesn't mount. Please help me im a noob in this aspect
Click to expand...
Click to collapse
Sending PM

akki7636 said:
Sending PM
Click to expand...
Click to collapse
Tried contacting him. No response.

Provide the files
Please provide the files of cust folder who have working voLTE.

braindeductions said:
Please provide the files of cust folder who have working voLTE.
Click to expand...
Click to collapse
Post 1 explains everything.

akki7636 said:
Post 1 explains everything.
Click to expand...
Click to collapse
Did you get it to have a fully functional voLTE?

braindeductions said:
Did you get it to have a fully functional voLTE?
Click to expand...
Click to collapse
Yes..that's why i made this thread.

Link to the rom version you are on
(exact one)
Have tried open_eu versions 20a/c/d
Vdf 20d

braindeductions said:
Link to the rom version you are on
(exact one)
Have tried open_eu versions 20a/c/d
Vdf 20d
Click to expand...
Click to collapse
Im using fulmics rom.
I used this method on v20a and v20d.
You just have to enable volte in build.prop and edit cust folder's according to your carrier configuration. ( explained in first post ). This method not works on tmobile variants having international roms like fulmics. If this method fails for you it means you need extra ims libraries accoring to your carrier.

akki7636 said:
Im using fulmics rom.
I used this method on v20a and v20d.
You just have to enable volte in build.prop and edit cust folder's according to your carrier configuration. ( explained in first post ). This method not works on tmobile variants having international roms like fulmics. If this method fails for you it means you need extra ims libraries accoring to your carrier.
Click to expand...
Click to collapse
I have the same model h850 unbranded variant. I tried with fulmics and edited all those configuration files as mentioned but when I dial the number I don't hear dial tone instead I get pulse tone. the same problem you mentioned earlier in other threads.

braindeductions said:
I have the same model h850 unbranded variant. I tried with fulmics and edited all those configuration files as mentioned but when I dial the number I don't hear dial tone instead I get pulse tone. the same problem you mentioned earlier in other threads.
Click to expand...
Click to collapse
May be you need to modify some extra settings and configurations which i don't know. Im not a developer and found this method by hit and trial after spending many nights by tweaking each and every configuration related to volte.
Dont forget to add cust enabling lines (mentioned in first post ) in build.prop when you u r using fulmics rom