Develop Bugs

[REF] How to: Extract "Freeze Code" for Free [NOT_UPDATED_ANYMORE]

As of today, August 25, this thread is for INFORMATiONAL PURPOSES ONLY and NOT Updated Anymore. For a complete guide on unlocking, please use this thread and donate to all who made this possible (XDA devs: GalaxySGuy, DaGentooBoy, RazvanG, rbnet.it and marcoponand and rhcp0112345)
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=======================================================================
LEGAL NOTES (because information should be free for all):
YOU MAY NOT, BY ANY MEANS, USE THIS SOLUTION/CODE OR PART OF IT FOR COMMERCIAL PURPOSES.
DO NOT USE THIS EXTRACTION METHOD COMMERCIALLY
YOU ARE NOT ALLOWED TO USE THIS METHOD IN YOUR FREE SOFTWARE WITHOUT PROPER CREDITS ADDED TO IT.
YOU SHOULD ALWAYS MENTION MY NAME AND MY PAYPAL ACCOUNT FOR DONATIONS IN YOUR SOFTWARE IF YOU CHOOSE TO DISPLAY THE UNFREEZE CODE !!
Remember the places online to get a code (NCK & UN-FREEZE), want $25-30 so please donate
PLEASE give credit (and donations if you can) to
RazvanG for finding The Solution, writing this Tutorial and the Automated Script (PayPAL Donation)
rhcp0112345 for finding the file and giving me (and others) a place to start (PayPAL Donation)
rbnet.it and marcopon for the cool SGUX2 utility to extract the code (donate to marcopon and rbnet.it here)
DaGentooBoy for finding a way to extract the .bin file on an un-rooted phone (PayPAL)
For those of you that have donated THANKS!
1. DEV Solutions; Canada
2. Mobile Solutions; Thailand
3. Helio Gastao; Angola
4. Daniel Costin; United States
5. Javier Vidal Mata; Spain
6. Ryan Holzer; United States
7. Kapildev Vyas; Canada
8. Johann Grabner; Austria
9. Valentin Reznik; Israel
.. and a bigger THANKS to those who will donate in the future !!
If your phone has a "Phone Freeze" / "Phone Freeze SIM Unavailable Please Contact Service Provider" or a similar message displayed when you enter a not yet accepted SIM card, this is because you have entered too many wrong unlocking codes previously.
To fix this, you'll be using ADB (Until someone writes down a script) Auto_process via Script file.
Make sure USB debugging is enabled when getting the .bak file from a rooted phone or the .bin file from an un-rooted phone.
(Settings->Applications->Development->USB Debugging)
Step 1. – Get the file
For rooted phones (Advanced Users):
adb shell
su
cd /dev/block
dd if=/dev/block/bml3 of=/sdcard/bml3.bak
For un-rooted phones (EASY method for everyone that uses Windows):
Download the file from the attachment (eXtract C0des.zip)
Extract it
Connect your phone to the PC (Make sure USB debugging is enabled)
Double click: Extract_CODES.bat
Jump to Step 3 (Enter the Code)
OR
Install Better Terminal Emulator 3.17 App
Launch the App on the device. It will give you a command prompt (shell)
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
Mount USB storage and copy the file off the internal SD card
Rooted phones: search for bml3.bak
Un-Rooted phones: search for nv_data.bin
Step 2. – Find the code
Download SGUX2 (v.0.92b): http://www.multiupload.com/81WAY99VHH
It's a win32 executable. Run the program from command line with the blockdevice backup as parameter:
Rooted phones:
c:\sgux2.exe bml3.bak
Un-Rooted phones:
c:\sgux2.exe nv_data.bin.bak
It returns the Freeze Code, Unlock Code/Control Key (NCK) and Network Code (MCC/MNC) for your phone.
OR
Open the file in a HEX editor
Search for SSNV (in ASCII Mode)
At the end of this block of data there should be a string of numbers
(my freeze code started at 00180036)
The format will be freeze_code.freeze_code.unlock_code.network_locked_to
eg.: 1234567812345678.34826952.00000022610
Blue = FREEZE Code (First 8 Digits)
Green = Network Control Key (NCK)
Orange = MCC/MNC the phone is locked to
Step 3. – Enter the code
Power on phone with wrong sim inside so phone displays "Phone Freeze, SIM unavailable. Please contact service provider"
Now type FREEZE CODE that you extracted from the .bak/.bin file and press OK (no digits will be seen on display when entering this code)
Now phone will ask you for Network Code, so enter the NCK code extracted from the .bak/.bin file and press OK.
Now your phone should be un-freezed and unlocked.
HOW TO LOCK SAMSUNG GALAXY S - FOR WARRANTY PURPOSES ONLY
After you get the NCK code using the method above, enter: *7465625*638*#
There will be a pop-up box.
Complete the first field (MCC/MNC) with the network you want your phone locked to (eg. 226 10 where 226 = romania; 10 = orange etc.) and the second field (Control Key) with the NCK extracted from the .bak file.
Press OK and your phone should relock.
RazvanG
LEGAL NOTES (because information should be free for all):
YOU MAY NOT, BY ANY MEANS, USE THIS SOLUTION/CODE OR PART OF IT FOR COMMERCIAL PURPOSES.
DO NOT USE THIS EXTRACTION METHOD COMMERCIALLY
YOU ARE NOT ALLOWED TO USE THIS METHOD IN YOUR FREE SOFTWARE WITHOUT PROPER CREDITS ADDED TO IT.
YOU SHOULD ALWAYS MENTION MY NAME AND MY PAYPAL ACCOUNT FOR DONATIONS IN YOUR SOFTWARE IF YOU CHOOSE TO DISPLAY THE UNFREEZE CODE !!
PS: For devs only: SP=00000000; CP=00000000 (default in every GT-I9000)
If you want me to extract the code for you just PM me with a link to your zipped bml3.bak/nv_data.bin file and I will send you back the code. If it works please feel free to donate via Paypal

