Related
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
Thanks! Extremely happy you are deving for this phone
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
uskr said:
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
Click to expand...
Click to collapse
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Thanks! I am messing around with the APKs and scripts to get the webtop to work without the dock. So I wanted to make sure I was covered.
designgears said:
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Click to expand...
Click to collapse
I already did both adb pull of system and tar, but how did you do the retail dump?
lpsi2000 said:
I already did both adb pull of system and tar, but how did you do the retail dump?
Click to expand...
Click to collapse
tar dump as root of system
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
uskr said:
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
Click to expand...
Click to collapse
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
designgears said:
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
Click to expand...
Click to collapse
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
lpsi2000 said:
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
Click to expand...
Click to collapse
tap at the bottom right of the screen right above the search button
designgears said:
tap at the bottom right of the screen right above the search button
Click to expand...
Click to collapse
ahha, thank you. Now I know I am going crazy. I used it yesterday to wipe when the system was unstable on me after playing around with the framework. I am must have stumble on that by accident. I am wondering if this documented yet somewhere around here.
Also too bad we cannot get root from there yet.
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
realawill said:
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
Click to expand...
Click to collapse
No, I just made a bad edit and it was FC hell
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
designgears said:
No, I just made a bad edit and it was FC hell
Click to expand...
Click to collapse
Crazy....mine just would not reboot. But good to know that there is a way to recover. Love the phone but hate Motorola. Wish that it was easy as the Cappy.
Cool stuff. I may snatch the framework off the phone in stock form and make a batch package for this so folks can easily just double click to restore their framework and system app folder.
Good work DG...
I never get past that initial... Starting RSD protocol support screen. Is that fast boot? If so I'm a retard...
EDIT: I need the face palm sticky. It's not Volume UP...it's Volume Down. Reading comprehension for the loss...
azy8000 said:
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
Click to expand...
Click to collapse
I have done this several times now, it works
I soft bricked my Atrix earlier this morning, and used this to recover. The time limit is a serious pain!
I ended up needing to separate /system into 5 separate pushes of 30MB each in order to get them done in time.
Oddly, after restoring everything, the phone is no longer associated with my motoblur account, and I can't add it.
Also, I think there my be some files in /system that are unaccounted for by the filesystem, as there is 70MB more than what is present.
Edit:
Restoring the system fixed both above problems.
I rooted my DS7 and changed the "phone.apk" name, and I couldn't get past "Force Close" message, so I reset (Vol+ + Power?).
I got the option of "0. Boot", "1. Wipe"..., and selected 1.
Rebooted and was stuck at "Touch Android To Begin" - Android turns white, but does not move forward.
I reset and selected a different option of complete wipe of internal and personal data.
Rebooted and am still stuck at "Touch Android To Begin".
Any suggestions?
I have 2 SD7's, so do I need to back up a ROM off the good one and reflash the stuck one? If so, how would I do that?
Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).
Z4nd4r said:
Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).
Click to expand...
Click to collapse
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore/clear cache have changed all of that...by replacing all files/kernal/rom to factory?
S4F4M said:
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore have changed all of that...by replacing all files/kernal/rom to factory?
Click to expand...
Click to collapse
Wipe/restore, if I understand it correctly, only wipes out cache and data; basically, all of your personal information and files for apps and such (not your SD card). This leaves the kernel as it was.
Do you have CWR on there? If so, simply install a new ROM. If not, you can flash it on there via ADB, I think (check the CWR thread).
Your other option is to change the file name via ADB, or push a new one to it. I've uploaded the stock Phone.apk here:
http://www.megaupload.com/?d=EEBPHB4H
You can push it by doing
Code:
adb push Phone.apk /system/app
I think there's an adb command to simply rename, but I don't recall what it is. Once you do this, you ought to be good to go. Get signed in, then change/move both the apps and restart. It might be annoying with the force closes; not sure if you'll have to use the pinhole reset.
Good luck!
Thanks, Z4nd4r! I'll give it a whirl.
I just moved/deleted the files to test it out (and run some battery tests). I had the force close issue to the point that I couldn't do anything, so I used the pinhole reset. Booted up fine and no cell signal, just as it ought to.
What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.
S4F4M said:
What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.
Click to expand...
Click to collapse
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!
Z4nd4r said:
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!
Click to expand...
Click to collapse
Oh, I did. What was left out of the procedure I found was the mention of continuous FORCE CLOSE and the use of the pin reset.
I will write up detailed instructions for a new thread in case anyone else wanted to know.
I know this is a really old thread, but I am stuck on this as well in the same situation that the OP had. However, SuperOneClick 2.2 and 1.55 both seem unable to root the streak so I can use the adb server to push the proper apk back! Anyone have any advice? I need to rename or push both TelephonyProvider.apk *and* Phone.apk. I have tried using adb and of course it errors since the device is unrooted.
turn device vertical.
start upper right touch
lower right touch
lower left touch
upper left touch
First off I am aware that 3g data works perfectly fine on most of the aosp roms in certain areas. It does not work in the area where I live however. After pulling my hair out for a couple of months trying to google for a solution I gave up and reflashed the Stock TouchWiz OS. After Samsung push their evil 4.3 rom I decided to try to figure this issue out myself. I don't know of every 3g issue on the phone but if you have the same issues I had then this will most likely work.
My 3g Symptoms: 3g connected with 2 or 3 bars. Pandora wouldn't work. Google Play store wouldn't work. Other things wouldn't work or would be very slow. I could pull some webpages however. Also running the ookla Speedtest.net app would freeze on the upload test.
The Solutions: Basically two fixes which should give you stock 3g performance when you do both.
Before you start make a backup just in case anything goes wrong. And yes, these steps assume you have rooted your phone because you probably wouldn't need to do this if you haven't. Also I have only tested these fixes on the CM10.2 10/3 nightly and the SlimBean 4.3 roms.
Fix one: Backup Stock APNs. - note: this fix helps but I didn't come up with it and alone it doesn't fix the upload issue.
1. With your stock Samsung rom on the phone download 2 apps from the Play Store: "APN Backup & Restore" and "/system/app mover".
2. Go into the /system/app mover and click on APN Backup & Restore.
3. It will ask you to confirm and then it will ask you to reboot
4. After rebooting phone go into the APN Backup & Restore app. Click your menu button and select disable ICS Check.
5. Click Backup APNs and then click OK.
6. After backing up APNs load up your aosp rom and do steps 1 - 3.
7. Click Delete APNs.
8. Click Restore APNs.
Fix two: enable MTU probing.
1. Connect your phone to usb.
2a. Linux: run sudo adb pull /system/etc/init.qcom.post_boot.sh
2b. Windows: from an administrator command prompt do adb pull /system/etc/init.qcom.post_boot.sh
3. open init.qcom.post_boot.sh from text editor of your choice
4. find these lines:
case "$target" in
"msm8960") <----- on the CM10.2 12/3 nightly this is found on line 106
5. under those lines put the following line:
echo 2 > /proc/sys/net/ipv4/tcp_mtu_probing
6. save - you may have be admin to save.
7. adb push init.qcom.post_boot.sh /storage/sdcard0/
8. adb shell
9. su
10. mount -o rw,remount /system
11. cp /storage/sdcard0/init.qcom.post_boot.sh /system/etc/
12. reboot
13. profit
You can use the speedtest.net app to test this fix if you like. If your upload test completes you should be good to go.
Thank you. I have had the same problems and your MTU tip solved it.
The MTU probing also worked for me. Thank you very much!
I'm new to adb and can't find a good resource that helped me. I get to step 3 of fix 2 and can't figure out how to access the .sh file to edit it. Any help would be awesome.
So this doesn't work outright on the new Lollipop build for the N7, but it can easily be made to work. Unfortunately the MirrorEnabler app doesn't work on Lollipop yet, and the SQLite Installer app that would make it work hasn't caught up; it installs a non-executable binary that even when set with the correct permissions doesn't run. Credit goes to @r3pwn for finding the initial method for doing this.
UPDATE: MirrorEnabler had been updated for 5.0, and i've seen reports it works now. You can try it Here. Don't forget to thank @r3pwn if it works for you! Otherwise, this method still works, so take your pick. [emoji2]
UPDATE 2: The update of the crhomecast app supposedly supports this natively now on ALL devices, so this may not even be needed anymore. If someone who has not applied this fix can test that out (Has to be chromcast v 1.9.6 or higher) and report back in this thread, that'd be great.
So because I wanted my screen mirroring back, I dove in and made it work. Yes, there are 20 steps, but they are all outlined precisely. If done correctly this shouldn't take more than 5 minutes.
Here's how:
1) Be rooted on Android 5.0 (L)
2) Install chromecast app from play store - Link
3) Open the chromecast app and set up your chromecast device
4) Install busybox (I prefer sterricson version) - Link
5) Open Busybox app and click Install.
6) Install SQLite Editor (not free, but works great on L and worth the money if you like to tinker) - Link
7) get adb shell and issue the commands:
Code:
[email protected]:/ $ su
[email protected]:/ # setenforce 0
[email protected]:/ # getenforce
Permissive
[email protected]:/ #
DO NOT EXIT ADB YET!
8) Open SQLite Editor on your device and navigate to "Google Services Framework"
9) Under google services Framework, select "gservices.db"
10) In gservices.db select "overrides"
11) Click "+ NEW RECORD"
12) In the name field put (exactly as shown):
Code:
gms:cast:mirroring_enabled
13) In the value field put (exactly as shown):
Code:
true
14) Click Save
15) Click "+ NEW RECORD" again
16) In the name field put (exactly as shown):
Code:
gms:cast:remote_display_enabled
17) In the value field put (exactly as shown):
Code:
true
18) Click Save
19) Exit SQLite Editor
20) In your adb shell ( you didn't close it, right? ):
Code:
[email protected]:/ # am force-stop com.google.android.gsf
[email protected]:/ # am force-stop com.google.android.gms
[email protected]:/ # am force-stop com.google.android.apps.chromecast.app
[email protected]:/ #
If it worked you won't see any output from these three commands; You can now exit adb and disconnect your device.
If you see this:
Code:
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:298)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)
You didn't do step 7 correctly. Repeat step 7 and then try this step again.
That's it! NO reboot required! You should now be able to stream screen mirror to a chromecast device from your N7(2012) using Lollipop!
To test it, you should now be able to use your quick settings "Cast Screen" button, or the "Cast Screen" option from within the chromecast app.
Enjoy!
Nice guide !
Gesendet von meinem GT-I9195 mit Tapatalk
Nice guide.
Can confirm after following this guide casting from settings pull down is indeed working on lollipop N7 2012!!
Cheers!
Its works great! thank you!
I think Mirror Enabler only set the first one row, and it is the reason it stopped working on this tablet
Unfortunately not working with panasonic ptv3000
does this hack survive a Google Services Framework update, and is there really need to install chromecast app?
thanks
m52 power! said:
Unfortunately not working with panasonic ptv3000
Click to expand...
Click to collapse
Never said it would.
Sent from my leanKernel 3.11.3 powered stock 4.4.2 (NF9) SM-N900T
donpippo said:
does this hack survive a Google Services Framework update, and is there really need to install chromecast app?
thanks
Click to expand...
Click to collapse
Theoretically yes. It's just a data change. Add for having to install the chromecast app, you can try without installing it but i do believe it's required.
Sent from my leanKernel 3.11.3 powered stock 4.4.2 (NF9) SM-N900T
Wow. Yep. Works with Chromecast.
not working on my N7 [emoji26]
Edit: tried again with success. I started from 0 again. thank you
I would like to annonce that this method worked perfectly in the Moto X 2014 (Lollipop)... the only problem is, when i restart the phone it stops working and i need to do the whole process again..... Any way to fix that?
Thank you
toastido said:
So this doesn't work outright on the new Lollipop build for the N7, but it can easily be made to work. Unfortunately the MirrorEnabler app doesn't work on Lollipop yet, and the SQLite Installer app that would make it work hasn't caught up; it installs a non-executable binary that even when set with the correct permissions doesn't run.
So because I wanted my screen mirroring back, I dove in and made it work. Yes, there are 20 steps, but they are all outlined precisely. If done correctly this shouldn't take more than 5 minutes.
Here's how:
1) Be rooted on Android 5.0 (L)
2) Install chromecast app from play store - Link
3) Open the chromecast app and set up your chromecast device
4) Install busybox (I prefer sterricson version) - Link
5) Open Busybox app and click Install.
6) Install SQLite Editor (not free, but works great on L and worth the money if you like to tinker) - Link
7) get adb shell and issue the commands:
Code:
[email protected]:/ $ su
[email protected]:/ # setenforce 0
[email protected]:/ # getenforce
Permissive
[email protected]:/ #
DO NOT EXIT ADB YET!
8) Open SQLite Editor on your device and navigate to "Google Services Framework"
9) Under google services Framework, select "gservices.db"
10) In gservices.db select "overrides"
11) Click "+ NEW RECORD"
12) In the name field put (exactly as shown):
Code:
gms:cast:mirroring_enabled
13) In the value field put (exactly as shown):
Code:
true
14) Click Save
15) Click "+ NEW RECORD" again
16) In the name field put (exactly as shown):
Code:
gms:cast:remote_display_enabled
17) In the value field put (exactly as shown):
Code:
true
18) Click Save
19) Exit SQLite Editor
20) In your adb shell ( you didn't close it, right? ):
Code:
[email protected]:/ # am force-stop com.google.android.gsf
[email protected]:/ # am force-stop com.google.android.gms
[email protected]:/ # am force-stop com.google.android.apps.chromecast.app
[email protected]:/ #
If it worked you won't see any output from these three commands; You can now exit adb and disconnect your device.
If you see this:
Code:
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.onRun(Am.java:298)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
at com.android.commands.am.Am.main(Am.java:99)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:249)
You didn't do step 7 correctly. Repeat step 7 and then try this step again.
That's it! NO reboot required! You should now be able to stream screen mirror to a chromecast device from your N7(2012) using Lollipop!
To test it, you should now be able to use your quick settings "Cast Screen" button, or the "Cast Screen" option from within the chromecast app.
Enjoy!
Click to expand...
Click to collapse
I would like to annonce that this method worked perfectly in the Moto X 2014 (Lollipop)... the only problem is, when i restart the phone it stops working and i need to do the whole process again..... Any way to fix that?
Thank you
Anyone have any idea if this is necessary on the newer ver2 N7 after OTA?
MLT2004 said:
Anyone have any idea if this is necessary on the newer ver2 N7 after OTA?
Click to expand...
Click to collapse
Not sure after OTA update, but my son's N7 (2013 / gen 2) needed zero mods to get screen casting to work. It worked fine after installing the google N7 image from https://developers.google.com/android/nexus/images
Sent from either Maguro or Grouper via XDA free
On step 9) Under google services Framework, select "gservices.db" i get the error
An error occurred while opening the database. attempt to write a readonly database (code 776) while compiling: select * from sqlite_master where type in('table','view') order by name
How can i solve this?
theone_s_me said:
I would like to annonce that this method worked perfectly in the Moto X 2014 (Lollipop)... the only problem is, when i restart the phone it stops working and i need to do the whole process again..... Any way to fix that?
Thank you
Click to expand...
Click to collapse
Unknown. Don't own that device. Only tested on the n7 2012.
boriznl said:
On step 9) Under google services Framework, select "gservices.db" i get the error
An error occurred while opening the database. attempt to write a readonly database (code 776) while compiling: select * from sqlite_master where type in('table','view') order by name
How can i solve this?
Click to expand...
Click to collapse
No idea. You are rooted, right? Might see if remounting /system in read/write mode would help. Also make sure you granted root privileges to sqlite editor if it asked.
Sent from my SM-T320 using Tapatalk
Creds? Or at least link to my source code that you took this from.
r3pwn said:
Creds? Or at least link to my source code that you took this from.
Click to expand...
Click to collapse
I didn't steal any source code, since it's a guide and not an application. I will, however, credit you for finding the method initially, although your app did not work in Lollipop at the time.
toastido said:
I didn't steal any source code, since it's a guide and not an application. I will, however, credit you for finding the method initially, although your app did not work in Lollipop at the time.
Click to expand...
Click to collapse
I know you didn't "steal the code", but parts of this guide are letter-for-letter in the code of my app. And don't worry, Lollipop-compatible version coming soon.
EDIT: Thanks for adding that to the OP, but I found the ActivityManager commands to kill the required processes, too.
r3pwn said:
I know you didn't "steal the code", but parts of this guide are letter-for-letter in the code of my app. And don't worry, Lollipop-compatible version coming soon.
EDIT: Thanks for adding that to the OP, but I found the ActivityManager commands to kill the required processes, too.
Click to expand...
Click to collapse
D'oh. My bad. Updated OP to be a bit more generic.
Also, when you get the Lollipop compatible version ready, let me know and I'll gladly update the OP to point people that way for those who don't want to manually do this
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 ...