I recently rooted my N900T using CF root, and all went well. Now I would like to install the Xposed framework, and have no clue which file to install, as I have found dozens of them, as well as reading there are different instructions on Samsung.
This phone has a stock rom, running 5.0 and I'd rather leave it that way. I've heard about using either Odin or Flashfire to flash the xposed framework, then just installing the APK, but once again, which file out of the dozens out there is for this device?
My main reasons are ad blocking, and to disable the idiotic headphone warning (since I can't strangle the developer of that screw up, heh heh) I use xposed on my old Nexus 7 and love it, and afaik, it was easy to put it on there.
I have searched, but either didn't find what I was sure applied to my device, or didn't find it, so sorry if it's already out there.
Thanks for any help!
my understanding is that to install xposed on a touchwiz ROM (samsung's rom), it needs to be deodex-ed
(see first post here: http://forum.xda-developers.com/not...m-stock-lollipop-5-0-n900tuvufob6-v1-t3215571 )
look for deodex for instructions. Then the thread I linked should have the correct links to xposed install.
If you use an AOSP rom, you can install directly (no deode step required).
frenchy2k1 said:
my understanding is that to install xposed on a touchwiz ROM (samsung's rom), it needs to be deodex-ed
(see first post here: http://forum.xda-developers.com/not...m-stock-lollipop-5-0-n900tuvufob6-v1-t3215571 )
look for deodex for instructions. Then the thread I linked should have the correct links to xposed install.
If you use an AOSP rom, you can install directly (no deode step required).
Click to expand...
Click to collapse
Thanks for the info, about to give it a try.
SUCCESS! The file I was trying to flash was the wrong one, apparently. was trying to flash xposed-v75-sdk21-arm-arter97-snapdragon.zip, but I needed the V71 version instead.
v85 by dkcldark works without needing to deodex your ROM.
http://forum.xda-developers.com/xpo...g-lollipop-t3113463/post65373013#post65373013
I am currently using this on rooted stock FOL1 knox 0x0 flashed using FlashFire.
Interesting. As this phone was given to me, and is over 3 years old, I could care less about knox or warranties, but still nice to know it can be done. The only problem I had was the touchwiz launcher deciding to just stop working, and getting those idiotic prompts "unfortunately touchwiz home has stopped, if this inconveniences you, too bad". I fixed that by ditching touchwiz home and going with Nova launcher, which I like better anyway. I also like that this phone has an IR blaster, which has led to fun with random TV's!
I hope its ok to ask my question here in this recent thread. I'm messed up with xposed I think. I had xposed installed and working while on the NK3 firmware. I don't do a lot of updates to my device very often, but decided it was finally time to move to 5.0. So I downloaded FOB6, got it flashed, rooted, twrp installed, sd card fix. I totally missed the part where I should have disabled or removed xposed before I upgraded. Now I seem to be stuck. Can't quite figure out how to remove the old version and install newer version. I tried downloading from the post by dkcldark ref'd above. I installed using flashfire (first time using that), but it seems I still have the same older version still showing when I run the app.
If all else fails I guess I'll make a backup and factory reset, but I'm hoping there is an easier way. Thanks in advance for any ideas.
Related
I'm running CM10.2 and having difficulty trying to get Xposed framework installed. I've tried a couple different methods to no avail. The only thing I've found searching the forums is some speculation that the included Superuser in CM10.2 is what might preventing Xposed to install properly. If anyone could just point me in the right direction, then I'd be much obliged. I'm more than willing to read and find the answer for myself, but I've hit a wall and don't know where else to look for information regarding installing on 4.3.
Thanks in advance.
HampTheToker said:
I'm running CM10.2 and having difficulty trying to get Xposed framework installed. I've tried a couple different methods to no avail. The only thing I've found searching the forums is some speculation that the included Superuser in CM10.2 is what might preventing Xposed to install properly. If anyone could just point me in the right direction, then I'd be much obliged. I'm more than willing to read and find the answer for myself, but I've hit a wall and don't know where else to look for information regarding installing on 4.3.
Thanks in advance.
Click to expand...
Click to collapse
its probably not compatible yet, 4.3 is relativity new. Wait a bit for an update and im sure the problems will be fixed
---------- Post added at 08:38 PM ---------- Previous post was at 08:33 PM ----------
HampTheToker said:
I'm running CM10.2 and having difficulty trying to get Xposed framework installed. I've tried a couple different methods to no avail. The only thing I've found searching the forums is some speculation that the included Superuser in CM10.2 is what might preventing Xposed to install properly. If anyone could just point me in the right direction, then I'd be much obliged. I'm more than willing to read and find the answer for myself, but I've hit a wall and don't know where else to look for information regarding installing on 4.3.
Thanks in advance.
Click to expand...
Click to collapse
Seems i was wrong, only the installer apk isnt compatible, but the actual framework is. Look Around the xposed framework thread here and try to find the flashable zip installer they seem to be talking about. From a quick reading of the last page, it seems to break PA hybrid settings, so if your using paranoid android you might wanna avoid the framework all together
Tried it twice. Hung at the boot logo both times
Update: Found this thread with a modified Xposed Installer APK for 4.3 devices. It didn't work on it's own, but after downloading SuperSU from the Play Store and choosing to update the superuser binary in recovery from within the SuperSU app, I was able to install Xposed. After that, I installed the donate version of Greenify, selected the module in Xposed, and rebooted to activate it. At this point, I hit another hang at the boot logo. Instead of giving up, I wiped cache and dalvik cache from recovery and rebooted to fully functioning Xposed framework with the Greenify module activated and working.
I hope that helps anyone else that may be experiencing the same problem.
Hi there,
I have a SM-T805 from a few months, and I grew tired of its lags and sloppiness. I've tried to read many threads to find the most simple way too root, install TWRP and a ROM, but most of the threads are old and quite confusing.
So... could someone please tell me, step by step and with the proper links, how to ROOT and install TWRP in the easiest and most safe way?
Thanks a lot!
davidrf said:
Hi there,
I have a SM-T805 from a few months, and I grew tired of its lags and sloppiness. I've tried to read many threads to find the most simple way too root, install TWRP and a ROM, but most of the threads are old and quite confusing.
So... could someone please tell me, step by step and with the proper links, how to ROOT and install TWRP in the easiest and most safe way?
Thanks a lot!
Click to expand...
Click to collapse
You don't need to ROOT 'AND' install TWRP.
Just install TWRP and it will root for you.
You can use the version below if you wish which I built, I have updated the Super su root files and fixed an issue with the wrong reboot option showing - BOOTLOADER instead of DOWNLOAD mode.
Just install via ODIN then boot into TWRP, select reboot from within TWRP and it will ask if you wish to root your device. After that your device will be rooted with the latest updated root.
unofficial-twrp-2.8.5.0-chagall
Did it and installed Iron Rom. Thanks a lot
I have one problem... after I installed TWRP and rooted, with ANY rom I install, included the original one, I get the "no connection" error with every single app from google. In other words, I can't use the tablet. It's like Google knows the tablet is rooted and blocks it. How can I solve this?
Try resigning into your Google account. If that doesn't work clear cache and data for Google play services.
Sent from my SM-T805 using XDA Free mobile app
I found out that when I'm rooted, Android automatically sets my wifi connection behind a non-existent proxy. This happens in EVERY ROM I install, from the original one to Cyanogen. I just have to disable that proxy and everything works. WTF.
Hello everyone, please be patient with me as I am relatively new to modifying phones. However, I have spent a good portion of the past 1-2 weeks looking into this problem on XDA + google, and I am at the end of my rope.
Here is my problem (I'm sure you already know):
I have no current solution to installing a custom recovery on my phone. I really just want custom recovery to restore FULL backups via Nandroid or equivalent.
Here are my questions:
1) In download mode, Odin has no problem flashing an official image/firmware (tar.md5) to the phone. Is it possible to create my own image of my phone into one file and flash it via Odin to my phone when I would like to restore? I have a feeling that something in the phone checks the hash of the image (I'm sure that I'm not saying it right), and that, considering my image would be twice the size of the official, there would be no way to make my image pass using collisions or what not. However, this would probably be my first choice after safestrap (assuming that won't work), so let me know.
2) I have read that certain people with phones similar to mine (not my variant though) have successfully "swapped" the external and internal SD cards. If I remember correctly they just change a couple lines in void.fstab. If this could actually be done, I could easily restore a backup to the now external internal SD, then change the settings to reswap on reboot. I feel like this is too good to be true though, as I have not seen this as a solution to my specific problem online. Is this actually a suitable option?
3) Currently my phone model is not an officially recognized device which Safestrap will work on. However, I have read that it is possible to do on my model using the Safestrap version which corresponds to a close variant of my phone. Can this be done? Please let me know if you have any information on this.
4) I guess this would be the last resort. I'm pretty good at taking things apart, but even better I can put those things back together Is the internal "SD" really just an SD card deep inside the phone? Would it be possible to replace that card for the purpose of backing up?
Here are my phone specs:
-Samsung Galaxy S4 Mini (SCH-I435)
-The carrier is Verizon Wireless
-Android Version 4.4.2 (kitkat)
-Baseband Version I435VRUBOC1
-Kernel Version 3.4.0 [email protected] #1 Fri May 23 2014
-Build Number KOT49H.I435VRUBOC1
-Hardware Version I435.05
-Configuration version B13.SAM.SCHI435.0
-Needless to say, phone is rooted and has busybox + etc correctly installed.
Any help will be greatly, GREATLY appreciated -- even if that help is telling me that it isn't possible. I can't seem to give up on this.
Thanks,
Kurt
Help
Does anyone have any advice on this? I would REALLY appreciate it. Thanks again.
-Kurt
I'm also interested on this. Thanks for your efforts
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Kannz2 said:
Nope no recovery because the Verizon minis bootloader is locked. It can be rooted with kingroot i think its called and then switched to SuperSU by replacing it.(I used super sume pro to get rid of kr) ****!!After root install a application like "disable application [root]" and disabe all Knox applications and any unused apps.(look for a list of recommended apps to disable)
Click to expand...
Click to collapse
How did you switch it over to SuperSU? I tried, but when it tried updating the root binaries it couldn't continue because of KNOX, so I was stuck with Kingoroot's.
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Kannz2 said:
I used this method to replace KINGROOT NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243 with supersu. most other versions i tried didnt want to cooperate and would make me lose root after one reboot. also i bought the pro version of supersume pro its 4$ off google play.
Click to expand...
Click to collapse
I tried it with the free version they linked to and it de-rooted it, so maybe I'll try later when I have enough Opinion Rewards credit to get the pro version. That or it doesn't work on this phone with Kingoroot. (The Google Play description says it should do Kingoroot though.)
Did you download the correct version? The one off the kingroot site doesn't work for me. It just deroots. I still have root on both of my s4mini Verizon phones. Try this link to get a working one.HERE scroll down a bit and the different versions are there. Try each one starting with 4.5. Also remember to restart after you root with kingroot and install super sume after the restart.
I just had to re-image my phone, so I did it according to your directions. (Though with the free version still of super sume) and it worked, although it won't update to the newest root binaries. It fails when I try. Did you have this issue? Other than that, SuperSU works.
I updated using "normal" and it worked fine for me. Glad su works at least. also for one phone I did a full unroot factory reset and then I reflashed a tar with Odin. Did the normal root with kingroot 4.5. Restarted tried a few root things like no frills cpu thing then installed super sume pro. Did stage 1. An 2 then supersu started up automatically it asks to update (I think net connection is needed) *do update "normal" because there isnt any recovery. Uninstalled kingroot like supersume says. Did a few root things then restarted. (Checked for superuser after reboot and it stayed)
Hi,
I just got a fire phone and I'm facing multiple issues. It updated to 4.6.6.1 once i started it. Now I want it to act like a normal android phone so I installed google now launcher.
Next thing i wanted to do is to customize the laucher. So I did research how to root it. Did it with kingroot and afterwards followed various instructions to change to superSu. Non of them worked. Neither via adb nor SuperSU me nor the terminal version. only rooted when on kingsroot. SuperSU binaries also would never succesfuly update. Anyways.
So after I got the root, I wanted to install Xposed Framework to finally customize the launcher. Now xposed is saying, that it is not (yet) compatible wit the ANdorid SDK Version 19 or my Prozessor architecture. (armeabi-v7a)
I'm running the phone on german language. Don't know what to do anymore with both. SUpersu and Xposed. Appreciate any help.
So you already bought Super-Sume-Pro? Good, because removing / replacing Kingroot was possible even with the (early) free version of Super-Sume (9.1.6).
Download this old version* of Kinguser.
Yes, like always, it's classified as a virus / exploit / PUP, because it uses very aggressive methods of achieving root.
"But Bingo, this is only Kinguser, I need Kingroot."
No you don't. I used this combo many times, it always worked, from the latest version down to Fire OS 4.6.1 when I first tried it.
Uninstall your current version of Kingroot / Kinguser and remove the leftover folders from the internal storage.
Install the old version (disable auto update within in the app, it can be quite annoying), let it "achieve" root, disable WiFi if you want.
Run Super-Sume. It will have no problem replacing Kinguser with 2 steps.
Download this compatible version of the Xposed Installer.
Install framework, etc. You know the drill.
For BusyBox, I'd recommend either Stericson's version or Meefik's.
I tested one of my devices with 4.6.6.1 and the above mentioned customizations (mainly to enjoy microG on Fire OS ^^), so I can say it definitely works.
* Had to use OCH, because the "good guys" like Dropbox and Google Drive won't allow hosting / linking this file, since it's a bad azz virüs.
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot.
Click to expand...
Click to collapse
Ugh, so many letters, I'm so confused, please... no more, let's stay with "dumb it down". This saves time so I can roll around in my own feces. :victory:
Plonko said:
I always found W0lfdroid's script to be quite effective and efficient in removing Kingroot:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Click to expand...
Click to collapse
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
coolni said:
W0lfdorid was one of the versions i tried. no success. I can start the script but then it says failure and every single steps fails. I finally made it to the supersu installed, but it wont update the binaries. installation always failed
Click to expand...
Click to collapse
Hmmmm...I don't know what to say. I just used it today after returning a phone to stock Fire OS for my niece. The only thing I can think of is I'm using an earlier version of Kingroot? I'm using KingRoot-4.1.0.524.apk if that matters. I can try to PM it to you, but I'm not sure it will work because, as Bingo mentioned, it is seen as a virus by most servers.
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Bingo Bronson said:
Yup, I also used the oldest version I had on my PC, this way I can avoid the cat and mouse game between Kingroot and Super-Sume ^^ ... well, for the Fire Phone and some "older" KitKat devices that is.
But since 'coolni' popped his Fire Phone cherry just recently, he naturally went for a current version of Kingroot and he's also on the latest Fire OS release; thought process = better bring the big guns so that root is guaranteed.
Click to expand...
Click to collapse
can anybody help to root 4.6.6.1 ?
Kingroot 4.0.0.233 from zip file did not work on my phone with 4.6.6.1.
Having problems on custom recovery
Hello sir I am using amazon 4.6.6.1 almost 1 year ago I have backed up my custom recovery from flashify and deleted accidentally now I need that but can't do anything I have tried most things to get back but can't and also can't root my phone with king root I am installing it but it's saying that app not installed any solution please my email is [email protected]
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app