Related
If I saved all my Android files on my computer from a previous build, can I somehow get the contacts out of them files ? perhaps there's a file that contains all contacts ?
log into your gmail and extract them that way
That's the weird part, for some reason the number I'm looking for wasn't logged by Gmail, and that's why with the current build I didn't have his number imported as the rest.
The contacts are stored in a SQLite3 database file so the file format is ".db"
The development tool Android Debug Bridge (ADB) can be used to extract the file from an EMULATOR
ADB can also extract the file from a phone but it must be rooted first AND the ADB drivers must be installed on your machibe as well
(Rooting is NOT for beginners though)
The contacts.db file is stored in the protected system memory, the file path is:
data/data/com.android.providers.contacts/databases/contacts.db
itsme_4ucz said:
The contacts are stored in a SQLite3 database file so the file format is ".db"
The development tool Android Debug Bridge (ADB) can be used to extract the file from an EMULATOR
ADB can also extract the file from a phone but it must be rooted first AND the ADB drivers must be installed on your machibe as well
(Rooting is NOT for beginners though)
The contacts.db file is stored in the protected system memory, the file path is:
data/data/com.android.providers.contacts/databases/contacts.db
Click to expand...
Click to collapse
If I understood correctly this file should be in the SD card, but I cannot find one, nor the directory /com.android.providers.contacts/ .
Your phone doesnt think its on the sdcard. It thinks its on the phone itself.
For my adb uses I use a program called android commander. It will allow you to navigate to that file.
Try using root explorer app, it will get you there...
My issue is not with the contacts on my working phone system, but on the files I copied before I've change to a new build. I thought there may be a chance it's on one of those files, but it sound much complicated then that.
If you don't want to try itsme_4ucz's solution, why not copy the files back to your phone and sync again with Gmail?
Because for some reason the build didn't load, that was the reason why I switched builds in the first place.
I don't want to root my phone for that, I'm pretty noob
I could be wrong, but...
Wouldn't that file be in the data.img file system image? If so, you can mount that file in Linux, or most likely Windows, then browse to the location mentioned above.
That'll at least get you there, but you still have to get the data out. Perhaps copy that one to the phone's current file system. If not, I'm sure someone will come up with something if the above posts don't work.
Can anyone throw the commands on how to create a .img file of the system and boot. Moto dosent see the need to post them for some reason so I was hoping there was an easy way to pull the info and create the files myself.
I'm looking for a guide which tells how to make a own custom ROM from another one
I mean:
1. How to add/replace/remove apps in /system/app/?
1. a) Do they need to have special permission?
2. How to replace boot screen?
3. How to add custom kernel?
4. How to add Desire lockscreen/flip clock?
5. How to add transparent notofication area?
6. How to add Power menu?
I've been serching forum, but didn't find such tutorial. Would be very thanful to get this knowledge.
I think that will be very useful for maaaany android maniacs
1. Simple delete/copy apks in .zip file using 7-Zip or any other.
2. I belive you need to put bootanimation.zip in /data/local/ folder.
3. Idk
4. For Desire lockscreen you need edited HtcLockScreen.apk; for flip clock - HtcClockWidget.apk
5. Edited /system/framework-res.apk or /system/framework/com.htc.resources.apk. I'm not sure
6. You need edited /system/framework/android.policy.jar
69. Resign your zip file using Auto Sign
Attachment doesn't load, but I know about resigning ROM after everything is done
Ad. 1. As I thought, but do the need special permissions? And I also wonder one thing. Are they installed while flashing? Cuz they need to be in system registry, I think...
I have found this: http://wiki.android.com.pl/wiki/Kon...iana_instalowanych_aplikacji_razem_z_systemem
No any permissions etc.
Found this, too. Thanks.
to add a custom kernel you have to unpack the boot image and edit the ramdisk manually, although i think there is an option in dsixda's kitchen to unpack and repack the boot.img
I've got two more questions:
1. When signing, three files are created in folder META-INF: CERT.RSA, CERT.SF, MANIFEST.SF. But in other packages I see also com/google/android/update-script in META-INF. How to make it? Is it necessary?
2. If I want to make only flashable update file which changes one app or another file, eg. framework-res.apk, I have to create folder structure: system/framework/framework-res.apk, add it to zip archive (no compression?) and sing using Auto-sing. Am I right?
Edit:
Found nice guide there: update-script syntax
tomekk_nt said:
I've got two more questions:
1. When signing, three files are created in folder META-INF: CERT.RSA, CERT.SF, MANIFEST.SF. But in other packages I see also com/google/android/update-script in META-INF. How to make it? Is it necessary?
2. If I want to make only flashable update file which changes one app or another file, eg. framework-res.apk, I have to create folder structure: system/framework/framework-res.apk, add it to zip archive (no compression?) and sing using Auto-sing. Am I right?
Click to expand...
Click to collapse
The most important part of a recovery update zip is the update script. It will tell the recovery what to do. If you want an example of a basic update package, which replaces one file in the /system/framework (although a different one) can found here. Open this and read the META-INF/com/google/android/updater-script (or whatever its called). The syntax is pretty straight forward and I think its easiest to learn from the examples of updater scripts found here on XDA. For the simple case, of only replacing/adding files to the /system partition you can leave the updater script from the above example as is and only change the files under the /system directory in the zip.
Note, that the above example uses the newer upader-script (I hope I am writing this correctly, I am writing from memory) which also has a binary file in the same directory. Some update zips use the older "update-script" lone text script. For these kind of scripts, you can find a guide here.
Personally, I use RA recovery, and for this recovery you need to sign the update zips (last thing you do of course). At least for RA recovery, both the older "update-script" and the newer "updater-script" work fine, so its up to your personal preference which do you prefer.
Thanks. Found a guide you mentioned a couple of minutes ago and read it.
The more I know, the more questions it brings So one more thing. If I'd like to use the newer version of syntax: "updater-script", I need also to put this binary file in this folder. But I create/edit only "updater-script", binary file is the same for all packages, or do I need to edit it, too?
I built a kernel tool long time ago, very easy to use (only for linux)
1: unzip the file, place it where you want it eg your desktop
2: place boot.img in the working directory
3: double-click the menu icon or launch from terminal
4: it creates a new directory named BOOT-EXTRACT,edit what you want in there or change the kernel etc.. and repack it again via the kernel tool
see screenshot. here for those how want the tool >>> http://www.elelinux.se/tools/kernel_tool.zip
Edit: Only for Hero
tomekk_nt said:
Thanks. Found a guide you mentioned a couple of minutes ago and read it.
The more I know, the more questions it brings So one more thing. If I'd like to use the newer version of syntax: "updater-script", I need also to put this binary file in this folder. But I create/edit only "updater-script", binary file is the same for all packages, or do I need to edit it, too?
Click to expand...
Click to collapse
Only the updater-script. The binary is a replacement of the script-interpreter I think, but thats just an assumption.
elelinux said:
I built a kernel tool long time ago, very easy to use (only for linux)
Click to expand...
Click to collapse
And that's a good reason to install newest Ubuntu Thanks!
riemervdzee said:
Only the updater-script. The binary is a replacement of the script-interpreter I think, but thats just an assumption.
Click to expand...
Click to collapse
That's mine assuption, too, but would like to know it for 100%
Edit: I see you use it in your kernel update package. So you write only updater-script and place also update-binary next to it?
LOL, you've got help from every well known hero dev on xda, I'm sure you'll have all the info you need now to start building rom's. Good Luck!
Found an app called Easy Flashable zip Builder on this thread. Will test it soon.
tomekk_nt said:
Found an app called Easy Flashable zip Builder on this thread. Will test it soon.
Click to expand...
Click to collapse
But it is for MS Windows, or saw I wrong ? I have also built a tool to javasign files,but should probably write a manual first,it is easy to use but some dependencies maybe not so easy for a beginner with Linux.
tomekk_nt said:
That's mine assuption, too, but would like to know it for 100%
Edit: I see you use it in your kernel update package. So you write only updater-script and place also update-binary next to it?
Click to expand...
Click to collapse
Correcto
If you did not make any backup of your EFS folder, and your IMEI is messed up, this could be your solution to recover your lost IMEI. NOTE THAT AT LEAST YOU MUST HAVE THE SHIPPED ORIGINAL EFS FOLDER ON YOUR PHONE ( even if you didn't make a backup of it yet and even it's messed up ) FOR THIS METHOD TO WORK
My history with my IMEI:
I flashed my phone with some ROMs, and I didn't backup my EFS folder before, then My SGS2 IMEI was changed to 004999010640000, and we know this is the fake IMEI that is assigned to the phone if the nv_data.bin file is messed up.
so I researched. searched all the forums and didn't find anything that could cure my phone's IMEI and set it to the original IMEI number. so I experimented and after some hours, I fixed my IMEI.
one thing that led me to the conclusion that " .nv_data " file is the thing that I need to fix the IMEI is that they share a very look alike name, and they have the same 2MB size.
PS: I restored my phone's firmware to it's original PDA, Phone and CSC, rooted it with CF-Root, and then done this procedures below
here is what I have done:
you must have:
-Root
-Root explorer for copying files to and from EFS folder
-Android SDK for the ADB tools or Terminal in your phone.
It is interesting to know that the IMEI is stored in ".nv_data" file in ORIGINAL SHIPPED EFS folder too, so you just have to do these:
1) make a copy of your EFS folder to your sdcard using root explorer and then make a backup of the folder to your computer [ to have another copy if you had to format sd card sometime ]
2) delete the EFS folder (BE SURE YOU HAVE BACKED IT UP IN A SAFE PLACE AS SAID IN STEP 1) from the root of your phone using root explorer.
3) reset the phone, after that, go to the root, and you can see that the EFS folder is still there, don't make any mistake, this EFS folder is new and generated by the android OS.
4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5".
5) go to your backed up EFS folder on your sdcard, copy the "imei" folder to the EFS folder at the root of your phone, then again go to the backed up EFS folder at yout sdcard and copy the " .nv_data " file to your EFS folder at the root of your phone using root explorer, NOTE: the dot in first of nv_data is not a mistake, copy the ".nv_data" file.
6) make another copy of the ".nv_data" file in EFS folder in your phone, so you would have 2 copies of ".nv_data" in EFS folder
7) rename one of ".nv_data" files to "nv_data.bin" and another one to "nv_data.bin.bak"
8) at your PC open CMD at the ADB tool path, or run Terminal at your phone enter these commands:
adb shell ( use this command of you use ADB, if you're using terminal, skip this line )
su ( ALLOW THE MESSAGE CAME AT YOUR PHONE's DISPLAY BY SUPERUSER PROGRAM )
chown 1001:radio /efs/nv_data.bin
9) reset your phone.... after that you have your original IMEI. you can check your IMEI by dialing *#06#.
and DO IT ON YOUR OWN RISK.
and PLEASE MAKE A COPY OF THE ORIGINAL EFS FOLDER BEFORE DELETING IT. IT HAS IMPORTANT FILES IN IT.
and sorry for bad English.
Thank you very much for taking the time to write this helpful thread, but can you please tell us how your IMEI was changed to a fake one in the first place so that we don't have to go through all this?
maddada said:
Thank you very much for taking the time to write this helpful thread, but can you please tell us how your IMEI was changed to a fake one in the first place so that we don't have to go through all this?
Click to expand...
Click to collapse
Flashing a rom may often be the only reason .
jje
Had you already made a copy of your EFS folder before your IMEI was changed?
kcaz said:
Had you already made a copy of your EFS folder before your IMEI was changed?
Click to expand...
Click to collapse
No, I didn't had the back up before IMEI change.
To make a conclusion:
... You didn't backup your EFS folder.
... Your IMEI changed because of ROM flashings.
... You want to recover your IMEI.
For the purpose of making a backup of the EFS folder, how about simply copying the whole folder into a safe place?
There is an app called Nitrality (if my spelling is not wrong) which one of its various functions is to backup and restore the EFS folder. I've made a backup using this method and it seems that what the app actually did was simply copying the whole folder into a different directory. If it's simple like that, it seems that Root Explorer or similar app would be enough for that purpose.
Nevertheless, as there are numerous guides on this topic, all of which providing more complex methods, either using ADB or Terminal Emulator (I've made a backup using it as well, just in case, which resulted in the EFS being saved as tarball file), I have some doubts whether simply copying the whole folder would be enough for a eventual restoration. Would it?
angelomaldito said:
For the purpose of making a backup of the EFS folder, how about simply copying the whole folder into a safe place?
There is an app called Nitrality (if my spelling is not wrong) which one of its various functions is to backup and restore the EFS folder. I've made a backup using this method and it seems that what the app actually did was simply to copy the whole folder into a different directory. If it's simple like that, it seems that Root Explorer or similar app would be enough for that purpose.
Nevertheless, as there are numerous guides on this topic, all of which providing more complex methods, either using ADB or Terminal Emulator (i've made a backup using it as well, just in case, which resulted in the EFS being saved as tarball file), I have some doubts wheter simply copying the whole folder would be enough for a eventual restoration. Would it?
Click to expand...
Click to collapse
Just copying your EFS folder to a safe place is enough, using any method, but copying EFS folder messes up wih its permissions, so if you want to restore your nv_data.bin file, you must set the owner of the nv_data.bin using "chown" command in ADB like described in my post.
After all, I hope this method works for everyone, worked for me though.
Have copied the efs folder onto my PC.
At least i now know i have a backup, i can mess about with permissions there and then if it ever comes down to it!
I do not have the .nv_data file. onle *.bin or *.bak. Any suggestions or do I have to stick with the generic 00... IMEI? The whole procedure did not word for me, but thanks anyway.
By the way I think you do not need adb for that. You can execute the chmod command in a Terminal editor on the phone.
Schindler33 said:
I do not have the .nv_data file. onle *.bin or *.bak. Any suggestions or do I have to stick with the generic 00... IMEI? The whole procedure did not word for me, but thanks anyway.
By the way I think you do not need adb for that. You can execute the chmod command in a Terminal editor on the phone.
Click to expand...
Click to collapse
yes you can use terminal in your phone, but as for information for the other users, you don't need to enter " adb shell " command in step 8, because you are already connected to the phone's kernel.
I think you deleted your original EFS folder that came preinstalled with your phone, because I had " .nv_data " file.
anyway, use " nv_data.bin.bak " instead of " .nv_data " and see what happens.
thanks for the update.
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
superleeds27 said:
Have copied the efs folder onto my PC.
At least i now know i have a backup, i can mess about with permissions there and then if it ever comes down to it!
Click to expand...
Click to collapse
thank you for your reply. but please don't play with EFS folder too much. the Android OS can't recover your IMEI if you lost it completely. I've been lucky with this method to restore my IMEI.
thanks.
Do you know if there are providers that block your
IMEI? I do not have any problems with my carrier now but I will soon go to the states, and I don't know wether my phone will get blocked there.
Sent from my GT-I9100 using XDA App
Im not messing with it at all. Basically just copied it onto my SD card and then onot my PC. That way i know i deffo have a backup if anything was to happen
Schindler33 said:
Do you know if there are providers that block your
IMEI? I do not have any problems with my carrier now but I will soon go to the states, and I don't know wether my phone will get blocked there.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
I don't know any providers. but as a guess, I think some providers MAY block an irregular IMEI because of their security policy. but it's just a guess.
vaskodogamagmail said:
No, I didn't had the back up before IMEI change.
To make a conclusion:
... You didn't backup your EFS folder.
... Your IMEI changed because of ROM flashings.
... You want to recover your IMEI.
Click to expand...
Click to collapse
I don't understand how you were able to apply the steps you describe to your case if you didn't have a backup of your original efs folder...
Help
My SGS 4G IMEI is corrupted showing some random symbols. Now I have taken backup of my EFS folder. EFS>root>afs>setings has .nv_state and nv_data.bin.
In IMEI folder there are only two files bt.txt and mps_code.dat.
Can it be repaired back to original IMEI? I don't have back up of my original EFS folder.
jerome.d said:
I don't understand how you were able to apply the steps you describe to your case if you didn't have a backup of your original efs folder...
Click to expand...
Click to collapse
I didn't had a backup of my original EFS folder BEFORE IMEI CHANGE.
after my IMEI has been changed to the fake one, then I backed up my EFS folder and do the steps in the first post.
---------- Post added at 05:22 PM ---------- Previous post was at 05:13 PM ----------
s_d123 said:
My SGS 4G IMEI is corrupted showing some random symbols. Now I have taken backup of my EFS folder. EFS>root>afs>setings has .nv_state and nv_data.bin.
In IMEI folder there are only two files bt.txt and mps_code.dat.
Can it be repaired back to original IMEI? I don't have back up of my original EFS folder.
Click to expand...
Click to collapse
the Content of your IMEI folder is correct, we don't have any business with the IMEI folder's content.
but look at your EFS folder contents, find the file named " .nv_data " (no post-fix), then do the steps in the first post.
but NOTE: my SGS 2 is a GSM model, not the 4G model, so I cannot guarantee that this method works with your phone too as it did for me.
thank you
Works in galaxy s too?
Thanks.
Hi...
I don't understand very well what you mean by
NOTE THAT AT LEAST YOU MUST HAVE THE SHIPPED ORIGINAL EFS FOLDER ON YOUR PHONE
Click to expand...
Click to collapse
Do you mean that we should have the efs folder with the sud-folder and files structure as it was when the IMEI was not corrupted???
I.E.
/efs (dir)
nv_data.bin (file)
.imei (hidden file)
.nv_data.bak (hidden file)
.nv_data.bak.md5 (hidden file)
nv_data.bin.md5 (file)
nv_state (file)
/.android (hidden folder)
/imei (folder)
bt.txt (file)
mps_code.dat (file)
nvmac.info (file)
Another issue i'm facing is the fact that I can't do a chown radio:radio because i get the error that user/group radio does not exist...
And would this work for SGS I?
Like others I am confused.
I flashed a ROM night before last.
I ended up with a phone that wouldn't work and the fake IMEI number.
By some chance I was able to get my phone working again with HC-kTool by restoring a efs.tar file -- I have a number of efsxxxx.tar.gz files in a folder called EFS_BACKUP on my sdcard (I don't how it got there but there are various dates of these files).
Now my phone works with data on the ATT network but my IMEI number is still the fake one.
SOOOO -- if I DON"T have an original backup of my EFS folder (or at least one I'm sure of) HOW do I restore my origianl IMEI ???
Thanks for this!
These are the steps explaining you how to create a custom firmware based on the SmartQ firmware releases.
Warning : Creating a firmware and changing the files may cause your device to stop working, I won't be held responsible for any damage caused by this.
Creating a firmware file is actually very easy, not much is involved and nothing more than some basic software is required to create the files. If you don't understand the steps below than maybe you shouldn't fiddle around with this and wait for other members to create these.
There is nothing explained here about the flashing itself, as I will create a seperate How-To about that with pictures explaining the steps of the recovery.
Also there is nothing explained about kernel building itself, I have no clue how to do that and I'll leave that up to SmartQ.
Use the instructions below to make your own Firmware file with the software you want in it and make all configuration changes you want.
1. If you haven't already download the latest official firmware from SmartQ.
2. Extract the zip file. You then have 2 files, a Chinese .txt file with the release notes. And a file called "SmartQT15".
3. Rename the file "SmartQT15" to "SmartQT15.zip". Accept any warning about making the file useless, as in fact you are making it useful.
4. Extract the zip file. Then you end up with 4 new folders :
"boot" - This will be the files required for booting the OS. And possibly the recovery.
"data" - The user apps and data are in this folder.
"META-INF" - The certificate SmartQ used is in this folder and also the update script that manages the update process.
"system" - The actual Android OS.Stay clear of the boot folder, unless you are 100% sure about what you are doing, this may cause a bricked device without the possibility to reflash.
Add apps to the app subfolder in the data folder. Make sure if you do add apps to set the permissions in the update script file and make changes accordingly. The data-extra.tar file is extracted during the update process.
In the "META-INF\com\google\android" folder you can find the updater-script file, you can edit this with Notepad++. This file tells the CWM based recovery what to do and in this file the permissions are set for apps. Also is it required to edit this if you want to create a pre-rooted firmware.
Be carefull what to change in the system folder it can cause your OS not to boot, but it should be no problem to revert back to another build that did work previously as you didn't touch the boot folder and the recovery should work normally.
Once you have made all the changes you wanted to do. You follow the steps back.
5. zip the 4 folders backup using Winzip or WinRAR, whatever suits you best (You can use compression, I tried out Fast, Normal, Good compression in WinRAR and the firmware flashed without problems). Make sure you have the 4 folders in the "root" of your zip file. Use for filename "SmartQT15.zip"
6. Rename the "SmartQT15.zip" file to "SmartQT15" and accept any warning again about changing the extension of your file.
You have now created a flashable firmware file for the SmartQ Ten3 T15.
Copy his file to the root of an empty microSD card and follow my How-To about flashing Custom Firmwares.
Don't use the guide to flash original SmartQ firmwares as this won't work, by changing the firmware package you break the firmware signature and the recovery will check for this during flashing.
Signature checking can be disabled though in the recovery as I will explain in the new How-To.
If you have any questions feel free to post below and I'll do my best to answer them, all the above is based on my experience and from what I could find out on the Internet.