worth a sticky!

mike.sw said:
worth a sticky!
Click to expand...
Click to collapse
yes, it does

Great find there, should help all those who tried too many times and locked the phone.
People like this are the reason this forum rocks.

galaxysguy said:
Great find there, should help all those who tried too many times and locked the phone.
People like this are the reason this forum rocks.
Click to expand...
Click to collapse
Thank you for support.
You are right, this forum rocks because knowledge IS power

RazvanG said:
Thank you for support.
You are right, this forum rocks because knowledge IS power
Click to expand...
Click to collapse
You know I agree with you there

galaxysguy said:
You know I agree with you there
Click to expand...
Click to collapse
.. and information should always be free
RazvanG

i keep getting an error using the easy (read: n00b) method.
*Error: unable to find the file <.\nv_data.bin>
phone is connected in debug mode. what am i doing wrong?

no-success said:
i keep getting an error using the easy (read: n00b) method.
*Error: unable to find the file <.\nv_data.bin>
phone is connected in debug mode. what am i doing wrong?
Click to expand...
Click to collapse
I just tested the script file once more. It should work.
Try using the other method, manually extracting the .bak file instead.
RazvanG

RazvanG said:
I just tested the script file once more. It should work.
Try using the other method, manually extracting the .bak file instead.
RazvanG
Click to expand...
Click to collapse
is there another method for unrooted phones?
this is for my wifes phone and she doesnt want hers rooted yet (don't ask)

no-success said:
is there another method for unrooted phones?
this is for my wifes phone and she doesnt want hers rooted yet (don't ask)
Click to expand...
Click to collapse
So I guess it worked for your rooted phone then ..
Try the method for un-rooted phones on another PC (for your wife's mobile phone) or re-install the samsung drivers on the first PC. It should help.
If not, you can always follow this guide, here even though it uses the same principles.
RazvanG

Help - "Network Control Key: 00000000"
Help
I do not know what else to do, someone help me?
I tried with three different Firmwares, and the result is always the same
The Network Code 00000000 doesn't work :'(.
"E:\Generate Unlock Windows>sgux.exe 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.exe bml3.bak
SGUX v0.92b (C) 2010 By Mark0 & rbnet
Samsung Galaxy Unlock code eXtractor
(based on info by rhcp0112345 & RazvanG)
Opening file <bml3.bak>...
Searching code block...
Found.
Searching codes...
Network Control Key: 00000000
E:\Generate Unlock Windows>"

What about if phone wont accept the unlock code? I relocked it and it still wont accept the unlock code?!
Any help about it?

Ai putea face un mic tutorial si in romana?

Program rip

Cannot connect to mobile network???

Hello, this is really weird. In fact, when I insert the SIM to my Note 2 N7100 and turn it on, it allows me to make emergency call, but I cannot use it to make any others and it doesn't show the carrier name (it shows Emergency call only). And when I try to use it to make normal phone calls, it says that I am not registered to a mobile network. I try to factory reset my phone, but the problem remains. I then try to remove the SIM card, and it says that I need to insert a SIM card (that means that it is not a hardware problem since it recognizes the card). I then try to go to the mobile network setting to try to connect to the network manually, it connects me but it shows me a warning which says that the mobile network service is not available (and the Emergency call only label remains). However, I am sure that this is not the problem of the card neither since when I insert the card to my Moto MB860, I can make calls as usual. So, what is the problem ??? It seems to me that the problem happens spontaneously since it works perfectly until yesterday. And all other wireless function works fine including wifi , Bluetooth and GPS and the only thing goes wrong is 3g and 2g.
Additional information:
ROM: Omega v.16
Carrier: Fido Canada (as you can see)
Thanks.

First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...

Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
I tried a simple way which is format everything and flash another ROM but the problem remains.

TRS_80 said:
Noob 1st post......have had similar problems with koodo CDN
Not gonna give such an in depth suggestion as above.....he's something simple to try.
I live in a dead zone and often my phone ( galaxyAce) will switch to no service. Even after refreshing and selecting network under settings, it says it's connected, but isn't. A simple apk that always fixes the problem for me is Network Signal Booster @ theplaystore
Click to expand...
Click to collapse
I don't know that we are in the same situation since at home I often got a good signal and this happened to me only since yesterday.

jabrif said:
First of all, check whether you can see the IMEI of the device. If you can see.
1. Contact your network operator and check whether your IMEI is blacklisted or not.
If you cannot see the IMEI
1.Restore the efs and persist backups (if you have one)
2. flash the device again with the modem image (download the firmware of your device from samfirmwares.com, delete everything from the .tar file except modem.bin, and then flash this file to the phone with Odin (you can get Odin and instructions from that site or from here)
2. maybe your nv_data.bin file or /efs directory got corrupted, make a backup of the folder, then simply delete nv_data.bin, it will be recreated for you.
For this, you’ll need root. If you have a root-enabled kernel, you only have to install the Superuser app and Busybox on the phone, download the Android SDK to your PC, install platform-tools in the SDK manager, go to the platform-tools directory and start adb shell.
In the shell, type su, wait for the Superuser prompt to appear on the phone (if it does not appear, open the Superuser app and try executing su again), enable root access for the command. Now go to /efs, copy everything to for example /sdcard/efs, then rm nv_data.bin.
Reflashing the device with a kernel and checking “phone EFS clear” in Odin also works (make sure you made a backup of the EFS folder just in case).
3. you can try changing the CSC: enter *#272*imei# on the phone tab.
Try this . I'm not sure it works. Just give it a try on yourself.
Trying the above mentioned methods could be vulnerable to your phone if it not done properly. So do it carefully. If you have any doubts feel free to ask me or search elsewhere. But, don't blame me for a fully dead phone. I am not at all responsible for any...
Click to expand...
Click to collapse
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.

Dan Law 001 said:
Some updates;
- IMEI is checked.
- I do not have any efs backup
- nv_data.bin has been deleted and recreated
- trying to register for the firmware
- My phone is always rooted.
Click to expand...
Click to collapse
Results..??
Sent from my GT-I9001 using xda premium

jabrif said:
Results..??
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
I need to get the firmware first... since I already passed the download quota for today... need to wait until tomorrow...

Mmm... I heard that you mentioned clearing the EFS in your given procedure, but I do not think that I modified that folder... However, about few days ago, since I want to gain better control on the volume on my headphone remotes, I did modify the file called Generic.kl in system/usr/keylayout, but I restore it after since it didn't work. However, I don't think that this modification will trigger something in the efs folder since it has different directory. By the way, I did some research online and they say that the efs contains information about the carrier on the phone, so will there's a greater chance that the problem is caused by the possible modification on the efs than any other factor and will there also something else that possibly trigger the similar effects?
Sent from my GT-N7100 using xda premium

Still nothing

[Q] Unlocking BL - need clarification

Hi,
I am going to unlock my Arc S BL. I read many here, but need some clarifications:
My goal is to have XUHD 5.0.1 with suggested kernel (Lupus). Right now I have XUHD 3 (with mod), phone is rooted (I did it somehow:laugh. It got slow and buggy after a while, so I need to refresh it totally.
THE PLAN:
1. Unlock BL using SE Bootloader Unlocking v1.6 by quangnhut123 (seems easier for a newbie than "sony" way, not mentioning the test point one).
2. Using the same tool flash LuPuS Kernel Stock.
Now to be confirmed: All I have to do is to enter IMEI and select file LuPuS_anzu_Stock-iCsv16-full.img. Done?
What would I get after that? Shell I turn on the phone as usual (and it is supposed to run as normal, maybe fresh)?
Should I remove my SD card while doing steps 1-2? Is the contentt of the SD card erased after the process?
Gaps - totally new to me - should I do something with them?
3. Flash the ROM. Well I did it earlies and it worked, so I believe when I will get confirmatoion of above I might succeed.
To be confirmed: to "make phone as new" - what pratition should I wipe? I am going to backup everything possible earlier.
I would like to add my own ringtone. How to do that? (I was told it can be done after installing ROM - via CWM - need suggestions...)
Do I miss something? Do I have to check anything before I start (dont want to finish with not working device...)
Any help would be VERY appreciated.
big thanks in advance.

tman_pl said:
1. Unlock BL using SE Bootloader Unlocking v1.6 by quangnhut123 (seems easier for a newbie than "sony" way, not mentioning the test point one).
Click to expand...
Click to collapse
That is the "sony" way but all the process is done with this app. You lose same features as with the "sony" way.
tman_pl said:
Now to be confirmed: All I have to do is to enter IMEI and select file LuPuS_anzu_Stock-iCsv16-full.img. Done?
Click to expand...
Click to collapse
Put phone into fastboot mode, enter IMEI, then get unlock code, then unlock BL, then select the file and flash the kernel.
tman_pl said:
What would I get after that? Shell I turn on the phone as usual (and it is supposed to run as normal, maybe fresh)?
Click to expand...
Click to collapse
You get unlocked bootloader, custom kernel installed. When you have installed the custom kernel, enter Recovery (press Volume Down button many times during kernel boot logo), wipe the necessary partitions (depends on the ROM) and install new ROM.
tman_pl said:
Should I remove my SD card while doing steps 1-2? Is the contentt of the SD card erased after the process?
Click to expand...
Click to collapse
Not necessary. No SD Data is touched during this process. Unlocking bootloader though does remove all data from your phone inside (not SD), so make backups if necessary.
tman_pl said:
Gaps - totally new to me - should I do something with them?
Click to expand...
Click to collapse
Gapps stand for Google Apps. They are only required, if you install non-stock based ROM (CyanogenMod aka CM or any other).
tman_pl said:
3. Flash the ROM. Well I did it earlies and it worked, so I believe when I will get confirmatoion of above I might succeed.
To be confirmed: to "make phone as new" - what pratition should I wipe? I am going to backup everything possible earlier.
Click to expand...
Click to collapse
For most ROMs, you need to wipe /data, /cache and /system. Non-stock based may require you to not wipe /system.
tman_pl said:
I would like to add my own ringtone. How to do that? (I was told it can be done after installing ROM - via CWM - need suggestions...)
Click to expand...
Click to collapse
If it is on your SD card, your phone can find it. Alternatively, you can put it to /system/media/audio/ringtones folder with any file explorer, that can edit system directory (I personally use ES File Explorer).
tman_pl said:
Do I miss something? Do I have to check anything before I start (dont want to finish with not working device...)[/B]
Click to expand...
Click to collapse
Seems fine for now, nothing that I can think of.

THANK YOU VERY MUCH, your help is very appreciated. All issues adressed perfectly:highfive:!
I am downloading the tools and backing up data (want to format as much as possible)..
Someguyfromhell said:
If it is on your SD card, your phone can find it. Alternatively, you can put it to /system/media/audio/ringtones folder with any file explorer, that can edit system directory (I personally use ES File Explorer).
Click to expand...
Click to collapse
The reason to put it to device memory instead of card one it that when phone is connected to PC in mass storage mode it switches the default ringtone (phone does not have acces to the card)
Well, I did try copy to devuce filesystem, but I get Read Only file system warning, no files copied. I used ES with root permission. I was told it can be done by flashing, but dont know how to do that..
BIG, BIG thanks for your help

tman_pl said:
The reason to put it to device memory instead of card one it that when phone is connected to PC in mass storage mode it switches the default ringtone (phone does not have acces to the card)
Well, I did try copy to devuce filesystem, but I get Read Only file system warning, no files copied. I used ES with root permission. I was told it can be done by flashing, but dont know how to do that..
BIG, BIG thanks for your help
Click to expand...
Click to collapse
Open ES File Explorer, press the Menu button, make sure Root Explorer is turned on, then click on Root Explorer, Mount R/W, make sure /system is set to RW.

SUPERB, thanks again. Working like a charm.
I backed up all I needed. I started SE Bootloader Unlockin Tool, but after I enter my IMEI and hit Get Unlock Code the text-area where the code should appear chnaged color to light-gray only, and nothing more.
I am running win764 if matters...
Should I proceed as told? (hit unlock BL even if Unlock code is not displayed?
I sould I get the code via http://unlockbootloader.sonymobile.com/, paste it and than proceed?

tman_pl said:
SUPERB, thanks again. Working like a charm.
I backed up all I needed. I started SE Bootloader Unlockin Tool, but after I enter my IMEI and hit Get Unlock Code the text-area where the code should appear chnaged color to light-gray only, and nothing more.
I am running win764 if matters...
Should I proceed as told? (hit unlock BL even if Unlock code is not displayed?
I sould I get the code via http://unlockbootloader.sonymobile.com/, paste it and than proceed?
Click to expand...
Click to collapse
Yes get the code from official website
Cheers,
AJ

yep, I got the code from website, But I woder wheter I should use SE BU to unlock if it doesnt get the code properly...?
Well... I will try... What I need is the flashing kernel button

All swept, but I used SEBU with the code I got from official site.
And it seems it all worked!
Just installed the rom and can see configuration screen.
BIG thanks to ALL

delete

well easy to do it

[HOW TO][GUIDE] VPN Without Security Lockscreen

I dont know how many other people out there use androids built in vpn, but i hate the fact that you are required to use a security screen (pattern, pin, password) to do so. I have found a way to bypass this if you are rooted. This has only been tested on the stock kk rooted ota. However i would think it is the same on almost any stock based rom.
This assumes you already have your vpn and a security screen setup and working.
Go to the market and download a root capable data base (db) editor. I use SQLite Editor which is a paid app, but im sure there are free ones too.
Open the db editor. SQLite Editor sorts it by the app (in this case Android System) the data base is associated with, others may not work this way and may require you to navigate to the db file directly (/data/system/locksettings.db).
Open locksettings.db and select the locksettings directory. Look for the line that says "lockscreen.password_type". Under the value colum it will show some random number. Select the line and edit the value to be 0 (zero). Save if required by your db app, and restart your phone.
When it reboots you should no longer have a security lock screen only the swipe up screen. When you go to settings - more - vpn, it will still say you need to setup a security lock. Hit CANCEL, and it will show you your list of setup vpn's. Select one and connect. Boom working vpn with no pattern, pin, password screen required.
To undo this just go to settings - security - screenlock, and setup a new lock pattern, pin, or password.
You can also disable the swipe up lock screen by editing the "lockscreen.disabled" value in the locksettings.db to be a 1 instead of a 0.

good write up, thank you sir.

Where did you get stock kk rooted?
Sent from my HTC One

I was already unlocked and s-off, so i ruu'd took the kk ota and then rooted it. But i believe santod has his thread in development where you can download the stock rooted kk rom.

an alternative method
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:

Alternative method
found it on another forum
The process does not require rooting its more like a bug
worked on my i9300 with 4.3 firmware
1. Add a VPN
2. Lock the device with a pin
3. Enter the pin wrong 5 times
4. Press OK to the message that pops up
5 Press Forgot Pin
6. Sign into your Google Account
7. Select pin lock
8. Press cancel.
and now u got unlocked screen with working vpns

the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance

Hirishiolo said:
the method works, but after I reboot, when I enter VPN screen is aks me for "password for credential storage"... how can I solve? thanks in advance
Click to expand...
Click to collapse
Yeah i have the same issue (nexus 10 rooted 4.4.3 stock)

Hit cancel, and it should bypass it.

cmlusco said:
Hit cancel, and it should bypass it.
Click to expand...
Click to collapse
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)

schickel said:
it should.... but it does not for me (Sony Xperia Z1 with CM11 4.4.3)
Click to expand...
Click to collapse
same for me, it does not work

ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
Thank you :good:

ebackbone said:
An add-on alternative update for relevancy. Using Samsung Note 3 4.3 MJ7 stock rooted.
Firstly, thanks OP for a nice clear guide for all on how to do this theoretically.
This is an alternative for those who aren't able to purchase SQLite Editor:
1. get a good freeware SQLite editor like for example SQLite Studio @ w w w sqlitestudio.pl
2. copy following files from your phone to the PC using some form of file explorer or whatever methods you can think of
/data/system/locksettings.db
/data/system/locksettings.db-shm
/data/system/locksettings.db-wal
3. open up the editor, load the locksettings.db and modify like what OP has mentioned
4. you will notice that the new saved DB is going to be a single file instead so just replace this file back into your phone and delete the OTHER files
5. reboot and done.
:highfive:
Click to expand...
Click to collapse
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2

vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
i am on kk 4.4.2
Click to expand...
Click to collapse
My locksettings.db is empty as well. Does anybody know why?

Geilerzucker said:
My locksettings.db is empty as well. Does anybody know why?
Click to expand...
Click to collapse
on mine one its not empty

Hirishiolo said:
same for me, it does not work
Click to expand...
Click to collapse
i also followed the tutorial now and same as you guys, doesnt work

worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
is there any other solution?

In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?

Clauu said:
In 4.4 there is no such file
Code:
/data/system/locksettings.db
.. any ideas?
Click to expand...
Click to collapse
Try a different file manager.
It failed like that for me with ES File Explorer,
but worked when I used SM File Browser.
---------- Post added at 10:53 AM ---------- Previous post was at 10:42 AM ----------
vadimo said:
i have followed your tutorial and the OP's but when i edit locksettings.db there is no such line "lockscreen.password_type"
Click to expand...
Click to collapse
Tap on the "QUERY *" button to see the file contents.
---------- Post added at 11:11 AM ---------- Previous post was at 10:53 AM ----------
pajenn said:
worked for me initially on samsung mega (jellybean), but after reboot i'm getting the 'enter password for creditial storage' issue and pressing cancel doesn't solve it.
Click to expand...
Click to collapse
What I do here: just type something.. anything, doesn't matter. At least one character.
Then on the next screen, where it asks to set up a lockscreen, just Cancel.
This seems to be necessary once per boot -- any password, different time or the same, works.
After that it lands me on the VPN manager screen, all functional.

Well I kind of messed up. I tried to open with SQLite but it would give me an error 14. So i decided to try to open just like that using ES Explorer and edit it like regular note(SQL is totally different I had no idea). Anyways i didnt edit anything but now i cant set a pin or any type of security on my phone. When i try to set up a pin it still shows a swipe and when i try again my Note 3 freezes and get an error message saying settings stopped responding.
Any idea on how to fix this? Im rooted and im running the latest firmware 4.4.2 if that helps.

[OBSOLETE THREAD] Rooting LG G4S (H735)

[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer

jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:

Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.

Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:

Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks

Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.

jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.

Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers

jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)

Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji

benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.

Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help

benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****

Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app

larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original

I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.

I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!

jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?

Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.

Congratulations @jen.magnolis
Well done