Database Info

****ROOT EVO After July 1 OTA Update

I tried every method, read every thread in every forum in an effort to root my EVO. Nothing worked. I was driving myself mad and spending tons of time. I Eventually I came across a post which directed me to XDA Developers Thread ---==={ROOT GUIDE}===--- | 1.47.651.1 ROOT, post 579 by SharkUW . I have used this on my own phone and I don't see a reason why it wouldn't work. I modified some of the instructions to make it clearer. The instructions may not be exact, and there is some seat-of-the-pants involved, but I got it to work. Use it at your own risk.
Prerequisites (follow in order)
Android-SDK developers program. I loaded it to C:
JAVA SE Development (use correct bit – 32 or 64). loaded in C:
Microsoft .NET Framework V 4.0
Reboot your phone and do a factory reset. Erase everything
Set phone to Charge Only and USB debugging
Open the stock browser and sign-in with your PCS phone number. Leave running.
Shutdown the phone, then restart
Make sure ADB is functional on your computer. You should be able to "adb shell" (confirming adb is working, exit shell if you're in it).
Extract the Do_root.zip (link below) and place all these files into the SAME folder as adb.exe. I have not included the appropriate PC36IMG.zip. Get it here. http://forum.xda-developers.com/showthread.php?t=701835 Leave the name as "eng-PC36IMG.zip". Place that in the SAME directory as well as the .zip.
Open a command prompt on your computer. point directory to Android-SDK directory\tools and a list will come up… click on "root.bat” and click RUN.
If it hangs for more than 30 seconds with the browser ****, CTRL+C, yes to kill the bat and just run it again.
Follow the directions. Your phone is going to reboot. It is then going to do a little **** and reboot into the boot loader. Keep track of the Command screen and wait because some steps take a while and there is no way of telling if it’s working. Nothing lasted more than 5 minutes. Eventually it will be in a "bootloader" and ask if you want to reboot. Say Yes with a Volume UP.
The .bat is now done. You have root. (not sure if next part is true) You now need a custom recovery to flash a proper ROM beyond the scope of this guide.
In original instructions but I’ve found the following Recovery step and code is not necessary: Now take the last step and flash the recovery.img that will already be on the root of your sdcard. To do this, after the PC36IMG flash:
Code:
adb shell
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img
To check for root do ADB Shell and should get #.
If you're all advancedy you can put on a different recovery image.
IMPORTANT If you get a message here about "not writing bad block", flash it again until you get 0 errors. I don't know how common it is, but personally my recovery has issues with flashing. Do NOT let that be a bad flash.
Attached Files
do_root.zip (4.07 MB, 49 views)
________________________________________
Last edited by SharkUW; 7th July 2010 at 01:06 AM.

Going to try it tomorrow and hope it works. Thanks

Where are the attached files?

Can't find the do_root.zip file. Seems there is no attachment, please re-post. Thanks.

I tried to attach the do_root.zip file and a link to Toast 2 file. If that doesn't work, go to the referenced post #579 here: http://forum.xda-developers.com/showthread.php?t=718889&page=58.

Have you tried this SimpleRoot? I just did it, and it worked flawlessly.

Vivix729 said:
Have you tried this SimpleRoot? I just did it, and it worked flawlessly.
Click to expand...
Click to collapse
Simpleroot ftw.

mattrb said:
Simpleroot ftw.
Click to expand...
Click to collapse
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.

gmanvbva said:
QFT. I did simple root (I still setup adb and ensured it was working first) and then flashed the rooted Stock 1.47 ROM in about 40 min. I think most people that are running into issues with Simpleroot do not have adb setup properly or they did something inadvertently and need to clear out the files/cache and need to start over from scratch.
Click to expand...
Click to collapse
I did simple root and it worked fine too. I don't think the issue is adb being setup since he has an adb file in his download.

Update from a few days ago.
Just got a new SDHC card and simpleroot worked. The SDHC that came with my phone died. I placed a spare in there that was a 2gd regular micro and Hboot would not ready the IMG for nothing.
If simple root is not working then it's the Sh!tty card acting up.
Happy ending for me.

I just got my phone yesterday did the ota simpleroot and seems like it worked fine
but now i dont know what to do next
to get custom roms or froyo 2.2 or anything lol

Awesome post |OP|.
My desktop is Windows 7 x64 and doesn't play nicely with the standard tools.
I was forced to adapt your root.bat script to an OSX friendly BASH script.
The only requirement is that you download the android SDK from developer.android.com/sdk/index.html (apparently, I'm too new to post links).
The steps I took to get root:
Unzip the android SDK
follow |OP|'s instructions, unzipping the contens of do_root into [sdk-root]/tools/
unzip the attached bash script to the [sdk-root]/tools/
run my bash script from the [sdk-root] folder instead of root.bat - type "./root.sh" without the double-quotes
Grab a copy of Froyo while your phone is being rooted

[ubuntu Q] Any way to root using Ubuntu?

is there a way to use ubuntu to root the epic? I have ubuntu and I want to root my epic but I can't figure out how to use the one-click method because I can't really use the drivers. I was trying to use the terminal with adb but I don't really know what I am doing.

linux doesnt need drivers i made a one click script for linux ill see if i cant find it
http://www.mediafire.com/?hk59z8j5dve6tgf
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable

You can try following along the run.bat script included in the one click root. I did not need to install any drivers to root using Ubuntu, but I did download the Linux version of the android sdk (from Google) just in case (instead of using the adb included in the one-click-root download.
If you have your android-sdk-linux_x86 directory in ~/Downloads/, and you extracted the one.click.root file into ~/Downloads/ as well, here's what you could do:
cd ~/Downloads/one.click.root
(Now you're in the location of the one click root files.)
Next, type each line of the run.bat file manually. Any time you see "adb" replace it with:
sudo ../android-sdk-linux_x86/tools/adb (command)
You'll need to adapt a bit to your situation, but because most of the adb commands are native to adb and run on the phone, they should work verbatim on your Ubuntu system.
Didn't someone put out a Linux one click root, though?
EDIT: Yes, shabbypenguin did. Looks like he posted it above me before I finished typing my post. Whoops.

Complete Big edit....
I thought I bricked my phone but I didn't. I ended up getting the permanent root. I used this guide http://forum.sdx-developers.com/epic-development/adb-root-exploit-test/
Is there anything special I am missing? like busybox? or remount scripts? not sure what either of those are.

remount allows your system to have rw access with a simple command, busybox.. think of it as an extended shell
the zip i included in my post is based off noobnl's latest version and works fine with linux. i made it while using ubuntu

shabbypenguin said:
linux doesnt need drivers i made a one click script for linux ill see if i cant find it
[snip]
download that and run the clickhere.sh it should root you just fine, you may need to make the script and adb executable
Click to expand...
Click to collapse
Thank you so much for this! ... "You have no chance to survive make your time" means I'm rooted?

i made version 2, its in my sig, will root and install clockwork mod 2.5.1.0

[Tool][Guide]Linux tools

I. How to root Defy via Linux!
A simple script for rooting Defy from Linux. I use SuperOneClick 1.9.1 files in my script, and I rooting succesfully my device from Ubuntu 11.04.
It does not install "bussybox" and "Android Terminal", just "su" and "Superuser.apk".
I hope it will work for someone else too.
Using:
0. install usb grants on your computer (see adb install method)
1. unzip file
2. run RootDefy.sh
3. after succesfully install, reboot phone (./adblinux reboot)
Download:
(version 0.2) download
Changelogs:
Code:
[B]02.06.2011:[/B] Version 0.2
- Added header to script
[B]13.05.2011:[/B] Version 0.1
- correct Defy device number
- correct /system filesystem type and path
[B]12.05.2011:[/B] First release
II. How to flash a SBF via Linux!
0. charge your phone 100%!
1. download and extract your sbf file: download
2. download sbf_flash file (same directory): download, or see the editor blog
3. chmod +x sbf_flash
4. sudo ./sbf_flash xxxxxx.sbf
Now your phone should start flashing, and phone will reboot when finish it.
III. How to unroot Defy via Linux!
Go to this topic: link

Nice, will try this =)

nice work!
I have been looking for it
Thx.

Great. I'm under linux too, each time I root a rom I launched a script from sdcard. For next time I'll test your script.
Fyi, I flash rom under linux too. I use 'sbf_flash', that works very well!
( but unsuccessfull under mac )
Now I'm looking for deodex script. I wrote and test some but still get errors with some apk and jar
Sent from my MB525 using XDA App

rumcajsz said:
I made a simple script for rooting Defy from Linux. I use SuperOneClick 1.9.1 files in my script, and I rooting succesfully my device from Ubuntu 11.04.
It does not install "bussybox" and "Android Terminal", just "su" and "Superuser.apk".
I hope it will work for someone else too.
Using:
0. install usb grants on your computer (see adb install method)
1. unzip file
2. run RootDefy.sh
3. after succesfully install, reboot phone (./adblinux reboot)
Download:
link
(sorry for my bad english)
Click to expand...
Click to collapse
I believe that this script will not work for Motorola Defy for the following reasons:
1)on lines 17-19 the script checks if there are any udev rules matching a Samsung device (for Samsung devices the idVendor attribute is 04e8, but for Motorola devices, the idVendor attribute is 22b8).
2)on line 53 you are remounting the /system partition specifying that the file system is yaffs2 and the device block is /dev/block/mtdblock0.
On my Defy the file system used is ext3 and the device is /dev/block/mmcblk1p21
I have managed to root my defy a few days ago, from my linux box, using the files used by Sooperonelick (rageagainstthecage, superuser.apk, su and busybox) but considering the facts stated above.
@MisterWB
Fyi, I flash rom under linux too. I use 'sbf_flash', that works very well!
( but unsuccessfull under mac )
Click to expand...
Click to collapse
Did you used the last version for sbf_flash? On the original site its stated that the same binary should work on linux and mac

tuxtm said:
I believe that this script will not work for Motorola Defy for the following reasons:
1)on lines 17-19 the script checks if there are any udev rules matching a Samsung device (for Samsung devices the idVendor attribute is 04e8, but for Motorola devices, the idVendor attribute is 22b8).
2)on line 53 you are remounting the /system partition specifying that the file system is yaffs2 and the device block is /dev/block/mtdblock0.
On my Defy the file system used is ext3 and the device is /dev/block/mmcblk1p21
I have managed to root my defy a few days ago, from my linux box, using the files used by Sooperonelick (rageagainstthecage, superuser.apk, su and busybox) but considering the facts stated above.
Click to expand...
Click to collapse
Thanks for the advice, I will correct their lines ...

