Hi Guys,
I'm having problems with my Nexus 5, which is running a custom recovery after root access, with CM mode. I then installed Franco Kernel, which worked on the 2nd try. NOW I want to tweak Franco, BUT my SuperUser app isn't allowing it access. I've tried cleaning the superuser logs, I even went into settings to make sure it allows everything, but nothing is happening.
How can I re-gain access to Franco Kernel (I contacted him, but never got anything in return..., and I have the paid app)
Thanks for your help
JustinMorinC said:
Hi Guys,
I'm having problems with my Nexus 5, which is running a custom recovery after root access, with CM mode. I then installed Franco Kernel, which worked on the 2nd try. NOW I want to tweak Franco, BUT my SuperUser app isn't allowing it access. I've tried cleaning the superuser logs, I even went into settings to make sure it allows everything, but nothing is happening.
How can I re-gain access to Franco Kernel (I contacted him, but never got anything in return..., and I have the paid app)
Thanks for your help
Click to expand...
Click to collapse
flash SuperSU with your recovery http://download.chainfire.eu/supersu
Thanks + Recovery
Thanks, will try that, how do it save all my data?
JustinMorinC said:
Thanks, will try that, how do it save all my data?
Click to expand...
Click to collapse
huh? you wont lose any data from flashing it. you will have yo give permission to your root apps when you open them the first time.
Related
Hey Guys,
i just got my OPO. Unlocked the bootloader, installed TWRP, installed custom kernel and Superuser. After a reboot everything seems to be fine with root but after some minutes of usage i loose root. for example after reboot i can use titanium for like 10 minutes and then my root is gone. in every app not just titanium. any solution?
thank you and regards,
blax
Edit: I had to disable an option for CM in SuperSU settings
Could you please Elaborate?
blax123 said:
Hey Guys,
i just got my OPO. Unlocked the bootloader, installed TWRP, installed custom kernel and Superuser. After a reboot everything seems to be fine with root but after some minutes of usage i loose root. for example after reboot i can use titanium for like 10 minutes and then my root is gone. in every app not just titanium. any solution?
thank you and regards,
blax
Edit: I had to disable an option for CM in SuperSU settings
Click to expand...
Click to collapse
Please tell me exactly what you did?
Umair Kamil said:
Please tell me exactly what you did?
Click to expand...
Click to collapse
My phone is German, sorry for that but just look at the screenshorlt, you gonna find it too. You have to normally root your phone. There are several guides in the forum, just search for them. And after rooting you have to go to SuperSU settings and untick the setting for CyanogenMod.
Sent from my Carbonized Nexus 4
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
I'm having issues with Titanium Backup on the latest nightly.
It installs and it gets root fine, but restores just hang at the first app forever.
Anyone else tried a TB restore after flashing cm-12-20150116-NIGHTLY-bacon.zip?
Did you click on the pop-up that asks if you want Google to inspect the sideloaded apps?
I missed that pop-up one time and it was just waiting for an interaction before it started restoring
I could not do it on 20150106-NIGHTLY without installing SuperSu. With SuperSu TB warks fine.
@Psichi
I don't even get to this point.
@elmerq
I hate that. I was using supersu before and it was causing all kinds of issues between it and the superuser that's baked in.
Is there anyway to update the binary on the baked in superuser?
No idea :/
I have just bought 1+1 and found only this way to use TB.
elmerq said:
I could not do it on 20150106-NIGHTLY without installing SuperSu. With SuperSu TB warks fine.
Click to expand...
Click to collapse
Flashing Chainfire Supersu did the job.
This is big a problem for CM roms imo. It's fine to have superuser preinstalled. But, there needs to be a way to use an alternate su app that doesn't cause issues.
Try this app instead:
http://forum.xda-developers.com/android/apps-games/app-backup-app-backup-restore-t2898674
Transmitted via Bacon
Hi all,
Wondering if any of you guys might know what's up with my OPO...
Today I noticed when running a root-dependent app that some of its functions didn't work, so I looked for SuperSu in my app tray - not there. Then I ran Root Checker - no root. Odd, I haven't done an OTA lately, and had root yesterday.
Undeterred, I did what I do when I do lose root through an OTA - I rebooted into TWRP recovery, flashed a version of a SuperSu zip, wiped dalvik and rebooted.
SuperSu was still not there on reboot, and Root Checker still gave me a negative. So I'm puzzled. I wondered perhaps if it was something to do with Xposed, so I uninstalled the framework and reflashed SuperSu. Still hasn't worked.
Any ideas? Even to determine diagnostically why I lost root? Only notable update I can think of is a battery saving app through the Play Store, which has a corresponding Xposed module - I got a notification about the module earlier, saying I needed to reboot for changes to take effect. But this might be a red herring, since the relevant module was never enabled anyway.
I'm super stumped. Any suggestions will be greatly appreciated!
Check dev options and enable root from there.
Sent from my bacon!!!!!
I don't have an option to enable root from dev options menu - unless I'm missing something?
Okay - resolved. Really weird. Had to download SuperSu from the market, open, allow superuser rights to Root Checker, then verify root.
I don't understand why SuperSu wasn't available before, having flashed it. I also don't understand why various root functions weren't enabled before :/
Oh well, working rooted phone again!
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
vsaery said:
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
Click to expand...
Click to collapse
Same issue with the note 4
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
parth7667 said:
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
Click to expand...
Click to collapse
this didn't work.. i tried installing franco kernel but still not logging in Snapchat
vsaery said:
this didn't work.. i tried installing franco kernel but still not logging in Snapchat
Click to expand...
Click to collapse
it worked.. thanks alot man.. i had to unroot again and then flash franco kernel to make it work
parth7667 said:
It is an issue of kernel not passing "SafetyNet", which required to complete the login of Snapchat and some other applications.
Easy fix that worked for me on other ROM with same issue is,
1.) Download latest Franco Kernel (Franco Kernel currently passes SafertyNet, that's why).
2.) Backup your "Boot" partition in TWRP.
3.) Flash Franco Kernel. Then reboot.
4.) Login in your Snapchat, it should work this time around.
5.) Go back to TWRP, and use restore function to restore the previous "Boot" partition to get LineageOS kernel back.
Let me know how it goes.
Click to expand...
Click to collapse
this works.. thanks
vsaery said:
this works.. thanks
Click to expand...
Click to collapse
No problem. Glad to be of service.
vsaery said:
I just installed Lineage OS on my Nexus 5 and i checked via root checker my phone is not rooted. But still whenever i try to login in Snapchat it doesn't let me in. I tried many solutions like removing root access from SuperSu(when it was rooted) but still it doesn't help. So can anyone help with that?
Click to expand...
Click to collapse
Do you have Xposed installed?
If yes, this is the issue. I have read, that the only soluton is to unistall Xposed, then install Snapchat, then login normally, then download Titanium Backup and backup the app, then reinstall xposed and use the backup to get yourself logged in.
Because this was too bothersome for me, I just installed CASPER, which is an alternative client for Snapchat, just make sure not to save too many snaps, you could get banned for that (I also read somewhere), in fact disable auto downloading snaps in the settings.
Nottrueuser said:
Do you have Xposed installed?
If yes, this is the issue. I have read, that the only soluton is to unistall Xposed, then install Snapchat, then login normally, then download Titanium Backup and backup the app, then reinstall xposed and use the backup to get yourself logged in.
Because this was too bothersome for me, I just installed CASPER, which is an alternative client for Snapchat, just make sure not to save too many snaps, you could get banned for that (I also read somewhere), in fact disable auto downloading snaps in the settings.
Click to expand...
Click to collapse
thanks for answering but i already found a solution.. you can check in other comment.
Franco kernel worked for me on my Nexus 5.
If you get logged out of Snapchat, the process must be repeated.
Curiously, my Nexus 7 can log on to Snapchat with the lineage kernel from lineage-14.1-20170228-nightly-flo-signed.zip ROM, no Franco kernel required.