**VIDEO GUIDE ADDED BELOW**
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
(This should be done from stock 2.1 (JF6) but may not be required (got this to work while in phoenix 1.5 without reverting)- results may very in custom rom environments....
***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.
fyi this fix is intended specifically for persons with borked product codes and imei's due to custom rom flashes and will not address nv_data issues of carrier blocks/etc. for those who had unlocked their devices and may in fact undo your unlock.***
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
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. *Since i have good backups now on PC and external sd...i generally just edit the nv_data.bin file in place and save over the original in the efs folder.
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. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete all nv_data files from efs folder EXCEPT FOR YOUR NEWLY CREATED NV_DATA.BIN. (Delete the following: .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files. This differs from video but i also delete any .nv_state or nv.log file present and they are recreated). FYI IF YOU ARE USING A GINGERBREAD ROM AND YOUR EFS CONTAINS .nv_core.bak and .nv_core.bak.md5 DO NOT DELETE THEM with the other .nv files.
15. (This step may not be necessary unless you lose your voice/data connection upon reboot)
Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
**NEW: VIDEO GUIDE**
SPECIAL THANKS TO CONNEXION2005 for providing the video guide below:
http://www.youtube.com/watch?v=JqLK_2I-SBM&feature=player_embedded#!
-----------------------------------------------------------------------------
*DISCLAIMER*
have already had one person post a response that this thread was misleading and stating that:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Click to expand...
Click to collapse
I have seen other users make this claim as well, however, they are either mistaken or what i experienced was a complete anomoly.
I had never backed up my efs folder or nv_data files prior to them being messed up (i didn't know they were there and had never used root explorer to view them until i had to research a fix). The first thing i did was use a hex editor to look at my nv_data.bin and its bak(s) and in fact none of them were good. They all contained wrong product code.
So the process i described was conducted without any previously backed up original nv_data.bin or nv_data.bak files.
I started with:
wrong IMEI
wrong product code
totally botched nv_data files with no backup of original unmolested efs folder or nv_data files
I ended up with
Restored original IMEI
Correct Product Code
Healthy/Correct nv_data files that i immediately backed up in multiple locations.
So if you didn't back up your original untainted efs or nv_data files and this fix doesn't work to restore your original imei and product code then allow me to apologize in advance for "misleading" you and trying to assist with your problem by posting what did in fact work for me.
--------------------------------------------------------------------------------------------------------------
DONATIONS NOT REQUIRED OR EXPECTED. IF YOU FEEL THIS THREAD HAVE HELPED YOU WITH A SICKLY DEVICE OR SAVE YOU ANY HEADACHE OR TROUBLE FEEL FREE TO CONTRIBUTE:
bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***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. Terminal Emulator
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. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. 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).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efa/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
I think i deleted the file i wasnt supposed to... can someone post that file?
krips2003 said:
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
Click to expand...
Click to collapse
you should revert to stock to run this.
your welcome to try it with any rom you are using but i have only used it in stock jf6 as that was when i discovered the problem. I tried odin one click jf6 when i noticed both my product code and imei were wrong thinking go full stock reinstall would fix. No luck....with alot of reading i discovered one method of fixing the problem then also worked out the 2nd method that doesn't require adb or pc in case it needed to be done on the fly away from computer.
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
CapnPez said:
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
Click to expand...
Click to collapse
yes..thanks...duly noted and corrected
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
rwj5279955 said:
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
Click to expand...
Click to collapse
what are you looking @ your efs folder with? It shouldn't be empty...even if you had completely deleted your nv_data files when trying the other method there should have been other folders in /efs. You didn't cut and paste or move all the folders/files from efs (rather than copy) somewhere did you?
PS - aside from the files starting nv_ you should have two folders /efs/imei and /efs/.android
bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***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. Terminal Emulator
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. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. 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).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
KALI2000 said:
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
Click to expand...
Click to collapse
suspected would only work with stock. the generic id is less of an issue because i think as long as your product code isn't screwed in the nv_data files your original imei will restore upon reflash of stock.
One interesting thing and may be just luck. I had flashed all kinds of roms before and it usually changed the imei to the generic one but it was no big deal because it would restore when going back to stock (and the product code was never altered).
Since having them get messed up and doing this fix i have flashed multiple roms Axura, Assonance, Perception, Epsyl, and currently chronos and it has yet to alter my original imei in the process. Right now i am running chronos and it still has my original imei.
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post):
http://forum.xda-developers.com/showthread.php?t=786532
krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post and it contains links to both versions):
http://forum.xda-developers.com/showthread.php?t=786532
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
rwj5279955 said:
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
Click to expand...
Click to collapse
hope it helps. let me know your results when you get a chance.
I did a similar method, but only changed the AATT part in a hex editor and moved the file back with super manager, gave owner full chmod access, rebooted, made sure kies mini detected my device and then reflashed stock/master clear.
Now everything is back to normal.
I don't have an EFS folder and a search in Root explorer finds no nv_data.bin.
Apparently I flashed too many ROMS...lol
So ... As I can get my imei?
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
EDIT - apparently my statement is incorrect in regards to the captivate. I had been researching fixing my unlock that got relocked and many on the Vibrant forums have the generic IMEI with no way back. As of Jan-3-2011 - bames testing shows that changing the product code, does indeed fix the IMEI - I have to assume that the encrypted IMEI in the nv_data.bin is tied to the product code (maybe a pad or salt) and the phone can't read the IMEI if the product code changes.
Still, the best solution, before any modding, is to back up nv_data.bin.
alphadog00 said:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
from my own experience you are either mistaken or my result was an anomoly.
I had NEVER backed up my efs (had never used root explorer and didn't know the folder was even there prior to researching a fix) folder prior to having my imei, product code, and nv_data files messed up. (Once it was discovered and started researching a fix i used hex editors to view my nv_data files and both the original and BAK copies were messed up).
I ran the fixes and in fact my original IMEI and product codes were restored and in fact have remained in tact for each of the 4 or 5 times i have flashed new 2.2 roms after completing the fix. Right now i am running Chronos and still have my original IMEI (not a generic).
Once i saw the fix worked and i had healthy proper nv_data files the first thing i did was back up the entire efs folder in multiple places.
Related
before we start sorry for the horrible grammar, i'm not native to U.S. so its kind of a challenge (if anyone can put it together in good grammar I'd be happy to edit this post)
Disclaimer: this may cripple your phones sms and mms functionality do at own risk
Anyways after going crazy for the past 3 weeks, searching all of the internet and obviously getting lots of crap from people who have iPhones I finally figured out a fix for mms images to show up full size on t-mo usa.
p.s. be nice this is my first post and i'm trying to be helpful to those who ran into the same issue
Things needed:
- rooted dell streak 5 (running froyo)
- mms.apk from cyanogenmod nexus one rom (cm6.1.1)
- t-mobile sim card
- root explorer installed on phone
- memory card
The process
Step 1.
load the mms.apk file from cyanogenmod onto any folder on your memory card
Step 2.
use root explorer to navigate to following folder on your phone:
system/app
Step 3.
mount R/W (enable read/write)
scroll down until you find the file labeled "mms.apk" copy the file to a safe spot on your memory card
Step 4.
navigate into folder with cyanogenmod "mms.apk" file, cut and paste file into directory from step #2 ( enable r/w if needed, overwrite file already there)
Step 5.
press and hold on mms.apk file, scroll down to permissions, put a check mark on all 3 in top row(owner)
Step 6.
look within "/system/app" for a file right underneath the mms.apk, I'm not fully sure about the name as far as i recall the name began with "mmso...." delete this file.
Step 7.
Reboot your device
Step 8.
navigate back to system apps folder and install mms.apk as if it were a regular app (not sure if r/w permissions are needed here)
Step 9.
Reboot device, open up messaging app, press menu button then click settings.
scroll down til you see "custom user agent" selection, select nokia n95 from the menu.
Step 10.
give yourself a pat on the back if everything worked correctly and you get full size mms
Notes:
-the device i'm using is an aws version of the streak mini not sure if this would work for unlocked streaks
I'm just taking what txlibre wrote in http://forum.xda-developers.com/showthread.php?t=1715149 and re-displaying it in a format that I think is easier to understand for n00bs
This really isn't that hard TBH IMO
This worked for me on a GS3 locked to Orange UK, and another locked to Three UK. Your Mileage May Vary!!
-----I cannot be held responsible for anything that happens to you or your phone, from carrying out anything I have said!-----
Credits: txlibre, mskip, the person whoever originally wrote these instructions
----------------------------------
VIDEO GUIDE:
Part 1 (A-E) - http://youtu.be/P1H2yUyQ4J8
Part 2 (1-25) - http://youtu.be/uAVbYx68WI4
----------------------------------
Things to do before starting:
A - Make sure your S3 is rooted (http://forum.xda-developers.com/showthread.php?t=1703488).
B - Make a backup copy of the /efs folder on your PC.
C - Also backup your EFS using mskips ToolKit (http://forum.xda-developers.com/showthread.php?t=1703488).
D - Get a Hex Editor (I used Notepad++ with this plugin: http://sourceforge.net/projects/npp...n v0.9.5/HexEditor_0_9_5_UNI_dll.zip/download (just put the dll in the plugins folder of Notepad++)).
E - Install Root Explorer on your phone.
Now for the actual process:
1 - Using Root Explorer, copy the file nv_data.bin file from your phones /efs folder to your PC and open it in Notepad++.
2 - Scroll down and find address 00181460, modify the 01 to 00.
3 - Save the file.
4 - Copy the modified nv_data.bin from your computer back to your phones /efs folder using Root Explorer.
.....(Make sure you keep a copy of this modified file for step 15.)
5 - Once copied to the phone, open Root Explorer and long press on the nv_data.bin file till the menu pops up and select 'Permissions'.
6 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked, and press OK.
7 - Then again, long press on the nv_data.bin file till the menu pops up, and select 'Change owner'.
8 - Change Owner and Group to 1001-Radio and press OK.
9 - Restart your phone.
10 - Once restarted dial *#7465625#, check Network Lock is ON and press OK.
11 - Using Root Explorer, copy the file nv.log from your phones /efs folder to your PC and open it.
12 - You should see something like:
... ..Mon Jun 18 23:34:32 2012: MD5 fail. orignal md5 'e1493854d4d62ff4e123040855f8b2a9' computed md5 'd29d791b193de8b6711445231fb7d427' (rild)
.. ...Mon Jun 18 23:34:32 2012: backup NV restored.
... ..(Your numbers may differ).
13 - Copy the file nv_data.bin.md5 from your phones /efs folder to your PC and open it.
... ..You should see the first number listed in step 12 (in my case e1493854d4d62ff4e123040855f8b2a9).
14 - Copy the second number in step 12 (in my case d29d791b193de8b6711445231fb7d427) and put in the nv_data.bin.md5 file, so it is the only number in there. Now save the file.
15 - Now copy the modified nv_data.bin file (from step 4) and the modified nv_data.bin.md5 (from step 14) back to your /efs folder on your phone.
16 - Once copied, long press on the nv_data.bin file till the menu pops up and select 'Permissions'.
17 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked and press OK.
18 - Then again long press on the nv_data.bin file till the menu pops up and select 'Change owner'.
19 - Change Owner and Group to 1001-Radio and press OK.
20 - Now, long press on the nv_data.bin.md5 file till the menu pops up and select 'Permissions'.
21 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked and press OK.
22 - Then again long press on the nv_data.bin.md5 file till the menu pops up and select 'Change owner'.
23 - Change Owner and Group to 1001-Radio and press OK.
24 - Restart your phone.
25 - Once restarted dial *#7465625# and check Network Lock is OFF and press OK.
anyone tried this
This is the exact same process I used to unlock my gs2. Unless the address where you modify the the byte is off, I see no reason why this wouldn't work on a gs3.
Sent from my SGH-I897 using Tapatalk 2
any pictures for step 14 or is it pretty self explanatory when you do do it. can you paste it anywhere ?
mox123 said:
anyone tried this
Click to expand...
Click to collapse
I have tried this, and on the original thread, 3 others have used is successfully.
I used this on my wife's phone last night and I'll use it on mine this morning when I get it. Ill do a video
galaxy.S3 said:
any pictures for step 14 or is it pretty self explanatory when you do do it. can you paste it anywhere ?
Click to expand...
Click to collapse
I'll hopefully get a video up later today or tomorrow
can this be undone for warranty if a repair is required.
I'll wait till you post a video.
Sent from my SGH-T769 using XDA Premium App
reaths17 said:
can this be undone for warranty if a repair is required.
Click to expand...
Click to collapse
I would say all you would have to do is repeat the process but in step 2, just overwrite the 00 with a 01.
I will try it out when I get my own GS3 later.
Video guide is up guys
the second vid has been taken down
also, i can't get notepad++ to read the file, it just looks like a load of symbols and no actual text. Any help would be appreciated.
dumb donkey said:
the second vid has been taken down
also, i can't get notepad++ to read the file, it just looks like a load of symbols and no actual text. Any help would be appreciated.
Click to expand...
Click to collapse
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
vinokirk said:
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
Click to expand...
Click to collapse
Great...! was able to unlock the phone without the video; just followed the instruction and voila I'm now sim unlock...
vinokirk said:
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
Click to expand...
Click to collapse
i've got notepad++ showing the dll file and also reinstalled it though plugin manager in notepad++ but still the same?
dumb donkey said:
i've got notepad++ showing the dll file and also reinstalled it though plugin manager in notepad++ but still the same?
Click to expand...
Click to collapse
You have to put the .DLL file you just download to this folder of your computer :
C:\Program Files (x86)\Notepad++\plugins...(If that is your installation folder of course)
And Go to:
1.Plugins
2.HEX editor
3.View in Plugin
In Notepad++ bar
armanderli said:
You have to put the .DLL file you just download to this folder of your computer :
C:\Program Files (x86)\Notepad++\plugins...(If that is your installation folder of course)
And Go to:
1.Plugins
2.HEX editor
3.View in Plugin
In Notepad++ bar
Click to expand...
Click to collapse
Thats done it! Thanks bud!
---------- Post added at 06:54 PM ---------- Previous post was at 06:14 PM ----------
Just putting my experience out there for anyone who comes across what i did.
Neither of my nv.log numbers matched the one from the nv_data.bin.md5, but i copied the second number anyway and put ONLY that one in the nv_data.bin.md5 file and follwed the rest of the instructions and it still worked!
I am now on a sim unlocked phone!
Thanx!
EDIT!! i'm currently having problems with 2 efs folders and tthe phone stuck in factory mode. i dont recoment changing if you come across what i did!
EDIT 2! Phone back to normal after i restored original efs folder.. but back to network lock on!
Thanks for taking the time to write this thread, as I have justed ordered a S3 which is locked to the 3 network. So will use your guide when I receive the phone, and save me £10 paying to get the code.
One quick question though, when you say download "root explorer" for a few pence, are you referring to the Root Explorer (File Manager) app at £3?
The other ones that come up are all free, so I assume these wont work with the below process?
dumb donkey said:
Neither of my nv.log numbers matched the one from the nv_data.bin.md5, but i copied the second number anyway and put ONLY that one in the nv_data.bin.md5 file and follwed the rest of the instructions and it still worked!
Click to expand...
Click to collapse
This is also what happened to me when I unlocked my phone. Once the video is up, you'll see
djglenn1337 said:
Thanks for taking the time to write this thread, as I have justed ordered a S3 which is locked to the 3 network. So will use your guide when I receive the phone, and save me £10 paying to get the code.
One quick question though, when you say download "root explorer" for a few pence, are you referring to the Root Explorer (File Manager) app at £3?
The other ones that come up are all free, so I assume these wont work with the below process?
Click to expand...
Click to collapse
I got it for 64p. It must've been a special offer.
dumb donkey said:
EDIT 2! Phone back to normal after i restored original efs folder.. but back to network lock on!
Click to expand...
Click to collapse
I'd try it from the top again.
Make sure you know which files you've modified already and which ones you haven't. The first time i did it, the phone didn't unlock. I found out it's because i copied across an unmodified bin file, doh!
have a recently rooted nexus 4.2.2 and did a nandroid backup using clockwork recovery. clockwork stored it into a directory which i can't access by just plugging my phone to the usb cable of my pc. i do see folders, but not that particular folder. i have usb debugging option turned on also. i just wanted to transfer the backup files to my pc for storage. is there a way to do this? thank you.
konoplya said:
have a recently rooted nexus 4.2.2 and did a nandroid backup using clockwork recovery. clockwork stored it into a directory which i can't access by just plugging my phone to the usb cable of my pc. i do see folders, but not that particular folder. i have usb debugging option turned on also. i just wanted to transfer the backup files to my pc for storage. is there a way to do this? thank you.
Click to expand...
Click to collapse
You can't see it because windows can't access those folders. You can either move the backups using a file explorer to a folder windows can access, pull the files using ABD or if you have the paid version of ROM Manager you can download the files to your pc using a browser.
I figured it was something of that nature. However I have downloaded different file explorers including the es file explorer and I still can't see the folders on my phone even, not just pc. But when I boot into clockwork recovery and browse through there I can see those folders. I'm at a loss.
konoplya said:
I figured it was something of that nature. However I have downloaded different file explorers including the es file explorer and I still can't see the folders on my phone even, not just pc. But when I boot into clockwork recovery and browse through there I can see those folders. I'm at a loss.
Click to expand...
Click to collapse
With ES File Explorer I had to turn on the root explorer option in the settings, the world and phone icon at the top left..
kzoodroid said:
With ES File Explorer I had to turn on the root explorer option in the settings, the world and phone icon at the top left..
Click to expand...
Click to collapse
yes, i did that as well, but it still doesn't let me see the directories that i see in clockwork. the directories i'm talking about are in /sdcard.. they are
- 0/
- clockworkmod/
- legacy/
- obb/
the only ones i can see are 0/ and legacy/. if i go to 0/ i can see what i normally see in the pc windows explorer. there is also a folder called clockworkmod/ but it only contains the folder called download/ and a couple of files under 100kb.
also, when i'm viewing the folders in ES file manager the sdcard folder has a little shortcut arrow on it instead of a solid folder like most of the other ones.
I can't speak for the intricacies of Clockworkmod as I have never used it, but after doing either a TWRP backup or a Titanium backup on 4.2.2, I have always been able to copy and/or view these backup files using any of the following methods, as well as verifying that they are equivalent (Same exact number of files, same exact file sizes):
1) Copying the files from the Nexus 4 to Windows 7 64 bit Professional using Microsoft Windows Explorer.
2) Copying the files from the Nexus 4 to Windows 7 64 bit Professional by performing an "adb pull".
3) Viewing the files with the Android ES Explorer app (With the "Root Explorer" option turned on and changing the top directory to root or "/").
4) Viewing the files in TWRP.
I also use the full path to the files (when possible). As I recall, there were instances where not all the files were visible if I didn't use the full path. Replacing /0 with /legacy on Android 4.2:
TWRP BACKUP
/data/media/0/TWRP/BACKUPS/<PHONE SERIAL# HERE>/<FILE BACKUP SUBDIRECTORY HERE>/
TITIANIUM BACKUP
/data/media/0/TitaniumBackup/
In fact I just performed all four of these methods a couple of minutes ago because I was originally having problems with Android 4.3 (Not all files being transferred over due to the known permission changes with 4.3), and I wanted to double check that everything is still working properly now. What solved all my issues with 4.3 was to update all my programs to “4.3 friendly” versions (You could see if this resolves your 4.2.2 issues as well):
1) Installed the latest version of TWRP.
2) Unrooted using the latest version of Superuser.
3) Installed the latest Android SDK and then ran the SDK Manager to insure everything was up to date.
a) Deleted my Windows driver and installed the latest Google USB driver from the SDK.
b) Used the new updated platform tools to perform fastboot, adb, etc.
pjc123 said:
I can't speak for the intricacies of Clockworkmod as I have never used it, but after doing either a TWRP backup or a Titanium backup on 4.2.2, I have always been able to copy and/or view these backup files using any of the following methods, as well as verifying that they are equivalent (Same exact number of files, same exact file sizes):
1) Copying the files from the Nexus 4 to Windows 7 64 bit Professional using Microsoft Windows Explorer.
2) Copying the files from the Nexus 4 to Windows 7 64 bit Professional by performing an "adb pull".
3) Viewing the files with the Android ES Explorer app (With the "Root Explorer" option turned on and changing the top directory to root or "/").
4) Viewing the files in TWRP.
I also use the full path to the files (when possible). As I recall, there were instances where not all the files were visible if I didn't use the full path. Replacing /0 with /legacy on Android 4.2:
TWRP BACKUP
/data/media/0/TWRP/BACKUPS/<PHONE SERIAL# HERE>/<FILE BACKUP SUBDIRECTORY HERE>/
TITIANIUM BACKUP
/data/media/0/TitaniumBackup/
In fact I just performed all four of these methods a couple of minutes ago because I was originally having problems with Android 4.3 (Not all files being transferred over due to the known permission changes with 4.3), and I wanted to double check that everything is still working properly now. What solved all my issues with 4.3 was to update all my programs to “4.3 friendly” versions (You could see if this resolves your 4.2.2 issues as well):
1) Installed the latest version of TWRP.
2) Unrooted using the latest version of Superuser.
3) Installed the latest Android SDK and then ran the SDK Manager to insure everything was up to date.
a) Deleted my Windows driver and installed the latest Google USB driver from the SDK.
b) Used the new updated platform tools to perform fastboot, adb, etc.
Click to expand...
Click to collapse
the thing is i can't see the directories that the files are in. either in file explorer or in windows. i need to get more familiar with adb and maybe do it through that, but its strange because i should be able to see them in the explorer. so essentially i have a nandroid backup on my phone that i can't really access to move it or delete it. i can only access it through clockwork recovery. also, all the stuff i used is the latest versions i.e. sdk, drivers, etc.
Then I am at a loss if you tried all the things mentioned. If it is a permission issue, then adb should bypass that problem. The adb executable is located in the platform-tools subdirectory of the SDK. You run the "adb pull" command from a "Command Prompt" window while located in that directory. The nandroid copy will take quite a while, so wait until it is finished (For example, my latest one was 330 MB in size).
While the phone is in recovery, here are some examples of grabbing the TWRP and TITANIUM backup files and putting them into the directories TWRP_BACKUP and TITANIUM_BACKUP respectively (That I previously created) on the windows "C" drive. As before, you would probably be replacing /legacy for /0:
adb pull /data/media/0/TWRP/BACKUPS/<PUT SERIAL # OF PHONE HERE>/<PUT DATE OF BACKUP HERE>/ C:\TWRP_BACKUP\
adb pull /data/media/0/TitaniumBackup/ C:\TITANIUM_BACKUP\
konoplya said:
yes, i did that as well, but it still doesn't let me see the directories that i see in clockwork. the directories i'm talking about are in /sdcard.. they are
- 0/
- clockworkmod/
- legacy/
- obb/
the only ones i can see are 0/ and legacy/. if i go to 0/ i can see what i normally see in the pc windows explorer. there is also a folder called clockworkmod/ but it only contains the folder called download/ and a couple of files under 100kb.
also, when i'm viewing the folders in ES file manager the sdcard folder has a little shortcut arrow on it instead of a solid folder like most of the other ones.
Click to expand...
Click to collapse
Clockworkmod puts the backups in a secure system folder with the path mnt/shell/emulated/clockworkmod/backup. In ES File Explorer hit the "/" at the top which will open up "device" and now you will see all of your system folders. Root Explorer is a simpler app to use as it only has two directory options, root and storage. I bought both apps a long time ago as I liked that ES File Explorer lets you connect to a lan to upload/download files through wifi.
pjc123 said:
Then I am at a loss if you tried all the things mentioned. If it is a permission issue, then adb should bypass that problem. The adb executable is located in the platform-tools subdirectory of the SDK. You run the "adb pull" command from a "Command Prompt" window while located in that directory. The nandroid copy will take quite a while, so wait until it is finished (For example, my latest one was 330 MB in size).
While the phone is in recovery, here are some examples of grabbing the TWRP and TITANIUM backup files and putting them into the directories TWRP_BACKUP and TITANIUM_BACKUP respectively (That I previously created) on the windows "C" drive. As before, you would probably be replacing /legacy for /0:
adb pull /data/media/0/TWRP/BACKUPS/<PUT SERIAL # OF PHONE HERE>/<PUT DATE OF BACKUP HERE>/ C:\TWRP_BACKUP\
adb pull /data/media/0/TitaniumBackup/ C:\TITANIUM_BACKUP\
Click to expand...
Click to collapse
i'll play around with that when i get home. thank you.
kzoodroid said:
Clockworkmod puts the backups in a secure system folder with the path mnt/shell/emulated/clockworkmod/backup. In ES File Explorer hit the "/" at the top which will open up "device" and now you will see all of your system folders. Root Explorer is a simpler app to use as it only has two directory options, root and storage. I bought both apps a long time ago as I liked that ES File Explorer lets you connect to a lan to upload/download files through wifi.
Click to expand...
Click to collapse
i have root explorer that i purchased a couple years ago as well. doesn't show me the path you mention. neither does the ES File Explorer. this is why it puzzles me since my phone is rooted. when i look in ES File Explorer and choose "/" as my starting point, i do see all the folders, however, the clockworkmod folder doesn't contain the "backup" folder. it has only "download" folder and a couple of files ".recovery_version" and ".settings".. nothing else.
konoplya;45563381i have root explorer that i purchased a couple years ago as well. doesn't show me the path you mention. neither does the ES File Explorer. this is why it puzzles me since my phone is rooted. when i look in ES File Explorer and choose "/" as my starting point said:
You can't see /mnt in the root directory? Are you sure your phone is still rooted? Open up your superuser app and see if both ES File Explorer and Root Explorer are listed. On my phone in the mnt/shell/emulated folder I have 4 files, 0, clockworkmod, legacy, and obb.
Click to expand...
Click to collapse
kzoodroid said:
You can't see /mnt in the root directory? Are you sure your phone is still rooted? Open up your superuser app and see if both ES File Explorer and Root Explorer are listed. On my phone in the mnt/shell/emulated folder I have 4 files, 0, clockworkmod, legacy, and obb.
Click to expand...
Click to collapse
I posted picks of the folders in ES File Explorer. In the clockworkmod folder I have 2 subfolders, download and backup.
kzoodroid said:
I posted picks of the folders in ES File Explorer. In the clockworkmod folder I have 2 subfolders, download and backup.
Click to expand...
Click to collapse
I looked in su and I have three apps listed there: root explorer, titanium backup, and es file explorer. I don't see those folders that you have in your screenshots. What app do you use for that? I'll take a screenshot of what I have.
Edit: I reinstalled the file explorer and rebooted the phone and I can see the mnt directory now. Don't know why it wasn't showing up. Thank you for the help.
Sent from my Nexus 4 using xda app-developers app
konoplya said:
I looked in su and I have three apps listed there: root explorer, titanium backup, and es file explorer. I don't see those folders that you have in your screenshots. What app do you use for that? I'll take a screenshot of what I have.
Edit: I reinstalled the file explorer and rebooted the phone and I can see the mnt directory now. Don't know why it wasn't showing up. Thank you for the help.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Glad you got it worked out. To take screen shots press and hold the power button and volume down at the same time. My photos automatically upload to dropbox and I just attached them from there to my post.
kzoodroid said:
Glad you got it worked out. To take screen shots press and hold the power button and volume down at the same time. My photos automatically upload to dropbox and I just attached them from there to my post.
Click to expand...
Click to collapse
thats badass. thanks!
Happened to me aswell
all you need to do is go into your file browser on your phone and then move the file somewhere else while still connected to the pc.. should be good then
Hi all,
I've decided to try and copy my nandroid backup that I made the other day (first ever since I've just rooted my phone) to my PC.
Long story short, I attempted to use Root explorer to cut and paste the backup's folder into a folder that is visible on my PC so I could get a copy onto my PC, and then cut and paste the nandroid back into its original folder (tedious, but I don't have enough space to have 2 copies of the nadroid on my phone at the same time). This, however, fails, and I can't see the backup folder in the folder that I can see on my PC despite it being visible in this same PC-visible folder via root explorer after its supposedly pasted it.
So I went via option 2, using ADB to pull the folder.
After another amount of research I found a path that does pull the folder (mnt/shell/emulated/clockworkmod/backup .... data/media/clockworkmod/backup = remote object doesn't exist error).
It appears to pull the folder successfully (an identically named folder appears in "platform tools" folder on my PC), however the size of this pulled folder is only ~500mb, and I'm certain the nandroid backup took up at least 3-4GB on my phone after it was created.
The pulled folder also doesn't show all the files that I can see within the nandroid backup's folder via root explorer.
I did notice the "read-only" checkbox of the pulled folder appears filled in, which I take it means not all files in the folder have read-only properties. Is it possible there are (still) hidden files within the pulled folder that would account for the difference in size and number of visible files compared to the original nandroid folder on the phone?
any clarificaion of this would be good - I'm keen to have a copy of my backup on my PC as a safeguard, but this scenario has baffled me despite an hr's worth of research
No one?
Surely someone has an idea about this..
I have experienced incomplete adb pulls also, and so I just stick to using MTP from within Windows. It's the only way for mention ensure a complete copy.
Sent from my Nexus 4 using XDA Free mobile app
lolcakes203 said:
I have experienced incomplete adb pulls also, and so I just stick to using MTP from within Windows. It's the only way for mention ensure a complete copy.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
How are you doing this?
I use cwm and the backup folder isn't visible if I use mmtp (Windows file explorer etc), hence why I'm having to use other methods.
salxtai said:
How are you doing this?
I use cwm and the backup folder isn't visible if I use mmtp (Windows file explorer etc), hence why I'm having to use other methods.
Click to expand...
Click to collapse
It's possible that the computer and phone may be calculating file sizes differently. I would check the MD5 sums to see if they are the same on the computer and phone rather than guessing
lopezk38 said:
It's possible that the computer and phone may be calculating file sizes differently. I would check the MD5 sums to see if they are the same on the computer and phone rather than guessing
Click to expand...
Click to collapse
Apologies for my ignorance, but I've been searching how to do this via Google and I must be really dumb because I'm not following how to do md5 checks. Could you explain it please?
salxtai said:
Apologies for my ignorance, but I've been searching how to do this via Google and I must be really dumb because I'm not following how to do md5 checks. Could you explain it please?
Click to expand...
Click to collapse
For Windows you need to download a program to check MD5. Microsoft has one available here, although it is a command line operated program. There are other programs that have a GUI for checking MD5 if you don't want to bother with the command line.
On your phone, using your file explorer and long pressing the backup should give you the option somewhere to calculate MD5 sums (Probably in properties). I don't know if root explorer does, I've never used it before, but I use Solid Explorer which does give me the option to calculate MD5 in the properties menu
I'm not sure why you're backup folder isn't visible, when I connect though USB, all my SD card folders are shown, including the CWM Folder.
Sent from my Nexus 4 using XDA Free mobile app
lopezk38 said:
For Windows you need to download a program to check MD5. Microsoft has one available here, although it is a command line operated program. There are other programs that have a GUI for checking MD5 if you don't want to bother with the command line.
On your phone, using your file explorer and long pressing the backup should give you the option somewhere to calculate MD5 sums (Probably in properties). I don't know if root explorer does, I've never used it before, but I use Solid Explorer which does give me the option to calculate MD5 in the properties menu
Click to expand...
Click to collapse
After a while of trying to work out the command line, I've think I've got it (but would like confirmation that this is correct).
- Pointed the fciv.exe command to the nandroid.md5 file located in the backup folder I had pulled from the phone via ADB
- using Solid explorer (root explorer also has this but I only worked this out after I worked out that I had look at the properties of the .md5 file itself w/in the explorer app, rather than the whole folder), I found the MD5 sum from within the backup folder
-- verdict: both numbers outputted by each source match.
Now my next question is, if I were to delete the backup on my phone, how do I go about putting it back into the "hidden" CWM backup folder where it came from later?
(seeing as I wasn't able to copy it using root explorer, and can't see the folder via MTP on my PC)
lolcakes203 said:
I'm not sure why you're backup folder isn't visible, when I connect though USB, all my SD card folders are shown, including the CWM Folder.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I have no idea either, and its really really annoying me.
Have you made some sort of permission changes to the folder/s themselves?
I have "show hidden folders" enabled under view options in windows explorer and have tried "show system folders", but that hasn't resovled it.
salxtai said:
After a while of trying to work out the command line, I've think I've got it (but would like confirmation that this is correct).
- Pointed the fciv.exe command to the nandroid.md5 file located in the backup folder I had pulled from the phone via ADB
- using Solid explorer (root explorer also has this but I only worked this out after I worked out that I had look at the properties of the .md5 file itself w/in the explorer app, rather than the whole folder), I found the MD5 sum from within the backup folder
-- verdict: both numbers outputted by each source match.
Now my next question is, if I were to delete the backup on my phone, how do I go about putting it back into the "hidden" CWM backup folder where it came from later?
(seeing as I wasn't able to copy it using root explorer, and can't see the folder via MTP on my PC)
Click to expand...
Click to collapse
You can use ADB push in recovery the folder. Just make sure you mount /data
I do have those settings enabled in control panel, but aside from that I'm not sure what else could be there. In terms of USB settings, I have USB debugging enabled in developer options, and in the storage menu I have mtp selected, not the other one. I think that is all the USB settings that I have changed.
Sent from my Nexus 4 using XDA Free mobile app
salxtai said:
I have no idea either, and its really really annoying me.
Have you made some sort of permission changes to the folder/s themselves?
I have "show hidden folders" enabled under view options in windows explorer and have tried "show system folders", but that hasn't resovled it.
Click to expand...
Click to collapse
The CWM backup folder shouldn't be able to be accessed with MTP. Android only allows you to access your user's folder (You can only have multiple users on tablets, but the user based file structure is still there) through USB. User folders have a number attached to them to mark which user they are for, which is why you have that folder named 0 with all your stuff in it, because you are user #0. Since CWM backups are saved in a separate branch, Android does not make them available to USB for security reasons. lolcakes203 probably has a modified version of CWM (Or you can change the save directory in CWM? I haven't used CWM in forever), or he has TWRP which saves backups in your user folder so you can access them through USB
Ahh yes I am using PhilZ CWM and that may be why I can see the backup.
Sent from my Nexus 4 using XDA Free mobile app
lopezk38 said:
You can use ADB push in recovery the folder. Just make sure you mount /data
Click to expand...
Click to collapse
Sorry, not sure I'm following the command line instructions - how would this command line look in full?
Long story short : I needed to get my sms from my old motoG and transfer them to my new motoG5. Here is how:
This can be done without any third part app, only a capable recovery and adb is needed.
Get your old SMS
take you Nand backup you hopefully did before your device died.
find the mmssms.db file that you can find in :
Code:
data.f2fs.win000
Use :
Code:
tar –xf data.f2fs.win000.tar.gz
Android 6:
Code:
/data/data/com.android.providers.telephony/databases/
Android 7:
Code:
/data/user_de/0/com.android.providers.telephony/databases/
Copy mmssms.db to your computer.
Import your database to your new device
==> root is needed for that operation
Push mmssms.db to your device (depending on you android version, see above)
e.g.:
Code:
adb push ./mmssms.db /data/user_de/0/com.android.providers.telephony/databases/mmssms.db
Delete any journal.db you may find in the same folder.
Wipe cache and art-cache
Reboot.
Delete sms-mms application data
Start the sms-mms app
Voilà!
An alternative way that doesn't require root is available here. (thx to @Mirhawk)
also thx to @dlegit for the new directory.
If you could convert the db file into xml format you should be able to use an app to restore without needing root
Edit
Just noticed you posted another guide which mentions that
TheFixItMan said:
If you could convert the db file into xml format you should be able to use an app to restore without needing root
Edit
Just noticed you posted another guide which mentions that
Click to expand...
Click to collapse
Yeap, I just wanted to do it without third party software
I didn't say this 'how to' is super useful, I just shared the way I did it.