Related
**VIDEO GUIDE ADDED BELOW**
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
(This should be done from stock 2.1 (JF6) but may not be required (got this to work while in phoenix 1.5 without reverting)- results may very in custom rom environments....
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.
fyi this fix is intended specifically for persons with borked product codes and imei's due to custom rom flashes and will not address nv_data issues of carrier blocks/etc. for those who had unlocked their devices and may in fact undo your unlock.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Android Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext. *Since i have good backups now on PC and external sd...i generally just edit the nv_data.bin file in place and save over the original in the efs folder.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete all nv_data files from efs folder EXCEPT FOR YOUR NEWLY CREATED NV_DATA.BIN. (Delete the following: .nv_data.bak, .nv_data.bak.md5 and the nv_data.bin.md5 files. This differs from video but i also delete any .nv_state or nv.log file present and they are recreated). FYI IF YOU ARE USING A GINGERBREAD ROM AND YOUR EFS CONTAINS .nv_core.bak and .nv_core.bak.md5 DO NOT DELETE THEM with the other .nv files.
15. (This step may not be necessary unless you lose your voice/data connection upon reboot)
Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
**NEW: VIDEO GUIDE**
SPECIAL THANKS TO CONNEXION2005 for providing the video guide below:
http://www.youtube.com/watch?v=JqLK_2I-SBM&feature=player_embedded#!
-----------------------------------------------------------------------------
*DISCLAIMER*
have already had one person post a response that this thread was misleading and stating that:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Click to expand...
Click to collapse
I have seen other users make this claim as well, however, they are either mistaken or what i experienced was a complete anomoly.
I had never backed up my efs folder or nv_data files prior to them being messed up (i didn't know they were there and had never used root explorer to view them until i had to research a fix). The first thing i did was use a hex editor to look at my nv_data.bin and its bak(s) and in fact none of them were good. They all contained wrong product code.
So the process i described was conducted without any previously backed up original nv_data.bin or nv_data.bak files.
I started with:
wrong IMEI
wrong product code
totally botched nv_data files with no backup of original unmolested efs folder or nv_data files
I ended up with
Restored original IMEI
Correct Product Code
Healthy/Correct nv_data files that i immediately backed up in multiple locations.
So if you didn't back up your original untainted efs or nv_data files and this fix doesn't work to restore your original imei and product code then allow me to apologize in advance for "misleading" you and trying to assist with your problem by posting what did in fact work for me.
--------------------------------------------------------------------------------------------------------------
DONATIONS NOT REQUIRED OR EXPECTED. IF YOU FEEL THIS THREAD HAVE HELPED YOU WITH A SICKLY DEVICE OR SAVE YOU ANY HEADACHE OR TROUBLE FEEL FREE TO CONTRIBUTE:
bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efa/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
I think i deleted the file i wasnt supposed to... can someone post that file?
krips2003 said:
Questions?
1) Do you need to be on stock jf6 or this can be done from the current custom rom?
2) Is this for restoring IMEI or Product code? (I guess imei doesn't change)
Thanks.
Click to expand...
Click to collapse
you should revert to stock to run this.
your welcome to try it with any rom you are using but i have only used it in stock jf6 as that was when i discovered the problem. I tried odin one click jf6 when i noticed both my product code and imei were wrong thinking go full stock reinstall would fix. No luck....with alot of reading i discovered one method of fixing the problem then also worked out the 2nd method that doesn't require adb or pc in case it needed to be done on the fly away from computer.
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
CapnPez said:
Shouldn't step 15. have
busybox chown 1001:1001 efs/nv_data.bin
instead of efa?
Click to expand...
Click to collapse
yes..thanks...duly noted and corrected
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
rwj5279955 said:
So when i open my efs folder, it's empty. Or it says iy's empty anyway. I couldn't get hex editor to save my file on the pc, so I figured I might give this one a try.
Click to expand...
Click to collapse
what are you looking @ your efs folder with? It shouldn't be empty...even if you had completely deleted your nv_data files when trying the other method there should have been other folders in /efs. You didn't cut and paste or move all the folders/files from efs (rather than copy) somewhere did you?
PS - aside from the files starting nv_ you should have two folders /efs/imei and /efs/.android
bames said:
There is already a guide for restoring IMEI and Product code with a PC and ADB moving files between phone and computer......so i thought i would provide an alternative method that can be done without a PC or ADB.
***IMPORTANT PRECURSOR - we will be working with an important system folder (/EFS) and its contents (nv_data files). It is important to back this folder up (we will be doing this in step 2 below). I first backed it up to my external sd card but i did also copy the backup folder to my PC just in case.***
This method assumes you are starting with a rooted phone w/ superuser rights
You will need the following APPS that can all be downloaded from market and, with the exception of Root Explorer, are all free:
A. Root Explorer (i know its paid but its the most $ worthy app i have encountered. You can use the free Android Mate as an alternative but not as robust or convenient IMO)
B. Busbybox (once installed from market open the app to install it)
C. Terminal Emulator
D. Hex Editor
E. SGS Toolbox
_________________________________________________________________
Once all tools/apps listed above have been downloaded proceed as follows:
THERE ARE 3 Total Lines you will need to edit:
00188008
00188010
00188020
1. Install Busybox if you haven't done so already.
2. Use Root Explorer to create EFS Backup folder on an External SD (if you don't have one you can use the internal sd and give it a generic name that you will be able to identify). When ROOT EXPLORER opens you will be in the system file directory to get to your internal sd card open the SDCARD folder (from there you will see your external sd card as well if you have one installed)
3. Use root explorer to view the open the EFS folder from your system directory. The EFS folder contains the file you will will need to edit and replace. Open the efs folder and use the multi-select copy to copy the following files: nv_data.bin and nv_data.bin.md5 (you can also copy their respective backup files nv_data.bak and nv_data.bin.md5.bak).
4. Staying in root explorer go back to parent directory (option at top of file/folder list) and navigate to the backup folder you created and paste the files there. While still in this directory make a copy of just the nv_data.bin and the paste is either in the root directory or external sd or internal sd if you do not have ext.
5. Open Hex Editor Application and open the copy of nv_data.bin from your external or internal SD (click the capacitive menu button on phone and select OPEN FILE)
6. Once the file opens click the capacitive button to bring up the menu again and select jump to address:
7. Enter 0188008
This will take you to line 00188008
8. Edit the last or 8th Block (last column of green text). Click in the box and edit it so that it reads 41.
LINE 00188008
Block 8 = 41
9. use menu to jump to address again and Enter 0188010
10. This will take you to line 00188010. Edit the first two blocks of green text from this line. Replace the #'s so that both of the first two blocks contain 54. (look to the text at the right of screen the first two letter should have changed to TT. To recap you need to edit Block 1 and Block 2 of line 0018010:
LINE 0018010
Block 1 = 54
Block 2 = 54
(text @ right should now read TT....SG)
11. Now look down to line 0018020 and look at the line. If you look at the line to the far right text you will see ATOR or ATMB (or something other than AATT) if your nv_is messed up.
12. You may need to edit blocks 2-4. They should read as follows:
LINE 00188020
Block 2 = 41
Block 3 = 54
Block 4 = 54
(the text at the right of your screen should now read AATT....)
13. Save the file and move it back to efs using root explorer copying over the original.
14. delete the nv_data.bak and the nv_data.bin.md5 files (leave the nv_data_bin.md5.bak in the folder..don't delete it).
15. Open Terminal Emulator and run the following commands:
su
busybox chown 1001:1001 efs/nv_data.bin
reboot
16. Once your phone has rebooted use SGS Toolbox APP to check your IMEI and Product Code to make sure the fix worked.
PS: Here are how the following lines should read (the ones in bold are the only ones you have to edit as line 00188018 will already be correct):
00188008|2e|34|00|00|00|00|ff|41|.4....A
00188010|54|54|00|00|00|00|53|47|TT....SG
00188018|48|2d|49|38|39|37|5a|4b|H-I897ZK
00188020|41|41|54|54|00|00|00|00|AATT....
PS - In terminal emulator after you enter your first Command Line
su
your keyboard may not pop back up. Don't worry if it doesn't just reopen it from your app drawer and proceed with line 2 and 3
Click to expand...
Click to collapse
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
KALI2000 said:
Does not work for me on jpx. This changed my product code, but not changed my imei.
I think we have to live with a generic imei.
However, thanks.
Click to expand...
Click to collapse
suspected would only work with stock. the generic id is less of an issue because i think as long as your product code isn't screwed in the nv_data files your original imei will restore upon reflash of stock.
One interesting thing and may be just luck. I had flashed all kinds of roms before and it usually changed the imei to the generic one but it was no big deal because it would restore when going back to stock (and the product code was never altered).
Since having them get messed up and doing this fix i have flashed multiple roms Axura, Assonance, Perception, Epsyl, and currently chronos and it has yet to alter my original imei in the process. Right now i am running chronos and it still has my original imei.
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post):
http://forum.xda-developers.com/showthread.php?t=786532
krips2003 said:
Also, you guys can also try using the 3 button fixed ODIN posted in the same thread instead of using DG's 1 click to stock jfs6 using ODIN. That might also fix the issues regarding product ID. Even if it doesnt resolve the product ID issue, you'll still be flashed to stock and then you can use the procedure mentioned in here to change your product ID. I'm using xda app to post so I cannot find a way to copy the link for that forum.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
here is the link odin files and 3 button fixed one click (scroll to 3rd post and it contains links to both versions):
http://forum.xda-developers.com/showthread.php?t=786532
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
rwj5279955 said:
Sorry, my files showed when i checked show hidden files.
Still, I'm gonna flash back to stock when I get home and try this again. Thanks for this.
Click to expand...
Click to collapse
hope it helps. let me know your results when you get a chance.
I did a similar method, but only changed the AATT part in a hex editor and moved the file back with super manager, gave owner full chmod access, rebooted, made sure kies mini detected my device and then reflashed stock/master clear.
Now everything is back to normal.
I don't have an EFS folder and a search in Root explorer finds no nv_data.bin.
Apparently I flashed too many ROMS...lol
So ... As I can get my imei?
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
EDIT - apparently my statement is incorrect in regards to the captivate. I had been researching fixing my unlock that got relocked and many on the Vibrant forums have the generic IMEI with no way back. As of Jan-3-2011 - bames testing shows that changing the product code, does indeed fix the IMEI - I have to assume that the encrypted IMEI in the nv_data.bin is tied to the product code (maybe a pad or salt) and the phone can't read the IMEI if the product code changes.
Still, the best solution, before any modding, is to back up nv_data.bin.
alphadog00 said:
This thread is misleading. There is no way to restore IMEI if you didn't back up your nv_data.bin before it got messed up.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
from my own experience you are either mistaken or my result was an anomoly.
I had NEVER backed up my efs (had never used root explorer and didn't know the folder was even there prior to researching a fix) folder prior to having my imei, product code, and nv_data files messed up. (Once it was discovered and started researching a fix i used hex editors to view my nv_data files and both the original and BAK copies were messed up).
I ran the fixes and in fact my original IMEI and product codes were restored and in fact have remained in tact for each of the 4 or 5 times i have flashed new 2.2 roms after completing the fix. Right now i am running Chronos and still have my original IMEI (not a generic).
Once i saw the fix worked and i had healthy proper nv_data files the first thing i did was back up the entire efs folder in multiple places.
I don't know if this is possible but it would be nice to have APN settings in the startup file. Have to re-set it everytime I try another build.
you can always add your APN settings in the apns-conf.xml located in system/etc/ then when you change builds, just copy it and put in int the new build in root/system/etc and it will be copied automatically to the specified location.
Thanks. I open the existing file but don't see all info there. Do you have an example?
I'm interested in this also. I find myself using a lot of Android builds and I always have to make some modification to the APN settings. What are you using to access that location? Droid Explorer?
Sorry, I've been lazy with learning how to modify the system files using ADB or Droid Explorer... I'll get up to speed soon enough.
I read in the SD-development thread about editing the
"GPS1_CLEANUP_ENABLED=1
HD2 have high current drainage(60mA) in the 0812 build. I noticed in /etc/gps.conf GPS1_CLEANUP_ENABLED was set to 0. After changing the value to 1. Current usage was back to normal 8mA"
I'm currently running the AmericanAndroid SD build and would like to change this value to 1. How do I access this? Using the phone, I went into file manager/etc and found the gps.conf file but how do I edit it? When I plug the phone to my laptop I can only view files from my SD card.
Thanks in advance, and sorry if this is a noob question.
Can anyone help?
During standy the battery drain is a consistent 60-70mA. Nothing is running, background data turned off, no wi-fi, no GPS, no sync.
rice-CHRISpies said:
I read in the SD-development thread about editing the
"GPS1_CLEANUP_ENABLED=1
HD2 have high current drainage(60mA) in the 0812 build. I noticed in /etc/gps.conf GPS1_CLEANUP_ENABLED was set to 0. After changing the value to 1. Current usage was back to normal 8mA"
I'm currently running the AmericanAndroid SD build and would like to change this value to 1. How do I access this? Using the phone, I went into file manager/etc and found the gps.conf file but how do I edit it? When I plug the phone to my laptop I can only view files from my SD card.
Thanks in advance, and sorry if this is a noob question.
Click to expand...
Click to collapse
You need to use a file explorer with root privileges. You can d/l ES File Explorer (or something like it) from the market for free.
When you run it, you'll be prompted to give it root (SU, or superuser) permissions. There's a checkbox in the menu, for you to do this anyway.
Most importantly - since the file system is read only - you'll have to also check the box directly underneath it in the root settings section of the menu to 'Mount File System'. This will make the files writable, so you can save your edits.
In general, you can keep the 'Root Explorer' box checked at all times, but it's not a bad practice to uncheck the Mount File System box when you're done so as to ensure against file changes.
gps.conf is located in the etc directory of the system. The line you want to edit is at the end of the file. When you make your change... don't forget to press the menu button and then press SAVE.
another user had similar problems - so you can take a quick look here...
http://forum.xda-developers.com/showpost.php?p=16735406&postcount=15225
Rob
thanx.works for me.
ke2v85 said:
thanx.works for me.
Click to expand...
Click to collapse
"Speaking of thanks, use the thanks button. Use it every time you get an answer, even if it's a one you don't like"
http://www.youtube.com/watch?v=JmvCpR45LKA&t=1m33s
I pressed it for you this time, next time you do it.
Hi there,
I am a user of the Redux2 HD2 ROM. With my own set 192 DPI. However as you will probably know many apps do not show up (cus of the old market, new one you'll see its "incomapatable"). And i was wondering if there was any fix for this. problem that sloves it well.
Now you have to change the DPI back, reboot, install apps, change DPI, reboot. There must be another way to this.
Since the HD2 has such an huge screen it is (imo) waaaaaaay more comfortable then the stock (oversized icons) 240DPI.
I agree that the 240 dpi makes the icons (and the whole display) too big for HD2. The ROM I use, had 167 dpi as default, but this caused compatibility problems to the newest Market app, so I changed it to 160. Here's how:
Install File Expert (file explorer). (you can use your preffered explorer for this, but keep in mind that you need to have root access and be able to change file permissions!)
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage/system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
This setting of 160 dpi might seem too small to you (compared to the 192 that you use) but trust me, after a couple of days you will like it and you won't have issues with the Market!
Sysifos said:
I agree that the 240 dpi makes the icons (and the whole display) too big for HD2. The ROM I use, had 167 dpi as default, but this caused compatibility problems to the newest Market app, so I changed it to 160. Here's how:
Install File Expert (file explorer). (you can use your preffered explorer for this, but keep in mind that you need to have root access and be able to change file permissions!)
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage/system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
This setting of 160 dpi might seem too small to you (compared to the 192 that you use) but trust me, after a couple of days you will like it and you won't have issues with the Market!
Click to expand...
Click to collapse
I think the question was more of trying to find a way around the DPI problem, not just changing it.
What if change the product name from HD2 to other native Android device in build.prop?
Could this work?
tharche said:
What if change the product name from HD2 to other native Android device in build.prop?
Could this work?
Click to expand...
Click to collapse
No since it wont change the fact that it uses a DPI that is not standard.
And i tested the 160 DPI and for some reason my rom (Redux2 HD2) is not compatable with those DPI settings (white statusbar if app is open) And some other weird glitches
Try this market, it's the old one but it's modified so the DPI isnt checked.
I use it and never had the problem of apps not showing up (as far as i know)
Just flash it in CWM or take the vending.apk inside the zip and move it to the /system/app/ folder on your phone
Please tell me if it helped.
Maxp101 said:
Try this market, it's the old one but it's modified so the DPI isnt checked.
I use it and never had the problem of apps not showing up (as far as i know)
Just flash it in CWM or take the vending.apk inside the zip and move it to the /system/app/ folder on your phone
Please tell me if it helped.
Click to expand...
Click to collapse
tested it. did not work.
try this then http://forum.xda-developers.com/showpost.php?p=20623581&postcount=10,
maybe in combination with Market Enabler to show country specific apps
Hi, I had beautiful widgets installed and it was not findeing the location automatically, I had to put the zipcode or the city. Now I copied the networklocation.apk from my phone to the kindle's in the system app folder and now it is finding it by geolocation.
Sent from my Kindle Fire using xda premium
I gave this a shot with nogo... CityID it pulls up with is jibberish and non-locational to where I am at.
Just so you know what I did...
o Copied com.google.androidlocation.apk to /system/app
o Rebooted the device
o Used BeautifyWidgets, selected Weather Widget Setting
o Selected Set Location
o Clicked Geolocation
Errors said Geolocation was not on
o told it to use it anyway
o Saved the settings.
krelvinaz said:
I gave this a shot with nogo... CityID it pulls up with is jibberish and non-locational to where I am at.
Just so you know what I did...
o Copied com.google.androidlocation.apk to /system/app
o Rebooted the device
o Used BeautifyWidgets, selected Weather Widget Setting
o Selected Set Location
o Clicked Geolocation
Errors said Geolocation was not on
o told it to use it anyway
o Saved the settings.
Click to expand...
Click to collapse
When you copy the app in the settings l, long press the app and choose permissiones and you must have it setup like the pic
Sent from my Kindle Fire using xda premium
Will this work with Google Maps as well?
EDIT: Yup, I am now finding my location in Google Maps as well. Saaweeet!
Used the same permissions as everything else in the /system/app directory
0644
Well my location is working I don't know why yours doesn't .
samomamo said:
Well my location is working I don't know why yours doesn't .
Click to expand...
Click to collapse
Samomamo, where did you get the NetworkLocation.apk package from, also did you have to adjust anything in Settings.db for any network settings?
I am completely stumped and have been scouring through myriads of posts for some shred of helpful info, so far this post and this one:
http://forum.xda-developers.com/showthread.php?t=1362472
but have had no luck with either one. I am wondering if the answer lies in from where you got your NetworkLocation.apk. Any help would great! Thanks!
I got the apk from my T-Mobile Galaxy s2
Sent from my SGH-T989 using xda premium
I downloaded the networklocation apk from the CM7 gapps. The followed the directions and it is now showing my location. I believe it will only show my location if connected to wifi though.
Gapps is found here : goo-inside.me/gapps/
Solved issue by adding files and editing framework-res.apk
If anyone searching is interested in how I was able to solve this I could not simply add the Google Network Location APK, I had to force the Amazon "framework-res.apk" file to recognize it by editing the '/res/values/strings.xml' with the following lines:
Same ol' disclaimers - I'm not responsible for whatever you do with this info, if you brick your device, its your decision to try and not my fault or issue to fix. This is nothing new I just put the various pieces together from research through other posts, forums, etc. so credit where credit is due.
irishmyles003 and samomamo thank you very much for your input. Though I wish your solutions would have worked I am glad I had this challenge as I think I taught myself a little more about how to mess around and tweak the system a bit.
I still added the NetworkLocation.APK as stated and explained by Samomamo, but I had the do the following steps in order to get the framework to actually react to network location requests, since it kept returning "null".
<<Original>>
Code:
<string name="config_networkLocationProvider">@null</string>
<string name="config_geocodeProvider">@null</string>
<<Modded>>
Code:
<string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>
<string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>
Steps:
Use ApkTool to pull "framework-res.apk" and decompile
Replace the lines above to match the modded section
Recompile the APK to "unsignedframework-res.apk"
Copy and rename original "framework-res.apK" -> "originalframework-res.apk" (put this file aside in case you need to flash if you make a mistake)
Rename the original and newly compiled files to .zip (so you can extract, edit, etc)
- "framework-res.apk" -> "framework-res.zip"
- "unsignedframework-res.apk" -> "unsignedframework-res.zip"
Extract "resources.arsc" from unsigned and paste (and overwrite) to the "framework-res.zip" file
Rename "framework-res.zip" -> "framework-res.apk"
Push "framework-res.apk" to device (need to mount /system r/w)
chmod 644 (i.e. <rw, r, r> for root explorer)
Reboot and voila it worked (for me at least)!
Sources / Props to the authors of these links:
I could not give correct props because I got these from outside links, but [email protected] and the Enable CRT Animation guide at freeyourandroid.com and the APKtool tutorial at miui-au.com
Also if you google using the info above you will find you can also enable the AOSP GB CRT Animation by editing a line in the bools.xml, I tried this and it works! Enjoy!.
EDIT: After applying the framework-res.apk and rebooting I just realized that my accounts were lost. I just had to re-add them via SyncSettings (Market: com.francesandmarky.android.syncsettings) - Amazon, Gmail, and Facebook.
rpw128 said:
If anyone searching is interested in how I was able to solve this I could not simply add the Google Network Location APK, I had to force the Amazon "framework-res.apk" file to recognize it by editing the '/res/values/strings.xml' with the following lines:
Same ol' disclaimers - I'm not responsible for whatever you do with this info, if you brick your device, its your decision to try and not my fault or issue to fix. This is nothing new I just put the various pieces together from research through other posts, forums, etc. so credit where credit is due.
irishmyles003 and samomamo thank you very much for your input. Though I wish your solutions would have worked I am glad I had this challenge as I think I taught myself a little more about how to mess around and tweak the system a bit.
I still added the NetworkLocation.APK as stated and explained by Samomamo, but I had the do the following steps in order to get the framework to actually react to network location requests, since it kept returning "null".
<<Original>>
Code:
<string name="config_networkLocationProvider">@null</string>
<string name="config_geocodeProvider">@null</string>
<<Modded>>
Code:
<string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>
<string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>
Steps:
Use ApkTool to pull "framework-res.apk" and decompile
Replace the lines above to match the modded section
Recompile the APK to "unsignedframework-res.apk"
Copy and rename original "framework-res.apK" -> "originalframework-res.apk" (put this file aside in case you need to flash if you make a mistake)
Rename the original and newly compiled files to .zip (so you can extract, edit, etc)
- "framework-res.apk" -> "framework-res.zip"
- "unsignedframework-res.apk" -> "unsignedframework-res.zip"
Extract "resources.arsc" from unsigned and paste (and overwrite) to the "framework-res.zip" file
Rename "framework-res.zip" -> "framework-res.apk"
Push "framework-res.apk" to device (need to mount /system r/w)
chmod 644 (i.e. <rw, r, r> for root explorer)
Reboot and voila it worked (for me at least)!
Sources / Props to the authors of these links:
I could not give correct props because I got these from outside links, but [email protected] and the Enable CRT Animation guide at freeyourandroid.com and the APKtool tutorial at miui-au.com
Also if you google using the info above you will find you can also enable the AOSP GB CRT Animation by editing a line in the bools.xml, I tried this and it works! Enjoy!.
EDIT: After applying the framework-res.apk and rebooting I just realized that my accounts were lost. I just had to re-add them via SyncSettings (Market: com.francesandmarky.android.syncsettings) - Amazon, Gmail, and Facebook.
Click to expand...
Click to collapse
Could someone post the modified framework-res.apk?
Why does it work for some but not others?
andTab, I tried but the max filesize is 8 mb for APK files, the framework-res.apk is 27-31 mb. I couldn't figure out why the original posters were able to do it by just adding the files. When I unpacked the APK it was intentionally set to null not allowing usage of the google location framework.
xxx.multiupload.com/5FJ4ZTH6TX (take out the x's, it wouldn't let me post the address b/c I am new)
Thanks for your work guys...
I downloaded and applied this frame work apk, the crt animation is now enabled, but google maps still not finding my location in the middle of Los Angeles.
Hmmmm
You still need NetworkLocation.Apk from Gapps put into /System/App (also run it from your SD Card), then reboot. The adjusted lines in the Framework-Res points to this framework.
So my evo 3d is running ICS, can I still use the file? Or could someone post a working one?
atomiclama said:
So my evo 3d is running ICS, can I still use the file? Or could someone post a working one?
Click to expand...
Click to collapse
irishmyles003 said:
I downloaded the networklocation apk from the CM7 gapps. The followed the directions and it is now showing my location. I believe it will only show my location if connected to wifi though.
Gapps is found here : goo-inside.me/gapps/
Click to expand...
Click to collapse
I'm not too sure, if you're working off stock the Kindle Fire uses 2.3.4 so I would use the 8/28 version from the website irishmyles003 provided.
Hmm still not having a whole lot of luck.
I downloaded the networklocations apk from gaps of the correct date. Also installed the updated framework. Like I said Im seeing CRT change.
I've set up the geo location through beautiful widgets.. but still not finding location.
What am I missing?
thanks
also when I placed the network locations apk I set correct permission and tried to install it, it said application not installed. Could to be part of the problem?
atomiclama said:
also when I placed the network locations apk I set correct permission and tried to install it, it said application not installed. Could to be part of the problem?
Click to expand...
Click to collapse
Placing it in the /system/app area is installing it.
Make sure you reboot for the system to see it though.
Note: I've not tried this patch...
I'm not exactly sure why it isn't working for you. I spent a few days looking at logcat's and forums. Don't forget to change the permissions (mentioned earlier in this thread) to 644.