You're welcome.
If you want to make a script that will work on all devices you could parse the /rpoc/mounts file from the device and extract the device that's mounted to /system and the file system used (in this case the udev part would also need to be modified)
Also, did you check if the adb binary you are using doesn't need any other external libraries installed by Android SDK. I'm asking this because in the sooperoneclick zip I downloaded, I saw some dll files which I' guess that are used by the adb windows binary, and I don't know if the linux adb binary doesn't need some external libraries, which should also be included in your zip file.
Good luck

tuxtm said:
@MisterWB
Did you used the last version for sbf_flash? On the original site its stated that the same binary should work on linux and mac
Click to expand...
Click to collapse
Yes I use it on mac+linux... but on my mac, at beginning sbf_flash see my phone, but when I want to flash a sbf, sbf_flash freeze on message "waiting for phone" It seems usb behavior varies on mac models.
Anyway, thanks for your reply.
@everyone
This thread could-be a good space to exchange about linux tools.
In this case rumcajsz should change the first post's title, and maintain text, links ...
What do-you think about ? Or do-you prefer a new thread ?

MisterWB said:
Fyi, I flash rom under linux too. I use 'sbf_flash', that works very well!
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
where can i download sbf_flash?
thank you.

MisterWB said:
@everyone
This thread could-be a good space to exchange about linux tools.
In this case rumcajsz should change the first post's title, and maintain text, links ...
What do-you think about ? Or do-you prefer a new thread ?
Click to expand...
Click to collapse
Great idea, I changed it.
johnw.xda said:
where can i download sbf_flash?
thank you.
Click to expand...
Click to collapse
The download link in the first post now.

