Database Develop

2.2 Kept root access

I used the ROM Manager app to update to 2.2froyo from a ere27 firmware with super user 2.0.3 and kept root access. I was wondering if anyone else had the same result?

I flashed the ROM Paul gave us and yes, it kept root access. So far all programs requiring root access have worked except for Titanium Backup which says it cannot find it.

just hit problems and download busybox then it will work.

Paul's rom had the added root access, you didn't really "keep" it.

Thanks for clearing that up...in the ROM Manager it was noted as Nexus One FRF50 Unrooted, Odexed. Which was why i was suprised to see the little ninja.

[TOOL]Auto Install Tools[Windows]

I have made this for people that have suddenly lost root access the installer contains
Superuser Application < Latest
Su Binary < Latest
Root Browser < Latest
Root Browser Thread http://forum.xda-developers.com/showthread.php?t=1338582
Busybox < 1.19.0
i will be adding updates as they come out so i will be updating busybox tomorrow to 1.19.3 i have tested this and it works a charm
Download v1.0.0.1
http://www.mediafire.com/?cl89ngtk4qrv1uh
More to be added like gapps installer and tweak installers

Download Link added

cool! Will try when I go back home on tuesday

thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica

Nice program. In which language have you made this? I suppose it was made in Visual Studio, or am I wrong?

lavero.burgos said:
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Click to expand...
Click to collapse
god this should have worked because all custom rom allow the adb shell command rooted or not it soulds like the rom didn't install correctly.
also it made using notepad++ to make the bat file

lavero.burgos said:
thanks eoghan i just realized when i was about to caligrate SDSL v2 that i lost root, and that mite be the reason im getting fc's and busybox doesnt want to install any version, how this happent with murki's versions and others i never had this problem.
ps: btw how does this work?
EDIT: i plugged my phone run the app as admin and no admin and all the times said permission denied, already tried twice and once being in recovery . im tired of all the issues i had had so far with sdsl v2 ill go back to v1. btw also tried Z4root with no success
Veronica
Click to expand...
Click to collapse
Z4root uses old root exploit that was patched in 2.2.1+, GingerBreak will work also Boot into recovery and mount system and connect then use this app

ill have a look at using gingerbreak aswel in the installer after it tests if root can be used without gingerbreak im currently making a new installer for google apps link market, youtube etc all the latest as possible

eoghan2t7 said:
ill have a look at using gingerbreak aswel in the installer after it tests if root can be used without gingerbreak im currently making a new installer for google apps link market, youtube etc all the latest as possible
Click to expand...
Click to collapse
That would be very Usefull, Instead of having to search for them,
For guys who don't know where the latest are go onto Cyanogenmod's website, they are all there

i will be putting the lastest market and music in it but will give the user the choice to use the old music app

[ROM][08/18][GT-P3100][4.0.4]-Stock Rooted De-Odexed-Base:IMM76D.P3100DDBLF3

GT-P3100 by RomsWell
Base: IMM76D.P3100DDBLF3 For the GT-P3100
This is a mostly stock version of the OTA. With a some of the more basic features added.
De-Odex
Zip Align
Rooted
init.d Support
I do not own this device.
Install Instructions
Flash thru Custom Recovery
DO NOT UPDATE SUPERUSER BINARYS YOU WILL LOSE ROOT!
If coming from CM you will need to do a full wipe including System before flashing.
Download Here​

Download Links Live
If you have trouble downloading to the pc Try Chrome or Firefox. Or download Direct to Tab

Anybody tried it ?

Will it replace Recovery ?
Downloading now....

silentvisitor said:
Will it replace Recovery ?
Downloading now....
Click to expand...
Click to collapse
No

Thanks !
Flashed it and it is working fine except Superuser. Any app which needs and uses Su generally freezes.

Can you inject latest su in this release m buddy???
NEOHACK

They updated super Su so it now works with our ics crap. If you jump on market install Super Su not superuser. It will let you update to the newest binarys. Then with root explorer or whatever nav to system apps and delete the superuser apk. On all up comming updates I will be using super Su. Not superuser.

Did you update the su binaries??
NEOHACK

I just did on my tab using super Su

