Root Explorer App Android 2.1 - Streak 5 Android Development

Hello,
Sorry if this is an already posted topic, did a couple quick searches and found nothing.
I'm running Android 2.1 build 8105 on an ATT streak. From what I understand The android 2.1 software is pre-rooted ?
I want to change my boot animation, So I downloaded the app *Root Explorer*. Every time I launch the app I get the error message that root explorer has not managed to obtain root access.
Is there something I'm missing ? Or that I have to do to gain root access thru 2.1 since its pre-rooted ?
or do I just need to download superboot and flash it ??
Thanks!

If you are sure that the build is rooted maybe you must install "superuser" to give permission to Root Explorer to use Root access! I maybe wrong but try it.

The 8105 builds does have su intact and unsecured. You can use it, but its not as simple as using superuser app from chainsdd.
Id recommend using universalandroot as its about the easiest way to get chainsdd app working.

Related

[Q] cant find busybox in terminal emulator?

hi guys,
new to all this and have rooted my x10 mini mainly in order to remove excess apps that came with the phone (and i'm sure i'll start using root access for other things too!)
having a bit of a problem though...
what i've done so far:
updated from OEM 1.6 to 2.1 via sony webste
used SuperOneClick to gain root access
added SuperUser
added titanium backup and used that to download busybox
installed terminal emulator
in terminal emulator i enter su - and this gives me access fine.
however when i type in busybox it says not found. i've rebooted after every app installation etc.
i gathered (probably incorrectly) that this may be because busybox isn't in a path or something, so i would need to navigate to the busybox folder first? however i cant find anything called busybox on my SD card!!
help please!!
cheers, Adam
well i still cand find busybox, BUT.....
didn't realise I can browse root with ES File Explorer that I already had - gunna delete apps now
cheers!!
<edit>
scrap that, says i'm not allowed lol.
if i buy root explorer from the market i guess that'll work?
lincoln_dj said:
if i buy root explorer from the market i guess that'll work?
Click to expand...
Click to collapse
it does
lincoln_dj said:
hi guys,
new to all this and have rooted my x10 mini mainly in order to remove excess apps that came with the phone (and i'm sure i'll start using root access for other things too!)
having a bit of a problem though...
what i've done so far:
updated from OEM 1.6 to 2.1 via sony webste
used SuperOneClick to gain root access
added SuperUser
added titanium backup and used that to download busybox
installed terminal emulator
in terminal emulator i enter su - and this gives me access fine.
however when i type in busybox it says not found. i've rebooted after every app installation etc.
i gathered (probably incorrectly) that this may be because busybox isn't in a path or something, so i would need to navigate to the busybox folder first? however i cant find anything called busybox on my SD card!!
help please!!
cheers, Adam
Click to expand...
Click to collapse
Superoneclick does not install busybox
Gothic-4-Schiffer said:
Superoneclick does not install busybox
Click to expand...
Click to collapse
i know. that's why i said i used titanium backup to try to install it, as per instructions elsewhere on this site
lincoln_dj said:
i know. that's why i said i used titanium backup to try to install it, as per instructions elsewhere on this site
Click to expand...
Click to collapse
Look for it in the market. That one works, i had the same problem. Titanium seems to install an old version of this one, and sometimes it fails.
Sent from my X10mini using XDA App
thats the busybox version i use for x10 mini 2.1 update1 (rooted of course):
http://dl.dropbox.com/u/1229065/busybox
copy it to "/system/bin/"
even better check this http://www.omapedia.org/wiki/Android_Installing_Busybox_Command_Line_Tools

[Q] Market Fix

Hello all, I am attempting to use root explorer which I've put on my tablet with drop box, which i installed via exchange email.. and I'm a little confused. I am trying to install the market fix, however I cannot seem to open /system with root explorer, even when i have su. Whenever I open the /system folder root explorer force closes (newest version).
Using Vanilla AOSP Gingerbread with latest clockworkmod recovery - also attempted to fix permissions.
Any help would be great
-Joe

[Q] root not found ! by few apps

