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.
Hi,
I was wondering if somebody could upload system/app/DockService.apk from Bell. My system version is 45.2.17.MB860.BellMobility.en.CA
Looks like I removed the original DockService.apk by accident while I was testing out some WebTop feature.
Your help would be much appreciated!
Here are the steps how to get DockService.apk if you have Root Explorer and a micro SD card.
1. Launch Root Explorer (you will be on the root directory)
2. Scroll down and open "system" folder by tapping
3. Open to "app" folder by tapping
4. Scroll down until you find DockSerivce.apk
5. Hold down the file for a sec, you will see a pop-up window with options
6. Select "Copy" (you will see Paste and Cancel buttons at the bottom)
7. Hit back button twice (this will bring you back to the root directory)
8. Scroll down until you find "sdcard-ext" folder
9. Tab the folder and tap "Paste" button at the bottom
10. Plug your atrix onto a pc and go to your the SD card on Windows Explorer
11. Upload the file
It's much simpler than how it looks.
I found out that my DockService.apk was the original. The reason why it didn't work was the permissions got changed during copy & paste some how. I changed the permissions back to rw-w-w like other files in "app" folder, everything works fine.
I am following the instructions as per the below thread to allow my Acer a500 see my Nokia N900 for tethering purposes.
http://forum.xda-developers.com/showthread.php?t=1033314
I have copied the wpa_supplicant file over the one thats already there.
Now when I open the Terminal Emulator to try ADB remount it comes with an error saying device not found.
I have the wifi turned off, I also have Root Explorer, but I found File Manager HD quite handy.
Now after trying the instructions I now dont have wifi - it comes with an error.
I have tried copying the stock wpa_supplicant file across, with no success.
Can someone please help.
to get AD-Hoc working you first need root and either root explorer (paid app but worth the money) or es file explorer (free but you have to enable root privaleges inside the app. its under the settings menu)
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
This is the easiest way to fix this... make sure in root explorer you set to rw at the top left in order to rename copy or past into this directory..
Good luck
this is the file .
View attachment wpa_supplicant.zip
Thanks for that, your a genius.
Now that my device can see my phone, I cannot see any web pages.
Is there something else I need to do?
That is very odd .. try rebooting the phone and the tablet..
also try on the tablet
go to settings / applications.. go to the web browser.. and clear cache and data..
is only thing i can think of ..
never had a issue other then my cell sometimes get hung on a cell tower and a reboot fixes this.. .
try connecting another wifi device to the phone to determine if its the tablet or phone..
I ended up changing the program I use to tether on my N900 and now works a treat.
Once again, thanks for your help
Thanks erica_renee . Worked right on point !
You are way too much girl....)))
So I guess THAT's why we should be nice to her!
Thsnks guys.
Now bring me my coffeee
erica_renee said:
Thsnks guys.
Now bring me my coffeee
Click to expand...
Click to collapse
I'll bring nothing, but the world
Works on Ideapad K1
Erica_renee, you are awsome!
I followed your instructions and BAM worked first time.
Thanks
You are Very welcome..
But i do want to point out They are not my instructions..Its been so very long ago i dont remember who to give the credit to.. I think someone from the Zoom Forum..
I just remembers how to do it and do not mind sharing what i have learned with anyone...
So i guess i should say thanks to everyone who is actually a developer or close.. for all the hard work they have done to make my tablet enjoyable to use..
erica_renee said:
to get AD-Hoc working you first need root and either root explorer (paid app but worth the money) or es file explorer (free but you have to enable root privaleges inside the app. its under the settings menu)
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
This is the easiest way to fix this... make sure in root explorer you set to rw at the top left in order to rename copy or past into this directory..
Good luck
Click to expand...
Click to collapse
I clicked the "Thanks" button but this one deserves more than that! Thank you so much GG, you've made my day!
Regards,
Bob
Ahhh!
Thanks.
Now I can use more than my phone while travelling.
erica_renee said:
to get AD-Hoc working you first need root and either root explorer (paid app but worth the money) or es file explorer (free but you have to enable root privaleges inside the app. its under the settings menu)
1. navigate to system/bin and copy wpa_supplicant
2. past this to your sd card as a backup
3. rename wpa_supplicant to wpa_supplicant.old
4. extract the file from the download and past it into the system/bin folder. (should be wpa_supplicant)
4. Long press on the file once copied
6. select Permissions and set to User: RWE, Group & Others:RE only
This is the easiest way to fix this... make sure in root explorer you set to rw at the top left in order to rename copy or past into this directory..
Good luck
Click to expand...
Click to collapse
I downloaded es file explorer and enabled root exploring as well as "Mount File System" (which is supposed to make the system writable) and with or without the mount file system, I cannot find the System file nor bin. I have the Samsung Galaxy Tab 8.9 Wifi Only. It's running Honeycomb 3.2. Any suggestions?
Not my credit
This fix is not from me.. I just re posted something that has been around since our tablet was released.. I would say give that person the credit. I am not sure who actually did it .. I think that file originally came from the ZOOM FORUM.
Anyway Just wanted to make sure that was POINTED OUT.I only know from what i have read for my own personal use.
Thanks All ... Erica Renee
Firecracker_RC said:
I downloaded es file explorer and enabled root exploring as well as "Mount File System" (which is supposed to make the system writable) and with or without the mount file system, I cannot find the System file nor bin. I have the Samsung Galaxy Tab 8.9 Wifi Only. It's running Honeycomb 3.2. Any suggestions?
Click to expand...
Click to collapse
Can anyone help me with this?
check you su. update the su root binaries . make sure busybox is installed and updated..
you can check the last two with root checker . a app on the market..
There iss also somewhere in the settings. that show a mount point . .something like /mnt/sdcard.
this should be just a / in there to have access to the system folder. I dont have es file explorer installed as i did not like it.. but i do remember having to change this defalt mount or folder option.. Astro file manager and some others also have this defalt . You can also keep going back and will take you there ..
Even though Titanium Backup says I have BusyBox, another app I tried to install said I did not and needed to install, so I went to the market to install and BusyBox says I need to perform Nand Unlock before installing BusyBox. Can you point me in the direction for doing that. I have the Galaxy Tab 8.9 Wifi Only. I see alot of stuff out there but not sure if it's right for my tab or if the instructions are universal to android users. How did you do Nand Unlock?
One of the main drawbacks of 5.1.1 update on Yureka was that the stock dialer had been replaced by Truecaller dialer. I, for one, liked the original dialer a lot. It had dynamic speed dial tiles which changed according to how much you called, which is probably one of the best features. Also, there's privacy issues associated with Truecaller dialer, if you're into that sort of thing.
To change the dialer, we'll simply replace the phone UI components with blisspop components. Blisspop has stock Android dialer.
Also, this is my first guide, so if mods think this is not in appropriate section, please move it to proper section.
Prerequisites:
1. You should have Yureka [duh]. I don't know if this works on Yureka+. Maybe someone can test & tell me so that I can update this guide.
2. You should have write access to the root partition of your phone.
What is root partition you ask? Yureka has Internal memory [Sdcard0], External memory card [Sdcard1] & a third partition, root partition[/].
You can access this partition using any reputed file manager such as ES file Explorer, Solid Explorer, Root Explorer etc.
However ES, Solid etc. had problem writing files in my phone. I therefore went with Root Explorer which works flawlessly.
From hereon, I'll consider you are using Root Explorer. However using any other file manger will be similar.
The only caveat in using Root Explorer is that writing permission requires root access.
Steps:
1. Open Root Explorer. Tap "Mount R/W". Grant it the superuser permission when it asks. This puts the Root explorer in Write mode for root partition & we can now write or over-write files which we want.
2. Download the zip file from here & extract it somewhere on you phone.
3. In root partition [the one with symbol "/"], go to system-->app and replace or overwrite the InCallUINext folder with the folder which you have downloaded from the zip file. Make sure you have backed up the original folder which was previously present i.e copy it somewhere on phone memory just in case.
4. Then go to system-->priv-app and replace or overwrite the DialerNext folder with the folder from the zip. Again make sure you've backed it up.
5. That's it. Reboot the phone & you have the stock dialer.
Credits to @Sundara Prakash & also to @Vams for prodding me in the right direction.
Hit Thanks if you think this helped!
Introduction:
This is a long but detailed guide to move user apps to system and to make them survive OTA so they will get restored on flashing every OTA(any rom?). This is lengthy but has to be done only once.
Things needed:
Unlocked and rooted device with TWRP installed and on any custom rom like Lineage which supports addon.d (NOT MIUI)
60-apps.sh
Link2sd
Titanium backup
A PC with any good notepad editor (I use notepad++)
Directory Printer
A USB Cable
Some free space (2GB) in internal/external sd card) temporarly
Little time and presence of mind (can't give link, sorry)
See Screenshots (folder) if it gets confusing, they are numbered 1 to 40 so it will be easy to understand.
Instructions:
1. Install you favorite rom and set it up. Install all the apps you use(do set the apps, just install for now). Once done, Install link2sd and titanium backup too.
2. Open link2sd and grand root permissions.
i. Tap menu and then Storage Info to check how much space do you have in System
ii. Tap back and set sorting mode to apk+dex+lib size and filter to User apps (both buttons are next to menu, you can't miss them)
iii. Now tap and hold on any application name you want to move to system, ideal apps would be like Greenify, Instadic, Truecaller etc. (apps you want to let run in background), apps you always keep in your phone or apps which are big in size. I used Kernel Adiutor-Mod here to demonstrate.
Move all the required apps and keep checking system space, leave 100-200mb free.
3. Once done, Reboot to TWRP
i. Tap Mount and put a tick before System
ii. Go back and Tap Advance--->File manager
iii. Scroll to find system, open it and find priv-app, open it too (you are here- /system/priv-app)
iv. Tap menu button and copy folder, scroll to find sdcard/sdcard1, again tap menu botton and swipe to copy. (i used Alarms folder in /sdcard)
4. Once done, Connect the phone to PC.
i. Make a folder (name it sysapps) and copy this priv-app folder in sysapps folder. (delete from sdcard)
ii. Download 60-apps.sh from here and place it in sysapps folder too.
iii. Open priv-app folder and delete everything except the apps you moved. Tip-Default system apps should have proper names like Settings. SystemUI, Velvet(gapps too) etc.
iv. Run Directory Printer and click save to disk. Set everything as shown here and navigate to \sysapps\priv-app folder.
v. Click Save to disk and again navigate to sysapps folder, name the file as my.txt and save it.
5. Run Notepad++ and open my.txt in it.
i. Press ctrl+h to open replace, write everything written before priv-app in find what column and delete everything written in replace with column. Click repalce all. (we are removing everything written before priv-app in every line)
ii. Again write \ in find what column and / in replace with column. Click replace all.
6. Open 60-apps.sh in notepad++
i. Look for addon.d/60-apps.sh under list_files() {
ii. Select and copy everything from my.txt and paste it between addon.d/60-apps.sh and EOF (there is a blank line there, check and delete if any blank line remains after pasting)
iii. Once done, save it and exit notepad++.
7. Now copy/move this 60-apps.sh to sdcard and disconnect the phone
i. As done above to copy priv-app from system to sdcard, copy 60-apps.sh from sdcard to /system/addon.d
ii. Navigate to /system/addon.d and tap 60-apps.sh. Tap chmod 755. Swipe to confirm.
iii. Reboot your phone.
8. Use your phone as you do and flash any ota without wiping system. If changing rom, try deleting everything except priv-app and addon.d folder in system, instead of wiping system partition completely.
Moving updated apps to system:
Occasionally apps will get updated and they will start to acquire space in data. To move them back to system do this.
1. Open titanium backup, tap Backup/Restore, tap click to edit filters and under Filter by type tap User and Uninst. to leave just System enabled. Tap green Check above right to set.
2. Tap Order by app name (click to change) and tap last update time.
3. Backup all updated apps temporarily and close titanium backup.
4. Open link2sd and set filter to Updated
5. Tap and hold on app's name and tap Integrate update into system
6. Once done, reboot.
7. Open titanium backup again and restore data only for the apps you backed up.
reserved
Wow. Thanks bro
reserved
Isnt repartition of data system would serve better for this.
Camlin3 said:
Isnt repartition of data system would serve better for this.
Click to expand...
Click to collapse
Yes definitely. But I am not familiar with qcom much. Had done that on mtk before.
Sent from my Redmi Note 3 using Tapatalk
Sudeep Duhoon said:
Yes definitely. But I am not familiar with qcom much. Had done that on mtk before.
Click to expand...
Click to collapse
Yes, its a little easy for mtk. Me Too played with mtk phones
Sudeep Duhoon said:
Yes definitely. But I am not familiar with qcom much. Had done that on mtk before.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
You think it can be done however? In TWRP there's an option for repartition. But obviously I guess it isn't that simple :silly:
Does it require developer-level skills?
Thanks for the guide, BTW!!:good::good:
iG0tB0lts said:
You think it can be done however? In TWRP there's an option for repartition. But obviously I guess it isn't that simple :silly:
Does it require developer-level skills?
Thanks for the guide, BTW!!:good::good:
Click to expand...
Click to collapse
Yes. can be done. but not through twrp. How? i don't know for sure yet.
Ty very much for this guide