silentvisitor said:
Thanks !
Flashed it and it is working fine except Superuser. Any app which needs and uses Su generally freezes.
Click to expand...
Click to collapse
I expect your talking about root explorer and tibu. They both freeze on this device. But I don't think its a super user issue as they both open and work fine but at a random point freeze. it seems more like a app issue then anything. They both have done that since day one of owning the device. I'll see if I can find the issue. Reason I think its app related is because I use a ton of rooted apps and a ton of root file explorers and root explorer is the only one with a issue.

Thank buddy I am in process to make a custom rom for tab 2. Let's see how it goes
NEOHACK

I dont think it app related.
Root Explorer worked beautifully earlier with Full Stock ROM so I know its not app problem. Currently even DroidWall and LBE Privacy also froze. Will switch back to Superuser and report.

silentvisitor said:
I dont think it app related.
Root Explorer worked beautifully earlier with Full Stock ROM so I know its not app problem. Currently even DroidWall and LBE Privacy also froze. Will switch back to Superuser and report.
Click to expand...
Click to collapse
Try super Su not super user. And you where on 403 I think if your were running stock. The rooted version I have posted is 404

When does droidwall crash? I'm trying to get it to freeze.

RomsWell said:
Try super Su not super user. And you where on 403 I think if your were running stock. The rooted version I have posted is 404
Click to expand...
Click to collapse
No I will completely replace SuperSu with Superuser through flashable zip.
I was on DDBLF3 only

I think I alrdy have superuser on this release. I switched to super Su on my tab via market and it auto updated binarys without loosing root. I then deleted super user apk from system apps via root explorer. Lemme know what ends up working for you. I'm leaning towards SuperSu since it updates without failing. SuperSu is superuser rebuilt and modded to handle some of the newer issues that showed up with ics and gbean

RomsWell said:
When does droidwall crash? I'm trying to get it to freeze.
Click to expand...
Click to collapse
Whenever I try to give Permission to a newly installed app. Droidwall freezes and exit with an error code and gets disabled.
---------- Post added at 08:11 PM ---------- Previous post was at 08:09 PM ----------
Replaced SuperSu with Superuser and everything working fine, as yet

silentvisitor said:
Whenever I try to give Permission to a newly installed app. Droidwall freezes and exit with an error code and gets disabled.
---------- Post added at 08:11 PM ---------- Previous post was at 08:09 PM ----------
Replaced SuperSu with Superuser and everything working fine, as yet
Click to expand...
Click to collapse
Kk every works fine for me. Couldnt get droidwall to act up. I'm using super Su. Wonder what the issue was.

A little mistake on my part - should have logcat 'ed the errors. Sorry

[SOLVED 2.07][BUG 1.94]: endless loading of apps and logs fragments

Thread specifically about finding and solving the issue that some are seeing where the apps and logs screen of SuperSU will load indefinitely, while su access does keep working.

r25txe said:
Hi @Chainfire
I just tried the 2.04BETA to see if my issue was resolved, to no avail.
I was wondering have you had any reports of certain settings not being configurable and the "apps" and "logs" tabs endlessly refreshing, i.e., you cannot see what apps you have approved or denied.
My root does work, I can approve or deny requests normally, it's just I cannot go back if I want to reconfigure an app's root access or review logs. Unchecking the refresh app and logs automatically has no effect.
In the settings, uninstall SuperSU will not work, causes an eventual crash of SuperSU (after quite some time) unless you do a reboot. SuperSU will still be there, too.
I'm a Pro user and unable to set a PIN either as SuperSU will just circle endlessly after trying to set one.
I've been reading about other users' issues mostly related to root access itself, but my issues seem to be interface only.
---------- Post added at 01:30 AM ---------- Previous post was at 01:19 AM ----------
Oh, my ..!
It's working now, I just did another reboot (because SuperSU had become stuck again) and on reboot all was working! :good:
:blush:
I'll redownload the licence and test Pro features tomorrow and report back.
Click to expand...
Click to collapse
r25txe said:
All the issues I described are back now.
With or without licence.
Will continue trying/testing see if I can get a pattern.
This is persisting across four phones, one on Gingerbread.
Click to expand...
Click to collapse
mathuaerknedam said:
I'm also seeing this, in 1.94 and 2.02, but I've not yet tried the 2.04 beta. Sometimes it works. I've tried all sorts of different things to identify a pattern, but I've had no luck.
I've also one instance, just last night, of SuperSU requesting root privileges for itself. I can post a screenshot and some log data if that would help.
Sent from my Nexus S 4G using XDA Free mobile app.
Click to expand...
Click to collapse
xlollomanx said:
Same issue I have, is presented from any version after 1.94. However it does not happen always: sometimes shows granted superuser app sometimes not, happens random.
Click to expand...
Click to collapse