usb tether
Hi,
thanks for both script, works well for me.
I like: go first to recovery menu (vol donw and power) with usb connected and run the flashing script, perfect...
How do you usb tether with your defy and linux ? (ubuntu)
I use this a lot with my previous phone htc.
I run the french froyo rom (http://forum.xda-developers.com/showthread.php?t=1072367), but i did not found the m.stone usbtether app.
Maybe you got a sbf with every things working natively with linux and no blur?
Regards and BRAVO again...

usb tether
Usb tether is ok with proxoid and port fowarding with the defy (see proxoid wiki).
It is not like my old htc as the device is seen by the pc as a network interface (usb0). In this way you got an IP to communicate with your phone (i am using it for vlc remote for example and other app where ip is needed).
When i plug my defy on usb I got 3 menu: motorola pc, windows sync, sd and nothing.
Is there a way to have menu without motorola and windows stuff ? ( sorry for duplicate the question between this form and the french froyo rom one...)
++

That option should be related to the Media Portal application. Maybe if you would rename it (by changing the apk extension to something else) would do the trick. I didn't test this so, I can not tell you if it will work or if it won't brick your phone
/LE I have just renamed the MediaPortal.apk and apk for the Media Share (I belive it is HomeSyncWizard.apk)then rebooted the phone, but the "Portal and Tools" and "Windows Media Sync" options are still there.

I have to check what is the difference between HTC and motorola.
Tkx for the try,

added "unroot" to first post

On an aside, superoneclick and sbfdepacker can both be ran with mono
If you running 64bit distro ensure libncurses 32bit is installed

I tried SOC & mono (ubuntu 10.10, 11.04: 32 bit), and it doesn't worked for me.

http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537
Follow the link on there, it will work although the script's here do it just as well anyway, but the sbfdepacker, I can find no equivalent of.

I tried this way...

Hi,
If
i root an froyo offical french rom with this script to backup my stuff
install 2nd-init
upgrade to an GingerRom with fixed sbf
then flash back the official french sbf
will i keep my warranty ?
No way to find out i rooted my defy?
I will try mono...

[Linux/Mac] ADB & Fastboot (Un)Install Script [Team BlueRidge]

[Linux/Mac] ADB & Fastboot Install Script
I have created a script to be used to install ADB and Fastboot on a Mac or a Linux computer. Simply run the script in Terminal or a similar application and it will copy ADB and Fastboot to /usr/local/bin/
Also, as of Version 3.1 this also installs the JDK for Linux-based systems.
While advanced users probably won't need this, it would be good for new users who need help using the ADB and Fastboot commands.
You can see the source at GitHub.
Download
If you have any problems or errors, let me know.

Changelog:
20171202
Moved entirely to GitHub
On Debian-based Linux, installs the adb and fastboot packages
Other systems, the binaries are pulled from Google's website
Executables are given +x permissions
Version 5.0
Hosted on GitHub and Google Code
Uses latest adb and fastboot (as of April 3, 2014)
Install to /usr/local/bin/
Version 4.1
Uses cp rather than mv
Hosted on GitHub again
Team BlueRidge project
Version 4.0
Now installs adb and fastboot to /usr/bin/ which is a more appropriate directory for the files.
Includes Readme now!
Version 3.1
Added JDK Install for Linux
Version 3
Created separate scripts for Linux & Mac
Updated uninstall script
Version 2.1.1
Fixed errors in installer
Version 2.1
More code efficient.
Better comments in script.
Version 2
Combined installer scripts into one Universal
Updated Uninstall.sh to remove udev rules
Version 1.1
Added udev rules for Linux
Version 1
Initial release

Linux
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.

shootind5nukes said:
Didn't work on linux, I suggest making a seperate script for linux, I believe the problem is where it detects linux. It gets sudo but nothing more. I ran each command by itself under linux and it worked. Thanks.
Click to expand...
Click to collapse
Thanks! I'll fix that and post an update soon!

JDK is now installed on Linux systems!

Now hosted on Google Code rather than GitHub.

Now installs to /usr/bin/, which is a more appropriate directory as these files are not required for normal system booting or are required for the general functions of your operating system.

i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices

boneskid1 said:
i know this thread is old but i need some help.
my devices are not showing up after running the script.
i used adb devices and ./adb devices
Click to expand...
Click to collapse
Does it say that ADB is not found or your devices?
Try enabling ADB (USB Debugging) on your device if it says no devices were found.
Gingerbread: Settings>Applications>Development>USB Debugging
Ice Cream Sandwich: Settings>Developer options>Android debugging

Thanks!!!! This worked perfectly. Using Ubuntu 11.10.

romuloxiii said:
Thanks!!!! This worked perfectly. Using Ubuntu 11.10.
Click to expand...
Click to collapse
I'm happy I could help! Don't forget to click "Thanks" if you liked it!
If you have any issues in the future with it, please feel free to let me know!

Good news!!! This is now a Team BlueRidge project and is on Team BlueRidge's GitHub

since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious

prflash3 said:
since tar.gz files are linux that means I download the zip file on my mac right? sorry if the question is obvious
Click to expand...
Click to collapse
Download whichever for whichever platform. It's the script inside that you use that matters.

Trying to run the script on OSX, but when I am prompted to enter my password I can't type anything. Please help.

Ditto ul49, being prompted for a password, please advise

Simply type your account password. It won't look like anything is being typed but it is. This is how the "sudo" command works. It is for security.

really glad i found this.
i run "sh "sh script name" and i get this error
ADB-Install-Linux.sh: 5: ADB-Install-Linux.sh: Syntax error: newline unexpected
not sure if it's installed or what
thanks for making this set of scripts and if u could advise me on that error id be grateful.
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
crazy
apt-get install android-tools-fastboot
and
apt-get install android-tools-adb
worked

Just released the first update in two years. Sorry to leave this project unmaintained. The files are now hosted by Team BlueRidge as Google Code no longer supports downloads.

First, thank you very much for putting this together for fellow users. While I'm not the most savy of guys I thought I might just share my experience while installing this ADB + Fastboot package on my MacBook Pro (mid 2012) running OS X Mavericks 10.9.3 in the hopes that somebody might benefit from it as well.
So here it goes:
I tried running the installation script found in "Androidv5.zip" which up until now is the latest version (I think). The script failed to install:
"This will install ADB and Fastboot on your computer.
Root Permissions required. Please type your password.
Password:
Changed directory to /Users/User/Downloads/Androidv5
Moving ADB
cp: /usr/local/bin/adb: No such file or directory
ADB Moved to /usr/local/bin/adb
moving Fastboot
cp: /usr/local/bin/fastboot: No such file or directory
Fastboot moved to /usr/local/bin/fastboot
You may now run Android Debug Bridge and Fastboot commands
Have a nice day."
So I figured I'd open the script file and run each command manually but they would still not work. I then decided to open the target directory
from terminal and it couldn't find it either, so I openned the /usr/ directory to find where the /bin/ directory was... and I found it at | /usr/bin | instead of | /usr/local/bin |.
I ran the commands in the script again manually one by one with the target directory set to | /usr/bin | and then closed terminal and reopened. After that I tried running "adb devices" and the output was "permission denied".
I then applied a "chmod 775 /usr/bin/adb" "chmod 775 /usr/bin/fastboot", closed & reopened terminal and voilà it worked!
Again I'm not a savy guy... there might probably be a better way to do this or perhaps I didn't run the install script as it was supposed to but anyway I decided to let you guys know how it went just in case it proves useful to somebody else....
Then again thanks a lot for sharing this! I finally have ADB + Fastboot on my Mac without having to nag about downloading the Android SDK. :laugh: :good:

[Q] Any suggestions on how to regain root after the OTA ICS update using Linux?

Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.

You should be able to just run the root.bat if you have the folder with all contents extracted to desktop.
Sent from my MB865 using xda premium

Aimless Rambler said:
Any suggestions on how to regain root after the OTA ICS update using Linux? I've read through various posts scattered about the innerwebs regarding how using Windows but I'm a stubborn Linux user. I've downloaded the A2_ICS_Root Zip and explored the contents but not sure how to properly utilize them. I've rooted the phone in the past manually using Android SDK, Linux Terminal, push/adb shell commands and Motofail but of course lost root with the ICS update. If I don't get an answer I may attempt to follow some of the scripting used for Droid/Razors post ICS, of course tailored a bit. Although my Superuser app is still showing it's pretty much useless, like others with the same issue I've read about, it's still written into the system but no longer rooted. I've tested phone access in terminal but get the R/W error message ... no permission, etc. So ... I thought maybe folks here may have an answer for us semi skilled Linux users.
Click to expand...
Click to collapse
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip

Re-Rooted!
jimbridgman said:
Use the process and scripts I created for the leak/OTA. All you need to do is step 6 in the following link, and use the shell not the bat as others noted... if you are running linux, I am sure you already knew that.
Link:
http://forum.xda-developers.com/showthread.php?t=1779968
6) Boot into ICS, and root using the zip below, you will connect the phone to your computer and use the root.bat (unzip this folder to your desktop) for windows and root.sh for linux/mac.
The script and root files:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!

