Database Develop

[SCRIPT] Toggle JIT on/off (updated instructions)

This will NOT work in CM5.0b4 as JIT has been disabled entirely
It seems like a lot of people are constantly pulling/editing/pushing build.conf in order to turn JIT on and off, so I threw together a short script to toggle it on and off.
It's nothing elaborate, but it gets the job done. This is meant to work with the build.prop that comes stock with cyanogenmod 5.0b2 but will most likely work with other build.props that have JIT.
Steps to run the script:
1) Download jit.txt, rename it jit.sh
2) If you downloaded from your computer, run "adb push jit.sh /sdcard" or mount your device and copy to your sdcard.
3) In terminal on Nexus One:
$ su
# sh /sdcard/jit.sh
JIT toggled ON
JIT enabled upon reboot
#
You can also set it up in GScript or GScript Lite so you can add an icon on your homescreen to toggle JIT more easily:
1) From command line: mv /sdcard/jit.sh /sdcard/gscript/jit.sh
2) Open GScript
3) Go to Menu->Add Script
4) Go to "Load file"
5) Select jit.sh
Then to make an icon on your homescreen:
1) Long press homescreen
2) Select Shortcuts
3) Select GScript(Lite)
4) Select jit
You must reboot for the changes to take effect after running the script. If you prefer, simply put "reboot" (without quotes) on it's own line at the end of the script and it will reboot automatically. Only do this after you have confirmed that the script works for you.
If you are using Windows, make sure you use the attached jit.txt rather than copying the code from this post. Copying/pasting the code will not work because of Windows CR/LF line breaks.
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
if grep -q fast /system/build.prop ; then
sed -i s/=int:fast/=int:jit/ /system/build.prop
echo "JIT toggled ON"
echo "JIT enabled upon reboot"
else
sed -i s/=int:jit/=int:fast/ /system/build.prop
echo "JIT toggled OFF"
echo "JIT disabled upon reboot"
fi
exit

mhaedo said:
It seems like a lot of people are constantly pulling/editing/pushing build.conf in order to turn JIT on and off, so I threw together a short script to toggle it on and off.
It's nothing elaborate, but it gets the job done. This is meant to work with the build.prop that comes stock with cyanogenmod 5.0b2.
Simply push the script to your phone (sdcard, or wherever you please) and run it. For example, put the quoted text into a file called jit.sh, push it to the root of your sdcard, and run "sh /sdcard/jit.sh" from a terminal. You can also set it up in GScript or GScript Lite so you can add an icon on your homescreen to toggle JIT more easily.
You must reboot for the changes to take effect.
Click to expand...
Click to collapse
Nice - been looking for just this, thanks. As a bit of a n00b, any idea why this doesn't seem to run in GScript Lite? I get the SU request OK, but then nothing - don't see the echo'd text at all, nowt. Running CM5b2 .29 kernel.

Ive installed pauls modaco patch wil this turn jlt off? its annoying me

Thanks for this script !

I just pull, nano, and push it back.
I don't think It's 100% stable.

push/pull? Shoot, I just use vi on build.prop from betterterminal. Don't have to mess with adb at all

Since you need to reboot anyway, couldn't we just put "reboot" in place of "exit"? I'm assuming that's not part of the script to save, since you have "fi" at the end of it. Personally, what I did is save 2 versions of build.prop to my sdcard and then built gscripts to swap 'em out. lol A little more crude, but just as effective.

when i try to run the jit.sh file in terminal i get:
failed: no such file or directoryk3 on /system : not found
sdcard/jit.sh : 13: syntax error: end of file unexpected (expecting 'then")
am i completely retarded?

trisl said:
Nice - been looking for just this, thanks. As a bit of a n00b, any idea why this doesn't seem to run in GScript Lite? I get the SU request OK, but then nothing - don't see the echo'd text at all, nowt. Running CM5b2 .29 kernel.
Click to expand...
Click to collapse
Yeah, I had the same problem. Remove the su request from superuser.apk. Then, run any script that requires root. Click remember, and allow. It will not work at this point. Back out to the homescreen with the back button, then go back into GScript Lite and run it again. It should work this time.
Guitarfreak26 said:
Ive installed pauls modaco patch wil this turn jlt off? its annoying me
Click to expand...
Click to collapse
Not sure. I would assume so, never seen the build.prop that's used but I don't see why it would be any different.

Mi|enko said:
Since you need to reboot anyway, couldn't we just put "reboot" in place of "exit"? I'm assuming that's not part of the script to save, since you have "fi" at the end of it. Personally, what I did is save 2 versions of build.prop to my sdcard and then built gscripts to swap 'em out. lol A little more crude, but just as effective.
Click to expand...
Click to collapse
That would be more efficient, but I just enjoy clicking my icon a few times and toggling it on and off Don't ask me why.

[email protected] said:
push/pull? Shoot, I just use vi on build.prop from betterterminal. Don't have to mess with adb at all
Click to expand...
Click to collapse
How would I do that? I have betterterminal emulator pro..

Four Fourty Four said:
How would I do that? I have betterterminal emulator pro..
Click to expand...
Click to collapse
$ su
# vi /system/build.prop
Proceed to edit (man vi, google vi). Bit of a pain in the ass though if you switch back and forth frequently.

mhaedo said:
$ su
# vi /system/build.prop
Proceed to edit (man vi, google vi). Bit of a pain in the ass though if you switch back and forth frequently.
Click to expand...
Click to collapse
Don't forget, you need to remount /system as rw also. it is a tiny bit of a pain, but I don't see much of a reason to switch back and forth all the time. Thus far I have yet to have any problems with JIT.

[email protected] said:
Don't forget, you need to remount /system as rw also. it is a tiny bit of a pain, but I don't see much of a reason to switch back and forth all the time. Thus far I have yet to have any problems with JIT.
Click to expand...
Click to collapse
The only time I consistently have problems with JIT is when tethering. Otherwise, I have yet to have any issues. I tether frequently, hence the script.
BTW, thanks for Apps2SD(2) and OpenOverclocker. They were very helpful to me at one point.

blakestimac said:
when i try to run the jit.sh file in terminal i get:
failed: no such file or directoryk3 on /system : not found
sdcard/jit.sh : 13: syntax error: end of file unexpected (expecting 'then")
am i completely retarded?
Click to expand...
Click to collapse
+1
I'm getting this message also.

blakestimac said:
when i try to run the jit.sh file in terminal i get:
failed: no such file or directoryk3 on /system : not found
sdcard/jit.sh : 13: syntax error: end of file unexpected (expecting 'then")
am i completely retarded?
Click to expand...
Click to collapse
Hm, strange. I can't duplicate this error. The steps I take are as follows:
1) Cut/paste the quoted code in the original post and save it in a document called jit.sh
2) On computer, adb push jit.sh /sdcard
3) In terminal on Nexus One:
$ cd sdcard
$ su
# sh jit.sh
JIT toggled ON
JIT enabled upon reboot
#
I'm sorry I can't be more help, but I'm not sure why you'd see that error.

