Related
youtube. com/watch?v=rRkAHw_GmIs (sorry won't let me post the link)
I used this website to root my HTC One, and tried to verify my root access
Could someone tell me what I (the video) did was wrong?
The only different thing I did other than what was shown on the video was using 2.6.3.0 twrp recovery instead of 2.5.0.0 and that was because I was unable to use the touchscreen.
Note: I am not running Kitkat
Did you flash SuperSU or superuser from recovery?
BD619 said:
Did you flash SuperSU or superuser from recovery?
Click to expand...
Click to collapse
I did
Also when I open the app, it says "there is no SU binary installed, and SuperSU cannot install it. This is a problem!"
noobdroider said:
I did
Also when I open the app, it says "there is no SU binary installed, and SuperSU cannot install it. This is a problem!"
Click to expand...
Click to collapse
Go back into recovery and flash SuperSU again
BD619 said:
Go back into recovery and flash SuperSU again
Click to expand...
Click to collapse
Did it and it said successful and I tapped reboot after it said successful, still didn't work though
Fix: I uninstalled SU from my phone and installed Superuser instead, flashed it and it works fine
AT&T HTC One m7 running ARHD 53.0 with TWRP. After I install the Xposed Installer apk I cannot Install/Update at all.
I press the Install/Update button, it asks me for SuperU permissions and when I grant it permission my phone reboots.
No updates are applied after the reboot, as my app_process and XposedBridge.jar are still "--" ...
I have tried countless times with different versions. My apologies if this thread was already created.
I've also tried every kind of installation process. (Recovery from zip auto, recovery from zip manual)
It just causes my phone to reboot every time with no updates. Any help would be appreciated.
Thanks in advance.
Sounds like a function related to S-On, but if not even installation via recovery works (which doesn't write to /system), I'm afraid I can't help you.
xiiKilo said:
AT&T HTC One m7 running ARHD 53.0 with TWRP. After I install the Xposed Installer apk I cannot Install/Update at all.
I press the Install/Update button, it asks me for SuperU permissions and when I grant it permission my phone reboots.
No updates are applied after the reboot, as my app_process and XposedBridge.jar are still "--" ...
I have tried countless times with different versions. My apologies if this thread was already created.
I've also tried every kind of installation process. (Recovery from zip auto, recovery from zip manual)
It just causes my phone to reboot every time with no updates. Any help would be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
I have a similar problem, only with the international version. Try soft rebooting the device, not fully rebooting. It also might not work if you use the Xposed app to soft reboot, try another if you have more problems.
I had the exact same problem after I installed the new Revolution HD 70.0 yesterday. I tried many times to reinstall and reboot but had no luck.
modules not working with xposed update
i have htc desire x rooted stock rom 4.1.1, i had gravity box and xblast module up an drunning however after upgrading xposed to 2.6 they bot stopped working, i tried reinstalling and rebooting modules are not working. is there any way around? please help.
Xposed log please. Also, are the version numbers in the install section green after rebooting?
I've been having the same issue with my m8. For me, XposedBridge.jar is green at version 54, but app_process is a red ---.
Here is my log.
-----------------
May 18, 2014 8:30:07 AM UTC
Loading Xposed v54 (for Zygote)...
Running ROM 'KOT49H.H16 release-keys' with fingerprint 'htc/m8_google/htc_m8:4.4.2/KOT49H.H16/326432:user/release-keys'
Errors during Xposed initialization
java.lang.UnsatisfiedLinkError: Native method not found: de.robv.android.xposed.XposedBridge.cloneToSubclassNativeLjava/lang/Object;Ljava/lang/ClassLjava/lang/Object;
at de.robv.android.xposed.XposedBridge.cloneToSubclassNative(Native Method)
at de.robv.android.xposed.XposedBridge.cloneToSubclass(XposedBridge.java:789)
at de.robv.android.xposed.XposedBridge.hookResources(XposedBridge.java:365)
at de.robv.android.xposed.XposedBridge.initXbridgeZygote(XposedBridge.java:267)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:117)
at dalvik.system.NativeStart.main(Native Method)
-----------------
Click to expand...
Click to collapse
I've tried setting everything in /system to rwx and all three installations methods still fail. My m8 is still S-ON.
Katharta said:
I've tried setting everything in /system to rwx and all three installations methods still fail. My m8 is still S-ON.
Click to expand...
Click to collapse
When you tried manual installation, did the output in recovery show a message that the file was flashed successfully?
everyone here who has problem install the installer.apk, please check your device if it is rooted or s-off. the apk only work with rooted or s-off device. for those has s-on device, you need install the xposed from recovery with a zip file. I just flashed the ARHD 70.0, still looking for a xposed 2.6 zip file. please if anyone know where to get one, please post here.
Same problem here with ARHD 70
28mufields said:
still looking for a xposed 2.6 zip file. please if anyone know where to get one, please post here.
Click to expand...
Click to collapse
Choose manual flashing as installation mode, then it will be written to your SD card. The zip itself doesn't work without prior installation with in this mode.
So is there no hope for us having the Xposed framework again? (HTC One M7 Same issue)
For some reason with 2.6.1 recovery loops without installing if you choose automatic recovery method. I was able to complete it manually. Note that I'm already S-OFF so technically I didn't have to go this route but I did anyways because I was using recovery before I went S-OFF.
Yes. Xposed will install via recovery if you are not S-OFF yet. Alternatively use a kernel that allows writing to /system when S-ON is active.
Anyways those looking for the zip to flash should pay attention to the location of the data storage for the zip. I guess it isn't being copied to the root of the sdcard anymore?
Location: /sdcard/Android/data/de.robv.android.xposed.installer/files
In there you should have Xposed-Installer-Recovery.zip that you need to flash in recovery mode.
shinji257 said:
For some reason with 2.6.1 recovery loops without installing if you choose automatic recovery method. I was able to complete it manually. Note that I'm already S-OFF so technically I didn't have to go this route but I did anyways because I was using recovery before I went S-OFF.
Yes. Xposed will install via recovery if you are not S-OFF yet. Alternatively use a kernel that allows writing to /system when S-ON is active.
Anyways those looking for the zip to flash should pay attention to the location of the data storage for the zip. I guess it isn't being copied to the root of the sdcard anymore?
Location: /sdcard/Android/data/de.robv.android.xposed.installer/files
In there you should have Xposed-Installer-Recovery.zip that you need to flash in recovery mode.
Click to expand...
Click to collapse
I've flashed that and still have a blank for app_process.
Bullonie said:
I've flashed that and still have a blank for app_process.
Click to expand...
Click to collapse
What did the text say when you flashed it? Did it say that everything was successful and that you should reboot now?
rovo89 said:
What did the text say when you flashed it? Did it say that everything was successful and that you should reboot now?
Click to expand...
Click to collapse
Ahh, actually not. It just rebooted nearly right away when I confirmed the flash. I haven't flashed anything in awhile so I forgot that there was a screen after. So I guess it didn't actually flash. :\
Bullonie said:
Ahh, actually not. It just rebooted nearly right away when I confirmed the flash. I haven't flashed anything in awhile so I forgot that there was a screen after. So I guess it didn't actually flash. :\
Click to expand...
Click to collapse
Same here. Dosn't Flash - goes directly into reboot when trying to flash with twrp.
That's the zip file: h**p://goo.gl/NztMbZ
is possible changed icon theme on Stock rom sense 6 rooted with xposed module ? exsist one module for this mod?
I have the Same issue with ARHD 51.0. After updating to Version 2.6.1 no modules are working and it seems the installer simply didnt Flash. Downgrading back to 2.5.1 did Not help either.
NOKIA 5110 > NOKIA 6310i > MOTOROLA RAZR > NOKIA 6301 > HTC Hero > HTC Desire HD > HTC One M7
This will probably apply to you as well: http://forum.xda-developers.com/xposed/xposed-framework-install-issue-t2759840/post53184020
Hi,
I just installed the Xposed installer.
I'm trying to install the XPosed framework. Tried the classic way, but after reboot the framework is not installed; then tried with the recovery, but it says "installation aborted". The phone is rooted, of course.
Please help me
What phone do you have? What recovery? You need to have a custom recovery to flash it
GermainZ said:
What phone do you have? What recovery? You need to have a custom recovery to flash it
Click to expand...
Click to collapse
Phone: huawei g700 (4.2). I don't have any custom recovery, I think, but in the instructions for the installation of Xposed this wasn't mentioned
ouardo said:
Phone: huawei g700 (4.2). I don't have any custom recovery, I think, but in the instructions for the installation of Xposed this wasn't mentioned
Click to expand...
Click to collapse
How is your phone rooted, if not from a custom recovery? Or did you revert from the custom recovery to a stock recovery after rooting?
If you selected "Classic" install in Android, it tries to install directly via root methods. This fails if you do not have root.
If you selected recovery method, an installationfile is saved to your SD card, and that is then automatically installed when the phone reboots (into the custom recovery you installed). If no custom recovery is installed, then the recovery method is pointless as the means by which the installation takes place, is not there at all (the custom recovery).
Please download Root Checker ( https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck ) - does it verify you have root?
Kind Regards
TwinAdk
TwinAdk said:
How is your phone rooted, if not from a custom recovery? Or did you revert from the custom recovery to a stock recovery after rooting?
If you selected "Classic" install in Android, it tries to install directly via root methods. This fails if you do not have root.
If you selected recovery method, an installationfile is saved to your SD card, and that is then automatically installed when the phone reboots (into the custom recovery you installed). If no custom recovery is installed, then the recovery method is pointless as the means by which the installation takes place, is not there at all (the custom recovery).
Please download Root Checker - does it verify you have root?
Kind Regards
TwinAdk
Click to expand...
Click to collapse
I used FRAMAROOT, which is the easiest way. The root is verified. And the system recovery is there, I also tried to manually flash the zip, but it says "installation aborted". If I choose the classic mode, it reboots but with no results, as the framework is not present, even if the two voices (app process and xposedbridge) are green and active.
I have z2 with rooted, I just installed xposed, but when I am trying to update framework work it shows me this error,.
Now I tried with a custom recovery, this time it flashed the zip and everything seemed alright, but then again when rebooted, in the Xposed launcher it seems like no framework has been installed, and there is still the red error :crying:
GermainZ said:
What phone do you have? What recovery? You need to have a custom recovery to flash it
Click to expand...
Click to collapse
Done, but with no results as I said
sandy.parulekar said:
I have z2 with rooted, I just installed xposed, but when I am trying to update framework work it shows me this error,.
Click to expand...
Click to collapse
Don't crosspost!
ouardo said:
Now I tried with a custom recovery, this time it flashed the zip and everything seemed alright, but then again when rebooted, in the Xposed launcher it seems like no framework has been installed, and there is still the red error :crying:
Click to expand...
Click to collapse
Which "red error" are you referring to? If it's just the red text on the welcome screen, but the version number is green, check the log section if there is any error message there. You might have run into the issue "ClassCastException" that is mentioned in the FAQ.
ouardo said:
I used FRAMAROOT, which is the easiest way. The root is verified. And the system recovery is there, I also tried to manually flash the zip, but it says "installation aborted". If I choose the classic mode, it reboots but with no results, as the framework is not present, even if the two voices (app process and xposedbridge) are green and active.
Click to expand...
Click to collapse
There is an old and a new way to install things in a recovery, and xposed uses the new way cannot remember the names or the difference), but your recovery must support it. What recovery did you flash, and what error do you get?
GermainZ said:
What phone do you have? What recovery? You need to have a custom recovery to flash it
Click to expand...
Click to collapse
rovo89 said:
Don't crosspost!
Which "red error" are you referring to? If it's just the red text on the welcome screen, but the version number is green, check the log section if there is any error message there. You might have run into the issue "ClassCastException" that is mentioned in the FAQ.
Click to expand...
Click to collapse
Yes, that's the error. So there's no way to get it working? In the settings I can't see any option to disable the resources API, as suggested in the FAQ.
Gesendet von meinem GT-N7000 mit Tapatalk
I have micromax canvas play q355.....custom recovery is not available for my device...........is there any other way to install xposed framework?
Hi,
Well, I do have one recovery - cyanogen recovery, all others are gone.
With cyanogen I can't flash gapps or tangerine kernel,so I need my old ones back.
How it happened? Flashed FlexOS,after reboot they were gone, replaced by cyanogen recovery.
Any help would be appreciated.
Thanks
jaretti said:
Hi,
Well, I do have one recovery - cyanogen recovery, all others are gone.
With cyanogen I can't flash gapps or tangerine kernel,so I need my old ones back.
How it happened? Flashed FlexOS,after reboot they were gone, replaced by cyanogen recovery.
Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Use Rashr app from playstore to flash twrp or philZ
don't have app store, in fact don't have any gapps as cannot install them in cyogen recovery. when download apk. file get "Cant open" message.
jaretti said:
don't have app store, in fact don't have any gapps as cannot install them in cyogen recovery. when download apk. file get "Cant open" message.
Click to expand...
Click to collapse
you have to install tangerine if you use lollipop ....go into fastboot mode flash the kernel via fastboot ..reboot and you have twrp or philz
Is it possible that I've lost root? Cause that what root checker says.
P.s. managed to install gapps,will try flashing kernel like suggested tomorrow. Any links on how to do it?
Thanks guys
jaretti said:
Is it possible that I've lost root? Cause that what root checker says.
P.s. managed to install gapps,will try flashing kernel like suggested tomorrow. Any links on how to do it?
Thanks guys
Click to expand...
Click to collapse
i have did this from a long time so forgive if it didn't work for you>>> form pc download this zip that i uploaded it for you(https://mega.co.nz/#!y51TmaJR!gSWCWbF_6d3JKbkyjgNzhdfBoKakFvNCCFFvBfRl-cY) extract to C:\fastboot then move the kernel.elf if is it tangerine it will be like this (tangerine.elf)>>>press ctrl+shift on the keyboard and then press open command window here then type: fastboot flash boot (the kernel name.elf) when it's done type fastboot reboot
example: fastboot flash boot tangerine.elf
p.s you have to install the drivers for you phone google it or maybe(Connect your Xperia SP via USB. (Don't forget to enable USB Debugging)
Then run the Software (http://adbdriver.com/downloads/) and choose ur phone, which should be listed in the list.
i hope i helped with this if it didn't work so i'm sorry my friend for wasting your time
good luck :good:
Hi, it's all sorted now.
if someone have same problem this is what I've done:
installed gapps aroma as other packages wouldn't install from cyanogen recovery, then flashed super su also from recovery. after that I was able to install phillz recovery using rashr app from Google store. then from phillz installed tangerine kernel. all good now,
thanks everyone!
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
If you originally patched the Samsung firmware and rooted under OneUI, that same version of Magisk will show up once you flash any GSIs.
Besides that, there's no other way that I know of since you can't simply sideload Magisk through TWRP for this device
You'll have to start over by patching the firmware and flashing through Odin to get back to stock. From there, set up Magisk like you'd normally do. Once that's done, you can proceed and use the same guide to get LOS back and be fully rooted with Magisk
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
You just need to install the magisk apk and run it. There is no need to patch anything.
lewmur said:
You just need to install the magisk apk and run it. There is no need to patch anything.
Click to expand...
Click to collapse
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Simply installing the Magisk APK is not the same. To install Magisk completely to your system you must patch the image.
For this device, you need to complete the patching process first with Samsung's firmware under OneUI. Once that's done, you can return back to LOS and a patched version of Magisk will be waiting for you to install
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
lewmur said:
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
Click to expand...
Click to collapse
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
itscryptic said:
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
Click to expand...
Click to collapse
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
lewmur said:
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
Click to expand...
Click to collapse
I do not see a direct option, it is only showing select a file to patch when I tap install...
itscryptic said:
I do not see a direct option, it is only showing select a file to patch when I tap install...
Click to expand...
Click to collapse
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
lewmur said:
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
Click to expand...
Click to collapse
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
That's normal. Ignore it.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
How did you flash the Magisk.apk with twrp?
gguman said:
How did you flash the Magisk.apk with twrp?
Click to expand...
Click to collapse
Use the "Install" button to flash as if it were a zip file.
lewmur said:
Use the "Install" button to flash as if it were a zip file.
Click to expand...
Click to collapse
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
So long as you know where it is, you should be able to browse to it. You might have to "Select storage" to switch between Internal and Micro SD. If it doesn't show, try renaming it from .apk to .zip.
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
You have to rename it as a ZIP, you cannot flash APK files
kevinco1 said:
You have to rename it as a ZIP, you cannot flash APK files
Click to expand...
Click to collapse
Not necessarily so. I've installed apk files in TWRP many times. It depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Just curious, what other apps can you do this besides Magisk?
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Successfully installed apk:
0) stock firmware
1) install TWRP
2) Formated data
3) Wipe all data
4) adb push magisk.apk to /
5) Install apk from TWRP
6) reboot to fastboot
7) flash LOS20