It'd be great if we can get a recap of which SuperSU versions, which devices and kernels and firmwares, are affected. Any information you have is welcome. Let's get this issue sorted out.

@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?

xlollomanx said:
@Chainfire So I'll start. I own a Galaxy W with unofficial Cyanogenmod 11 ( http://forum.xda-developers.com/showthread.php?t=2588495) and now I'm using this kernel http://forum.xda-developers.com/showthread.php?t=2593027 (I' ve tried also with stock kernel but the problem persist and is the same). I used SuperSU for years and worked perfectly until v1.94. When I installed v2.0 the problem starts. After that I updated to 2.01 and I tried some beta like 2.04 and 2.05 but the problem still persist.
I hope this can help you, thanks for support.
EDIT: Some kind of Log could help you?
Click to expand...
Click to collapse
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?

I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?

Chainfire said:
How did you update? Via in-app, Play store, or exclusively ZIP updates? Which recovery are you using? Have you tried making a backup, wiping, and install SuperSU cleanly - does the issue persist?
Click to expand...
Click to collapse
Now I'm using CWM recovery based (6.0.5.0)
I tested the v1.94 and update v2.0 on a " old rom". Few days later, thinking was my device problem's I performed a full wipe with pristine and installed v2.0 directly from play store, so I could try a cleanly installation of SuperSU (but the problem persist). Here I tried all new versions (I also tried the v1.94, which worked fine, but mainly to uninstall the newer version's as I will explain below) but without success.
I tried in different ways:
I downgraded to v1.94(replacing supersu with root explorer), uninstalled SuperSU, reistalled v1.94(via in-app) and then updated to 2.0 and then v2.01 when update came out from play store.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.0 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I downgraded again to v1.94(replacing supersu with root explorer), uninstalled SuperSU and then installed v2.02 from zip-updates. Also tried flashing directly over v1.94 ,without uninstall, from recovery with zip-updates.
I tried v2.04 and v2.05 with zip-update from recovery by flashing directly over v2.02(this v2.02 is a result from previous test).
I uninstalled SuperSU by replacing supersu with root explorer, installed via in-app v1.94(that work perfectly) and then installed 2.04.
I hope I have answered in the right way in all your questions.
Regards

I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Thank you.

Been playing around, haven't replicated so far. A common theme seems to be CM and CWM, though it works fine in my own testing still... sigh.
mathuaerknedam said:
I've definitely seen this with SuperSU 2.02, and I believe I also saw it with 1.94 (but I can't recall for certain). I've not yet tried 2.04 beta.
I'm using the device, rom, and recovery in my sig. I've see this with several different kernels, including the one in my sig, Marmite 10.6/10.5/10.4/10.3, Matr1x 25 cfs and bfs, Devil Kernel 20131025_VC and Air Kernel Weekly r350.
When I flash a kernel, cwm asks if I want to "fix root". I've reboot both fixed and unfixed, and it doesn't seem to matter.
What else can I try or provide?
Click to expand...
Click to collapse
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.

Chainfire said:
Which installation method do you use for busybox? As I recall, the app you use provides several different methods.
Click to expand...
Click to collapse
I just clicked the big install button for a regular install.
Sent from my Nexus S 4G using XDA Free mobile app

Chainfire said:
Which installation method do you use for busybox?
Click to expand...
Click to collapse
That seems like a probable culprit. Maybe if someone installed your version of 'busybox' we might see a difference.
Frank

Installed BusyBox as well ... still working for me ...
Can you guys having this issue post your /data/data/eu.chainfire.supersu/files/supersu.cfg file ?

