Related
1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
tsukisan said:
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
Click to expand...
Click to collapse
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
LiquidSolstice said:
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
Click to expand...
Click to collapse
Do you know if there is a compatible recovery for the garminfone? You can't flash a sholes recovery on a garminfone.
ROM Manager is useless for the Garminfone. There are no backups for it and its not a supported phone.
"adb reboot recovery" I'll have to give it a try as well, now that I am also rooted.
I did a similar process... used androot (temporary root) to get rootshell with superuser app from the market.
I downloaded su binaries separately, fired up adb shell,ran rootshell.
I manually copied su to /system/xbin then used gscript lite to script the following:
/system/xbin/su -c 'mount -o remount,rw /'
/system/xbin/su -c 'mount -o remount,rw /system'
/system/xbin/su -c 'cp /system/xbin/su /bin'
After that I added the script to my home screen and I have one click root.
The changes won't persist until the boot image is changed to and repacked.
Note that the rootshell app is useless after a cold boot or if moved. It just crashes.
The most interesting thing is looking through the startup scripts that run.
There are parts from 3 or 4 developers commented out that,!among other things, show what to set to root it permanently,and what looks like loading parts of. the os from the emmc or sdcard.
And the automated test scripts built in come complete with a Garmin test phone number that can be called as well as a full suite of functional and regression test scripts that can be used to validate all functions including the Garmin apps automatically. The daemon even loads itself on boot by default.
It looks like the build they used was a virtually unmodified developer build. Hell,the boot scripts even show what to change to make it run in the emulator. That is my next project (getting it up in emulation so I can test different modifications)... well,that and see what it will take to get the Garmin app running in the latest android. I see no point in upgrading to the latest os if I lose Garmin functionality.
Being that the devs left nice comments for damn near every line and wrote very clean and elegant scripts, i would be shocked if it took very long to get Garmin up, at least in emulation.
Fyi, since piracy is illegal, I want to make it clear that the Garmin portions of my rant refer only to regaining functionality in the latest os.
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
I don't know why people say the Garminfone is more locked down or unflashable than any other phone. It comes with a flash_image program on the phone that lets you specify a destination partition and an image file, it will flash /system/recovery.img on boot and all the boot scripts are commented for how to do things like boot off the emmc. The developers left a bunch of services in the boot scripts but disabled to do various functions.
Tim2246 said:
1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Click to expand...
Click to collapse
So I ran into a little speed bump here, I'll post what I've done thus far and maybe someone has some feedback...
1) Open the applications settings menu for Android OS and Check off the option "Uknown Sources" and then click on "Development" and make sure options "USB debugging" and "Stay Awake" are checked.
2) Download and install the "Universal Androot" apk. application installer using the web browser on your android phone.
3) Launch "Universal Androot" and use the drop down menu on the main screen and select the option that states, "Do not install Superuser" and then click the "Root " button, the application will run a few scripts and then confirm success.
4) Go the Android Market, and download and install the following application, "SuperUser" written by android software developer, chainsdd.
5) Once "SuperUser" is installed on your phone, launch the application and click, "Settings" on the top right hand corner of the application, it will bring you to a list of options, scroll to the bottom, and click on, "Su binary v original", this will download a zip file containing any updates. (You may have to click this several times if it fails, it will eventually download)
6) Go to the Android Market, and download, "Root Explorer (File Manager)" and install it, you may also download this package elsewhere...
7) Open "Root Explorer" and make sure you are in the / "root directory" of the unit and then click the "Mount R/W" button at the top.
8) Browse to /system/xbin/ and copy file "su" to /sdcard
This is where I have a problem, I can not locate /system/xbin/su
Here is some additional information that may be relevant
Garmin
Hardware R1.7
Software 4.0.12
Android
Firmware 1.6
Kernel version 2.6.29
hey all!
I've tried following the directions like 10 times and i keep coming up short..i can't seem to get root.. It's odd. Would anyone be kind enough to post a video, or clarify the directions needed in a step-by-step fashion?
Thanks in advance!
Does anyone in the know have a timeframe for when we might know how to get rid of the t-mobile animation that plays when the phone boots up? I'd like to replace all the bootscreens with some wicked cool custom stuff, but gotta knock that pink crap outta the way first.
merwin said:
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
Click to expand...
Click to collapse
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Spazmogen said:
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Click to expand...
Click to collapse
Are you sure the version of su in /system/xbin is the one that comes with superuser? You can check by using either a terminal app or adb,going into the xbin folder, and type ./su
You should get a superuser request. If not, then something was not done correctly.
Thanks for the reply.
but since 2.1 Eclair was installed today, it's a moot point:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is no SU in either /bin or in /system/xbin.
SuperUser by ChainsDD won't install the SU file, it keeps failing. Tried it 30x today.
Root Explorer only allows folders to be r/o now. So I am waiting on an update for that one.
How exactly did you get 2.1 on a Garminfone?
I have a Garminfone with 2.1 and all i did was download z4root from the market place and ran it and it seems to have given me a perminant root and i have no problems hopefully this helps you guys out it is a simple one click root unroot app.
Root is persistant. It survived a few battery pulls.
I have been able to get it into ADB REBOOT RECOVERY. A green droid guy with a yellow warning triangle appears.
One of the fellows in the Tmo forums claims to have gotten it into FASTBOOT menu options. If that is true, it would appear the boot loader is unlocked...
Garminfone 2.1 easily rooted...
I easily rooted my Garminfone 2.1 Eclair with z4root. It was one click and done with the options to temp or permanently root the phone it is also reversible.
Problem I am having is that I created an ext2 partition on my sd card but the phone doesn't recognize it. It was partitioned with "ubuntu livecd" with "gparted" partition manager. It also shows up in windows with "Mini Tool Partition Wizard 5" when the sd card is in a card reader attached to the pc.
Whats the next step? I want to move apps to the sd card. I have link2sd installed for this but can't figure out how to enable ext2 mount.
Also another good pc app to have if you trashed your sd card partitions is "Active Partition Recovery for Windows" works for all drives.
Issues - Rooting with Z4Root
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
z4root
Perseus71 said:
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
Click to expand...
Click to collapse
What exactly are you trying to do by rooting? Did you install SuperUser by ChainsDD? What app/file manager are you using? If you dont have this you won't be able to do anything. The apps you use for app/file management need to have root permissions or they will do nothing.
Mine rooted with z4root no problem and was able to remove all the fluff apps it shipped with that I didn't want. But this was only half of what I wanted to achieve. I haven't been able to move apps to sd, but I can't get ext2 to mount, not a problem because of the root I don't think.
What I have on my Garminfone 2.1
z4root
busybox (installed with z4root)
superuser
my backup root
uninstaller for root
super manager
Hope this helps.
Ok First off. Thank you very much for your time. It is greatly appreciated.
Well, Here's what I have done so far.
1. Downloaded and installed Z4Root from the Market.
2. Download and Install SuperUser by ChainsDD from the Market.
3. Ran Z4Root and first tried Temporary Root. That seemed to go fine until it was stuck after displaying the message ReBooting.
4. Next Tried Permanent Root Option after a Battery Pull. That asked me to turn on USB Debug. Did so and it seemed to go smoothly until that too was stuck with Rebooting message.
5. I tried the same Permanent Option after another Battery Pull. This time, it worked and the phone rebooted & came back. So I installed BusyBox from Market.
6. At this time I downloaded Titanium Backup. It complained not having root access. 7. So I started SuperUser and that showed an empty list under application tab. Went under Settings and hit the update. It failed but saved the Zip on my SD card.
8. I installed the Binary from Step 7 using Apps Manager. Tried SuperUser again. Still empty list for applications.
So there I am. I suspect I probably missed something somewhere. Possibly before doing Step 6 I should have done something. Can't seem to figure out.
Also earlier in this thread there was a mention that you will need to manually copy the binaris for SuperUser to certain specfic directory. Since it got installed successfully, do I still need to do it ?
I've finally created working adfree for Desire HD.
*** Probably there is something in ROM which overwrites hosts to default every one hour. I'm trying to track this. ***
Please comment.
Instructions:
1. Install visionary
2. Set visionary to run on boot
3. Extract files to /data/local/
Use Root Explorer or something like this, mount system partition as r/w and copy files from zip. You should have two files: /data/local/hosts and /data/local/visionary.sh
4. Set permissions of visionary.sh to executable
4. Restart phone
Ver. 0.9
Using my huge hosts file which is compilation from three sources plus my manual additions.
Is it for always have a root acces ? (Android logged)
NeoKiro said:
Is it for always have a root acces ? (Android logged)
Click to expand...
Click to collapse
It is for hiding ads.
Code:
4. Set permissions of visionary.sh to executable
How to set permissions executable?
Pacjonek said:
Code:
4. Set permissions of visionary.sh to executable
How to set permissions executable?
Click to expand...
Click to collapse
In Root Explorer hold your finger on file and choose option 'permissions'.
Probably You can try skip this step.
than33 said:
In Root Explorer hold your finger on file and choose option 'permissions'.
Probably You can try skip this step.
Click to expand...
Click to collapse
When I do that I don't get "permissions"... Trying to restart now without it...
E D I T: Just rebooted and ads are now gone in some apps Will see what will happen in one hour
ANOTHER EDIT: Thank you for this. Hope you can fix the one hour problem. Still need to wait for an hour to be over before I can check it.
/CK
So everything works? If so, thank you
Do you recommend we uninstall adfree app when using this?
Uninstalled but still not blocking ads in apps for me, e.g. in alchemy
The ads came back a few mins later... So guess you didn't quite break the code yet
/CK
Does this method not work with the temp root?
1. Search for Adfree Android on the market
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
10. Reboot your phone and enjoy adfree android.
this is what i used on my legend was hoping it would be as easy, :\
I think it might be better to use 0.0.0.0 instead of 127.0.0.1
With 127.0.0.1 it will attempt to connect to itself and wait until it times out, but with 0.0.0.0 is will stop straight away since it's an invalid address.
noobdeagle said:
Does this method not work with the temp root?
1. Search for Adfree Android on the market
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
10. Reboot your phone and enjoy adfree android.
this is what i used on my legend was hoping it would be as easy, :\
Click to expand...
Click to collapse
on the DHD we don't have a custom recovery nor write access to /system atm so this won't work
Strangely enough my Ad-Free works fine without the need of this.
0.0.0.0 worked for me.. cheers
Hey guys, I have a similar thread to this running on both CyanogenModForums and TypoPhile, but it seems as though I'm not going to find the help I need.
When I go to replace the fonts, I use two different methods. Both have ended in a bootloop for me as of 7RC2. I even know why the bootloop is happening, I just have no idea how to fix it.
The first method is in the terminal. For this to work, you need root (obviously), busybox, a terminal emulator and the fonts:
su
mount -o remount /dev/block/mtdblock4 /system
busybox cp /sdcard/Fonts/* /system/fonts
mount -o ro,remount /dev/block/mtdblock4 /system
sync
reboot
Unfortunately, the second mount command fails. It throws the error: filesystem is busy (not an exact quote because I don't really want to reboot to recovery again right now). Because it never remounts as r/o, the writing never gets done correctly and the system bootloops.
The second method is through Root Explorer.
I mount /system as r/w and then proceed to copy my fonts over (I've tried both using multi-select and copying one-by-one). Then, when I click mount R/O, I get the same problem. It won't remount. Therefore, same thing happens and bootloop ensues upon reboot.
Though I cannot imagine that it would matter, the fonts I am trying to use are as follows:
Liberation Sans => Droid Sans (Rg, Bd)
Terminus => Droid Sans Mono
Linux Libertine G => Droid Serif (Rg, It, Bd & BI)
I say that it shouldn't matter because this is exactly what I had for a very long time on 6.1.
I suspect that the problem may be coming from the fact that since 2.3, Android changed how the /system/fonts folder is setup, and I'm not sure how to handle the changes. If anyone is familiar at all with this, I would much appreciate any and all help you can send my way!
Bump. Please guys, any ideas are welcome. I really want to get to the bottom of this. Typographers are people too!
Same here, anyone has found something ?
ok I found that on CM7 forum :
Method 1: The Terminal Emulator
For this, you need root (obviously), busybox, a terminal emulator, ROM Manager and your fonts: They must already be renamed to which fonts you want them to replace (e.g., you could rename LiberationSans to DroidSans in order to use LibSans instead. For easiness, don't have any spaces in your pathname)
Step 1:
su
mount -o remount /dev/block/mtdblock4 /system
busybox cp /sdcard/[Font Dir]/* /system/fonts #Replace "[Font Dir]" with where ever you put your fonts (minus the "")
mount -o ro,remount /dev/block/mtdblock4 /system
sync
Step 2: If the second mount command does not work, try "umount -f /dev/block/mtdblock4" without the quotes. If that doesn't work, then you just have to hope that it will work anyways. If the second mount command succeeds, then you're done. It worked and your phone should now be using the new fonts. Skip to Method 1 > Step 4.
Step 3: Next, go into ROM Manager, and press the "Fix Permissions" option. Wait for it to finish going through everything, and then reboot. If your device bootloops, then something went wrong that ROM Manager's Permissions Corrector couldn't catch. In this case, I strongly recommend purchasing Root Explorer and giving it a go because Method 2 hasn't ever failed for me.
Step 4: If everything worked fine, then your fonts will already be used by the system (you don't even need to reboot!). However, if you now plan to backup your ROM, make sure that you reboot once first to make sure that the fonts survive and your system doesn't bootloop upon reboot.
Method 2: Root Explorer (Recommended)
For this method, you need root, possibly busybox (but I'm actually not sure about that), Root Explorer, ROM Manager and the fonts setup the same way they would have been for Method 1.
Step 1: Enter into Root Explorer and navigate to the fonts folder on your sdcard that has all of the renamed fonts. Press Menu > Multi-Select and select all of the fonts you wish to use. Then press "copy."
Step 2: Next, navigate to /system/fonts/ and press "Mount R/W" at the top of the screen. Press "Paste."
Step 3: Now comes the tedious part, long-press each file you replaced individually and select "Permissions." The permission set you want for each of these files is "r-xr-xr-x." So the first and last column should all be checked and the middle column should be empty. You can try to press "Mount R/O" at the top of the screen, but if it won't change, it will still be okay (It's not ideal, but it's happened to me, and it worked fine).
Step 4: Next, go into ROM Manager and hit the "Fix Permissions" option. Wait for it to go through everything and then "Voila!"
Step 5: If everything worked fine, then your fonts will already be used by the system (you don't even need to reboot!). However, if you now plan to backup your ROM, make sure that you reboot once first to make sure that the fonts survive and your system doesn't bootloop upon reboot.
Hello,
the Main XDA Page had a tutorial on how to disable the Google Assistant.
Step 1: Root
Step 2: Change build.prop
All you need to do is edit build.prop with the following change, reboot, and clear Google App data and you’ll no longer be greeted with the Google Assistant.
Change
Code:
ro.opa.eligible_device=true
to
Code:
ro.opa.eligible_device=false
Click to expand...
Click to collapse
But somehow I am stuck with how to change build.prop.
- With adb pull I can get the file, but I can't push it, I get the message "failed to copy 'build.prop' to '/system/build.prop': couldn't create file: Permission denied"
- I can't do adb root, I get the Message "adbd cannot run as root in production builds"
- With Total Commander I can't change the File as TC can't mount system with RW.
It would be great to know how to disable the Google Assistant, I anyway don't use it.
Cheers
I was able to mount as RW with ES File Manager (with root installed on the phone), they have a root browser option built in that is off by default. Enable it and select the mounts you want as RW and edit away. I used this to edit the build.prop and bootanimation
Tnx, worked smooth! Assistant no more
I'm guessing that we will need to be able to use TWRP to mount /system in order to modify the build.prop through ADB, that's what was required for Nexus without rooting.
Current as of March 29, 2018.
I've been saving this for a rainy day and it's raining at my house today I have been with XDA for about a year and a half now. I made a list of several goals I wanted to accomplish, mainly to do so without root. Though I have been successful at many tricks and hacks on these tablets WITHOUT root, sometimes, no matter how hard you try, some things can't currently be done without it. One of the goals I set was activating Android's stock Daydream screensaver. This is something that was built into Android and is a feature that is greatly underappreciated and many people just don't know it exists. It's also a feature Amazon blocks us from using. Another goal was to find a way to change the lock screen wallpapers after you got rid of Amazon Photos.
After several weeks of reading and researching, I finally discovered a working way to edit the framework and successfully install it back onto at least two of the Amazon tablets I own. In doing so I discovered how Amazon blocks the use of certain features and settings and in some cases, have been able to reverse their code and replace it with values that activate those things. As you can see in the screenshot below, the Daydream screensaver feature is installed onto the tablet. Using Activity Launcher, tap the top left pull down menu and select 'all activities. Scroll until you see the settings option and tap it. Then scroll until you see 'Daydream'. That's as far as you can go. If you tap it, the display settings is what pops up. Furthermore, if you disable or delete Amazon Photos, and you're stuck with their lock screen wallpapers for the rest of time, until now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In this case the settings don't redirect to another app like setting your lock screen wallpapers, which until now, required Amazon Photos to change. They simply take advantage of the framework, and block the use of the Daydream function through settings within it. That setting, among many more settings, are all allowed to be blocked and are options Android provides to manufacturers and service providers when they purchase the rights to a copy of an Android OS.
Today I am proud and very happy to announce through modding the FireOS framework on the Fire 7 and HD 10, I have successfully activated Android's stock Daydream screensaver, while at the same time, not destroying the fabric of FireOS. I have also found a way for you to once and for all, change your lock screen wallpapers WITHOUT the use of Amazon Photos.
In this TWO PART guide, I'll show you how to enable the use of the Daydream screensaver, install the 'Colors' add-on and show you how to change your lock screen wallpapers. The best part about Daydream, I have been able to track down the proper APK for Android's stock 'Colors' screensaver, also known as 'BasicDreams' and as you can see in the screenshot below, it surprisingly worked on both the Fire 7 and HD 8
The hardest part of all this, once Daydream was activated, was finding the proper APK to get this working. It took me about a week or more to track down the closest version of the 'BasicDreams' APK for our version of Lollipop and I provide it to you today as well. Follow the guide below on how to get Daydream activated and in part two, learn how to change your lock screen wallpapers WITHOUT the use of Amazon Photos.
*****WARNING*****
Editing or modifying the system framework can be very damaging to your device. I have spent an extensive amount of time studying it and ways to edit it. I am writing this guide now because I believe this method is the safest way to edit the framework without damaging your tablet. With that said, your results might not be the same. As such, from this point forward in this guide, I cannot be responsible for any damage that may occur to your device. Please only continue if 1) You are willing to risk a possible brick 2) If you are willing to flash back to the last version of FireOS that your tablet was on in case a brick does occur.
Part 1: Enable 'Daydream' Screensaver
Requirements:
- Rooted Amazon Fire 7 or HD 10.
- Windows PC with ADB installed.
- APKtool (Please note you need to install Java version 7 or greater in order to use APKtool).
- 7-Zip
- Proper 'BasicDreams' screensaver APK, provided at the bottom of this post.
- Notepad++
- ADB insecure
- Patience.
Instructions:
1. On your PC, Download and install 7-Zip, Java (INSTALL JAVA BEFORE YOU INSTALL APKTOOL!!), APKtool and Notepad++ and ADB Insecure, if you haven't done so already, from the links provided above. Download links and install instructions for APKtool can be found here. On your Fire 7 or HD 10, download and install ADB insecure from the link provided above. For APKtool, I recommend you create a folder named 'apktool' in your C:\ directory, as seen in the screenshot below:
2. Once you've installed those two things, plug your tablet into your PC and make sure you have ADB debugging enabled in developer options. (Tap settings, device options, tap serial number 7 times, tap developer opeions and enable ADB). Open an ADB window. We need to get a copy of your framework package by typing the command below into your ADB window and pressing enter. This command assumes you installed APKtool into your C:\ directory:
Code:
adb pull /system/framework/framework-res.apk C:\apktool
3. Now on your PC, you need to navigate to your APKtool folder in C:\. When the window opens, open a command window by holding down shift and right clicking on the APKtool folder window and select 'open command window here'. An example of how that command window would look is posted below:
4. Now we need to install the framework APK into APKtool so it's able to decompile it. In the APKtool command window, type the following command:
Code:
apktool if framework-res.apk
5. Time to decompile the framework so we can look inside of it and make ONLY one edit. Yes that's all it takes is one edit. Amazon only blocks out the Daydream screensaver by using one word. Type the following command in the APKtool window to decompile the framework APK:
Code:
apktool d framework-res.apk
6. Now go back to your APKtool folder on your PC. Another folder should have been created inside the APKtool folder. The folder will be called 'framework-res'. Open up the folder and double click the RES folder. Scroll down until you see the folder named 'values' and double click it. You then should then see a list of XML files, like in the screen shot posted below:
7. Right click on the file named 'bools.xml' and select 'Open with Notepad++'. Slowly scroll the page and look for the configuration setting as seen below. On my Fire 7 the configuration is on line 98:
Code:
<bool name="config_dreamsSupported">false</bool>
8. In the configuration it will say 'false'. Change it to 'true' (no quotation marks) so it looks like this:
Code:
<bool name="config_dreamsSupported">[B]true[/B]</bool>
9. Then save the file by clicking on the floppy disc icon at the top left of Notepad++. DO NOT MAKE ANY OTHER EDITS!! You can now close Notepad++ and open the command window for APKtool again. We have to recompile the framework. Do that by typing the following command into the APKtool command window:
Code:
apktool b framework-res
10. You might get an error or three as the APK recompiles. As long as APKtool builds the APK, ignore the errors. If any pop up during the rebuild process, at most there will be 3 that will say something about an 'ellipsis' and time formatting. They don't mean anything as far as I can tell. If there are more errors which are fatal for the framework APK building, APKtool will not complete the build process. If the build process successful, move onto the next step. Otherwise please repeat the process from step two and make sure you don't edit anything else.
11. Back on your PC, bring up the APKtool folder again. Open the 'framework-res' folder. A few new folders have been created by APKtool. The only one you need to worry about is 'dist'. Double click that folder. This is where APKtool puts rebuilt APKs. Right click on the 'framework-res.apk' file and choose '7-Zip' and 'open archive'. DO NOT CHOOSE UNZIP!!! (Unzipping or decompiling the APK improperly will result in undesirable consequences when you install it back on your tablet.)
12. A 7-Zip window will open up listing a few files. You can make it a little smaller and move it out of the way, but don't minimize it. Back at the APKtool folder (you should still be inside the dist folder), click the back or arrow up button until you are back in the main APKtool folder. Right click your OLD framework-res.apk file and select 7-Zip and 'open archive'. Again do NOT unzip or decompile the APK. You can make the 7-Zip window that opens, smaller if you like, but now make sure the two 7-zip windows are side by side, noting which one is the OLD and which is the NEW archive (the one with 'dist' in the directory is the NEW APK. See below):
13. Highlight the 'res' folder in the 7-Zip window containing the NEW archive. Now drag the 'res' folder from the new archive into the 7-Zip window containing the OLD archive. A window will appear asking if you "really want to copy the folder". Click yes. Now highlight the 'resources.arsc' file in the NEW archive window and then drag it to the OLD archive window and click yes when it asks you if you really want to copy it. You can now close both 7-Zip windows and navigate back to your APKtool window.
14. Now it's time to install the modified framework. Open ADB Insecure if you've already installed it. Grant it SuperUser rights and check the box next to "enable insecure adbd" and open an ADB command window. In order for this next step to be successful, you MUST have insecure adbd enabled. When you're ready, type the command:
Code:
adb remount
15. The window should reply with 'remount succeeded" as seen above. Now we are going to install the framework to the system. Don't worry about setting permissions for the framework. Because we are pushing the framework into the system via ADB and because the framework-res APK was already a system app, ADB will automatically set the proper permissions for the framework APK. This is the moment of truth! Type the following command below (this is assuming you installed APKtool into the C:\ directory). Once installed, within 5-10 seconds some buttons may appear different or be a different color. This is normal and generally signals a successfull installation. If within 5-10 seconds your tablet automatically reboots itself, that generally signals a soft brick. Here we go! Type the commands below, into your ADB command window one at a time:
Code:
adb push C:\apktool\framework-res.apk /system/framework/framework-res.apk
adb reboot
16. If your tablet rebooted successfully, congrats, you just activated Daydreams Before we install the Colors screensaver, go ahead and navigate to your display settings on the tablet. You'll notice a new tile, 'Daydream'. Tap on it and a new window opens. From here you can use the stock desk clock app for the screensaver, install 'Colors' or choose the Amazon screensaver. For Colors: Download the attached BasicDreams APK at the bottom of this post, but do NOT install it. Place the APK into your ADB folder. When done type the following command below. Again no need to worry about setting permissions to the APK as ADB will do it for us:
Code:
adb push BasicDreams.apk /system/app
adb reboot
17. When your tablet reboots, download and install Activity Launcher if you haven't done so already. Tap the pull down at the top left and select all activities. Scroll down until you see SystemUI and tap on it, then tap 'Dessert Case'. To stop the screensaver, tap and pull up near the navigation bar and swipe it closed. Navigate to your display settings again and tap on Daydream. You now have 3 screensavers!!! Tap the three dots at the top right for options on when the screensavers should turn on aka 'daydream'. You can also tap 'start now' to preview them.
So far, these are the only three I have been able to get working. I am still trying to get Photo Table to work, but I am pretty sure Gapps needs to be installed, and I haven't gotten that far to test it. I've tried other screensavers from the Play Store with no luck unfortunately. However if anyone finds anymore working ones, please post your results/finds
Thanks everyone who followed. This makes me quite happy to see this unique feature on these tablets as they are deserving of such a thing. It's disappointing Amazon lets such a great thing go to complete waste. This maybe an old feature, but a very cool and underappreciated one. I hope everyone enjoys this as much as I did unlocking it. I'll be honest; I never thought I would be able to learn basic coding. At least not enough to get this far and accomplish the things I have. Thanks for the support everyone
Watch for part two in the next couple days: Change your lock screen wallpapers...WITHOUT using Amazon photos!!
Part 2: Change your lock screen wallpapers
This guide will teach you how to change all of the stock FireOS wallpapers. This is much easier than activating Daydreams and you don't need Java or Apktool to make the edits.
This guide is mainly for individuals who want to or already disabled/uninstalled Amazon Photos. When you disable or uninstall Amazon Photos, you lose the ability to change your lock screen wallpapers. This guide will work for both the Fire 7 and HD 10.
Requirements:
- ROOTED Fire 7 or HD 10
- 7-Zip
- ADB insecure
- Your choice of any 7 wallpapers
- Windows PC with ADB
Instructions:
IMPORTANT: Make a copy of your SystemUI.apk at /system/priv-app/SystemUI and place it somewhere on your PC in case you have an unfavorable result, you won't have to reset your device.
1. Download and install 7-zip.
2. First we need to get a copy of your SystemUI. Plug your tablet into your PC, making sure ADB debugging is enabled in the developers menu. Open an ADB window on your PC and type the command below (the actions of moving the SystemUi.apk around should only be done via ADB. Never copy and past an APK from one device to another if you intend on editing it.)
Code:
adb pull /system/priv-app/SystemUI/SystemUI.apk
3. Running the above command will have resulted in making a copy of your SystemUI.apk and then placed it on your PC, into the same folder as ADB.
4. Create a folder on your desktop for the 7 wallpapers you desire. You can pick 7 different ones, or use the same wallpaper 7 times, but you can't choose any more or any less of a quantity. Putting anymore or less in the SystemUI will cause the tablet to bootloop. I have a collection of about 200 stock Android wallpapers from the first version, all the way to Nougat. It doesn't matter what size they are because you'll be resizing them anyways.
5. Once you've chosen your wallpapers, you'll have to resize them. For this guide I will be using Microsoft Paint. Navigate to the folder containing your new wallpapers and open the first one in Paint. Click the 'Resize' button at the top left of the screen, select Pixels and make sure the 'maintain aspect ratio' box is UNCHECKED. Your wallpaper MUST be the same size/resolution as Amazon's. Enter the values as listed and pictured below:
Code:
Horizontal: 1920
Vertical: 1200
6. Save the wallpaper as a .jpg. The name doesn't matter right now because we will be renaming them. If you are going to use 7 different wallpapers, you need to make a copy of the wallpaper you just resized. Open it in paint and again click resize, select Pixels and make sure 'maintain aspect ratio' is UNCHECKED. Reverse the dimensions:
Code:
Horizontal: 1200
Vertical: 1920
7. If you want to keep the same wallpaper on your lock screen all the time, repeat the above step with copies of the same wallpaper. Regardless if you use the same ones or different ones, you will have 14 wallpapers in the folder when done.
8. Navigate back to your ADB folder and locate SystemUI.apk. Right click on it and select the '7-Zip' option then 'open archive'. DO NOT UNZIP, EXTRACT OR DECOMPILE THE APK! Resize the window so you have a good amount of space to open the wallpaper folder we just made. Place the windows next to each other.
9. In the 7-zip, SystemUI archive window, double click on the 'res' folder then locate and double click the 'raw-hdpi-v4' folder. This is the location of the Amazon's default lock screen wallpapers. In your custom, wallpaper folder, you need to rename each wallpaper to match the names of Amazon's. It's important you do this step and that the names match. Otherwise when you reinstall the SystemUI, it will crash.
10. When you're done, in your custom wallpaper folder, click on 'Edit' a the top and 'select all'. Click on any of the wallpapers but don't let go! Start to drag them over to the 7-zip SystemUI window. Make sure you have all of them, then let go. When the box pops up asking you if you want to overwrite the other wallpapers just click yes. Close both windows and open an ADB window again.
11. Download and install ADB Insecure from the link at the beginning of this post. Open it and grant it root access if you don't have SuperSU set to automatic. Check the box to put ADB into insecure mode. In the ADB window, type the following commands, pressing enter after each one.
Code:
adb remount
adb push SystemUI.apk /system/priv-app/SystemUI/SystemUI.apk
adb reboot
12. That's all. If successful, your tablet will reboot and your custom lock screen wallpaper(s) should appear. If unsuccessful, your tablet will reboot, but with no SystemUI active. I'll write a small guide on recovering from a SystemUI crash without reflashing firmware if anyone has a problem. Until then enjoy your wallpapers. Just remember you have to repeat this guide each time you want to change them. Until I can figure out how Amazon Photos has such control over the lock screen, this is the only way to change your lock screen wallpapers if you uninstall Amazon Photos. Thank you for following everyone!
Definitely looking forward to trying this!
Still waiting for part 2. Also wondering if it's possible to modify the framework so that we can customize the power options.
oscarcx said:
Still waiting for part 2. Also wondering if it's possible to modify the framework so that we can customize the power options.
Click to expand...
Click to collapse
Got a little busier this weekend than I predicted. I will try to get part 2 up today or tonight.
Is it possible? Yes. However I'm having a difficult time with it. Those settings are a bit scattered and butchered so I'm having trouble figuring out which xml to edit. Amazon created their own xml files to override some of androids. It also doesn't help that a lot of values from the bools are repeated then scattered across various system apps. I know one issue is the power profile. Amazon did a good job of butchering that setting and it's proving difficult reconstruct. In other words the power profile is almost non existent.
DragonFire1024 said:
Got a little busier this weekend than I predicted. I will try to get part 2 up today or tonight.
Is it possible? Yes. However I'm having a difficult time with it. Those settings are a bit scattered and butchered so I'm having trouble figuring out which xml to edit. Amazon created their own xml files to override some of androids. It also doesn't help that a lot of values from the bools are repeated then scattered across various system apps. I know one issue is the power profile. Amazon did a good job of butchering that setting and it's proving difficult reconstruct. In other words the power profile is almost non existent.
Click to expand...
Click to collapse
No need to hurry. These are great discoveries so take your time to write the tutorial
In my opinion, your tutorial is kind of way too detailed. I know it's great for tech newbies, but by simplifying it a little bit could effectively save your time.
For the power option, if it's way too hard to customize it, maybe spending time on other stuff will be a better choice.
Anyways, thanks for your amazing work!
oscarcx said:
No need to hurry. These are great discoveries so take your time to write the tutorial
In my opinion, your tutorial is kind of way too detailed. I know it's great for tech newbies, but by simplifying it a little bit could effectively save your time.
For the power option, if it's way too hard to customize it, maybe spending time on other stuff will be a better choice.
Anyways, thanks for your amazing work!
Click to expand...
Click to collapse
I think it's more of putting pieces back in the right spots, for example, settings fragments. Some things are directed with Amazon's fragments and it's just a matter of finding the right android fragment and replacing it. In other cases, Amazon blocks out some features in an 'assets' file. Some things are also set in smali files/java and I know very little about smali, so have been reading up on that. Sometimes the fix is just a simple word change like the DayDream. I also recently discovered other settings or at least "project defaults " set by mediatek. I'm able to change some of those and supposedly add them to the build prop for more activation, but so far I haven't seen a difference.
Change your lock screen wallpapers everyone Part 2 is out!
DragonFire1024 said:
This guide will teach you how to change all of the stock FireOS wallpapers. This is much easier than activating Daydreams and you don't need Java or Apktool to make the edits.
(........................)
Thank you for following everyone!
Click to expand...
Click to collapse
Brilliant! Never thought of replacing those default wallpapers. At least this is a temporary solution.
I am wondering how the lockscreen wallpaper works and correct me if I am wrong. The app called "Special offer" is included in stock Fire OS and it has the ability to either change the wallpaper or overlay the wallpaper. Maybe it's a good idea to start from there but I am not sure about the legitimacy issue.
The lockscreen itself is weird though. Using Gravity Box, I can change some of the features but not all of them. Someone here told me that the lockscreen is deeply integrated into Fire OS.
oscarcx said:
Brilliant! Never thought of replacing those default wallpapers. At least this is a temporary solution.
I am wondering how the lockscreen wallpaper works and correct me if I am wrong. The app called "Special offer" is included in stock Fire OS and it has the ability to either change the wallpaper or overlay the wallpaper. Maybe it's a good idea to start from there but I am not sure about the legitimacy issue.
The lockscreen itself is weird though. Using Gravity Box, I can change some of the features but not all of them. Someone here told me that the lockscreen is deeply integrated into Fire OS.
Click to expand...
Click to collapse
There's a line in the build.prop file called "curlockscreen" with a value of 1. I have no idea exactly what it's for, but it might be related to disabling and/or modifying the lock screen.
lakitu47 said:
There's a line in the build.prop file called "curlockscreen" with a value of 1. I have no idea exactly what it's for, but it might be related to disabling and/or modifying the lock screen.
Click to expand...
Click to collapse
Just did a quick search on it and looks like it's the default lockscreen style
I decided to give Part 1 a try.
I got up to step 15 successfully, including having the Daydream tile.
I'm presuming that — to install BasicDreams.apk (in step 16) — you need to have another round of "adb remount"
Unfortunately, although "adb remount" worked when I did it the first time, trying to do it now results in an error:
remount of system failed: Invalid argument
remount failed
Trying to copy (with the "adb push BasicDreams.apk" command) results in an error:
adb: error: failed to copy '[PATH]/BasicDreams.apk' to '/system/app/BasicDreams.apk': remote Read-only file system
(Unsurprisingly, this is the same error if I try to do the "adb push BasicDreams.apk" thing without trying "adb remount")
In all cases, I'm re-enabling the "Enable insecure adbd" option from the "adbd insecure" app.
Any ideas how to fix this?
GamerOfRassilon said:
I decided to give Part 1 a try.
I got up to step 15 successfully, including having the Daydream tile.
I'm presuming that — to install BasicDreams.apk (in step 16) — you need to have another round of "adb remount"
Unfortunately, although "adb remount" worked when I did it the first time, trying to do it now results in an error:
remount of system failed: Invalid argument
remount failed
Trying to copy (with the "adb push BasicDreams.apk" command) results in an error:
adb: error: failed to copy '[PATH]/BasicDreams.apk' to '/system/app/BasicDreams.apk': remote Read-only file system
(Unsurprisingly, this is the same error if I try to do the "adb push BasicDreams.apk" thing without trying "adb remount")
In all cases, I'm re-enabling the "Enable insecure adbd" option from the "adbd insecure" app.
Any ideas how to fix this?
Click to expand...
Click to collapse
Make sure box is checked in adb insecure. After a reboot, you need to check the box again.
oscarcx said:
Just did a quick search on it and looks like it's the default lockscreen style
Click to expand...
Click to collapse
Yes but broken up internally. I do have a fix but I have to consult a developer before I announce it as it uses a piece of software from another rom.
GamerOfRassilon said:
I decided to give Part 1 a try.
I got up to step 15 successfully, including having the Daydream tile.
I'm presuming that — to install BasicDreams.apk (in step 16) — you need to have another round of "adb remount"
Unfortunately, although "adb remount" worked when I did it the first time, trying to do it now results in an error:
remount of system failed: Invalid argument
remount failed
Trying to copy (with the "adb push BasicDreams.apk" command) results in an error:
adb: error: failed to copy '[PATH]/BasicDreams.apk' to '/system/app/BasicDreams.apk': remote Read-only file system
(Unsurprisingly, this is the same error if I try to do the "adb push BasicDreams.apk" thing without trying "adb remount")
In all cases, I'm re-enabling the "Enable insecure adbd" option from the "adbd insecure" app.
Any ideas how to fix this?
Click to expand...
Click to collapse
How about,
adb shell
su
mount -o rw,remount /system
Instead of adb remount? It looks like an error in adb remount.
Supersonic27543 said:
How about,
adb shell
su
mount -o rw,remount /system
Instead of adb remount? It looks like an error in adb remount.
Click to expand...
Click to collapse
You can do that I suppose. I haven't tried. I side stepped that method because adb will make sure the APK has the permissions assigned properly amongst other anomalies I've come across. These are old APKs from original sources I work with. Most of the time i keep them safely inside their zipped ROM and sometimes you only get so many uses out of them if you move them around outside the system too much without proper permissions. In a matter of speaking they get lost and stop working. So I try to minimize the amount of time they remain away from home. With that said, it shouldn't be a problem.
Sent from my Samsung Galaxy S4 using XDA Labs
To follow up here:
1) I was certain I re-enabled adb insecure.
2) I tried "mount -o rw,remount /system", and got a similar error: "mount: Invalid argument". I also tried a command that worked in the past (that I'm pretty sure is doing the same thing): "mount -w -o remount /system" (no quotes, obviously), and also got the "mount: Invalid argument" error.
3) The error I had in this circumstance was similar to one I had on an unrelated matter regarding getting FlashFire working.
What I suspect is that somehow /system gets tired of being written to, and it "locks me out" for some reason. (There are two points when I have traditionally made use of "mount -w -o remount /system" — when I copy over the initial /system image via "dd if=/sdcard/system.img of=/dev/block/mmcblk0p13; sync" and when I disable OTA updates with "mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_" )
Another possibility is that I had somehow made a mistake in following this tutorial originally, typing "adb push [SOURCE]\framework-res.apk /system/framework-res.apk" instead of "adb push [SOURCE]\framework-res.apk /system/framework/framework-res.apk"
I deleted the errant framework-res.apk from /system, but I wonder if that somehow tripped up some kind of "don't muck with this" flag that wouldn't let me remount it.
4) Speaking of which, are you sure about this command in Step 16?
adb push BasicDreams.apk /system/app
Click to expand...
Click to collapse
I can't get it to work. In fact, if I use a file browser to go to /system , I just have a non-folder file named "app" that happens to be the same size as BasicDreams.apk . . .
I reflashed my /system and confirmed that I don't seem to have a folder named "app" in /system , so I can't quite figure out what that command is doing . . . Does it need to be:
adb push BasicDreams.apk /system/priv-app
? (I have a 2017 HD10, if it matters.)
5) For my second attempt, I tried to do as "clean" a re-install of my system as I could, avoiding the two instances of when I would remount /system in the past (flashing a straight system.img extracted from an update and freezing the OTA app with Titanium Backup). This time, remounting worked both times, as did the rest of the procedures (with the exception of the "BasicDreams.apk" problem, directly above).
GamerOfRassilon said:
To follow up here:
1) I was certain I re-enabled adb insecure.
2) I tried "mount -o rw,remount /system", and got a similar error: "mount: Invalid argument". I also tried a command that worked in the past (that I'm pretty sure is doing the same thing): "mount -w -o remount /system" (no quotes, obviously), and also got the "mount: Invalid argument" error.
3) The error I had in this circumstance was similar to one I had on an unrelated matter regarding getting FlashFire working.
What I suspect is that somehow /system gets tired of being written to, and it "locks me out" for some reason. (There are two points when I have traditionally made use of "mount -w -o remount /system" — when I copy over the initial /system image via "dd if=/sdcard/system.img of=/dev/block/mmcblk0p13; sync" and when I disable OTA updates with "mv /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA/DeviceSoftwareOTA.apk_" )
Another possibility is that I had somehow made a mistake in following this tutorial originally, typing "adb push [SOURCE]\framework-res.apk /system/framework-res.apk" instead of "adb push [SOURCE]\framework-res.apk /system/framework/framework-res.apk"
I deleted the errant framework-res.apk from /system, but I wonder if that somehow tripped up some kind of "don't muck with this" flag that wouldn't let me remount it.
4) Speaking of which, are you sure about this command in Step 16?
I can't get it to work. In fact, if I use a file browser to go to /system , I just have a non-folder file named "app" that happens to be the same size as BasicDreams.apk . . .
I reflashed my /system and confirmed that I don't seem to have a folder named "app" in /system , so I can't quite figure out what that command is doing . . . Does it need to be:
adb push BasicDreams.apk /system/priv-app
? (I have a 2017 HD10, if it matters.)
5) For my second attempt, I tried to do as "clean" a re-install of my system as I could, avoiding the two instances of when I would remount /system in the past (flashing a straight system.img extracted from an update and freezing the OTA app with Titanium Backup). This time, remounting worked both times, as did the rest of the procedures (with the exception of the "BasicDreams.apk" problem, directly above).
Click to expand...
Click to collapse
I am not too sure why this is happening. I presume you edited the framework-res.apk? If so, use a root explorer, I use the actual Root Explorer, and navigate to /system/priv-app and create a folder named BasicDreams. If using root excplorer, Long press the folder, tapp three dots at top right, tap permissions, set to 0755 (rwxr-xr-x). Place the APK in the internal storage of your tablet. Open your root explorer and go to your internal storage. CUT the APK FIRST to /system then CUT it to the BasicDreams folder in /system/priv-app you just made. When done, if using root explorer, long press the APK, tap three dots on upper right and tap permissions. set permissions to 0644 (rw-r--r--). Reboot then go to settings, display, and see the Daydream menu.
DragonFire1024 said:
I am not too sure why this is happening. I presume you edited the framework-res.apk? If so, use a root explorer, I use the actual Root Explorer, and navigate to /system/priv-app and create a folder named BasicDreams. If using root excplorer, Long press the folder, tapp three dots at top right, tap permissions, set to 0755 (rwxr-xr-x). Place the APK in the internal storage of your tablet. Open your root explorer and go to your internal storage. CUT the APK FIRST to /system then CUT it to the BasicDreams folder in /system/priv-app you just made. When done, if using root explorer, long press the APK, tap three dots on upper right and tap permissions. set permissions to 0644 (rw-r--r--). Reboot then go to settings, display, and see the Daydream menu.
Click to expand...
Click to collapse
I did edit the framework-res.apk, yes.
I jumped through all those hoops, it it is — indeed — working! (I interpreted the instructions as "Cut and paste into /system, then cut and paste it from /system into the folder on /system/priv-app" . . . is that because the file needs to "touch" /system to work correctly? And I just COPY/pasted the first time into /system, to keep the original backed up on my SD card.)
GamerOfRassilon said:
I did edit the framework-res.apk, yes.
I jumped through all those hoops, it it is — indeed — working! (I interpreted the instructions as "Cut and paste into /system, then cut and paste it from /system into the folder on /system/priv-app" . . . is that because the file needs to "touch" /system to work correctly? And I just COPY/pasted the first time into /system, to keep the original backed up on my SD card.)
Click to expand...
Click to collapse
It touches the system just as a precaution. I've read in places it a way for the system to better accept APKs as a system app when you force install it like this. I don't know if it's true, but when manually adding a file, i take this step as a just in case route.