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
Related
I know many of us are quite frustrated with the xposed module installation on the rooted htc phones. The main culprit for it is the busy box application. This application contains all the terminal commands necessary to break the security of the stock mobile system. It is not a virus application though but install those commands and provide you the functionality to execute the framework changes needed for some important apks like Titanium backup, adfree, xposed module, etc etc..
On HTC devices with Kitkat 4.4.2 specifically, due to the (S-ON) security feature, the busybox app will not get installed easily as apk even on the rooted custom roms. It must be installed separately along with the cwm recovery after updating the supersu. That is why many busybox installers lying on the play store are not working/effective anymore.
It could also be due to the busybox files getting installed either in the incorrect path/location (due to change in the internal sd card path in 4.4.2 kitkat versions) or the S-ON feature must be stopping from installing at the right place. Whatever may be the reasons for not working, there is fix for this issue and the steps are outlined below.
DISCLAIMER: Please don't blame me if you corrupt your device by following the below process. I am pretty sure that the below process works flawlessly, but the reason for failing or corrupting your device could be a combination of several existing issues in your phone. So I take no responsibility for your bricked devices.
Now the coolest part:
1. Your HTC desire 816 must be rooted and should have working clockworkmod recovery. Otherwise this trick doesnt work at all.
2. First lets fix the busy box app - Go to playstore and download Busybox on Rails free apk from here: https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
3. Open the Busybox on Rails app, select the Operation option as "Cleanup & Install" and method as Recovery (and not "normal"). This will reboot your device into recovery and install the busy box application.
4. Reboot the system. Vola Busy box should have installed correctly now. To confirm that reopen the same Busybox on Rails app and see if the System Status shows up as OK. If it does, your busybox is successfully installed. If not by any chance, try repeating the steps 2, 3 and 4 again. It should work.
Some people install the terminal apk from play store and execute some su commands to verify if the busybox is installed properly. But that is for people having much knowledge on software scripting side of things.
5. Now lets install the xposed module - search for the xposed module apk from here http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 and install it. Remember to download the xposed disabler apk zip as well, just in case if your mobile gets corrupted, you can flash that to bring back your original settings.
6. Install the xposed module and open Framework within the apk
7. Before hitting the Install/update option, change the Installation mode from defaulted Classical (Write to /system directly) mode to the middle one Recovery (flash zip automatically) mode. Dont change anything else in the settings.
8. Now hit Install/update
9. Phone will reboot the system into recovery mode, install the xposed module.
10. Reboot the phone and Volaaaaaaaa!!!!!!!!!! Enjoy the xposed framework in your mobile, which opens the endless opportunities to tweak your mobile.
Hit the thanks button if I have helped you in any way.
This method might works on all HTC models with S-ON security feature and 4.4.2 android Kitkat version, but have not tested it myself though. However, my friend did say it worked on HTC one latest model. Dont blame me if it doesn't by any chance.
Xposed
vbrsekhar said:
I know many of us are quite frustrated with the xposed module installation on the rooted htc phones. The main culprit for it is the busy box application. This application contains all the terminal commands necessary to break the security of the stock mobile system. It is not a virus application though but install those commands and provide you the functionality to execute the framework changes needed for some important apks like Titanium backup, adfree, xposed module, etc etc..
On HTC devices with Kitkat 4.4.2 specifically, due to the (S-ON) security feature, the busybox app will not get installed easily as apk even on the rooted custom roms. It must be installed separately along with the cwm recovery after updating the supersu. That is why many busybox installers lying on the play store are not working/effective anymore, mainly because of the files getting installed either in the incorrect path/location (due to change in the internal sd card path in 4.4.2 kitkat versions) or the S-ON feature must be stopping from installing at the right place. Whatever may be the reasons for not working, there is fix for this issue and the steps are outlined below.
DISCLAIMER: Please don't blame me if you corrupt your device by following the below process. I am pretty sure that the below process works flawlessly, but the reason for failing or corrupting your device could be a combination of several existing issues in your phone. So I take no responsibility for your bricked devices.
Now the coolest part:
1. Your HTC desire 816 must be rooted and should have working clockworkmod recovery. Otherwise this trick doesnt work at all.
2. First lets fix the busy box app - Go to playstore and download Busybox on Rails free apk from here: https://play.google.com/store/apps/details?id=me.timos.busyboxonrails
3. Open the Busybox on Rails app, select the Operation option as "Cleanup & Install" and method as Recovery (and not "normal"). This will reboot your device into recovery and install the busy box application.
4. Reboot the system. Vola Busy box should have installed correctly now. To confirm that reopen the same Busybox on Rails app and see if the System Status shows up as OK. If it does, your busybox is successfully installed. If not by any chance, try repeating the steps 2, 3 and 4 again. It should work.
Some people install the terminal apk from play store and execute some su commands to verify if the busybox is installed properly. But that is for people having much knowledge on software scripting side of things.
5. Now lets install the xposed module - search for the xposed module apk from here http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 and install it. Remember to download the xposed disabler apk zip as well, just in case if your mobile gets corrupted, you can flash that to bring back your original settings.
6. Install the xposed module and open Framework within the apk
7. Before hitting the Install/update option, change the Installation mode from defaulted Classical (Write to /system directly) mode to the middle one Recovery (flash zip automatically) mode. Dont change anything else in the settings.
8. Now hit Install/update
9. Phone will reboot the system into recovery mode, install the xposed module.
10. Reboot the phone and Volaaaaaaaa!!!!!!!!!! Enjoy the xposed framework in your mobile, which opens the endless opportunities to tweak your mobile.
Hit the thanks button if I have helped you in any way.
This method might works on all HTC models with S-ON security feature and 4.4.2 android Kitkat version, but have not tested it myself though. However, my friend did say it worked on HTC one latest model. Dont blame me if it doesn't by any chance.
Click to expand...
Click to collapse
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
heppojo said:
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
Click to expand...
Click to collapse
The only advantage of installing busybox and xposed installer is to open up endless opportunities of tweaking your mobile to look and behave the way you want (in most cases). Also some finest apps like titanium backup, and others etc use these busy box services too.
The link2sd app may or may not work and in my view it is totally unrelated. I havent tried that much, so cannot comment much on that I am afraid.
heppojo said:
Sir,
Please advice what is the advantages for installing this?
is this will solve link2sd problem?
Click to expand...
Click to collapse
I have tried and it worked.
vbrsekhar said:
The only advantage of installing busybox and xposed installer is to open up endless opportunities of tweaking your mobile to look and behave the way you want (in most cases). Also some finest apps like titanium backup, and others etc use these busy box services too.
The link2sd app may or may not work and in my view it is totally unrelated. I havent tried that much, so cannot comment much on that I am afraid.
Click to expand...
Click to collapse
Lnk2Sd is somehow useful for users with partition, very useful for low internal memory devices. Though a high quality SD card is necessary. Thanks to this tutorial. CONFIRMED WORKING for Xposed Framework.
Huge thanks for this. Got xposed working on my phone - running 4.4.2 with S-on / boot loader unlocked from HTC
Sent from my HTC_D816x using XDA Free mobile app
This is a off topic Que , but I require urgent help ..
I haven't rooted my device nor did I do any trick with it , but now my device is showing TAMPERED on hboot menu .. is this means my warranty is void .. how that can happen with even connecting my phone to pc.. can I suggest any way of removing it or unlocking my bootloader other than HTC Dev site, or any way to s off it . .. warranty issues
Sent from my HTC Desire 816 dual sim using XDA Free mobile app
sonnu said:
This is a off topic Que , but I require urgent help ..
I haven't rooted my device nor did I do any trick with it , but now my device is showing TAMPERED on hboot menu .. is this means my warranty is void .. how that can happen with even connecting my phone to pc.. can I suggest any way of removing it or unlocking my bootloader other than HTC Dev site, or any way to s off it . .. warranty issues
Sent from my HTC Desire 816 dual sim using XDA Free mobile app
Click to expand...
Click to collapse
It is very unusual to see that happen without you connecting to pc and trying to unlock the bootloader from HTC dev site. This was first time hearing that this can happen without trying to root or alter the mobiles internal system.
Anyways, to unlock bootloader, you have to go via HTC site and there is no other alternative as of now. The moment you unlock your bootloader, you will see that TAMPERED message in the hboot. If you are also receiving the red text while booting HTC that "This device has been tampered/altered and is development purposes only.... blah blah blah message", then definitely it has been unlocked bootloader.
May be your phone is a unlocked version, which requires the vendor to unlock the bootloader first and then have to unlock the service carrier. In this case you would get that message for sure, without you having to do anything. This way you will not have manufacture warranty, but will have the vendor warranty. Check with the place where you bought that piece.
Btw, if you find out that it has already been unlocked, then you might as well can root it as it makes your piece worth buying. All the best.
Hi, already follow the guides and steps given and now how can I know xposed working on my phone? What should I do next?
You are a genius vbrsekhar :laugh: Installation has been successfully Thank you dear :highfive:
Syria_BoY said:
You are a genius vbrsekhar :laugh: Installation has been successfully Thank you dear :highfive:
Click to expand...
Click to collapse
Cheers buddy, glad to know that it worked. Thank you for acknowledging!
Im a little confused seeing this post. Is this an old probelm? I get xpoaed to install just fine. Some of the status bar mods are wonky . Am I missing something ? Lol.
carnivalrejectq said:
Im a little confused seeing this post. Is this an old probelm? I get xpoaed to install just fine. Some of the status bar mods are wonky . Am I missing something ? Lol.
Click to expand...
Click to collapse
This is for stock ROM's.
Yeah I know. I've only ever used stock and cm11. Never had a problem besides some of the status bar icons not all changing colors. Install always went fine.
Sent from my 710C using XDA Free mobile app
Yeah some HTC 816 devices have the problem with busy box installation and that is why xposed framework doesn't work immediately after rooting.
สุดยอดเลยนาจ๋าาาา
im getting problem to install busybox on rails shows missing applets
pls reply guys
sjadhav252 said:
pls reply guys
Click to expand...
Click to collapse
Don't worry...mine is also showing missing applets.
But exposed still works.
Install xposed using the recovery method.
how can i install viper4android it keep asking for roos access after phone reboot
sjadhav252 said:
im getting problem to install busybox on rails shows missing applets
Click to expand...
Click to collapse
Mine too, in the first try there is warning in CWM about losing root etc. (sorry for my goldfish memory), the second try is ok but Busybox stills show "missing applets". However, you can continue to install Exposed Framework.
Big thanks to vbrsekhar!
Hi!
Today, while doing my daily reading blogs, I found an article by El Android Libre (in spanish) of an app for rooting Android devices quickly, so I decided to try it on my own and effectively, the application success to root my Fire HD 6!. His name is KingRoot. I'm very excited, it worked, and so far I have not noticed errors in the operation of my tablet (at least, today). I could say that this is the ultimate solution to root the Fire HD 6.
WARNING: This is a Chinese application, so I can not guarantee that it 100% safe to use . IF YOU INSTALL THIS, IT IS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR BUGS, BOOTLOOPS OR SOFTBRICKS..
Antivirus information:
If the antivirus software on your tablet shows this application as a virus, it is evident: for root you device, this app made a series of exploits to the operating system, and obviously the antivirus will display warnings before or during the process
I hope this can be useful to someone.
(Sorry for my English, I am using Google translator)
UPDATE 12-05-2015 02:01 AM
This process is not yet totally safe and we have very little information. Indeed, it is possible to root the Fire HD 6/7, but there's a very high risk of the device is unable to boot.
Unroot instructions:
Open the KingUser app
Press the Settings button (upper right corner)
Then press the "Remove Permission Root" option
Confirm and wait a few minutes.
Reboot
Yay!!! Thank you for posting this, I will try it now
great news! plz report how it goes thx.
Made a quick vid. Thanks for the info! How to Root Fire HD6: www.youtube.com/watch?v=KcQ30qcImJc
at last my hd6 is rooted now thx
Trying it on my HD7 now. Are we forced to use the king superuser or can we switch to superSu after?
skyhopper88 said:
Trying it on my HD7 now. Are we forced to use the king superuser or can we switch to superSu after?
Click to expand...
Click to collapse
The SU binary will be saved in the /system/bin folder after rooting the Fire HD 6, so I think that while this binary is not deleted you can use any other app for root management like SuperSu.
Suh-weeeet! Can confirm, works on HD7!
Confirmed, my HD6 (well, my mother's HD6) is now rooted :3
I seem to have lost root on reboot though
Or maybe it's because I un-installed the app?
Now to figure out how to get the Play Store working...
dmillerw said:
I seem to have lost root on reboot though
Or maybe it's because I un-installed the app?
Click to expand...
Click to collapse
I restarted my Fire several times throughout the day and still root.
What is the app you've uninstalled?
Here is a screenshot of Root Checker on my tablet right now.
Yeah, it's because I uninstalled KingRoot. Need to get SuperSU in here... somehow
dmillerw said:
Yeah, it's because I uninstalled KingRoot. Need to get SuperSU in here... somehow
Click to expand...
Click to collapse
Well, I try sideload SuperSu directly on my Fire but when I open it, the app ask me to update the su binaries, and a few seconds later shows me an error...
Any suggestions?
Has anyone successfully installed the Google Play Store?
Unfortunately, no. Android root stuff isn't something I'm too familiar with. I think we've still got a long way to go...
So what does the development road look like from here? Do we need a custom recovery before any roms start coming?
Thanks for this, I am excited to get home and play with my tablet!
argrr101 said:
So what does the development road look like from here? Do we need a custom recovery before any roms start coming?
Thanks for this, I am excited to get home and play with my tablet!
Click to expand...
Click to collapse
That's my understanding
argrr101 said:
So what does the development road look like from here? Do we need a custom recovery before any roms start coming?
Thanks for this, I am excited to get home and play with my tablet!
Click to expand...
Click to collapse
merlise said:
Has anyone successfully installed the Google Play Store?
Click to expand...
Click to collapse
dmillerw said:
Unfortunately, no. Android root stuff isn't something I'm too familiar with. I think we've still got a long way to go...
Click to expand...
Click to collapse
It seems you need to install an advanced recovery. The recovery that is built into our Fire does not allow flash apps, only allows to make a factory rese ...
The problem is that if you installed a wrong recovery, can bricking the system. Not sure if CWM Recovery works here.
andersonsalas said:
It seems you need to install an advanced recovery. The recovery that is built into our Fire does not allow flash apps, only allows to make a factory rese ...
The problem is that if you installed a wrong recovery, can bricking the system. Not sure if CWM Recovery works here.
Click to expand...
Click to collapse
I'm wondering how similar this Kindle is to the previous version software wise. Maybe some of the older methods will work now we have root?
This is the situation right now:
It is now possible to root the Fire HD 6 (and 7, as I'm reading)
The root is persistent while you don't uninstall the KingRoot app.
For now, you can not install the SuperSU app (throws an error)
Installing System Tuner Pro gives you the ability to uninstall system applications, review the logs of the kernel, modify the file build.prop, among other things (Other apps can also be used for do this...).
It is not possible (for now) install Gapps until to find an advanced recovery that it works with this tablet. Despite this, you can install some Google apps like YouTube, Google, and Google Search taking an alternative way. Read this thread for more information:
(Yes, there is still road ahead ...)
(Obvious words of legality, etc. I take no responsibility for anything that happens to your phone. I managed this on my own and everything worked. If you messed it up, I'm sorry, but it's not my problem)
Ok, now the good stuff! Hello all!
As you may know, user messi2050 managed to get us root on our phones (yay!). We don't yet have a custom recovery, and this is a usual requirement for Xposed, but fear not! I have figured out how to install it without a custom recovery. I'll try and be as clear as possible and provide all direct links to the files needed, but if something confuses you please let me know!
1. Root your phone
2. Download and install FlashFire
3. Samsung has weirdness associated with their roms and the way they do things under the Android hood, so you can't use the normal Marshmallow xposed module. You will need the Unofficial Xposed for Samsung Marshmallow by Wanam (HERE is a link directly to the APK you need)
4. Install the Xposed Installer for Marshmallow (Again, there is a direct link to the APK HERE[/URL
5. Open up FlashFire and press the (+) button. Select "Flash ZIP or OTA"
6. Choose the file downloaded in step 3
7. IMPORTANT! DESELECT "MOUNT /SYSTEM READ/WRITE"! Make sure everything is deselected! Then click the "✓"
8. Moment of truth y'all. Press the "FLASH" button at the bottom of the screen. You may get warnings, accept or clear them and continue
9. Your phone will shut down, show a bunch of text, and reboot after installing. THE REBOOT TAKES A LONG TIME, SEVERAL MINUTES AT LEAST! Don't be afraid, it will take quite a while to reboot. When it is done, it will "optimize apps" and then you should be all set!
Some xposed modules may not work for this phone! You run the risk of constant crashes and reboots with some modules. There are compatibility issues, especially if you neglect to read the warnings of each module, so read carefully! I'll give a list of modules I've installed with no issues, which will give yo a decent place to start (NOTE: There are individual settings in many of the modules, I haven't tried everything. So I can only tell you that the installation of the module is safe, NOT each setting).
Burnt Toast
Disable Fullscreen Keyboard
GPM Notification Seek Bar [L-M]
Greenify
Marshmallow SD Fix
Media Notification Seek [L-M]
NoSafeVolumeWarning
Notification Count
Wanam Xposed
XTouchWiz
If you happen to have success with any others, let us know and I'll update this list. Hope you guys enjoy, I'm so happy we finally got root and Xposed on this phone!
Followed your instructions (thanks) and have
BootManager
MinMinGuard
Swype Row and
Xinsta
Running.
It seems like most xposed modules work. Anyone interested should just follow the above instructions and give it a shot.
garyf said:
It seems like most xposed modules work. Anyone interested should just follow the above instructions and give it a shot.
Click to expand...
Click to collapse
Glad it works for you!
Yeah, I don't think there will be too many problems, I only mention the warning because if you're not careful, there are many modules that haven't been updated in years. If you're careless, you may install something from 2014 and it isn't compatible with Marshmallow and may cause constant crashes and force closes. Because we don't have a custom recovery, it's that much more important to be careful, as a mistake will requi9re a reflash and wipe everything. =S
Followed instructions and everything went just fine. Working great. Thank you!
EDIT: Having trouble finding Wanam Xposed. Can anyone help?
SonOfAnarchy0210 said:
Followed instructions and everything went just fine. Working great. Thank you!
EDIT: Having trouble finding Wanam Xposed. Can anyone help?
Click to expand...
Click to collapse
I see Wanam exposed in the list, however, it looks like XTouchWiz is similar, made by the same guy (Wanam), and is made for Marshmallow. Givev that a shot?
rainbowtuba said:
I see Wanam exposed in the list, however, it looks like XTouchWiz is similar, made by the same guy (Wanam), and is made for Marshmallow. Givev that a shot?
Click to expand...
Click to collapse
Yeah I must have been half asleep or something when I posted that because it is definitely there haha thank you though!
Opened Xposed this morning and this popped up. And when I go to downloads, there is no list. When I refresh, this keeps popping up. Any ideas as to what I should do?
Hi. Do you know how to install Xposed on j700f running mm?
Sent from my SM-J700F using XDA-Developers mobile app
Opened Xposed this morning and this popped up. And when I go to downloads, there is no list. When I refresh, this keeps popping up. Any ideas as to what I should do?
Click to expand...
Click to collapse
Sopn of Anarchy, I have no idea, sadly. Everything is working okay from my phone. No such issue
SankyLucky said:
Hi. Do you know how to install Xposed on j700f running mm?
Click to expand...
Click to collapse
If you have it rooted I would assume it's fairly similar. If there is any difference in the processor you will want to download the appropriate file, but using Flashfire and the Wanam version of xposed should be the correct move. Best of luck!
SankyLucky said:
Hi. Do you know how to install Xposed on j700f running mm?
Sent from my SM-J700F using XDA-Developers mobile app
Click to expand...
Click to collapse
Wrong thread ! For your answer here you go buddy: How to Root, TWRP and Install Xposed Framework on J7 (SM-J700F) (Screenshots inside)
Worked!
THANKS!
Hey, guys, just wondering if it's possible to flash this xposed through twrp? Or does having a working twrp alter the process or results in anyway?
acesavant00 said:
Hey, guys, just wondering if it's possible to flash this xposed through twrp? Or does having a working twrp alter the process or results in anyway?
Click to expand...
Click to collapse
Yes, I flashed this through twrp and got J700H xposed
Is there a way to keep the processor from overhearing?
SykkNyzz said:
Is there a way to keep the processor from overhearing?
Click to expand...
Click to collapse
Assuming you meant overHEATING on Snapdragon, try using the phone without aftermarket cover and without charger plugged in.
Also check out this extended guide: http://forum.xda-developers.com/galaxy-j7/how-to/marshmallow-battery-drain-overheating-t3439274
natri23 said:
Assuming you meant overHEATING on Snapdragon, try using the phone without aftermarket cover and without charger plugged in.
Also check out this extended guide: http://forum.xda-developers.com/galaxy-j7/how-to/marshmallow-battery-drain-overheating-t3439274
Click to expand...
Click to collapse
No, the phone heats up in my hand without charger and I don't even own a cover. I misspelled my word on accident so I understand why you would correct me.
---------- Post added at 01:42 PM ---------- Previous post was at 12:51 PM ----------
But that is now an old issue since I used the debloated version
I am running the modules and they all seem to work perfectly:
HideBatterylowAlert,
Neo power menu,
PMP,
YouTube background playback,
And flat style bar indicators.
Thank again!
I have the sm- j700p Boost and tried this but it bricks the phone. The apk installs fine but the phone never boots up fully after installing the framework. I tried with twrp and flashify.
worked perfect on J700T Tmobile.
maybe you should post this in the J700T Section or i can do it?
Solved
newsense2004 said:
I have the sm- j700p Boost and tried this but it bricks the phone. The apk installs fine but the phone never boots up fully after installing the framework. I tried with twrp and flashify.
Click to expand...
Click to collapse
OK finally got it working I don't know if I had the wrong file somehow or if using twrp to flash but I started over. Re-download the files and used flashfire to flash the zip. Worked perfectly this time, this phone has no compass sensor. Wish I knew that as I only wanted Xposed for the module that mimics a gyro.
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.
Hey everyone!
I have a G4 Play, trying to get xposed to work, but can't make it work no matter what.
I have already unlocked the bootloader, flashed a Deodexed stock image (i believe is this one https://www.androidfilehost.com/?fid=745425885120714391).
What I've tried so far:
- Install from Material xposed installer (arm SDK23 87.3), will not get past the boot logo (using magisk root).
- Install from recovery without magisk installed, same as above.
- Install it systemless through magisk, worked once and then black screen, any other attempt to install it leads to a black (blank?) screen, after boot animation, screen lights up, but nothing happens, cannot even turn off the screen and nothing happens even if I let it be for a couple hours.
I just really want to use xposed, I miss it so much from my previous devices, if someone can help or recommend a Working ROM for it (or with it already integrated), that would be so cool.
I have xposed moto g4 play since I needed it for pandora patcher. My current setup for months now is cyanogenmod-13-moto-g-play.
Did Xposed for marshmallow, android 6.0. I'm offering the option I've personally tried. What negative thing I experience in my whole setup is it downloads data on the background and I needed to force my cellular provider to disable my data. Only using it for wifi.
*I'm just returned from XDA from 3+ months of non-xda forums login so I needed to catchup, hoping others would suggest better setup than mine (moto g4 play CM 13 + xposed for MM).
Bump?
bidomo said:
Bump?
Click to expand...
Click to collapse
Unlocked device with stock ROM and SuperSU 2.8x branch. Xposed 87 went in without a hitch and has run smoothly for nearly a year. Guessing Magisk is the culprit.
Davey126 said:
Unlocked device with stock ROM and SuperSU 2.8x branch. Xposed 87 went in without a hitch and has run smoothly for nearly a year. Guessing Magisk is the culprit.
Click to expand...
Click to collapse
Will try your combo and see how it goes, will post back, thanks for letting me know
Davey126 said:
Unlocked device with stock ROM and SuperSU 2.8x branch. Xposed 87 went in without a hitch and has run smoothly for nearly a year. Guessing Magisk is the culprit.
Click to expand...
Click to collapse
Didn't work, systemless root 2.82 SR3 and xposed v87 SDK23 ARM, doesn't work, would not get past the boot logo, I don't know if it's the ROM or whats wrong.
bidomo said:
Didn't work, systemless root 2.82 SR3 and xposed v87 SDK23 ARM, doesn't work, would not get past the boot logo, I don't know if it's the ROM or whats wrong.
Click to expand...
Click to collapse
Using 2.82 stable systemless on pure stock. Probably need to roll back or pursue another Xposed friendly ROM. If you prefer stock (works well) one has the a question the value of going deodexed unless theming or have another specialized situation. Read up on transitioning between Magisk and SuperSU. Some claim a painful experience; others switch with ease. Possible Magisk remnants were present in your last test. Good luck.
Davey126 said:
Using 2.82 stable systemless on pure stock. Probably need to roll back or pursue another Xposed friendly ROM. If you prefer stock (works well) one has the a question the value of going deodexed unless theming or have another specialized situation. Read up on transitioning between Magisk and SuperSU. Some claim a painful experience; others switch with ease. Possible Magisk remnants were present in your last test. Good luck.
Click to expand...
Click to collapse
I'm gonna flash a fully stock ROM and directly try it, the reason a got a deodex is that I messed up the stock ROM and found it easier to install the deodex as I didn't have my laptop, will do as soon as I get back from work