Database Develop

Need help from botched root attempt.

GRRRRR SuperOneClick breaks it also
I hate posting a question, but I've exhausted searching for an answer.
I have a G1 that i am trying to root in order to flash, I made the mistake of using ANDROOT because it said it worked for G1. Well it said it rooted my phone, but I think it botched something internally because I can't actually get root access.
I then attempted to use the SUPERONECLICK and it ran through the whole proccess and failed when it did a test command at the end to send a SU request.
I then tried some other things to flash clockworkmod recovery with no success.
Now when I attempt to access root in terminal I get...
"371 could not load needed library 'libbinder.so' for 'su' (lLibrary 'libbinder.so' not found)CANNOT LINK EXECUTABLE"
I'm not an idiot, I've rooted and flashed both the NEXUS ONE and CAPTIVATE many times problem free, but this has now got me stumpped and I've searched to no avail. Any help is appreciated.

I'm having the same problem.
Path I took was a bit different, just got here from WM some Linux exp not much.
I tried universal androot
It said it worked. But it didn't.
Then SuperOneClick
Failed at SU test.
So i tried the Shell Root that said it worked.
Only proof I have that it works is that android screen cast works.
Then I was installing Titanium and it said I didn't have root or my busy box was not installed. So I pushed I'm having trouble ... I downloads it.. to where i dont know
I tried pushing it from command prompt with
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
at this point I get that error
when I exit and come back into shell I get the same error just by typing SU.
Any help would be appreciated it. I have a Zio

What's a zio?
To both...start over with the DREAIMG.nbh and just start from scratch. These one clicks may work but they're boring. I actually unrooted one of my dreams and used visionary and it worked too funny (but boring)
htc vision

[Q] nTelos Milestone Root Failed. Can't find Mount Path or /etc/fstab

Hey all, just purchased my Milestone 1 from my local provider nTelos. They are CDMA carrier located in the Shenandoah Valley of Virginia. Now, everything has been working fine for almost a week and a half now, but yesterday upon trying to update my Busybox install (from 1.14.x to 1.17.x) it completely killed my root. What I mean by that is no Barnacle, no Titanium Backup, no SuperUser privileges!
Even from the Terminal Emulator, if I try to su into the system after "rerooting" with Universal Androot, it says that I need to be suid for it to work.
Upon typing anything else, suid, root, suid su, etc. it says permission denied.
ADB is a hit or miss because I can obtain shell root using SUPEROneClick for a short time in order to push and pull things from the device. Thinking this would be a cure all, I tried rooting with SOC and found out that it cannot do this because it cannot find the mount path. Digging around further, I find out that my Android can't access /etc/fstab because it doesn't exist on Android devices do to no media drives.
So, is there anyone out there that can help me in any way possible? I've been digging online for over 24 hours for this and have yet to find anything helpful/useful for my situation. I'm thinking if I can reset the "su" permissions or remove Busybox and reinstall, it could fix things? Idk, any help is appreciated!

I reinstalled the GOT 2.2.1 ROM and also could not get BusyBox to work. Even though the phone is rooted, apparently, BusyBox cannot remount.
Anyway, I'm no longer using Titanium. So long as you have real root access, there are plenty of other back up apps that you can use (Root Explorer, Super Manager, etc.).
Try z4root by RyanZA for rooting your phone. I'm sick of BusyBox and its fussiness.

Found out that after flashing with the sbf file for my build A854, I was unable to join the nTelos network. Had to get a new phone, for free of.course
Sent from the Milestone

[Q] Root

I have a stock KB1 AT&T Captivate. How would i root it? The update.zip method doesn't work because none of the packages are signed (E.Signature Verification Failed). Superoneclick root 1.7 doesn't either for some reason. It keeps saying temporary adb root rebbot device to remove whenever i try to use the shell root option.

sthodupunuri said:
I have a stock KB1 AT&T Captivate. How would i root it? The update.zip method doesn't work because none of the packages are signed (E.Signature Verification Failed). Superoneclick root 1.7 doesn't either for some reason. It keeps saying temporary adb root rebbot device to remove whenever i try to use the shell root option.
Click to expand...
Click to collapse
superoneclick works fine, but you have to set it to RAGE instead of PSNEUTER...look at the right hand side of the screen

rage puts superuser on the phone but it still doesn't have root privileges.

[Q] Can't get my S4 Active rooted

I was hoping for some help getting my S4 Active rooted.
But first, apologies if this thread is misplaced.
I have reviewed the following threads and followed the instructions therein, but to no avail:
http://forum.xda-developers.com/showthread.php?t=2347793
http://forum.xda-developers.com/showthread.php?t=2576460
http://forum.xda-developers.com/showthread.php?t=2596352
Against my better judgment, I tried various other options like One Click Root, even thought it was not certified for the I537; I also tried Kingo, VRoot and another Chinese root, and still nothing.
Phone:
AT&T
Samsung-SGH-I537
Version: 4.2.2
BaseBand: I537UCUAMF3
Kernel: 3.4.0-784654
From a new phone, I attempted to use activeroot.apk. I get the confirmation message that the phone is rooted, but Root Check, and Root Checker Basic both indicate no root. However, I was able to install SuperSU and update the binaries. I also installed SuperSU, Root Explorer, and Titanium Backup, and they all appeared to be working. Next, I installed XPrivacy.
However, at no time did any of the root checkers confirm root.
Today, SuperSU disappeared from my install list. I re-installed it, but upon attempting to update the binaries, I received an error message indicating that it has no binaries, and no way to install them. Titanium backup now gives me an error message indicating that I don't have root.
I unistalled activeroot, but when I navigated back to geohot's site to click on the "lambda", I got an error indicating that I needed an SD card to download activeroot. The card I was using at the time was a SanDisk 8gb SDHC Class 2 card from an old phone. So I researched and found that older cards, or cards from other devices can sometimes cause difficulties. So my current card is a SanDisk 32gb SDHC Class 10 that I formatted in the phone.
Now when I go to geohot's site on the default browser, I click on the "lambda", receive a notification that the download has commenced, but nothing further - no confirmation message. On Dolphin Browser, I still get the "SD card is required to download ar.apk."
Thanks to anyone who had read this far; and I would certainly appreciate any assistance that any of you are willing to provide.
Thanks so much.