Hmm
Aimless Rambler said:
Thanks Jim! I actually figured it out on my own, of course using the same zip file you provided which I had found in another thread.
I extracted the file into it's own folder, put the phone into debug mode and made sure MTP (media device) was checked, hooked to USB then ran a few checks in Terminal to make sure the device was recognized. Then I dragged "a2_ics_root.sh" into the open Terminal window and let it do its thing. I already had Superuser installed in earlier root (prior to ICS) so maybe that's why I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error but then it said "You are rooted!". So to check to make sure I was actually rooted I ran the adb shell command and got this "[email protected]:/ $" then entered su, and got this "[email protected]:/ #"
Success!!
Click to expand...
Click to collapse
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm

update on strange problem
Aimless Rambler said:
Well I don't have root after all? Once unplugged from computer I ran a terminal emulator app on the phone and tried to access root but it says I don't have permission, as well as a few other apps I tried to install. Strangeness. As it looks above in quote is it just a temporary root? One thing I did notice after the OTA ICS update is that the superuser app remained. I tried a factory data reset thinking it would take it off but it didn't. Is my original rooting (GB Motofail) SU somehow stuck in perpetuity within some system file somewhere which is fouling up this root? So how would I go about a clean install of Superuser? I updated Superuser on Play Store but no difference. Hmm
Click to expand...
Click to collapse
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!

