Related
Hi i was wondering if what is the proper way to use an init.d file. I want to set my liveoc value to 105 on boot using an init.d file. I edited the line below in an init.d file using a file manager with root rights.
echo 105 > /sys/class/misc/liveoc/oc_value
but somehow it does not work. do i need special permissions for this??
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
frutelaken said:
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
Click to expand...
Click to collapse
yupp its great!! i'm using it in the mean time. but i really want to know the proper way to go about using init.d files. if someone could help that would be greatly appreciated!!
Hey guys, So how I would use script manager? I want to the same of running the script at boot so liveoc starts at reboot! Thanks!
Sent from my Google Nexus S using Tapatalk
frutelaken said:
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
Click to expand...
Click to collapse
yes its great try it "Script Manager" hope you like it sory for my bad eng
idelgado782 said:
Hey guys, So how I would use script manager? I want to the same of running the script at boot so liveoc starts at reboot! Thanks!
Sent from my Google Nexus S using Tapatalk
Click to expand...
Click to collapse
I just learned all this.. so here's my take.
You simply put your script to the /init.d subfolder in /system/etc
There's one more essential step, you'll see all the scripts named with "01, 02" etc. I named mine as "58liveoc" as another post in Dec section recommended. Keeps it out of the way of system scripts and tweak scripts for kernel.
make sure you have " #!/system/bin/sh" at the top and have voltages and Max frequently set before echo for live_oc
see live oc thread for some demo scripts, backup your device!!!!
---------- Post added at 02:43 PM ---------- Previous post was at 02:36 PM ----------
Almost forgot match permissions of file to that of existing ones... should be rwxr-x--- also change owner to 0 root and group 2000 shell.... did it all using root explorer
ecksion said:
I just learned all this.. so here's my take.
You simply put your script to the /init.d subfolder in /system/etc
There's one more essential step, you'll see all the scripts named with "01, 02" etc. I named mine as "58liveoc" as another post in Dec section recommended. Keeps it out of the way of system scripts and tweak scripts for kernel.
make sure you have " #!/system/bin/sh" at the top and have voltages and Max frequently set before echo for live_oc
see live oc thread for some demo scripts, backup your device!!!!
---------- Post added at 02:43 PM ---------- Previous post was at 02:36 PM ----------
Almost forgot match permissions of file to that of existing ones... should be rwxr-x--- also change owner to 0 root and group 2000 shell.... did it all using root explorer
Click to expand...
Click to collapse
oh wow!! hmmm ok i'll give it a shot. thanks for the help. cheers.
edit: i tried what you told me and did it exactly but its still not setting my live oc on boot. is there something else i am missing??
tinselttown said:
oh wow!! hmmm ok i'll give it a shot. thanks for the help. cheers.
edit: i tried what you told me and did it exactly but its still not setting my live oc on boot. is there something else i am missing??
Click to expand...
Click to collapse
OK.. Im sure we can figure it out here
So step 1 you're using a kernel that supports live oc
Step 2 script has been copied from SD to init.d and then permissions and group set(not sure if those stick when copy/pasting)
Step three I guess is renaming it
And step 4 is the script itself...
Are you using one of the preset scripts?
If not.. what values? Voltage/Max/min/oc/gov's
When I screwed mine up my phone would crash left and right
..
Hmm... oh make sure "run on boot" is unchecked in SM for said script... reboot and CPU frequency. Should all be set as desired....
Lemme know? I'm not an expert but if you've got the time Im happy to help
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
xtracrispy said:
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
Click to expand...
Click to collapse
I think its best to use multiples of 5. That being said I think its capped at 125. Also it requires higher voltages the higher you set it. If you want a 200 MHz bus you can use trinity kernel its compiled at 200 and keeps lowest possible voltages while giving overclock aswell
wait hang on...
I always thought it was a double pumped bus, so 100 base close = 200 bus, the trinity kernel's not actually 2x faster bus than anything else, is it?
xtracrispy said:
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
Click to expand...
Click to collapse
yupp it works for odd numbers but like ecksion said its better to use multiples of 5.
ecksion said:
OK.. Im sure we can figure it out here
So step 1 you're using a kernel that supports live oc
Step 2 script has been copied from SD to init.d and then permissions and group set(not sure if those stick when copy/pasting)
Step three I guess is renaming it
And step 4 is the script itself...
Are you using one of the preset scripts?
If not.. what values? Voltage/Max/min/oc/gov's
When I screwed mine up my phone would crash left and right
..
Hmm... oh make sure "run on boot" is unchecked in SM for said script... reboot and CPU frequency. Should all be set as desired....
Lemme know? I'm not an expert but if you've got the time Im happy to help
Click to expand...
Click to collapse
ok i have done step 1-3 correctly. about the script i am using the one that is written for my phone, i just changed the liveoc value. is it a must to include all the steps?? can i just set the oc values and not set the stuff i don't want to change?? because currently i have only that line included in the script. i also have a test script inside init.d which does not execute as well which makes me believe that the scripts in init.d aren't being run on boot.
So I've used the sqlite vacuum/re-index feature of V6 SuperCharger blindly without knowing what it does getting a placebo effect sort of thing, and I started doing some research on it and realized that this feature has started getting stripped out of a lot of stock roms and what not on android devices and that basically it makes it wayyyy easier for the system to index and sort out system/app files a lot of it was over the top for me but I figured there could be no negative effects to this at all.
So long story short I downloaded SQLite Installer from the market
Restarted and everything on my phone has been quick and painless it's been up for 6 hours now since the restart and have yet to have any lag/problems.
here's my set up:
Tweaked 2.0
0504 PBJ Kernel
OC'd to 1.2ghz (SIO i/o and Interactive governor)
don't know if it is placebo affect once again and I'd love to get some more veteran knowledge on this but I LOVE MY PHONE NOW
As I am a new member here I cannot post links but go to my thread at rootzwiki[dot]com/topic/25072-sqlite3-phone-is-snappier-than-ever/ and read the instructions there and download the easily flashable .zip file with the included detailing script.
happy flashing
p2kmafia
I just flashed so ill report if results are the same for me
Sent from my SCH-I510 using XDA
good lookin. there were positive results in my rootzwiki thread.
RFS or EXT4?
and is this the app: https://play.google.com/store/apps/details?id=ptSoft.util.sqlite3forroot
It would be fairly easy to run before and after database benchmarks in an app such as AnTuTu Benchmark. That would show if there are any real gains to be had.
Looking at the script, it essentially just re-writes all of the databases on the phone (via a VACUUM/REINDEX combo). Logic would state that if you have badly fragmented databases, which would manifest as things like degredation of performance over time, then this should make your phone a bit snappier.
[edit: I ran before and after tests (average of 3 tests). There was no appreciable difference between the tests. Now, the test results may not reflect real world results for two reasons: 1. I have no idea how the database I/O test in AnTuTu actually tests (what database, etc) and 2. I received errors when the script was attempting to vacuum databases ("error: unable to open file"), though the re-indexing worked fine.
End result? The test essentially means nothing and all we can go off of is anecdotal evidence. However, whether it's a placebo effect or not, this process simply can't harmfully impact your phone. As such, results should be anything from no change in response to some response increase.
Yeah, I know. A whole lot of typing that essentially says nothing. Sorry!]
jco23 said:
RFS or EXT4?
and is this the app: play.google[DOT]com/store/apps/details?id=ptSoft.util.sqlite3forroot
Click to expand...
Click to collapse
yes that's the app but check out my rootzwiki thread the flashable zip file adds the detailing script to your sd card that you'll need if you feel your device slowing down.
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip
p2kmafia said:
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip
Click to expand...
Click to collapse
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.
I don't know what to tell you. I just re-ran the detailing script and I don't receive those errors, but if you know it is installed correctly/is vacuuming it shouldn't be a problem. I wish I knew more about this software to help out. I just discovered it helps a lot haha.
Cilraaz said:
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.
Click to expand...
Click to collapse
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium
Endless2232 said:
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Script manager as root. Command line as root. The entire script and individual manual vacuums. Same result on all. Maybe I'll boot into CWM and run a fix permissions to see if that does anything.
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium
Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?
p2kmafia said:
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?
Click to expand...
Click to collapse
No, you're fine.
So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium
Crap7126 said:
So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.
p2kmafia said:
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.
Click to expand...
Click to collapse
Failed for me.
Sent from my SCH-I510 using xda premium
deafptl4ever said:
Failed for me.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
what failed for you? i'd love to help out but need a little more information
Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Click to expand...
Click to collapse
If this was in regard to my issue, it's of no consequence. The sqlite3 executable was running fine, as evidenced by the fact that there were no errors in executing sqlite3 (the REINDEX command ran without problem). The permission issue would be with the database files themselves, though root should have no permission issues on r/w partitions like data and dbdata, or wherever sqlite3 is trying to write the temporary database during the VACUUM process. The VACUUM process actually reads data out of the database file, stores it in a temporary file, and then overwrites the original file with data from the temporary file. This eliminates "blank" data and fragmentation within the database files, which is why you see a slight performance increase and smaller database footprint.
Does anyone know where that temporary db file is stored by sqlite3?
Cilraaz said:
Does anyone know where that temporary db file is stored by sqlite3?
Click to expand...
Click to collapse
Unfortunately my expertise stops at how it works/why it works I just found out that it helps my phone and that's it
This def made my phone much snappier. My only question is, when i run the script i get a constant error, "error mountind database". Not really sure whato do (if anything) since it has made the phone quicker regardless.
Sent from my SCH-I510 using XDA
I created a shell script to do full internal memory backup.
Backup will be saved to "/sdcard/external_sd/devbackup".
Versions
2013-02-19: v1.0 (DOWNLOAD)
- Added option to backup user partitions.
- Added safety checks for device model, busybox availability and running user.
- Works on GB only.
- Needs Busybox.
Code:
su
busybox sh /sdcard/backup.sh system
Code:
su
busybox sh /sdcard/backup.sh user
2013-02-08: v0.5 (DOWNLOAD)
- Backups only system partitions.
- Runs on GB and JB without Busybox.
Code:
su
sh /sdcard/backup.sh
Partitions
System partitions
01 = param.lfs.md5
02 = modemfs.img.md5
03 = system.img.md5
06 = cspsa.img.md5
07 = EFS.img.md5
09 = hidden.img.md5
10 = GT-I9070_EUR_XX_8G.pit.md5
11 = ssgtest.img.md5
12 = ipl.bin.md5
13 = modem.bin.md5
14 = normal.bin.md5
15 = kernel.bin.md5
16 = normal2.bin.md5
17 = kernel2.bin.md5
User partitions
4 = cache.img.md5
5 = userdata.img.md5
8 = ums.rfs.md5
Post it in general section next time,report your thread to a mod and tell him to move this.
You can/should use general section for this topics.
Re: Full backup
mj111996 said:
Post it in general section next time,report your thread to a mod and tell him to move this.
Click to expand...
Click to collapse
How do I do that?
Sent from my GT-I9070 using xda app-developers app
Skarllot said:
How do I do that?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Hit orange triangle with "!" inside of it in top right corner of first post.
Skarllot said:
I created a shell script to do full internal memory backup.
To run the script type the following into terminal:
su
busybox sh backup.sh system
Download: http://goo.gl/Ky9qH
Needs Busybox.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
shut_down said:
Hit orange triangle with "!" inside of it in top right corner of first post.
Click to expand...
Click to collapse
Is a text document? must be stored in one place on the telephone?
emmanueldmc said:
Is a text document? must be stored in one place on the telephone?
Click to expand...
Click to collapse
It's a script... copy all the text, create a new text document, paste in the new text document calling it something like : fullbackup.sh .
Then
Move it to telephone, install smanager (Script Manager) , run it as SU . Done
Skarllot said:
I created a shell script to do full internal memory backup.
To run the script type the following into terminal:
su
busybox sh backup.sh system
Download: http://goo.gl/Ky9qH
Needs Busybox.
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I tried to install by Terminal and script manager but always i get this error:
Thanks for share your script!
So, can I ask what the script can copy? I mean, can you specify what it does, what it will backup, what it can't ?
To be more clear, It can backup everything, even the bootloader, so we can flash all stock again? In my country (Brazil), Samsung called that phone "Galaxy SII Lite" and the bootloader image has this text . Could it be a way to turn back to my stock? People have told that with this tuto:[ Solved ] How to Downgrade JB 4.1.2 to GB 2.3.6 the text of bootloader image becomes "Galaxy S Advance". By the way, I am just asking. I have no trouble with all that stuff, only curiosity.
Sorry for noob questions and poor english!
johnnybr said:
Thanks for share your script!
So, can I ask what the script can copy? I mean, can you specify what it does, what it will backup, what it can't or how to "restore" that backup?
Sorry for noob questions and poor english!
Click to expand...
Click to collapse
It will backup all your partitions. You could look at its content and find out.
Code:
SPART1="1,param.lfs.md5"
SPART2="2,modemfs.img.md5"
SPART3="3,system.img.md5"
SPART4="6,cspsa.img.md5"
SPART5="7,EFS.img.md5"
SPART6="9,hidden.img.md5"
SPART7="10,GT-I9070_EUR_XX_8G.pit.md5"
SPART8="11,ssgtest.img.md5"
SPART9="12,ipl.bin.md5"
SPART10="13,modem.bin.md5"
SPART11="14,normal.bin.md5"
SPART12="15,kernel.bin.md5"
SPART13="16,normal2.bin.md5"
SPART14="17,kernel2.bin.md5"
UPART1="4,cache.img.md5"
UPART2="5,userdata.img.md5"
UPART3="8,ums.rfs.md5"
In that location is stored the full backup?
emmanueldmc said:
In that location is stored the full backup?
Click to expand...
Click to collapse
By the content of the script location of backed up files will be: /sdcard/external_sd/devbackup/
P.S. And those backed up files are Odin flashable, as I see. OP could add how to restore on the first post. It is pointless just write how to backup, without explanation how to restore.
Re: Full backup
shut_down said:
By the content of the script location of backed up files will be: /sdcard/external_sd/devbackup/
P.S. And those backed up files are Odin flashable, as I see. OP could add how to restore on the first post. It is pointless just write how to backup, without explanation how to restore.
Click to expand...
Click to collapse
Sorry, it's my next step.
I'll do a restore script, but I have been busy.
Sent from my GT-I9070 using xda app-developers app
Re: Full backup
emmanueldmc said:
In that location is stored the full backup?
Click to expand...
Click to collapse
I'll update the script to show that explicitly.
Sent from my GT-I9070 using xda app-developers app
Re: Full backup
emmanueldmc said:
I tried to install by Terminal and script manager but always i get this error:
Click to expand...
Click to collapse
Please, try to run without "system" parameter/command.
Sent from my GT-I9070 using xda app-developers app
So, someone managed to make work this script? I don't know what is messed here, but no success at now...
Re: Full backup
johnnybr said:
So, someone managed to make work this script? I don't know what is messed here, but no success at now...
Click to expand...
Click to collapse
Any message?
Sent from my GT-I9070 using xda app-developers app
Re: Full backup
How is this different /better than nandroid backups ?
Sent from my GT-I9070 using xda app-developers app
Re: Full backup
Sadvance said:
How is this different /better than nandroid backups ?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I really don't know, I never tested it.
Sent from my GT-I9070 using xda app-developers app
Skarllot said:
Any message?
Click to expand...
Click to collapse
With terminal emulador:
"sh: applet not found"
With SManager, first: "Current value is " " and was expected "GT-I9070";
then I marked the SU icon before execute the script, this time the result was that screen, that I can't understand. I will attach.
So I need a real developers opinion. The build prop mod doesn't work. How would one go about enabling this? Is there a modification that needs to be done to the framework-res? SystemUI? Both? Please help. I can find jack about this for any device.
Sent from my XT1080 using XDA Premium 4 mobile app
+1 I have done a lot of digging and can't find a way so far to make it work. It looks like the button properties are somewhere else. I didn't see the home, back, and recent button entries in build prop ether.
Sent from my XT1080 using Tapatalk 4
TheWhiteChallenger said:
So I need a real developers opinion. The build prop mod doesn't work. How would one go about enabling this? Is there a modification that needs to be done to the framework-res? SystemUI? Both? Please help. I can find jack about this for any device.
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Post your framework-res (and blur res if applicable) and your systemui apk and il take a look at it
runandhide05 said:
Post your framework-res (and blur res if applicable) and your systemui apk and il take a look at it
Click to expand...
Click to collapse
Should I deodex the systemui or would u need it stock with the odex file?
TheWhiteChallenger said:
Should I deodex the systemui or would u need it stock with the odex file?
Click to expand...
Click to collapse
Needs to be deodex
runandhide05 said:
Needs to be deodex
Click to expand...
Click to collapse
thanks a bunch. here you go. i had to compress the framework to stay under the 8mb limit
royer10r said:
+1 I have done a lot of digging and can't find a way so far to make it work. It looks like the button properties are somewhere else. I didn't see the home, back, and recent button entries in build prop ether.
Sent from my XT1080 using Tapatalk 4
Click to expand...
Click to collapse
Yes I'm pretty sure I found the files for hw buttons and lights and I found the imgs for back home and recent in the system ui I just have no clue how to enable them. I think something needs to be added to one of the XML files of the ui
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Yes I'm pretty sure I found the files for hw buttons and lights and I found the imgs for back home and recent in the system ui I just have no clue how to enable them. I think something needs to be added to one of the XML files of the ui
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After compairing the build.prop of both the Moto X and Ultra the only thing that stood out to me that may enable the softkeys is the line:
ro.product.display=Moto X
Click to expand...
Click to collapse
Try placing it under # ADDITIONAL_BUILD_PROPERTIES After you have backed up of course.
Also, look for an xml in systemui.apk called navigation_bar.xml. It should be located in res/layout/ of your decompiled systemui apk.
What brand moto x is that I have a sprit build.prop and its didn't have ro.product.display at all. Neither dose my maxx
Sent from my XT1080 using XDA Premium 4 mobile app
Nvrmnd it just got left out when I copied it to a word doc somehow
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Yes I'm pretty sure I found the files for hw buttons and lights and I found the imgs for back home and recent in the system ui I just have no clue how to enable them. I think something needs to be added to one of the XML files of the ui
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
are you using an unlocked version?
have you tested your deodex framework-res to ensure it works?
if i give you a moddified framework-res.apk do you know how to properly push it? obviously you need root and RW on the /system
do u have a backup?
or a way back if need be?
in other words do you know what you are doing?
and will not hold me responsible in any way shape or form?
and fyi you cant just adb push the framework while booted you will bootloop. cause you have to rm - the odex and apk will be over written when you push, the best way would be to push it while in recovery, ( which you would only have if you have a dev version)
i say all that to warn you,
A) its 100% untested.
b) i dont have a device to even test it on.
C) beware bootloop is a possibility especially if you dont know what you are doing.
its compressed just unzip do what you will with it
framework-res.zip Show_navbar
and yes your right(ish) the bool.xml in the framework has to be changed from
Code:
<bool name="config_showNavigationBar">[COLOR="Red"]false[/COLOR]</bool>
to
Code:
<bool name="config_showNavigationBar">[COLOR="red"]true[/COLOR]</bool>
Actually strangely enough the framework res is factory deodex. No I don't have Dev edition (yet) to pushing via adb is out right? Will copy and paste with root explorer work, setting proper permissions of course, or is it going to f%#k up right away? I have no total back up but I've got the important stuff and it wouldnt be the first time of me using the fxz back to stock
Sent from my XT1080 using XDA Premium 4 mobile app
And I absolutely will hold you responsible.
Not really.
Sent from my XT1080 using XDA Premium 4 mobile app
I am not responsible for what you do to your phone. I am 99.9% sure this will not bork your phone but if it does its your fault not mine. OK? Great. Enjoy.
I dont have this phone though ive done this on other phones ive owned. Im confident it will work.
If anyone is feeling adventurous, ive modified the framework-res.apk to show the nav keys. Below is the best way to apply it. You must be rooted and be willing to flash back to stock if things go wrong (or push the backed up app if possible). You may have issues if you are not deodexed, though included in the instructions below is how to apply it even if you are not. You also must be able to use adb. Id make a flashable zip but you dont have a recovery.
Copy the framework-res.apk file to your internal storage however you please.
Make sure your phone is plugged into your computer and adb debugging is enabled.
Type the following commands (read carefully!):
adb shell
Click to expand...
Click to collapse
su
Click to expand...
Click to collapse
(look on your phone, it may ask for superuser permissions, allow it)
stop
Click to expand...
Click to collapse
(note: this will make your screen go black and it will be unresponsive, this is normal)
cp /sdcard/framework-res.apk /system/framework/
Click to expand...
Click to collapse
(if you have a problem at this point type: adb remount and try this step again.)
rm /system/framework/framework-res.odex
Click to expand...
Click to collapse
(only do this if your apk is not deodexed)
reboot
Click to expand...
Click to collapse
On reboot you should have onscreen nav keys.
Here is the modded framework: https://dl.dropboxusercontent.com/u/44601870/framework-res.apk
I see runandhide05 has also done the mod for you. I can confirm that what he (and I) have done is what adds the nav keys to the moto x (which i have).
mentose457 said:
I am not responsible for what you do to your phone. I am 99.9% sure this will not bork your phone but if it does its your fault not mine. OK? Great. Enjoy.
I dont have this phone though ive done this on other phones ive owned. Im confident it will work.
If anyone is feeling adventurous, ive modified the framework-res.apk to show the nav keys. Below is the best way to apply it. You must be rooted and be willing to flash back to stock if things go wrong (or push the backed up app if possible). You may have issues if you are not deodexed, though included in the instructions below is how to apply it even if you are not. You also must be able to use adb. Id make a flashable zip but you dont have a recovery.
Copy the framework-res.apk file to your internal storage however you please.
Make sure your phone is plugged into your computer and adb debugging is enabled.
Type the following commands (read carefully!):
(look on your phone, it may ask for superuser permissions, allow it)
(note: this will make your screen go black and it will be unresponsive, this is normal)
(if you have a problem at this point type: adb remount and try this step again.)
(only do this if your apk is not deodexed)
On reboot you should have onscreen nav keys.
Click to expand...
Click to collapse
Questions... Is this for the modded framework red posted above I don't see a link for one in ur post?
If u did do one ur self did you do it off of the FW red I posted?
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Questions... Is this for the modded framework red posted above I don't see a link for one in ur post?
If u did do one ur self did you do it off of the FW red I posted?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should be in my post now. It is infact of the framework you posted on the first page.
The adb crap may not work right now. You need to mount the system as r/w and i dont know what file system the X/Ultra etc use. Though it may work because the way root was aquired for this phone. Worst case is you cant copy the file to the system. No harm will be done.
mentose457 said:
It should be in my post now. It is infact of the framework you posted on the first page.
The adb crap may not work right now. You need to mount the system as r/w and i dont know what file system the X/Ultra etc use. Though it may work because the way root was aquired for this phone. Worst case is you cant copy the file to the system. No harm will be done.
Click to expand...
Click to collapse
It should be noted that there were two ways to root your ohone, the first DID NOT allow rw on the /system
The second from jcase allows rw only when booted into "recovery" which is not the normal recovery but a mirror img of your /system and will appear as normally booted however you have rw access to the system.
This is how you would have to do it. If you rooted with his first release you wont have rw on the system, if thats the case use his latest release and follow his instructions in his OP then do as mentose457 suggested
Thanks a bunch guys my battery's almost dead so I'm going to try this in the morning. And thank you runanhind for giving specifics as to what was done
Sent from my XT1080 using XDA Premium 4 mobile app
Oh and what is the adb command to reboot to recovery if there is one? I've had problems getting changes to stick if the first reboot after the changer doesn't have write access
Sent from my XT1080 using XDA Premium 4 mobile app
TheWhiteChallenger said:
Oh and what is the adb command to reboot to recovery if there is one? I've had problems getting changes to stick if the first reboot after the changer doesn't have write access
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I believe it's:
Code:
adb reboot recovery
But someone please correct me if I'm wrong... =x
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just long press outside a menu (2 sec and slightly change pressure after the delay)
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy S5 Unified (klte): International, Canada, Sprint, TMO
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/klte
Notice: ATT and VZW are locked. You must unlock them to be able to flash a recovery
Click to expand...
Click to collapse
special credits to @PlayfulGod for his unified device tree
https://github.com/playfulgod
XDA:DevDB Information
[klte][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Samsung Galaxy S 5
Contributors
Phil3759
Version Information
Status: Stable
Created 2014-04-04
Last Updated 2014-04-16
reserved
You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.
PlayfulGod said:
You did notice that there was a issue with internal storage right?? It was suggested I could fix using a init file but I've not had a chance to work on it yet. If you happen to have the same issue and fix it, please share and let me know what you did.
Click to expand...
Click to collapse
ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code
Phil3759 said:
ups, sorry, I did not notice
Link to the exact issue?
Sure if I find a fix I will share all sources. That's what I always do now, outside the touch code
Click to expand...
Click to collapse
not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.
TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol
Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.
PlayfulGod said:
not sure of the source of the issue, but its internal sd/storage is read only. So no backups can be made to internal storage. Restoring data works fine tho.
TWRP doesnt have this issue tho, so I think its in the device repo and prolly something simple. lol
Also this is only known to work with the G900F so far. The kernel src I have on github is technically for the G900D, but its working in CWM. Just seems to be missing model specific dts files.
Click to expand...
Click to collapse
Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files
Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)
Can you try this:
ensure you are not using the recovery.fstab file in your device tree but the fstab.qcom
adb shell:
Code:
mount /system
/system/bin/toolbox setenforce permissive
Click to expand...
Click to collapse
See if you can now access internal storage in write mode
Phil3759 said:
Not having the device makes it a too long debug process. Also, seems few users interested in debugging it
About write to sdcard, it is probably a selinux permission issue. At least that's what I most often encountred
I looked at your twrp sources. They use custom selinux permission files
Well, in fact they are using Samsung enforced permissions and they run this at boot:
Code:
toolbox setenforce permissive
You'll have to mount /system for that than unmount it as we have still no setenforce in busybox (they are in Pruvot custom busybox repo though)
Can you try this:
See if you can now access internal storage in write mode
Click to expand...
Click to collapse
Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.
I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.
Its using the fstab.qcom.
PlayfulGod said:
Agreed, debugging w/o the device is a pita. lol
I seen that as well and had the tester try to set it. Not sure if they mounted system first, so will have them try it again to make sure. If they did, it didnt help.
I will have to check and see which fstab I have it using too. When I hear from my tester I will test all your suggestions. And thanks.
Its using the fstab.qcom.
Click to expand...
Click to collapse
Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users
If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level
Phil3759 said:
Oh, you're also doing it blindly
It can be possible, but not with such a non existing feedback from users
If you think testers are just able to boot and check, try to add the needed lines to postrecoveryboot.sh (inherited from msm8960-common/recovery)
Code:
mount [BLKID] /system
/system/bin/toolbox setenforce permissive
umount /system
However, I think you need the blkid, not sure the path symlink to partition will work
You cannot just make a mount /system from postrecoveryboot.sh as the fstab file is not yet generated by recovery at that level
Click to expand...
Click to collapse
I will give that a try. thanks
img built and linked to tester(s).
PlayfulGod said:
I will give that a try. thanks
img built and linked to tester(s).
Click to expand...
Click to collapse
Thanks,
will watch your thread and wait for testers before wasting more time on it
Phil3759 said:
Thanks,
will watch your thread and wait for testers before wasting more time on it
Click to expand...
Click to collapse
Philz, its boot looping! it doesnt work at all !
leoaudio13 said:
Philz, its boot looping! it doesnt work at all !
Click to expand...
Click to collapse
Can you post a stock recovery.img please!
Phil3759 said:
Can you post a stock recovery.img please!
Click to expand...
Click to collapse
Here you are : https://drive.google.com/file/d/0B3HkAzPm36j4b05kbDNtTVA1ZnM/edit?usp=sharing
I'll test this on Friday. Verizon S5 on it's way that day.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Philz,
Thank You for all you did.
Every time i'm buying a new phone, i have the pleasure to get your recovery "ready to install".
Great work, great support.
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Has this been tested on a 900H Model?
Phil3759 said:
Update Alpha 6.26.1
- proper repack on stock kernel
- selinux permissive hack
Download: (flash in odin)
http://d-h.st/B20
The aim is to only see if it boots
If it boots, we're ready to fix any bugs and make it stable
Click to expand...
Click to collapse
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk
leoaudio13 said:
Gahhh! Ive been waiting for yours to test. Now im in Cambodia on business. Will test when im bak by 2mo tks again Philz
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
LoL
Two months!
Hope someone else will test before
Phil3759 said:
LoL
Two months!
Hope someone else will test before
Click to expand...
Click to collapse
U dissapeared since I post u the stock recovery lol. I was wondering
Sent from my SM-G900F using Tapatalk