DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
Thank you very much for this post - I am awaiting my UK 32gig SGS2 which I believe is locked to Orange UK - rooting it then following your instructions should be fairly straight forward. I have no idea what fw version it is likely to have - all I know is that its brand new, white and 32gig.
I took the plunge from my Desire HD so fingers crossed I will be happy with my decision to change!
Thanks again for your post...
No problem. Glad it was a help. Thought it should be posted in his forum as well as the same method that worked for the SGS1 works for the SGS2.
Congrats on the purchase. You'll love the phone. Have had mine for a few weeks and it's been great.
I have spend many hours going through XDA dev forums to prepare for the arrival of the SGS2 and I am still trying to work out what ROM to go for.
I recently moved to MIUI on the Desire HD and am really enjoying the difference between this and the HTC Sense bloat. I'm hoping that the extra screen and power of the SGS2 will make me prefer this device as the Desire HD is an old but well respected bit of kit.
The SGS2 looks simple enough to root so, hopefully, over the weekend I'll get it rooted unlocked and have a rom that I can start to tinker with.
Thanks again!
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
http://forum.xda-developers.com/showthread.php?t=1064978&page=36
Incidentally, how does your method differ from the APKs that unlock the sim on these devices?
Rooting is very easy. Just get CF_ROOT for your firmware version. Chainfire has been making the best rooting kernels.
This method lets you do it yourself. The apps work but sometimes won't depending on the phone, not really sure why tbh, but didn't work on my phone so I used this method.
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
but small confusion in hex edit
my model is I9100
country uk
carrier tmobile
for me i edit this address:
2. Using a hex editor go to hex address 18145C You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
Not trying to flame or anything but all I did was download a free app from the market and it did all this for me, even backed up the efs!
= What are you even doing asking whether or not you should root your phone on XDA?! =
does this work on ics??? Thanks!
davidheffernan said:
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
Click to expand...
Click to collapse
simple and easy, since it took me few hour on seeking network code by using HEX-WORKSHOP, this took me just in few minutes, it's great... cheers!!!!
this is like a one click method for sim unlock S2 i9100p
http://forum.xda-developers.com/showthread.php?t=1360174
Even you can't get the unlock code - copy the patch file back, will work.
Tested with Galaxy S2 GT-i9100P
Orange UK
Thanks
Adnan
P.S. Sorry there will be few clicks
-edit and delated
sundar83 said:
DISCLAIMER
NB Same info as in thread by dagentooboy for Galaxy S unlock, which I used on the two Galaxy S' I owned and two others. Thanks should be sent on to them
NB I have seen the thread in Galaxy S II Original Android Development but that method adds too much complication
NB Tested on my Galaxy S II International which was network locked to Three
[PHONE MUST BE ROOTED]
To check if you have Network Lock type *#7465625# into phone dialer
1. Using root explorer or adb copy nv_data.bin and the md5 sum for that file from /efs
For adb or terminal emulator type:
su
cat /efs/nv_data.bin >> /sdcard/nv_data.bin
cat /efs/nv_data.bin.md5 >> /sdcard/nv_data.bin.md5
!!Keep a backup of these files!!
2. Using a hex editor go to hex address 181468 You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
4. Delete nv_data.bin and the md5 for it. Put the edited nv_data.bin on sdcard root (KEEP YOUR BACKUP)
In adb or terminal emulator:
su
rm /efs/nv_data.bin
rm /efs/nv_data.bin.md5
cat /sdcard/nv_data.bin >> /efs/nv_data.bin
chmod 755 /efs/nv_data.bin
chown radio.radio /efs/nv_data.bin || chown 1001.1001 /efs/nv_data.bin
reboot
DONE
but small confusion in hex edit
my model is I9100
country uk
carrier tmobile
for me i edit this address:
2. Using a hex editor go to hex address 18145C You should see FF 01 00 00 00
In order the blocks after FF are:
Network Lock
Network Subset Lock
SP Lock
CP Lock
3. The first block after FF with 01 is the network lock. Change this to 00
Click to expand...
Click to collapse
The same for me I got 18145C and not 181468 but...Yersterday I was able to unlock it,then I uninstall the root flashing back the firmware brand A1 nad...the handy was back sim lock.Today I have done everything again,root,delated the two file,edited the bon file in line 18145C changeing 01 to 00 but...thi time nothing worked .My question is:Maybe I must delaate olsoo some .bak files?There is a different root that after,to unroot it ,I musent refash it?I think Is the falsh the problem (maybe).Any suggest?
Thank's
Helen
Thanks it work's for me with some different methode by my self.
Will this method work on any phone? I used it a few years ago on a galaxy gio, but now I need to unlock a galaxy grand prime, so I'm wondering if this is usable only on older devices. I'm asking without trying it myself because the phone in question is not mine, so I don't have it at the moment.
hi ... im trying to unlock samsung galaxy s3 sgh1747m.
i cant find the nv_data.bin file . anyone can help plz? where is this located?
in efs folder i can t see anything.
ty vm
T-Mobile Austria will remove own Locks for free.
Currently it is not success story, but may be it could helps to somebody.
I bought an old S2 with broken display as parts replacement for my phone. So, I swap mainboard and after succeed flashing of Android 7 I find out that network was locked.
S2 Spec:
Exactly similar Problem was found here.
Model > GT-I9100
Android-Version > 4.0.4
Band > I9100BOLP7
Kernel-Version > 3.0.15-1056084, [email protected]#3
Build > IMM76D.BOLPM
1. This tread does not help me, after reboot that was no Network code asked, but always shown "no SIM" instead.
2. I try this app, but it could not find any code for me.
3. I try app from Helroz and it manage to find some code, but shown me only � � � Symbols instead of the code...
4. I found this app. And after run it was saying that it could do the job for some EUR. However at the "Details" of the app I find out the MCC MNC code and check it here. I find out that it was belongs to T-Mobile Austria. After google it I found this and this FAQ. Based on last one I goes to support the via Chat. The offer me unlock code for 50 EUR, but after I point to the last FAQ, they ask me to use Web Contact to solve this issue. So, I also open a ticketed via Contact here. My point was that I bought phone on Ebay few days ago and based on information in last FAQ it should be unlocked for free. I attach screenshots of the Bills copies from Ebay and PayPal. And after 1 Hour I got an Email with Code.:laugh:
Unfortunately Phone is hanging on the "Requesting SIM Network unlock code" Message, seems I need to go back to stock Android first and try again...
At home a apply an old android 4.1.2 from Sammobile together with pit from here file was in "3 parts Firmware".
Android-Version > 4.1.2
Band > I9100BOLP9
Kernel-Version > 3.0.31-889555, [email protected] #3
Build > JZO54K:I9100WLSD
Basically if you boot directly after flash you will see password enter prompt, that"s because we are back from Android 7 to 4 and we need to boot into recovery mode and wipe everything that can be wiped under it. After this action phone will let you normally boot. During the boot I saw prompt to enter Network Lock Code. That was a time to check if it works:fingers-crossed:
After I entered code - it booted and works perfectly on Android 4.:laugh:
I will do upgrade back to the newest ROM, hope this Lock will never back.
Also I think that this tread solution could help if I knew about the lock before to flash it with Android 7, but only rooting instead.
Does this works for Samsung Galaxy Ace 3 S7275R ?
I just founded that this app work with S2 too, not just S1..
https://play.google.com/store/apps/details?id=com.helroz.galaxysunlock
Sent from my GT-I9100 using XDA Labs
no such file found ...but i have service its crazy .....any ideas? sm-g920p sprint on boost
can be work on J200F ?
Related
Hey,
So i got this vibrant off craigslist. I rooted it, installed root explorer and checked the efs folder and it had the nv_data files but the IMEI was 004999010640000. Now i know my nv_data file isnt the original one cuz i tried the repair_nv_data fix with absolutely no luck. No matter what i still get this fake IMEI. Completely different from the one on the back of my phone.
Is there any way to restore my original nv_data files or manually edit the IMEI number? I flash back to stock firmware using ODIN a=but it resulted in the exact same thing. My IMEI was this 004999010640000 number.
Really need help
I have something you might be able to try (but want to you to look at something first).
I encountered a problem after an i9000 rom flash where something changed my product code in the nv_data file (captivate model). The generic imei was nothing new as i had often seen this using custom roms but a flash to stock always restored my original imei until the time my nv_data files were corrupted and showing the wrong product code.
Download SGS-Toolbox and check your product code....report results back here.
bames said:
I have something you might be able to try (but want to you to look at something first).
I encountered a problem after an i9000 rom flash where something changed my product code in the nv_data file (captivate model). The generic imei was nothing new as i had often seen this using custom roms but a flash to stock always restored my original imei until the time my nv_data files were corrupted and showing the wrong product code.
Download SGS-Toolbox and check your product code....report results back here.
Click to expand...
Click to collapse
Hey thanks a lot for the reply. Uh yea just did that and i got this:
product code in nv_data.bin: i9000hkdkor. Lol thats totally wrong isnt it?
darktranquility18 said:
Hey thanks a lot for the reply. Uh yea just did that and i got this:
product code in nv_data.bin: i9000hkdkor. Lol thats totally wrong isnt it?
Click to expand...
Click to collapse
totally wrong.
give me some time as my fix was for the captivate and its codes......need to update/convert the changes to be applicable to your vibrant. Watch here and i will post a fix to try shortly.
In the meantime. Please do me a favor download Hex Editor Free from the market. Go ahead and make backups to external SD Card or if you don't have one create a temp efs backup folder on /sdcard (internal sd) (Backups of all nv_data files in your efs folder) even if they are wrong.
1. Use hex editor to open the backup of the nv_data.bin
2. Use the capacitive menu button on your phone and it will bring up your options....choose JUMP TO
3. enter 0188008 which takes you to line 188008 and tell me what the text to the far right reads (should read something like .4....K )
3. Scroll down to 00188010 and report text @ right
4. Scroll down to 00188018 and report text @ right
4. finally scroll down to line 188020 and also tell me what text is to the far right (i want to make sure product codes on the vibrant are located on same lines as the captivate)
bames said:
totally wrong.
give me some time as my fix was for the captivate and its codes......need to update/convert the changes to be applicable to your vibrant. Watch here and i will post a fix to try shortly.
In the meantime. Please do me a favor download Hex Editor Free from the market. Go ahead and make backups to external SD Card or if you don't have one create a temp efs backup folder on /sdcard (internal sd) (Backups of all nv_data files in your efs folder) even if they are wrong.
1. Use hex editor to open the backup of the nv_data.bin
2. Use the capacitive menu button on your phone and it will bring up your options....choose JUMP TO
3. enter 0188008 which takes you to line 188008 and tell me what the text to the far right reads (should read something like .4....K )
3. Scroll down to 00188010 and report text @ right
4. Scroll down to 00188018 and report text @ right
4. finally scroll down to line 188020 and also tell me what text is to the far right (i want to make sure product codes on the vibrant are located on same lines as the captivate)
Click to expand...
Click to collapse
Yo really appreciate the help man. Aite
00188008: .800...K
00188010: OR....GT
00188018: -I9000HK
00188020: DKOR....
darktranquility18 said:
Yo really appreciate the help man. Aite
00188008: .800...K
00188010: OR....GT
00188018: -I9000HK
00188020: DKOR....
Click to expand...
Click to collapse
thanks just a little bit more info before i convert my fix.
Go back to those same lines in hex editor
There will 8 block of data between the line # and the text at the right that you reposted. Please post the #'s/letters for each corresponding block so i can ensure that i convert properly.
00188008 | | | | | | | | | .800...K
00188010 | | | | | | | | | OR....GT
00188018 | | | | | | | | | -I9000HK
00188020 | | | | | | | | | DKOR....
I will need the 2 digit/numeral codes in each of the boxes for the line above.
thanks
bames said:
thanks just a little bit more info before i convert my fix.
Go back to those same lines in hex editor
There will 8 block of data between the line # and the text at the right that you reposted. Please post the #'s/letters for each corresponding block so i can ensure that i convert properly.
00188008 | | | | | | | | | .800...K
00188010 | | | | | | | | | OR....GT
00188018 | | | | | | | | | -I9000HK
00188020 | | | | | | | | | DKOR....
I will need the 2 digit/numeral codes in each of the boxes for the line above.
thanks
Click to expand...
Click to collapse
sorry...i know thats a pain in the butt but once i have that data i think i can convert the fix to work for you
bames said:
sorry...i know thats a pain in the butt but once i have that data i think i can convert the fix to work for you
Click to expand...
Click to collapse
disregard last post...i got the code from a health nv_data file so you just need to compare the data from those lines to your own and make corrections in Android Hex Editor.
I sent you detailed instructions in a PM. Please test it....if it works i will repost my ported fix to the general section.
let me know if something is unclear.
PS - Even in a custom rom this should correct your product code (tested in 2.2 code).
I was in stock 2.1 when i crafted and executed this fix the first time so i don't know if it will restore your imei in custom rom environment as when i had an invalid product code in 2.2 i still had right imei.
any resolution to this??? i unlocked my vibrant in the USA and used it with both at&t and tmobile, came to india and i can't use indian sim cards...i took it to a local unlocking wiz, and he told me that my phone's imei has been wiped and according to indian law, no network will register to a phone that has a wiped imei...SO NOW I EITHER HAVE TO figure this out, or buy a new phone for 2 weeks
ANY HELP?
ppriyank said:
any resolution to this??? i unlocked my vibrant in the USA and used it with both at&t and tmobile, came to india and i can't use indian sim cards...i took it to a local unlocking wiz, and he told me that my phone's imei has been wiped and according to indian law, no network will register to a phone that has a wiped imei...SO NOW I EITHER HAVE TO figure this out, or buy a new phone for 2 weeks
ANY HELP?
Click to expand...
Click to collapse
Oh for real? So it is the imei? I have 2 vibrants. Used both in the US with AT&T. I came back to india in november and my vibrant worked perfectly. It has the right imei. When i came back in decemeber with the other phone, unlocked working perfectly in the US, it just said no service here. If what you said was true then the only solution would be to repair the imei somehow. Ive tried everything and no luck :S
bames said:
I sent you detailed instructions in a PM. Please test it....if it works i will repost my ported fix to the general section.
let me know if something is unclear.
Click to expand...
Click to collapse
Hi, Bames!
I have the same issue with IMEI of my phone. Now it shows 004999010640000.
Can you help to restore it to the original which must be equal to the number in the back of my phone?
Thanks.
Id like to know if this was ever resolved and if the correct IMEI had been restored or not? Thank you
bumping because I want to know the reultion to this as well
Hey I got the same problem~!!
Wanna know the resolution, Please~!!
Hasnt been fixed on my phone yet. But try doing what bames did. Maybe itll work for you
i thought the imei number for your phone is located under the battery?
Original post by bames. Just posting it again to make everything clear.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Android Terminal Emulator (make sure to download the one with higher star rating)
D. Hex Editor
E. SGS Toolbox
__________________________________________________ _______________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. To the left you will see line #’s followed by 8 blocks of hex code data that will be 2#’s, 2 letters, or a combination of #’s letters (examples | ff | 54| 00| 4b|). Well will need to edit code in 3-4 lines of the code. Once you have used the jump to option you will see all the lines that need edited on the screen starting with 00188008 (the others will be 00188010, 00188018, 00188020)
9. Compare that data in each of your corresponding lines you see below. Where your numbers are different correct them with the corresponding #’s below. (click corresponding box and it brings up the contained # simply replace it with correct # from chart below). I put the parts you will be comparing and correcting in bold to make viewing easier.
00188008 | 2e | 33 | 00 | 00 | 00 | 00 | ff | 54 |
00188010 |4d | 42 | 00 | 00 | 00 | 00 | 53 |47 |
00188018 |48 | 2d | 54 | 39 | 35 | 39 | 5a | 4b |
00188020 |42 | 54 | 4d | 42 | 00 | 00 | 00 | 00 |
10. Save the file and move it back to efs using root explorer copying over the original.
11. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
12. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
(If you have an issue in Android Terminal Emulator where the keyboard doesn’t come back up after entering su command simply hit the capacitive menu button and you will have the open to re-open the keyboar)
13. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
Using hex editor, check these again:
00188000 - ff ff ff ff 52 45 56 30 - . . . . R E V 0
00188008 - 2e 33 00 00 00 00 ff 54 - . 3 . . . . . T
00188010 - 4d 42 00 00 00 00 53 47 - M B . . . . S G
00188018 - 48 2d 54 39 35 39 5a 4b H - T 9 5 9 Z K
00188020 - 42 54 4d 42 00 00 00 00 - B T M B . . . .
00188028 - 00 00 01 50 02 4e 03 4e - . . . P . N . N
Also, the imei cant be fixed without the original nv_data files(ur efs folder). So its very unlikely that itll be fixed. Also with certain carriers in certain countries, Airtel in india for example, have banned phones from connecting to their network cuz of the wrong imei numbers. On the other hand, a phone with a wrong imei still works on a carrier like at&t.
DontJoinTheDarkSide said:
i thought the imei number for your phone is located under the battery?
Click to expand...
Click to collapse
The imei number of the hardware must match the imei in the nv_data.bin file located in the efs folder of the phone. If they do not match, when u go to 'about phone', you get a wrong imei like 004999010640000 which is banned by certain networks and the android market acts weird at times(doesnt download).
How would the imei number get changed in the 1st place?
edit lines 00188000-00188020
to match the screenshot
I was looking up the partition layout of the Galaxy S III while I stumbled upon this problem.
The first time you run a command in 'adb shell' everything is fine, but when you try to run a second command, it just hangs. It doesn't crash, it just hangs.
So, I tried to find out what could be wrong, by doing the following: Instead of going into the shell itself, I just entered a semi-random command 'adb shell mount', which returned the normal result.
Then, I typed 'adb shell' and guess what? It returns a commonly known error: 'error: protocol fault (status 72 6f 6f 74?!)'
The status code is HEX, which translates to: 'error: protocol fault (status root?!)'
So I suppose this has something to do with the fact that my SGS3 is rooted.
I don't feel like unrooting it, but if someone would be so kind to test this on an unrooted SGS3 and report back the results here so we can investigate this further that would be greatly appreciated.
it works without any error.
do you know what to backup which contains kernel and ramdisk ?
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Cranck said:
Mine is rooted, with Omega Rom V3 and everything works perfect with adb.
Click to expand...
Click to collapse
Have you tried multiple shell commands? I know adb functions, but it's about using adb shell.
I'm on the stock rom, rooted manually with CF's insecure kernel by the way.
I'm not sure this is related, but there is some very suspicious new functionality in the FactoryTest.apk, called "SysScope". Its some kind of service checking and verifying the authenticity of "something". But I have no idea of what, only that a related java file (ResultCode.class [sysscope.service] contain the following code segment:
Code:
[SIZE=2] arrayOfResultCode[0] = OK;
arrayOfResultCode[1] = ADB_RUNNING_AS_ROOT;
arrayOfResultCode[2] = PARTITION_TAMPERED;
arrayOfResultCode[3] = ROOT_PROCESS_FOUND;
arrayOfResultCode[4] = DANGEROUS_FILE_DETECTED;
arrayOfResultCode[5] = NOT_OFFICIAL_BINARY;
[/SIZE]
Then it looks for SysScope files in the SysScopeVerifyer.class like this:
Code:
[SIZE=2]/data/app/com.sec.android.app.sysscope-1.apk
/data/app/com.sec.android.app.sysscope-2.apk[/SIZE]
I suggest you to back these up, and then replace them, with empty files of the same name, and see what happens.
I have the exact same problem on the GS2, OneX, and OneS. I have no problem shelling into the devices using another system, but on one of my computers I have the same issue. Windows 7 64bit with jdk7 installed.
Also, I enabled adb trace to see what was being returned: set ADB_TRACE=all
-Entering ls three times on the OneX, the first time works correctly
Code:
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=5
ls
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=32
acct
cache
config
cwkeys
d
system/core/adb/commandline.c::read_and_dump():read_and_dump(): pre adb_read(fd=
101)
system/core/adb/commandline.c::read_and_dump():read_and_dump(): post adb_read(fd
=101): len=318
data
default.prop
dev
devlog
etc
firmware_dsps
firmware_q6
firmware_radio
firmware_wcnss
init
init.elite.rc
init.goldfish.rc
init.qcom.rc
init.qcom.sh
init.rc
init.target.rc
init.usb.rc
mnt
proc
root
sbin
sdcard
sys
system
tombstones
ueventd.goldfish.rc
ueventd.rc
vendor
[email protected]:/ $ system/core/adb/commandline.c::read_and_dump():read_and_dump()
: pre adb_read(fd=101)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
ls
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): post uni
x_read(fdi=0,...)
system/core/adb/commandline.c::stdin_read_thread():stdin_read_thread(): pre unix
_read(fdi=0,...)
Hi, the title told you what I want to do, i'm under froyo with Telus I root them with Superoneclick and it work my phone is root. I have BusyBox install too but I cant unlock with Galaxsim unlock or SGS Unlock Tool, I'm lost I'm not a pro to do that and I lost time to look for program
Pleazzzz helpppp :crying:
no one?
Looking for the same thing
zeniizenii said:
Hi, the title told you what I want to do, i'm under froyo with Telus I root them with Superoneclick and it work my phone is root. I have BusyBox install too but I cant unlock with Galaxsim unlock or SGS Unlock Tool, I'm lost I'm not a pro to do that and I lost time to look for program
Pleazzzz helpppp :crying:
Click to expand...
Click to collapse
Will post if I find anything good.
---------- Post added at 11:47 AM ---------- Previous post was at 11:42 AM ----------
Netscr1be said:
Will post if I find anything good.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1163843
ok there is 2 ways of doing this
first way..................................................
unlock the Telus Galaxy S Fascinate 4G SGH-T959P
First root the device with SuperOneClick and reboot. Then using adb shell,
su
cat /efs/root/afs/settings/nv_data.bin >> /sdcard/nv_data.bin
Use a Hex editor on nv_data.bin. I used xvi32.
Jump to line 1463 (Or just Ctrl+F "01" hex, it's the first set)
Change "FF 01 00 01 00 00 30" to "FF 00 00 00 00 00 30" <<<<<< IMPORTANT USE THESE TOO FIND CODE!!!!!
rm /efs/root/afs/settings/nv_data.bin
cat /sdcard/nv_data.bin >> /efs/root/afs/settings/nv_data.bin
chmod 755 /efs/root/afs/settings/nv_data.bin
chown radio.radio /efs/root/afs/settings/nv_data.bin || chown 1001.1001 /efs/root/afs/settings/nv_data.bin
reboot
Second way.......................... follow instructions on this link http://forum.xda-developers.com/showthread.php?t=1335548
i use method 2 myself easy just follow instructions and use these in hex editor to find your code .........>>>>>>>>>> "FF 01 00 01 00 00 30" or use "FF 00 00 00 00 00 30" <<<<<<<<<<<NOT THE ONE IN LINK this is proper hex string for this phone.....use one or other to find your code
both will work .....
Just to share a successful restoration of a damaged /efs partition on a i9300 without any backup. Maybe this will help someone save their phone or avoid having to send it in for repair. This appears to be the usual advice when the efs partition is damaged and you don't have a backup. You're fsck'ed. However, you might get lucky, like I did. Read on.
The story: I was running the phone with a custom built cm-10.1 and playing Candy Crush when the battery died. After that the phone wouldn't boot. After booting into recovery it appeared /efs wouldn't mount. That puts the phone in a boot loop. Desperation...
The key to the provided solution is that eventhough your parition is damaged, the relevant data (nv_data.bin) may still exist.
Here's what I did. Not all steps may be necessary, but this is what happened to work for me. The steps I think are crucial are highlighted.
!!!AS USUAL, TRY ANY OF THIS AT YOUR OWN RISK!!! In any case, only do this when your efs partition is damaged and won't mount, not when only files in it are missing or something else.
1. Create an image of /dev/block/mmcblk0p3. mmcblk0p3 is the device file for the partition that is mounted as /efs
I did this by logging into the phone while it is in recovery with adb:
Code:
linux# adb root
linux# adb shell
phone# dd if=/dev/block/mmcblk0p3 of=/data/efs.img
phone# exit
linux# adb pull /data/efs.img .
You now have an image of the efs partition. To verify that it is indeed broken, I did a filecheck on the image:
Code:
linux# losetup /dev/loop0 efs.img
linux# fsck /dev/loop0
That gave an "Invalid Superblock" message. The partition is indeed b0rked. No (obvious) way to rescue the filesystem.
2. I still didn't know what to do so I flashed a stock ROM (G4) using Odin. Still boot looping. Since I wasn't sure the partition table wasn't damaged and the efs partition was lost anyway, I decided to check "Repartition", which is generally discouraged, using a pit file downloaded from the forum.
3. I re-rooted using CF-Root. This time using Heimdal from linux. Stock didn't fix things and you need root to access the partitions.
4. Format the efs! It's unusable and I made a backup, so in recovery:
Code:
linux# adb root
linux# adb shell
phone# mke2fs /dev/block/mmcblk0p3
Reboot the phone and voila! A booting phone, but obviously without serial number and a default IMEI. And some screen came up which I think means I was in factory mode. The data in the /efs partition has been rebuilt with a set of default files.
5. I edited some files in /efs/FactoryApp
Code:
linux# adb root
linux# adb shell
phone# cd /efs/FactoryApp
phone# echo -n ON > factorymode
phone# echo -n ON > keystr
phone# echo -n <xxxxxxx> > serial_no
Where <xxxxxxx> is your serial number, found under the battery. Not sure if this did anything useful, but the serial number no longer indicated 0000000 after that.
6. I flashed cm-10.1 again from recovery, because I was experimenting with EFSPro, which requires busybox on the phone. EFSPro doesn't do much for you in this case. So I don't think this is important.
7. Try to recreate an nv_data.bin from the damaged partition! In order to do this I pulled the rebuilt default nv_data.bin from the phone and compared it to efs.img created in step 1.
Code:
linux# adb root
linux# adb pull /efs/nv_data.bin .
linux# xxd nv_data.bin > nv_data.hex
linux# xxd efs.img > efs.hex
Now inspecting the nv_data.hex, it started out like:
Code:
0000000: cccc cccc cccc cccc cccc cccc cccc cccc ................
0000010: cccc cccc cccc cccc cccc cccc cccc cccc ................
0000020: 4d21 5317 00a0 a2f7 1435 5799 529d 129b M!S......5W.R...
0000030: 48bd ca0e 6249 1367 37a5 96c3 39da 19ea H...bI.g7...9...
0000040: 0000 0000 e000 0000 0200 7400 6c00 0000 ..........t.l...
0000050: 0000 0000 0000 8130 0100 0000 0000 0000 .......0........
0000060: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000070: ffff ffff 0200 0000 333a 3476 2020 2020 ........3:4v
0000080: 5350 3632 3630 5f4d 305f 4d4f 4445 4d5f SP6260_M0_MODEM_
0000090: 3033 2e31 3332 375f 4442 3133 3037 3032 03.1327_DB130702
00000a0: 2032 3031 332d 4a75 6c2d 3136 2032 303a 2013-Jul-16 20:
00000b0: 3035 3a33 3020 0a20 2020 2050 4442 5f4e 05:30 . PDB_N
00000c0: 4f54 5f41 5641 494c 4142 4c45 200a 0000 OT_AVAILABLE ...
I then searched for "MODEM" in efs.hex and found several similar entries. So for the next step, you might have to try a few times. I found one at address 0600000:
Code:
0600080: 5350 3632 3630 5f4d 305f 4d4f 4445 4d5f SP6260_M0_MODEM_
0600090: 3033 2e31 3234 315f 4442 3132 3130 3038 03.1241_DB121008
06000a0: 2032 3031 322d 4e6f 762d 3136 2031 343a 2012-Nov-16 14:
06000b0: 3030 3a34 3920 0a20 2020 2050 4442 5f4e 00:49 . PDB_N
06000c0: 4f54 5f41 5641 494c 4142 4c45 200a 0000 OT_AVAILABLE ...
I then extracted a block of data with the size of nv_data.bin from efs.img starting at this address:
Code:
linux# dd if=efs.img of=new_nv_data.bin skip=12288 count=4096
"skip" indicates the offset (0x0600000) and "count" the filesize (0x0200000). I now had a recreated old nv_data.bin.
8. Put the recreated nv_data.bin on the phone and delete backups.
Code:
linux# adb root
linux# adb shell
phone# cd /efs
phone# rm nv_data.bin
phone# rm .nv_data.bak
phone# rm .nv_core.bak
phone# adb push new_nv_data.bin /efs/nv_data.bin
I rebooted the phone and miracle oh miracle. I had my original IMEI back! Not sure if the phone is in optimal condition, but I can make calls and I have mobile data.
Hope any of this may be of any help to anyone. It took me quite a while to figure things out !!
If this works, you have made an excellent work and i think this has to be stickied :sly:
Inviato dal mio GT-I9300 utilizzando Tapatalk
Well done fella, good work!
Sent from my GT-I9300 using xda premium
Hi SlashV,
Very interesting approach of one of the most frequent issues for I9300!
My case is as follows: I have recovered IMEI with more common methods: kTool,and..
- in 4.3 ROM's my IMEI and serial are ok ... and I have network ,but
- in CM11 or OMNI 4.4 my IMEI is correct but the serial number is wrong !
(and therefore I have no network)
Could you suggest, please, a way to read and/or repair the Serial number in CM11 ?!
( using Terminal Emulator would be also possible?)
Thanks in advance!
serial number in cm
stefan.slavici said:
Hi SlashV,
Very interesting approach of one of the most frequent issues for I9300!
Click to expand...
Click to collapse
Thanks.
stefan.slavici said:
My case is as follows: I have recovered IMEI with more common methods: kTool,and..
- in 4.3 ROM's my IMEI and serial are ok ... and I have network ,but
- in CM11 or OMNI 4.4 my IMEI is correct but the serial number is wrong !
(and therefore I have no network)
Could you suggest, please, a way to read and/or repair the Serial number in CM11 ?!
( using Terminal Emulator would be also possible?)
Thanks in advance!
Click to expand...
Click to collapse
I think my serial number got restored by step 5 of what I did even before I restored my original nv_data.bin, so you might try that. It's easy from the terminal and I'm fairly sure it won't hurt. Make a backup of you efs first!
However, I am somewhat surprised by your issue. How can the serial number change? I did notice CM shows a different serial for me than is on the sticker, so maybe I have the same issue, or CM just shows a different representation of the same number. Anyway, I have no network issues because of it. Maybe your network issues have to do with something else than the serial no?
SlashV said:
Thanks.
I think my serial number got restored by step 5 of what I did even before I restored my original nv_data.bin, so you might try that. It's easy from the terminal and I'm fairly sure it won't hurt. Make a backup of you efs first!
However, I am somewhat surprised by your issue. How can the serial number change? I did notice CM shows a different serial for me than is on the sticker, so maybe I have the same issue, or CM just shows a different representation of the same number. Anyway, I have no network issues because of it. Maybe your network issues have to do with something else than the serial no?
Click to expand...
Click to collapse
no! the serial number changed when i flashed CM11 but no network problem. and then it is back to the previous serial number when i flashed s4 evolution rom!
OMG
You are a genius
This Thread should be moved to General
Glad that the op got his imei & serial back, also that he's posted such detailed instructions (although I think a couple of them won't be necessary for most). For the majority of those who arrive at xda, after breaking their phone by flashing random things they didn't understand it will read like diy brain surgery.
Best option, as always, is to backup the efs -unfortunately it's usually far too late by the time they get to xda.
Sent from my GT-I9300 using Tapatalk
I also had a similar problem. I had IMEI but not valid serial (000000). I solved temporaly using Ariza Patch. But if I can restore the serial using your method.... then I MUST BUY YOU A BEER MY FRIEND!
Some news. In my case I have a correct IMEI but a wrong serial (000000). Resulting in a no network conenctivity.
I've tried modifing the efs.img directly by hand and adding the serial to the serial_no file (it's in plain text). Then I restored using ktool. And nothing. It still says 0000000.
So. Then I tried over adb as you did. echo -n <serial> > serial_no. The operation went succesfully but when I rebooted my phone it still shows 000000.
So I'm guessing (as excepted) these things have protection against tampered serials/imei. Maybe a hash somewhere... But I'm not willing to reverse engineer that (I don't even have the knowledge!).
So....I don't know how you did it. But that step alone doesn't restore the serial number.
---------- Post added at 02:45 PM ---------- Previous post was at 01:56 PM ----------
So I decided to took my investigation a little further.
I had an efs back up so I reproduced all your steps but only on linux.
The offsets of my nv_data.bin are the same as yours. I extracted my new_nv_data.bin from my efs.img (using dd). Then I compared the nv_data.bin extracted mounting the efs.img. They are the same. Not a single bit difference.
I guess it was expected. I just wanted to make sure there wasn't anything wrong with my efs backup.
So. This method really works if you lost you efs partition (corrupted). But In my case (efs not corrupted, IMEI ok, serial 0000), it didn't help.
I bet there's a solution floating around. But there's also a business behind this (all those boxes). So, I don't know if I will be ever be available to fix this by myself.
I'm starting to think that maybe the trick is to format efs (having a backup of course). But I don't know. I'm not that brave haha.
Changing the serial_no file does nothing. That doesn't work for sure. I've tried one more time using root browser and it didn't change from 00000.
Everything is inside nv_data.bin I think. Even the serial. But I guess nobody will tell me here how to correct that so I have network connectivity again without patching.
Anyway, I don't know why so secretive about all this info. I mean, all the boxes out there let you change you IMEI. I bet all the burglers out there already know how to do it. The only ones that still don't know how to do it are the honest people haha. Kind of ironic.
Because it's illegal and gets you five years. Follow the guides on how to restore your efs backup. Discussing imei changing will get the thread locked.
If you don't have backup then pay for a repair.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Because it's illegal and gets you five years. Follow the guides on how to restore your efs backup. Discussing imei changing will get the thread locked.
If you don't have backup then pay for a repair.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
In my case my phone came like this. I can't return it because I bought it abroad.
I have a backup of my efs. I did restored it. But serial is still 0000. IMEI is FINE. I don't want to change IMEI. Just fix my EFS to have a proper serial. Only way of having connectivity back is ariza patch. But I would love to return my phone to factory state. That is not illegal.
Always wonder how the repair shops are able to restore. Still OP post is informational.
hyperorb said:
Always wonder how the repair shops are able to restore. Still OP post is informational.
Click to expand...
Click to collapse
Yes. Maybe formatting the EFS is the key. Because the phone will regerate a dummy one without errors. And then restore the files individually insted of the whole partition.
But... that's is just a guess. And I'm not willing to try it either. I will start worrying when Samsung releases a decent 4.3 version of the stock firmware. Until then I will stay on 4.1.2 with Ariza Patch.
Boxes
hyperorb said:
Always wonder how the repair shops are able to restore. Still OP post is informational.
Click to expand...
Click to collapse
I think they use tools like the SmartSamBox. I contacted the manufacturer and they claim that you can restore imei and serial with it. A box like that isn't even that expensive. I considered buying one before I tried my final "I must get lucky" shot described in this thread.
lost serial
Gonzakpo said:
I'm starting to think that maybe the trick is to format efs (having a backup of course). But I don't know. I'm not that brave haha.
Click to expand...
Click to collapse
If you dumped an image of it, it can't really hurt you imho.
Gonzakpo said:
Changing the serial_no file does nothing. That doesn't work for sure. I've tried one more time using root browser and it didn't change from 00000.
Everything is inside nv_data.bin I think. Even the serial. But I guess nobody will tell me here how to correct that so I have network connectivity again without patching.
Click to expand...
Click to collapse
Yeah, everything is in nv_data.bin. It's a pity I am not a 100% sure, but I really think I got the serial back though before restoring my original nv_data.bin. Changing the serial_no file now, doesn't do anything, like you say, but I added it to an /efs that was created from scratch after a format. Like you, I am a bit reluctant to try and reformat it again, just to see if that would work, but maybe I will. It won't help you though, because starting out with an /efs from scratch is not an option for you. You won't have an imei in that case.
Gonzakpo said:
Anyway, I don't know why so secretive about all this info. I mean, all the boxes out there let you change you IMEI. I bet all the burglers out there already know how to do it. The only ones that still don't know how to do it are the honest people haha. Kind of ironic.
Click to expand...
Click to collapse
Welcome to the World my Friend
Formatting /efs in fact results in automatic regeneration of file structure, just with a null (but still valid) data. By replacing important files with a working backup you can actually revive your phone, as long as you have valid core files.
Anyway, hats off for the solution. May help someone .
You could also try to mke2fs -n /dev/loop0 (with mounted efs.img), and then read superblocks and restore them with e2fsck -b block_number /dev/loop0.
Wow. Thank you for the answers. For a moment I though I was talking alone hahaha
Well. I made the jump and formatted the efs to see what happens. I was on stock 4.1.2 (the old EFS one == I9300XXELLC_I9300XEFELL1_I9300XXELKB)
Surprisingly, after a reboot the EFS wasn't restored for a dummy one. It was empty. I even tried a wipe from the recovery and it didn't work either.
Then I freaked out (haha) and restored my EFS backup and everything was back to normal.
Conclusion. 4.1.2 is no good for this method? Maybe I should try with stock 4.0.4?
SlashV, what firmware do you refere when you say "G4". Latest Android 4.1.2 (mg4 modem)?
I hope I can reproduce your method. So we can at least help the community with a more tested solution.
SlashV said:
Just to share a successful restoration of a damaged /efs partition on a i9300 without any backup. Maybe this will help someone save their phone or avoid having to send it in for repair. This appears to be the usual advice when the efs partition is damaged and you don't have a backup. You're fsck'ed. However, you might get lucky, like I did. Read on.
The story: I was running the phone with a custom built cm-10.1 and playing Candy Crush when the battery died. After that the phone wouldn't boot. After booting into recovery it appeared /efs wouldn't mount. That puts the phone in a boot loop. Desperation...
The key to the provided solution is that eventhough your parition is damaged, the relevant data (nv_data.bin) may still exist.
Here's what I did. Not all steps may be necessary, but this is what happened to work for me. The steps I think are crucial are highlighted.
!!!AS USUAL, TRY ANY OF THIS AT YOUR OWN RISK!!! In any case, only do this when your efs partition is damaged and won't mount, not when only files in it are missing or something else.
1. Create an image of /dev/block/mmcblk0p3. mmcblk0p3 is the device file for the partition that is mounted as /efs
I did this by logging into the phone while it is in recovery with adb:
Code:
linux# adb root
linux# adb shell
phone# dd if=/dev/block/mmcblk0p3 of=/data/efs.img
phone# exit
linux# adb pull /data/efs.img .
You now have an image of the efs partition. To verify that it is indeed broken, I did a filecheck on the image:
Code:
linux# losetup /dev/loop0 efs.img
linux# fsck /dev/loop0
That gave an "Invalid Superblock" message. The partition is indeed b0rked. No (obvious) way to rescue the filesystem.
2. I still didn't know what to do so I flashed a stock ROM (G4) using Odin. Still boot looping. Since I wasn't sure the partition table wasn't damaged and the efs partition was lost anyway, I decided to check "Repartition", which is generally discouraged, using a pit file downloaded from the forum.
3. I re-rooted using CF-Root. This time using Heimdal from linux. Stock didn't fix things and you need root to access the partitions.
4. Format the efs! It's unusable and I made a backup, so in recovery:
Code:
linux# adb root
linux# adb shell
phone# mke2fs /dev/block/mmcblk0p3
Reboot the phone and voila! A booting phone, but obviously without serial number and a default IMEI. And some screen came up which I think means I was in factory mode. The data in the /efs partition has been rebuilt with a set of default files.
5. I edited some files in /efs/FactoryApp
Code:
linux# adb root
linux# adb shell
phone# cd /efs/FactoryApp
phone# echo -n ON > factorymode
phone# echo -n ON > keystr
phone# echo -n <xxxxxxx> > serial_no
Where <xxxxxxx> is your serial number, found under the battery. Not sure if this did anything useful, but the serial number no longer indicated 0000000 after that.
6. I flashed cm-10.1 again from recovery, because I was experimenting with EFSPro, which requires busybox on the phone. EFSPro doesn't do much for you in this case. So I don't think this is important.
7. Try to recreate an nv_data.bin from the damaged partition! In order to do this I pulled the rebuilt default nv_data.bin from the phone and compared it to efs.img created in step 1.
Code:
linux# adb root
linux# adb pull /efs/nv_data.bin .
linux# xxd nv_data.bin > nv_data.hex
linux# xxd efs.img > efs.hex
Now inspecting the nv_data.hex, it started out like:
Code:
0000000: cccc cccc cccc cccc cccc cccc cccc cccc ................
0000010: cccc cccc cccc cccc cccc cccc cccc cccc ................
0000020: 4d21 5317 00a0 a2f7 1435 5799 529d 129b M!S......5W.R...
0000030: 48bd ca0e 6249 1367 37a5 96c3 39da 19ea H...bI.g7...9...
0000040: 0000 0000 e000 0000 0200 7400 6c00 0000 ..........t.l...
0000050: 0000 0000 0000 8130 0100 0000 0000 0000 .......0........
0000060: ffff ffff ffff ffff ffff ffff ffff ffff ................
0000070: ffff ffff 0200 0000 333a 3476 2020 2020 ........3:4v
0000080: 5350 3632 3630 5f4d 305f 4d4f 4445 4d5f SP6260_M0_MODEM_
0000090: 3033 2e31 3332 375f 4442 3133 3037 3032 03.1327_DB130702
00000a0: 2032 3031 332d 4a75 6c2d 3136 2032 303a 2013-Jul-16 20:
00000b0: 3035 3a33 3020 0a20 2020 2050 4442 5f4e 05:30 . PDB_N
00000c0: 4f54 5f41 5641 494c 4142 4c45 200a 0000 OT_AVAILABLE ...
I then searched for "MODEM" in efs.hex and found several similar entries. So for the next step, you might have to try a few times. I found one at address 0600000:
Code:
0600080: 5350 3632 3630 5f4d 305f 4d4f 4445 4d5f SP6260_M0_MODEM_
0600090: 3033 2e31 3234 315f 4442 3132 3130 3038 03.1241_DB121008
06000a0: 2032 3031 322d 4e6f 762d 3136 2031 343a 2012-Nov-16 14:
06000b0: 3030 3a34 3920 0a20 2020 2050 4442 5f4e 00:49 . PDB_N
06000c0: 4f54 5f41 5641 494c 4142 4c45 200a 0000 OT_AVAILABLE ...
I then extracted a block of data with the size of nv_data.bin from efs.img starting at this address:
Code:
linux# dd if=efs.img of=new_nv_data.bin skip=12288 count=4096
"skip" indicates the offset (0x0600000) and "count" the filesize (0x0200000). I now had a recreated old nv_data.bin.
8. Put the recreated nv_data.bin on the phone and delete backups.
Code:
linux# adb root
linux# adb shell
phone# cd /efs
phone# rm nv_data.bin
phone# rm .nv_data.bak
phone# rm .nv_core.bak
phone# adb push new_nv_data.bin /efs/nv_data.bin
I rebooted the phone and miracle oh miracle. I had my original IMEI back! Not sure if the phone is in optimal condition, but I can make calls and I have mobile data.
Hope any of this may be of any help to anyone. It took me quite a while to figure things out !!
Click to expand...
Click to collapse
dont work on my galaxy s3
Do not know what I did right
SD file transfer
Do
Command
Su
Sync
Reboot recovery
I pressed install file is shown getting error
Why?
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Hahaha do not understand what you record
Just realized that trying to install it.. why?
The stock recovery not install CM11 need to flash CWM or TWRP. To do this, first unlock the bootloader. Here is the topic http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
eta82 said:
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
Click to expand...
Click to collapse
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
eta82 said:
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
Click to expand...
Click to collapse
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
How do I install this example TWRP-d620.img
What do I do with this file?
I have ADB
There are all [=
Just what to do where to start an application I beg help me
Write me step by step how to do this request
You can also talk to me on Skype haimmalka85
haimmalka said:
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
Click to expand...
Click to collapse
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
eta82 said:
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
Click to expand...
Click to collapse
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
haimmalka said:
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
Click to expand...
Click to collapse
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
eta82 said:
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
Click to expand...
Click to collapse
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
haimmalka said:
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
Click to expand...
Click to collapse
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I'm going nuts who can help me it has been installed properly
https://www.youtube.com/watch?v=8aRrmxCOnQ0 It's okay to do the right directory request is made?
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
haimmalka said:
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
If you are using a terminal on the phone there is no need to connect the USB
eta82 said:
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
If you are using a terminal on the phone there is no need to connect the USB
Click to expand...
Click to collapse
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
To access the options developers have to tap 7-10 times is an option in Settings> Info About phone> Build number
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
OK I managed to figure out what to do
I'm stuck here
I did not get here just like what?
Continue?