Database Info

SuperUser problems | Fix | Lost root? | binary 3.0.3 | SU 3.0.6

lost root after updating the SU binary, flash the following in recovery:
http://downloads.androidsu.com/super...fgh-signed.zip
Then update to binary 3.0.3 from SU. Goto all apps, start superuser, under superuser information tap SU binary. Follow instructions.
Or download binary at: http://downloads.androidsu.com/superuser/su-bin-3.0.3-efgh-signed.zip and flash in recovery.
---------------------------------------------------------------------------
Update Superuser
1) update to binary 3.0.3 from SU. Goto all apps, start superuser, under superuser information tap SU binary. Follow instructions.
Or download binary at: http://downloads.androidsu.com/superuser/su-bin-3.0.3-efgh-signed.zip and flash in recovery.
2) Update SU to 3.0.6 via market. or download
http://downloads.androidsu.com/super...fgh-signed.zip and flash
3) clear the data from SU.
Credits go to HomerSP for the binary fix

Or you can do it manually...as posted by the OP (@theraver) in a different thread :
binary: http://dl.dropbox.com/u/11494687/superuser/su
to install do this:
Update to superuser 3.0.5 in the market (if you didn't do this)
adb remount
adb push su /system/bin/
adb shell chmod 06755 /system/bin/su
adb shell rm /data/data/com.noshufou.android.su/databases/permissions.*

bloodhawk said:
Or you can do it manually...as posted by the OP in a different thread :
binary: http://dl.dropbox.com/u/11494687/superuser/su
to install do this:
Update to superuser 3.0.5 in the market (if you didn't do this)
adb remount
adb push su /system/bin/
adb shell chmod 06755 /system/bin/su
adb shell rm /data/data/com.noshufou.android.su/databases/permissions.*
Click to expand...
Click to collapse
That;s correct . thats what i posted earlier today, lol

theraver said:
That;s correct . thats the fix i posted earlier today, lol
In which thread was it placed in the OP?
Click to expand...
Click to collapse
Didnt, find it any OP per se. It was there in Faux's HTC Stock kernel thread...
Have tested it across 4 ROM's by now. (Though shouldn't really make a difference)
- by OP i meant YOU. OP for this thread

bloodhawk said:
Didnt, find it any OP per se. It was there in Faux's HTC Stock kernel thread...
Have tested it across 4 ROM's by now. (Though shouldn't really make a difference)
- by OP i meant YOU. OP for this thread
Click to expand...
Click to collapse
edit post #1 because of new 3.0.6 SU!

It works for me! yay

Awesome, it worked for me too. They should put a thanks botton on the mobile app too.
Sent from my HTC Sensation 4G using XDA App

Thanks!No FCs so far
Sent from my greatest Sensation 4G with Beats Audio

Failed to push su as it says the directory is not empty...

paultcook said:
Failed to push su as it says the directory is not empty...
Click to expand...
Click to collapse
Fix for Superuser
1) Update to binary 3.0.2. Go to all apps, start superuser, under superuser information tap SU binary. Follow instructions. Or download binary at:
downloads.androidsu.com/superuser/su-3.0.2-bin-efgh-signed.zip and flash in recovery.
2) Update SU to 3.0.6 via market. or download update at:
http://downloads.androidsu.com/superuser/Superuser-3.0.6-efgh-signed.zip
and flash in recovery.
3) clear the data from SU if your still getting FC's
Credits go to HomerSP for coming up with the fix!!

broncogr said:
SU Binary 3.02 is out.
Update it through the superuser app settings
Click to expand...
Click to collapse
thanx. .

There are problems with 3.02!!!!
Dont update to it!!!!!

broncogr said:
There are problems with 3.02!!!!
Dont update to it!!!!!
Click to expand...
Click to collapse
problems are only on arm6 , sensation is arm7 so i have no problems
http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/

It removes root

http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/

justice26 said:
It removes root
Click to expand...
Click to collapse
only on arm6 chipset
http://androidsu.com/2011/10/i-updated-to-3-0-1-binary-and-lost-root-help/

lost root on HTC sensation?
I updated to 3.06 and also updated the binary...but then it seems I've lost root after I did that. I am not sure how to clear the data if I can't get into titanium backup?? I am using a HTC sensation.
Any ideas how I can fix it? Do I just flash the su file again in recovery?
Thx

