Database Info

Will this method work to bypass devauth ?

I read somewhere that I dont have to SUPER CID to install a 3rd party ROM, or perhaps our WM6 ROM
"Here is how I got the rom to install without the devauth error.
1) use a hex editor on the rom file and search for the devauth.exe string e.g. 44 00 65 00 76 00 41 00
2) between the "devauth" and the "exe" you will see the hex "00 2e".
3) swap these bytes around so they are "2e 00" instead of "00 2e".
4) This will keep te same checksum but will not allow the devauth.exe to run. well it work in my case at least"
Hope it works
Click to expand...
Click to collapse
Will the above method works? because my phone is still under warranty, and i dont want to void it so early

Building NBH files from RAW files for a Kaiser

Well. I've spent 1 week. Yes, one week. I haven't been productive at all becacuse I've dedicated more than 16 hours per day to find one stupid answer to this question:
Once you dump the rom of your kaiser into the Part00.raw, Part01.raw, Part02.raw and Part03.raw, how can you create an NBH file?
Listen everybody: I've been looking for this site AND OTHERS, and the only gaseous, not so clear at all, lame answers are: "Oh, oh. You need to use Tadzio´s tools".
And that's it. How the f.... do you think that an answer like that is going to work?
Step by Step instructions, people !!!!!
That's what we need to build knowledgebase.
Most people are lazy and want fast answers with out reasearching. That's why they brick their phones. Others, like me, do our their homework but since there isn't anywhere else to ask, so, I have no choice to create a new thread since there isn't NO G.. D..N answer in the forum or in the site !!!!
I have my eyes squared and peeled of looking google's, live search and yahoo results.
Please, people, lets recreate the scenario:
You have a kaiser (TyTN II or what ever you want to call it) phone and you decide that, before bricking, or, even in case of bricking it, you want to copy your original ROM and have a copy of it and also BUILD, for chrisake, a flashable ROM to make the restore procedure easy and dandy.
You download itstools and execute pdocread.exe -l to get the RAW files.
Once you get your 4 RAW files, THEN WHAT????
All what I could find is that you can use some tools from Tadzio called imgfstools but, again, and so nice from you, NO INSTRUCTIONS AT ALL !!!!
So. Any kind soul to give a DETAILED, step-by-step walk through for a Kaiser?
Thanks, community.

http://forum.xda-developers.com/showthread.php?p=1968557

"How to Reconstruct a Dumped ROM & Reconstructed ROMs" by jcespi2005
goye said:
. . . Once you dump the rom of your kaiser into the Part00.raw, Part01.raw, Part02.raw and Part03.raw, how can you create an NBH file?
. . . So. Any kind soul to give a DETAILED, step-by-step walk through for a Kaiser?
Thanks, community.
Click to expand...
Click to collapse
I think this is the thread you want, "How to Reconstruct a Dumped ROM & Reconstructed ROMs" by jcespi2005

