Hi,
I'm new to ROMs modifications so don't judge me too much.
System Setup:
Note 4 N910C
Android 5.0.1 Lollipop stock N910CXXU1BOC3
Rooted with CF-Auto-Root-trelte-treltexx-smn910c
Custom recovery CWM 6.0.5.1
In order to deodex the system, I used the guide by townsenk - http://forum.xda-developers.com/sprint-galaxy-s5/general/how-to-deodex-lollipop-rom-t3065596, which is pointing to joeldroid's tool JoelDroid Lollipop Batch Deodexer V 2.5
After deodexing everything is back to normal, except of the SuperSU. The apps that were already granted the root access are seems to be working with no trouble, but for new apps that are requesting root access, there's no pop-up to grant it.
Any ideas how to fix it?
Exact same problem. Only thing in logs is Secure Settings at boot, everything else doesn't even get that far. No popups, nothing.
EDIT: Apparently installing the latest beta fixes it, as noted by someone in the Galaxy Tab forums. Worth a try.
EDIT 2: Yep, you just need the beta and its all hunky dory again.
If I remember right from when I deodexed my Xperia m2 during the process it removes supersu from the system during deodexing and before booting up my device i needed to re flash supersu then power up to keep root
D2303 18.3.1.C.1.15 kk deodexed, rooted, philz touch recovery, xposed, z1 bravia engine 2 + x-reality+ z3 super vivid, viper audio
I don't have this problem.My device is Galany Note 4,too
Thanks megaspel! The 2.49 BETA solved the problem.
Related
Hi everyone i just got a note 4 coming from a note 2. Ive had exposed running great for years. Ive noticed when i rooted and installed exposed 2.7 or 2.6.1 on kitkat my sms took forever to send and when im installing or updating apps they will start go half way sometimes to 90 percent then pause for 5 to 10 minutes then finish off. This is with no modules installed. When i uninstall exposed everything goes fast again as it should. I know i cant be the only one experiencing this. As im typing this my keyboard freezes sometime for a couple seconds at very consistent intervals. Just wondering if there is something i can do or just maybe there is still some bugs and conflicts with 4.4.4. Also im on a note 4 team mobile rooted and teamwin recovery installed stock rom. Thanks
Guys, I made xposed 2.6.1 work with private mode on stock rom 4.4.2. Here's how you can do it. But do it exactly step by step or you'll mess it up. I started with flashing stock rom from odin with a full wipe.
-Opened Shealth and configured.
-Do not open private mode or finger scanner. Do not try to configure these two.
-Root with CF root in odin.
-Open supersu. Update binary. Reboot. Disable knox.
-Install xposed 2.6.1. Install wanam xposed and go to security option. Disable knox and also disable secure storage. Reboot.
-Now configure private mode.
Tell me if it works for you.
LOST ROOT For Most but not all
Currently using [ROM][NH5][4.4.2] AllianceROM v5 – Lite on a Galaxy S5 SM G900T. After initial my initial setup was complete, I moved to the tweaker.
I started with SuperSU 2.16 and rooting was not an initial issue during the install of this ROM. Started to make adjustments in KTweaker and then found that root was denined for SetSPU. Learned that other apps that required root were also denied but KTweaker, ADB shell, IFont, and ROM Customizer were granted root.
Updated SuperSU 2.40 by flashing through recovery, TWRP 2.8.0.1 and after starting several times ended with the same results as indicated above. Tried various suggestions that I found and they did not work. Did notice that SuperSU 2.40 was working as an app but currently it is now back to 2.16.
How can I fix this and get back to FULL root access?
Update: Wipe device and reloaded the same custom ROM. Again the same thing happened after loading apps and configuring them. Now have six that are rooted correctly and then all further apps for rooting are being denied.
cyaclone said:
LOST ROOT For Most but not all
Currently using [ROM][NH5][4.4.2] AllianceROM v5 – Lite on a Galaxy S5 SM G900T. After initial my initial setup was complete, I moved to the tweaker.
I started with SuperSU 2.16 and rooting was not an initial issue during the install of this ROM. Started to make adjustments in KTweaker and then found that root was denined for SetSPU. Learned that other apps that required root were also denied but KTweaker, ADB shell, IFont, and ROM Customizer were granted root.
Updated SuperSU 2.40 by flashing through recovery, TWRP 2.8.0.1 and after starting several times ended with the same results as indicated above. Tried various suggestions that I found and they did not work. Did notice that SuperSU 2.40 was working as an app but currently it is now back to 2.16.
How can I fix this and get back to FULL root access?
Update: Wipe device and reloaded the same custom ROM. Again the same thing happened after loading apps and configuring them. Now have six that are rooted correctly and then all further apps for rooting are being denied.
Click to expand...
Click to collapse
Problem Solved: Changed Runtime from Delivk to ART and rebooted.....................Root Checker indicates ROOT ACCESS
cyaclone said:
LOST ROOT For Most but not all
Currently using [ROM][NH5][4.4.2] AllianceROM v5 – Lite on a Galaxy S5 SM G900T. After initial my initial setup was complete, I moved to the tweaker.
I started with SuperSU 2.16 and rooting was not an initial issue during the install of this ROM. Started to make adjustments in KTweaker and then found that root was denined for SetSPU. Learned that other apps that required root were also denied but KTweaker, ADB shell, IFont, and ROM Customizer were granted root.
Updated SuperSU 2.40 by flashing through recovery, TWRP 2.8.0.1 and after starting several times ended with the same results as indicated above. Tried various suggestions that I found and they did not work. Did notice that SuperSU 2.40 was working as an app but currently it is now back to 2.16.
How can I fix this and get back to FULL root access?
Update: Wipe device and reloaded the same custom ROM. Again the same thing happened after loading apps and configuring them. Now have six that are rooted correctly and then all further apps for rooting are being denied.
Click to expand...
Click to collapse
UPDATE History is repeating itself. Now that I am in Lollipop, that rooting problem has returned to both my Nexus 7 (2013) and Galaxy Tab S 10.5 in Lollipop ver 5.0, 5.0.2, and 5.1.1 No Runtime fix here. HELP
Here is a pic from Root Checker Pro
So... I had my N6 on 6.0 stock with root, made room in the system to install Xposed and had GB running great. Then I got greedy and installed 6.0.1, made room in system again and installed Xposed - on reboot I get constant NFC service errors and the phone is unusable. Go back to 6.0 and it works great. Tried installing a debloated stock 6.0.1 rom, w/ system-less root and get the same result after flashing Xposed.
Any insight? Tried searching with no results.
Seems like the issue was with the new root method. My solution was to remove the new root method using Update-unSU and then flash the Su2.52.zip. Xposed seems to be working fine now.
HTC-OH_SNAP said:
Seems like the issue was with the new root method. My solution was to remove the new root method using Update-unSU and then flash the Su2.52.zip. Xposed seems to be working fine now.
Click to expand...
Click to collapse
I am using sytemless root on 6.0.1 with xposed and don't have these issues
OK... The problem is back.
I was on 6.0.1 stick firmware - rooted with SU2.52 - removed the foreign language keyboards to make enough room in system to install the xposed framework (sdk78_arm version) - rebooted and get NFC services errors and phone is frozen.
Loaded the 6.0.1 lite rom - used unSU - installed SU2.52 and xposed and same result/error.
Loaded the 6.0.1 lite rom - left the system less root - installed xposed and same thing again.
Anyone have thoughts? I swear I am not that much of a newb but I can't figure this out. Even tried downloading a fresh copy of xposed but same thing.
HTC-OH_SNAP said:
OK... The problem is back.
I was on 6.0.1 stick firmware - rooted with SU2.52 - removed the foreign language keyboards to make enough room in system to install the xposed framework (sdk78_arm version) - rebooted and get NFC services errors and phone is frozen.
Loaded the 6.0.1 lite rom - used unSU - installed SU2.52 and xposed and same result/error.
Loaded the 6.0.1 lite rom - left the system less root - installed xposed and same thing again.
Anyone have thoughts? I swear I am not that much of a newb but I can't figure this out. Even tried downloading a fresh copy of xposed but same thing.
Click to expand...
Click to collapse
It is most likely not updated to work with those root methods yet. With the updates in security each android update is gonna need xposed to be updated. Even to the point that it may stop working all together. So I would get used to not having it to be honest. It is only a matter of time before it stops working all together.
Same issue happening to me, all roads pointing to systemless root. I'm sure Rovo will update. I'm using SuperSu v2.6.2r3 btw
Try to do factory reset throughout TWRP.
I had same problem yesterday. After I installed xposed framework, I could not use my phone due to NFC service error popup message. But now, everything seems okay after factory reset. - no more error message.
After 4 hours of searching: it seems, that I have a special problem though it is already asked on xda-developers, but not answered.
The Problem: if an app is needs root-rights, it is endless working without any result. Supersu does not receive any request.
What you have to know:
1. I am very familiar with rooting especially with Huawei-devices and with Lollipop
2. My current problem-device: Huawei y6 II compact - version LYO-L21
3. The phone is unlocked, TWRP is installed and works.
I have installed via TWRP Supersu 2.76.zip (tried also 2.78 and 2.82), installation was ok with zip-verification. The app appears, su is in /system/xbin. Supersu works so far, but apps can not gain root.
What I also tried so far: changing the superuser app, in Supersu "cleaning for new install via Playstore" and install supersu-app from Playstore, clean unroot (and new install via TWRP), and the whole bunch with delete cache and dalvik.
If supersu does a clean unroot, the the su-binary is gone, every app requesting root tells me: "no root available".
What I read sof far: the best versions for this phone should be 2.7.6 and 2.7.9, Chainfire writing about special problems with newer Huawei-firmware, but that doesn't tell me anything - my phone is not "newer" ...
I would like to start from scratch - flash the system-partition from stock - but I did not think of any such problems, so I did no backup of the system-partition. Has anyone got one?
Where can I look for further information? Does anyone have the same problem?
Spielmops
No Problem
Spielmops said:
After 4 hours of searching: it seems, that I have a special problem though it is already asked on xda-developers, but not answered.
The Problem: if an app is needs root-rights, it is endless working without any result. Supersu does not receive any request.
What you have to know:
1. I am very familiar with rooting especially with Huawei-devices and with Lollipop
2. My current problem-device: Huawei y6 II compact - version LYO-L21
3. The phone is unlocked, TWRP is installed and works.
I have installed via TWRP Supersu 2.76.zip (tried also 2.78 and 2.82), installation was ok with zip-verification. The app appears, su is in /system/xbin. Supersu works so far, but apps can not gain root.
What I also tried so far: changing the superuser app, in Supersu "cleaning for new install via Playstore" and install supersu-app from Playstore, clean unroot (and new install via TWRP), and the whole bunch with delete cache and dalvik.
If supersu does a clean unroot, the the su-binary is gone, every app requesting root tells me: "no root available".
What I read sof far: the best versions for this phone should be 2.7.6 and 2.7.9, Chainfire writing about special problems with newer Huawei-firmware, but that doesn't tell me anything - my phone is not "newer" ...
I would like to start from scratch - flash the system-partition from stock - but I did not think of any such problems, so I did no backup of the system-partition. Has anyone got one?
Where can I look for further information? Does anyone have the same problem?
Spielmops
Click to expand...
Click to collapse
I also successfully root a Huawei Y6 2 Duo CAM-L21 and there was no probleme. but i installed latest version of supersu, and also installed busyboxno probleme for the root. The probleme was the custom Rom.
I rooted my LG g3 (stock Lollipop) and flashed Supersu. It's been working well for some time, but lately, Supersu seems to be uninstalled (?) by the system, denying then root access to my apps (sd maid, titanium... ). What i do then is flash supersu again from TWRP , and all is back to normal... Untill Supersu is uninstalled again...
Is there anything i should do to avoid that? I'm thinking about installing Supersu as a system app. Would that matter?
Sent from this galaxy
pr1jker said:
I rooted my LG g3 (stock Lollipop) and flashed Supersu. It's been working well for some time, but lately, Supersu seems to be uninstalled (?) by the system, denying then root access to my apps (sd maid, titanium... ). What i do then is flash supersu again from TWRP , and all is back to normal... Untill Supersu is uninstalled again...
Is there anything i should do to avoid that? I'm thinking about installing Supersu as a system app. Would that matter? Sent from this galaxy
Click to expand...
Click to collapse
Your best bet is to post this question within the following thread.
https://forum.xda-developers.com/showthread.php?t=2947298
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
pr1jker said:
I rooted my LG g3 (stock Lollipop) and flashed Supersu. It's been working well for some time, but lately, Supersu seems to be uninstalled (?) by the system, denying then root access to my apps (sd maid, titanium... ). What i do then is flash supersu again from TWRP , and all is back to normal... Untill Supersu is uninstalled again...
Is there anything i should do to avoid that? I'm thinking about installing Supersu as a system app. Would that matter?
Sent from this galaxy
Click to expand...
Click to collapse
I have seen this on several Android 5.1 based systems following the release of SuperSU 2.7.9. I don't know if the most recent builds (2.8.2 SR5 as of this post) solved it. In my case I either reverted to the native root solution (for CM/Lineage based ROMs) or fell back to SuperSU 2.7.6