newr said:
I updated to 3.06 and also updated the binary...but then it seems I've lost root after I did that. I am not sure how to clear the data if I can't get into titanium backup?? I am using a HTC sensation.
Any ideas how I can fix it? Do I just flash the su file again in recovery?
Thx
Click to expand...
Click to collapse
did you update to 3.0.1 binary? then you can try to flash 3.0.2 binary in recovery
http://downloads.androidsu.com/superuser/su-3.0.2-bin-efgh-signed.zip

I updated to SU3.06..and also updated the binary in there to 3.02...then I lost root. I just flashed the 3.06 file...still don't have root...so I need to flash 3.02 binary as well? It says I already have 3.02 binary when I open SU. I have clear data in the manage application on my phone....still the same problem

I loose ROOT with 3.0.2 bin update over market ad trought app.
Just flashed 3.0.1 binaries from recovery
downloads.androidsu.com/superuser/su-3.0.1-bin-efgh-signed.zip
Rooted again

[Q] Busybox Normal Install Failed - su not found, phone has been unrooted.

Hi Guys!
Newbie here. I have root my phone I have installed busybox from Google Play. I want to update my busybox to 1.21 so I installed it. I have launched the application and then clicked install. I have chosen "Normal" for normal installation. Then I tried installing the busybox into "/sdcard/busyboxfree/" to see if it would run so I entered "/sdcard/busyboxfree/" to the installation path after selecting "Normal" rather than "Smart". And then an error occured saying my su binary was not found. And then I tried opening a adb session and typed "su" (screenshot attached). I can see the SU app grant superuser permission for adb but the adb shell got stucked (see screenshot). So I tried navigating to /system/bin/ and /system/xbin/ to search for the su binary but I can't find it. I also lost some sh commands like "ls" and "rm" so I am using the busybox to do those commands. I can use the busybox so I suppose it is still in my system.
I have done some restoration such as Factory reset / Wipe Data, and restoring userdata using recovery mode (I don't have CWM so stock recovery). And then I tried rooting it again using the same process I have made rooting it before but now it is not working, I can't get the root back. So I decided to ask the huge developer community and experts to consult what to do about this. :victory:
But I have followed instructions from a post at XDA. I have dumped the mtd6 "recovery" and mtd11 "system" before I did the busybox installation (see screenshot mtd.png). Is this enough to restore things back? How do I flash these dumped images? I will be attaching a link to download the dumped images.
My question is, is there a way to gain SU permissions (root)? Do I just need to push/replace/configure/etc binaries or files? Any help will be appreciated. Thanks!
Click to expand...
Click to collapse
My phone is a re-branded phone from CloudFone. Model is Excite 350g. Original Phone model is "Mobistar Touch Cream 350".
Downloads
System Dump Image
Recovery Dump Image
Links:
Rooting Process for CloudFone Excite 350g by mrichiem

Root access on adb shell but not for apps

Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans

skatehans said:
Hello,
i am working on chinese android tablet called "MID-U705B". The device came half rooted i guess. I am getting an # in the adb shell, even without running "su", right from the start of adb shell. Nevertheless i am not able to run any root apps. When i am trying to call a root shell command from my app i am getting: [java.io.IOException] : write failed: EPIPE (Broken pipe).
There is a su file inside my /system/xbin folder and i also created a symbolic link to it in /system/bin.
Does someone know how to get full root access on this devices? Whats missing?
Thanks for your help and advice!
Best regards,
Hans
Click to expand...
Click to collapse
If you can get root on ADB then just install SuperSU app and its binaries and you are good to go.
Flashing the attached ZIP will install SuperSU app and everything it requires to function.
NOTE: You probably need a custom recovery because the zip isn't signed.

Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?

skatehans said:
Thanks for your reply!
Unfortunately i dont have a custom recovery because its a no name device an there does not exist a custom recovery for this device. Is there any way to install this without a custom recovery? What happens when i try to flash it from a (chinese) stock-recovery?
Click to expand...
Click to collapse
You should be able to flash it via fastboot.

Thats the next Problem. I cant boot into fastboot mode. When i execute "adb reboot bootloader" or "adb reboot download" the device boots up like normal, so i guess fastboot is not available on this device.
Do you know any other way?

Su installed but not available

Hi guys... I'm new here, and I'm losing my hope resolving my problem.
at first I have my rooted phone with kingroot installed, and I installed busybox and worked fine with root apps.
it start when I got confused to move busybox in /system/bin since it is not available in system/xbin. at first it can't install. what I did was I changed permission to r/w of system/bin try to install busybox applet in there and it succeas . but it gave me a big problem. my kingroot failed to recognize I'm rooted or I have lost my root? or root access. I tried rooting it but it can't go. it only get to 70% as always but failed. and I lost a high rate of succession. actually my first root was fast and ez.
I tried checking my su and root with some root/su checkup.
using DevCheck available in GPlaystore, it says
"Device is rooted" and
Busybox: "system/bin/busybox".
upon using RootCheckerBasic , its says " Sorry! Root access is not properly installed in this device."
and using Busybox Checker... its gives Busybox Available: YES
Path: /system/xbin, and SuperUser gives
Su Available: YES
Su access given: NO
Path: /system/xbin/su
Version info busybox and su: both not found.
so please help me with this. for the future this would be helpful.
mobile: Cherry mobile astro 2 (Philippines)
Model: Q490
Android: 5.1 lollipop
sc7731c

You need to unlock the bootloader

Hello, from what you said, that it happened after moving BusyBox to /system/bin instead of /system/xbin?
but there must be files for bb in /system/xbin and /system/bin
and if bb gives you the option to uninstall do it.
and then, reboot
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
thaiphuoc1 said:
You need to unlock the bootloader
Click to expand...
Click to collapse
read the whole thread before posting, we apprentice that you are trying to help, but copying the same statement all over the forum won't help, read the post first

Unable to run adb root on rooted OnePlus 7 Pro with Android 11

Hi all,
I've spent the better half of my Sunday trying to finally get `adb root` to work on my device (rooted with magisk).
I've tried a variety of things, such as using the `resetprop` tool to modify the ro.debuggable and ro.secure properties (supposedly successful upon checking the output of `resetprop ro.debuggable`, however upon exiting the shell and attempting to run adb root, it doesn't work. I assume it's because I need to reboot, but the `-p` flag for percistence doesn't appear to work for me.
I've attempted modifying the build.prop file directly, with no avail. I just want to add a CA cert to my /system/etc/security/cacerts to intercept an app's requests through burpsuite (a HTTP proxy).
If anyone has any recommendations on what to try, I'm all ears, and would be massively appreciative of any help.

If it's rooted just patch adbd to not care about that stuff.

Renate said:
If it's rooted just patch adbd to not care about that stuff.
Click to expand...
Click to collapse
Any idea where I can find a patched binary or more information on how to do this? I would've thought I can't patch as it requires writing to read-only parts of the system (I've been unsuccessful in trying to remount it with write permissions too... not sure why when I am in a root shell.

Sorry, I wasn't trying to give you totally worthless advice.
Production builds of adbd don't respond to "adbd root".
Since it's all open source you can build from source to have a rooted adbd.
OTOH, I never build from source, I find it easier to mod.
To put that on your device you'll need Magisk or somehow rooted.
Modding /system requires Magisk or that you abandon the concept of incremental updates (without restoring to last official version).

Renate said:
Sorry, I wasn't trying to give you totally worthless advice.
Production builds of adbd don't respond to "adbd root".
Since it's all open source you can build from source to have a rooted adbd.
OTOH, I never build from source, I find it easier to mod.
To put that on your device you'll need Magisk or somehow rooted.
Modding /system requires Magisk or that you abandon the concept of incremental updates (without restoring to last official version).
Click to expand...
Click to collapse
Interesting, thank you for the detailed response, I really appreciate it.
Gonna dig into this for the next couple days as I'd like to have a good phone for mobile security testing.

Not saying that this is the best route or the sane route. There are devices that I care about and devices that I can't be bothered about.
For the device that I care about:
I modify the dtb in the boot image so that /vendor is loaded without verifying.
I modify the fstab in /vendor so that /system is loaded without verifying.
I modify both /vendor and /system so that there is no error correction (wipe the last 4096 of each partition).
I patch (SE Linux) sepolicy for what I need in .cil
I patch adbd to be rooted (without any adb root or su command)
Yes, one could use Magisk, but I don't know where that is going. It's a clever program, but mod some stuff and look at all the stuff that a mount command shows.
For me, it's above the threshold. The downside of my approach is that you can't do incremental updates (without reverting to stock).

hola amigo disculpa lo que veo tu dispositivo esta rooteado y quisiera saber si me puedes ayudar a pasarme algunos archivos del sistema, ya que tengo un problema con las camaras que no puedo solucionar...