Thanks, but no thanks ....
Thanks community for your fast reply.
Well, actually that article "How to Reconstruct a Dumped ROM & Reconstructed ROMs" (http://forum.xda-developers.com/showthread.php?t=337066) from jcespi2005 sucks.
He doesn't give any details of how to do it.
I did learn a lot from doctaJay's videos (http://forum.xda-developers.com/showthread.php?t=372469) on his series "Cooking Guides for the Ultimate Noobs- Screencasts".
Now that's helping the community.
But, no. I need to build FROM SCRATCH my own NBH files using my Part0x.raw files. I don't need to use any one's RUU_Signed.nbh file to cook mine. I need to create FROM SCRATCH the NBH file only from my RAW files, with out using any other NBH file!
I mean ----
0. You tweak your registry IN YOUR PDA, not the computer, to change a Security Policy key:
HKLM\Security\Policies\Policies
valuename '00001001' was set to dword:2, change it to dword:1
YOU NEED TO USE A Registry Tweaker like RegeditSTG. Google it just as I did.
Once you've done all this, then
1. you pdocread.exe -l your ORIGINAL ROM from your kaiser.
So you get an output like this:
210.38M (0xd260000) FLASHDR
| 3.12M (0x31f000) Part00
| 3.63M (0x3a0000) Part01
| 68.50M (0x4480000) Part02
| 135.13M (0x8720000) Part03
STRG handles:
handle a7486c82135.13M (0x8720000)
handle a749618e 68.50M (0x4480000)
handle 074aff52 3.63M (0x3a0000)
handle 074aff76 3.12M (0x31f000)
disk a7486c82
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk a749618e
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074aff52
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
disk 074aff76
0 partitions, 0 binary partitions
customerid=00000000 uniqueid= 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Cute!
2. Step Two is Supposed to be creating your own, personal NBH installer kit from your original dumped ROM without using any other's ruu_signed.nbh downloaded from some guy's ROM kit.
I've read that you need Tadzio's imgfstools for doing so. See?
Even Tadzio's, the creator of the tool doesn't even explain, men and women !
That's pretty much f...ed up !
3. Open and HardSPL your phone BEFORE doing ANY FLASHING TASKS or you would really end up with a nice paper holder on your desk.
4. You should find a way to back up your RADIO ROM.
That's something completely differerent from the OS ROM. Many people complains that once they use some guy's ROM kit, their phones stop working in their networks.
Me, I live in Japan. I can't just download what ever ROM kit and flash my Kaiser, since in Japan my phone provider, E-Mobile, uses a weird 1700 Mhz W-CDMA frecuency, and most of the ROM kits are flashed for GSM networks and different 800Mhz - 1900 Mhz and 2100 Mhz GSM/GPRS networks.
Many stupidly think that flashing a phone's OS is a matter of downloading a g.. d...ed ROM and "bingo", you got your phone done. Actually, because following this guy jcespi2005's ROM (I can't blame him. You can't blame no one for flashing and messing your own ROM, I want to make that CLEAR), my phone doesn't work.
So .... You have to be careful and teach others to be careful, but the best way is to do a comprehensive, all in one step-by-step guide that will clearify most of the doubts of people.
5. Cook your own ROM's
I think, personally, that following these steps will prevent most people of bugging their phones and, at least, in the worse scenario, be able to some how restore most of the original condition of the kaiser so we can claim service or guarantee.
---------------------------------------
We have our RAW files from scratch, dumped BEFORE DOING anything that potentialy might brick our kaiser.
Now, before cooking and all that (again, thanks doctaJay for your screencasts, you da man !), I need to know:
HOW CAN I BUILD AN IMAGE FILE FROM TOTALLY SCRATCH JUST USING MY OWN RAW FILES !!!
It is said that we can use imgfstools from tadzios, but, as usual, not even a g.. d..med clue here !
Instructions !!
I can commit to post a nice, very in depth screencast for all of the people, but, please, I need to create from scratch, with out using ANYONE's dumped image NBH or ROM, a ROM file.
It's as simple as this: How did the FIRST PERSON IN this community manage to create FROM SCRATCH a NBH from his/her RAW files? And let it be told: FOR A KAISER, for chrisake ! Don't compare apples with oranges, even if they tend to behave alike.
See? That's the nature of the question. I'm not interested in COOKING A ROM, using as a base someone else's ROM.
That's the question, community.
Believe me, once I have all these steps mastered, I will make videocasts (screen casts) in both English and Spanish (Maybe Japanese as well).
So, help me out to help others and in tha way we can help new users in a better way !
Thanks !

i don't know how much reading you did in either post from the other guys but the threads they posted give you a STEP-BY-STEP walkthrough, if you can't read the walkthrough then you're a f*****g idiot and you shouldn't be trying any of the $h1t you are trying to do. READ i read through both of those threads posted and now i can dump a rom and cook one for the hell of it, mine only go to me but whatever. your steps only say "2. Step Two is Supposed to be creating your own, personal NBH installer kit from your original dumped ROM without using any other's ruu_signed.nbh downloaded from some guy's ROM kit.
I've read that you need Tadzio's imgfstools for doing so. See?
Even Tadzio's, the creator of the tool doesn't even explain, men and women !
That's pretty much f...ed up !" well that's not an answer. don't creat a thread just to ***** about how you want an answer, write your own damn program and DIYFS if you want to do everything from scratch.
personally i thank each and every member who has contributed anything, because without the guys here i would still have a stock att rom(minus bloat). thank you chefs and all others that have allowed my phone to be as great as it can be

STEP 1: Extract the RAW (IMGFS) file to a dump directory
imgfstodump part02.raw

fgs......how much more info do you need.
from the rom reconstruction thread.
jcespi2005 said:
2. Download the WWE BaseROM to use in the reconstruction process here http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html
3. Download the modified version by Alex of Kaiser Kitchen here, that allows to reconstruct the ROM from the dump. Follow the guide included in the Readme using WWE from previous step and to will get you reconstructed ROM from your device.
Click to expand...
Click to collapse
sure i admit, that's not that much info, which is why i gave u the link to doctajay's screencasts, watch all his videos, everything you need is there. what more do you want?

I forgot to mention: My network is not GSM or similiar and I can't smoke my Radio
tubaking182 said:
i don't know how much reading you did in either post from the other guys but the threads they posted give you a STEP-BY-STEP walkthrough, if you can't read the walkthrough then you're a f*****g idiot and you shouldn't be trying any of the $h1t you are trying to do. READ i read through both of those threads posted and now i can dump a rom and cook one for the hell of it, mine only go to me but whatever. your steps only say "2. Step Two is Supposed to be creating your own, personal NBH installer kit from your original dumped ROM without using any other's ruu_signed.nbh downloaded from some guy's ROM kit.
I've read that you need Tadzio's imgfstools for doing so. See?
Even Tadzio's, the creator of the tool doesn't even explain, men and women !
That's pretty much f...ed up !" well that's not an answer. don't creat a thread just to ***** about how you want an answer, write your own damn program and DIYFS if you want to do everything from scratch.
personally i thank each and every member who has contributed anything, because without the guys here i would still have a stock att rom(minus bloat). thank you chefs and all others that have allowed my phone to be as great as it can be
Click to expand...
Click to collapse
Also, I already mentioned this (who's not reading?):
goye said:
4. You should find a way to back up your RADIO ROM.
That's something completely differerent from the OS ROM. Many people complains that once they use some guy's ROM kit, their phones stop working in their networks.
Me, I live in Japan. I can't just download what ever ROM kit and flash my Kaiser, since in Japan my phone provider, E-Mobile, uses a weird 1700 Mhz W-CDMA frecuency, and most of the ROM kits are flashed for GSM networks and different 800Mhz - 1900 Mhz and 2100 Mhz GSM/GPRS networks.
Click to expand...
Click to collapse
That's why I need to create my own ROM from SCRATCH, not taking other ROMs as a base.

[TUTORIAL] Unlock Samsung [GT-S5570 / i5500 / Galaxy Ace]

Unlock your Samsung Phone
[GT-S5570 / more...]​
------------------------------------------------------------------------------------------------------------------------------------------------------------
First i would like to say some words about this thread. I made this thread at some users requests, original thread contains some obsolete method for unlocking, making some people brick theyr phone. The last method and safe one, was somewhere mixed through other posts from different method and may confuse users. I just rewrite this from 0 for a better understanding and possible questions, discussions about this. I don't own anything from method used.
Original author of method: tweakradje
Original thread: http://forum.xda-developers.com/showthread.php?t=828534&page=34
------------------------------------------------------------------------------------------------------------------------------------------------------------
This tutorial was tested on a Samsung GT-S5570 ( Galaxy Mini ) but worked on some other models too ( i5500 / Galaxy Ace ). For more details you can search in original thread.
First thing you must know is that in order to keep following this tutorial you must have your phone rooted. Temporary or permanent, both will do the job. For any information about rooting phone ( Android 2.2 / 2.3 ) you can do a quick search on XDA-forum or Google.
Root Desktop App: SuperOneClick
SuperOneClick Root Tutorial: Root Tutorial
Now there are 2 methods for extracting the file we need to obtain unlock code, one using ADB Shell(if you use this method, make sure you have installed Android USB Driver first) or using a Terminal App for phone. ADB comes with Android SDK Tools and Terminal Emulator App from market or somewhere else.
• Method 1 (ADB Shell)
- Open one instance of "Command Prompt" and go to folder containing ADB tool (adb.exe). (e.g C:\Program Files (x86)\Android\android-sdk\platform-tools>)
- Make sure your phone is connected to PC and "USB Debugging" it's enabled. (Settings -> Applications -> Development -> USB debugging [X])
- The following commands will be executed in "Command Prompt" that we opened earlier:
Code:
- adb shell
- su
- cat /dev/block/bml5>/sdcard/bml5.img
- exit (2x)
- adb pull /sdcard/bml5.img
So let's understand what we did here. First we run remote shell interactively, grant super-user access, extract the bml5 file to /sdcard then copy it to PC.
The file that we copied to PC should be in C:\Users\~username~\AppData\Local\VirtualStore but you can do a quick search to find it.
• Method 2 (Terminal App)
- Open Terminal Emulator app
- Grant Super-user access to application
- The following commands will be executed in current opened application:
Code:
- su
- cat /dev/block/bml5>/sdcard/bml5.img
- exit (2x)
- Close the application.
bml5 -> (BE-EM-EL-FIVE)
2x -> run the command 2 times
Attention: If you run cat command with the path from above and it's says the file doesn't exists or something like that make sure you try "cat /dev/bml5>/sdcard/bml5.img". For Samsung GT-S5570 the files is under /dev/block.
Click to expand...
Click to collapse
If you get this message when trying to access .bml file while your connected to PC: Permission Denied then try to get your USB card out of Mass Storage mode, so card won't be used by another process.
Click to expand...
Click to collapse
Ok, so after using one of these methods we have our file bml5.img in our PC if we used first method or on our /sdcard if we used second method. Keep in mind that we need this file on our PC, so if you used second method just copy the file to PC!
Now comes the part where we need to work with the file that we just extracted. So, in order to get the unlock code we need a HEX Editor, i've used XVI32 Hex Editor to open the file.
• Finding the unlock code
- Open XVI32 Application that we just downloaded. Hit CTRL+O and select the bml5.img file that we extracted earlier. (Open the file)
- At the first look we will see just a bunch of FF's and 00's and random decimals or symbols, but somewhere deep in there it's our unlock code.
- Hit CTRL+F to open search dialog, select "Hex String" and put the following search string
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 30 30 30 30 30 30 30 30
Click to expand...
Click to collapse
(maybe the search string won't be the same for all phones, but the one from above worked for Samsung GT-S5570)
- Mark "Case Sensitive", Direction "Down", Scope from "Begin".
- Click ok, or hit ENTER to start our search.
- So now, we must hit F3 untill we find our unlock code.
Our unlock code will be 8 digits plain text surrounded by unknown symbols just like in image below.
(I've hited F3 like 3 times, but don't know if it's the same for everyone. Also to make sure you see the code, after hitting F3 make sure you go 2-3 rows up to make sure the code is not above the searched string.)
(Unlock code can be finded in multiple places in file, so if you skip one searched string by mistake, just pay attention for next ones)
After getting the unlock code, write it somewhere in PC or paper... close the phone, remove the actual SIM Card, insert a foreign one and turn it ON! Wait untill it boots up, insert the unlock code and your done. Now you have an unlocked phone!
Attention: Unlock code can be extracted using a Custom ROM like CM7 in my case, the file was there, but can't be unlocked since the window to insert code doesn't appear(pop-up). In order to unlock your phone you must have a Stock ROM that actually can read any Samsung code and have that Network unlock code window!
Click to expand...
Click to collapse
Most custom roms that tries to remove blur break the subsidy lock interface (sim unlock screen doesn't show on them). If you flash other rom and subsidy unlock screen doesn't pop when you insert foreign sim, you will need to flash back stock ROM in order to unlock. So the easyest way for those of you running a Custom ROM, just do a nandroid backup using CWM, flash Stock ROM, unlock your phone then restore your backup.
Click to expand...
Click to collapse
• Useful Codes
*#7465625# - Dial code to check if phone it's network locked.
#7465625*638*UNLOCK-CODE# - Replace UNLOCK-CODE with your 8 digits number, then dial. Phone might reboot.
Click to expand...
Click to collapse
Details about test environment
Code:
Phone used: Samsung GT-S5570 (Galaxy Mini)
Android Version: 2.3.4 (Gingerbread)
PC Windows: Windows 7 (64-bit)
------------------------------------------------------------------------------------------------------------------------------------------------------------
If you have reached the end of the tutorial and you wasn't able to obtain the unlock code( find numbers like 00000000 / 11111111 ), then it means that your phone it's "Hard Locked" or doesn't have the unlock code provided with the phone. I don't know any solution until now for this problem. For most of the people here, this works flawlessly, for some doesn't work.
------------------------------------------------------------------------------------------------------------------------------------------------------------
If you find this tutorial useful please consider pushing the Thanks button at the end of thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can also send me a beer by donating Thank you.

Nice work. I will add it to the OP of my thread.
Cheers

tweakradje said:
Nice work. I will add it to the OP of my thread.
Cheers
Click to expand...
Click to collapse
Nice. Thank you i hope it's clear enough.
Cheers

Nice work OP!

I have extracted the unlock code from a Samsung Galaxy ACE (st-5830) with CM7 mod with the PC method. However, the file was in the SD finally.
I can't unlock the phone until I flash a stock rom. In less than a week I will post if it has work or not.
Thank you everyone.
EDIT: IT IS WORKING RIGHT. My Galaxy Ace is now unlock and making calls. =)

davidteleco said:
I have extracted the unlock code from a Samsung Galaxy ACE (st-5830) with CM7 mod with the PC method. However, the file was in the SD finally.
I can't unlock the phone until I flash a stock rom. In less than a week I will post if it has work or not.
Thank you everyone.
EDIT: IT IS WORKING RIGHT. My Galaxy Ace is now unlock and making calls. =)
Click to expand...
Click to collapse
Nice to hear that heh
@pvp26 - Thank you.

Thanks. I have bml5.img on my sdcard, but how do I transfer it to my PC. I've been searching and can't seem to find an answer. I tried following a link (can't post it because I'm a new member) but my “Wireless and Network” does not have a USB utilities
EDIT: I got it unlocked!! I just emailed myself bml5.img. But does anyone know why I couldn't transfer before?

Many thanks for your organized post.
With it I was able to find my unlock code but I cant get the popup message.( "Unlock code can be extracted using a Custom ROM like CM7 in my case, the file was there, but can't be unlocked since the window to insert code doesn't appear") I have cyanogenmod 7.1 and I would like to know which stock rom you used and where did you get it. Thanks and good job.

LuisDuarte said:
Many thanks for your organized post.
With it I was able to find my unlock code but I cant get the popup message.( "Unlock code can be extracted using a Custom ROM like CM7 in my case, the file was there, but can't be unlocked since the window to insert code doesn't appear") I have cyanogenmod 7.1 and I would like to know which stock rom you used and where did you get it. Thanks and good job.
Click to expand...
Click to collapse
I used stock Gingerbread 2.3.4 that you can get it on samfirmware, scrool down, search for your phone model and click FIRMWARE from table.
@dannycastaway - i don't know exactly why, but usually when you insert USB cable a notification should show on statusbar, slide down and click "Manage Storage / Copy files" something like that and activate it.

It works really good for me!
Samsung Gio S5660, gingerbread 2.3.4 (locked from Bell mobility).
Thanks

This is really a good simple guide. That works, thanks

nice one..!
works fine.. thank you!

Nice work!
Samsung Galaxy Mini (GT-S5570), Gingerbread 2.3.5, Orange network - working flawlessly
Thank you!

I have just registered to show my appreciation! Ive got an S2, but bought the mrs an ACE locked to Orange.
While ive flashed Android Roms on my old galaxy portal, Ive never used ADB, and after a bit of searching online I managed to get my head round it.
So heres a Big thank you for a Complete working unlock on a Galaxy ACE.
Only thing i may add is that i had to use 'cat /dev/bml5>/sdcard/bml5.img'
And with hex editor found the code straight away.
Thanks again!
Ill stick around and see what i can do with my S2 now aswell

tks!
great guys! you are truly amazing.
Perfectly working on i5500
But if you restore the phone unlock code to be reset again? and remains always the same?
Thanks for the answer

marianomonaco said:
great guys! you are truly amazing.
Perfectly working on i5500
But if you restore the phone unlock code to be reset again? and remains always the same?
Thanks for the answer
Click to expand...
Click to collapse
The phone should remain unlocked even after reset or flashing ROM.

Worked in Samsung i5500 Android 2.1
I have a Samsung Galaxy i5500 (Galaxy 5, Galaxy europa, Corby, Galaxy 550), with Android 2.1 update1 bought in Amazon USA.
The given instructions worked perfectly.
I found the code in the first search and was only once in the file.
I got root using SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682
Here is how I made SuperOneClick work for me: http://forum.xda-developers.com/showthread.php?t=803682
I had previously installed:
Java SDK (JDK): http://www.oracle.com/technetwork/java/javase/downloads/index.html
(needed by Android SDK)
Android SDK: http://developer.android.com/sdk/index.html
(that installs adb)
Android USB Driver: http://developer.android.com/sdk/win-usb.html
(I don't know if it's needed)

Hi, many thanks for the guide, it didnt work for me I have a galaxy y and there is no: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 30 30 30 30 30 30 30 30 in bml5.

AchilleX said:
It works really good for me!
Samsung Gio S5660, gingerbread 2.3.4 (locked from Bell mobility).
Thanks
Click to expand...
Click to collapse
How did you manage to do it? What's the process you've used?
I've tried the second method and in the terminal emulator it says permission denied

wow, very useful, thanks!

N920T Storage issues after flashing.

Greetings and salutations, fellow brothers and sisters in modding! You probably have never seen me around, but I've been here a looooong time, behind the scenes, clicking, watching, learning and, of course, modding it up like the crazy fool I am!
Let me just say I love XDA. XDA has helped me out of some HELLA messed up situations, a couple of times my reckless flashing has ended in bricking and if not for XDA I would have to do some fast talking! LOL
N e wayz!! My goal for this phone is to have a stable, updatable ROM on this phone. I need, at least, temporary root for sim unlocking later.
Right now, I'm very confused that after many hours of downloading and flashing the wrong firmware.... no, scratch that, I'm not confused at all.... this is exactly WHY my phone is doing what its doing...
I have root with cf-auto-root and I'm on firmware N920TUVS4DQA2_N920TTMB4DQA2_TMB
The rom is very stable but I only have 8gigs of total storage and the OS eats up about 7.5gigs of that so I can only install busybox and my storage is full!
The specs say I should have 32/64/128 GB of storage.
I'm not sure what to do next to fix this.
Also, I'm receiving a push notify, something about it being locked. I'll post a screen on it.
Any assistance is HUGELY appreciated!!!!!
Much love,
D
P.S. I have the Z3X unlock box for Samsung but it has done absolutely nothing with this phone except let me get the phone codes info off of it, so I'll copy/paste that in. Just in case it helps figure it out lol
Operation: Read Codes
Selected model: SM-N920T
Software version: 29.6
Waiting ADB device... OK
Reading phone info...
Model: SM-N920T
Android version: 6.0.1
Product code: SM-N920TZWATMB
Phone version: N920TUVS4DQA2
PDA version: N920TUVS4DQA2
CSC version: N920TTMB4DQA2
CSC country code: USA
CSC sales code: TMB
HW version: REV0.2
Phone SN: RF8G71W808R
Chip name: EXYNOS7420
Modem board: SHANNON333
Security patch: 2017-01-01
RF cal date: 20150728
IMEI: 000000000000000
Checking Super user right... true
Reading NV data... OK
Checking NV data... OK
Initialization zTool... OK
Running zTool, please wait... OK
HWID: 48 C6 12 AF 0E 07 00 00 00 00 00 00 00 00 00 00
Calculating... OK
Checking hash file... OK
Please wait, calculating codes... OK (time - 00:00:16)
Freeze code: 42050703
NET lock: 17368573
SUB lock: 00000000
SP lock: 00000000
CP lock: 00000000
SIM lock: 00000000
Done with Samsung Tool PRO v.29.6

Screenshot

[GUIDE] How to change SKUID to Worldwide or China (Root required)

FIH made Android Phones with Android 8.0 out of factory installed can't switch SKUID by OST LA without service permission.
Changing SKUID will allow you pass SafetyNet, especially for the Nokia 7 plus converted from TA-1062 China Variant.
如果你来自中国，请看下面翻译成中文的教程：
If you're from China, Chinese translation of this guide:
https://dospy.wang/forum.php?mod=viewthread&tid=154&extra=page=1
Click to expand...
Click to collapse
Here's the procedure:
1. Bootloader must be unlocked and you must get your phone rooted.
2. Use a terminal emulator or adb shell to execute these commands:
Code:
$ su
(Accept root permission on your phone)
# dd if=/dev/block/bootdevice/by-name/deviceinfo of=/storage/emulated/0/deviceinfo.img
WARNING: YOU MUST USE YOUR OWN DEVICEINFO, DO NOT ASK ANY OTHERS FOR THIS DUMP.
THIS PARTITION CONTAINS YOUR IMEI AND SERIAL, AND CRUCIAL DRM KEY, SERVICE KEY THAT ALLOWS YOU TO FLASH PARTITION.
Click to expand...
Click to collapse
3. Use a Hex Editor to open deviceinfo.img placed at root directory of internal storage.
4. Goto offset 0x13B0, you should see data look like this:
Code:
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00001380 53 4B 55 49 44 00 00 00 00 00 00 00 00 00 00 00 SKUID
00001390 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000013A0 53 4B 55 63 68 61 6E 67 65 00 00 00 00 00 00 00 SKUchange
000013B0 36 30 30 43 4E 00 00 00 00 00 00 00 00 00 00 00 600CN
On Nokia 6 (TA-1000) or any other variants, you may not see string "SKUchange" from offset 0x13A0 to 0x13A8, which is normal.
Click to expand...
Click to collapse
5. Modify the value of 0x13B3 and 0x13B4 to 57 which is ASCII "W".
Code:
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00001380 53 4B 55 49 44 00 00 00 00 00 00 00 00 00 00 00 SKUID
00001390 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
000013A0 53 4B 55 63 68 61 6E 67 65 00 00 00 00 00 00 00 SKUchange
000013B0 36 30 30 57 57 00 00 00 00 00 00 00 00 00 00 00 600WW
5. Save it as deviceinfo_mod.img.
6. Copy it to internal storage if you modify it on a PC, then execute these commands with a terminal emulator or adb shell:
Code:
$ su
# dd if=/storage/emulated/0/deviceinfo_mod.img of=/dev/block/bootdevice/by-name/deviceinfo
7. Reboot your phone, reflash global firmware and relock your phone if you wish:
Code:
fastboot flashing lock_critical
(Confirm on your phone)
fastboot oem lock-go
(Confirm on your phone again)
8. Now your phone is completely converted to global version which can pass SafetyNet - you can use Google Pay normally now.

good job

It works~
After doing this and converting from CN version to Android One, the first splash is changed to Android One , not Powered By Android.

Thank you, I have used your method to successfully modify my SKUID to 600WW.

hikari_calyx said:
FIH made Android Phones with Android 8.0 out of factory installed can't switch SKUID by OST LA without service permission.
Changing SKUID will allow you pass SafetyNet, especially for the Nokia 7 plus converted from TA-1062 China Variant.
Here's the procedure:
1. Bootloader must be unlocked and you must get your phone rooted.
2. Use a terminal emulator or adb shell to execute these commands:
3. Use a Hex Editor to open deviceinfo.img placed at root directory of internal storage.
4. Goto offset 0x13B0, you should see data look like this:
5. Modify the value of 0x13B3 and 0x13B4 to 57 which is ASCII "W".
5. Save it as deviceinfo_mod.img.
6. Copy it to internal storage if you modify it on a PC, then execute these commands with a terminal emulator or adb shell:
7. Reboot your phone, reflash global firmware and relock your phone if you wish:
8. Now your phone is completely converted to global version which can pass SafetyNet - you can use Google Pay normally now.
Click to expand...
Click to collapse
can use china sim card?

hackjackyer said:
can use china sim card?
Click to expand...
Click to collapse
Can use China SIM card, mine is China Mobile and China Telecom, dual 4G online

hi everyone, before editing the hex and everything, can you tell me how to unlock the bootloader of nokia 7 plus?(ta-1062)

I succeed and change my boot UI to Android One,then I flashed my phone to 213E by OST and got june patch ,but it still shows uncertified in playstore,will it effect OTA? (T1046 unlocked)

MUGIW said:
I succeed and change my boot UI to Android One,then I flashed my phone to 213E by OST and got june patch ,but it still shows uncertified in playstore,will it effect OTA? (T1046 unlocked)
Click to expand...
Click to collapse
It won't affect OTA. If you wanna make it certified, you need relock bootloader. Just the same methods as unlock bl.
fastboot flash unlock unlock.bin
fastboot oem lock
fastboot flash unlock unlock.bin
fastboot flashing lock_critical

SUN Huayan said:
It works~
After doing this and converting from CN version to Android One, the first splash is changed to Android One , not Powered By Android.
Click to expand...
Click to collapse
which device u use?

juwelrana091 said:
which device u use?
Click to expand...
Click to collapse
Nokia 7 Plus TA-1062 Chinese Version

SUN Huayan said:
Nokia 7 Plus TA-1062 Chinese Version
Click to expand...
Click to collapse
What firmware version was you on and how did you root?

It worked! This needs to be added to the china conversion thread.
Thanks so much

I broke it
Actually, I really stuffed up.
My TA-1062 was rooted and unlocked bootloader, went to follow the guide.
Updated and copied over the device_info.img
Then I did the steps out of order and my device is stuck in download mode.
I relocked my bootloader, which wiped the device, and I though this was reflashing global firmware, which is wasnt.
After the device had wiped itself, I then used magisk manager to remove root, which then caused the phone to only boot to download mode.
I then re-unlocked my bootloader, then I used the deprecated instructions here to try and reflash my device, but the vendor, e2p_script and formatuserdata commands failed. My phone is now still stuck in download mode.
I also tried to reflash using OST 6.1.2 patched, but it seems to get stuck on Reflash Service Bootloader (900sec)
Any tips on how to fix this?
Thanks,
Tom

Thanks!
Getting root took me a while, but with this guide and some others I finally pass SafetyNet.

tomascivinod said:
Actually, I really stuffed up.
My TA-1062 was rooted and unlocked bootloader, went to follow the guide.
Updated and copied over the device_info.img
Then I did the steps out of order and my device is stuck in download mode.
I relocked my bootloader, which wiped the device, and I though this was reflashing global firmware, which is wasnt.
After the device had wiped itself, I then used magisk manager to remove root, which then caused the phone to only boot to download mode.
I then re-unlocked my bootloader, then I used the deprecated instructions here to try and reflash my device, but the vendor, e2p_script and formatuserdata commands failed. My phone is now still stuck in download mode.
I also tried to reflash using OST 6.1.2 patched, but it seems to get stuck on Reflash Service Bootloader (900sec)
Any tips on how to fix this?
Thanks,
Tom
Click to expand...
Click to collapse
Can you get into recovery mode? (Volume UP and Power until it buzzes, then Vol Up and power again to bring up the abd screen). If so you should be able to adb sideload from there.

I cant seem to get this to stick. My about phone still shows TA-1062.
How would i know if this worked?
Should i then flash the worldwide TWRP over the 1062 flash as well?

Surgent said:
I cant seem to get this to stick. My about phone still shows TA-1062.
How would i know if this worked?
Should i then flash the worldwide TWRP over the 1062 flash as well?
Click to expand...
Click to collapse
Yeah it will still show TA-1062. The difference is that it will show the 'WW' model instead of 'CN'. I knew mine had stuck when the play SafetyNet checker showed a pass.
Here's what I did:
1. Unlocked bootloader and critical bootloader
2. Rooted.
3. Followed this guide to make the change.
4. Uninstalled Magisk (basically unrooting)
5. Relock bootloader and critical bootloader
6. Sideloaded the stock Oreo image
And everything is hunky dory. You could also sideload the P beta image from Nokia as well.

shiftybugger said:
Yeah it will still show TA-1062. The difference is that it will show the 'WW' model instead of 'CN'. I knew mine had stuck when the play SafetyNet checker showed a pass.
Here's what I did:
1. Unlocked bootloader and critical bootloader
2. Rooted.
3. Followed this guide to make the change.
4. Uninstalled Magisk (basically unrooting)
5. Relock bootloader and critical bootloader
6. Sideloaded the stock Oreo image
And everything is hunky dory. You could also sideload the P beta image from Nokia as well.
Click to expand...
Click to collapse
Have you received the August ota since doing this?

Yep, got August the day before yesterday.