Is there a way to get tethering to work without using something like FoxFi?
I tried the method posted here: http://forum.xda-developers.com/lg-g3/general/enable-tethering-lg-g3-d850-t2814367 but I have a different settings.db file with no tether_entitlement_check_state.
The same was true when I tried on version D85010d.
jiexi said:
Is there a way to get tethering to work without using something like FoxFi?
I tried the method posted here: http://forum.xda-developers.com/lg-g3/general/enable-tethering-lg-g3-d850-t2814367 but I have a different settings.db file with no tether_entitlement_check_state.
The same was true when I tried on version D85010d.
Click to expand...
Click to collapse
root and mod the flags
In your SQLite Editor, click on the FILES tab and look for the path: /data/data/com.android.providers.settings/databases/SETTINGS.DB/SYSTEM
DO SEARCH OF SYSTEM FOR ‘TETHER’
I HAVE ‘TETHERING TIME 600000, CHANGE TO 0
I HAVE TETHER ENTITLEMENT 5, CHANGE TO 0
this came from xda. i keep it handy in a note
did you make sure to first run the tether setup first, before doing the mod? that puts the entries into the correct file.
Yes I did run the tether first for it to initialize the file, as per the instructions.
I was able to find the two values and changed them both. However after I restarted my phone it went into a boot loop.
I flashed a recovery and then tried just changing tether_entitlement to 0, but the same thing happens.
Is there anything else I should try?
Also, there were some things I noticed and I'm not sure if they make a difference.
1)
instead of having the directory path
data>data>com.android.provider.settings>system>databases>settings.db
I have just
data>data>com.android.provider.settings>databases>settings.db
2)
SQLite Editor does not have root access. It never prompts me to give root access, nor do I see a way to manually grant it through SuperSU.
However, other apps like Root Browser were prompted and do have root access.
I did a work around by copying settings.db to sdcard to change the values, then copying it back.
Any more help will be greatly appreciated.
jiexi said:
Also, there were some things I noticed and I'm not sure if they make a difference.
1)
instead of having the directory path
data>data>com.android.provider.settings>system>databases>settings.db
I have just
data>data>com.android.provider.settings>databases>settings.db
2)
SQLite Editor does not have root access. It never prompts me to give root access, nor do I see a way to manually grant it through SuperSU.
However, other apps like Root Browser were prompted and do have root access.
I did a work around by copying settings.db to sdcard to change the values, then copying it back.
Any more help will be greatly appreciated.
Click to expand...
Click to collapse
after you make the changes to the file, make sure you set the permissions or you will boot loop
JeffDC said:
after you make the changes to the file, make sure you set the permissions or you will boot loop
Click to expand...
Click to collapse
I ended up using another database editor, but that was most likely the problem.
Thanks.
jiexi said:
I ended up using another database editor, but that was most likely the problem.
Thanks.
Click to expand...
Click to collapse
Yes., exactly. You must use and editor which can handle the entire file, and not truncate the file when you save it. I use 920 text editor
Related
I have an AT&T Tab and thus need to periodically enable USB debugging to use the Side Load Wondermachine app. Stinks navigating thru the menus to enable / disable. I've searched the market but can't seem to find a widget that would handle toggling this as needed. Anyone know of one out there?
Not sure why you wouldn't just leave debugging enabled (you can always mount usb via the notification bar), but you can create a shortcut to the Development settings page using LauncherPro (the activity is under Settings->Development).
Thank you! I actually did not know you can have it selected all the time. I just tried it and it worked! I was use to have it unselected such that it would prompt me for either mass storage, Kies, or media. Since I only use it for Mass storage it works fine. Thanks again!
Why not just allow from market? Sure the options not there, but if you edit the settings.db from /dbdata/databases/provider-settings you can enable install_from_non_market.
It's what I did.
JaysFreaky said:
Why not just allow from market? Sure the options not there, but if you edit the settings.db from /dbdata/databases/provider-settings you can enable install_from_non_market.
It's what I did.
Click to expand...
Click to collapse
Hmm? Where exactly do you find this file? I searched via Astro File Explorer on the whole Tab and did not find this file. Would love to enable this option. Please provide additional details? Is yours also an AT&T tab? Can you provide a copy of the file?
cbb77 said:
Hmm? Where exactly do you find this file? I searched via Astro File Explorer on the whole Tab and did not find this file. Would love to enable this option. Please provide additional details? Is yours also an AT&T tab? Can you provide a copy of the file?
Click to expand...
Click to collapse
Sorry, that wasn't the exact name - I was just guesstimating. I have the AT&T Tab.
The actual path is /dbdata/databases/com.android.providers.settings/setti
ngs.db
I'm attaching the modified file. Just replace the file that's already specified in the path above with the one I'm attaching in the zip.
JaysFreaky said:
Sorry, that wasn't the exact name - I was just guesstimating. I have the AT&T Tab.
The actual path is /dbdata/databases/com.android.providers.settings/setti
ngs.db
I'm attaching the modified file. Just replace the file that's already specified in the path above with the one I'm attaching in the zip.
Click to expand...
Click to collapse
Ok, bear with me as I am a noob, but I am still not seeing it. See my attached screenshot. I am not seeing anything in the dbdata folder. I searched for com.android.provider.settings and the only item that comes back happens to be in my Titanium backup directory. Not sure why there and not in a folder itself. Searching for settings.db results with nothing.
Ok, never mind I figured it out. Looks like I needed a Root Explorer app. I thought Astro or ES File Explorer would show me everything but I was wrong. Downloaded a root explorer app and now I can see the file. Will backup and replace mine and see how it goes.
Thanks
Update: Excellent this works! I actually didn't use your file as I was concerned there may be other setting that were different. I was comparing the changes and noticed that my settings file already had the change you mentioned. I remember doing this via SuperOneClick root tool; however never bothered to try it. Duh! Well it works. This now in combination with dropbox is excellent. I can simply copy the file to my dropbox folder, select and install it on the tab. Works Awesome! Thanks for mentioning this to me; probably would have never thought to try it on my own. Thanks again.
cbb77 said:
Ok, never mind I figured it out. Looks like I needed a Root Explorer app. I thought Astro or ES File Explorer would show me everything but I was wrong. Downloaded a root explorer app and now I can see the file. Will backup and replace mine and see how it goes.
Thanks
Update: Excellent this works! I actually didn't use your file as I was concerned there may be other setting that were different. I was comparing the changes and noticed that my settings file already had the change you mentioned. I remember doing this via SuperOneClick root tool; however never bothered to try it. Duh! Well it works. This now in combination with dropbox is excellent. I can simply copy the file to my dropbox folder, select and install it on the tab. Works Awesome! Thanks for mentioning this to me; probably would have never thought to try it on my own. Thanks again.
Click to expand...
Click to collapse
No problem!
Hi there,
Is there a way to temporary root my Nexus S [I9020XXKD1] or alternatively a non-root way to access /data so that I can copy a file in and out? Essentially I want to be able to backup and restore some game saves
Most posts I've read basically have folks saying "Just root it", which is good advice to most but isn't right for me - I really don't want to have to wipe my phone and I'd also like to be able to dip my toe into rooting before taking a full leap. That, and aside from needing this one file in /data my phone works exactly as I'd like it to
I only need "su" access for a brief moment to copy off a file to and from /data. I set up the android sdk but ADB didn't work because of the protection of "production builds".
VISIONary seemed like the right kind of thing, but I don't believe it works for the Nexus S or recent firmware, so while temp rooting would be nice so would any solution that allows me to backup and restore some files in /data.
At the moment I am wondering if writing an apk of my own that copies/replaces this one file is the way to go - but that seems perversely long way around!
So any help/suggestions most appreciated
There is no temporary root for the Nexus S. You're either rooted, or you're not. However, if, perchance, you are on Android 2.3.2 or earlier, you might be able to root without wiping.
Without root, you cannot see the files in /data, but you can read/write the files directly if they have the proper permissions and you know the exact path/filenames. After poking around a bit, it seems that read & write permissions vary among apps. Most apps have full permissions reserved for the parent app. Some allow other apps/user to read some files, and read+write others. (The permissions being app-specific, if it can't be done by command line, I doubt it could be done by creating an app, either.)
So, what is the game? Perhaps I can do some exploring.
If you have the old bootloader (2.3.2 i think) you can boot a recovery without flashing. From you computer use "adb boot recovery.img" and boot clockwork recovery. From there you can mount and access the filysystems.
Sent from my Nexus S using XDA App
Maximilian Mary said:
There is no temporary root for the Nexus S. You're either rooted, or you're not. However, if, perchance, you are on Android 2.3.2 or earlier, you might be able to root without wiping.
Without root, you cannot see the files in /data, but you can read/write the files directly if they have the proper permissions and you know the exact path/filenames. After poking around a bit, it seems that read & write permissions vary among apps. Most apps have full permissions reserved for the parent app. Some allow other apps/user to read some files, and read+write others. (The permissions being app-specific, if it can't be done by command line, I doubt it could be done by creating an app, either.)
So, what is the game? Perhaps I can do some exploring.
Click to expand...
Click to collapse
Thanks I figured as much. The game is Dungeon Hunter 2 and essentially I am trying to implement a simple fix to make my save game work again (the fix is here: http://forum.xda-developers.com/showthread.php?t=1042675 a few posts down) but it requires root. So I do know the exact paths and filename.
Thank you for your helpful answer
Ok, I'm not having any luck here, and it's pissing me off. FYI, I don't have that game, so I'm testing it with Angry Birds. I can read and copy the file just fine, but I can't modify it without using root. The data file itself has read/write access, but the containing folder (files/) is read-only, so I can't overwrite the file after I've modified it. Since the file itself has r/w access, I wonder if it would work to modify the file directly, instead of using an outside program to modify it then overwriting it. (I'm a bit ignorant of the finer points of linux permissions.) This would require an app that would allow you to open and modify a file by typing the full path & filename, instead of just browsing the directory tree. You could also try < adb pull /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame dh2_000.savegame > (using the correct path, if that's not it). Then see if < adb push dh2_000.savegame /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame > works. The fact that you can copy the file out is promising, anyway. So even if you had to root, you could backup the file before rooting wipes everything, then fix it & back it up after you had root.
Btw, what version of Android are you on?
Edit: I think I'm getting somewhere. While you can't modify the file itself, you can modify the file contents. So something like this might work: < adb shell >
< more /sdcard/dh2_000.savegame > /data/data/com.gameloft.android.TBFV.GloftD2HP.ML/files/dh2_000.savegame >
So the next step is to get some help from someone who has the game and is rooted as to the exact path to the savegame file. Once we have that, I think we're golden. (Or, let me know if adb pull works with the path I guessed at.)
wow! Thank you for your help
In answer to your questions: my Nexus s is running 2.3.4 and you are correct about the file path (many other kind xda users died to bring us those paths ) is /data/data/com.gameloft.android.TB with the filename being dh2_000.savegame
I don't want to drive you to distraction! If I could back it up I probably would go ahead then and root the phone given how complexplaying with a non-rooted phone is!
I will try the adb pull method and let you know how I get on.
Thank you again for your help and for showing me why I probably do want to root!
Wifi Tethering Mod
Here are the original instructions use the zip at your own risk. It seems some people are experiencing problems with it...
I have modified the instructions to pertain to the Flex exactly.
This mod is not for the newbie, you must be rooted and I implore you to make a safe back up file in a new location of the file you will be editing. Actually two back ups, one completely stock the other you will use for editing.
I have edited his instructions for usage on the Pantech Flex running ICS.
Here’s the usual disclaimer: if you brick your phone it’s not my problem…. though I will help in any way I can as in my research I soft bricked my own device and was able to get it restored to a factory state.
Steps:
1. Root device using this method http://forum.xda-developers.com/show….php?t=2008888
2. Acquire/Install SQlite Editor or any Android SQL editor of your choice, Install ES File Explorer or Root File Explorer
3. Navigate to (root level) /Data/data/com.android.providers.settings/databases/
4. Copy file settings.db Navigate to SDcard/Backups/ now paste file to this location
5. Rename the file in Backups/ settings.db to settings.db.bak (if all goes to hell this is your backup file)
6. Paste the file again so you will have two settings files in Backups one ending in .bak and one ending in .db (this is the file you will be editing).
7. Open SQLite Editor and point it to /sdcard/Backups/settings.db and open it. You now will see a list of settings locations. Click on “secure”
8. Here you are going to be looking for two distinct lines. The line numbers may vary by device so I suggest you list name in list view:
Line 1. softap_free_supported
Line 2. softap_entitlement_interval
9. Change Line 1′s value to 1 in the SQL editor. Change Line 2′s value to 0 in the SQL editor save and close or just close depending on the editor.
10. Using your file explorer navigate back to /data/data/com.android.providers.settings/databases/ rename settings.db to settings.db.bak
11. Navigate to /sdcard/backups/settings.db(the one you edited) and copy the file go back to com.android.providers-etc and paste the file.
12. SUPPER IMPORTANT if the file permisuions on settings.db are not rw-rw-rw make them so in your file explorer.
If these permissions are no correct your phone will get stuck on the AT&T boot screen. ie softbricked
13. Reboot and you should be able to go to More in settings then Tethering & portable hotspot and turn it on set up your settings etc.
14. FYI under battery management you may want to change the value to never time out as it applies to the phones activity not the wifi activity.
This had been tried and tested on AT&T only it may work on other carries. USE AT YOUR OWN RISK!
Zip Method
You must be rooted and have CWM intalled.
1 Download the recovery mod zip file to the internal storage of your phone.
2 Reboot into recovery and make a CWM backup of your phone.
3 From recovery clear the cache and dalvik cache
4 Install the zip from the location you saved it to.
5 Reboot your phone.
6 Go to your phone settings wireless and networks, click on more, click on tethring and portable hotspot, click the box next to portable-wifi-hotspot. You are now up and running.
7 Personalize your hotspot settings in portabpe wi-fi hotspot settings.
8 Grab a free app like Hotspot Toggle to add to your home screen for easy one click on and off.
A huge Thank You goes out to Timmythanoob for making my original mod zip installable!
https://www.dropbox.com/s/9zv14h36j6xdjhq/tether.zip?m
This had been tried and tested on AT&T only, it may work on other carriers. USE AT YOUR OWN RISK!
Sent from Freakshow999's Nexus 7 using Tapatalk 2
If you find this post useful please remember to hit the thanks button!
Works perfectly
Sent from my PantechP8010 using xda app-developers app
@freakshow what part of the LBC u from were practicly neighbors bro lol
atadres said:
@freakshow what part of the LBC u from were practicly neighbors bro lol
Click to expand...
Click to collapse
I'm actually living in Cerritos right now but I'm at Portfolio at 4th and Juniper pretty much every day.
Sent from my PantechP8010 using Tapatalk 2
Mod update now zip installable through CWM recovery thanks to Timmythanoob!
the zip doesnt work for me !!
messes up my phone !
pls tell me the previous method ?
thanks...
I'm out right now. I will post up how to do it the manual way tonight some time.
Sent from my PantechP8010 using Tapatalk 2
Sorry I haven't been able to get the manual method up. I've been extremely busy with work. I will make an attempt to get it up later today.
Sent from my PantechP8010 using Tapatalk 2
after install this MOD my HOME key not work!!!
levanr said:
after install this MOD my HOME key not work!!!
Click to expand...
Click to collapse
Did you get it fixed?
if not restore system from backup
If you didnt do a backup do a factory data reset
Manual method is back and tried & true working...
Sorry it took so long. A quick Google search found a repost of my original thread on a blog... Lol!
Sent from my Nexus 7 using Tapatalk HD
Chadw1985 said:
Did you get it fixed?
if not restore system from backup
If you didnt do a backup do a factory data reset
Click to expand...
Click to collapse
i did factory data reset.
but i lost
tethering again )
levanr said:
i did factory data reset.
but i lost
tethering again )
Click to expand...
Click to collapse
Its because the file you edited is in your data folder. You will need to change a few things in your system folder to completely enable it.
levanr said:
i did factory data reset.
but i lost
tethering again )
Click to expand...
Click to collapse
Use the manual method for now we have a new zip file that should be up within the next 24 hours.
The manual method only changes the exact strings of info pertaining to tethering so it doesn't disturb the system files etc.
Sent from my Nexus 7 using Tapatalk HD
I think manual mode only work on att
becose in my carier not work (
but if delete line 1 work or using Secret Codes Revealer this work
https://play.google.com/store/apps/details?id=com.afp_group.software&hl=en
sorry for my english
File not found
freakshow999 said:
Wifi Tethering Mod
Here are the original instructions use the zip at your own risk. It seems some people are experiencing problems with it...
I have modified the instructions to pertain to the Flex exactly.
This mod is not for the newbie, you must be rooted and I implore you to make a safe back up file in a new location of the file you will be editing. Actually two back ups, one completely stock the other you will use for editing.
I have edited his instructions for usage on the Pantech Flex running ICS.
Here’s the usual disclaimer: if you brick your phone it’s not my problem…. though I will help in any way I can as in my research I soft bricked my own device and was able to get it restored to a factory state.
Steps:
1. Root device using this method http://forum.xda-developers.com/show….php?t=2008888
2. Acquire/Install SQlite Editor or any Android SQL editor of your choice, Install ES File Explorer or Root File Explorer
3. Navigate to (root level) /Data/data/com.android.providers.settings/databases/
4. Copy file settings.db Navigate to SDcard/Backups/ now paste file to this location
5. Rename the file in Backups/ settings.db to settings.db.bak (if all goes to hell this is your backup file)
6. Paste the file again so you will have two settings files in Backups one ending in .bak and one ending in .db (this is the file you will be editing).
7. Open SQLite Editor and point it to /sdcard/Backups/settings.db and open it. You now will see a list of settings locations. Click on “secure”
8. Here you are going to be looking for two distinct lines. The line numbers may vary by device so I suggest you list name in list view:
Line 1. softap_free_supported
Line 2. softap_entitlement_interval
9. Change Line 1′s value to 1 in the SQL editor. Change Line 2′s value to 0 in the SQL editor save and close or just close depending on the editor.
10. Using your file explorer navigate back to /data/data/com.android.providers.settings/databases/ rename settings.db to settings.db.bak
11. Navigate to /sdcard/backups/settings.db(the one you edited) and copy the file go back to com.android.providers-etc and paste the file.
12. SUPPER IMPORTANT if the file permisuions on settings.db are not rw-rw-rw make them so in your file explorer.
If these permissions are no correct your phone will get stuck on the AT&T boot screen. ie softbricked
13. Reboot and you should be able to go to More in settings then Tethering & portable hotspot and turn it on set up your settings etc.
14. FYI under battery management you may want to change the value to never time out as it applies to the phones activity not the wifi activity.
This had been tried and tested on AT&T only it may work on other carries. USE AT YOUR OWN RISK!
Zip Method
You must be rooted and have CWM intalled.
1 Download the recovery mod zip file to the internal storage of your phone.
2 Reboot into recovery and make a CWM backup of your phone.
3 From recovery clear the cache and dalvik cache
4 Install the zip from the location you saved it to.
5 Reboot your phone.
6 Go to your phone settings wireless and networks, click on more, click on tethring and portable hotspot, click the box next to portable-wifi-hotspot. You are now up and running.
7 Personalize your hotspot settings in portabpe wi-fi hotspot settings.
8 Grab a free app like Hotspot Toggle to add to your home screen for easy one click on and off.
A huge Thank You goes out to Timmythanoob for making my original mod zip installable!
https://www.dropbox.com/s/9zv14h36j6xdjhq/tether.zip?m
This had been tried and tested on AT&T only, it may work on other carriers. USE AT YOUR OWN RISK!
Sent from Freakshow999's Nexus 7 using Tapatalk 2
If you find this post useful please remember to hit the thanks button!
Click to expand...
Click to collapse
The link to flashable zip file is not working. Would you please upload again or provide a valid link?
Sorry guys all the zip installable files people have done for me have not worked for various reasons.
The manual method works tried and true on AT&T. I don't know about other carriers but I'm sure you would want to look at the same settings in the same file for changes.
By the way bluetooth tethering also works with this mod, but wifi tether yields much higher internet speeds.
This fix Requires ROOT and Busybox installed to /system/xbin
Context: I have been looking for a way to make an app that hides files to read/write files on my external SDcard, The way I found was to edit the platform.xml file to add that missing line as guided here: LINK this is just one of the many articles saying the same thing. which helped some apps work, but not the one i was looking for.
Reason: the point of this script is to make it so you do not have to set permission to the "media_rw" folder after every reboot manually.
Steps:
1) Follow and complete guide linked above, or any other similar guide, if you have not done so already.
*NOTE* some custom ROMs have already implemented this fix
2) After reboot use an app that allows you to make scripts (Ex. Rom Toolbox) this guide will use Rom Toolbox app
- create new script, name it whatever you want. I named it "sdcard permission"
- input this line and save:
Code:
chmod 777 /mnt/media_rw
*NOTE* you do not need to put it as 777 but it is what worked for me as it gave full read/write/execute permissions
3) Set script to run at boot
4) Run script manually then check app to see if it worked
-Alternatively go check /mnt/media_rw to see if it has the new permissions
Now you should be able to access the external SD card after every boot.
NOTE: you may need to redo the guide in the first step after switching ROMs as the new ROM may not have the fix implemented.
Reserved just in case
Buddyjohn said:
This fix Requires ROOT and Busybox installed to /system/xbin
Context: I have been looking for a way to make an app that hides files to read/write files on my external SDcard, The way I found was to edit the platform.xml file to add that missing line as guided here: LINK this is just one of the many articles saying the same thing. which helped some apps work, but not the one i was looking for.
Reason: the point of this script is to make it so you do not have to set permission to the "media_rw" folder after every reboot manually.
Steps:
1) Follow and complete guide linked above, or any other similar guide, if you have not done so already.
*NOTE* some custom ROMs have already implemented this fix
2) After reboot use an app that allows you to make scripts (Ex. Rom Toolbox) this guide will use Rom Toolbox app
- create new script, name it whatever you want. I named it "sdcard permission"
- input this line and save:
Code:
chmod 777 /mnt/media_rw
*NOTE* you do not need to put it as 777 but it is what worked for me as it gave full read/write/execute permissions
3) Set script to run at boot
4) Run script manually then check app to see if it worked
-Alternatively go check /mnt/media_rw to see if it has the new permissions
Now you should be able to access the external SD card after every boot.
NOTE: you may need to redo the guide in the first step after switching ROMs as the new ROM may not have the fix implemented.
Click to expand...
Click to collapse
I have a Samsung Galaxy S3 and been trying all kind of things to get to media_rw folder to keep its read writable and nothing worked so far. I did everything in you post to see if it would help/work but script not working. I can only keep permissions if I set manually set permission using root browser and then it working until I reboot the phone and I tried adding the script using ROM Toolbox pro but its not even changing the media_rw permission when run it.
This my first time using the script tool but to me seems to be setup properly. If needed I will get some screenshots of the script windows to show how I set it up. I am just posting this now to see if anyone can help or wants to ask some questions.
I know how permissions work in Windows and getting up to speed with Android. I been trying to make the media_rw folder r/w to be able to able to path it to my Titanium Backup folder on my external SD.
This looks similar to setting boot bat files in Windows so I know it should work but no go so far.
Heres the screenshots of my script that failed to run and the output file hoping to get some advice why script did not work.
Is this thread dead? Should I seek answers elsewhere?
techmanc said:
Is this thread dead? Should I seek answers elsewhere?
Click to expand...
Click to collapse
yes this thread is dead, lots of apps are updating compatibility finally, also there are some xposed modules that essentially does what i did on here. so this is dead.
Buddyjohn said:
yes this thread is dead, lots of apps are updating compatibility finally, also there are some xposed modules that essentially does what i did on here. so this is dead.
Click to expand...
Click to collapse
can yuo point me to some threads that are still working cause I still not been able to get RW access to media_rw folder.
techmanc said:
can yuo point me to some threads that are still working cause I still not been able to get RW access to media_rw folder.
Click to expand...
Click to collapse
try these three xposed modules, i recommend enabling one at a time to see which works, reboot after enabling one.
http://forum.xda-developers.com/xposed/modules/app-handleexternalstorage-t2693521
http://forum.xda-developers.com/xposed/modules/kitkat-sd-card-access-t2790992
http://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2789267
also i just realized why it was failing on yours. make sure you have busybox installed to system/xbin
that will make the script work. or atleast should.
Buddyjohn said:
also i just realized why it was failing on yours. make sure you have busybox installed to system/xbin
that will make the script work. or atleast should.
Click to expand...
Click to collapse
Looked s Busybox says installed to /system/bin heres the screenshot do I click install to move or use smart install. Never did much with app just know it was needed for rooting.
techmanc said:
Looked s Busybox says installed to /system/bin heres the screenshot do I click install to move or use smart install. Never did much with app just know it was needed for rooting.
Click to expand...
Click to collapse
Install it to /xbin
Buddyjohn said:
Install it to /xbin
Click to expand...
Click to collapse
What the difference between installing to /xbin vs /system/bin might I ask?
techmanc said:
What the difference between installing to /xbin vs /system/bin might I ask?
Click to expand...
Click to collapse
Honestly I am not to sure, I just assumed xbin was the right one as a lot of older mods and roms required busybox on xbin. so i tried it and it worked.
http://forum.xda-developers.com/showpost.php?p=61260005&postcount=80
Above is the ram fix for the s6, I am pretty new to this kind of stuff and I read some verizon users were getting bootloops from editing the build.prop . If it is possible can anyone make a guide through it or post their build.prop if successful?
NumberTwoinQQ said:
http://forum.xda-developers.com/showpost.php?p=61260005&postcount=80
Above is the ram fix for the s6, I am pretty new to this kind of stuff and I read some verizon users were getting bootloops from editing the build.prop . If it is possible can anyone make a guide through it or post their build.prop if successful?
Click to expand...
Click to collapse
I gave it a whirl. No bootloop here. I'm on OC3 firmware running Ricks rom.
Tulsadiver said:
I gave it a whirl. No bootloop here. I'm on OC3 firmware running Ricks rom.
Click to expand...
Click to collapse
so did you have to do anything after editing the build.prop? Like "after editing make sure permissions are 0644 on it or you will boot loop."
I do not know where to find permissions
EDIT: I just changed these and it worked:
ro.config.dha_cached_max=12
ro.config.dha_empty_max=36
ro.config.dha_th_rate=2.3
ro.config.dha_lmk_scale=0.545
ro.config.sdha_apps_bg_max=70
ro.config.sdha_apps_bg_min=8
ro.config.oomminfree_high=7628,9768,11909,14515,16655,20469
NumberTwoinQQ said:
so did you have to do anything after editing the build.prop? Like "after editing make sure permissions are 0644 on it or you will boot loop."
I do not know where to find permissions
Click to expand...
Click to collapse
Most root explorers will show and allow permissions to be changed.
I actually edited mine via an app but I've done it through my root explorer text editor as well. Probably need to copy it off root drive. Edit it, then copy back. Some people say to copy it to the root folder first. Set permissions, them copy/move it to the system folder to overwrite it. Then, reboot.
I left this line out. Should I have?
ro.config.oomminfree_high=7628,9768,11909,14515,16 655,20469
It was on on CleanROM to begin with.
musicfreak190 said:
I left this line out. Should I have?
ro.config.oomminfree_high=7628,9768,11909,14515,16 655,20469
It was on on CleanROM to begin with.
Click to expand...
Click to collapse
According to the post, that line should have been inserted.
so i had quite an issue - my first go at it was done by copying build.prop via adb to my computer, editing and pushing back - after that, i nearly bricked the device. had to roll back to stock rom using odin .. not fun. now i decided to try again (cause i'm a masochist apparently) but i just edited the file using ES - no problems, no boot loops.. all is well for now - hopefully will see fewer apps closing for no reason. hooray.
i can say downloading the build prop that was posted here and replacing mine with it will brick a phone