mhaedo said:
Hm, strange. I can't duplicate this error. The steps I take are as follows:
1) Cut/paste the quoted code in the original post and save it in a document called jit.sh
2) On computer, adb push jit.sh /sdcard
3) In terminal on Nexus One:
$ cd sdcard
$ su
# sh jit.sh
JIT toggled ON
JIT enabled upon reboot
#
I'm sorry I can't be more help, but I'm not sure why you'd see that error.
Click to expand...
Click to collapse
Ok, I didn't do the whole adb push thing, I just copied it to my SDcard root from windows. Is that the problem?

BoostedSR20 said:
Ok, I didn't do the whole adb push thing, I just copied it to my SDcard root from windows. Is that the problem?
Click to expand...
Click to collapse
Ah, it's the line breaks. Windows uses a pair of CR and LF characters to terminate lines. Unix based system use an LF character only.
You can get a utility to convert the line breaks to unix style line breaks. I'm sure it will come in handy. I'll also upload the jit.sh with proper line breaks to the original post.

BoostedSR20 said:
Ok, I didn't do the whole adb push thing, I just copied it to my SDcard root from windows. Is that the problem?
Click to expand...
Click to collapse
Just tried pushing it to the sdcard, that went thru ok.
Still cant get it to run, same error. I've tried your command in the OP, and the what you wrote out a couple posts up. Same error on each one.

mhaedo said:
Ah, it's the line breaks. Windows uses a pair of CR and LF characters to terminate lines. Unix based system use an LF character only.
You can get a utility to convert the line breaks to unix style line breaks. I'm sure it will come in handy. I'll also upload the jit.sh with proper line breaks to the original post.
Click to expand...
Click to collapse
Ahhh, so it had to do with me making the file in the Windows Notepad. Got it..

[SCRIPT] Add BASH shell to your rooted Milestone

Don't know if this has been mentioned anywhere, but I'll post it anyway...
This utility will come in handy for those who use terminal emulators. "Bash" features command completion (by holding the center button on the directional pad) and can execute previous commands from history (by pressing Up on the direction pad).
Simply unzip the attachment to anywhere on your SD card, and, using a terminal emulator like ConnectBot do the following:
Code:
cd sdcard/[I]<folder where bash was saved>[/I]
su
sh bash.sh
Or, if you want to run from OpenRecovery, then unzip the files under /sdcard/OpenRecovery/scripts, then edit "bash.sh" so that the "cp bash/bash /system/bin" line is changed to "cp /sdcard/OpenRecovery/scripts/bash/bash /system/bin". To install it, use the "Miscellaneous->Run Script" option from OpenRecovery.
It will automatically take effect as your default shell the next time you start a terminal session or reboot. Or just type 'bash'

Thanks for the script , I havent had a chance to use it just yet but it would be extremely useful
~PsyCl0ne

PsyCl0ne said:
Thanks for the script , I havent had a chance to use it just yet but it would be extremely useful
~PsyCl0ne
Click to expand...
Click to collapse
No problem! It's a time saver for me... no more need to re-type commands or type out the long folder names.

Isnt busybox sh acting the same way ? whats advantage over busybox sh ?

http://www.faqs.org/faqs/unix-faq/shell/shell-differences/
Scroll down till you see a table...

zewelor1 said:
Isnt busybox sh acting the same way ? whats advantage over busybox sh ?
Click to expand...
Click to collapse
I think the most visible is the permanent history.
Busybox has the permanent history as compile option but nobody cares to enable it.
For the rest the busybox's shell is more than enough for the limited usage on a cellphone.

oh this is awesome.
Gonna come in real handy for ro/rw mounting. I'd been cheating by throwing a bunch of common commands into the 'first command' line and saving different connection profiles in ConnectBot
-----
*edit*
bummer, couldn't get Terminal Emulator to initialize the session. Attached is a zip with sh.sh to restore your shell to sh - actually, it just redirects the sym. link from bash to sh (sh0 binary), so you could use it to swap back and forth if you want - bash is left on the system.

[Q] How did I screw up the "ls" command in adb shell?