i have rooted my mobile using this tut forum.xda-developers.com/showthread.php?t=1196808.
and it was successful but few apps like system app remover and linux installer is displaying root not found error!
what should i do to provide root access 4 these apps?
even in Better terminal , if ask for superuser permission the access is denied
Just Try 2 Help..
..Base on TuT "http://forum.xda-developers.com/showthread.php?t=1196808"..
Make sure you've Flash It Correctly First..then Check in about phone the BB version now is 2.1.71..? Then Check if SU already Installed in your phone..
If the SU not yet installed..try again for "Instaling X-Recovery" Step..
aah..try to install a new version Busybox..
I've No Problem after Rooting for Better Terminal, System App Remover and other RooT Apk..

[Q] root Karbonn A37

I was able to root Karbonn A37 (MTK6577) using the software from t - http://www.mgyun.com/vroot.
After the root process it instalsl this app - https://play.google.com/store/apps/details?id=com.mgyun.shua.su&hl=en.
This app is in Chinese and it manages all the root permission requests as well as installs its own su and some other files.
I have tried to root using many other methods available here and only the above method was successful. After rooting I tried installing SuperUser and found that su is always getting overwritten. I would really love to use the standard English version of su and superuser, but if I uninstall the the Chinese app, the root access goes away.
Was wondering, if anyone could suggest a way to make root permanent without the Chinese app and mange root permissions using superuser. Also what is this Chinese app doing, that none of our other rooting methods are not able to do?
More details on the chineese app here - http://forum.xda-developers.com/showthread.php?t=2434453
Vroot to Supersu
You can go to the following weppage and follow the procedure
googlr search vroot to supersu and click on w0lfdroid link
It worked for me.
In return I need your help.
Can you please upload or email me a copy of your default unedited build.prop found in /system/ folder
I edited the file and stuck in boot screen
k00lk0der1 said:
You can go to the following weppage and follow the procedure
googlr search vroot to supersu and click on w0lfdroid link
It worked for me.
In return I need your help.
Can you please upload or email me a copy of your default unedited build.prop found in /system/ folder
I edited the file and stuck in boot screen
Click to expand...
Click to collapse
Attached build.prop for Karbon TAFONE A37. Hope it helps.

Can't install SuperSU with TWRP

