Related
********NOTE*********
i have included a few of the tools you will need as attachments to this post. I will not take any credit for these programs as i was not the developer for them... these people work too hard to have anyone steal their credit... please give credit where credit is due!Your nv_data.bin file and its matching nv_data.bin.md5 files are located on your phone in /efs/
All references that i make to "sd card" or "/sdcard/" refer to your phone's internal SD Card, not an external SD card that you may have installed.
I have created a windows batch file that you can run and it will extract your entire /efs/ folder from your phone to your PC. I am currently working on the batch script to move the edited nv_data.bin files back to your/efs/ folder and do the other adb stuff.
attached is the EFS Extractor.zip file that contains the ADB files and the batch script.
The product code for your AT&T Captivate is: SGH-I897ZKAATT
WARNING… I AM NOT RESPONSIBLE IF YOU BREAK YOUR PHONE FOLLOWING ANY OF THESE INSTRUCTIONS
The Attached EFS Extractor.zip file contains the necessary adb file and a couple batch files. "retrieve efs.bat" copies your entire /efs/ folder to your PC in a folder called /efs_bkup/ in the directory where you unzipped the file and ran the batch program from. The file "update nv_data.bat" takes your edited nv_data.bin file from the root directory where you ran the .bat file from and places in in your phone's /efs/ folder and removes the old copies from your phone... when it is done, it will power cycle your phone.
To fix your nv_data.bin, you will have to have access to the following tools:
A hex editor (search google for hex editors, they have tons of them that are free… I use one called HexEdit and i have it attached)
GalaxyS_One-Click_Root_All_Models (available via XDA-Developers... attached)
ADB (Android Debugging Bridge) This is available by getting the Android SDK at the Android Developers Website (http://developer.android.com/sdk/index.html) or if you downloaded the Galaxy S One Click Root, it is in the directory where you unzipped the files.
BusyBox – Search the google market for “BusyBox”. It will appear and will be the free one from stericson (i have included the .apk as an attachement)
Odin One-Click Downloader (available from XDA)… make sure you get the correct one. There are 2 versions. If you batch number is 1008 then you need the one with the 3-button fix, if you batch number is greater than 1008 then you should need the regular one. Your batch number is written on the sticker on your phone under your battery on the left side right under the words “S/N” where your serial number is listed.
Samsung Kies Mini (gotten from Samsung website)
Download the attached EFS Extractor .zip file. It contains everything you need to copy your /efs/ folder to your PC
Now for what you need to do to get your phone’s nv_data.bin back to normal:
Flash back to stock and then do a master clear using Odin One Click
put phone into USB debugging mode and also check the setting to "stay awake"
connect phone to PC and root and install busybox
extract the attached EFS Extractor.zip file and run the "retrieve efs.bat" file. This will copy your entire /efs/ folder from your phone to your PC in a direcotry called ./efs_bkup/
Using the Hex Editor, edit the file ./efs_bkup/efs/nv_data.bin on your PC to have the correct product code SGH-I897ZKAATT. do an ASCII search for "SGH" to locate the line in the file that contains your product key. then save the edited file to ./nv_data.bin (the root directory where you extracted your ZIP file to on your PC)
run the file "update nv_data.bat" to copy your corrected nv_data.bin to your phone's efs folder and chown it and reboot your phone
change USB Settings on phone back to Kies then open Kies Mini and connect phone.
you should now be able to connect to Kies Mini and not have unregistered device... now would be a good time to back_up your /EFS/ folder... you can now either do Odin One-Click and a master clear, or flash a different rom. You should do Odin if you want to use Kies to get updates to be 100% stock to remove your root and busybox.
The general overview what what you need to do is this for those of you that want to know and/or use other tools to do this
Copy your /efs/nv_data.bin file from your phone to your PC
Use a hexeditor to modify the line in the nv_data.bin file that contains the productcode to contain your correct product code
delete any nv_data.* files from your /efs/ folder on your phone
copy the corrected nv_data.bin file from your PC to your /efs/ folder on your phone
busybox chown 1001:1001 /efs/nv_data.bin
reboot phone
Done!
Now, when you backup your /efs/ folder to your PC you may see files like nv_data.bak and nv_data.bak.md5. Using a hexeditor, open the nv_data.bak file and look at the line that has the product code (ASCII values starting wtih SGH)... if the product code in the .bak file is correct, then delete the nv_data.bin and nv_data.bin.md5 from your /efs/ folder on your phone and reboot your phone. Your phone should then create new .bin and .bin.md5 files from the .bak and .bak.md5 files that will have the proper productcode. You can also optionally rename the .bak and .bak.md5 files on your PC to be .bin and .bin.md5 and copy them to your /efs/ folder on your phone.
You can view what Kies is reading your productcode as by opening your windows registry editor Start>Run>regedit[enter]
Connect phone to PC in Kies(Firmware) mode
Navigate to HKEY_CURRENT_USER/Software/Samsung/KiesMini/FUS
Look at the key "PRODUCTKEY" and what it's value is... if it is correct, then you are good. If not, then something went wrong somewhere.
If you have issues please post the issues you are having and I will update as necessary.
Here is a link to a different thread that contains a program and instructions for restoring your unlock codes if that is what you are trying to do. The .jar (java program is written in frech, but it only asks for the codes you want to use for your unlock codes... i did not make this program so I cannot help you with it.
http://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
Tried to trim this down a little as there are a ton of steps, let me know if any of this is incorrect.
1. Flash back to stock rom, and do a master clear using the Odin3 One-Click Downloader by designgears
2. Root using one-click-root and install busybox, turn on usb development mode + stay awake, and connect to your PC.
3. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /efs/nv_data.bin /sdcard/nv_data.bin
d. cp /efs/nv_data.bin /sdcard/nv_data.bin.copy (incase there is a problem)
e. rm /efs/nv_data.*
4. Exit your adb.exe window, mount your phone on your PC and navigate to the internal card. Edit the nv_data.bin with a hexeditor (bpsoft.com) and search (ascii) for "SGH-" (without the quotes)
5. It may be something like SGH-I897ZKATOR or SGH-I897ZKATMB. You need to change this to SGH-I897ZKAATT then save the file, and unmount your phone.
6. Disconnect usb data cable from pc to phone, re-enable usb development mode + stay awake, reconnect.
7. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /sdcard/nv_data.bin /efs/nv_data.bin
d. busybox chown 1001:1001 /efs/nv_data.bin
8. Power cycle
Hi hansomni. l've been down this road. Were you successfull with creating Nv_data.bak this way and restoring with that. For example editing nv_data.bak and making a corresponding md5 file and only placing those files in your efs folder and restarting your phone
I had problems creating this file. i would always get an incorrect iemi. This is why i recommend using nv_data repair.zip posted in the tmo vibrant unlock thread not only can you recreate the correct product code but also fix the fffffffff for unlock code.
Have you checked this outhttp://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
mattbeau said:
Hi hansomni. l've been down this road. Were you successfull with creating Nv_data.bak this way and restoring with that. For example editing nv_data.bak and making a corresponding md5 file and only placing those files in your efs folder and restarting your phone
I had problems creating this file. i would always get an incorrect iemi. This is why i recommend using nv_data repair.zip posted in the tmo vibrant unlock thread not only can you recreate the correct product code but also fix the fffffffff for unlock code.
Have you checked this outhttp://forum.xda-developers.com/showpost.php?p=8983897&postcount=103
Click to expand...
Click to collapse
yeah... i have been successful using the steps i outlined... like i said in the original post, this is only to get your product code fixed... i don;t have an unlocked phone so i don't know if that program works... i did use it to check it out, but it is written in frech or something and it never copied the "patched" nv_data files back to my phone... i had to do it manually and still the product code from the created files were wrong. Others say that they have had success using it, but i never did. I took a buch of stuff from a buch of posts on this site to compile the guide here for restoring product codes only.
the .bak files are your backup files that get generated sometimes... usually those files have your correct unlock codes and productcode... to restore them, just delete the non .bak files and remove the .bak extension from the backups... then copy them to your /efs/ folder and powercycle and you should be good. you should keep all your orignial files from your /efs/ folder in a safe place though so you have them to fall back on if you need to. I have never had the .bak files in my /efs/ folder so i haven't ever been that lucky.
devz3r0 said:
Tried to trim this down a little as there are a ton of steps, let me know if any of this is incorrect.
1. Flash back to stock rom, and do a master clear using the Odin3 One-Click Downloader by designgears
2. Root using one-click-root and install busybox, turn on usb development mode + stay awake, and connect to your PC.
3. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /efs/nv_data.bin /sdcard/nv_data.bin
d. cp /efs/nv_data.bin /sdcard/nv_data.bin.copy (incase there is a problem)
e. rm /efs/nv_data.*
4. Exit your adb.exe window, mount your phone on your PC and navigate to the internal card. Edit the nv_data.bin with a hexeditor (bpsoft.com) and search (ascii) for "SGH-" (without the quotes)
5. It may be something like SGH-I897ZKATOR or SGH-I897ZKATMB. You need to change this to SGH-I897ZKAATT then save the file, and unmount your phone.
6. Disconnect usb data cable from pc to phone, re-enable usb development mode + stay awake, reconnect.
7. Open a command prompt window and navigate to the directory where you extracted the one-click-root. Run the following commands:
a. adb shell
b. su
c. cp /sdcard/nv_data.bin /efs/nv_data.bin
d. busybox chown 1001:1001 /efs/nv_data.bin
8. Power cycle
Click to expand...
Click to collapse
Yeah, looking at it quickly it looks like all the instructions are correct... maybe abbreviated too much... Thanks for that... i will update with instuctions similar.... i have to remember that there are those folks that have never used adb or know what it is. I will credit you in my update tomorrow. I am used to where i work we have people that use computers that don;t know how to power them on and off so they just leave them on all the time... i have to be very specific on my instructions that i tell them so they can understand... a two second task becomes an all-day event. Just something i am used to doing.
I will be working on a dos script (.bat) file that will do most of the adb stuff so then the users only need a few things to do and just let the scripts take care of the rest.
hansonmi said:
yeah... i have been successful using the steps i outlined... like i said in the original post, this is only to get your product code fixed... i don;t have an unlocked phone so i don't know if that program works... i did use it to check it out, but it is written in frech or something and it never copied the "patched" nv_data files back to my phone... i had to do it manually and still the product code from the created files were wrong. Others say that they have had success using it, but i never did. I took a buch of stuff from a buch of posts on this site to compile the guide here for restoring product codes only.
the .bak files are your backup files that get greated sometimes... usually those files have your correct unlock codes and productcode... to restore them, just delete the non .bak files and remove the .bak extension from the backups... then copy them to your /efs/ folder and powercycle and you should be good. you should keep all your orignial files from your /efs/ folder in a safe place though so you have them to fall back on if you need to.
Click to expand...
Click to collapse
You dont even need to change the extenaion of those files if you power cycle your phone with just .Bak files. Your phone will recreate the nv_data.bin and md5 from those .Bak files and create a log file
Yeah i know the java program is in french. But its only asking you what two codes you want to use for unlocking your phone ( ahh google translate)
And yes the first time i tried the program i had trouble too. I think it helps if you have a good busybox version.
Believe me the easier you can make it the better it will be for everyone. Now if we could just get everyone to back up that folder before flashing anything we wouldnt even need to go down that road. Thanks for your help in this. Ill leave this thread alone now sorry if im intruding. Pm me if you need any help
mattbeau said:
You dont even need to change the extenaion of those files if you power cycle your phone with just .Bak files. Your phone will recreate the nv_data.bin and md5 from those .Bak files and create a log file
Yeah i know the java program is in french. But its only asking you what two codes you want to use for unlocking your phone ( ahh google translate)
And yes the first time i tried the program i had trouble too. I think it helps if you have a good busybox version.
Believe me the easier you can make it the better it will be for everyone. Now if we could just get everyone to back up that folder before flashing anything we wouldnt even need to go down that road. Thanks for your help in this. Ill leave this thread alone now sorry if im intruding. Pm me if you need any help
Click to expand...
Click to collapse
Yeah... the problem is that not everyone knew to do it before flashing as a lot of the ROM pages don't say it (I was one of them that never knew about it)... i knew what the java was saying but since i don't have an unlocked phone, i had no way of testing it to see if it worked for me or not... and on top of that it didn't work with restoring my productcode (i know that becuase i couldn't use Kies until i did things manually)... I tell people to rename the files, becuse i am assuming they copy the contents of their /efs/ folder to a PC or something... then they just have to delete the nv_data files from /efs/ on their phone, and rename the .bak files on their PC and copy them back to their phone's /efs/ so they still have a copy of their original files saved on their PC... plus i don't like relying on the phone doing the renaming because if it doesn't no one will know what went wrong...
Working on Windows Batch (.bat) script
I will be working on doing a windows .bat script that will do most of the dirty work for you... it may take a couple days because where i work the end of the year is the busiest time for me and i don't have a lot of time between work during the week.
I will make the script an attachment and will hopefully be able to zip with the abd files to make life a little easier for everyone.
Thanks for the input everyone.
What line
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Worked great, followed steps exactly as outlined didn't have any problems. Thanks again for this, I've been wanting to have a proper backup of efs folder with correct product code, but could never change it back.
Slowazz28 said:
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Click to expand...
Click to collapse
I used hexedit, and if the line number is in first column it begins on line 188010. I did notice when searching a second time to get line number, that I had to have sgh- in all caps, and once i got string not found, I closed program reopened and searched again using caps (SGH-) it worked several times. Hopes this helps.
Big thanks for posting this.
I'll give this a shot prior to flashing Axura 2.5.
Thanks hansonmi! I got it updated with kies. I done it a lil diffent using root explorer to move files around and used hexeditor to edit files and root explorer to copy back.
great guide.
wish this would have been around the first time i ran into this problem as it was a headache when it happened and the threads and advice on fixing were so fragmented within the forum threads.
The only thing i did differently was that i didn't use ADB on a pc at all during the process (I completed the process using both Root Explorer and Terminal Emulator on my phone and copying files to pc via mounting the phone and its storage as disk drives).
(PS before doing any of this i backup up my efs folder first to my external SD using root explorer and then to my pc via mounting the phones storage)
1. I had already copied my nv_data.bin file to external SD when backing up EFS folder.
2. Connected to pc via usb and mounted for storage (with debugging on)
3. copid nv_data to pc
4. used PsPad to edit the nv_data file in accordance with previous instruction in this thread. (I highly recommend PSpad as a hex editor. Its nice that you can switch back and forth between hex and text editor views) See PS in the end for using PSpad hex editor to find the line you need to edit. That seemed to be the only thing that needed clarified.
5. copy nv_data.bin back to the root directory of external sd
6. use root explorer to move newly edited nv_data from external sd back to original EFS folder.
7. Delete the nv_data..bin.md5 file..i left the backup from efs folder
7. delete any nv_data.baks from efs folder
8. Now the use of Termainl Emulator (download from market). Busybox must be installed as well
9. Open terminal emulator execute following commands:
SU
busybox chown 1001:1001 /efs/nv_data.bin
reboot
(reference to step 4 using hex editor)
PS - These are the steps for editing the hex code and starting with step first step assuming you have copied the nv_data.bin to your PC
1. Open PsPad (or other hex editor)
2. Open nv_data.bin in hex editor mode
3. Go to line 188000 (using search modes you will likely have to enter $00188000 or 00188000) Using PsPad you would do the following:
Select SEARCH from top tool bar. Select GOTO LINE.......then enter $00188000
4. You will see yTMB....SGH_i897ZKATMB (or yTOR....SGH-ZKATOR).
5. Replace that first TMB or TOR with ATT then replace ZKATMB or ZKAATOR with KZAATT
6. Save
7. Now you should have a proper nv_data.bin
HBeezy said:
I used hexedit, and if the line number is in first column it begins on line 188010. I did notice when searching a second time to get line number, that I had to have sgh- in all caps, and once i got string not found, I closed program reopened and searched again using caps (SGH-) it worked several times. Hopes this helps.
Click to expand...
Click to collapse
Ok that worked great except when I get to that line it says productcode several times then a bunch of x's then 11 0's but no SGH- so not sure where to put it in at. The 0's start on line 1880f0 and end on line 188100 ??? Appreciate the help
Slowazz28 said:
Ok that worked great except when I get to that line it says productcode several times then a bunch of x's then 11 0's but no SGH- so not sure where to put it in at. The 0's start on line 1880f0 and end on line 188100 ??? Appreciate the help
Click to expand...
Click to collapse
what hex editor are you using?
i recommend downloading the free PSpad Hex/Txt editor.
1. Open your nv_data file using FILE then OPEN IN HEX EDIT
2. use SEARCH from toolbar commands....GOTO LINE from search menu....options after opening in hex edit mode
3. then search for $00188000
you should see the line you need to edit.
The nice thing about PSPAD is that you can also open the binary file in a Text mode. If you have trouble finding it in the hex editor mode try the following.
1. open PSpad. Goto FILE then OPEN (vs. open in hex edit). This will open in a text editor view/mode.
2. goto SEARCH and select INCREMENTAL SEARCH
3. type SGH and search
(you could also do all the hex editing without moving files to pc if you wanted using HEX EDITOR from market...though for most the PC hex editors might be easier)
if you want to use the android hex editor app to do all the editing on your phone...do the following:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Use Root Explorer to copy nv_data.bin from efs folder to the root directory on your external sd.
2. Use Hex Editor App to open the copy from your external SD.
3. One Open click the capacitive menu button and select jump to address
4. Enter 0188008
This will take you to line 00188008
5. Edit the last or 8th Block so it reads 41.
6. Enter 0188010
7. This will take you to line 00188010. Edit the first two blocks of 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)
8. Now look down to line 0018020 and look at the line. If you at the line and to the far right text you will see ATOR or ATMB if your nv_is messed up.
9. 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....)
10. Save the file and move it back to efs using root explorer.
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....
bames said:
what hex editor are you using?
i recommend downloading the free PSpad Hex/Txt editor.
1. Open your nv_data file using FILE then OPEN IN HEX EDIT
2. use SEARCH from toolbar commands....GOTO LINE from search menu....options after opening in hex edit mode
3. then search for $00188000
you should see the line you need to edit.
The nice thing about PSPAD is that you can also open the binary file in a Text mode. If you have trouble finding it in the hex editor mode try the following.
1. open PSpad. Goto FILE then OPEN (vs. open in hex edit). This will open in a text editor view/mode.
2. goto SEARCH and select INCREMENTAL SEARCH
3. type SGH and search
(you could also do all the hex editing without moving files to pc if you wanted using HEX EDITOR from market...though for most the PC hex editors might be easier)
if you want to use the android hex editor app to do all the editing on your phone...do the following:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Use Root Explorer to copy nv_data.bin from efs folder to the root directory on your external sd.
2. Use Hex Editor App to open the copy from your external SD.
3. One Open click the capacitative menu button and select jump to address
4. Enter 0188008
This will take you to line 00188008
5. Edit the last or 8th Block so it reads 41.
6. Enter 0188010
7. This will take you to line 00188010. Edit the first two blocks of 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 AT....SG)
8. Now look down to line 0018020 and look at the line. If you at the line and to the far right text you will see ATOR or ATMB if your nv_is messed up.
9. 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....)
10. Save the file and move it back to efs using root explorer.
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|AT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
Click to expand...
Click to collapse
Ok, So my nv_data.bin must be fubared cause I don't even have lines 188008 or 188018. They go by 10's like 188000, 188010, 188020, ect. And the text to the right of line 188010 starts TT....SG not AT....SG
File
I didn't back this up from my first flash to a custom ROM. Stated at the beginning it says this is likely unfixable. I have run Axura, Cog and Perception Roms (not in that order). Not sure if that makes a difference. Is this still fixable? The problem I have (using new market) is apps are either
A) Installed and not showing so on the market
B) I have them installed and they disappear & have to reinstall them from the market only to have them disappear from my phone again
C) Unable to download them (such as Pocket Legends)
Any feedback is appreciated.
Thanks
Slowazz28 said:
Ok, So my nv_data.bin must be fubared cause I don't even have lines 188008 or 188018. They go by 10's like 188000, 188010, 188020, ect. And the text to the right of line 188010 starts TT....SG not AT....SG
Click to expand...
Click to collapse
my bad
the 188010 should start TT i will correct my original.
but you should be able to find lines 188008 an 18 though you wont need to do anything with 18. Did you try looking at it with the android hex editor app from market?
You won't see the 008 and 018 lines if your using a hex editor on PC you will only see the lines by by 10's.
The section you are referring to are for Using Android Hex Editor App on your phone.
-----------------------
if your using a hex editor on your PC you should see the following when corrected:
188000 | FFFF | FFFF | 5245 | 5630 | 2E34 | 0000 | 0000 | FF41 |
188010 | 5454 | 0000 | 0000 | 5347 | 482D | 4938 | 3937 | 5A4B |
188020 | 4141 | 5454 | 0000 | 0000 | 0000 | 0150 | 024E | 034E |
Slowazz28 said:
Could someone that has successfully done this post what line in the hex file the product code is found on. All I get is string not found??? Thanks
Click to expand...
Click to collapse
It really depends on the editor you are using and you have to make sure you are searching for ASCII...
in the edit that i use, it is line 188010
Hello:
i tried to change my Bootanimation but with no Luck.
1. i tried to make a "theme" via Online Kitchen; got a file (about 6mb) flashed it via Recovery but Botscreen stayed at white "HTC-Briliant"
2. i tried to manualy delete the bootaniamtion.zip at /data/app/local with androidmate (free)--> http://forum.xda-developers.com/showthread.php?p=10041079&highlight=bootanimation#post10041079
3. i tried to make my own update.zip ( http://www.londatiga.net/it/how-to-create-android-update-zip-package/)
script:
Code:
show_progress 0.1 0
copy_dir PACKAGE:data\app\local data\app\local:
show_progress 0.1 10
4. tried to change the bootimage.zip in NEO's Reflext.Rom by deleting all unneccesary stuf and changing the bootanimation-zip
--> got stuck after Recovery so i had to reflash the whole ROM..
--------------------------------------------
why i'm not able to change this bootanimation ?
can someone provide me a funktional Update-zip for this ROM
(or a HowTo for doing it myself?)
i would like to test these Bootimages:
http://forum.xda-developers.com/showthread.php?t=648555
http://forum.xda-developers.com/showthread.php?t=905538 (android particle2)
PLEASE Help
EDIT: i also tried via
Terminal Emulator
- Connect your phone to your computer via USB
- Copy the downloaded file to your sdcard
- Disconnect phone from computer
- Open Terminal Emulator on your phone and enter the code below (press enter after every line)
su
cp /sdcard/480x800_AndroidGlow1.zip /data/local/bootanimation.zip
reboot
Click to expand...
Click to collapse
EDIT:
Try putting it into /system/customize/resource
thats where the bootanimation (and the boot sound..) was located on my desire rom.
tried this but:
1: i found no "resource" folder under /system/customize..
2. after creating this folder and copying bootanimation.zip nothing happens
it seems like NEO put it on a special place in his ROM so i cant't figure out..
Test this route: /system/etc/customer/bootanimation.zip ;-)
System/sd/app/local remplace the bootanimation.zip and reboot.
It worked !!
Thanks ASIER
the System/sd/app/local .. did the trick
why does neo uses this folder-structure.. weird ..
(and also thx to raa_ for his help)
does it make sense if i say, i don't have a /system/sd/app/local folder??? the sd part is nowhere to be found
any idea?
edit. found it on my Desire it was under /system/customize/resource/bootanimation.zip
cheers
i think it depends on the ROM you are using!
i use the ReflextSense 1.7 from NEophyte.360
that uses the "unusual" path as postet before.
"normal" Sense ore SenseHD Roms are using different locations as you found out..
it is sad that there's not a standard-path for all roms !
Asier said:
System/sd/app/local remplace the bootanimation.zip and reboot.
Click to expand...
Click to collapse
I have the reflext 1.7 rom on my desire and i have no folder named app in system/sd
neo2006pf said:
I have the reflext 1.7 rom on my desire and i have no folder named app in system/sd
Click to expand...
Click to collapse
are you sure youre on the system-"partition" ?
i first set the System to Read/Write in SPareparts and afterwards used ESData explorer (in the program you have to enable ROOT funktions..)
--> menu/settingsroot options --> mount filesystem
------
click on the button on the very left (sd-icon) and it should change into a "house"
the path should be a "/"
afterwards choose SYSTEM/SD/APP/Local
in this folder there should be bootanimation.zip, downanimation.zip, shutdown.zip and "placeholder"
hope it helps
I cant find my bootanimation.zip anywhere,Im using insertcoin 1.8f(trying to update to 1.8h with no luck )
this Thread describes Changing BOOTANIMATION in ReflextSense (1.7)
i think insertCoin uses an different Folder for Bootanimation.zip than this rom.
you could try one of these options:
get shure you hav read/write acces to your Root.. (as i described in de Posting before..)
search the "insert coin" thread for Bootanimation.zip
ask in the Thread about the neccesary "Path"
try to download a "change bootanimation" zip from online kitchen or from the forum..
apply the zip via Recovery and if it works !! ... open the zip and analyse the script file (which Path it uses..)
i hope it helps..
klefreak said:
are you sure youre on the system-"partition" ?
i first set the System to Read/Write in SPareparts and afterwards used ESData explorer (in the program you have to enable ROOT funktions..)
--> menu/settingsroot options --> mount filesystem
------
click on the button on the very left (sd-icon) and it should change into a "house"
the path should be a "/"
afterwards choose SYSTEM/SD/APP/Local
in this folder there should be bootanimation.zip, downanimation.zip, shutdown.zip and "placeholder"
hope it helps
Click to expand...
Click to collapse
I had the right path but was using a software that can't see the folder system/sd/app. I managed to replace the bootanimation.zip with SUFBS. Thank you for your help though.
I) : V6 Supercharger Tutorial
II) : Kick Ass Kernel Tweak tutorial
Hi all, I found it V6 Supercharger
This script is a complete memory management fix. More info in the original thread !
Me and some others had tested it and it works ! The phone is smoother and faster !
Note : it's recommended to delete all memory scripts before using this !
Warning ! You need a rooted Phone, and you need a kernel that supports Autostartup Scripts !
( This tuto is provided without warranty of any kind )
If you have laggs ( With or without V6SuperCharger ) see at the end of the post !
I) Tutorial V6 SuperCharger :
First of all you have to downgrade Busybox ( It might work with version 1.19, I don't know but recommended to downgrade cause of risk of bugs ! )
Use Busybox Installer and try version 1.18.2 or lower !
Then you can use Script Manager ( recommended ) or Terminal emulator (Two methods).
And you need the script(V6 update9beta3.1)
Delete .txt extension, file have to be a sh file
Just place it on your SD card.
WITH SCRIPT MANAGER :
Launch Script Manager
Search the script you placed on SD card
Slect it, and select " Run as root " ( /!\ Don't Select Run at boot ! /!\ )
Execute it
It will ask for speed, tap on screen, type 2 and press enter.
You can see now a list with 17 choices.
Recommended choices are 6 and 7 ( You can test others if you want, maybe they work better ).
So write 6 or 7 and press enter.
You will see under the list, "Current Minfrees = X,XX,XX,XX....."These are the values you've selected before.
When it's done, exit Script Manager, and browse to /system/etc/init.d with Root Explorer or equivalent.
You can see "99SuperCharger", you have to rename it in "S99SuperCharger" ( If not renamed, it will not be load at boot ! )
Now reboot your phone !
When phone rebooted, launch Script Manager and the script
Choose 0
And after list, verify that says : ( Exemple for choice 7 so, values are values from 7th choice )
Code:
Current Values MATCH Prior SuperCharge!
Current minfrees = 6,8,26,28,30,32 mb
Prior V6 minfrees = 6,8,26,28,30,32 mb
If values match, it's OK !
Enjoy !
WITH TERMINAL EMULATOR OR ADB SHELL (First Method) :
Note : Rename file script in "Script.sh" is easier
First, type su ( enter in Super User rights )
Type:
Code:
sh /mnt/sdcard/Script.sh
Select Scroll speed : Type 2 and enter.
You'll see the script with the list
Recommended choices are 6 and 7 ( You can test others if you want, maybe they work better )
So, type 6 or 7 and enter
After script done, you will see under the list, "Current Minfrees = X,XX,XX,XX....."These are the values you've selected before.
Exit terminal emulator or ADB Shell
Browse with Root Explorer to /system/etc/init.d
Rename "99SuperCharger" in "S99SuperCharger" ( If not renamed, it will not be load at boot ! )
Reboot Your phone !
When phone rebooted, launch script again,
Choose 0
And after list, verify that says :
( Exemple for choice 7 so, values are values from 7th choice )
Code:
Current Values MATCH Prior SuperCharge!
Current minfrees = 6,8,26,28,30,32 mb
Prior V6 minfrees = 6,8,26,28,30,32 mb
If values match, it's OK !
Enjoy !
WITH TERMINAL EMULATOR (Second Method)
Note : Rename file script in "Script.sh" is easier
First, type su ( enter in Super User rights )
Type:
Code:
sh /mnt/sdcard/Script.sh
Select Scroll speed : Type 2 and enter.
You'll see the script with the list
Type 15, and Enter
Type Y and Enter
Exit the script ( Type 17 )
And now, type V6 bash ( or V6 or bash V6 or sh V6 )
You'll see the script with the list
Recommended choices are 6 and 7 ( You can test others if you want, maybe they work better )
So, type 6 or 7 and enter
After script done, you will see under the list, "Current Minfrees = X,XX,XX,XX....."These are the values you've selected before.
Exit terminal emulator or ADB Shell
Browse with Root Explorer to /system/etc/init.d
Rename "99SuperCharger" in "S99SuperCharger" ( If not renamed, it will not be load at boot ! )
Reboot Your phone !
When phone rebooted, launch script again (type bash V6 in terminal),
Choose 0
And after list, verify that says :
( Exemple for choice 7 so, values are values from 7th choice )
Code:
Current Values MATCH Prior SuperCharge!
Current minfrees = 6,8,26,28,30,32 mb
Prior V6 minfrees = 6,8,26,28,30,32 mb
If values match, it's OK !
Enjoy !
II) Tutorial KickAssKernelTweak :
Just Download The script
Rename it as S98KickAssKernelTweaks ( If not renamed, It will not be load at boot ! )
Place it in /system/etc/init.d folder and reboot your phone
___________________________________________________________________
___________________________________________________________________
If you have laggs just download Script file "Cache.sh.txt" in attachement.
Remove .txt extension to have a .sh file.
Put it on your SD card, and run it with Scriptmanager ( You can do a Script widget with script manager to access it simply by homescreen )
Look at here for more information : zeppelinrox's post
NOTE : You can explore other choices by yourself and / or look at zeppelinrox thread !
Tutorial by me !
ALL CREDIT TO : zeppelinrox
If you have suggestion, request or question just tell me
Did you had to downgrade you busybox too like was recommended?
Mine is 1.18.4 now. Think it came with Titanium.
Kingzak34 said:
( Sorry if I posted in wrong section )
Click to expand...
Click to collapse
It is proper section...just mention the name of the original developer also...
Kingzak34 said:
Hi all, I found it yesterday, V6 Supercharger
I tried it, it works, and I find phone more responsive and smooth, can anyone test it and give me feedback ?
I use Balanced 3 ( 6th choice )
After you run the script go to system/etc/init.d and ( mount system R/W )
And rename 99SuperCharger in S99SuperCharger
And then reboot the phone ( You can verify by re run the script if setings are saved after reboot )
I wait your feedbacks
( Sorry if I posted in wrong section )
Click to expand...
Click to collapse
I tried it. But my phone stucked in sleep mode each time.
i5 Rom
busy box downgrade and it works on in5 non oc and other cfws
Trying Balanced3 with Kyrillos 6.1, G3Mod v1.3.4 Performance and busybox 1.18.2. Feels pretty snappy, I hope it's not because of the reboot or the placebo effect.
Thank you for feedbacks, for all, please say what ROM Kernel and CPU Settings you use
Yeah, use 1.18.2 !
So, Good or not ?
@arunmcops What kernel do you use ? I have it for 2 days now, and it works properly ( My Kernel: Fugumod_ BE_2.4-alpha19 ( Kyrillos V6 OC defaut ) with 1300Mhz Performances and 246 performance when screen off )
work realy good had to downgrade busybox and used option7 in script manager no freezes realy fast its recommended
RafayelG said:
work realy good had to downgrade busybox and used option7 in script manager no freezes realy fast its recommended
Click to expand...
Click to collapse
Thanks, can you say to us what ROM Kernel and setting do you use ?
option 7(mutitasking too) working great for me too...using pre release fugumod...using ondemand governor min freq at 260000 and max at 780000..upper threshold 95%..powerbias 400...removed juwe's ram script and auto memory management too..its fast and awesome...trying figure out option 11 and 12
EDIT: indroid 5 rom
cool.darshak said:
option 7(mutitasking too) working great for me too...using pre release fugumod...using ondemand governor min freq at 260000 and max at 780000..upper threshold 95%..powerbias 400...removed juwe's ram script and auto memory management too..its fast and awesome...trying figure out option 11 and 12
Click to expand...
Click to collapse
Yeah thanks ! What ROM ?
Kingzak34 said:
Thanks, can you say to us what ROM Kernel and setting do you use ?
Click to expand...
Click to collapse
G3Mod extreme at 1ghz Rafo's Rom V1.0 JPK base
RafayelG said:
G3Mod extreme at 1ghz Rafo's Rom V1.0 JPK base
Click to expand...
Click to collapse
G3 mod Extrem has many screen off bug, try with ultimate
( Maybe fixed by 1.3.4 version )
rom kyrillos v7.0
kernel G3MOD 1.3.4 ultimate 200-1200Mhz @ savagezen
and i try option 6 and 7, and option 6 for me is smother...
any good results here ?
(•.•) said:
any good results here ?
Click to expand...
Click to collapse
Yes, almost all feedbacks are good
Has anyone tried option 2?
Sent from my GT-I5800 using XDA App
Anybody tried these??
And why is there a need to rename in init.d??
dhirend_6d said:
And why is there a need to rename in init.d??
Click to expand...
Click to collapse
I noted that if the script not begin by S, it's not loaded in my phone :/
Here tried to make tablet mode for our Huawei U8800 x5! Finally I stack it run! But he still needs work!Here are screenshots .....
soon
works:
-Al
lDoes not work:
-Phone (solved by the installation of alternative dialer https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5tb2Rvb2h1dC5kaWFsZXIiXQ..)!
instructions:
-install Aurora 2.11 with wipe (because the later start could not!)-
-Turn on your phone to install Apex launcher (standard crash)
-After you install this mod http://narod.ru/disk/65524412001.80b481e7bcc87e6f3068bfb286b1cd1d/Table mod.zip.html
-Now go to / system /, look for the file build.prop. Long press on it - open (open with), choose a text editor (text redactor). Leaf through to the bottom line of the file and see ro.sf.lcd_density = 240. Change 240 to 128. Save the result.
t-Now you have a mini tabletSay
THANK YOU!
Look's good I really can't wait for screenshots!!! :good:
Mlopik said:
Look's good I really can't wait for screenshots!!! :good:
Click to expand...
Click to collapse
+1:good:
moved to general section
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
stefano_te said:
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
Click to expand...
Click to collapse
I think it's enough that you throw it into the SystemUI.apk(have a look inside that apk, if it's not there then it is in secframework.apk) (/res/.../XHDPI). Open the apk in winrar (you might have to rename it from .apk to .zip) and drag and drop the new files. Decompiling isn't necessary for this sort of thing.
Also, check this out:
http://forum.xda-developers.com/showthread.php?t=1918500
I did this a long time ago so some of what I just said might be wrong, if you need more help then just say so.
I would like to use as a basis the stock rom 4.1.2 : N7000XXLT9_N7000ITVLT3_ITV.zip
I used the kitchen to create workfolder following all the steps suggested by the program , I found the following problems:
1 ) during the procedure appeared to me the following warning :
Warning : A valid boot.img is not found . You have the option to add a
' fake ' boot.img So THAT the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM 's
ZIP file When Is It built .
Add boot.img (y / n)? (default: y) "
is this normal? how to solve ?
2 ) Working folder information ( v)
Android OS version: 4.1.2
Device: GT- N7000
Model: GT- N7000
ROM Name : JZO54K.N7000XXLT9
CSC version: It 's normal that there is nothing written here ?
Rooted ( Superuser app + su) : NO
Rooted ( unsecured boot.img ) : UNKNOWN how I fix this ?
BusyBox installed : NO
BusyBox run-parts support: UNKNOWN UNKNOWN how I fix this ?
Apps2SD (Apps to EXT) enabled: NO
/ data / app enabled: NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support: NO
/ system / framework is deodexed : NO
/ system / app is deodexed : NO
modem.bin found: YES
ROM will wipe all data : NO
3) throughout the META-INF folder there are only 2 files: update-script; update-script.bak
4) scripts / get_api_level: line 18: more: command not found
5) I checked the update-script and there are 3 warning in the report:
7/101: copy_dir PACKAGEystem SYSTEM:
8/101: format PRELOAD:
>> WARNING: Partition not recognized
9/101: copy_dir PACKAGEreload PRELOAD:
>> WARNING: PRELOAD: not found in working folder
10/101: symlink dumpstate SYSTEM:bin/dumpcrash
11/101: symlink toolbox SYSTEM:bin/cat
82/101: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
83/101: run_program PACKAGE:create_preload_symlinks
>> WARNING: create_preload_symlinks not found in working folder
84/101: set_perm 0 3003 06755 SYSTEM:bin/ip
How do I resolve this? I tried a lot of on-line but have not found anything. My goal is to make me a custom rom from the last stock (LT9) ... what should I do?
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
ThaiDai said:
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
Click to expand...
Click to collapse
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
stefano_te said:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
Click to expand...
Click to collapse
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
ThaiDai said:
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
Click to expand...
Click to collapse
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
stefano_te said:
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
Click to expand...
Click to collapse
No. Because you do this partly when using the kitchen step by step. Or when changing your updater-script.
The kitchen is a great help and simplifies cooking a rom - but it still is a little bit more complicated than heating baby food in the microwave. And if you really want your "custom" rom you should start to learn what happens in each step. And this can't be done by revealing everything...