You said you tried One Click Root. Have you tried SRS One Click Root from srsroot,com or did you try oneclickroot,com ? SRS Root worked for me on a cheapo Bauhn tablet - wasn't a device specific root, just used some sort of flaw, so (from my limited understand) the following instructions should apply to you (since I can't post links yet, I c+p'd)
1. Download the free SRS One Click Android Root v4.6 from SRSRoot One Click Root for Android (SuperUser) and install on your PC.
2. Download the free Root Checker by joeykrim from Play Store
3. Connect your device to your PC with the USB cable, wait for any drivers to install.
4. On the device:
a. Make sure Unknown sources is turned on – Settings>Security>Unknown sources
b. Make sure USB Debugging is turned on – Settings>Developer options and turn on at Top Right Corner if grayed out and turn on both USB debugging and Allow mock locations
c. Make sure the USB computer connection is set up – Settings>Storage and click on the 3 dots in the Top Right Corner – Click on USB computer connection and select Mount SD card.
5. Back out to the Home screen
6. Wait until the tablet goes into standby and the screen is black
7. Run Super One Click Root (you need to be connected to the Internet)
8. Select ADB Toolbox
9. Select Reboot Device
10. Wait for Reboot
11. Wait until the tablet goes into standby and the screen is black
12. Select Root Device (All Methods)
13. Follow directions and when you unlock the screen
14. Select Install SuperUser
15. When the root finishes turn off and restart the device and it should be rooted
16. Use the root checker
I hope this works for you. Credits to enviro8 from the androidtablets forum and obviously everyone who developed all that nitty gritty stuff.

Tiskael,
Thanks for your help. I followed your instructions, but I got some confusing results - the rooting program indicates that I have SU Root, but the Root Checker programs all indicate that I do not. Super SU and Root Explorer are still not working.
---= SRS One-Click-Root v4.7 =---
4:30:33 PM - Starting ADB Server..
4:30:38 PM - Manufacturer: samsung
4:30:38 PM - Model: SAMSUNG-SGH-I537
4:30:39 PM - Android Version: 4.2.2
4:30:39 PM - Build ID: JDQ39.I537UCUAMF3
4:30:39 PM - Board ID: MSM8960
4:30:39 PM - Chipset Platform: msm8960
4:30:39 PM - Getting OffSets.. : 0x8003 0x8005 (False)
4:30:40 PM - Checking Root access: True
[x] Device already have SU Root access, Rooting not needed.

My 14 day return period ends this weekend; I am going to do a Reset and start again from scratch. Certainly would appreciate any help if someone out there has had a similar experience.

Dansun said:
My 14 day return period ends this weekend; I am going to do a Reset and start again from scratch. Certainly would appreciate any help if someone out there has had a similar experience.
Click to expand...
Click to collapse
FWIW: This process worked for me:
http://forum.xda-developers.com/showthread.php?p=44165374#post44165374

Can't root my S5830 2.3.6 - tried everything.

Yesterday I installed Windows XP on my PC, cause I couldn't install phone drivers on 8.1. I downloaded Odin for S5830 and flashed a Polish 2.3.6 ROM (from updato.com) over the existing 2.1. Next I flashed 5.0.2.6 fix CWM. Then I realized, that to root my phone I need to have a stock recovery, so I flashed it and then rooted with root.zip. I ran the phone to look if there's a superuser app and there was, so I flashed the CWM back. When I wanted to upgrade the CWM (to flash custom ROMs) via terminal, I typed 'su' and it said that I don't have root access, so I installed an app to see if I have root and it said, that I don't. I tried everything to root my phone. I flashed the ROM again, did a factory reset. Every time I tried to root, it was like it's rooted but not or it failed to root. What I did wrong?

My guess is that the root.zip didn't install the su binary correctly(E.g. into the wrong path so that the vendor su binary is still called).
To verify that, you could try(from the terminal):
echo $PATH
That should show you a ":" seperated list of paths in which the shell(The thing running in the Terminal) looks for a binary.
You'd now need to go through every path in this list, and check for a su binary. If you find one, run it. For example:
ls /example/path/su
If this finds a file(indicated by it showing the filename, su), run it:
/example/path/su
If you find more than one su binary, chances are that one of them will work. If you don't find any su binary, the root.zip probably wasn't able to remount rw.
If you're a little more advanced, you could try rooting your phone manually(I needed to to this yesterday because I'm on linux):
Download SuperOneClick 2.3. The .zip contains a folder called exploits. These programs initially get you the root permissions. To use them, adb push them to /data/local/tmp (Because you have write and execute permissions there), and execute them. They either directly drop you to a root shell or restart the adbd with root permissions. Either way, you can then remount /system and copy the su binary from the SuperOneClick to your /system/bin and set the correct permissions. I can't really recommend this method unless you know what you're doing though.
Good luck!