Hi everyone. I'm trying to root my Alcatel 1T 7 8067, by using TWRP 3.2.1 and zip SuperSu images, but rooting was unsuccessful.
The last successful root that I got with that method, was on a marshmallow android device (a CATS60), with no issues; but on my recent device (with oreo go), when I try to install supersu by TWRP option "install", it begins to install, and the process log shows apparently an error: "Patching Sepolicy -----Failure, aborting", and when I reboot to system, there is no root access.
As result of those failed attempts, I have tried by installing old versions of supersu with apparent success, but then, when I try to boot the device, it enters into a bootloop.
So I think, that unsuccessful rooting is related to that Sepolicy error ¿Am I right?
I've noticed that there's no SU folder inside /system folder, so, as I understand, it means supersu wasn't installed (I can see that by using the TWRP's file explorer).
So ¿What can I do with that issue?
I've read that Magisk can solve this problem. Following tutorials about, I tried by flashing a magisk patched boot image, but supersu installation issue still continues.
I must say, that I prefer supersu over magisk, because is more familiar to me, but in general what I need, is a system root, a real root access; not a systemless root; and based on my experience, I only can get that with supersu.
@Camilo Gil I don't really understand your point "real root access".
On my Magisk rooted devices I can access any system file and even change it externally and write it back into system.
I used SU previously but as further development has stopped I had to switch anyway.
superSU? do you live in 2010? get rid of that old stuff and use magisk, SupeSu is totally useless in android 7+
bmwdroid said:
@Camilo Gil I don't really understand your point "real root access".
On my Magisk rooted devices I can access any system file and even change it externally and write it back into system.
I used SU previously but as further development has stopped I had to switch anyway.
Click to expand...
Click to collapse
By real root access, I want to mean, that SU binaries are installed on /system folder. As I understand, if that requirement is given, all apps that need root access, can fully work, without any limitations. Recently, I tested magisk, supposedly my device already had root access. Then I installed ES file explorer to give it root access, and it was granted on magisk but root access couldn't be activated in the app. That never happened me before.
As I understand, that's because ES file explorer couldn't find SU binaries, because magisk root method is systemless root.
I hope I would explain myself right.
tutibreaker said:
superSU? do you live in 2010? get rid of that old stuff and use magisk, SupeSu is totally useless in android 7+
Click to expand...
Click to collapse
¡More o less! I live in 2018, or at least that was the last date when I rooted a device (CAT S60, android 6.0). I don't trust on Magisk, just because I couldn't give root access to ES file explorer. That never happened me before. And I know there are many more file explorers; I know that Es file explorer is kinda deprecated, and root explorer works fine; but I want a root access on which any app that needs root access, and that I want to install obviously, can work without any limitation. My firsts impressions of magisk root is that it cannot provide that service.
Now, what you say that supersu is useless, it's worrying to me, because I can't see any other alternative for root access.
¿Why do you say it's useless?
Camilo Gil said:
¡.... I want a root access on which any app that needs root access, and that I want to install obviously, can work without any limitation. My firsts impressions of magisk root is that it cannot provide that service......
Click to expand...
Click to collapse
Yes it can but in a different way.
You're asked once to grant root privileges for each app that needs it and if you let it have root that's it.
Or you grant root temporarily and will be asked every time for this app.
Apps that don't need it don't get it.
You can change your decision afterwards as well.
Btw I use Total Commander with LAN plugin to access my NAS.
bmwdroid said:
Yes it can but in a different way.
You're asked once to grant root privileges for each app that needs it and if you let it have root that's it.
Or you grant root temporarily and will be asked every time for this app.
Apps that don't need it don't get it.
You can change your decision afterwards as well.
Btw I use Total Commander with LAN plugin to access my NAS.
Click to expand...
Click to collapse
With magisk, I grant root access to ES file explorer, but I can't enable it on the app. As I read, that's because ES File Explorer can't find SU folder in system folder (which actually happens on system root), and because of that, some apps like es file explorer, won't detect systemless root or better, to them, systemless root is detected as non root access.
I read that even supersu must be installed as systemless root, because if installed as system root (or what I refer as "real root") on android 7+, causes bootloops. On my particular case, system root causes an endless boot. As I understand, that happens because supersu can't set /system folder to R/W, on android 7+.
On the other hand, I know there are several alternatives to ES file explorer, for instance Root Explorer, Total Commander, etc. But it's just I'm accustomed to it. But also I read that systemless root not only can cause issues with ES File explorer, but also with Viper4android and some other Xposed modules.
PS 1: We should suggest to google, that release an official rooted android version, specially addressed for us, the medium skilled and advanced android users (that normally we like to root android and get the most of it).
PS 2: So finally ¿is there any way to have a working system root access in oreo, or systemless root is the only option?
Camilo Gil said:
... because if installed as system root (or what I refer as "real root") on android 7+, causes bootloops.
Click to expand...
Click to collapse
I can't remember on which LOS version or when I used it the last time before switching to Magisk.
Camilo Gil said:
On my particular case, system root causes an endless boot. As I understand, that happens because supersu can't set /system folder to R/W, on android 7+.
Click to expand...
Click to collapse
Idk
Camilo Gil said:
On the other hand, I know there are several alternatives to ES file explorer,
Click to expand...
Click to collapse
There seem to be several with that name so just tell me it's full correct name and I will install it on my Magisk rooted LOS14.1=Nougat tablet and see if I get problems with it.
Camilo Gil said:
... Viper4android and some other Xposed modules.
Click to expand...
Click to collapse
don't use them so can't tell
Camilo Gil said:
PS 1: We should suggest to google, that release an official rooted android version, specially addressed for us, the medium skilled and advanced android users (that normally we like to root android and get the most of it).....
Click to expand...
Click to collapse
afaik the pure Vanilla is the base from which most custom ROMs are built by the devs and imo most ROMs you can get are not rooted as it's of course a safety hazard.
bmwdroid said:
afaik the pure Vanilla is the base from which most custom ROMs are built by the devs and imo most ROMs you can get are not rooted as it's of course a safety hazard.
Click to expand...
Click to collapse
I know a rooted android is a security and stability hazard of the device. But evidently who wants to root his/her device, is fully warned about its potential consequences. So google could publish a prerooted version, previously warning about its use, warning that its use is exclusively under user responsability, and maybe disclaiming liability for damages. I guess there's no problem if users of that (at the current moment) imaginary OS , are aware of the risk that they are taking by using it. At least, I would use it if could (and as it doesn't exist, it's because I'm trying to root my current one).

Categories

Resources