DISCLAIMER: Please bear in mind that my flashing didn't end up perfect and I'm still learning. That said, we're just gonna be copying some files so I think it's kinda harmles to the phone. It worked for me, but it doesn't mean it will necessarily work for you, I post this because I think it's important that we share our experiences so we can learn from each other. Also I cannot guarantee that it will restore everything. In short what I mean is you do this under your own risk. This procedure was tested only on the following models. If you have success in other models please post back so I can update the list
Tested:
- Galaxy 551 (GT-i5510L)
- Galaxy mini (GT-S5570L)
1. Type *#272* IMEI # on your phone. In the little white box that appears on top there's a 3 letter code, that's your CSC code. Now hit the back button. (DON'T click "Install")
2. Go to /system folder and look for the file "CSCFiles.txt". To make things easier copy it to your sdcard and then download it to a pc so you can watch it during the procedure.
That file lists all the files that the phone uses to install a new CSC when you enter the code *#272* IMEI # so basically what we have to do is go through the system folders looking for those files and back them up in the sdcard or to a pc (your choice). Also back up with Ti Backup (just in case, you should always do a backup)
3. Flash.
4. After flashing go to the /system/csc folder. Inside this folder we have subfolders named with the codes of all the CSC included in the CSC file. What we need to do is create a folder with our CSC name (my case it was CTI) and then put all the files we backed up earlier in it.
5. Take your backed up CSCFiles.txt and back it up again, we're gonna be modifying it (TIP: if you're using Root Explorer for this process it makes a backup for you named CSCFiles.txt.bak).
6. Now we are going to tell android where the files are now so it can install them. Open your CSCFiles.txt for editing (note: I edited with Root Explorer, I just opened the file with windows Notepad to copy some sections for this post and it opened all in one long line, so it's probably not a good idea to edit it on windows) mine looked something like this
Code:
/system/media/bootani.qmg
/system/media/video/shutdown/shutdown.qmg
/system/media/audio/notifications/Claro.mp3
/system/CSCFiles.txt
/system/csc/contents.db
/system/csc/customer.xml
/system/csc/isnew_csc.txt
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/SW_Configuration.xml
/system/wallpaper/drawable/wallpaper_claro.jpg
/system/wallpaper/drawable/wallpaper_claro_small.jpg
/system/wallpaper/default_wallpaper/default_wallpaper.jpg
/system/app/LauncherMyfiles.apk
/system/app/YahooSearch.apk
/system/app/Plugger.apk
/system/app/MBO2_SMS_I5510L_CSBP_AMX_302.apk
/system/app/LauncherMessage.apk
/system/app/LauncherCamera.apk
/system/app/LauncherStk.apk
/system/app/CTI_Link.apk
/system/app/AMXNotification.apk
/system/app/LauncherCalendar.apk
/system/app/ASCR_SMS_i5510L_ML_AMX_301.apk
/system/app/LauncherContact.apk
/system/app/TopappMessage.apk
/system/app/LauncherMusicplayer.apk
/system/app/LauncherSettings.apk
you can tell there are some customized animations (with the operator logo) and sounds, then some bloatware and apps (which I didn't chose to restore) and then there are these files
Code:
/system/CSCFiles.txt
/system/csc/contents.db
/system/csc/customer.xml
/system/csc/isnew_csc.txt
/system/csc/others.xml
/system/csc/sales_code.dat
/system/csc/feature.xml
/system/SW_Configuration.xml
I only copied these files to the /system/csc/CTI folder we previously created and now comes the "tricky" part. You have to copy the files maintaining the path that the file says. i.e. the CSCFiles.txt goes into /system/csc/CTI/system/CSCFiles.txt then sales_code.dat goes in folder /system/csc/CTI/system/csc/sales_code.dat and so on. Then we have to edit our CSCFiles.txt to reflect these new paths so it will look something like this
Code:
/system/csc/CTI/system/CSCFiles.txt
/system/csc/CTI/system/csc/contents.db
/system/csc/CTI/system/csc/customer.xml
/system/csc/CTI/system/csc/isnew_csc.txt
/system/csc/CTI/system/csc/others.xml
/system/csc/CTI/system/csc/sales_code.dat
/system/csc/CTI/system/csc/feature.xml
/system/csc/CTI/system/SW_Configuration.xml
7. Finally if we've done eveything right when we type *#272* IMEI # our CSC will be listed and we can chose it, select it.
WARNING: THE FOLLOWING STEP WILL ERASE ALL YOUR PHONE DATA AND PERFORM A HARD RESET
8. Click "Install". The phone will shutdown.
9. Turn it on, an image of the little green droid with a box appears for a while and then the phone shuts down again. Just wait a little longer and it will reboot itself and presto!! You have your phone flashed and with your CSC restored!! (and hopefuly everything works out fine). Note that this time the reboot can take longer since it copies all the files before starting the OS.
This is my first Howto so any questions, comments, help will be greately appreciated and encouraged. I will try to answer if I can. Also if you try this on a different phone please tell me so I can start making a list with supported/not supported devices.
Finally!!!
Worked like a charm. I was able to restore the original CSC on my device and proceed with carrier updates. Thanks so much!
jmlowes said:
Worked like a charm. I was able to restore the original CSC on my device and proceed with carrier updates. Thanks so much!
Click to expand...
Click to collapse
I thought this post was dead. But I'm glad to see it helped someone!
Has anyone tested this on an i9100?
this should be sticky since there had been success and the OP did post proper tutorials...
swnt said:
Has anyone tested this on an i9100?
Click to expand...
Click to collapse
So far, I have only tested it with Galaxy GT-I5510L and Galaxy GT-S5570L it "should" work in other models if they maintain the same csc file/folder structure. If anyone tries this and it works for another model please post back results and I'll update first post
Very helpful !! Must be a sticky
Finally!!!
Hey! I tried this method with my Galaxy y 5360L and it works perfectly...
THANKS!!!
Pir8 said:
Hey! I tried this method with my Galaxy y 5360L and it works perfectly...
THANKS!!!
Click to expand...
Click to collapse
Glad it helped!
Veryy usefull, as many dumbs make faults in flashing.
But you could first explain to them what a CSC is
Sent from my Galaxy Nexus using Tapatalk 2
mDroidd said:
Veryy usefull, as many dumbs make faults in flashing.
But you could first explain to them what a CSC is
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i think CSC mean country specific code
I have a little warning for this: the "contents.db" is actually an SQLite file, which contains the full path+name and the filesize of the CSC files. I think that this file should be edited when you change the path or the size of your CSCs. Screenshot attached
Thanks man! It really helps alot!
Related
There is a font on another rom that I like, how would I get that installed onto my Eris? I have the file from the other rom.
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
bftb0 said:
Have a look at T2noob's batch file font installer for ideas (and fonts, too).
Looks like he takes a pair of True Type (.ttf) files - one regular face, one bold face - and copies them to
/system/fonts/
renaming the (respective) .ttf files to "DroidSans.ttf" and "DroidSans-Bold.ttf"
Then, just reboot.
That was done for rooted 2.1 ROMs; I'm not sure if it the same for AOSP or CM6 Froyo ROMs
good luck
bftb0
Click to expand...
Click to collapse
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
johnny quest said:
Thank you so much, this helps. I posted a question to his thread on the other site, but is it possible, since the fonts are in "true type" format that I can use some of mine?
Click to expand...
Click to collapse
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
bftb0 said:
The best way to find out is to try.
Just make a Nandroid backup before you start, and then there is zero risk involved in trying.
bftb0
Click to expand...
Click to collapse
Ok, thanks I will give it a try.
johnny quest said:
Ok, thanks I will give it a try.
Click to expand...
Click to collapse
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
johnny quest said:
I used the T2Noobat but it says Device not found but when I go to the folder where my font is, its not there. So I don't know if I have to reboot my phone in order for my font to take effect. Or, the way you said about system/fonts..... I don't know where in my sd would I find the fonts in order to change it.
Click to expand...
Click to collapse
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
bftb0 said:
If you get errors, it is not reasonable to conclude that the install worked despite the errors. That's what error messages are for - to tell you that something went wrong.
T2noobs .bat file (script) presumes that you have:
1) ADB working on your PC (generally by installing the Android SDK or HTC Sync + adb)
2) That your phone is connected via USB cable
3) That your phone has USB Debugging turned on
4) That your phone is running a rooted ROM.
You don't have to use his script. I mentioned it as an example. You can just use a root-aware file manager (RootExplorer or Estrongs File Manager), and re-mount /system in RW mode, and then drop your two True Type fonts into
/system/fonts/
with the file names "DroidSans.ttf" and "DroidSans-Bold.ttf"
and then reboot. Obviously, there will already be files in there with those names to begin with, so you need to either (a) rename them to something else, (b) move them to some other folder, or (c) delete them.
I don't know how to make this any clearer.
You probably should spend some time learning how to perform Nandroid backups and restores before you do any of this (if you have not already mastered those skills). Having good backups will save your butt.
bftb0
PS. I just did this on my (CELB 3.2) ROM, so I know it works - assuming you are not using some screwy fonts.
Click to expand...
Click to collapse
Thank you so much, I've been living on backups and restores. believe me I've learned my lesson. I will give this a try.
Your method worked great with the Root Manager. I bought it on the market. Ok, my biggest problem now is that my font is microscopic small. I don't know why. But I can't see the letters of which folder I'm in to take that font out.
I need a favor: can you post up screenshots or the number of folders to scroll down to get to the system/fonts/droidsans.tff
I can't see it, really its that small its the universal acc font.
Never mind I got it. Took a lot of squinting but I got it. Thanks.
Hi,
I have managed to lose my IMEI and empty my /efs folder. I was using the Gingerbread Beta 2 ROM provided by Whitehawkx on my Samsung Vibrant. Everything was great for me, I was loving it and was using it as daily driver. Until one day, my cell was in my pocket and I realized it was overheated. I removed it from my pocket and saw that it was frozen and had the double rainbow screen. I removed the battery to switch it off and restarted.
Since that moment, I lost all the files under my /efs folder and also lost my IMEI. As a result my phone does not recognize any SIM card. I can use all other functions like wifi, bluetooth, etc. but cannot use any phone functions like calling, sms, etc.
Please please please help me out to resolve this problem. I do not have backup of my /efs folder. I do have nandroid backups of my JFD, JI6 and KA6 ROMs. (if that helps in any way)
I have already tried going back to Stock JFD with clear efs checkbox checked using odin but no luck...
Please Help & Very Thanks in advance...
P.S. Let me know if you need any more details...
This is tricky, but it can be done, I am not sure how much your phone is jacked up. But here is a link explaining how to do this, read carefully a few times before you proceed:
http://forum.xda-developers.com/showthread.php?t=881162
Good luck
oka1 said:
This is tricky, but it can be done, I am not sure how much your phone is jacked up. But here is a link explaining how to do this, read carefully a few times before you proceed:
http://forum.xda-developers.com/showthread.php?t=881162
Good luck
Click to expand...
Click to collapse
Thanks oka1,
But before your reply I did something because of which I am screwed even more
While trying out everything, I flashed my Vibrant with the International Samsung Galaxy S ROM - 'I9000DDJF2'. I also used the CSC file that came with it.
This did not solve my IMEI problem but then now I can't go into Download mode or recovery mode as we do not have the home key that International Galaxy S has.
Please help me get in Download mode or Recovery mode so that I can get back to Vibrant ROM.
we do have a home button. use that to go to DL mode.
how come did that messed up your eds? was it told that you need to backup your efs folder?
Sent from my SGH-T959 using XDA App
Got lucky, managed to get into Download mode. Found this post 'http://forum.xda-developers.com/showthread.php?t=728698', the key was - "If you still can't enter download mode, you may want to try holding down the volume key + the power button. Plugging in your USB cable may also aid your efforts to enter download mode."
But this does not solve my lost IMEI and /efs problem. I did not know about backing up the /efs folder :-(
I am trying my hardest to try and restore my IMEI...
just get a replacement. that's the easiest way I think.
is your phone unlocked?
Sent from my SGH-T959 using XDA App
Hey Im looking now through some old threads, might have a fix.
I did that too, but luckily, after that, i bricked.
Backing up /efs will avoid any problems like this?
Potential Fix
I attached a screenshot of the files that should be in your efs folder. When I unlocked my phone, it required deleting all of the nv files besides the log, which leaves -
The .android folder is empty
The .imei file contains your imei number (found under your battery - put it in without slashes)
The imei folder which contains bt.text with your bluetooth mac address and a code file with the word XEN
I would recommend ODIN back to stock, root, set up this file structure (leaving out the nv files), then download the sgs unlock tool, and run it. People have reported success using the unlock tool to rebuild nv_data.
If this fails try reading through this thread - http://forum.xda-developers.com/showthread.php?t=879189&page=3
Thanks guys for helping out...
@iynfynity - My phone is unlocked. I can't get replacement since I am not in US. I bought it from ebay.com.
@pvspencer22 - I will try the way that you have mentioned. I thought since I am not in US, I can request someone from US to share their /efs folder contents. A nice guy from xda was ready to do that but then he was not comfortable :-(
Ya I wasn't to comfortable with it. It just doesn't seem safe for me to give someone else my IMEI. And plus I dont think it would work on your phone anyways, because the efs file wouldn't match your phone
Sent from my SGH-T959 using XDA App
pvspencer22 said:
I attached a screenshot of the files that should be in your efs folder. When I unlocked my phone, it required deleting all of the nv files besides the log, which leaves -
The .android folder is empty
The .imei file contains your imei number (found under your battery - put it in without slashes)
The imei folder which contains bt.text with your bluetooth mac address and a code file with the word XEN
I would recommend ODIN back to stock, root, set up this file structure (leaving out the nv files), then download the sgs unlock tool, and run it. People have reported success using the unlock tool to rebuild nv_data.
If this fails try reading through this thread - http://forum.xda-developers.com/showthread.php?t=879189&page=3
Click to expand...
Click to collapse
I tried these ways, no luck :-( Seems that the only possible way to resolve this is if someone agrees to share the contents of /efs folder of a working spare vibrant phone. But then no one is ready to do this...
Wonder if it could be possible for YOU to give your information from your phone & battery to someone on here that could make edits to their files with your info and send it to you??
jmcghee1973 said:
Wonder if it could be possible for YOU to give your information from your phone & battery to someone on here that could make edits to their files with your info and send it to you??
Click to expand...
Click to collapse
Not a bad idea
Sent from my GT-I9000 using XDA App
My original IMEI was 351801041232857.
My phone model is TMo Samsung Vibrant, I bought it from ebay.com.
Not sure what other details would be required as the only thing different is the IMEI, rest would be just as any other Vibrant phone.
Currently I am on stock JFD (downloaded from xda) and my /efs folder is completely empty.
Guys, please let me know if any other information is needed. I would be more than obliged to provide it. I am just trying out all possible ways to resolve the problem and I deeply appreciated each and every message coming my way... This is what makes xda so special...
As I have said, my handicap is that I am not in US, else I could have easily asked T-Mobile to solve this problem for me...
FATEOWNZYOU said:
Ya I wasn't to comfortable with it. It just doesn't seem safe for me to give someone else my IMEI. And plus I dont think it would work on your phone anyways, because the efs file wouldn't match your phone
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I have nothing against you mate, you were just trying to help... I have completely understood your concern...
About the second part whether it would work or not, we need to try it first to figure out whether it works out or not. That is why we are here... trying to help each other out...
Guys, someone please help me out with /efs folder contents of a spare Vibrant phone...
kisfit2000 said:
Guys, someone please help me out with /efs folder contents of a spare Vibrant phone...
Click to expand...
Click to collapse
reply if you still need help. I got a solution as long as you have the backup efs folder.
iynfynity said:
reply if you still need help. I got a solution as long as you have the backup efs folder.
Click to expand...
Click to collapse
Thats the main problem, i do not have backup of my efs folder. My efs folder is empty and hence I am requesting someone to share their efs folder contents :-(
I need a vounteer helper who can share his efs folder contents...
Please...
About:
This tool is meant to easily compare the contents of two rom archives and allow easy manipulation by copying files from one rom to another and removing files from a rom archive. The idea is to specify two rom archives which have the same structure, usually something like the following:
[data]
[META-INF]
[sdcard]
[system]
flash_image
modem.bin
zImage
I made it because I would like to know which files/apks might have been removed from one rom compared to another, which isn't always clear from the descriptions. But then thought other people might find it usefull as well, so here it is
It's written in java, just extract the zip and run through run.bat (windows only) or the .jar file.
Update, version 2 added
Ok, I tested it today and seems to work fine... Was able to reflash a rom modded with this tool (file from another rom added, other files removed).
For now it just allows transferring of files between roms and removal of files from a rom archive.
How it works:
1. Load the rom-archives (zip only) using the browse buttons. If one file is selected all contents are simply listed, in case 2 files are supported only the extra files per rom are listed.
You can filter on .apk/.odex files only by using the checkbox and pressing 'Scan'.
2. By using the 'Copy >>' and '<< Copy' buttons you can copy files between roms, these entries will be colored GREEN in the respective table views.
3. By using the 'Remove files' buttons you can remove files from the roms, these entries will be colored RED in the respective table views.
4. Save the rom by pressing the proper 'Save Changes' button and specifying the name of the .zip it has to be saved to.
A progressbar will show the progress and you'll get a message telling you when it's done. It's not the fastest but it does the job. The resulting zip can then be flashed through clockworkmod (at least the one I tested it with could ).
THere are prolly some bugs when you move files back and forth and delete files in between and adding them again, etc... I just tested it with moving a few files from one rom to another and deleting a few form the target rom. This worked fine, but please let me know about bugs and issues.
Update, version 2.1 added
Allrighty, I included the data from the spreadsheet found here:
http://forum.xda-developers.com/showthread.php?t=1069924
To display information about the selected apk's in the table. This gives you a quick overview about what an apk does and whether or not you can and want to remove it. It's displayed in a little text area below the table.
I also changed it so that by default one 'view' is shown, once a first archive is selected the option to select a second one is enabled by displaying the proper buttons. Only after a second file is specified the complete view is shown (two tables, etc).
That's it again for now
Use it at your onwn risk!
Thanks this is very helpful tool.
Would love to see this further developed...two thumbs up!
Sent from my GT-I9100 using Tapatalk
Subscrived to this topic in a hope to see development on it
Sent from my GT-I9100 using xda premium
Woooww, this tool is awesome, how about adding feature like u can copy one or more file from one archive to another one so we can not only remove but also add
I hope u will improve this app further in the future!
Sent from my GT-I9100 using Tapatalk
Thanks for the comments people, good idea about moving apk's to one and another as well indeed To be continued (and always open for suggestions!)
Also updated main post, but...
I rewrote it to allow removal of files and copying of files between two rom packages, I haven't been able to test it myself yet (finished it just now and really need to catch some sleep) but will try to do so tomorrow... However, if anyone else wants to give it a shot as well please let me know and I'll send it (tomorrow evening or monday prolly). I will not put it up before it has been tested and it is about 2:30am here so time to go to sleep. If I get a chance to test and upload tomorrow I'll do so...
Will try to check this topic tomorrow again but can't promise... Busy day.
Clever tool. Will definitely watch this develop
Gr8 work pal. Please continue your development. Is really a handy tool.
Updated 1st post with new version and some instuctions/clarifications
wow. missing that tool.
And another update, added ifnormation display about the apk's using the spreadsheet from this source:
http://forum.xda-developers.com/showthread.php?t=1069924
and changed the UI a bit to make it a bit simpler...
ps. Thinking about adding a feature where you can add seperate apk's/files... Would have to think about how to add that without rewriting too much.
I know that there are lots of forums but NONE of them answer this question, and i have spent the last week checking so i did my best. I have a SGS2 gt-i9100T with voda australia, if its relevant, and i have upgraded to XXLPQ ICS and it is rooted so i get CWM, and i have come across no lockscreen or power options. I had the same problem with the other versions of ICS but none with gingerbread. So initially i thought that i had to get into /efs/imei and change keystr to make it work. The problem is, no matter which root explorer i use when i get to the folder /efs i cannot open it. it just stays in the main / folder. I have tried to use a terminal to edit the file but it says that i dont have the permissions to do so and that it cant. i have backed up the folder using HC-K and it says that it was successful. Please someone who can help me as it is driving me nuts not being able to use ICS as it doesnt work. i also cant copy /efs as when i hold press on it and ask for info, it says that it has no files in it and no folders. and when i try to copy it, it says that nothing was copied as there was nothing TO copy.
So yeah, any help would be massively appreciated to all
so you're saying that backup was successful, why don't you make 2 backups, edit one of them to your need and restore it ? it should work.. and of course, don't forget to keep that 2nd original backup
I would except that the backup files/folders are not the ones that go in the /efs normaly. there is 2 files made from the backup, one called efs and it is a disc image file. and the other efs.tar. hang on, that tar file i may be able to edit. il get back to you on that thanks
huntsman0185 said:
I would except that the backup files/folders are not the ones that go in the /efs normaly. there is 2 files made from the backup, one called efs and it is a disc image file. and the other efs.tar. hang on, that tar file i may be able to edit. il get back to you on that thanks
Click to expand...
Click to collapse
you can edit that TAR with WinRAR for example
No luck, when i edited the file oddly it made it 0.7kb smaller, even though i added a file. and that .tar is a .tar.gz
Can you reboot in download mode?
huntsman0185 said:
No luck, when i edited the file oddly it made it 0.7kb smaller, even though i added a file. and that .tar is a .tar.gz
Click to expand...
Click to collapse
you have to pack it without compression..
078gregory said:
Can you reboot in download mode?
Click to expand...
Click to collapse
Yes i can although i dont see how it helps
amozonesk said:
you have to pack it without compression..
Click to expand...
Click to collapse
any help on how to do this?
huntsman0185 said:
Yes i can although i dont see how it helps
Click to expand...
Click to collapse
You can flash with odin official firmware from Intratech thread
078gregory said:
You can flash with odin official firmware from Intratech thread
Click to expand...
Click to collapse
i can although thats not what i want to do...
i have official firmware already from checkfus, its just this editing business thats has me confused.
the older firmware doesnt help when i need the /efs for ICS
also winrar says it can only add files to a rar or zip archive, so i cant edit the current .tar
try any other packing app, google is always here for you "how to edit .tar"
Yeah i used one of them, peazip and i thought i replicated the file perfectly and everything but its not working still, maybe i am lacking other files from /efs aside from the keystr one.
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
deathsquad737 said:
hello fellow xda junkies!
HERE IS A SIMPLE WAY TO GET DATA TETHERING THROUGH BUILD.PROP EDIT
NOTE:MESSING WITH BUILD.PROP COULD MESS YOUR PHONE UP BE CAREFUL
Step 1.) download a text editor.i suggest 920 text editor.
Step 2.) you will also need an root explorer so download that also.
Step 3).open up your root explorer and navigate to system/build.prop. and copy that file to another directory. i.e example sdcard/download.then rename
original build.prop file to build.prop.bak
Step 4).open up your text editor and navigate to the directory where you copied the build.prop file
Step 5.)look for this line [they are both close to the end of the build.prop file] "net.tethering.nonprovisioning=true" [once you find it change the true
to false] so it reads "net.tethering.nonprovisioning=false" NOTEDO NOT TYPE THE QUOTATION MARKS!!!
Step 6.) " look for line "persist.data.tethering_oc=1" change the variable 1 to 0 so it reads "persist.data.tethering_oc=0
Step 7.) move the build.prop file that you copied and edited from location you placed it in to its rightful spot in system/.change permissions to rw--r--r
reboot phone and your good to go!works on my vs985 LIKE A CHAMP.
Click to expand...
Click to collapse
You know there is already a flash for this and an apk.
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
deathsquad737 said:
Yes i do know this but some like to do it on there own.but hey nice to meet ya!
Click to expand...
Click to collapse
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
tech_head said:
Just checking.
I'm a tinkerer also which is how I figured out the thermal throttling.
Nice to met you.
Click to expand...
Click to collapse
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
deathsquad737 said:
Thermal daemon mitigation?is that what you are referring too?
A.L.B/E.B.B
Click to expand...
Click to collapse
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
tech_head said:
Actually not.
Instead of trying to stop the thermal mitigation from working I did just the opposite, I changed the parameters on how it operates.
The file /system/etc/thermal-engine-8974.conf.
This file controls what happens to cpu speed at various temperatures.
That is what you tweak and it just works.
I also used ROM Toolbox to change the governor.
Click to expand...
Click to collapse
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
deathsquad737 said:
Wow that's heavy I don't know if I have a high enough pay grade to do that lol
A.L.B/E.B.B
Click to expand...
Click to collapse
I can always get you a copy of the file.
tech_head said:
I can always get you a copy of the file.
Click to expand...
Click to collapse
Yes please I pm you
A.L.B/E.B.B
Thank you but...
First of all, thanks for the post. Although I appreciate the helpful post, my phone is now stuck in boot loop . I hate to be the one to open up an old thread but I'm freaking out at the moment due to brick fever :crying: My current setup was a rooted LG G3 VS98512b. My goal was simple, I didn't want to do anything crazy, I just wanted to enable wifi tether now I'm afraid I've lost everything... Is there a way I can get back into the storage of my phone and delete the modified build.prop, remove the ".bak" from the original and be back to the good life? Any assistance is greatly appreciated, this seemed like such a simple modification that led to such a big headache.
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
trent999 said:
It sounds like you might have used an editor on your build.prop that could not handle the file size, resulting in your editted build.prop being truncated. Otherwise, maybe your permissions were left wrong. Either of these will cause your phone to bootloop.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
soundmasterx said:
Thanks for the reply. I used the editor recommended in the tutorial, 920 text editor. I followed the instructions word for word, I don't know what the problem is. Maybe its because I have the newest update and this mod was for 10b???As far as the permissions, the phone asked automatically if I wanted to change the permissions. The original build.prop is still there... is there a way I can delete the modified build.prop and replace it with the original? I really wish I would not have followed this tut, it didn't seem like a popular method. There has to be a way to delete the modified build.prop right?
Click to expand...
Click to collapse
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Digital_MD said:
Yes you can reflash the firmware or if you don;t want to restore to stock you can use ADB to fix the files and restore your .bak
Click to expand...
Click to collapse
Again, thank you for the response. Do you recommend a specific method or tutorial for trying restore the original build.prop? I did search however, because this scenario is so specific I'm not sure there is an exact solution to my problem.
Again, just in case someone else can chime in, I followed the instructions on the first post of this thread (see first post for detailed info). I copied the original build.prop then changed the name of the original build.prop, edited the copy, moved it to the original directory and restarted the phone. Now my phone doesn't make it to the Verizon screen (I think it is stuck in boot loop), the screen stays black and the small led on the left corner flashes blue and green. If I can just get access to the storage I can replace the modified build.prop with the original that is still in the same directory just renamed. It seems like such an easy task but, I just don't know how to go about it I'm a somewhat of an old school tinker, I'm just now getting back into the swing of Android... Thanks in advance!!
Bump
Bump please
This is crazy... I changed 2 values in build.prop for tethering and my phone wont boot now... I didnt install a ROM, change DPI, or make any major changes WTF???
Do you have a custom recovery (twrp)?
Can you connect to your phone with adb?
If you have twrp, search the board for the startup hardware key sequence to reach twrp, else from adb do a reboot recovery.
In twrp, you can select to mount system, then go to advanced - file manager. You can delete the bad build.prop, rename the good one, then set the permissions on the good one. If your good copy of build.prop is on a PC, put it on a flash drive, and use twrp's file manager to get it into your phone.
If you have a saved copy of build.prop on your PC, you can also use adb's push command. (You may also want to look at the adb shell command. The sequence might be to open a shell, delete the bad build. prop, get the right build.prop into the right directory, then chmod the right build.prop so it has the proper permissions.)