Very important 3d
Inviato dal mio SM-G900F X-Note 5.0 con Tapatalk

Nothing here

FeraVolt said:
I have similar bug. I am on SE xperia GB ROM and all previous versions below 2.00 were working fine. After that I started to notice various problems.. For ex. on 2.00+ versions I was always getting "update su binary" notification. I tried to update it in both ways and both were sucessufull and root was working but i still was getting that notification. On last beta (2.05) root stopped to work and all root apps are loading continuously... when I enter to supersu app I get a notification that there is no su binary (but it exists). I install supersu on clean rom from recovery.. Here is the source code..for reference..
https://github.com/feravolt/feralab
Click to expand...
Click to collapse
These issues are not related, as the problem we're discussing only applies to Android with SELinux, which Gingerbread doesn't have.

Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx

Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
Click to expand...
Click to collapse
It works!!!
The problem was never entirely consistent, so I'll keep checking and report back. But so far, so good!
Sent from my Nexus S 4G using XDA Free mobile app

Chainfire said:
Let me know if v2.06 BETA solved the problem, please!
@r25txe @mathuaerknedam @xlollomanx
Click to expand...
Click to collapse
Hi @Chainfire
I just flashed 2.0.5 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?

r25txe said:
Hi @Chainfire
I just flashed 2.05 and the problem is persisting after two full reboots.
What kind of logs would be useful to you if you need them?
Click to expand...
Click to collapse
Flash 2.06 ?
Did you mistype, or ? If you are actually on 2.06 then I'll have to think some more what the issue could be and how to trace it...

Oh, dear.
I am clearly much too tired to be on XDA! I only noticed that you posted 2.0.6. I will try it after work tomorrow, really need to crash now.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
Oh, I see you´re online, I will flash it right now ...
---------- Post added at 01:02 AM ---------- Previous post was at 12:56 AM ----------
2.06 works!!
(Although, 2.0.4 did this to me, too)
We´ll see how we get on tomorrow
Thank you, @Chainfire
---------- Post added at 01:08 AM ---------- Previous post was at 01:02 AM ----------
Not sure its of use, but here is the cfg file after the flash of 2.06.
https://www.dropbox.com/s/2s3kircndbfjqmm/supersu.cfg?dl=0

what does this mean? can anyone help

Please anyone

no idea man, how did you get root in the first place for 5.1.1

It's not totally rooted. I found this site. SRSRoot One Click Root for Android (SuperUser)

https://mega.nz/#!3JlGBRqB!-xgWHVy5HDNiSQc3SSkkI7UTk0SSpjs1EFsfGSUtZxw

GayCasper said:
https://mega.nz/#!3JlGBRqB!-xgWHVy5HDNiSQc3SSkkI7UTk0SSpjs1EFsfGSUtZxw
Click to expand...
Click to collapse
ok cool thanks

If u figure it out let me know

It is rooted if you flashed that one file that was posted but you don't have a Su Binary installed. I was trying to figure out what I have to push to my phone for the su binary, etc but no one seems to know? It sounded like there was script initially posted by Tanh but I don't see a link anywhere to it.
---------- Post added at 10:07 PM ---------- Previous post was at 09:41 PM ----------
rascal00 said:
It is rooted if you flashed that one file that was posted but you don't have a Su Binary installed. I was trying to figure out what I have to push to my phone for the su binary, etc but no one seems to know? It sounded like there was script initially posted by Tanh but I don't see a link anywhere to it.
Click to expand...
Click to collapse
SRS seems to have installed the su binary however it won't run correctly still. It gives an error of "only position independent executables (PIE) are supported."

As far as I know with the last few days of research and flashing:
The "root" that keeps floating around here is not full root. It is an official samsung kernal intended for buisnesses to force apps to the system. It only allows adb root access, it will not allow you to install the binaries needed for su. Either it won't fully install and be useless or it will put you into a boot loop with no current fix.
SRS root does not work. They might claim it roots your phone but it is only a half install of su. I have tried many times, and it will not give you su.
Sent from my SAMSUNG-SM-G925A using XDA Premium HD app