Related
I'm running EB01 2.6 sc. Have been trying to add shut down animation but my phone won't let me modify system folder. I've flashed back to stock and used a different method for root access and tried several different file managers. Whenever I try to make a change, it tells me the folder was created successfully or the move was successful but no changes actually happen. Does anyone have any ideas?
From my Super Frankencleaned Fascinate via XDA App
bump from 2nd page..
Hmm, There is a shutdown.apk in system/app that has appeared within the last 4 versions of super clean. I bet that has something to do with your shutdown ani's not being recognized or appearing.
good day.
Ran into the same problem. I had to use Super Manager. Just make sure u go into the settings for super manager and enable root function
Sent from my TRS-80 using DOS
zipgunjny said:
Ran into the same problem. I had to use Super Manager. Just make sure u go into the settings for super manager and enable root function
Sent from my TRS-80 using DOS
Click to expand...
Click to collapse
Thanks I'll give that a shot and report back. I'm happy to find someone who at least is aware that this issue exists haha. I've been perusing the forums for days and everyone is speechless about it.
zipgunjny said:
Ran into the same problem. I had to use Super Manager. Just make sure u go into the settings for super manager and enable root function
Sent from my TRS-80 using DOS
Click to expand...
Click to collapse
It worked!!! Thanks a ton.......such a weird problem...why would only that particular file manager work???
Then again........maybe it's not entirely fixed. I'm now allowed to add system folders. I wasn't before. But I don't see a "move" option anywhere, to move shutdown.ogg (or whatever I'm trying to move) I only see Copy and Cut. When I choose one of those, it says "Prepare to Copy" (or Cut), but never actually does so.
Just rename the original to shutdown.ogg.old or oldshutdown.ogg . I remember that it says preparing to copy and it actually will copy the file/folder so all you have to do is navigate to the right folder and hit the clipboard icon to paste.
QQQQ
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!
This is a quick walk through for editing the build.prop to allow lock screen and launcher rotation.
I got tired of looking at my phone sideways while it was propped up landscape wise, in my case.
1. Locate "build.prop" in /system using your favorite file explore
2. Open it up and at the bottom add the lines
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
3. Save your edit and reboot.
Lockscreen rotation still not working for you???
A few users have reported that adding a blank line between the two, fixes this issue.
Once the phone reboots your lockscreen and Google Now launcher will rotate with the orientation of the device just like other apps do.
To undo this, simply remove the lines we added
:good:
Update: 11/10/2015
enigma9o7 Has figured out how to get this to stick even after an update! Head over to his post for the walkthrough and install guide!! Remember to give them a "thanks" for sharing the work!
Awesome I been wondering how to get this done.
Nice tip. I've always just used an app called Ultimate Rotation Control. Seems to work just fine on the Nexus 6. A quick build.prop tweak removes the need for a separate app for it, though. I might get around to trying this...eventually
can someone make a flash able zip for this please ?
thanks in advance
Anybody know how one would do this with adb?
N6
I used an app for quite some time but i disliked it running in the background.
Im not able to make a flashable zip. Maybe in time I will see if i can.
For adb, youd have to pull the build.prop, edit on computer then push it back. The instructions to do that are unclear to me
mrfuzzie23 said:
can someone make a flash able zip for this please ?
thanks in advance
Click to expand...
Click to collapse
You can install Nova Launcher and toggle the setting in there, or use the ultimate rotation app someone else mentioned.
Thx
If you set the DPI to 384 or less, this happens by default.
pavankp said:
If you set the DPI to 384 or less, this happens by default.
Click to expand...
Click to collapse
Thats good to know! Not surprising, the device is most likely changed to "tablet size" to the system. And they have full rotation.
Works great, thanks! (AT&T Nexus 6)
Would not work for me I get error saving
techrider6262 said:
Would not work for me I get error saving
Click to expand...
Click to collapse
Thats not good. What error are you getting?
eqbirvin said:
Thats not good. What error are you getting?
Click to expand...
Click to collapse
It just said error can't save and I tried a couple different time
techrider6262 said:
It just said error can't save and I tried a couple different time
Click to expand...
Click to collapse
gotcha. You are rooted, correct? and if so what file manager are you using to locate the build.prop?
es file explorer and i'm rooted.
in ES file explorer when you grant it root permissions, click on root, then mount R/W, make sure "/system" is RW instead of RO. (sorry if you already know this, im just trying to save time and figure your error out haha)
Thanks I got it working.:good:
Glad to hear it!
to each their own, I like being able to get OTAs so I'll stick with Ultimate Rotation Control
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?
I am getting my Nook ST from ebay very soon. Please help me understand the process:
What is the difference between just rooting using Nook Manager and flashing a ROM like 1337?
I am assuming, I can still install APKs after rooting?
thanks
S
sany said:
I am getting my Nook ST from ebay very soon. Please help me understand the process:
What is the difference between just rooting using Nook Manager and flashing a ROM like 1337?
I am assuming, I can still install APKs after rooting?
thanks
S
Click to expand...
Click to collapse
Rooting with NookManager gives you access to "root" directories that are normally off limits to users. It also allows for various customizations. It sets the security flag for installing from "unknown sources", allowing you to install apps via a file manager (or ADB), as opposed to getting them from the PlayStore (which you can't anymore). And it installs a base set of apps to get you going, like a file manager, launcher, browser, etc. That is customizable.
Custom ROMs like the 1337 simply enable different features that some people like. Perhaps better to use the system "as-is" for a bit before you decide to wipe it out? Then you'll have a better idea of what you'd like to have.
nmyshkin said:
Rooting with NookManager gives you access to "root" directories that are normally off limits to users. It also allows for various customizations. It sets the security flag for installing from "unknown sources", allowing you to install apps via a file manager (or ADB), as opposed to getting them from the PlayStore (which you can't anymore). And it installs a base set of apps to get you going, like a file manager, launcher, browser, etc. That is customizable.
Custom ROMs like the 1337 simply enable different features that some people like. Perhaps better to use the system "as-is" for a bit before you decide to wipe it out? Then you'll have a better idea of what you'd like to have.
Click to expand...
Click to collapse
Thank you @nmyshkin, I think my liking will be towards Nook Manager. So I will try to get ready with the Nook Manager installation files and instruction. The only thing confusing here in the forum is there are too many threads and geeting lost which and where to start. Hope if I start with the original thread which is from way back 2012, it will still work. My understanding is if I am on a new firmware 2.1.2 I will rewrite the modification files to nook manager as per that thread.
thanks again
S
sany said:
Thank you @nmyshkin, I think my liking will be towards Nook Manager. So I will try to get ready with the Nook Manager installation files and instruction. The only thing confusing here in the forum is there are too many threads and geeting lost which and where to start. Hope if I start with the original thread which is from way back 2012, it will still work. My understanding is if I am on a new firmware 2.1.2 I will rewrite the modification files to nook manager as per that thread.
thanks again
S
Click to expand...
Click to collapse
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 .
Click to expand...
Click to collapse
Very helpful! thanks again.
nmyshkin said:
2. Register your device with B&N.
Click to expand...
Click to collapse
How important is this step - do I really need to register? any advantages and disadvantages?
sany said:
How important is this step - do I really need to register? any advantages and disadvantages?
Click to expand...
Click to collapse
The device software is designed to sell ebooks from B&N. Anything that frustrates this design (like not registering or disabling parts of the B&N system) tends to raise all kinds of internal alarms and the system dialogs constantly with itself, worrying about its purpose in life, its inability to "phone home", and generally fritters away a lot of its battery charge on rehearsing for a role it cannot assume.
In short, the path of least resistance results in the least system hand-wringing, improved battery life, etc. You don't need to enter any credit card information. All you need is an email address (which I suppose could be fake) and a password. Then you can forget about it if you have no interest in purchasing ebooks from B&N. I have completely ignored the B&N system except for the Reader and Library which I find adequate--and simple--enough for my needs. But everything else is hidden. It just lives its happy little digital life waiting for that one special day when I will buy an ebook with a patience only electrons can exhibit. Meanwhile I have all kinds of other stuff that I am interested in and there don't seem to be any issues or conflicts with the B&N system.
My 2 cents.
Installed but no apps
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
Click to expand...
Click to collapse
I successfully backed up and rooted the device. Firmware is 1.2.2.
But I don't have any apps. Not even the base software. See screenshot. Even the extras like es file explorer were not installed. Since I don't have any file explorer, I am unable to install any apps. I want to go for ADB method as last resort. Please advice.
Thanks
sany said:
I successfully backed up and rooted the device. Firmware is 1.2.2.
But I don't have any apps. Not even the base software. See screenshot. Even the extras like es file explorer were not installed. Since I don't have any file explorer, I am unable to install any apps. I want to go for ADB method as last resort. Please advice.
Thanks
Click to expand...
Click to collapse
You can try for ADB (more headaches there), but it would be better now to get some useful apps and have a way to conveniently side-load others. You are supposed to be able to install apps from Relaunch in the file manager screen. That would involve copying the apk file to the NST via a USB connection, then locating that apk file using the file folder browser and tapping on the icon. I could never get that to work, but it is supposed to work.
Failing that, you need to revisit NookManager. You must not have done the customization correctly if none of the apps you wanted were installed. If you can get that fixed, you can simply root again with NookManager (right on top of what you have now) and it will fix the problem IF you get it set up correctly.
There are four steps required to add an app to the NookManager rooting routine:
1. Copy the apk file to the folder files/data/app on the NookManager SD card
2. in the folder "scripts" on the NookManager SD card, copy and rename one of the "install_x" files so it represents the app you just moved into the folder in step 1. So, if you want ES File Explorer, you might rename the file "install_esfileexplorer"
3. Edit the file you just copied and renamed, changing the name of the apk file in the first line to exactly match the filename of the apk file you have replaced in files/data/app. So continuing the example, "es_file_explorer.apk" (which is the name of the apk file as I provided it). Then edit the "echo" statement so it reads something like "echo ES File Explorer installed"
4. Locate the file scripts/do_root. Copy and rename one of the "install_x" files so it matches what you did earlier, in this case "install_es_file_explorer". There are no contents to edit.
You need to do those four steps for each app you want to add to the install list. To remove an app you don't want (like the Amazon App Store), remove the apk file from files/data/app, remove the "install_x" file for that app from the folder "scripts", and remove the "install_x" file for that app from the file scripts/do_root.
nmyshkin said:
Here's how you get started:
1. When you get your NST, execute a factory reset. This will return the device to an out-of-the-box condition. To do this, power up and as soon as you see the "Read Forever, your Nook is starting up" screen, hold the two lower hardware buttons until you see a screen prompt.
2. Register your device with B&N.
3. Update the firmware to 1.2.2 (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip)
4. Prepare a NookManager card according to the instructions here: https://forum.xda-developers.com/nook-touch/development/nst-g-updating-nookmanager-t3873048, making whatever changes/additions you want in terms of base software such as a file manager, browser, launcher, etc.
5. Run NookManager. Before you do anything else I suggest you make a backup of the newly updated and registered NST. That way if something goes wrong, you won't have to go all the way back to a factory reset. After the backup, root the NST and exit NookManager.
After that, it's pretty much up to you. Any time you want to make another backup, just reboot with the NookManager card inserted and make a backup. Just remember that the backup will replace whatever is on the NookManager card, so if you wanted to keep that one, you need to have copied it to your PC first.
Click to expand...
Click to collapse
Thanks, I followed all those steps...I will take a relook at it. But without es file explorer, I thought there is already a file manager. How to I get there as I can't see anything in the app drawer? (Screenshot in previous post).
sany said:
Thanks, I followed all those steps...I will take a relook at it. But without es file explorer, I thought there is already a file manager. How to I get there as I can't see anything in the app drawer? (Screenshot in previous post).
Click to expand...
Click to collapse
I know very little about Relaunch, but I believe you need to tap on the open door in the upper right corner to get out of the app drawer.
Oh okay! I was expecting to launch file manager from app drawer. So when relaunch opens we are already in file explorer.
One more question: how do we make dictionary work in the default nook reader, that is when you you open a book from library. I thought pressing on a particular word will present me the option. I only see option to bookmark. I have to read the manual again.
sany said:
Oh okay! I was expecting to launch file manager from app drawer. So when relaunch opens we are already in file explorer.
One more question: how do we make dictionary work in the default nook reader, that is when you you open a book from library. I thought pressing on a particular word will present me the option. I only see option to bookmark. I have to read the manual again.
Click to expand...
Click to collapse
That's how the dictionary works for me. Hold your finger on a word until it is highlighted. Then a series of options pops up from the bottom, one of which is "Look up".
nmyshkin said:
You can try for ADB (more headaches there), but it would be better now to get some useful apps and have a way to conveniently side-load others. You are supposed to be able to install apps from Relaunch in the file manager screen. That would involve copying the apk file to the NST via a USB connection, then locating that apk file using the file folder browser and tapping on the icon. I could never get that to work, but it is supposed to work.
Failing that, you need to revisit NookManager. You must not have done the customization correctly if none of the apps you wanted were installed. If you can get that fixed, you can simply root again with NookManager (right on top of what you have now) and it will fix the problem IF you get it set up correctly.
There are four steps required to add an app to the NookManager rooting routine:
1. Copy the apk file to the folder files/data/app on the NookManager SD card
2. in the folder "scripts" on the NookManager SD card, copy and rename one of the "install_x" files so it represents the app you just moved into the folder in step 1. So, if you want ES File Explorer, you might rename the file "install_esfileexplorer"
3. Edit the file you just copied and renamed, changing the name of the apk file in the first line to exactly match the filename of the apk file you have replaced in files/data/app. So continuing the example, "es_file_explorer.apk" (which is the name of the apk file as I provided it). Then edit the "echo" statement so it reads something like "echo ES File Explorer installed"
4. Locate the file scripts/do_root. Copy and rename one of the "install_x" files so it matches what you did earlier, in this case "install_es_file_explorer". There are no contents to edit.
You need to do those four steps for each app you want to add to the install list. To remove an app you don't want (like the Amazon App Store), remove the apk file from files/data/app, remove the "install_x" file for that app from the folder "scripts", and remove the "install_x" file for that app from the file scripts/do_root.
Click to expand...
Click to collapse
\
I followed all your instructions above and successfully installed all apps. To summarise my observation after the successful installation:
1. Only Opera browser app and ES File Explorer app works
2. Yalp app store does not work at all - it just takes me to the next screen with options to 'update' or 'run'. Pressing update keeps searching forever and 'run' takes me back to the previous screen. After several tests, I decided to uninstall the app.
I tried to install youversion bible app which also works (but its a old version) so several features not available. But at least it works.
I noticed wifi outage issues intermittently on the opera browser and also once while trying the yalp store app. It said I was not connected, but I know for a fact I was connected when I connect to the Nook store etc.,
Overall, I am wondering what did I gain out of the whole process. Not much I can do with the custom installation. So I might return back to a original nook after playing with this setup for a while. This leaves me with couple of questions that I will start on a new thread.
Thanks again @nmyshkin for your patience in explaining.
S
To go back to original nook state - do I need to simply go into settings>Device Info> Erase & Deregister Device to get it back to out of box condition? Will this cancel the rooting?
Or do I have to stick the nook manager card and restore from backup?
sany said:
To go back to original nook state - do I need to simply go into settings>Device Info> Erase & Deregister Device to get it back to out of box condition? Will this cancel the rooting?
Or do I have to stick the nook manager card and restore from backup?
Click to expand...
Click to collapse
Erase and deregister will remove root and restore to out-of-the-box state unless you have done something serious. In that case, a factory re-image should solve the problem. That is done by powering off, then powering on and holding down the two lower hardware buttons as soon as the "Read Forever" screen appears. Wait for the prompt and follow it.
Re: Yalp Store, I just checked mine a minute ago and it's running fine. Very rarely it goes down and can't log in to the PlayStore, but it generally comes back later in the day.
Okay - so maybe I should try yalpstore at different times.