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
Related
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
brandon2x said:
ok, so i tried to get help in the actual froyo 2.2.13 install thread but i'm not getting an answer.
i downloaded, installed, and it said it was successful.. i rebooted, went into the settings to see if it changed, and it still said 2.2.9. i tried to do it again and now my phone will not reboot into recovery using droid x bootstrap or rom manager... won't even go into it if i do it manually... i tried to uninstall bootstrap and rom manager and reinstalling, no luck. please help.
Click to expand...
Click to collapse
Try these comands from :
AllDroid Public Board»Motorola»Droid X Forums»Droid X Rooting»How to get 2.2, Rooted, on your Droid X
under:
If you have /system/xbin/su and /system/app/Superuser.apk, but cannot use "Superuser" (no prompts from Superuser app, "permission denied" when you try to run "su"), just do the following:
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow"
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
Open the SuperUser application on the phone (app launcher) and make sure that "superuser" isn't listed and denied. If so, "forget it" and return to step 2. If you can't find SuperUser, it's not installed and you should download from this posts attachments and "adb install Superuser.apk"
[optional] Run "mount -o remount,ro /dev/block/system /system"
This should help you get your su working again.
not sure on your process so if you still do not have the .13 I would go back to your process and see what you are missing. I rebooted into recovery from bootstrap when I installed mine. Then I had to do the above commands to get my su back.
If you still don't have it, try the FULL instructions from here:
MDW Presents: Droid X 2.3.13 - The Froyo Upgrade
read through it and see if #5 from step 2 pertains to you.
The biggest thing to remember is to mount before you select the file to load on your sd card.
This thread:
Motorola Droid 2Droid 2 Android DevelopmentHow to root the Droid 2
will also be helpful regarding root if you have further questions.
Hope this helps.
My su is working fine. Nothing is being denied when I open it. Just cannot get to recovery with any option... im lost...
Sent from my DROIDX using XDA App
Maybe just double check through adb shell even if you are not having su issues?
Run "adb shell"
Run "/system/xbin/su"
Watch your screen for Superuser app to prompt for permission and click "allow" (I never saw any request)
Run "mount -o remount,rw /dev/block/system /system"
Run "cp /system/xbin/su /system/bin/su"
Run "chmod 4755 /system/bin/su"
I had similar issues of nothing being denied after a successful install and had to do the su commands. It helped me to reboot into recovery afterwards.
Sent from my DROIDX, Froyo FTW. Obsidian?
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
brandon2x said:
Ok im still learning.... how do I "run adb shell" and do these commands you're telling me...
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I saw your post in the other thread. The best thing you can do is go through the links I gave you. Start with the root thread and click the more directions link in it. read through the processes and make sure you download all files and also understand what sbf is. Once you have all of the tools to do root and load whatever leak or rom you want you should be set. Understanding what is going on is key. This is a decision you are making to alter your phone for your benefit. Take the time to download SDK and whatever else is needed for your computer. Become familiar with what shell is and how to get there as well as explore within it. If you can get shell down and how to access your su and run commands, you should know enough to start. There are many things you need to research in order to be confident in what you are doing. I am sure you will not have a problem, just putting the time in to figure out everything is key. This is what I had to do.
I think that this is the best advice I can give you. None of us can know exactly what you are doing so you need to know the processes and choose which one is going to work for your circumstance. Good luck and if you have anymore problems I am sure all of us on xda can figure out a solution for you.
ok, finally, with a little help i got my phone rerooted and back to normal. learned a lot in the process too. thanks to all...
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
doughanson78 said:
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
Click to expand...
Click to collapse
Yes. Searching the forums for the various ways how to root 2.2.1
The problem is that it already says that I am rooted. But any app that requires root says that I'm not. I think it might have to do with being rooted with androot while the update happened. I want to try to avoid factory resetting the phone if possible.
doughanson78 said:
I was using Universal Androot on stock 2.2. The 2.2.1 OTA came through and after ignoring it for a few days, I accidently installed it. Now I can't unroot with Universal Androot, keeps saying "Failed! You still have the power, my lord.." Now things like AdFree say unable to get root access, and the SuperOneClick won't get past "waiting for device..."
Any way to fix this without completely wiping the phone?
Click to expand...
Click to collapse
I have the same problem. I tryed to restore to my 2.2 backup i made on rom manager before updating to 2.2.1 but it do not work.
nexusdue said:
Yes. Searching the forums for the various ways how to root 2.2.1
Click to expand...
Click to collapse
No research ... no gain.
it may say it but you dont.. why it says it cause it still sees the su in xbin and superuser in app.. but if you read the 2.2.1 update it did remove everything with root.. which sucks.. i have instructions on how to root 2.2.1 with rage..
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell
$chmod 700 /data/tmp rageagainstthecage
exit
go to sdk/tools
/tools>freenexus.bat
adb shell
$cd data/local/tmp
ls
check if all files are in
rage
su
Superuser.apk
busybox
$./rageagainstthecage
743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
DONT TYPE ANYTHING TILL YOU HERE THE ADB ON PHONE RESTARTS.
C:/adb kill-server
C:/adb start-server
adb shell
#
should get pound sign if not run ragecage again and dont do anything to you here the last ding on computer
#cd /data/local/tmp
#./busybox cp busybox /system/bin/
(if get read-only error do this
mount -o remount,rw /dev/block/mtdblock3 /system)
#chmod 4755 /system/bin/busybox
#./busybox cp Superuser.apk /system/app
#./busybox cp su /system/bin/
#chmod 4755 /system/bin/su
#exit
if $ type exit again
then go into terminal on phone, and type su
if you get the # you have root once again! yay!
now to install busybox command
hope this will help you to get root back..
i found this so this may work for you and easier to do
http://forum.xda-developers.com/showthread.php?t=803682
I have done both the rageagainstthecage to see how hard it would be but if you follow step by step, you'd be fine. I have also upgraded to 2.2.1 and tried SOC and that works as well. After I used SOC, I reverted back to 2.2 and loaded Rod's Rom again. I was curious
What is SOC and how did you get back to 2.2?
Sent from my Nexus One using XDA App
Super One Click root, I believe.
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
Hello everyone, I have been tring to root my phone for two day. I tried the z4root and it gets to rebooting and just stops, it finally reboots when I press the home button but it never installs super user app. I went to unlocker and tried androot, nothing. At the end of superone-click short fuse it failed the test for su permissions but installed superuser but it wouldnt do anything. Please help me root this phone. I have an Alltel phone. Kernel ver. 2.6.29-bc0d2cff firmware ver. 2.1-update 1 baseband ver. 2.42.01.04.23 if you need more info just pm me.
Thanks
I have never used these one click methods, but, if it actually roots it, just download super user from the market? Or just use one of the rooting methods found in the Development section (yes, you will have to read a short list of instructions).
I used z4 and it got stuck like you said, i clicked home and for me superuser was there.
but since not try rebooting and if its not there then, download android terminal emulator.. type su then press enter. if you see a # then youre rooted, so go just download superuser from the market and you should be solid
Try super one click. It installs superuser when it installs root files.
Sent from my HERO200 using XDA Premium App
stayclean said:
I have never used these one click methods, but, if it actually roots it, just download super user from the market? Or just use one of the rooting methods found in the Development section (yes, you will have to read a short list of instructions).
Click to expand...
Click to collapse
I tried it your way and this is what happens... So any Ideas
5. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2/system/bin/sh
6. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
operation not permitted
I tried this one.. It didnt work..
but thanks..
Okay so I have recently rooted my HTC Hero and would like to flash a custom ROM, but I am getting held up in ADB when trying to flash_image my custom recovery.
I have tried to put the Flash_Image file in the root of my SD Card, in my ADB folder, etc.... But nothing has worked so far.
Here is what I am doing, with the outcomes.
C:\Program Files\Android\Android-sdk\Platform-tools\>adb shell
$ su
# flash_image recovery /sdcard/CWRecovery.img
flash_image: not found
# ./flash_image recovery /sdcard/CWRecovery.img
flash_image: not found
Also I have adb pushed all the files required, and shortened the CWM Recovery image to 'CWRecovery.img' so I don't have to type as much lol.
My phone is rooted successfully, have installed BusyBox, SU, etc. So I don't know where the problem is coming from, but if anyone with any information could help, it would be greatly appreciated!
I couldn't tell you what is wrong with it, but have you tried using a terminal emulator on your phone to get it done? From there I'd just
$ su
#flash_image recovery /sdcard/CWRecovery.img
like you've done in adb.
I have tried doing it through Terminal Emulator.. But after trying for about 3 days, I have come up with something. Apparently in the 2.27.651.6 update there is no flash_image. So I had to downgrade to 2.27.651.5.
So I followed this guide http://forum.xda-developers.com/showthread.php?t=694572
Thanks to regaw_leinad for posting that!
Ah, now you've refreshed my memory. I actually had trouble with rooting my phone because mine was at 2.27.651.6 as well. I tried a bunch of the one-click methods and stuff, and they weren't compatible with it... Glad it worked out.
I think if you install busybox (via the Busybox installer app), that'll give you the flash_image executable on your phone. You shouldn't have to downgrade anything to get that functionality.
Not around my laptop atm but I believe Windows has two Android folders. One named "android-sdk-windows" and the other "AndroidSDK" . Have you checked to make sure you put the recovery.img into the "AndroidSDK" folder and not the
"android-sdk-windows" folder???
Also have you checked to make sure both img's are named exactly alike??
#Root-Hack_Mod*Always\
Thank you for the responses fellas, I tried to install BusyBox by downloading the App on the Market, and it said that BusyBox was already installed and asked if I would like to remove it or install over it, tried both options and still nothing. Tried re RUU-ing with .6 and doing z4Root, SuperOneClick, and tried RegrawMOD. Still could not access the flash_image.
Yeah, when I tried to root mine I also tried z4Root, SuperOneClick, andRegrawMOD, none of which worked for me either. I really didn't want to do the whole command line thing, but that's what I ended up having to do. This is the guide I used for root:
http://wiki.cyanogenmod.com/index.php?title=HTC_Hero_(CDMA):_Full_Update_Guide
I followed the directions in step one to install the SDK, then completed the rest of them. It actually wasn't as bad as I thought it would be, and after that I was able to flash a recovery.
Use Rom Manager from the market to flash a recovery
Sent from my HERO200 using XDA