Aimless Rambler said:
First of all I apologize for all this confusion with replies to my own questions but I don't know any other way to relay the information. I'm troubleshooting as I go and hope it helps define what the issue may be and maybe a fix haha! Okay!! So I get root access easy as pie in terminal, no issues whatsoever, so I did a little searching and this is what I've found. The problem seems to be su is listed twice within my system folder (see below).
PROBLEM
[email protected]:/system/app # ls
Superuser.apk <<< is listed in the right location
# cd ..
[email protected]:/system #
[email protected]:/system/bin #
su <<< is listed here
[email protected]:/system/xbin #
su <<< is also listed here?
That can't be right? Shouldn't it only be in the /bin folder? Having downloaded the A2 ICS Root zip file I explored the Windows root.bat file in a text editor and saw that SU is suppose to install to /bin. So how the heck did it get in 2 different locations? ha!!! I'm guessing this would cause some issue but before I go deleting the extra file I thought I should inquire first. Haha!
Doh!!!! I know it's got to be something I did!
Click to expand...
Click to collapse
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.

Rooted again??
jimbridgman said:
That is completely correct. The su in /system/xbin is a link to /system/bin/su. And that is correct, and how it should be.
Please explain your issue in more detail as I am not fully understanding what is not working.
Click to expand...
Click to collapse
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin it alone did not fix the problem. I still could not access root. So I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!

