To developers.
My question is simple. After years to discover where are the files to the nominal capacity of a battery, i know that the system stores this data in a file called charge_full_design.
In my s3 neo (I9301I) the original battery capacity is 2100 Mah and that file contents only a number (2100000).
My answer is very simple. What are i to do to change this number with the capacity of my battery (anker 7200 mah) in that file?. The system tell me that i Can't do.
Thanks.
My rom now CM 11 ( )
Sincerely Juan Carlos
I have same battery...
take a try on TWRP mode
needforszpit said:
I have same battery...
take a try on TWRP mode
Click to expand...
Click to collapse
How do I edit files in TWRP?
chmod 755...or use total commander to edit file(root mode)
needforszpit said:
chmod 755...or use total commander to edit file(root mode)
Click to expand...
Click to collapse
In total commander it keeps saying that it can't be saved because of not enough memory. And in TWRP mod I slide to apply chmod 755 but then nothing happens.
755 chmod enable write access...
try to rename the file and after create a file with 7200000 with original name
needforszpit said:
755 chmod enable write access...
try to rename the file and after create a file with 7200000 with original name
Click to expand...
Click to collapse
When I rename the file it stays the same and nothing happens. Also when I try to Change the value in it, it always changes back to the original value when I save. I have System read write but it´s not working.
dead end...
needforszpit said:
dead end...
Click to expand...
Click to collapse
Do you have a suggestion on how to solve this problem?
without I know where is file located on system is littlebit hard to say anything.
But.... the file was writed by code included on another file... it's needed to find it because probably include the needed function
needforszpit said:
without I know where is file located on system is littlebit hard to say anything.
But.... the file was writed by code included on another file... it's needed to find it because probably include the needed function
Click to expand...
Click to collapse
The file is located in sys/devices/qpnp-charger-e89dec00/power_supply/battery "charge_full" and "charge_full_design". I don´t know if this is the correct file that determines the recognized battery capacity.
I try a solution bu its not tested...
1. download and install: https://play.google.com/store/apps/details?id=com.battery.chargingstatus
Install termux: https://play.google.com/store/apps/details?id=com.termux
2. Save on PC framework-res.apk ( find it on: /sytem/framework directory) editable in apk: /res/xml/power_profile.xml U find a line with: battery.capacity 2100....change to 7200
For that action I use Kubuntu linux and MC(midnight commander).
Save ....
3.Upload to your phone the edited apk.
4.Start recovery mode...delete original framework-res.apk and copy the edited apk
5. reboot sytem.
6. Start Termux and use commands:
su
echo 7200000 /sys/class/power_supply/battery/charge_full_design
7. Reboot
8 Start battery status app and its show 7200
needforszpit said:
I try a solution bu its not tested...
1. download and install: https://play.google.com/store/apps/details?id=com.battery.chargingstatus
Install termux: https://play.google.com/store/apps/details?id=com.termux
2. Save on PC framework-res.apk ( find it on: /sytem/framework directory) editable in apk: /res/xml/power_profile.xml U find a line with: battery.capacity 2100....change to 7200
For that action I use Kubuntu linux and MC(midnight commander).
Save ....
3.Upload to your phone the edited apk.
4.Start recovery mode...delete original framework-res.apk and copy the edited apk
5. reboot sytem.
6. Start Termux and use commands:
su
echo 7200000 /sys/class/power_supply/battery/charge_full_design
7. Reboot
8 Start battery status app and its show 7200
Click to expand...
Click to collapse
So I´m stuck on uploading the edited apk to my phone. Everytime I replace the framwork-res.apk with the modded version I get stuck on the boot image. I don´t know what the problem is.
"echo 7200000 /sys/class/power_supply/battery/charge_full_design".....useless...its not rewrite the file...
Other....the rewrite of framework-res.apk its just a "looklike" thing...in chargingstatus looks battery like 7200 but on system works like an original
Solution NOT works
Related
thanks to this page for teaching me: http://www.robmcghee.com/android/creating-an-android-update-zip-package/
note: although i am copying this from the page, this isnt a straight ctrl+c, ctrl+p from it. ive rewritten it with slightly more english. ok alot more.
before we start, grab ppcgeeks auto signer here, or nothing will flash anyway. its the easiest method since its drag, drop, and click.
also i recommend 7-zip but its not necessarily needed.
first step, make the folder structure.
ive included prebuilt updates to make it a little faster for you. they contain no actual files, just the appropriate folder structure and update script. they must be resigned if you add files and expect to flash them.
if what your looking for isnt included, make a folder and name it "workdir". this will contain your work.
this is just to make it easier to organize all your stuff. if you feel so inclined you can name it whatever you want, it doesnt really matter.
next youll need to make folders inside the workdir according to where your flashing stuff, ie if your flashing wallpapers youd need to make a structure that looks like this: "workdir/system/customize/resource"
next to make the update-script. this tells the system what to do.
first make this folder structure: "workdir/META-INF/com/google/android"
make sure you capitalize "META-INF"
now put a text file into the "android" folder and call it "update-script"
the easiest way to code it would be to copy this into it:
Code:
show_progress 0.1 0
copy_dir PACKAGE:(x) (X):
set_perm_recursive 0 0 0755 0644 (X):(y)
show_progress 0.1 10
replace the (x) with the directory in the root your flashing to in lowercase, ie system or data or sdcard.
replace the (X)'s with the same thing as (x) except in UPPERCASE such as SYSTEM or DATA or SDCARD.
replace the with the next directory in lowercase like media or app or customize.
note: if your adding to the root of (X) folder then leave this blank, no spaces or anything.
if your flashing an app it should look something like this:
Code:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:app
show_progress 0.1 10
after youve done that, save and close the file. now you need to take the extension off of the text file. simply delete the .txt at the end of the file.
if there is no extension showing, make sure you have "hide extensions for known file types" unchecked in tools> folder options> "view" tab.
second to last step! compress the workdir contents into a zip file, not the actual workdir though. it should look like this inside the zip: "update.zip/(folders)" not "update.zip/workdir/(folders)"
finally, sign the zip with the auto signer and put it into the root of the sd card.
boot into recovery and flash it up! with a bit of luck, it should work.
if you have any questions, problems, or concerns just post them. i have instant subscription to this thread and will be notified every 30 min when my evo fetches my mail.
Thanx for this thread!
Ok, my app should be installed in /system/app/
but is it possible to include in the same (app)update-script: delete /data/app/xxx.apk?
What directories do boot animations go into?
Awesome thread and thanks btw.
Foxwolfe said:
What directories do boot animations go into?
Click to expand...
Click to collapse
/data/local/
rori~ said:
Ok, my app should be installed in /system/app/
but is it possible to include in the same (app)update-script: delete /data/app/xxx.apk?
Click to expand...
Click to collapse
honestly, i couldnt tell you for sure but i dont see why you couldnt
Foxwolfe said:
Awesome thread and thanks btw.
Click to expand...
Click to collapse
thanks
I keep getting a syntax error. I am trying to flash silent.mp3 so i can select that in my notifications, because for some reason it does not have that option :/
can you let me know where I went wrong?
have tried both
set_perm_recursive 0 0 0755 0644 SYSTEM:media
set_perm_recursive 0 0 0755 0644 SYSTEM:notifications
but to no avail
what was the whole code in the update-script?
did you use the example i posted?
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:media
show_progress 0.1 10
daktah said:
what was the whole code in the update-script?
did you use the example i posted?
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
set_perm_recursive 0 0 0755 0644 SYSTEM:media
show_progress 0.1 10
Click to expand...
Click to collapse
yeah, sorry for not making it clear. Im kinda rote-learning this atm, I did a straight copy of your notifications script into my flashable-zip. when that didnt work I tried it with line3 modified as a stab in the dark.
what does the entire folder structure look like? if I am changing notifications is it /system/media/audio/notification where I put the files?
i believe it is
Code:
workdir.zip/
_system/
__media/
___audio/(files).mp3
_META-INF/
__com/
___google/
____android/update-script
if you still cant get it going i can assemble it for you
Just wanting to be sure here because Ive read the first post a few times and still can't tell. On the root of the update.zip I am supposed to create the folder structure that I want it to flash too. (ie. media/audio/ringtones) and then place the actual file that im flashing in that directory. (ie media/audio/ringtones/newring.mp3) At this point then the whole .zip dir would look like:
update.zip
__media/
_____audio/
_______ringtones/
__________newring.mp3
__META-INF/
_____com/
_______google/
___________android/
_______________update-script
_____CERT.RSA
_____CERT.SF
_____MANIFEST.MF
Then just sign the .zip and flash it... Is this correct?
You got it
Wow sounds real complex just to add an mp3 for a ringtone. I know if you create a file on sdcard
media/
audio
alarm
notifacation
And then put the file you want for what you want into the folder you want it for it will show in dropdown menu so you can select it.
Been trying to get googles auto app builder program to force download the sdk for devices so i can start there first. Want an app that forces mms to the sprint max of 5mb send limit and not stocks 2mb or handsents 1.2 limit. Will doing this according to thread give me an app that does this? What would i need to change? (guess you could make it faster than trying to teach me but still wonder)
jpwhre said:
Wow sounds real complex just to add an mp3 for a ringtone. I know if you create a file on sdcard
media/
audio
alarm
notifacation
And then put the file you want for what you want into the folder you want it for it will show in dropdown menu so you can select it.
Click to expand...
Click to collapse
thats true but installing saves space on the sd card and makes it load instantly instead of waiting for the sd card to be prepared
jpwhre said:
Been trying to get googles auto app builder program to force download the sdk for devices so i can start there first. Want an app that forces mms to the sprint max of 5mb send limit and not stocks 2mb or handsents 1.2 limit. Will doing this according to thread give me an app that does this? What would i need to change? (guess you could make it faster than trying to teach me but still wonder)
Click to expand...
Click to collapse
what? im lost lol
On wm arcsoft had a setting in the app that lets you change settings and change size limit to 500kb. You can also make these changes in regeditor. Android doesn't have a registory nor does there seam to be an app to install that will allow these changes. Wondering if your tutorial thread would allow the building of an app and what would i need to change to do this. Googles app builder program doesn't come preinstalled with any sdks and on a slow connection i can't get it to download.
if your saying building an app as in coding and assembling one then no as this is just a guide to make an installable zip to flash with ra or clockwork. youd need to use the sdk tools and such for that. but this guide should allow you to install pretty much anything into the nand from ringtones to apks and the like.
daktah said:
i believe it is
Code:
workdir.zip/
_system/
__media/
___audio/(files).mp3
_META-INF/
__com/
___google/
____android/update-script
if you still cant get it going i can assemble it for you
Click to expand...
Click to collapse
finally got adb to stop sh***ing itself. did it that way.
thanks for the help anyway.
so, i'm by no means an expert at this... but i was trying to make an update.zip for wallpapers. i've attached what i did, if you could take a peak at it and give me a pointer, that would be awesome!
path to my wallpapers...
using launcherpro
data/app/com.fede.launcher-1.apk/res/drawable-hdpi
data/app/com.fede.launcehr-1/apk/res/drawable-mdpi
granted, I'm trying to flash a theme, but it seems like the process and folder/file structure would be the same.
I've followed the steps one by one, but after flashing the .zip in recovery and rebooting, everything looks the exact same as it did before! I figured I would start with framewor-res, and see if I could get that to work before I started working on all the other images, but even after modifying all images, straightening out the .9.png's, and compiling everything correctly in Eclipse, I get nothing.
I have no effing clue what's going on, any ideas?
im on a mac, any suggestions for what i can use to sign the zip? i have apk manager and thempro and they can both sign apps but i dont know if its okay to use them to sign a flashable zip
Hi man!
I'm not do a Update.zip yet with your tutorial, but i have a question:
some Update.zip have a file named updated-binary together with update-script, how i do that file? because when i try to flash via OpenRecovery say's that coul'd not find that file: update-binary...
Sory for my english, i'm from Argentina, and i try not to use Google Translate...
Regards!!!
PS: Great work with this tutorial!!!
********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
Hi all,
i often noticed people(including me) who tried to modificate their framework-res.apk resulting in boot loops(e.g. looping at white/green quietly brilliant screen).
So i tried to find out a fast way to get back to my(original) framework-res.apk without usage of recovery console each time my framwork-res.apk did not work as expected.
How it could help you:
It's a fast way to:
check out your moddings when doing numerous modifications in different versions of your modded framework-res.apk on your way to get it to work.
if you want to get back to your original/working framework-res.apk, even when it boot loops!
Click to expand...
Click to collapse
When you do numerous modifications on framework-res.apk and your modded apk leads to a boot loop you will be able to replace the current apk through e.g. the original apk.
At this boot point(boot loop screen) Android nearly finished booting and you have access on ADB commands.
What do you need to do this:
Download and extract/install QtADB from the link below:
QtADB
to replace the erroneous(current) framework-res.apk by the original or a fixed one.
Click to expand...
Click to collapse
There's no need to describe how to get a copy of your untouched framework-res.apk from device, since there are numerous tutorials around here.
Please check this tutorials to get a copy of your apk.
Please note before beating your device:
this probably will work with the most visual moddings of framework-res.apk - but i can't guarantee it works 100%.
It probably will not work when you play around with hardware or connections setting, other apk's or other stuff in other folders, so i am not responsible if it does not work.
always backup your current ROM/settings/whatever and save a copy of your untouched framework-res.apk
There is a little catch in it in comparsion with using recovery:
After you did like described, you have to set your background image and your (google) accounts anew.
But this is just a little work and it's not necessary until your framework-res.apk is doing the modded stuff correctly - or if you want to set the original framework-res.apk back.
Click to expand...
Click to collapse
So let's start to revive your original framework-res.apk.
(Of course you can use this method to push a modded to your device, to check out if your modding works):
Boot your device and let it load until you're at boot loop
(Download, extract,) run QtADB
Navigate in left window(Computer) to your copy of original framework-res.apk(e.g. in root directory of SD card, but i recommend a folder on your computer)
Navigate in right window(Phone) to device folder /system/framework/
Use in left window(Computer) context menu on your original framework-res.apk and select copy or drag&drop it to right window to copy the original framework-res.apk to your device
(just ignore that your device is doing strange stuff then, since it cannot access your framework-res.apk correctly at this point)
Then enter shell of QtADB(at left toolbar of QtADB) and enter the following commands to set the apk's prermissions:su
cd /system/framework/
chmod 777 framework-res.apk
Reboot your device( e.g. by using top menu->tools-ADB->reboot)
Set your background image and your (google/HtcSense) accounts anew.
Hope it helps you a bit on modding,
Greetings, brush2(Stephan)
error
hey man, Im getting an error on this. I changed my transitions effects ( folder anim on framework-res.apk) using the app metamorph. well, now every time I open an app the phone ( xt920) reboot. I ask my friend that have the same phone to send me his framework-res.apk. I try to replace using this method but dont got. I draged and droped the new apk and when I would type the shell's code the last code dont work because it said that the file is a "read-only system". What can I do to have my phone back? Please help.
Thanks.
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 followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?
yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.
ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.
This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.
be careful, backup buid.prop and restore it after creating Box account.
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
I am having no luck finding a way to get root access from a computer.
deleted post
user error
The tumbleweeds are big around here
There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
But is there an app to copy my file over from my computer?
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.
jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...
its taking forever to install SDK
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.
yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?