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!
Related
So I've decided I want 2.2 at least on my CDMA Hero. I am following this guide.
wiki.cyanogenmod[DOT]com/index.php?title=HTC_Hero_%28CDMA%29:_Full_Update_Guide
Well Here are the problems I am running into.
I can get Temporary root access to my phone. (Meaning I get # in the shell and my id check gives me a 0) However on restart i loose that root access. I have pushed the flash_image, su, Superuser.apk, and the recovery rom (using amon_ra) to their respective folders (flash_image goes to /sdcard/) and from what I can tell my su isn't working properly.
Essentially heres what happens
Shell opens up fine
#su
su
#cd /sdcard/
cd /sdcard/
#
My number sign after cd is still JUST a number sign. I was expecting #/sdcard/ but didn't get that, should I?
The reason I ask is because when I hit flash_image <image> it gives me
flash_image: not found.
I've personally checked that flash_image is on the root directory and it is, it is also named exactly that. So I can think of no reason flash_image isn't working except my su is bad. However just afterword I do an id check and I'm still root...
ugh...
*frusterated*
halp?
What ROM are you running right now? What version?
http://forum.xda-developers.com/wik..._CDMA.png#Rooting_.2F_Un-rooting_.2F_Flashing - has all links you might need to root and flash a ROM. Try and report back...
why dont you flash clockwork....it is easier (i think) and is very straight forward...
get rom manager from the market and flash CW recovery and then boot from it and flash the rom you want....
One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...
there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date
I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.
http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App
OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!
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
I had Emanon's ROM on it for a while, but it just came crashing down so I flashed CM7.2... boots a lot faster, seems a bit more stable.
But I used to have full access, and now I don't. How do I get it back? I just want to switch out the bootanimation.zip.
Came across this:
status_six said:
Hi there, you need to have s-off (aka security off or full root) to write to /system and /data with the device booted, i.e. using root explorer etc.
You can also do it with s-on, but you have to to that with your PC via cmd prompt and adb shell which is less convenient.
Great guide to getting s-off here, took me <10 mins!
http://forum.xda-developers.com/showthread.php?t=794314
Click to expand...
Click to collapse
I've just finished mucking around with a HTC, so I'm a bit confused, but I gather there's no fastboot mode on the Mini, so I can't see how I can access the phone's flash from the PC without using the ADB shell...
And I'm not sure s-on/off is even relevant to the Mini... halp!
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Kimmoth said:
Okay, I was able to do it with Absolute System; must have missed the SU prompt or suffered a system glitch when I was installing ES File Explorer.
Anyone know how I can grant SU privileges to ES?
Click to expand...
Click to collapse
Go to the su app and grant the permission for ES
you are coming from HTC so I am clearing some points some of them are of-topic
no fastboot instead download mode
bootloaders are not locked so no s-on no s-off in Samsung devices
use Odin multidownloader to flash firmware through PC
never use rom manager on this mobile, else a brick will be waiting for you
galaxy mini is easily root able
just flash an update.zip in recovery and you will be rooted
after root to change something in system
type mount -o remount,rw /system then do whatever you want to
stock rom cannot be backed up with the help of cwm
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
doublea70 said:
Thanks for making this so easy! Updated to JB without losing anything. However, I hit a snag. Everything was okay until I tried to update su.bin via ES File Explorer. I couldn't write to system/bin, and couldn't get the app to gain root access again. Now I'm stuck with no root... Can I adb the file in, or somehow write to system/bin? Or will I have to do this all over again? I just really don't want to lose any settings.
Click to expand...
Click to collapse
Yes. The un-updated version of Su should be enough to give ADB root, so you can use ADB to remount the filesystem with r/w, then push the new su.
For future readers who don't know:
First, navigate to ADB in the terminal of your choice (Command Prompt on Windows, Terminal on Linux/OS X. I'll be using Windows.)
Do this by typing
Code:
cd /your directory ADB is in/
In my case, it now says "C:/Users/MyName/Desktop/ADB" because I keep ADB on my desktop like a silly person.
Now, remount your filesystem in ADB with read/write access. The command is
Code:
adb shell su mount /system rw
Now, we can push that new SU binary with ease, with
Code:
adb push c:/The_Directory_you_keep_su_in/ /system/bin
In my case, It was just "adb push c:/su /system/bin" because I keep files I want to push on the root of my hard drive, like a silly person.
Now, switch system back to read only with
Code:
adb shell su mount /system ro
All done, use Superuser app to Check for updates. It should say you're up to date, and if you update anyway, it'll do it without failing.
Is there another method to this? I have this problem idk why it says I have root saved but it won't let me restore? I don't have computer access and my root keeper says I have root?
Sent from my MB886 using Tapatalk 2
Gaining root access... fail!
ripin150 said:
Update:
Holy crap, I just thought of something like, way stupid simple.
Just update Su before updating to 4.1. Then simply use OTA Rootkeeper like normal.
Again, I sincerely apologize for not realizing this sooner, and wasting a lot of time.
I guess I'll keep this guide here for people who forgot to update su before updating. Sorry guys.
---------------------------------------------------------------------------------------------------------------------
You might want to read this all the way through, THEN do the steps. Good Luck.
Remember to have Unknown Sources enabled.
First off, you're going to need to start off with ICS, rooted. Thats a pretty straight forward process, and can be accomplished totally with the AHD Utility (Here). Go ahead and install OTA Root keeper, we're going to need that.
After Root Keeper is installed, locate it with your favorite file manager, I prefer Root Explorer, but anything that can mount with r/w is great. It's going to be in /data/app. Copy the APK to /system/app and install it. Do this exact same thing with your file manager's APK. This way, they wont be uninstalled when we update to 4.1.
Run OTA Rootkeeper. Backup Su, and temp unroot. From here, you can upgrade to 4.1 without losing your essentials by using stock recovery to flash the 4.1 zip.
So that's finished, you're now in Jelly Bean and you decide not to read the rest of this because you think "oh i know where this is going, I flashed roms back on the atrix 4G all the time, im a PRO at this phone stuff" and you've restored root with Rootkeeper, and you're like "wat the heck, i dont have root, lying tutorial". Have no fear, we're not done yet.
In JB, open Rootkeeper and restore root from backup.
Now go update the Superuser app from Google Play (Anyone else ever call it Market still?)
Ok, almost done. If you were to go in to Superuser and update the binary, it would not work (I don't have an explanation for why, it just says Root failed. Probably since we're not actually rooted (but we have su so wtf mate)) So what we're going to need to do is go download the binary here from androidsu.com.
Extract the su binary from the zip and put it on your SD card. On your phone, using that trusty File explorer from earlier, mount the fs as r/w and put su in /system/bin. Make sure permissions are all checked EXCEPT Group Write and Others write. (I don't know if it makes a difference, but I don't want to mislead you.)
Alternatively, you can use ADB. Mount the file system as r/w on the phone. Put su on the root of your hard drive, and use " adb push c:/su /system/bin "
Then it's done. Test root from adb with " adb shell su " and from the phone by using any root app, or typing "su" in terminal emulator. Or just root checker.
Click to expand...
Click to collapse
After following all the steps. When i install root checker, it is telling me i don't have root.
Below is what i got back from superuser:
Su Binary Updater
Downloading Manifest... Okay!
Parsing manifest.. Okay!
Latest version = 3.1.1
Checking installed version = 3.1.1
Upacking sutools... okay!
Checking current install path.. /system/bin/su
Downloding new binary.. okay!
Gaining root access... fail!
Any idea to help?