1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
tsukisan said:
Good work on the first steps, next we need to flash a new recovery.img, I've been hearing that there is no easy way into the recovery at startup, what does "adb reboot recovery" result in, long story short if we can get a new recovery then we can flash unsigned roms including your su/root pre installed. Sorry I'm not more help on the legwork portion of this, I really need to get a garmin to work more on this, but p.m. me if I can help more as I don't pay enough attention to these forms
Click to expand...
Click to collapse
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
LiquidSolstice said:
Have you tried grabbing ROM Manager from the market? It allows you to install Clockwork recovery.
Click to expand...
Click to collapse
Do you know if there is a compatible recovery for the garminfone? You can't flash a sholes recovery on a garminfone.
ROM Manager is useless for the Garminfone. There are no backups for it and its not a supported phone.
"adb reboot recovery" I'll have to give it a try as well, now that I am also rooted.
I did a similar process... used androot (temporary root) to get rootshell with superuser app from the market.
I downloaded su binaries separately, fired up adb shell,ran rootshell.
I manually copied su to /system/xbin then used gscript lite to script the following:
/system/xbin/su -c 'mount -o remount,rw /'
/system/xbin/su -c 'mount -o remount,rw /system'
/system/xbin/su -c 'cp /system/xbin/su /bin'
After that I added the script to my home screen and I have one click root.
The changes won't persist until the boot image is changed to and repacked.
Note that the rootshell app is useless after a cold boot or if moved. It just crashes.
The most interesting thing is looking through the startup scripts that run.
There are parts from 3 or 4 developers commented out that,!among other things, show what to set to root it permanently,and what looks like loading parts of. the os from the emmc or sdcard.
And the automated test scripts built in come complete with a Garmin test phone number that can be called as well as a full suite of functional and regression test scripts that can be used to validate all functions including the Garmin apps automatically. The daemon even loads itself on boot by default.
It looks like the build they used was a virtually unmodified developer build. Hell,the boot scripts even show what to change to make it run in the emulator. That is my next project (getting it up in emulation so I can test different modifications)... well,that and see what it will take to get the Garmin app running in the latest android. I see no point in upgrading to the latest os if I lose Garmin functionality.
Being that the devs left nice comments for damn near every line and wrote very clean and elegant scripts, i would be shocked if it took very long to get Garmin up, at least in emulation.
Fyi, since piracy is illegal, I want to make it clear that the Garmin portions of my rant refer only to regaining functionality in the latest os.
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
I don't know why people say the Garminfone is more locked down or unflashable than any other phone. It comes with a flash_image program on the phone that lets you specify a destination partition and an image file, it will flash /system/recovery.img on boot and all the boot scripts are commented for how to do things like boot off the emmc. The developers left a bunch of services in the boot scripts but disabled to do various functions.
Tim2246 said:
1: ok step one download universal and root to sd card.
2: then download a file manager such as linda file manager.
3: download chainsdd SuperUser
4: go to settings then applications put a check next to unknown sources.Then go to Development and check usb debugging and stay awake.
5: use linda file manager and browse to sd card and install universal root "DO NOT INSTALL SUPERUSERBUILT INTO IT"
6: Install chainsdd Superuser, After install open it goto settings then scroll too bottom and click su binary it may fail the first time but click it again it will say Su binaries updated.
7: I am using root explorer i bought it from market.
8: after this is installed open it and be sure to click the rw option when you open it at top of directory. Now copy /system/xbin/su to your sd card for safe keeping along with rootshell file from sqlite_stmt_journals folder.
after you back them up too sd then copy Su file too /bin let it over write theres.
Now fire off adb and type adb shell then at the $ type su and walla full root.
Anyone have ideas on how to make it read only so system cant delete those files on reboot or automated way of putting the files in right place at reboot let me know.
Click to expand...
Click to collapse
So I ran into a little speed bump here, I'll post what I've done thus far and maybe someone has some feedback...
1) Open the applications settings menu for Android OS and Check off the option "Uknown Sources" and then click on "Development" and make sure options "USB debugging" and "Stay Awake" are checked.
2) Download and install the "Universal Androot" apk. application installer using the web browser on your android phone.
3) Launch "Universal Androot" and use the drop down menu on the main screen and select the option that states, "Do not install Superuser" and then click the "Root " button, the application will run a few scripts and then confirm success.
4) Go the Android Market, and download and install the following application, "SuperUser" written by android software developer, chainsdd.
5) Once "SuperUser" is installed on your phone, launch the application and click, "Settings" on the top right hand corner of the application, it will bring you to a list of options, scroll to the bottom, and click on, "Su binary v original", this will download a zip file containing any updates. (You may have to click this several times if it fails, it will eventually download)
6) Go to the Android Market, and download, "Root Explorer (File Manager)" and install it, you may also download this package elsewhere...
7) Open "Root Explorer" and make sure you are in the / "root directory" of the unit and then click the "Mount R/W" button at the top.
8) Browse to /system/xbin/ and copy file "su" to /sdcard
This is where I have a problem, I can not locate /system/xbin/su
Here is some additional information that may be relevant
Garmin
Hardware R1.7
Software 4.0.12
Android
Firmware 1.6
Kernel version 2.6.29
hey all!
I've tried following the directions like 10 times and i keep coming up short..i can't seem to get root.. It's odd. Would anyone be kind enough to post a video, or clarify the directions needed in a step-by-step fashion?
Thanks in advance!
Does anyone in the know have a timeframe for when we might know how to get rid of the t-mobile animation that plays when the phone boots up? I'd like to replace all the bootscreens with some wicked cool custom stuff, but gotta knock that pink crap outta the way first.
merwin said:
Ok... to permanently root your phone...
Use the method in the first post. Then, in Root Explorer go to /system/bin and click r/w (if it isn't already). Scroll down to governor.sh, long press and choose open in text editor. Add the following to the end:
mount -o remount,rw /
mount -o remount,rw /system
cp /system/xbin/su /bin
Save it. Now at every boot you will have rw filesystems and the su file will copy over. I am working on making a modified recovery.img to flash.
Click to expand...
Click to collapse
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Spazmogen said:
Sorry, but it didn't work for me. Rooting mine by manually pasting SU into the /bin folder works fine.
I copied/pasted your code over to the end of the file as described above.
Click to expand...
Click to collapse
Are you sure the version of su in /system/xbin is the one that comes with superuser? You can check by using either a terminal app or adb,going into the xbin folder, and type ./su
You should get a superuser request. If not, then something was not done correctly.
Thanks for the reply.
but since 2.1 Eclair was installed today, it's a moot point:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There is no SU in either /bin or in /system/xbin.
SuperUser by ChainsDD won't install the SU file, it keeps failing. Tried it 30x today.
Root Explorer only allows folders to be r/o now. So I am waiting on an update for that one.
How exactly did you get 2.1 on a Garminfone?
I have a Garminfone with 2.1 and all i did was download z4root from the market place and ran it and it seems to have given me a perminant root and i have no problems hopefully this helps you guys out it is a simple one click root unroot app.
Root is persistant. It survived a few battery pulls.
I have been able to get it into ADB REBOOT RECOVERY. A green droid guy with a yellow warning triangle appears.
One of the fellows in the Tmo forums claims to have gotten it into FASTBOOT menu options. If that is true, it would appear the boot loader is unlocked...
Garminfone 2.1 easily rooted...
I easily rooted my Garminfone 2.1 Eclair with z4root. It was one click and done with the options to temp or permanently root the phone it is also reversible.
Problem I am having is that I created an ext2 partition on my sd card but the phone doesn't recognize it. It was partitioned with "ubuntu livecd" with "gparted" partition manager. It also shows up in windows with "Mini Tool Partition Wizard 5" when the sd card is in a card reader attached to the pc.
Whats the next step? I want to move apps to the sd card. I have link2sd installed for this but can't figure out how to enable ext2 mount.
Also another good pc app to have if you trashed your sd card partitions is "Active Partition Recovery for Windows" works for all drives.
Issues - Rooting with Z4Root
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
z4root
Perseus71 said:
Hello,
I have a Garminfone that came with 2.1 version. I have downloaded Z4Root and tried both options Temp and permanent. But no Joy.
I made sure, USB Debugging is off. Can someone let me know what step am I missing ??
Much appreciate your time.
Click to expand...
Click to collapse
What exactly are you trying to do by rooting? Did you install SuperUser by ChainsDD? What app/file manager are you using? If you dont have this you won't be able to do anything. The apps you use for app/file management need to have root permissions or they will do nothing.
Mine rooted with z4root no problem and was able to remove all the fluff apps it shipped with that I didn't want. But this was only half of what I wanted to achieve. I haven't been able to move apps to sd, but I can't get ext2 to mount, not a problem because of the root I don't think.
What I have on my Garminfone 2.1
z4root
busybox (installed with z4root)
superuser
my backup root
uninstaller for root
super manager
Hope this helps.
Ok First off. Thank you very much for your time. It is greatly appreciated.
Well, Here's what I have done so far.
1. Downloaded and installed Z4Root from the Market.
2. Download and Install SuperUser by ChainsDD from the Market.
3. Ran Z4Root and first tried Temporary Root. That seemed to go fine until it was stuck after displaying the message ReBooting.
4. Next Tried Permanent Root Option after a Battery Pull. That asked me to turn on USB Debug. Did so and it seemed to go smoothly until that too was stuck with Rebooting message.
5. I tried the same Permanent Option after another Battery Pull. This time, it worked and the phone rebooted & came back. So I installed BusyBox from Market.
6. At this time I downloaded Titanium Backup. It complained not having root access. 7. So I started SuperUser and that showed an empty list under application tab. Went under Settings and hit the update. It failed but saved the Zip on my SD card.
8. I installed the Binary from Step 7 using Apps Manager. Tried SuperUser again. Still empty list for applications.
So there I am. I suspect I probably missed something somewhere. Possibly before doing Step 6 I should have done something. Can't seem to figure out.
Also earlier in this thread there was a mention that you will need to manually copy the binaris for SuperUser to certain specfic directory. Since it got installed successfully, do I still need to do it ?
On my newly compiled Android 2.2.2 build, whenever i type "su" in the terminal it says:
link_image[2033]: failed to link su
CANNOT LINK EXECUTABLE
I tried everything possible, I have busybox working, but not su. I have the su binary in the /bin folder and correctly symlinked to the /xbin folder and the permissions correctly applied in the update-script but it still will not execute. Any solutions?
Anyone.. (bumped because of massive amount of threads created each day in this section..)
Having recently bought an ePad V2, it was my first introduction to Android. Therefore having rooted, upgraded firmware, etc I've hit the same issue in trying to get Root Explorer working.
I've found a potential fix at h**p://zenpad.doubtechdotcom/?p=50 but haven't had chance to give it a go yet. You'll have to fill in the gaps of the URL as this is my first post and won't let me give external links.
Ignore my last post as I sorted my problem (originally being unable to mount R/W in RootExplorer). Here's what I did:
1. Uninstalled RootExplorer and Superuser.
2. Unrooted using Universal AndRoot.
3. Rooted NOT installing SuperUser.
4. Installed Busybox Installer from Market (noob fail as I never installed it before!).
5. Installed Busybox.
6. Installed latest version of RootExplorer.
Now I can mount R/W in RootExplorer and therefore I'm guessing my SU problem has gone away.
I am fairly new with using android phones, and I am encountering that error when I am attempting to update Superuser. I'm using a Samsung Admire SCH-R720 Android 2.3.4 and I rooted it with the One Click root. I've downloaded titanium backup, Root Checker, and terminal emulator to make sure I am really rooted. I've tried uninstall/reinstalling superuser, installing the superuser update fixer(which said signatures matched), and clicking on automatic update. Current version of SU Binary is 2.3.1-ef and everything in the update is fine until it gets to "Copying su to /system... fail!". Superuser does request for rights when it asks to gain root access which I click on Allow. I am also not sure if busybox installed correctly or not, but the Root Checker program I installed said busybox was installed.
Code:
Downloading manifest... okay!
Parsing manifest... okay!
Latest Version = 3.0
Checking installed version = 2.3.1-ef
Fixing Database... okay!
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... fail!
I got the same problem with my Galaxy S. Then I opened BusyBox Installer and it said that I have multiple busybox installed. I found busybox in /system/xbin and /sbin but the file size of the one in /sbin seemed abnormal, just 402 bytes. So I reinstalled busybox to /sbin. And rerun the superuser update after that. The fail has gone.
What program did you use to explore your system files?
Astro file manager
I only have busybox in system/xbin. I tried reinstalling busybox and i still get the same error when trying to update Super user. How can I uninstall Busybox? Please give a step by step if possible since I have no clue what the hell I am doing lol.
Edit 2: Er... I tried installing it also in system/bin, and it SEEMS like its working. Seems it's installed in 3 places, on my sd, bin, and xbin. It works now, so I won't touch it lol. Thanks for the help.
Hi everyone,
Same problem for me too.
after installed busybox in system/xbin using busybox installer downloaded from android market, the problem with superuser update was fixed.
I used in samsung galaxy s2..
Thank u
Hi All.
Sorry about the noob question, I am not a developer at all, and the only reason I rooted my Galaxy Note N7000 was so that I can update the ROM to the newest version of KitKat once the ROM is stable.
The problem is that last week I flashed the PhilZ-cwm6-XXLT4-OXA-4.93.6-signed file to the phone and it rooted successfully (Superclean asked for root access, I allowed it, and it appeared in the log of Superuser)
The problem happened last night when there was an OTA update for superuser, it said Su Binary needs updating, and I hit yes. I then lost root access as per Titanium backup.
I did a search and someone suggested removing and reloading the original superuser APK but that did nothing.
It seems the binary update pooched the root. Anyone successful in getting it back, or knowing how to?
Anyone can help on this?
It appears from the comments in Google Play that many people that were prompted to update the binary from superuser were left without root.
I lost root access on apps once.
All I did was:
1. re-install "superuser" from Google Play.
2. when opening "superuser" app, it asked to update the SU Binary.. and I allowed it to do so through recovery (TWRP/CWM). (I use CWM).
3. the phone will restart into recovery mode automatically, updating the SU Binary, then phone will restart again back into the OS.
This is all it took for myself to gain SU access again.
This should work if the ROM you're using truly does allow SU access.
OTHERWISE.
You could get the latest Super User.zip for your phone, and run it yourself through TWRP/CWM.
Hope this helps, or at least leads you to an answer.
new su binary is the culprit
Hello,
I too lost root after the su update - Superuser would not prompt any more, and all requests are denied after a timeout. Tried deleting Superuser data, deinstalling and reinstalling Superuser, same with some of the apps, but no avail. Then I noticed that sometimes after reboot /system/xbin/su worked when in android debug bridge shell, so I could get root. Then I replaced the su binary with a copy (in my case of OTA rootkeeper), and all started to work again.
Steps to replace:
1. become root in ADB shell using existing su binary
2. remounting system rw
3. bring replacement su to a ext-fs-partition of your device (needed for setuid)
4. make sure file permissions are set to 06755 (-rwsr-sr-x)
5. exit root
6. become root with newly copied su binary
7. replace defect su with new su
8. remount system ro
Hope koush will stop delivering this defect su soon ... I did mail him already ...