I don't know how I did it. I don't even know if it's a windows 7 thing, or a adb shell thing. But...
When I open adb shell and enter the "ls" or "ls -l" command, it returns the name of the file/dir in a strange format. Instead of just the name like "sdcard" I get:
<-[1;34msdcard<-[0m
I'm pretty sure it didn't always do this, so I must have enabled a switch somewhere (or I'm misusing the "ls" command). I do not have this problem with Terminal Emulator on the Captivate itself... just when using ADB shell on a Windows 7 machine. How do I turn this off? Any help would be greatly appreciated.
Thanks!

dc41 said:
I don't know how I did it. I don't even know if it's a windows 7 thing, or a adb shell thing. But...
When I open adb shell and enter the "ls" or "ls -l" command, it returns the name of the file/dir in a strange format. Instead of just the name like "sdcard" I get:
<-[1;34msdcard<-[0m
I'm pretty sure it didn't always do this, so I must have enabled a switch somewhere (or I'm misusing the "ls" command). I do not have this problem with Terminal Emulator on the Captivate itself... just when using ADB shell on a Windows 7 machine. How do I turn this off? Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
ugh, this isn't garbage information or a mistake. this is windows command prompt (which isn't a proper terminal emulator) not being able to deciper the color coding techniques used in *NIX shells.
all these odd numbers are are simply color coding to "prettify" the shell if you're using a *NIX shell

Kaik541 said:
ugh, this isn't garbage information or a mistake. this is windows command prompt (which isn't a proper terminal emulator) not being able to deciper the color coding techniques used in *NIX shells.
all these odd numbers are are simply color coding to "prettify" the shell if you're using a *NIX shell
Click to expand...
Click to collapse
Thanks for the info! Now that I know what's going on, I should be able to find solution on the web.
Thanks!

dc41 said:
I don't know how I did it. I don't even know if it's a windows 7 thing, or a adb shell thing. But...
When I open adb shell and enter the "ls" or "ls -l" command, it returns the name of the file/dir in a strange format. Instead of just the name like "sdcard" I get:
<-[1;34msdcard<-[0m
I'm pretty sure it didn't always do this, so I must have enabled a switch somewhere (or I'm misusing the "ls" command). I do not have this problem with Terminal Emulator on the Captivate itself... just when using ADB shell on a Windows 7 machine. How do I turn this off? Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
I've never had this happen when I use the adb shell on my Win7 machine. Which distro are you using? I have Home Premium x64.

miztaken1312 said:
I've never had this happen when I use the adb shell on my Win7 machine. Which distro are you using? I have Home Premium x64.
Click to expand...
Click to collapse
Ultimate 64, but like I said, it wasn't always like this. Some point in the lady week I must have changed a setting or something. Now I just have to figure out what I did and how to undo it.

I am guessing you switched ROMs? Seems to be the color setting in some of the ROMs on the LS command. It is not a windows bug, any terminal/shell that doesn't support colored directory/file names will give you this behavior.
See this thread for a fix:
http://forum.xda-developers.com/showthread.php?p=7714491

I have been having this issue since I upgraded to JH3 and SRE 1.2.1a (which included a new busybox 1.17.1 and proper symbolic links). SRE 1.2.1a also remove the stock ls command. I did not start looking into fixing it until tonight. Setting an alias for every adb shell session is annoying. Android does not include any of the profile start scripts like linux does or we would be able to stick an alias in some place like a .bashrc or /etc/bashrc.
Here is a permanent solution. I normally have a permanent alias setup on my linux machines with the switches below, you can modify the switches to your liking.
create a file in notepad with the following:
"ls -alh --color=never [email protected]" do not include the quotes.
Note the switches I am using:
a = show all files including hidden (the ones that start with a "." as a prefix on the name)
l = show files in long listing format/layout
h = show file size in human readable format eg and 1k instead of 1000.
Save the file as "ll" without an extension. You can use another name if you wish.
Use adb to push the file into /sdcard then adb shell to copy it to /system/xbin or copy via root explorer.
#assuming ll is in your SDK tools folder - move to sdcard
adb push ll /sdcard
#move to xbin folder
adb shell
su
mv /sdcard/ll /system/xbin/ll
I didn't touch the permissions (its working with -rw-rwxr-x) but just in case you can set permissions on the file.
chmod 755 ll
I rebooted my phone and I was still good to go using "ll" from adb shell.
adb shell ll
or adb shell
$ll
enjoy.

Mine does the same, looks nice when I am using on Ubuntu. I had flashed JH3 + SRE 1.2.1a also.
Did you try using the "dir" command? I think it comes with busybox 1.7.1. That one outputs fine for me when I am using the cmd prompt. Only little quirk is that I have to remember not to use ls when logged on Win7.

color codes were removed in SRE 1.2.2a: http://forum.xda-developers.com/showthread.php?t=751934

tikidroid said:
I have been having this issue since I upgraded to JH3 and SRE 1.2.1a (which included a new busybox 1.17.1 and proper symbolic links). SRE
Click to expand...
Click to collapse
Your fix worked perfectly for me!
Thanks!

tikidroid said:
Here is a permanent solution. I normally have a permanent alias setup on my linux machines with the switches below, you can modify the switches to your liking.
create a file in notepad with the following:
"ls -alh --color=never [email protected]" do not include the quotes.
Click to expand...
Click to collapse
Ahhh.... thank you so much for this post. This has been driving me crazy for a few hours, and I almost considered putting an alias to ll in init.rc (but I much prefer this less invasive method)

Useful workaround, thanks. Still needed, some two years later!

[ADT-1] Casting

So I picked up a ADT-1 due to having Ethernet and more HD space on it. FOund out only certain apps can "cast" to it due to it being a dev device has there been anyone that figured out what needs to get it to have full casting features?
https://developer.android.com/tv/adt-1/index.html

Try changing ro.build.type to eng in build.prop, that should open up all apps.

/sub
let us know if this works

Confirmed this works!
HomerSp = worth his weight in gold.

Sorry
HomerSp said:
Try changing ro.build.type to eng in build.prop, that should open up all apps.
Click to expand...
Click to collapse
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again

Bboy_LeoGun said:
Sorry to sound like a newbie, however can someone teach me how to do this? I was trying to look it up on xda but had no luck finding anything. If anyone point me in the right direction, I would be very happy. Thank you again
Click to expand...
Click to collapse
1. Root
2. Open /system/build.prop
3. Change the line
4. Reboot
5. Enjoy.

I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?

Budius said:
I'm trying to do this but I'm being very unlucky. Not sure what's going wrong and any light on the matter will be greatly appreciated.
I changed the ro.build.type from `user` to `eng` and my device (on LPX13D) stops booting completely. All I see is the android logo and then blank screen. I already tried two times. The process I did is (from sudo on my Ubuntu 14 machine)
- adb pull /system/build.prop
- edit build.prop on `nano` on Ubuntu (change only that line)
- adb push build.prop /sdcard/
- adb shell
- su
- mount -o remount,rw /system
- mv /sdcard/build.prop /system/
the second time I adb pull /system/build.prop again just to check that the only thing changed was that, and it was fine.
The only thing I've been able to do to recover the system is to:
- install CWM from here https://forum.gtvhacker.com/adt-f52/topic1629.html (fastboot flash recovery <filename>)
- flash the image from here http://forum.xda-developers.com/har...t/adt1-stock-molly-images-unbricking-t2927888
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
any help? Maybe some bizarre permission on my ubuntu machine because I'm on "sudo shell" ?
Click to expand...
Click to collapse
build.prop has to be chmodded to 0644, or the device will not boot.

HomeSp I can't thank you enough!
That was exactly the issue. Third time is a charm.
So at the end of the procedure I:
- cd /system/
- mv build.prop build.prop.bak (just for the the sake of it)
- mv /sdcard/build.prop /system/
- chmod 0644 build.prop
- chown :root build.prop (prolly not needed but what-a-heck, why not)
- ls -l (and checked that both build.prop and build.prop.bak are exactly the same permission, owner and group)
- exit, exit adb reboot and all works great"
Thanks again!!!

Budius said:
- and then using the root from this post: https://plus.google.com/+Chainfire/posts/a5YshULM8hf to be able to "adb shell su"
Click to expand...
Click to collapse
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.

jm9843 said:
For the purposes of modifying build.prop using "adb shell su", do you only have to flash the bootloader image from the linked post? I'd like to make the bare minimum changes so that future OTA's will install after restoring the original build.prop and flashing the stock bootloader.
Click to expand...
Click to collapse
my idea was a bare-minimum changes too. I just ended up ****ing up stuff and had to re-built a couple of times until I made it right.
but yeah, if you're comfortable with terminal commands and do the proper `chmod` (which I originally didn't), you can get everything done with "adb shell su" following like this:
- from PC: adb shell pull file to your PC
- from PC: edit file
- from PC: adb shell push file to /sdcard/
- from PC: adb shell
- from device shell: su
- from device shell/su: make /system/ writable, chmod file, rename "old" build.prop, copy new one over, double check chmod before rebooting.
ps.: the root from that post does install SuperUser.apk on the device, it's there on the UI, but after you do those changes there's some options in the .apk to remove root and uninstall it (if you want to)

I just thought that I'd directly use some build prop editor apk and do it easily but now my device is bricked :v
Stock ROM on download.
I'm just getting a black screen and bootloader.

So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell

jm9843 said:
So, the build.prop edit detailed in this thread works fine to make the ADT-1 a cast target for all Google Cast enabled apps. The problem is that it's hardly worth doing right now since Google Cast support on Android TV seems to be a work in progress. There's a support article that details third-party apps that are not supported - https://support.google.com/androidtv/answer/6123347
In addition to the apps listed there, I found that Watch ESPN isn't working on ADT-1 either. It's selectable in the app, but the video playback will not start. Here's to hoping that Google brings the Google Cast Receiver app for Android TV up to snuff soon - https://play.google.com/store/apps/details?id=com.google.android.apps.mediashell
Click to expand...
Click to collapse
Have any of you tried Slingplayer casting after changing build.prop?
Apple TV just died recently, it was the most reliable thing for Airplaying Slingplayer. Chromecast slingplayer kind of is ****ty at times.

Followed Budius' instructions and it worked perfectly.
adb pull /system/build.prop
----(edit build.prop on Notepad++ and changed ro.build.type=user to ro.build.type=eng)
adb push build.prop /sdcard/
adb shell
su
mount -o remount,rw /system
cd /system/
mv build.prop build.prop.bak
mv /sdcard/build.prop /system/
chmod 0644 build.prop
chown :root build.prop
ls -l
---(checked that both build.prop and build.prop.bak are exactly the same permission, owner, and group)
mount -o remount,ro /system
exit
exit
adb reboot

during the update from 5.0 -> 5.0.2 my ADT-1 stopped working again
It showed the little droid with the belly open and an error message
so that means here I went again to restore it, and this time I manage to streamline a bit the process, so let's share with you guys. Remember, my idea with this process is to have STOCK, but with Cast working from any app. I have no intention to root, or flash custom this or that. I want something that I can cast without issues and hopefully it will update the next update without problems.
first of all, the CWM link I posted before is giving malware warnings on Chrome so I found an alternative, and of course XDA is the source (see downloads).
so to factory restore ADT-1 to good working condition, was the same I said before:
- install CWM:
Code:
fastboot flash recovery cwm_molly_recovery_lpx13d.img
- install stock image. CWM->install zip-> from ADB:
Code:
adb sideload update-molly-Stock-LPV79-1.zip
- reboot and let auto-update run until the end.
now to enable cast to all apps with absolutely minimal modifications to the system (hopefully enabling future updates to run without issues)
- reboot ADT-1, holding the button, enter fastboot mode
- reboot to the CWM, but without installing it:
Code:
fastboot boot cwm_molly_recovery_lpx13d.img
- in CWM go to `mount n storage` -> mount /system
and carry on to do the build.prop modification from there, the trick is that I did not have to install a custom recovery and did not have to install super user. I made the modification directly via a RAM-only CWM and that's it. So below is just a copy of my previous post
Code:
> adb pull /system/build.prop /home/budius/build.prop
then change the build.prop on my computer and rename to new_build.prop.
And back to terminal
Code:
> adb push /home/budius/new_build.prop /system/new_build.prop
> adb shell
# cd system
# mv build.prop build.prop.bak
# mv new_build.prop build.prop
# chmod 0644 build.prop
And that's all! Full cast enabled to ADT-1 with the most absolutely minimal system changes I could come up with :victory: :highfive:
Downloads:
- here you'll find a very nice workin CWM.
- good working stock Android TV image for ADT-1
bonus:
while searching stuff I found this: https://plus.google.com/+AdamLawrence/posts/5Yr5vG7QJUq
I didn't try it but it seems useful, so the link is there.

5.1.1 Alternative Launcher: Parental Controls Message

I have installed Google Now launcher on the 5..1.1 firmware, I have root access as well and have pm hid and removed (just rm'ing the process folders from /system/priv-app) most of the bloatware. Whenever I try to hit the "home" button it just brings up a message saying " The requested action is not permitted. Check Parental Controls settings and retry". I also pm hid and attempted to remove com.amazon.parentalcontrols and it hasn't had any effect either.
If I reboot the device it does bring up the Now launcher, but as soon as I go to another application view and try to go "back" or use the home button I get the parental controls message.

KennBr said:
I have installed Google Now launcher on the 5..1.1 firmware, I have root access as well and have pm hid and removed (just rm'ing the process folders from /system/priv-app) most of the bloatware. Whenever I try to hit the "home" button it just brings up a message saying " The requested action is not permitted. Check Parental Controls settings and retry". I also pm hid and attempted to remove com.amazon.parentalcontrols and it hasn't had any effect either.
If I reboot the device it does bring up the Now launcher, but as soon as I go to another application view and try to go "back" or use the home button I get the parental controls message.
Click to expand...
Click to collapse
Well that's a new one, though have seen people say that now launcher is finicky and to have another launched installed as well.

I to have ota 5.1.1 with root and have tried to block the stock lauuncher got the same error i tried with 2 diff launchers, i havent tried to install both then disable the stock maybe it will trigger something to do with the default settings. in one of the settings menus for one of the launchers it says something about "set default launcher" and when i select it to set it to new launcher it just opens the stock one. does anyone know if there is a way to change what launcher the home button defaults to, either through adb shell or fastboot someway.
Have you tried su pm hide com.amazon.parentalcontrols
from a adb shell

jdeandeck said:
I to have ota 5.1.1 with root and have tried to block the stock lauuncher got the same error i tried with 2 diff launchers, i havent tried to install both then disable the stock maybe it will trigger something to do with the default settings. in one of the settings menus for one of the launchers it says something about "set default launcher" and when i select it to set it to new launcher it just opens the stock one. does anyone know if there is a way to change what launcher the home button defaults to, either through adb shell or fastboot someway.
Have you tried su pm hide com.amazon.parentalcontrols
from a adb shell
Click to expand...
Click to collapse
How did you try to block it?
Whilst the stock launcher is on and is a system app the Fire OS won't let any other launcher steal default.

Pond-life said:
How did you try to block it?
Whilst the stock launcher is on and is a system app the Fire OS won't let any other launcher steal default.
Click to expand...
Click to collapse
I used adb shell pm hide com.amazon.firelauncher -- adb reboot-- reboots to apex launcher but when i push home i get the error, do i need to actually uninstall it or can i install a rom management app and remove it from system app list and freeze it im trying not to do any of this stuff without confirmation on it working, my wife is worried ill ruin her fire. Do you know how hard is it to flash back to stock firmware from a bricked Fire?
i have flashed devices before roms and recovery so im not a noob but i would just hate to be wrong and try something and not be able to fix it.

jdeandeck said:
I used adb shell pm hide com.amazon.firelauncher -- adb reboot-- reboots to apex launcher but when i push home i get the error, do i need to actually uninstall it or can i install a rom management app and remove it from system app list and freeze it im trying not to do any of this stuff without confirmation on it working, my wife is worried ill ruin her fire. Do you know how hard is it to flash back to stock firmware from a bricked Fire?
i have flashed devices before roms and recovery so im not a noob but i would just hate to be wrong and try something and not be able to fix it.
Click to expand...
Click to collapse
Hmm I'm sure that hiding it has worked for others, maybe not on 5.1.1 though, I froze it in titanium backup. Widgets didn't work in Apex until I pushed it to system but it did work as main launcher. As did trebuchet and Nova.
If it's opening when you've hidden it then suggests that it's not hidden maybe needs root shell to do it on 5.1.1 as with hiding the ads and ota

Pond-life said:
Hmm I'm sure that hiding it has worked for others, maybe not on 5.1.1 though, I froze it in titanium backup. Widgets didn't work in Apex until I pushed it to system but it did work as main launcher. As did trebuchet and Nova.
If it's opening when you've hidden it then suggests that it's not hidden maybe needs root shell to do it on 5.1.1 as with hiding the ads and ota
Click to expand...
Click to collapse
it doesnt open but it gives me the parental control error, is it possible to rename the apex application maybe to com.amazon.firelauncher.apk and overwrite the current one, after backing up the original of course, to get rid of the parental error?

jdeandeck said:
it doesnt open but it gives me the parental control error, is it possible to rename the apex application maybe to com.amazon.firelauncher.apk and overwrite the current one, after backing up the original of course, to get rid of the parental error?
Click to expand...
Click to collapse
Pretty sure that wouldn't work. It'll likely expect Apex to be able to work in ways amazon launcher can but it can't.
If you've got a back up of the original you could try renaming it or just deleting it on the tablet, I don't think hide is working as it should.
Could try the supertool to switch the launcher to nova and then change launcher to Apex after. The tool does delete the amazon launcher, so backed up original handy.
http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.

KennBr said:
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
Click to expand...
Click to collapse
so if you have perm root than first download and install
HTML:
http://www.apkdrawer.com/rom-toolbox-pro-apk/
then install the google now launcher and run it and everything get it running then reboot
next through the Rom Toolbox make the Google Now a system app
then "adb shell pm hide com.amazon.launcher" then "adb reboot"
Just incase this factors in i used the script from the super tool, since i run linux and cant run the bat file, as a guide i was trying to get my laucher "adb push Apex-Launcher.apk" & "adb shell "cp /data/local/tmp/--Apex-Launcher.apk--(my preferred laucher) /system/apps/Apex-Launcher.apk" but it would not let me mount file system as RW, so before i tried the above solution, which worked for me, i ran (adb reboot-bootloader) and (fastboot oem append-cmdline "androidboot.unlocked_kernel=true") so you may or may not have to do this before you try to hide the launcher but after you install Rom Toolbox

KennBr said:
Using pm hide com. amazon. firelauncher worked fine for me to disable the Fire launcher but I had to reboot before Google Now tried to launch. Which it did, but then trying to use the home or back buttons brings on the message.
Another weird thing, all the bloat thst I hid the same way deems to have come back overnight somehow. I did disable Ota updates so not sure how that is.
Click to expand...
Click to collapse
Those are both symptoms of the hide command not working fine. It needs to be done in root as jdeandeck did.
If you disable the ota with a hide command too I'd rename the ota files or do that again in root.

jdeandeck said:
so if you have perm root than first download and install
HTML:
http://www.apkdrawer.com/rom-toolbox-pro-apk/
then install the google now launcher and run it and everything get it running then reboot
next through the Rom Toolbox make the Google Now a system app
then "adb shell pm hide com.amazon.launcher" then "adb reboot"
Just incase this factors in i used the script from the super tool, since i run linux and cant run the bat file, as a guide i was trying to get my laucher "adb push Apex-Launcher.apk" & "adb shell "cp /data/local/tmp/--Apex-Launcher.apk--(my preferred laucher) /system/apps/Apex-Launcher.apk" but it would not let me mount file system as RW, so before i tried the above solution, which worked for me, i ran (adb reboot-bootloader) and (fastboot oem append-cmdline "androidboot.unlocked_kernel=true") so you may or may not have to do this before you try to hide the launcher but after you install Rom Toolbox
Click to expand...
Click to collapse
I am using Linux as well, I got the persistent root going, Super SU installed as described in this thread: http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64347634#post64347634 I tried intsalling the Now launcher just via the Play Store app. However, when I tried to remove the bloat from the /system/priv-apps/ directory I also noticed the filesystem was read-only so I remounted it like so (I am totally unsure if this is proper)
Code:
adb shell
su
mount -o rw,remount /system
That seemed to give me sufficiant read-write access with a root terminal.
Pond-life said:
Those are both symptoms of the hide command not working fine. It needs to be done in root as jdeandeck did.
If you disable the ota with a hide command too I'd rename the ota files or do that again in root.
Click to expand...
Click to collapse
As in a root terminal? I launched an adb shell and used su and mount as described above to get read-write access and a root terminal, then did...
Code:
cat /data/local/tmp/bloat_list | while read process ; do pm hide $process ; done
and
Code:
cat /data/local/tmp/bloat_list | while read process ; do rm -R $process ; done
It seemed to remove the directories associated with the given item on the "bloat_list" file which I compiled from the "safe to remove bloatware" threads and pushed to the /data/local/tmp directory using adb. I did this prior on 5.0.1 without breaking too much... Aside from not being able to open my account settings any longer.
Contents of my "bloat_list"
Code:
com.amazon.ags.app
com.audible.application.store
com.amazon.camera
com.amazon.client.metrics
com.android.contacts
com.amazon.csapp
com.amazon.device.backup
com.amazon.h2settingsfortablet
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kindle.otter
com.amazon.mp3
com.amazon.kindle.otter.oobe
com.amazon.kindle.otter.settings
com.amazon.kindle.personal_video
com.amazon.legalsettings
com.amazon.photos.importer
com.amazon.photos
com.amazon.platform
com.amazon.tahoe
com.amazon.venezia
com.amazon.whisperlink.core.android
com.amazon.windowshop
com.amazon.zico
com.andoid.contacts
com.android.calendar
com.android.email
com.audible.application.kindle
com.goodreads.kindle
com.nuance.edr.androidservice.service
com.amazon.webapp
amazon.jackson-19.apk
com.kingsoft.office.amz
com.amazon.kor.demo
com.amazon.ods.kindleconnect
com.amazon.accessorynotifier
com.amazon.cloud9
com.amazon.weather
com.amazon.calculator
So every item in that list would have been acted on with both pm hide and rm -R (just clarifying)
Yet somehow a good amount of the items on that list came back over night. I'm not really sure my method for removing the files really had the effect that I think it did, because everything still seemed to work as if I hadn't deleted it... Well except for the "My Account" section of the "Settings", so I don't think I should have done the "rm -R" part to delete the files because it seems to have had some kind of effect.
As for the launcher situation, I backed up the firelauncher first before trying to remove and hide it and that did seem to work, but given the parental controls message I had to restore the launcher to maintain functionality. I don't think that trying to delete the items on the bloat_list first might have "broken" something and caused the message though because I tried to change the launcher BEFORE the items on the bloat_list.
I tried installing the Apex Launcher and for whatever reason it's working even without hiding or deleting Firelauncher... Though I haven't rebooted yet so I'm doubting that will remain the case.
As for the Rom Toolbox app, what exactly does it do? Reboots the device into some kind of custom recovery where I can alter settings? I've never heard of it before.

KennBr said:
I am using Linux as well, I got the persistent root going, Super SU installed as described in this thread: http://forum.xda-developers.com/amazon-fire/orig-development/root-t3272362/post64347634#post64347634 I tried intsalling the Now launcher just via the Play Store app. However, when I tried to remove the bloat from the /system/priv-apps/ directory I also noticed the filesystem was read-only so I remounted it like so (I am totally unsure if this is proper)
Code:
adb shell
su
mount -o rw,remount /system
That seemed to give me sufficiant read-write access with a root terminal.
As in a root terminal? I launched an adb shell and used su and mount as described above to get read-write access and a root terminal, then did...
Code:
cat /data/local/tmp/bloat_list | while read process ; do pm hide $process ; done
and
Code:
cat /data/local/tmp/bloat_list | while read process ; do rm -R $process ; done
It seemed to remove the directories associated with the given item on the "bloat_list" file which I compiled from the "safe to remove bloatware" threads and pushed to the /data/local/tmp directory using adb. I did this prior on 5.0.1 without breaking too much... Aside from not being able to open my account settings any longer.
Contents of my "bloat_list"
Code:
com.amazon.ags.app
com.audible.application.store
com.amazon.camera
com.amazon.client.metrics
com.android.contacts
com.amazon.csapp
com.amazon.device.backup
com.amazon.h2settingsfortablet
com.amazon.kindle
com.amazon.kindle.kso
com.amazon.kindle.otter
com.amazon.mp3
com.amazon.kindle.otter.oobe
com.amazon.kindle.otter.settings
com.amazon.kindle.personal_video
com.amazon.legalsettings
com.amazon.photos.importer
com.amazon.photos
com.amazon.platform
com.amazon.tahoe
com.amazon.venezia
com.amazon.whisperlink.core.android
com.amazon.windowshop
com.amazon.zico
com.andoid.contacts
com.android.calendar
com.android.email
com.audible.application.kindle
com.goodreads.kindle
com.nuance.edr.androidservice.service
com.amazon.webapp
amazon.jackson-19.apk
com.kingsoft.office.amz
com.amazon.kor.demo
com.amazon.ods.kindleconnect
com.amazon.accessorynotifier
com.amazon.cloud9
com.amazon.weather
com.amazon.calculator
So every item in that list would have been acted on with both pm hide and rm -R (just clarifying)
Yet somehow a good amount of the items on that list came back over night. I'm not really sure my method for removing the files really had the effect that I think it did, because everything still seemed to work as if I hadn't deleted it... Well except for the "My Account" section of the "Settings", so I don't think I should have done the "rm -R" part to delete the files because it seems to have had some kind of effect.
As for the launcher situation, I backed up the firelauncher first before trying to remove and hide it and that did seem to work, but given the parental controls message I had to restore the launcher to maintain functionality. I don't think that trying to delete the items on the bloat_list first might have "broken" something and caused the message though because I tried to change the launcher BEFORE the items on the bloat_list.
I tried installing the Apex Launcher and for whatever reason it's working even without hiding or deleting Firelauncher... Though I haven't rebooted yet so I'm doubting that will remain the case.
As for the Rom Toolbox app, what exactly does it do? Reboots the device into some kind of custom recovery where I can alter settings? I've never heard of it before.
Click to expand...
Click to collapse
Once in terminal the commands are the same from whatever computer you are using aren't they? Doesn't rm need the full directory address as it's not through pm?
The rom toolbox I think he just used to make the Now launcher a system app, so not something you can't do in adb.

Rom Toolbox is my favorite app for everything. Here is a list of some of the features you will find:
ROM Management
Install ROM’s & themes from a growing list of ROM’s. KAPOK, Cyanogen Mod and other popular ROM’s included in ROM Toolbox Pro apk.
Create, manage & restore nandroid backups
Wipe data, cache, dalvik-cache, battery stats
Install multiple ROMs & ZIPs from your SD card
App Manager
Batch backup & restore apps and their data
Schedule backups to run at a certain time
Restore apps from nandroid backups
Backup/Restore text messages, bookmarks, accounts, etc.
Backup your apps to dropbox
Freeze/Defrost system & user apps
Backup/restore Android Market link
Task manager
Automated batch uninstaller
E-mail your apps to friends
Move any user app to the SD card
Clean up dalvik-cache
Zip align, fix permissions, wipe data & cache, force close any app
Root Explorer
Access the whole of android’s file system (including the elusive data folder!).
Batch copy/paste, zip, tar, delete, move any file or folder
Change file permissions and ownership
View, edit & share files with ROM Toolbox Pro apk
File manager with two panels for easier management
Script-er & Terminal Emulator
Create and run scripts as root
Set your scripts to run at-boot
Auto Start Manager
Enable/disable apps that run on start-up
Enable/disable any broadcast receiver, activity or service
Reboot er
Reboot recovery, powerdown, bootloader, restart status bar, etc.
Font Installer
Install custom fonts from a huge list or from your sdcard
Set fonts as favorites & send them to friends
Boot Animation Installer
Install custom boot animations from a huge collection or from your sdcard
Preview boot animations
Create a boot animation from a GIF file
Have a new random boot animation each time you boot-up!
Theme Manager & Status bar Icon Changer
Create and install full themes (Meta Morph compatible)
Customize your status bar by installing custom icons for wifi, signal, gps, etc.
Change your battery icons in the status bar to a custom one from a list of 200+
Boot Logo Changer
Change your boot logo for supported phones
Theme Chooser Themes
View a list of themes for the T Mobile Theme Chooser
Set CPU
Set CPU & scaling governor
CPU Profiles
Kernel tweaks to speed up performance
Build.prop Editor
Easily edit your build.prop
Change LCD density, improve battery life, increase performance
Auto Memory Manager
Set min free values & select from presets. Apply values at boot
SD Booster
Increase the speed of your SD card
Permissions
Contacts – Backup call log and sms
SMS – Backup call log and sms
Accounts – Backup and restore from Google Drive
As for the bloat problem the:
Code:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
Seems to be imoportant for my Special Offer "screensaver" hiding a.k.a. com.amazon.kso
but idk if this works i guess i could try myself but Rom Toolboxes App Manager feature, that is only available in the pro, can "freeze" the com.amazon.firelauncher....
ok the above seems to worked maybe having the app installed when i did it did something in the settings or i froze the launcher and just dont remember it, but when i froze the firelauncher and pushed the home button, without the apexlauncher installed, nothing happened, not even the parental control message. then i reinstalled the apex launcher, hint get the pro from the site i mentioned before, and adb reboot, it worked.
next i might try to freeze some bloatware and see what i can get rid of but still save amazon app store stuff like books, audio books+store, videos, Game circle-thats for me, music player, shop amazon, which as i type i realize i can do from the Rom Toolbox with root, i swear im not selling anything

Pond-life said:
Once in terminal the commands are the same from whatever computer you are using aren't they?
The rom toolbox I think he just used to make the Now launcher a system app, so not something you can't do in adb.
Click to expand...
Click to collapse
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.

And the commands are the same but the \ in windows commands are / in linux like android so scripts meant for windows wont work on linux, or that i have found and i cant get .bin to run but never tried to change to .sh and run as shell script but thats for another forum

jdeandeck said:
Rom Toolbox is my favorite app for everything.
As for the bloat problem the:
Code:
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
Seems to be important for my Special Offer "screensaver" hiding a.k.a. com.amazon.kso
but idk if this works i guess i could try myself but Rom Toolboxes App Manager feature, that is only available in the pro, can "freeze" the com.amazon.firelauncher....
ok the above seems to worked maybe having the app installed when i did it did something in the settings or i froze the launcher and just dont remember it, but when i froze the firelauncher and pushed the home button, without the apexlauncher installed, nothing happened, not even the parental control message. then i reinstalled the apex launcher, hint get the pro from the site i mentioned before, and adb reboot, it worked.
next i might try to freeze some bloatware and see what i can get rid of but still save amazon app store stuff like books, audio books+store, videos, Game circle-thats for me, music player, shop amazon, which as i type i realize i can do from the Rom Toolbox with root, i swear im not selling anything
Click to expand...
Click to collapse
It does seem rather a flexible toolkit.
Once you've got permanent root the fastboot bit shouldn't be needed I don't think. Hmmm.
I did clear much of the apps out, though did put Shop Amazon back on as I think something I wanted to use wouldn't work. I can't recall what though.

KennBr said:
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
Click to expand...
Click to collapse
I use it to mostly change build.prop and backup apks and terminal emulator other things that i feel comfortable doing nothing like flashing or whatever i only flash from terminal on my linux pc or there is a app for flashing lg phones nothing easier than that.

KennBr said:
Yeah they are the same since it's basically a *nix shell, was just showing how I did it. I'm not sure if there's some nuance I'm not aware of thst would make it not work... It seemed like I had all the permissions I needed, and I have root set up persistently as described in the thread I linked to.
The rom toolbox app, how does it boot recoveries if fastboot can't? Sorry I'm so used to desktops, fiddling with Androids goes above my head.
Click to expand...
Click to collapse
Ooops I edited that one while you were replying.
Unlike pm doesn't rm need to know where the file or directory is like in this from the supertool?
adb shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
so it'd need to know that those directories were in priv-app in system?
And it seems to make a different part writeable than you did, at least I think that's what the chmod does and uses disable rather than hide oh and the " " everywhere.
adb shell su -c "chmod 777 /cache"
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"

And the fastboot oem command followed by fastboot reboot, not fastboot continue, lets me adb remount fine then when im done doing whatever i use adb reboot then it will reboot and reconfigure apps and settings or something and works good.
---------- Post added at 02:36 AM ---------- Previous post was at 02:30 AM ----------
Pond-life said:
Ooops I edited that one while you were replying.
Unlike pm doesn't rm need to know where the file or directory is like in this from the supertool?
adb shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
so it'd need to know that those directories were in priv-app in system?
And it seems to make a different part writeable than you did, at least I think that's what the chmod does and uses disable rather than hide oh and the " " everywhere.
adb shell su -c "chmod 777 /cache"
adb shell su -c "pm disable com.amazon.otaverifier"
adb shell su -c "pm disable com.amazon.device.software.ota"
adb shell su -c "pm disable com.amazon.settings.systemupdates"
Click to expand...
Click to collapse
i edited what i read to what i needed and if it said adb shell i ran everything from the adb shell fro terminal instead of saying adb shell su every time i said adb shell then su then pm ...