Related
I'd like to change the wallpaper on the root u-tube home screen, but I don't see how one can access the internal folders. I'd like to be use adb push but I don't know the path for the 'Picture', or 'Wallpaper gallery Home' that are possible locations for adding the images.
You do mean the desktop wallpaper?
I'm boring. I just changed the default wallpaper to solid white.
In /system/framework/framework-res.apk
Replace /res/drawable-mdpi/default_wallpaper.png
To answer your original question: I don't know.
Thanks for the information; however being a complete beginner that does help me get a little bit closer to what I'd like to do but there is still much that I don't really understand. How do I access that location? And should I add my new image to the subfolder with a totally differently name, or should I rename the my image to that of the default.png and replace the old image?
If I adb push to the nook my image renamed to match the old wallpaper image, will that work?
still trying to replace home image in rooted Nook ST
I have a question for someone who knows more than I about android systems. Thanks to Thank Meter 78 who pointed out the file I need to change in order to replace the home image is in
/system/framework/framework-res.apk
and that I need to replace in that apk
/res/drawable-mdpi/default_wallpaper.png
Will the following procedure work properly without screwing up my newly rooted Nook?
Using Root Explorer I copied the 'framework-res.apk', and saved it to my Nook sd card. Then copied that apk file to my windows xp computer and changed the extension to 'zip' and unzipped it. The png file thus is available for replacement by another image of identical size and name.
Will it be correct for me to rename the modified .zip extenson file containing a new default_wallpaper.png file back to its original .apk extension, copy/paste it to the sd card, insert the sd card into the Nook, and the using Root Explorer to copy the apk file and paste it back to the drawable-mdpi folder where it will replace the nook apk (being sure that I change the r/o to r/w permission for the folder, and change it back after the replacement)?
Could there be adverse effects of the replacement?
My friends all call me Renate...
Yes, that procedure works, correcting for your typo.
Unzip, replace PNG, zip, copy back to /system/framework/framework-res.apk
You don't need to set it back to r/o. It's better/easier to just reboot, preferably with ADB.
You should always backup at reasonable intervals and before major changes.
Heck, I've bricked my Nook a dozen times.
Thanks Renate!
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Renate NST said:
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Click to expand...
Click to collapse
1) I thought the original question was about u-tube (I guess "Youtube" ;-))
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
The Media Scanner service is what scans.
Normally it is activated on insertion of an SD card.
It does not run continuously.
It ignores directories with file in it called ".nomedia"
The MediaScannerConnection can be used to request scanning of a single file.
Level 8 API (we're 7) can request scanning of multiple files.
It seems to turn its nose up at files and not put them in its database.
ajislav said:
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
Click to expand...
Click to collapse
Are you asking about having your own pics as screensavers?
I did that by connecting my NST to the PC, and creating a folder (one word name) under screensavers/ and copying the pics into that folder. It then shows up in the screensavers menu, and you can select it. The location from within the nook is /media/screensavers
--
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Renate NST said:
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Click to expand...
Click to collapse
Isn't their any way to repair the nooks MediaScanner? like, re-install it, clear the app data, copy another one in from another android 2.1 device? I don't understand why it isn't working, or why it can't be fixed. I've tried backing up the app and re-installing it, deleting the external db's, running media scan apps. Disabling it, re-enabling it...
Here are the steps I followed to change the wallpaper on my Kindle. Credit for this goes to Josepho1997 for the guide for the original Kindle Fire: http://forum.xda-developers.com/showthread.php?t=1765044&highlight=wallpaper
Disclaimer:
The risk of a bricked device or bootloop exists. To my knowlege there is no way to create a back up yet which makes recovery even harder. I am not liable for any damaged devices. Proceed at your own risk.
Things You'll Need:
Rooted Kindle
File Browser like ES File Explorer
7-Zip
Changing the Wallpaper:
1. Using ES File Explorer go to: /system/framework and copy (do not move!) framework-res.apk to your SD card.
2. Plug your Kindle into the computer and move the framework-res.apk (from SD card) to your computer and make a back up copy.
3. Use 7-Zip to open the one you intend to modify
4. Browse to \res\raw
5. Find the wallpapers named hi_xxx_p.jpg and hi_xxx_l.jpg. (These are the 1280x800 images, p are portrait images and l are landscape images. I am unsure what purpose the other images of different resolutions serve at this time).
6. Replace the .jpgs with the images you want, keeping the names exactly as they are. DO NOT delete any images. (I recommend replacing each image with the same resolution image for the best results).
7. Close 7-Zip and the new framework-res.apk will be saved, move this back to your SD card.
8. Open ES File Explorer. In the settings make sure you select "Up To Root", "Root Explorer" and "Mount File System".
9. Copy the framework-res.apk to /system.
10. Change the permissions to rw-r-r using ES File Explorer (this is critical, failure will cause a bootloop)
11. Move framework-res.apk to /system/framework. Let it replace the other file.
12. Reboot.
13. You will see your new wallpaper(s) when your Kindle reboots. To tidy up, go back into ES File Explorer and uncheck "Mount File System".
These are the steps I followed successfully but I caution anyone as it is risky. Follow them carefully and if you are uncomfortable or cannot afford to brick your device please wait until someone has developed a safer, easier method.
You can delete all of images (it'd result in a black no-background), and you can also add new images. Differently prefixed images (which you may also notice are of diff resolution) are for other devices.
ignoramous said:
You can delete all of images (it'd result in a black no-background), and you can also add new images. Differently prefixed images (which you may also notice are of diff resolution) are for other devices.
Click to expand...
Click to collapse
If you add new images, you need to renamed them correctly. I think in the id.xml(maybe string.xml), they have the wallpaper's name. If you put in a different name, it wont work. And you could edit the id.xml(maybe string.xml, I forget) so that the name of the wallpapers match yours, but then you would have to properly uncompile it and then recompile it.
Android>iOS... Android FTW!
jst07 said:
9. Copy the framework-res.apk to /system.
10. Change the permissions to rw-r-r using ES File Explorer (this is critical, failure will cause a bootloop)
11. Move framework-res.apk to /system/framework. Let it replace the other file.
Click to expand...
Click to collapse
Although I should have been warned by the red text above I finally resulted in a bootloop when changing those permissions. I don´t know what exactly went wrong, but it did.
As this may have happened to someone else (apparently it did, as the warning shows): Is there a way out? The only thing to do is to change back the framework-res.apk file from a backup on desktop or even to flash the whole KFHD from an update file (which does contain this file also). Unfortunately the device is unknown to cmd, although adb seems to be properly configured...
Any suggestions?
nakedtruthishere said:
Although I should have been warned by the red text above I finally resulted in a bootloop when changing those permissions. I don´t know what exactly went wrong, but it did.
As this may have happened to someone else (apparently it did, as the warning shows): Is there a way out? The only thing to do is to change back the framework-res.apk file from a backup on desktop or even to flash the whole KFHD from an update file (which does contain this file also). Unfortunately the device is unknown to cmd, although adb seems to be properly configured...
Any suggestions?
Click to expand...
Click to collapse
Flashing system.img in fastboot is about the only way to recover these devices right now-
http://forum.xda-developers.com/showthread.php?t=1951254
onemeila said:
Flashing system.img in fastboot is about the only way to recover these devices right now-
http://forum.xda-developers.com/showthread.php?t=1951254
Click to expand...
Click to collapse
Unfortunately this tool doesn´t work for me - "waiting for device" is the only result.
ADB is on, but I´m not sure about fastboot with the original USB cable - although QemuRoot worked fine with that. How do I surely know that fastboot is on? While trying to start fastboot via cmd, it prompted some syntax info, nothing else happens - that´s it (?)
nakedtruthishere said:
Unfortunately this tool doesn´t work for me - "waiting for device" is the only result.
ADB is on, but I´m not sure about fastboot with the original USB cable - although QemuRoot worked fine with that. How do I surely know that fastboot is on? While trying to start fastboot via cmd, it prompted some syntax info, nothing else happens - that´s it (?)
Click to expand...
Click to collapse
The possible reason is your using the cable that came with the kindle and for you to flash the system.img file you will need the factory cable which is differnt from the one that came with your KFHD
Hope this helps
doriean said:
...to flash the system.img file you will need the factory cable
Click to expand...
Click to collapse
That´s, what I suspect, too. I ordered one already.
On the other side there must be a way with the OEM cable, as in my opinion rooting means access to the affected files as well. Qemuroot works well
With "nolock" and go locker its much easier to change the lock screen wall paper or not?
Gesendet von meinem KFTT mit Tapatalk
I got to change my wallpaper in my friend kindle fire, really nice, thank all.
Help!
jst07 said:
Here are the steps I followed to change the wallpaper on my Kindle. Credit for this goes to Josepho1997 for the guide for the original Kindle Fire: http://forum.xda-developers.com/showthread.php?t=1765044&highlight=wallpaper
Disclaimer:
The risk of a bricked device or bootloop exists. To my knowlege there is no way to create a back up yet which makes recovery even harder. I am not liable for any damaged devices. Proceed at your own risk.
Things You'll Need:
Rooted Kindle
File Browser like ES File Explorer
7-Zip
Changing the Wallpaper:
1. Using ES File Explorer go to: /system/framework and copy (do not move!) framework-res.apk to your SD card.
2. Plug your Kindle into the computer and move the framework-res.apk (from SD card) to your computer and make a back up copy.
3. Use 7-Zip to open the one you intend to modify
4. Browse to \res\raw
5. Find the wallpapers named hi_xxx_p.jpg and hi_xxx_l.jpg. (These are the 1280x800 images, p are portrait images and l are landscape images. I am unsure what purpose the other images of different resolutions serve at this time).
6. Replace the .jpgs with the images you want, keeping the names exactly as they are. DO NOT delete any images. (I recommend replacing each image with the same resolution image for the best results).
7. Close 7-Zip and the new framework-res.apk will be saved, move this back to your SD card.
8. Open ES File Explorer. In the settings make sure you select "Up To Root", "Root Explorer" and "Mount File System".
9. Copy the framework-res.apk to /system.
10. Change the permissions to rw-r-r using ES File Explorer (this is critical, failure will cause a bootloop)
11. Move framework-res.apk to /system/framework. Let it replace the other file.
12. Reboot.
13. You will see your new wallpaper(s) when your Kindle reboots. To tidy up, go back into ES File Explorer and uncheck "Mount File System".
These are the steps I followed successfully but I caution anyone as it is risky. Follow them carefully and if you are uncomfortable or cannot afford to brick your device please wait until someone has developed a safer, easier method.
Click to expand...
Click to collapse
Ok I did all of this but i am still getting the regular images, which doesnt make sence because if i open up the framework in system/framework folder all the images i replaced are there none of the originals. Did I do something wrong? I gave rw-r-r access I have Kindle Fire HD 7
Go Launcher EX and HD
Just out of interest, isn't installing Go Launcher and Go Locker a safer approach?
Both these applications do not require any movement to /system/apps
I guess if you like the Amazon Launcher, this is not a solution? I just try to keep
people away from any steps that may involve Bricking the device. These are
only thoughts. By the way, great tutorial, very informative and detailed.
jst07, Never mind, your solution eliminates the annoying double lock
screen. Great work jst07!
Best Regards, Chris Bryant (prokennexusa)
joedirt2013 said:
Ok I did all of this but i am still getting the regular images, which doesnt make sence because if i open up the framework in system/framework folder all the images i replaced are there none of the originals. Did I do something wrong? I gave rw-r-r access I have Kindle Fire HD 7
Click to expand...
Click to collapse
Same here. I also tried to 'reinstall' framework-res but it failed to reinstall.
Do not attempt this modification it is no longer valid
Slimepuppy said:
Same here. I also tried to 'reinstall' framework-res but it failed to reinstall.
Click to expand...
Click to collapse
Slimepuppy,
This post needs to be updated. This was written when the software version was 7.1.x, at that time
this worked great and he had a great idea - he still does. Unfortunately, it looks like the jst07 has
been too busy to keep up the post. It happens to the best of us! I would recommend to NOT make
these changes until one of us is able to post an updated version of this modification. In Software
version 7.2.1 and higher, which is a modified version of Ice Cream Sandwich, the names in the
folder \res\raw have changed to k2_xxx_p.jpg and k2_xxx_l.jpg - not hi_xxx_p.jpg and hi_xxx_l.jpg.
Having said this, you will not see any changes when you attempt to modify images that the Kindle
no longer uses. Our new Kindle Fire Toolkit will automate this dangerous modification. So be
warned DO NOT ATTEMPT THIS MODIFICATION IT IS NO LONGER VALID IN SOFTWARE 7.2.X
The following is a link to our new Backup and Recover software: http://forum.xda-developers.com/showthread.php?t=2096888
---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------
joedirt2013 said:
Ok I did all of this but i am still getting the regular images, which doesnt make sence because if i open up the framework in system/framework folder all the images i replaced are there none of the originals. Did I do something wrong? I gave rw-r-r access I have Kindle Fire HD 7
Click to expand...
Click to collapse
joedirt2013,
This post needs to be updated. This was written when the software version was 7.1.x, at that time
this worked great and he had a great idea - he still does. Unfortunately, it looks like the jst07 has
been too busy to keep up the post. It happens to the best of us! I would recommend to NOT make
these changes until one of us is able to post an updated version of this modification. In Software
version 7.2.1 and higher, which is a modified version of Ice Cream Sandwich, the names in the
folder \res\raw have changed to k2_xxx_p.jpg and k2_xxx_l.jpg - not hi_xxx_p.jpg and hi_xxx_l.jpg.
Having said this, you will not see any changes when you attempt to modify images that the Kindle
no longer uses. Our new Kindle Fire Toolkit will automate this dangerous modification. So be
warned DO NOT ATTEMPT THIS MODIFICATION IT IS NO LONGER VALID IN SOFTWARE 7.2.X
The following is a link to our new Backup and Recover software: http://forum.xda-developers.com/show....php?t=2096888
prokennexusa said:
Slimepuppy,
This post needs to be updated. This was written when the software version was 7.1.x, at that time
this worked great and he had a great idea - he still does. Unfortunately, it looks like the jst07 has
been too busy to keep up the post. It happens to the best of us! I would recommend to NOT make
these changes until one of us is able to post an updated version of this modification. In Software
version 7.2.1 and higher, which is a modified version of Ice Cream Sandwich, the names in the
folder \res\raw have changed to k2_xxx_p.jpg and k2_xxx_l.jpg - not hi_xxx_p.jpg and hi_xxx_l.jpg.
Having said this, you will not see any changes when you attempt to modify images that the Kindle
no longer uses. Our new Kindle Fire Toolkit will automate this dangerous modification. So be
warned DO NOT ATTEMPT THIS MODIFICATION IT IS NO LONGER VALID IN SOFTWARE 7.2.X
The following is a link to our new Backup and Recover software: http://forum.xda-developers.com/showthread.php?t=2096888
---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------
joedirt2013,
This post needs to be updated. This was written when the software version was 7.1.x, at that time
this worked great and he had a great idea - he still does. Unfortunately, it looks like the jst07 has
been too busy to keep up the post. It happens to the best of us! I would recommend to NOT make
these changes until one of us is able to post an updated version of this modification. In Software
version 7.2.1 and higher, which is a modified version of Ice Cream Sandwich, the names in the
folder \res\raw have changed to k2_xxx_p.jpg and k2_xxx_l.jpg - not hi_xxx_p.jpg and hi_xxx_l.jpg.
Having said this, you will not see any changes when you attempt to modify images that the Kindle
no longer uses. Our new Kindle Fire Toolkit will automate this dangerous modification. So be
warned DO NOT ATTEMPT THIS MODIFICATION IT IS NO LONGER VALID IN SOFTWARE 7.2.X
The following is a link to our new Backup and Recover software: http://forum.xda-developers.com/show....php?t=2096888
Click to expand...
Click to collapse
If the new images are named k2_xxx......, then you will just have to properly rename them to the appropriate name.
a.k.a. Urahara
The truth! I'm really a girl!
Change the Wallpaper
Jessica said:
If the new images are named k2_xxx......, then you will just have to properly rename them to the appropriate name.
a.k.a. Urahara
The truth! I'm really a girl!
Click to expand...
Click to collapse
Jessica,
Thank you Jessica, if it was that easy I would have said just that but it looks like Amazon has make changes to
the cabinet. I spent about 40 minutes to put it all together and I just did not have time to test it all. I saw one
person Brick there Kindle and another frustrated since it "was not working". I have been a Software developer
for over 25 years (Linux Unix AS400 & Windows) and a phone app developer since the first smart phone was
released. I am just VERY conservative when I make recommendations - I always test, test, and test. When I
know it works and safe, then I post the results. I have not had time tonight and did not want to see anyone
waste there time, so I posted the warning. Tomorrow when I am at the office, I will post the modification
after I have thoroughly tested the solution.
Jessica said:
If the new images are named k2_xxx......, then you will just have to properly rename them to the appropriate name.
a.k.a. Urahara
The truth! I'm really a girl!
Click to expand...
Click to collapse
Exactly. There is a set of images in the location specified for this method (framework-res.apk/res/raw) and they have the k2_xxx_l.jpg or K2_xxx_p.jpg name. I created a replacement pair of images, renamed them, and pushed them into the apk with 7zip on a PC.
The replacement images are in the framework-res.apk but after two reboots the Fire HD is still displaying the old image. (I only replaced one image in both portrait and landscape mode. One can quickly cycle through the lockscreen images by closing/opening the cover. I wonder if it's the magnetic catch or the light sensor that's triggering that?)
Maybe there's another set of images. This is just enough like Linux to be trouble - time to buy another book!
prokennexusa said:
<snip> I have not had time tonight and did not want to see anyone
waste there time, so I posted the warning. Tomorrow when I am at the office, I will post the modification
after I have thoroughly tested the solution.
Click to expand...
Click to collapse
Sounds great, Chris - thanks for being conscientious and methodical.
Andy
Slimepuppy said:
Exactly. There is a set of images in the location specified for this method (framework-res.apk/res/raw) and they have the k2_xxx_l.jpg or K2_xxx_p.jpg name. I created a replacement pair of images, renamed them, and pushed them into the apk with 7zip on a PC.
The replacement images are in the framework-res.apk but after two reboots the Fire HD is still displaying the old image. (I only replaced one image in both portrait and landscape mode. One can quickly cycle through the lockscreen images by closing/opening the cover. I wonder if it's the magnetic catch or the light sensor that's triggering that?)
Maybe there's another set of images. This is just enough like Linux to be trouble - time to buy another book!
Sounds great, Chris - thanks for being conscientious and methodical.
Andy
Click to expand...
Click to collapse
Well, that doesn't make any sense. I have done this with my 1st gen kindle(I made the original guide). The way it works(simplified) is it rotates throughout all of these pictures. If you replace the pictures, it shouldn't show them, as they're not there.
a.k.a. Urahara
The truth! I'm really a girl!
Follow Up - Feedback
Slimepuppy said:
Exactly. There is a set of images in the location specified for this method (framework-res.apk/res/raw) and they have the k2_xxx_l.jpg or K2_xxx_p.jpg name. I created a replacement pair of images, renamed them, and pushed them into the apk with 7zip on a PC.
The replacement images are in the framework-res.apk but after two reboots the Fire HD is still displaying the old image. (I only replaced one image in both portrait and landscape mode. One can quickly cycle through the lockscreen images by closing/opening the cover. I wonder if it's the magnetic catch or the light sensor that's triggering that?)
Maybe there's another set of images. This is just enough like Linux to be trouble - time to buy another book!
Sounds great, Chris - thanks for being conscientious and methodical.
Andy
Click to expand...
Click to collapse
Slimepuppy,
No worries Slimepuppy, I just did not want to see anyone damage there Kindle, so I felt - I had better post a quick
warning before another person waists 1 to 2 hours and finds there hard work has gone down the drain. We actuality
have an option to change the Wallpaper in our next software release:
http://forum.xda-developers.com/showthread.php?t=2096888
The solution is in our software manifest and will be added in version 4.2.4 - the feature will be allow you to make
a change on the fly, so to speak. Either way, I will post the changes tomorrow for the people who like to edit apk's
Jessica said:
Well, that doesn't make any sense. I have done this with my 1st gen kindle(I made the original guide). The way it works(simplified) is it rotates throughout all of these pictures. If you replace the pictures, it shouldn't show them, as they're not there.
a.k.a. Urahara
The truth! I'm really a girl!
Click to expand...
Click to collapse
Yes ma'am - had me scratching my head a bit as well. It was interesting that when I copied the updated framework-res.apk into the file system the the Kindle froze and then rebooted - didn't expect that.
Hmmm...seems there are a couple of different sets of images after all. The set in /res/raw are 1024x600 JPGs at 96 dpi. There's another set of images in /res/raw-hdpi and in /res/raw-land-hdpi. These little puppies are 1280x800 at 96 dpi. The high-res images use the name format xi_arhm.jpg (in both the portrait and landscape directories).
In the Fire HD 8.9, there's only four images in /res/raw and the lockscreen images are in /res/raw/raw-xlarge-land-hdpi/ and /res/raw/raw-xlarge-hdpi/ Filenames are the same in both - xi_arhm.jpg and the rest in xi_xxxx.jpg format. These images are 1920x1200 still at 96 dpi.
Tomorrow I'll change a couple and see what happens - it's been too many hours between now and coffee, and I try not to delete anything after midnight.
Andy
edit...
Ok, since I really didn't have to technically 'delete' anything... Placing the new pictures in the /res/raw-hdpi folders worked perfectly on the 7".
The odd sorta-lockup happened this time as well. Here's the rundown: the Fire's running 7.2.3 and is rooted, Google-app'd, and the OTA updates are defeated. ES File Explorer in root mode. Followed the direction precisely. On the last move - when framework-res.apk is put into the /system/framework/ directory, ES FileEx freezes. I can still highlight the back and home buttons - the machine's responding to the touch screen but there's no response beyond that. Tapping the power button results in an immediate boot screen - exactly as if the machine had powered down but forgot to tell the screen what happened. Once the machine's up, the new lockscreen wallpaper is visible. Any chance that the Fire's processing the framework-res.apk automatically?
Life is good!
Hey everyone,
I recently upgraded from the original Fire to the HDX. I searched high and low on how to change the lock screen pics on the HDX and turned up nothing. However, I did find a different way to change the lock screen on the original Fire and thought it might work on the HDX. After rooting, safe strapping, making a system back up and several hours of searching for the lockscreen pics folder, IT WORKED!! I apologize if this has already been done on the HDX but I wanted to share for those of you who couldn't find it either. I urge you to follow these steps EXACTLY or you could end up with a very expensive door stop.
**Before Starting** Your HDX must be rooted. I would highly advise installing safe strap and making a backup of your system (I boot looped twice before I finally got it right!) Down load 7-zip and install on your PC. Download root explorer from the Amazon market. Credit goes to Josepho1997 for posting this on the original Kindle Fire. I just took his method and tweaked it for the HDX.
1. Using Root Explorer from the Amazon Market, go to: /system/framework and copy (do not move!) framework-res.apk to your SD card.
2. Plug your Kindle into the computer and move the framework-res.apk (from SD card) to your computer and make a back up copy.
3. Use 7-Zip to open the one you intend to modify
4. Open the "res" folder then the "raw-xhdpi" folder.
5. You'll find 22 jpeg images in this folder, 11 images with the "_p_" in the file name.
6. Replace the "_p_" jpegs with the images you want, keeping the names exactly as they are. DO NOT delete any images. You can use 11 different images or the same one over and over again. I highly recommend formatting each picture to 1600x2650 like the originals.
7. Close 7-Zip and the new framework-res.apk will be saved, move this back to your SD card.
8. Open Root Explorer.
9. Copy the framework-res.apk to /system.
10. Long press on the framework-res.apk file and change the permissions to rw-r-r. (This is critical, failure to do this will cause a bootloop)
11. Move framework-res.apk to /system/framework. Overwrite the existing file.
12. The Kindle will automatically reboot and your new wallpapers will appear on the lock screen.
That's it! Good luck :good:
This is awesome! I think I may wait though if you suggest safestrap. It's currently not available for the 8.9.
Sent from my KFAPWI using xda premium
I don't blame you. There is nothing worse than that pucker factor you get when you go into boot loop without a backup. Hopefully, our awesome devs will safe strap your sweet 8.9" machine in no time!
I've only just got mine Kindle Fire HDX 7 to use Google Apps. Playing around with the rest of Amazons interesting design choices is the next step. This looks like a brilliant idea! Time to get my HD space pictures in there.
Thanks!
--- I have just tried this. I can copy the file to a visible directory but then i cant see it in there...
It isn't hidden or anything, thoughts?
There is a check box in Root Explorer preferences that enables you to see hidden files. Make sure this is checked first and then copy the file to the root of your SD card. You should be able to see it.
It's showing up now.
Thanks!
Sweet:fingers-crossed:
Because I am pure awesome, I managed to bootloop it too haha.
I have recovered it though and had another go with much better result haha
For anyone else having a go at this, I can't stress enough cthebadge's point about moving it to "/system" first, changing the permissions, and THEN moving it to "/system/framework"!
My next step is trying to find the gray background pic on the carousel screen. If anyone finds this before me, I'd appreciate the location. I don't see why we couldn't customize this background image as well..?
the lock screen pics doesn't bother me ,but I want to make the nova ;auncher show it's wallpaper.
cthebadge said:
My next step is trying to find the gray background pic on the carousel screen. If anyone finds this before me, I'd appreciate the location. I don't see why we couldn't customize this background image as well..?
Click to expand...
Click to collapse
system\app\Launcher-release-signed_81224610\res\drawable-sw600dp-xhdpi/home_bg.png and system\app\Launcher-release-signed_81224610\res\drawable-sw600dp-land-xhdpi\home_bg.png
How to change Kindle Fire HDX carousel wallpaper
ONYXis, you are awesome my friend!
Anyone that would like to change their carousel screen wallpaper, it's basically the same steps as I listed above for changing your lock screen wallpaper, only the pics are in different directories.
Following ONYXis's path, you want to copy the Launcher-released-signed_xxxxxxx.apk from the system/app directory and move it to your SD card. Transfer to the PC and open with 7-zip. Open the res folder and locate the portrait picture in the "drawable-sw600dp-xhdpi" folder named "home_bg.png". The landscape picture is in the "drawable-sw600dp-land-xhdpi" folder listed as "home_bg.png". Take both pics and replace them with the ones of your choice. The resolution for the portrait pic is 1200x1869 and the landscape pic is 1920x1149. **Make sure you save your new pics as .PNG and not .JPEG. Overwrite the old stock pics with your new pics keeping the name exactly the same. Close 7-zip and transfer the .apk file back to your SD card. Move the file to /system and change permissions again to rw-r-r. Move the .apk file to the /system/app directory and overwrite the original .apk file. Your Kindle will reboot on it's own and the new wallpaper appears! Thanks again to ONYXis for finding the pics!
Thanks. BTW this TUT http://forum.xda-developers.com/showthread.php?t=2373563 works too.
Notice that new resolution for HDX is 562x562 and 198x198.
My screens http://imgur.com/a/g559a and some icons from me attached (put folder "images" from archive to system/vendor/data with overwrite and reboot).
ONYXis said:
Thanks. BTW this TUT http://forum.xda-developers.com/showthread.php?t=2373563 works too.
Notice that new resolution for HDX is 562x562 and 198x198.
My screens http://imgur.com/a/g559a and some icons from me attached (put folder "images" from archive to system/vendor/data with overwrite and reboot).
Click to expand...
Click to collapse
Those icons look amazing!
Sent from my iPhone using Tapatalk
cthebadge said:
Hey everyone,
I recently upgraded from the original Fire to the HDX. I searched high and low on how to change the lock screen pics on the HDX and turned up nothing. However, I did find a different way to change the lock screen on the original Fire and thought it might work on the HDX. After rooting, safe strapping, making a system back up and several hours of searching for the lockscreen pics folder, IT WORKED!! I apologize if this has already been done on the HDX but I wanted to share for those of you who couldn't find it either. I urge you to follow these steps EXACTLY or you could end up with a very expensive door stop.
**Before Starting** Your HDX must be rooted. I would highly advise installing safe strap and making a backup of your system (I boot looped twice before I finally got it right!) Down load 7-zip and install on your PC. Download root explorer from the Amazon market. Credit goes to Josepho1997 for posting this on the original Kindle Fire. I just took his method and tweaked it for the HDX.
1. Using Root Explorer from the Amazon Market, go to: /system/framework and copy (do not move!) framework-res.apk to your SD card.
2. Plug your Kindle into the computer and move the framework-res.apk (from SD card) to your computer and make a back up copy.
3. Use 7-Zip to open the one you intend to modify
4. Open the "res" folder then the "raw-xhdpi" folder.
5. You'll find 22 jpeg images in this folder, 11 images with the "_p_" in the file name.
6. Replace the "_p_" jpegs with the images you want, keeping the names exactly as they are. DO NOT delete any images. You can use 11 different images or the same one over and over again. I highly recommend formatting each picture to 1600x2650 like the originals.
7. Close 7-Zip and the new framework-res.apk will be saved, move this back to your SD card.
8. Open Root Explorer.
9. Copy the framework-res.apk to /system.
10. Long press on the framework-res.apk file and change the permissions to rw-r-r. (This is critical, failure to do this will cause a bootloop)
11. Move framework-res.apk to /system/framework. Overwrite the existing file.
12. The Kindle will automatically reboot and your new wallpapers will appear on the lock screen.
That's it! Good luck :good:
Click to expand...
Click to collapse
Hi,
I've mistakenly skipped step 10 and done step 11 , now, as you've anticpated, my Kindle Fire HDX 8.9 has gone into bootloop at the Kindle Fire logo. Can you help? Many thanks!
You are a braver person than I for trying this hack without safe strap my friend. The have been searching for a fix for your 8.9" boot loop and could find nothing. I am by no means a developer and will only experiment with things if I have safe strap installed. I would recommend posting your question in it's own thread and hope that someone can help. Sorry
cthebadge said:
You are a braver person than I for trying this hack without safe strap my friend. The have been searching for a fix for your 8.9" boot loop and could find nothing. I am by no means a developer and will only experiment with things if I have safe strap installed. I would recommend posting your question in it's own thread and hope that someone can help. Sorry
Click to expand...
Click to collapse
Is it really that bad? Thanks for your suggestion anyway. I've post it in other thread already. Have my fingers crossed:fingers-crossed:
Well..it's not good! Lol Normally, I won't even attempt root without a fxz or sbf file to flash in case I boot loop. You just changed a system file when you dropped that file in the framework folder. The only way that I can think to fix it would be to somehow be able to access that file via computer and overwrite your modified file with the stock file. You did make a backup of the original file I assume..?
cthebadge said:
Well..it's not good! Lol Normally, I won't even attempt root without a fxz or sbf file to flash in case I boot loop. You just changed a system file when you dropped that file in the framework folder. The only way that I can think to fix it would be to somehow be able to access that file via computer and overwrite your modified file with the stock file. You did make a backup of the original file I assume..?
Click to expand...
Click to collapse
Yes I did. I'm also thinking how to reinstall the original file back.
Image "replacement"
cthebadge said:
Hey everyone,
6. Replace the "_p_" jpegs with the images you want, keeping the names exactly as they are. DO NOT delete any images. You can use 11 different images or the same one over and over again. I highly recommend formatting each picture to 1600x2650 like the originals.
...
12. The Kindle will automatically reboot and your new wallpapers will appear on the lock screen.
That's it! Good luck :good:
Click to expand...
Click to collapse
I followed the directions except I don't know how to "replace" the images in the file without deleting the old image files. I used the same file names for my images and copied my new images into the file after deleting the old image files.
When I moved the .apk into /system/framework several programs shutdown and I thought the tablet was going to reboot but it never rebooted. Eventually I just used the power button and shut it off. When I restarted the system all I got was the grey screen. I shut down by holding the power button for about 10 seconds and then tried a second time.... no joy.
Since I am using safestrap I am up and running, I will rebuild my rom-slot1 from backup. Curious what I may have done wrong or if I am missing some small step...
HDX 8.9 rooted, modified so google playstore works.
The _p_ files are portrait, the _l_ files are the same picture in landscape. I will figure out what the dimensions are for the landscape files and reformat all the pics for a retry.... all are 1600 x 2560 (not 2650!)
Ok, replaced all the _p_ and _l_ files, make sure they are the right dimensions and in portrait or landscape shape. It all worked and now I just need to kill the Amazon advertising.
Can someone convert or tell me how to convert this bootanim to the Nexus 7?
Thanks!
https://dl.dropboxusercontent.com/u/12414928/bootanimation.zip
Boncey said:
Can someone convert or tell me how to convert this bootanim to the Nexus 7?
Thanks!
https://dl.dropboxusercontent.com/u/12414928/bootanimation.zip
Click to expand...
Click to collapse
Hi, Boncey...
When you say 'convert', I assume you mean 'encapsulate' it into a CWM/TWRP flashable .zip.
Well, that skill and level of technical knowledge is a bit beyond me, I'm afraid. But changing a boot animation is a relatively trivial task, providing you exercise care, and are comfortable poking around inside /system.
I've tested your bootanimation.zip on my own Nexus 7... and it works... but there's too long a duration after the animation has run, before you're presented with the home launcher (or Android desktop). All you see, after the animation (which runs for about 2 seconds) is 30 seconds of black screen.
It's also quite large, clocking in at a whopping 9.7Mb... compared to the standard KitKat 'dancing colored circles' boot animation... which is just a miniscule 714Kb.
Anyway... here's the how-to-bit...
Your Nexus 7 will need to be rooted.
You'll also need a root capable Android file manager. There are several such file managers available on Google PlayStore, with ES File Explorer File Manager arguably one of the most famous and renowned. But I prefer X-Plore file manager, because it has dual-pane capability, which makes copying stuff from one location to another easy. So my instructions and thumbnails that follow are written with 'X-Plore file manager' in mind...though they should be adaptable to any root capable Android file manager.
Whichever file manager you choose... you'll first need to go into its settings or configuration options, and enable root... you'll also need to enable a setting which allows changes to be made to /system.
In X-plore filemanager, this is called Superuser+Mount Writable (Superuser mode, which allows changes in read-only mode).
(See thumbnail no.1, at the bottom of this post).
Other Android file managers may use a different description and words... but the key thing to remember, is that you're allowing the file manager to makes changes to /system. And for this reason, EXTREME CAUTION should be exercised when using the file manager with this setting enabled. By default, and for very good reasons, /system is set as READ-ONLY. Enabling the 'Mount Writable' option, makes /system READ-WRITE.
Once you've completed the following procedure, remember to disable the 'Mount Writable' option.
-------------------------------------------------------------------------
OK... with that lengthy preamble out of the way... we begin.
The Nexus 7's boot animation is stored in a folder called /system/media... and unsurprisingly, its called bootanimation.zip.
The first thing you need to do, is rename this file. When doing this sort of thing on my own Nexus 7, I just rename the file extension... so, bootanimation.zip becomes bootanimation.bak
Leaving the old (original) boot animation in place is a good idea, so should you tire of its replacement... you can easily revert back, by simply renaming the files extension back to .zip, ie., bootanimation.zip
Next... copy the new replacement into the same system folder... namely /system/media
You should now have two files in the folder /system/media...
/system/media/bootanimation.bak - the original boot animation, but disabled.
/system/media/bootanimation.zip - the new, replacement boot animation.
(See thumbnail no.2)
We're nearly there... but there is one last thing to do... set the file permissions on the new bootanimation.zip file.
How this is done will vary from one file manager to the next... but in X-Plore, it's accomplished by LONG PRESSING on the file in question, until a context sensitive menu appears.
(See thumbnail no.3)
Select the option marked 'Permissions'... a dialogue box will appear with nine check boxes.
Ensure all the ones for READ are ticked, and just the USER one for WRITE. The permissions mode should amount to 644. Anyway, it's probably better if you just take a look at my screenshot at the bottom of this post. (Describing this sort of thing makes my head hurt... a picture really does paint a thousand words).
(See thumbnail no.4)
Finally... go back into the file managers settings option, and disable the Mount Writable option (or whatever it's called in your chosen file manager).
Right that's it... you can now reboot your Nexus 7 and enjoy the dubious pleasure of watching the green Android mascot peeing all over an Apple logo... I'm guessing you're not a big fan of Apple!.
-------------------------------------------------------------------------
Although the above sounds fairly involved and complicated... it really isn't. Like all things technical, it's easier to do, than describe. Descriptions often run to several paragraphs for the most prosaic of things.
Summary.
** A rooted Nexus 7.
** A root capable Android file manager.
** Enable root and Mount Writable or similar option in your chosen filemanager.
** Rename /system/media/bootanimation.zip...to.../system/media/bootanimation.bak
** Copy the new bootanimation.zip into the folder /system/media.
** Set file permissions on it... to 644.
** Disable Mount Writable or similar option in your chosen filemanager.
** Reboot... Enjoy!.
-------------------------------------------------------------------------
Good luck... and hope this helps.
Rgrds,
Ged.
Thanks!
Turns out my permissions were wrong!
Ok so I figured out how to change the lock screen wallpapers WITHOUT the use of an app, wallpaper picker or modifying the framework or systemui. It's nothing short of amazing.
PROS:
-NO image quality is lost because of a crappy cropper.
-NO application or modifications to the framework are needed for this to work so you can officially get rid of Amazon Photos
CONS:
-Only one wallpaper at a time
-Requires root. However this is done through /data where it is mounted as R/W. This would't be a problem if you could symlink the /data folder to internal storage or /mnt. I have tried a few ways on the HD 8 with no success.
Instructions:
1. Download your favorite HD wallpaper (as close to 1920x1200 as possible). I have a collection of dozens of stock Android wallpapers from various versions and devices at your disposal.
2. When you have chosen your wallpaper and downloaded it, the file extension should be a .jpg. Please go here and convert it to a .png https://jpg2png.com This should be done for all wallpapers. Changing the file extension is not the same. This web based tool also compresses the file to reduce the loss of image quality.
3. Using a file explorer like Total Commander copy the wallpaper.JPG from your download folder on internal storage to this /data directory:
Code:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
4. Activate your lock screen to see your custom wallpaper. A reboot shouldn't be required.
DragonFire1024 said:
Ok so I figured out how to change the lock screen wallpapers WITHOUT the use of an app, wallpaper picker or modifying the framework or systemui. And it's glorious.
This is done on my rooted HD 10, but there is a huge possibility this does NOT require a rooted tablet. Why? Because it's done through /data where it's writable without root this is so easy I kick myself for not discovering this earlier. So if you have an HD 8, any model or year (NOT on Nougat) I need you test this.
1. Download your favorite HD wallpaper (as close to 1920x1200 as possible). I have a collection of dozens of stock Android wallpapers from various versions and devices at your disposal.
2. Using a file explorer like Total Commander copy the wallpaper.JPG from your download folder on internal storage to this /data directory:
Code:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
3. Activate your lock screen to see your custom wallpaper. A reboot shouldn't be required.
I've only tried this with one wallpaper so you might be able to have several in that directory so it's different every time the lock screen is activated. I look forward to your reports!
Click to expand...
Click to collapse
Trying right now... brb...!
DragonFire1024 said:
Ok so I figured out how to change the lock screen wallpapers WITHOUT the use of an app, wallpaper picker or modifying the framework or systemui. And it's glorious.
This is done on my rooted HD 10, but there is a huge possibility this does NOT require a rooted tablet. Why? Because it's done through /data where it's writable without root this is so easy I kick myself for not discovering this earlier. So if you have an HD 8, any model or year (NOT on Nougat) I need you test this.
1. Download your favorite HD wallpaper (as close to 1920x1200 as possible). I have a collection of dozens of stock Android wallpapers from various versions and devices at your disposal.
2. Using a file explorer like Total Commander copy the wallpaper.JPG from your download folder on internal storage to this /data directory:
Code:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
3. Activate your lock screen to see your custom wallpaper. A reboot shouldn't be required.
I've only tried this with one wallpaper so you might be able to have several in that directory so it's different every time the lock screen is activated. I look forward to your reports!
Click to expand...
Click to collapse
Sorry, I was pulled into something for a bit. And then I became distracted making this lovely new lock screen wallpaper, lol...
Unfortunately, it does not seem we are able to access that folder without root. I tried four different file managers. When I finally typed the direct address verbatim as you provided, the device didn't say the folder did not exist, but said I did not have access. I did however notice a different com.android.systemui folder, which was located at /data/data/ , but also did not have access to this folder.
Screenshots of my attempts to locate/access the folder you described are here if you want to see for yourself.
I just bought a new soldering iron today. I'm about to hardmod root this sucker ✔ ??*???
richaardvark said:
Sorry, I was pulled into something for a bit. And then I became distracted making this lovely new lock screen wallpaper, lol...
Unfortunately, it does not seem we are able to access that folder without root. I tried four different file managers. When I finally typed the direct address verbatim as you provided, the device didn't say the folder did not exist, but said I did not have access. I did however notice a different com.android.systemui folder, which was located at /data/data/ , but also did not have access to this folder.
Screenshots of my attempts to locate/access the folder you described are here if you want to see for yourself.
I just bought a new soldering iron today. I'm about to hardmod root this sucker ?*
Click to expand...
Click to collapse
My beautiful wallpaper will have to wait for now... :crying:
richaardvark said:
Sorry, I was pulled into something for a bit. And then I became distracted making this lovely new lock screen wallpaper, lol...
Unfortunately, it does not seem we are able to access that folder without root. I tried four different file managers. When I finally typed the direct address verbatim as you provided, the device didn't say the folder did not exist, but said I did not have access. I did however notice a different com.android.systemui folder, which was located at /data/data/ , but also did not have access to this folder.
Screenshots of my attempts to locate/access the folder you described are here if you want to see for yourself.
I just bought a new soldering iron today. I'm about to hardmod root this sucker ?*
Click to expand...
Click to collapse
Update: Ultimately however, I was able to set the lock screen wallpaper, using the "Prime Photos" app. This however changed my launcher/home screen wallpaper as well. I then downloaded the standard Google "Wallpapers" app from the Play store and was able to set my wallpaper back to what it had been, and was also able to keep weird cat sweater lady as the lock screen image. So, ultimately same end result, just a tiny bit more effort to make it happen, but not really a big deal.
Updated screenshots in my shared folder.
richaardvark said:
Update: Ultimately however, I was able to set the lock screen wallpaper, using the "Prime Photos" app. This however changed my launcher/home screen wallpaper as well. I then downloaded the standard Google "Wallpapers" app from the Play store and was able to set my wallpaper back to what it had been, and was also able to keep weird cat sweater lady as the lock screen image. So, ultimately same end result, just a tiny bit more effort to make it happen, but not really a big deal.
Updated screenshots in my shared folder.
Click to expand...
Click to collapse
What a shame. Well at least this is a lot easier now rather than taking the time and effort to mod the systemui.
Ok so this is disappointing. I'll have to post a rewritten guide. This one is tough to explain. But I am pretty sure I did this through the Amazon Device Settings application.
I plugged my HD 8 into my PC and opened ADB in an attempt to access the directory. I was able to cd into /data/securedStorageLocation just fine. However I tried to make the directory com.android.systemui and got an error of 'permission denied', but not because of no root, 'the directory already exists'. So it's there, just not totally accessable.
So this has to be exclusive to Amazon, or a result of or a combination of things. I have literally found only two forum posts that mention the directory perfectly. However the website is in Japanese. Thankfully Google translate helped. The good news is, it looks like you can gain entry by symlinking. When I saw this entry, and sdcard was mentioned, I did realize one thing I did yesterday that I've never done before. Optimized the databases. Specifically I used SDmaid (bought full version but I don't think that mattered). So it occurred to me, it likely 'fixed' whatever Amazon took out of the databases. This is a wild guess though.
Reporting on the rom copied Stock ROM reporting that it was possible to download amazon instant video,
and copied /data/secureStorageLocation/com.amazon.avod to each directory / sdcard
· Then the following So evacuate the original and
create a symbolic link (su with adb shell and executed). Once done, restart
cd / data / secureStorageLocation /
mv com.amazon.avod com.amazon.avod.org
ln -s /sdcard/com.amazon.avod com.amazon.avod
Click to expand...
Click to collapse
I went ahead and did a little bit of a rewrite to change the title. Just set up flash to stock and just saw the folder had already been there. I honestly cannot believe it's been there this entire time and I honestly can't believe I've missed it this entire time. Unfortunately this requires root access unless somebody can figure out how to symlink the folder to internal or external storage. though it is located in part of the data that is read and write, the folder is not.
Sent from my Galaxy S4 using XDA Labs
Update:
I just want to add, wallpapers can be in .jpg format, but for best compression, least amount of quality loss and if you have the same wallpaper for both lock screen and desktop, convert your .jpg to a .png for both (this should be done regardless of the wallpapers are the same or not). This handy, web based tool does exactly that, and compresses the file at the same time. This has resulted in my wallpapers being 100% in sync. https://jpg2png.com
I have copied my wall paper in png format to the location (with root access). However, it's not used as the wall paper or lock screen background, even after reboot. What am I missing?
In the meantime, I can use an image browser (Quick Pic) to set it as wall paper. However, it does not last. It may revert without reboot.
redhonker said:
I have copied my wall paper in png format to the location (with root access). However, it's not used as the wall paper or lock screen background, even after reboot. What am I missing?
In the meantime, I can use an image browser (Quick Pic) to set it as wall paper. However, it does not last. It may revert without reboot.
Click to expand...
Click to collapse
Make sure you are in the right directory/folder and all the way to the end of com.android.systemui:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0. Your wallpaper goes in the '0' folder. So far as I know no special permissions needed. But it won't hurt to set permissions to:
rw-r--r-- (0644). Make sure you have a lock screen set
# ls /data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
-rw-r--r-- root root 11833019 2018-12-08 16:19 Wallpaper-Florida-Keys.png
So it all looks right. Just not taking effect. I don't know if it depends on some package that might get disabled (I've disabled a bunch).
redhonker said:
# ls /data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
-rw-r--r-- root root 11833019 2018-12-08 16:19 Wallpaper-Florida-Keys.png
So it all looks right. Just not taking effect. I don't know if it depends on some package that might get disabled (I've disabled a bunch).
Click to expand...
Click to collapse
It very well may have been patched on 5.3 or 5.6.3 (whatever it really is)
The good news is that I can just set it using a image viewer. However, they do revert back though it's not clear what triggers revert.
redhonker said:
The good news is that I can just set it using a image viewer. However, they do revert back though it's not clear what triggers revert.
Click to expand...
Click to collapse
Try disabling com.amazon.kindle.kso and deleting it.
I am on the latest 5.6.3.0, and copying to the '0' folder works for me. I had ads removed when I first got the device, so I don't have com.amazon.kindle.kso. So as Dragon said, maybe disabling and deleting will help.
Note that if the image is subsequently deleted from the '0' folder, the "7 cycling wallpapers" return. I don't know if they would return if some other method of setting the lock screen wallpaper is used, like the Prime Photos app.
---------- Post added at 09:55 PM ---------- Previous post was at 09:17 PM ----------
Dragon, with regard to the "7 cycling wallpapers" in your other thread, I was able to use your post 2 to get my own 7 wallpapers to cycle on the lock screen. So even though I wanted your info on how to recover if I screwed up SystemUI.apk, I didn't need it! If you ever get around to it, I'd still like to know how to recover without having to reinstall stock, reroot, etc.
This post really should be put over in that thread, but I didn't know if you were getting notified there, so I continued to write here (and in another thread that I knew you would see). Thanks for your great work!
sga999 said:
I am on the latest 5.6.3.0, and copying to the '0' folder works for me. I had ads removed when I first got the device, so I don't have com.amazon.kindle.kso. So as Dragon said, maybe disabling and deleting will help.
Note that if the image is subsequently deleted from the '0' folder, the "7 cycling wallpapers" return. I don't know if they would return if some other method of setting the lock screen wallpaper is used, like the Prime Photos app.
---------- Post added at 09:55 PM ---------- Previous post was at 09:17 PM ----------
Dragon, with regard to the "7 cycling wallpapers" in your other thread, I was able to use your post 2 to get my own 7 wallpapers to cycle on the lock screen. So even though I wanted your info on how to recover if I screwed up SystemUI.apk, I didn't need it! If you ever get around to it, I'd still like to know how to recover without having to reinstall stock, reroot, etc.
This post really should be put over in that thread, but I didn't know if you were getting notified there, so I continued to write here (and in another thread that I knew you would see). Thanks for your great work!
Click to expand...
Click to collapse
Sometimes it's easier to make a new thread and index them into one as you go along...I sorta have one started. Anyways, if the SystemUI fails when you install it, the tablet will still boot...just without any user interface. So you can just push your back up back to the tablet. It's tricky if you come to it because you have to keep your tablet attached to PC while running a few shell commands.
I have copied my wallpaper in png format to the location (with root-access) and used a website like https://convertx2y.com/png-to-jpg/ to convert between the image formats. Is it a good one?