I've been searching and searching and really couldn't find a clear answer.
I flashed my phone using method 1 as described in this thread http://forum.xda-developers.com/showthread.php?t=593786
Now I am seeing this other I guess they are android releases like http://forum.xda-developers.com/showthread.php?t=591104
They post these sqsh files. I already got my phone flashed and running Android is there a way I can upgrade or do whatever I need to do to use the sqsh file in the link I mentioned above? I can't find any clear instructions on how to do this really.
Thanks!
Yes, put the system.sqsh file on your SD card, and create a file called 'systemtonand', when you reboot, the bootloader should pick up that you want to transfer the file and do it automatically.
you may want to add blank file "cleardata" to delete your current data file to prevent conflicts (some system files store items in the data file that may not agree with another system file). there is a cache that, alternatively, can be cleared to avoid deleting your data file, have not tried this, another use posted it but I don't recall which thread.
This is a little tool I put together after a post I made on the Rom Customizer thread.
This is only for linux only at the moment, but its simple enough that i may be able to get a batch file for you windows guys.
it comes with everything needed-including the option to install java if you dont have it
What it does is this
1. pulls the specified apk
2. takes a baskup -you can restore to the backup by running the restore script.
3. replaces an image file in drawable-mdpi with the one you provide.
4. re-zips and re-signs the app
5.pushes the app back to either /system or /data
this has only been tested on pre-installed app, ie no market apps.
Its pretty simple but it could be helpful, so let me know what you think.
Extract the working folder to your desktop please.
Title says it all. I've seen this question asked but too many times I see people saying. "Use Search Function"
The search function has been scoured and I see plenty of great apps that restore and backup apps, contacts, etc.. none restore data WITHIN the apps.
Is there an app that backs up DATA within the apps not just the apps.
Thank you,
come again.
Titanium backup backs up my apps plus all system data
I'd like to know this too, with possible Rom coming in September I'm desperate to make the change over as smooth as possible.
post in general section
Mooved
Good question. I use MyBackup (online) for saving my data - but only sms-contacts..
If you find an app that save all you need, please post its name here ^^
thx
The process is quite complex (at least the way I do it) but it can be done!
Note: YOU NEED LINUX FOR THIS (or if you're brave you can mess with the tools on this site: http://www.chrysocome.net/download. success is not guaranteed. Still post about your experiences though )
Note: Steps 1 to 3 are not always necessary, it depends on which Android build you are using.
1) Give Root Explorer (or a similar file explorer app - must be able to access system/data files) root access
2) Locate the folders containing the user data you want to backup, this is usually somewhere near /data/data. The folders have various naming conventions and dont always contain the name of the app (i'll check and edit this post if i have time)
3) Change the folder's permission settings - I usually just permit everything
4) Shut down Android and in one way or another, mount your sd card on your Linux machine, and locate your data.img or userdata.img file.
5) Open a command line window, enter the following:
Code:
sudo mount -o loop data.img /mnt/data
Note: you might need to create the folder you are mounting too
Note: sudo not always neccesary
Note: change data.img to userdata.img, you'll know if this applies to you
6) Browse to the folder containing the data you want to backup and copy it onto your computer. DONE!
You can restore these backups on a different build by using the same method, just in reverse. Also, don't forget to check if the same folder already exists, if yes, it can be extremely annoying to find you dont have permission to change/overwrite it!
I used this to copy all of my saved games, i especially didn't want to loose my Asphalt 5 progress
P.S. if this solves your problem, please change the title of this thread to simplify things for other users
Thanks Kev007, I'll try this
filou75 said:
Thanks Kev007, I'll try this
Click to expand...
Click to collapse
While it is good to know how to do this stuff, just download Titanium from the market. It backs up all apps plus data in about a minute. You can restore individually or in batches using filters. Search around there is lots of info on this app.
It is great to learn some basic Linux stuff. It will help when you are trying to do things in Android. If you have no intention of learning Linux, Titanium is the way to go.
that be good actually - on my last android reinstall I lost my paper toss high score (allbeit only 3 pmsl) but still seems like a good thought considerin the games etc with save data.
Seconded - Titanium Backup preserves all my app data.
This is one of the reasons I love Android over WinMo - backing up app data is practically a nobrainer when you have the right tool.
+1 on Titanium Backup.
Works great on all builds. Just don't try to restore native HTC apps/data from sense to vanilla Froyo.
Kev007 said:
The process is quite complex (at least the way I do it) but it can be done!
Note: YOU NEED LINUX FOR THIS (or if you're brave you can mess with the tools on this site: http://www.chrysocome.net/download. success is not guaranteed. Still post about your experiences though )
Note: Steps 1 to 3 are not always necessary, it depends on which Android build you are using.
1) Give Root Explorer (or a similar file explorer app - must be able to access system/data files) root access
2) Locate the folders containing the user data you want to backup, this is usually somewhere near /data/data. The folders have various naming conventions and dont always contain the name of the app (i'll check and edit this post if i have time)
3) Change the folder's permission settings - I usually just permit everything
4) Shut down Android and in one way or another, mount your sd card on your Linux machine, and locate your data.img or userdata.img file.
5) Open a command line window, enter the following:
Code:
sudo mount -o loop data.img /mnt/data
Note: you might need to create the folder you are mounting too
Note: sudo not always neccesary
Note: change data.img to userdata.img, you'll know if this applies to you
6) Browse to the folder containing the data you want to backup and copy it onto your computer. DONE!
You can restore these backups on a different build by using the same method, just in reverse. Also, don't forget to check if the same folder already exists, if yes, it can be extremely annoying to find you dont have permission to change/overwrite it!
I used this to copy all of my saved games, i especially didn't want to loose my Asphalt 5 progress
P.S. if this solves your problem, please change the title of this thread to simplify things for other users
Click to expand...
Click to collapse
Now THIS is an answer. I knew I wasnt the only one trying to do this. I dont need to backup the APPS because I already have them backed up oin my PC.
My buddy has a linux box ill try this with. Thanks.
PS. To the titanium suggestions. I've tried that. Doesnt seem to save game states or 3rd party app preferences...
**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.
After rooting with Magisk, users of Moto G6 are faced with the “Stock Rom does not exist” error at the Restore Images step of Magisk’s OTA Upgrade Guide. However, the following suggestion was made in the discussion following issue #1870 on Magisk’s git-page:
The backups should be kept in /data (/data/stock_boot_<hash>.img.gz)
You could probably edit /sbin/.magisk/config to point to the backup you want by putting your <hash> after SHA1=
Click to expand...
Click to collapse
With Solid Explorer, I found different directories called /data in Root and in Internal Memory, but only the one in Root had a ./data/ subdirectory. Is that the one to which I should download the stock rom
ALI_RETAIL_9.0_PPSS29.118-15-11-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
which was posted in March, before the latest OTA release? Do I extract this zip, create an img.gz file from the .xml file and rename it stock_boot_<hash> before putting it there? Is <hash> blank-notation for any name that I give it, and which I then add after the “SHA1=” in /sbin/.magisk/config?
Finally, how do I edit the config file? I was able to get to it with Solid Explorer after checking the option to show hidden files in /sbin/. However, I couldn’t send this file to my computer by sharing it through email or messaging apps, as they all denied sending it. Apparently, it’s being blocked by anti-viruses. In this case, is there a safe way to transfer it to a computer, where I’ll be able to more comfortably edit it? Alternatively, if I just omit <hash> in naming stock_boot_.img.gz, can I leave config the way it is?
Best regards!