• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Problems with running LBE: a root issue or something else?

Pondering

Member
So I followed the process for the CF-Root and everything seemed to work as advertised. The red Android came up on my phone, the phone data was wiped and it successfully rebooted. However, I've since tried LBE Privacy Guard will not work. At my first attempt, Titanium Pro also failed and reported it could not find root.

I rebooted the N5 and tried again. This time Titanium Pro ran and successfully accessed root.

LBE Privacy Guard still reports it cannot run. I have reinstalled LBE and still get this same problem.

I have checked and SuperSU was installed and will run when I select it.

Given that Titanium Pro is now working, I am guessing this is a problem with LBE, not a rooting gone wrong.

Suggestions?

Thanks!
 
How do I reflash SuperSU? I have only unlocked the boot loader and rooted. I was planning on leaving everything stock for a bit and have not flashed a custom recover. Thanks!
 
OK.. Yeah without recovery you can't flash SuperSu.
Now that TB has been granted SuperSu permissions you do have root access and there is something not quite right with LBE. You will have to further research it.
 
Whoops! Users are reporting in Play Store reviews lots of problems with the current release of LBE Privacy Guard and SuperSU. Too bad, it was a pretty good app on my old phone.
 
OK.. Yeah without recovery you can't flash SuperSu.

Would just like to point-out that if you have an unlocked bootloader and your fastboot access works, you can soft-boot a custom recovery which loads it but does not write/overwrite the recovery partition (i.e., fastboot boot <recovery.img file>).

Then, you can do whatever you need to do while in your soft-booted custom recovery and when you reboot, your stock (or whatever previous) recovery will still be there, untouched.

Cheers!
 
Would just like to point-out that if you have an unlocked bootloader and your fastboot access works, you can soft-boot a custom recovery which loads it but does not write/overwrite the recovery partition (i.e., fastboot boot <recovery.img file>).

Then, you can do whatever you need to do while in your soft-booted custom recovery and when you reboot, your stock (or whatever previous) recovery will still be there, untouched.

Cheers!

Thanks scary alien... Your right! Most of the time I do forget about that and it completely slips my mind.
 
Back
Top Bottom