Database Users

[HOW TO] Get Wallpaper on Custom Launcher

EDIT: This post applies to Fire OS 4.5.n. Beginning with OS 5, Lollipop, we're able to put wallpaper on custom launchers.
This method lets you use any image for wallpaper and works with most launchers. If it doesn't work with yours and you really, really want wallpaper, try a different launcher.
This requires root and does not apply to the stock Fire launcher. You can't put wallpaper on that.
Requirements
Root
Xposed framework v. 2.6.1 from here. (Look under Show older versions for 2.6.1. Don't use experimental 2.7)
Gran PC's KindleBG module here
A file explorer to install Xposed and KindleBG
QuickPic app from the Play Store
Instructions
Install and open Xposed. Choose the Framework option and press Install/Update. Tap Reboot and say Yes at "Are you sure?" [Fire reboots].
Install KindleBG.
Run Xposed and choose Modules. Tick the KindleLockBG box. Go back to the Framework screen and reboot.
Run QuickPic and choose the image you want for wallpaper.
Open the QuickPic menu, choose Set as, and then QuickPic wallpaper.
Crop the image the way you want it and press the checkmark at top of screen.
Linker Warning with Shell Commands
With Xposed installed, Android displays a linker warning with the commands we use to block/unblock system apps. You can safely ignore this. Xposed does not cause a memory leak and, at least with the the KindleBG module, does not pose any security risk.

is this for the fire HD6 and HD7. I've heard reports of bricks due to exposed on these devices

powerpoint45 said:
is this for the fire HD6 and HD7. I've heard reports of bricks due to exposed on these devices
Click to expand...
Click to collapse
Yes, Fire HDs. I've been using Xposed on my Fire HD 7 for several days without problem. BUT FWIW, I did not install SuperSU.
EDIT: Installed SuperSU yesterday and np with Xposed through lots of boots and messing around.

DoLooper said:
Yes, Fire HDs. I've been using Xposed on my Fire HD 7 for several days without problem. BUT FWIW, I did not install SuperSU. Still using Kingroot. If you think Xposed with SuperSU is a problem, I'll edit OP.
Click to expand...
Click to collapse
DoLooper, would you care to do a detailed report on what you tried with Xposed that worked besides the wall paper? I'd like to try it, but the bricking reports scare me for now, since I don't understand fully what Xposed does.

bibikalka said:
DoLooper, would you care to do a detailed report on what you tried with Xposed that worked besides the wall paper?
Click to expand...
Click to collapse
Hey bibikalka, so far I've only done the steps I wrote--installed Xposed, the BG module and also Gran PCs module to block OTA updates. Today, I uninstalled Xposed and installed superSU, reinstalled Xposed and modules--just to make sure the SU didn't have an effect.
Better question might be what I haven't done, which is mess with any system apps or other internals. Did use JMZ's great tool to install gapps, but don't think that should matter.
Anyway, will install Gravity Box later (one of the more fun xposed modules) and keep you posted.

powerpoint45 said:
is this for the fire HD6 and HD7. I've heard reports of bricks due to exposed on these devices
Click to expand...
Click to collapse
So I scoured the Fire HD 6/7 forums for posts of bootloops/bricks caused by Xposed and everything comes back to just one post. This from @Drew123abc123 where he says:
I installed a custom boot animation, did a few system modifications and everything was working fine. But then, the next day (today) I tried to install Xposed and rebooted and got a bootloop.
Click to expand...
Click to collapse
I wouldn't wish unrecoverable bootloop on anyone, but wonder what were those mods? Did he reboot after? Did he install the xposed 2.7 (experimental) or any "unusual" modules? But that said, Xposed can put devices into bootloops--see "In case you get into a bootloop"--so I understand people being reluctant.
Only know that Xposed with the BG module is working fine on my "pretty clean" rooted HD 7--and I've got wallpaper!

DoLooper said:
So I scoured the Fire HD 6/7 forums for posts of bootloops/bricks caused by Xposed and everything comes back to just one post. This from @Drew123abc123 where he says:
I wouldn't wish unrecoverable bootloop on anyone, but wonder what were those mods? Did he reboot after? Did he install the xposed 2.7 (experimental) or any "unusual" modules? But that said, Xposed can put devices into bootloops--see "In case you get into a bootloop"--so I understand people being reluctant.
Only know that Xposed with the BG module is working fine on my "pretty clean" rooted HD 7--and I've got wallpaper!
Click to expand...
Click to collapse
Ah ok then I think this should be just fine. Too bad I lost root /:

With Nova Launcher you Doesnt need QuickPic

That's fine. This is for anyone who can't get wallpaper

Just a little bump for others who need this now.

When I try to install the Xposed Framework I get an error saying "Failed to get root access."
I just upgraded to 4.5.4 via instructions here: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
I believe I am rooted (Titanium Backup says so) but I do not see the Superuser app in my app drawer?
Edit - Just installed Superuser from the Play Store and that fixed it!

is there a way to modify the lock screen images using this process?

No. They can't be changed.

Prior to this build, changing lockscreen was not a problem..Did they remove the feature in 5.2.2u2

coolguy2488 said:
Prior to this build, changing lockscreen was not a problem..Did they remove the feature in 5.2.2u2
Click to expand...
Click to collapse
You can still block ads and get Amazon's wallpapers, but you can't put your own images on lockscreen, which I thought the OP was asking about. Vaguely remember you could use own image in Developer's Preview, which was much more AOSP. 5.2.2u2 is all Amazon all the time again.

DoLooper said:
You can still block ads and get Amazon's wallpapers, but you can't put your own images on lockscreen, which I thought the OP was asking about. Vaguely remember you could use own image in Developer's Preview, which was much more AOSP. 5.2.2u2 is all Amazon all the time again.
Click to expand...
Click to collapse
Yes I had a custom wallpaper on my lockscreen in Developer's Preview. I have since bricked that one and putting it back on there would be my last step to my new refurb. I could even rename my tablet which is greyed out now on 5.1.1.
Is it possible to downgrade back to Developer's Preview?

I would ask bibikalka in this thread: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950

Magisk, SuperSU, SafetyNet

wondering if anyone here is using Magisk and SuperSU and was able to get their LGV20 to pass SafetyNet? for some reason using the same exact steps as others who have this combination working on different devices, I can't get it to pass on the LGV20 and I have a feeling it might be due to the stock kernel. I wasn't able to get this to work on the LGV10 either and neither did the "Device Unlock" app provided by T-Mobile to perform a SIM unlock until I reverted back to a stock boot image.

Would be super interested to know this as well. Been researching this on and off all day. I read somewhere that there are modifications to kernels that can be made to report things back to Safety Net and not sure if any of the custom V20 kernels have this or not.
Was also looking into suhide as an option as well

All credit goes to @ZachJohnson for this after seeing his posted here: https://forum.xda-developers.com/showpost.php?p=70426738&postcount=1131
I downloaded the rootswitch app and using only that, I was able to pass SafetyNet checks and register my credit card with Android Pay. It was very hit and miss though.....took a number of tries. I have yet to make a purchase.
I should note that I have not downloaded suhide yet and wonder if that will help make it more consistent.
For reference, I am using a VS995 unlocked via dirty santa on a stock verizon 11A rom + konverged kernel. I have made small tweaks to /system such as modifying some sounds and disabling some apks via renaming them apk.bak.

That's awesome! I'm glad to hear that helped! ?
To elaborate a little... I was only trying to play Pokémon Go, I've never tried using Android pay. As I mentioned in that post you linked to, I stumbled across the Root Switch app.
Prior to that, I had flashed suhide and installed the accompanying suhide gui from the play store and it didn't seem to do anything for me. With suhide already flashed, I found Root Switch to work perfectly.
And in case it's relevant for anybody looking into this, I rooted with Dirty Santa on my VS995, flashed the US996 rom and konverged kernel, and am now running the VS995 modded NotSoStock rom with its kernel and this worked for me on all three.

Rootswitch Install?

I just rooted my phone using Dirty Santa and I'm on the stockish rom thats provided off they're thread.
Basically trying to get access to Snapchat, but won't allow me, I downloaded rootswitch off Asus (user) 1.3.3.2 but upon install I'm getting it interferes with already installed applications.
Any help is appreciated, I'm getting different answers on other threads but they're pretty outdated.

I'd try Magdisk I have the T-Mobile variant and it works quite well with it.

I would suggest Magisk as well. Some roms will support root switch, but other roms will have more recent security patches. Anything past Nov/Dec will result in rootswitch causing you to bootloop until you pull your battery... Magisk is very nice and smooth on this phone. But just make sure you leave nop traces of supersu installed or magisk most likely will fail to flash.
Im guessing you have a sprint phone??

Biff627 said:
I would suggest Magisk as well. Some roms will support root switch, but other roms will have more recent security patches. Anything past Nov/Dec will result in rootswitch causing you to bootloop until you pull your battery... Magisk is very nice and smooth on this phone. But just make sure you leave nop traces of supersu installed or magisk most likely will fail to flash.
Im guessing you have a sprint phone??
Click to expand...
Click to collapse
Yeahi have Sprint. Sorry I'm such a noob now. The last time I had root was back with my LG G3. I stepped away from root with my G5 and came back with the V20, and everything's so different now lol. So I'll download an Rom then that supports Magisk.

Help w tuten1000's Guide: Root + custom kernel + clean rom

In the last week I received my xperia x compact completely stock. First thing I do when I get a new phone before even activating it is root it. I was utilizing this guide to root my xperia x compact "Guide: Root + Custom Kernel + Clean rom + TA for X Compact" and I am stuck on the step where you are instructed to flash the modified XC-GenesisKernel-v1.04-nodrm kernel and SU. Flashing this kernel always results in a boot loop (Ive waited more then 30 minutes for it to resolve). I reflash the stock service exchange unit - 34.1.A.1.198 MM firmware to get back a functioning phone. The guide recommends:
"Run xperifirm and download the "service exchange unit - 34.1.A.1.198" firmware for posterity and latest rom for your region."
Am I supposed to use the most current nougat firmware for the following steps and only use the service exchange unit firmware if I need to downgrade to the lower original firmware? The thread for the XC-GenesisKernel states it is for nougat roms, which would explain a boot loop when I try to use the service exchange unit MM rom. Ideally Id like to stay on MM so that I can use xposed. Root and the phone being fully functional with no loss of camera and such is my main desire, xposed is secondary. I have a Backup TA of my DRM keys, the phone bootloader is unlocked, and I am looking for a little direction / clarification, any help in this respect is greatly appreciated.
Thanks

efaustus9 said:
help in this respect is greatly appreciated.
Click to expand...
Click to collapse
Click the first link in the guide and read it.

XperienceD said:
Click the first link in the guide and read it.
Click to expand...
Click to collapse
Thanks, I read through it and I see indeed the latest nougat firmware is what I should use in the later steps of tuten1000's guide and is the source of the boot loop I am experiencing.
If possible I would like to stay on marshmallow so I can used xposed framework. Are you aware of or can you recommend a kernel I can flash that will give me root, fingerprint, and use of most DRM functions while still on marshmallow.

Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342

itandy said:
Maybe you can try my guide using Magisk with full DRM, Xposed and root. But you need to flash back to MM first if you need Xposed.
https://forum.xda-developers.com/x-compact/how-to/android-pay-safety-net-rooted-unlocked-t3610342
Click to expand...
Click to collapse
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?

efaustus9 said:
Excellent itandy, this this just what I had in mind. I never downloaded and flashed a nougat rom as xposed was important to me. In following tuten1000's guide I did flash the XC genesis kernel as well as SU in recovery. This resulted in a boot loop but a prerequisite in your guide is a /system partition without any trace of su. Since I reflashed the stock service exchange unit 34.1.A.1.198 MM firmware I should be good to proceed right?
Click to expand...
Click to collapse
You're all good to begin with MM stock ROM.

itandy said:
You're all good to begin with MM stock ROM.
Click to expand...
Click to collapse
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?

efaustus9 said:
It worked beautifully, thank you so much itandy :victory:
Anyway to get rid of the device is not secure screen on boot?
Click to expand...
Click to collapse
This is a common request but the answer is no.

itandy said:
This is a common request but the answer is no.
Click to expand...
Click to collapse
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?

efaustus9 said:
Okay, it would be nice to be rid of but it is a worthwhile trade off.
In your guide you mention a safety net, and installing xposed breaks it. What is this safety net and what is the draw back to breaking it? Am I locked out of certain apps or functions?
Click to expand...
Click to collapse
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.

itandy said:
SafetyNet is the security checking API used by some apps like Android Pay and Pokemon Go to make sure your device is not tampered with. Simply put it makes sure your device is stock, not unlocked, rooted or modified. Magisk currently is able to bypass SafetyNet checking for root and some other "unwanted" apps. But Xposed will still be detected because it works in much lower system level. And with Magisk you can simply disable Xposed temporarily and reboot if you want to use, say, Android Pay.
Click to expand...
Click to collapse
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.

efaustus9 said:
ah very informative, thanks again.
I installed the xposed framework SDK23 in Magisk manager, it is showing up as installed under modules in magisk but xposed is not in the app drawer and I cant seem to access it.
Click to expand...
Click to collapse
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758

itandy said:
You need to install Xposed Installer separately. Try this unofficial app.
https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Click to expand...
Click to collapse
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?

efaustus9 said:
Haha once again you come through. You are really helping me get this all sorted with so little fuss, I am very grateful.
This is my first xperia experience, I am coming from a samsung s3 running a KK slimrom and things are a bit different on this device. Any other pointers or recommendations for this new phone? Is there a way to make the soft key bar transparent so I can actually utilize the full 4.6"?
Click to expand...
Click to collapse
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.

itandy said:
I remember there're mods (maybe Xposed modules) to make the navbar autohide. Maybe you'd also like to check out my navbar Xposed module. See my signature.
Click to expand...
Click to collapse
Great, I will definitely check out your app. Ideally Id like to mimic what I believe is called the "immersive mode" in supported apps. In this mode the app takes up the full screen and the icons are replaced with three persistent minimal dots.

Magisk didn't install on my On5

I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?

Mike_77712 said:
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Click to expand...
Click to collapse
I had one time where I got Magisk working with the Superstarz ROM on the SM-G550T1. I don't remember what I did tbh, but it took hours of rebooting, frustrating hanging, etc.. Upon one of the Magisk modules I flashed after it did work, of course to my sadness it stopped working. Nandroid backups are so crucial and I just stopped making so many changes before a backup these days. Sure you can't speed demon through and get all your wildest fantasies to come true overnight, but I find making incremental progress with backups to me more sustainable. Anyways, I tried many times, many setups, and ultimately wasted many hours trying to "win" with this phone. I'd honestly highly recommend sticking with SuperSu by Chainfire as it has always just worked. That means no Android Pay, no Pokemon Go, and prolly others I haven't considered. I too wanted to have my cake and eat it... For Safetynet to pass and la la la. Truth be told, it is a royal pain in the arse!!! If YOU STILL DARE, you would definitely want to make sure you start with a stock ROM boot image and BACK IT UP #1. If you are using a custom ROM it may not allow you to fully unroot and go back to a stock img because it doesn't find one to revert to. For Magisk to pass SafetyNet and work at full capacity, you must start there. If you go to the trouble of going all the way back to stock, please upload one for all of us and make sure to include your phone/os specs from about phone. From stock, flash custom recovery BEFORE ROOT, within recovery back up boot, upload for us and yourself. Now, you have a legit revertible img to go back to in case you can't from Magisk/SuperSu. Phh's Superuser was a nightmare btw, never worked correctly. There's no way to unroot and go back to a stock boot img that I found unless you first back up from TWRP or custom recovery. Long answer, more than you bargained for no doubt, but hopefully something to be gained from. Really though... if all you want is for Snapchat to work and can live without Android Pay/Pokemon Go. Here's an easier method: uninstall Xposed, unroot, log into Snapchat (let it save a login token), root, re-install Xposed, Titanium Backup Snapchat, it should hold up from there. Did it once, forget if that's entirely right, but search and ye will find exact threads. I just said to hell with Snapchat, Pokemon Go, and Android Pay. I'd rather settle for Chainfire's Superuser's stability, Xposed (more mods), & less overall B.S. Sorry if that isn't the best possible answer, or what exactly you were sought. I did however want to share some of my experience (many, many, many hours of tinkering). All in all, I finally decided to order a new digitizer/lcd to repair an old OnePlus One that I have had laying around. I plant to fix it and migrate because I'll tell ya right now... ppl just aren't gonna do much more for this model than what you see out there. Perhaps I'm being a pessimist, but also realist... I've been waiting around looking for something to come, too lazy to attempt re-compilation of code myself, and no one else has yet. Magisk can be a nightmare to the ninth gate's extreme degree. It is possible, not saying it can't be done. Have patience, or it won't that's for sure. Just really have to mess up... lots of times... over and over, and over and over and over again. Learn, read XDA, and be stubborn/patient as hell until you get there. Document your progress so you know what you did and maybe you can help someone else. Other times it's more advantageous pick what matters, settle, and focus on something else. :good:

From my understanding you need a clean install, unroot with SU (or install SU as systemless (?)),wipe internal, and follow instructions to install Magisk... I'm not totally sure though, also install the Magisk module.

Mike_77712 said:
I installed super su on my Galaxy On5, flashed super su and rooted it with Odin too. Today i hit full unroot on supersu then rebooted and snapchat worked which told me it's been unrooted. Then figuring I'd be safe with installing magisk (since super su said it reverted to the stock image or something like that) I flashed magisk 13.3 but after it finished succesfully i rebooted but can't find anything magisk related installed on my phone. Could someone point me in the right direction?
Click to expand...
Click to collapse
I just successfully rooted with Magisk & modded a few things out with it, only issue seemz to be systemless xposed but ill crack that shell when need be . Let me know if any1 is in need of help doing the same.

woahOppO999 said:
I just successfully rooted with Magisk & modded a few things out with it, only issue seemz to be systemless xposed but ill crack that shell when need be . Let me know if any1 is in need of help doing the same.
Click to expand...
Click to collapse
Can you please share the steps you followed to root ON5 pro using magisk.
Also if you can list the modules u have from magisk.