Hey,
EDIT!: I restored one of my backups with ROM Manager (Which still could restore ROMs? ) and i got my root access back! =)
Sorry if theres already a thread about this somewhere which Google haven't been able to find.
About a month ago i successfully rooted my phone using revolutionary. I tried out a few ROMs and ended up with MIUI 1.11.25, and suddenly i lost root access. Im not sure when this happened, it might have been when i updated from MIUI 1.11.18 to 1.11.25, which i did a couple of days ago,(I wiped dalvik cache and flashed with ROM Manager since the buildt in updater didn't work) or when i tried to update Busybox with an app from the market... :/
Weird thing is, Superuser runs perfectly normal, while almost every other root app i have tells me i need root access to use the application. I tried updating and installing the Su zip file (Binary?) and updating Superuser, but it didn't work .
Another weird detail is that root checker says "Congratulations! You have root access!" While ROM Manager can't run fix permission.
Should i reflash my ROM or a backup? Or is there some weird simple fix to this (Please!)?
Im not a wiz at rooting so if your able to, please put it in simple words
Thanks,
Mikkel
try tools>superuser>menage permissions
Adidas108 said:
try tools>superuser>menage permissions
Click to expand...
Click to collapse
I already tried to look around in the apk and it's settings, but with no luck. As I said earlier superuser runs perfectly : /
Thanks tho
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.
I installed link2sd, everything was working perfectly, until noobie me switched apps to system apps (mainly Google play store) and the started breaking, tried to change them to user apps, and they disappeared. How would I go about getting tem back, would I have to flash gapps? AA did just unlock the bootloader and made a cwm for my phone if I need to.
sent from my lgms323 towelrooted waiting on custom rom
brentwago said:
I installed link2sd, everything was working perfectly, until noobie me switched apps to system apps (mainly Google play store) and the started breaking, tried to change them to user apps, and they disappeared. How would I go about getting tem back, would I have to flash gapps? AA did just unlock the bootloader and made a cwm for my phone if I need to.
sent from my lgms323 towelrooted waiting on custom rom
Click to expand...
Click to collapse
Yes, flash Gapps and it should be fine
TechMinerUK said:
Yes, flash Gapps and it should be fine
Click to expand...
Click to collapse
Thanks, was able to "factory reset" back to stock and they all reinstalled.
Device: LGMS323 rooted
brentwago said:
Thanks, was able to "factory reset" back to stock and they all reinstalled.
Device: LGMS323 rooted
Click to expand...
Click to collapse
Good, I'm glad it's working again
Just for future reference, I think that whenever switching between user/system apps you always need a reboot.
Sent from my Nexus 4 using XDA Free mobile app
lolcakes203 said:
Just for future reference, I think that whenever switching between user/system apps you always need a reboot.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I did reboot, after every change.
Device: LGMS323 rooted
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
Hi guys. First of all sorry if i'm writing in the wrong section. I have a problem with my Honor 8 (FRD-L09) updated to Nougat. Today i've decided to unlock the bootloader and root it. I managed to unlock the phone via Huawei official unlock bootloader method, then i've pushed the latest twrp (3.1.0-1-frd) by cmd. All was going fine. After that i've probably downloaded an old version of Superuser, the phh SuperUser r275 and installed it. I've downloaded Phh's Supersu application from playstore, installed busybox (by Jrummy) and i was able to use various apps that required supersu just fine. But i faced a lot of problems when trying to uninstall system apps. For example, i wished to uninstall "Maps" with System app remover and it shows me that the app was correctly uninstalled and in fact it disappeared from the list, then i rebooted and the app was still there! Tried again with System app remover with the same app and this time even if the app showed "successfully uninstalled" it was still there. Then i tried Root Essentials, Titanium Backup, Root Explorer, SD Maid but i was unlucky with them all. Always problems and errors. In particular, Root Explorer, after mounted the system for r/w, shows "unable to delete the file". These problems appears with all the system apps. I don't know what's going on, i've never had this problems with my old S2 plus. Hope some of you can help me. What i have to do? Uninstall phh's superuser? If yes how can i do it? Can't find any uninstaller zip around the web. Or i need to install "SuperSU-v2.79-201612051815-EMUI5.0" attached in the TWRP post? Can i overwrite phh's superuser script with this? Is safe? Will it work? I'm very desperate, please help me.
P.S. I basically followed this guide: "http://www.theandroidsoul.com/root-honor-8-nougat-twrp-phh-superuser/" but using the new twrp. Don't ask me why...i can't explain why i did this stupid thing.
Rooting the honor 8 just sucks. It's pretty much a crapshoot.
Try the TWRP and special SuperSU from this thread, and let me know if it works.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I'm in the same boat, I rooted nougat before but didn't actually have r/w permissions. So I've been waiting to re-root until huawei patched their bugs, but it doesn't seem like that will happen.
Best of luck.
SolarisSixth said:
Rooting the honor 8 just sucks. It's pretty much a crapshoot.
Try the TWRP and special SuperSU from this thread, and let me know if it works.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
I'm in the same boat, I rooted nougat before but didn't actually have r/w permissions. So I've been waiting to re-root until huawei patched their bugs, but it doesn't seem like that will happen.
Best of luck.
Click to expand...
Click to collapse
It worked! With this version of supersu i was able to unistall all those useless system apps! I just flashed it by twrp overwriting the previous one and it uninstalled phh'supersu app and installed chainfire's one. Everything seems to work flawlessy thank you. Just wondering if there's a way to remove the annoyng screen at startup that advise that the device can't be trusted. . .
Giuskiller said:
It worked! With this version of supersu i was able to unistall all those useless system apps! I just flashed it by twrp overwriting the previous one and it uninstalled phh'supersu app and installed chainfire's one. Everything seems to work flawlessy thank you. Just wondering if there's a way to remove the annoyng screen at startup that advise that the device can't be trusted. . .
Click to expand...
Click to collapse
That is a product of unlocked bootloader and happens on every phone no matter the brand. It can't be removed