Aimless Rambler said:
The issue was my phone was not actually rooted after running a2_ics_root.sh in Terminal (computer). I got the "cannot stat 'su': No such file or directory cannot stat 'Superuser.apk': No such file or directory" error message in terminal and also checked root by running a terminal emulator app within the phone and received the no permission message after entering su at the prompt. Once I reconnected the phone to the computer and ran the sh file again I gained temporary root. That's when I noticed su was in two different locations as I mentioned above and you subsequently replied was normal. Of course before I saw your response I had already removed (rm command) the extra su ha! After removing the su file from /xbin I reran the a2_ics_root.sh in terminal (computer) and got root with no error messages and verified it with my phone's terminal app (also got the Superuser root access permission check, which I hadn't got before). No idea why this worked if su was suppose to be in two locations. As I was in the phones terminal emulator app I checked the /xbin folder and did not see it reappear yet it all seems rooted now! Ha! Gosh my brain hurts.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded
492 KB/s (22372 bytes in 0.044s)
3434 KB/s (397229 bytes in 0.112s)
You are rooted!
Click to expand...
Click to collapse
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.

jimbridgman said:
Did you by chance try and use some sort of root keeper before trying to do the OTA, then had these problems after the OTA was completed?
We have seen this before, and the reason you got the stat errors is because the wrong versions of the files were in /system/bin and /system/xbin. Yeah we have found that trying to use any OTA root keepers are BAD on this phone. Motorola is so anal about updates. That is why we mention to do an fxz before doing any OTA, then using the root scripts afterwards.
If you still have any more issues you might think about using the new ICS fxz in the development section and using/redoing the script from there.
P.S. I saw that you said you dragged the script into the terminal, that is a bad way to run it, BTW.... Try and open a terminal and cd into the dir that you unzipped the script in, and then into the ics_root dir and type ./root.sh and see if that works a little better next time, that might be why you only got temp root, because it was not able to find the proper su and superuser.apk to copy over with adb, I use relative paths in the script just for ease.
Click to expand...
Click to collapse
Thanks! I'm sure I did something to cause the troubles but can't recall exactly what it was I did wrong! My brain is getting old. Ha! But to answer your question ... other than my original root (using Motofail) I've hesitated to do anything until after the ICS update. I recently bought the phone 2nd hand to replace my Samsung Captivate so I could experiment with a Lapdock (in my line of work portability and multi-role is a plus). The phone was stock when I got it. Also, I had moved the root.sh file and superuser.apk into my Android/Platform_Tools folder which is in my system path (android rules,etc), so there was some forethought prior to dragging the script into terminal. Next time I'll 'cd it like ya recommend!
Could it be there was an issue with how I did the original GB motofail root?
In any case all seems to be good now.
Thanks again!