Database Info

adfree android

now that we have an easy way to push update.zip files I was wondering if there was any way to push the host file that adfree android downloads to the sdcard. I know that it doesn't have write access to the system partition when booted but in recovery we do right?
So it should be as simple as creating an update.zip that overwrites the old host right?
I'm going to try to get this working
EDIT: Here's how to get this working
1. Search for Adfree Android on the market
2. Install and run
3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)
4. Power off the phone and hold Volume Down and power.
5. Use volume down to select recovery
6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select
7. Select "mount /system" and "mount /sdcard" "mount /data"
8. Plug in your usb cord and open a command line on your pc
9. enter adb shell and type the following commands
cp /sdcard/hosts /data/data/hosts
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
10. Reboot your phone and enjoy adfree android.
Thanks to all for help in getting this running.

Just adb push your modified host file to /system/etc/hosts. No need for update.zip

ive already done this doesnt work still have tons of adds

word, I figured it out

junjlo said:
ive already done this doesnt work still have tons of adds
Click to expand...
Click to collapse
what I did was install adfree android, wait for it download and error (the phone will reboot itself) put it into recovery and run the following command from adb shell
cp /sdcard/hosts /system/etc
All my ads are gone

You mind sharing the host file? I'd like to do the same. Now that I can connect as root with 'adb shell' then 'su' after the new Unrevoked^2 root. I'd like to start tweaking with things.

supagene said:
You mind sharing the host file? I'd like to do the same. Now that I can connect as root with 'adb shell' then 'su' after the new Unrevoked^2 root. I'd like to start tweaking with things.
Click to expand...
Click to collapse
just download and install adfree android, it copies the host file to your sdcard.

n0-0ne said:
what I did was install adfree android, wait for it download and error (the phone will reboot itself) put it into recovery and run the following command from adb shell
cp /sdcard/hosts /system/etc
All my ads are gone
Click to expand...
Click to collapse
i may have an older hosts file than but i just used adb push hosts /system/ect/hosts
tryed cp but get a box with busybox info

n0-0ne said:
just download and install adfree android, it copies the host file to your sdcard.
Click to expand...
Click to collapse
I intalled the app and when I hit download and intall I get java/io.FileNotFoundException:/sdcard/hosts
My guess is that it's not downloading.
Tried it on both WiFi and 3G

supagene said:
I intalled the app and when I hit download and intall I get java/io.FileNotFoundException:/sdcard/hosts
My guess is that it's not downloading.
Tried it on both WiFi and 3G
Click to expand...
Click to collapse
ok well here's what was downloaded to my card
https://www.yousendit.com/transfer.php?action=batch_download&batch_id=K0JRUGhYT2JQb0t4dnc9PQ
Thats good for 100 downloads.

Found this. forum.xda-developers.com/showthread.php?t=664532 do you guys know if the zip file with hosts good enough since I can't seem to get the AdFree app to work correctly? Of is there an apk somewhere for this app and I shouldn't have gotten the one in the app store?

host installed still doesnt block ever ad using tikl and fring to test

supagene said:
Found this. forum.xda-developers.com/showthread.php?t=664532 do you guys know if the zip file with hosts good enough since I can't seem to get the AdFree app to work correctly? Of is there an apk somewhere for this app and I shouldn't have gotten the one in the app store?
Click to expand...
Click to collapse
I used the one from the market, it does error but it should copy the hosts file to your SD card (and reboot your phone shortly thereafter).

What now?
Great...
cat /sdcard/hosts > /system/etc/hosts
write: No space left on device

junjlo said:
host installed still doesnt block ever ad using tikl and fring to test
Click to expand...
Click to collapse
I've tested both apps and no ads in either.
The one thing I did different that I didn't post was in recovery under partitions I mounted both system and sdcard. Try that and copy the file over.

Thanks!!
So I downloaded the hosts file, booted in recovery, mounted both /system and /sdcard and then 'adb shell' and 'su' and then 'cd /system/etc' and then 'cat /sdcard/hosts > hosts' and it seemed to have worked.
I go to fring and it displays 'Web page not available', not what I'd like to see but it's better than those retarded ads that I keep clicking on by accident.

can someone post step by step how to get adfree working I installed the one from the market and let it error and reboot then i entered into clockworkmod recovery now what? do i need to mount system and sd how do i enter into adb shell and change host file. thanks in advance for any help.

supagene said:
So I downloaded the hosts file, booted in recovery, mounted both /system and /sdcard and then 'adb shell' and 'su' and then 'cd /system/etc' and then 'cat /sdcard/hosts > hosts' and it seemed to have worked.
I go to fring and it displays 'Web page not available', not what I'd like to see but it's better than those retarded ads that I keep clicking on by accident.
Click to expand...
Click to collapse
Glad it worked out, not sure why your getting page not available, I just get a blank box at the top of my contacts list, other apps show the same as well, a blank box where the ad used to be.

j1000 said:
can someone post step by step how to get adfree working I installed the one from the market and let it error and reboot then i entered into clockworkmod recovery now what? do i need to mount system and sd how do i enter into adb shell and change host file. thanks in advance for any help.
Click to expand...
Click to collapse
Edited OP.

thanks for the quick response everything is good until step 8. I know i sound stupid but i learning fast you say enter adb shell. the way i think you do this is type
1. cd\
2. cd sdk
3. cd tools
4. adb shell
when i do this i get error device not found
can you help from there. thanks

Stock 2.1 rom rooted ROM Manager won't FIX Permissions

I searched and got on IRC and can't get a fix for this. WHen i try to use the Fix permissions option in ROM Manager Premium i get the following error.
"error occurred while attempting to run privelaged commands"
I checked superuser and ROM Manager is in there so i selected "forget" then rebooted and tried "fix permissions" again. I got the promp to allow SU and then the error.
Any idea how i can fix this? Is this a bug or a isolated problem?

Not sure if it is related or not but I had to same problem until I bought the full version off of the market.
Maybe it's part of the extended functionality?

As I noted I have "Rom Manager Premium" I don't think it's related anyway.

Just found the answer to this (as I too was having this problem). See the link below:
http://androidforums.com/899973-post26.html
It has to do with busybox not installed in the correct place.
One more thing: Make sure that busbox is set to "755" so that it can execute.

Thanks
sw99 said:
Just found the answer to this (as I too was having this problem). See the link below:
http://androidforums.com/899973-post26.html
It has to do with busybox not installed in the correct place.
One more thing: Make sure that busbox is set to "755" so that it can execute.
Click to expand...
Click to collapse
Thanks for the link to the fix!

I am unable to get the busybox file to copy from the /data.... directory into the /system/bin/ directory. Any ideas?

jtoole1 said:
I am unable to get the busybox file to copy from the /data.... directory into the /system/bin/ directory. Any ideas?
Click to expand...
Click to collapse
did you mount the system partition prior to trying this?

I'm also having an issue moving the file using root explorer. Any other ideas?

the_grobe said:
I'm also having an issue moving the file using root explorer. Any other ideas?
Click to expand...
Click to collapse
Yeah, same here. My problem is that I've never used Root Explorer before. At the top it says mounted as r/w (in the /system/bin directory) , but it won't copy the file using the Root Explorer program. When I click [Paste] it doesn't give me an error, but when I go and check the directory, the file is not there. I even tried refresh. Any ideas?
UPDATE: I have not solved the problem yet, but I did notice that the /system/bin directory that I am trying to copy to says "0K bytes available," which is probably why it won't copy. So I guess my (no copy) problem is due to my lack of understanding of the file structure of the DI.

UPDATE: I finally got it working. Here is what I did.
1. Boot phone into recovery
2. Push busybox from /sdk/tools folder to sdcard
Code:
adb push busybox /sdcard/busybox
adb shell
3. Installed busybox to /system/xbin
Code:
$ su
#export PATH=$PATH:/system/bin
#cd /system/xbin
# cat /sdcard/busybox > busybox
# chmod 06755 busybox
# busybox --install -s /system/xbin
# rm /sdcard/busybox
# exit
$ exit
4. Booted up phone, and ROM manager fixed permissions as per request.
Hope that helps.

Thanks. I appreciate your feedback. But it looks like I wasted my money again on a useless program like "Root Explorer." I was hoping that I wouldn't have to do all of that command line crap anymore after having rooted.
Does anyone know if there is a file manager out there that will push/pull files via cut/paste rather than using a seperate computer with a command line interface?

I don't think that there is going to be a program like that until we've got full NAND unlock.

the_grobe said:
I don't think that there is going to be a program like that until we've got full NAND unlock.
Click to expand...
Click to collapse
Is someone working on that? I believe the facts are, that the Unrevoked team knows how to do it...but they won't give us the means to do it. Probably because they think we'll shoot ourselves in the foot...and blame them...and they're probably right!

I can not do the cat command it tels me Cant create busybox, read only file system.
Any ideas????????????????

when i was modding widget locker i was using linda file manager free to cut and paste out of the system folder im gonna try it right now to fix this problem ill let u know if it works

[Q] Is there any way to reinstall a system app?

Hi,
I was having trouble with my app YouTubeTablet.apk, it stopped working while I was using it. thinking I was starting to get the hang of this OS, I found the apk in system/app/ and, thinking I could just reinstall it, I deleted it. It wont let me reinstall it. it trys to install, then just gives an error saying "app did not install"
I have been reading and searching all night, I have tried the chmod 644 and a few other things but nothing I have done has seemed to work to get this reinstalled.
Does anyone know a way to get this app back?
thanks,
John

Hello I'm not 100% certain as I'm also pretty new to this scene, but couldn't you just copy the apk back to /system/app ?
Sent from my ADR6300 using XDA App

Use a root explorer and copy the new app to /system/app. Restart and it should work.

I use ES File Explorer, but you have to check mount as read/write in the settings before you copy to system/

Install in /system/app and make sure your permissions are correct. Read: User, Group and Others checked and Write: User checked. Reboot
BTW Youtube crashed last night for everyone. Was a thread about it.

Thanks for the reply's,
I have tried most of this stuff, I tried the rest (changing the permissions) and it still doesn't show up in apps or install
not sure what else to try??
John

Try pushing it via adb then fixing permissions.
Beamed from my TF101 using Tapatalk HD

Xerravon said:
Thanks for the reply's,
I have tried most of this stuff, I tried the rest (changing the permissions) and it still doesn't show up in apps or install
not sure what else to try??
John
Click to expand...
Click to collapse
What ROM are you running? Just flash that ROM again without wiping.

infazzdar said:
Try pushing it via adb then fixing permissions.
Beamed from my TF101 using Tapatalk HD
Click to expand...
Click to collapse
Hi,
I have been trying to do this, I cant seem to do it
after installing sdk I am
1. booting into apx vol up + power while plugged into the pc (plus I tried pluging nto the pc after going into apx mode)
2. adb devices (none show) If I boot normally the devices do show
3. in apx mode, apx shows under devices and printers in my pc
so I tried to do adb remount with the TF booted normally it says not permitted, if I try in apx mode it says no device
I dont know, I am lost, I hope this is all my fault, it has to be, I am reading and reading, nothing I find, or stuff people tell me to try works. I am really starting to wonder about this OS
John

Xerravon said:
Hi,
I have been trying to do this, I cant seem to do it
after installing sdk I am
1. booting into apx vol up + power while plugged into the pc (plus I tried pluging nto the pc after going into apx mode)
2. adb devices (none show) If I boot normally the devices do show
3. in apx mode, apx shows under devices and printers in my pc
so I tried to do adb remount with the TF booted normally it says not permitted, if I try in apx mode it says no device
I dont know, I am lost, I hope this is all my fault, it has to be, I am reading and reading, nothing I find, or stuff people tell me to try works. I am really starting to wonder about this OS
John
Click to expand...
Click to collapse
It's ADB, you do NOT put it in APX mode. Just turn USB Debugging on.
Open the command window and type in ADB devices to see if your device come up.
This thread help with driver's and such for ADB
http://forum.xda-developers.com/showthread.php?t=1071584

baseballfanz said:
What ROM are you running? Just flash that ROM again without wiping.
Click to expand...
Click to collapse
I think I am running the stock rom, rooted. I dont have anyidea how to flash
Is there a way for me to reflash the same stock rom? If you can point me to same directions or info where I can try to learn this?
thanks

baseballfanz said:
It's ADB, you do NOT put it in APX mode. Just turn USB Debugging on.
Open the command window and type in ADB devices to see if your device come up.
This thread help with driver's and such for ADB
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
thank you, I just read somewhere it had to be in apx for adb
Ok the devices do show in the list
I read to type
adb remount
adb push youtubetablet.apk /system/app/
adb push youtubetablet.odex /system/app/
to push these into system/app
when I type adb remount I get the error
"remount failed operation not permitted"
any idea what I am doing wrong
thanks
John

try
Code:
adb shell remount rw

baseballfanz said:
try
Code:
adb shell remount rw
Click to expand...
Click to collapse
It gives me
remount: permission denied
I just read I will quote below
"If it shows a $ sign when u type adb shell then u got no root son"
Ok, when I type adb shell I do get the $ does this mean I am not rooted? I do have su and can get su permissions in root explorer. heck that is what got me in this trouble, I was able to delete the youtubetablet apk from system/app/
adb

Xerravon said:
It gives me
remount: permission denied
I just read I will quote below
"If it shows a $ sign when u type adb shell then u got no root son"
Ok, when I type adb shell I do get the $ does this mean I am not rooted? I do have su and can get su permissions in root explorer. heck that is what got me in this trouble, I was able to delete the youtubetablet apk from system/app/
adb
Click to expand...
Click to collapse
What method did you use to root?

baseballfanz said:
What method did you use to root?
Click to expand...
Click to collapse
I used this one to root back on (8.6.5.9)
ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22 (brk's)
http://forum.xda-developers.com/showthread.php?t=1185104
and I updated with these
[UPDATE] CWM - Stock + Root - 8.6.5.21 US 8.6.5.21-WW 8.6.6.23-WW Updated 12/29/2011 (daoist )
http://forum.xda-developers.com/showthread.php?t=1334673
I was able to do this in terminal emulator
mount -o rw,remount /system
cp sdcard/download/youtubetablet.apk /system/app/
cp sdcard/download/youtubetablet.apk /system/app/
mount -o ro,remount /system
this did seem to work, i mean It did copy the files into the system/app dir however I still dont see the app in my apps and still cannot install
One difference this time, if I copied the files into the system/app dir using root explorer then changed the permissions with root explorer I could, I mean it would allow me to check the box's and save the change
this time In root explorer I cannot keep or save the changes to the permissions, it gives some error about "not being able to change permissions on some file formats such as sdcard etc..." something like that
thanks
John

I was able to push the files over using this method found here (pushing it via adb with my TF in recovery (CWM)
http://androidforums.com/optimus-m-...anyone-who-has-rooted-deleted-lghome-apk.html
it did push the files but still doesnt show up as an app

The may seems simple and don't get mad at me for saying this, but did you reboot after you pushed it to /system /app? It should show up then. At least that is the way I push them and usually when it doesn't work, it is because I forgot that part.

Xerravon said:
[UPDATE] CWM - Stock + Root - 8.6.5.21 US 8.6.5.21-WW 8.6.6.23-WW Updated 12/29/2011 (daoist )
http://forum.xda-developers.com/showthread.php?t=1334673
John
Click to expand...
Click to collapse
Have you tried flashing that ROM again?

baseballfanz said:
Have you tried flashing that ROM again?
Click to expand...
Click to collapse
No I havent, is it ok to just reflash like that? I ask cause it says (in the thread) it wont work unless you have the update before that one installed.
Hi, Yes, I did reboot, actually tried the whole thing a few times/
thanks guys

[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!

[Q] SuperSu Installation fails, cannot root

Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks

Backup important pics, videos, and docs that are located in your phone storage. You will need to Odin flash the VRUCML1 tar then run Saferoot. You can download the 1+ GB file from my link below. Unzip it then use Odin to flash the entire tar or tar.md5. Doing this will format your phone's storage.
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 4

shark_dude said:
Hi,
I was rooted on my Galaxy S3 I535 (Verizon) on 4.1 and took the 4.3 OTA update as is. Now I am unable to use the Saferoot method because when I launch SuperSu and get the popup to update su, it fails every time (using normal or twrp methods). I've wiped the phone but get the same thing each time. I'm running the latest SuperSU 1.9.3 and I'm wondering if it's failing because of old files that are not getting wiped for whatever reason? Can anyone show me how to manually delete any previous su/root files using adb or terminal emulator?
Thanks
Click to expand...
Click to collapse
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.

buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?

shark_dude said:
Confirmed, I get the # prompt after running "/system/xbin/su"
Titanium backup says it's not rooted via the /system/bin/su attempt and every root checker app fails as well although it seems like I'm rooted via command line?
Click to expand...
Click to collapse
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.

buhohitr said:
Type:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.
Click to expand...
Click to collapse
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?

shark_dude said:
Done. It seems to be working as expected now (so far). Now I'm assuming I can run Saferoot again?
Click to expand...
Click to collapse
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.

buhohitr said:
No, once you update SuperSu and reboot, you should be rooted. No need to run saferoot.
Click to expand...
Click to collapse
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?

shark_dude said:
Ah, yes I'm rooted now! Thank you for the assistance as well as to you SlimSnoopOS for the unbrick method, I wasn't aware of that solution yet.
So what exactly was my problem? Did the Saferoot script crap out at some point leaving the necessary files on the phone but not fully set up yet to keep root privileges?
Click to expand...
Click to collapse
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Nice work! Thanks for finding that fix.
Sent from my SCH-I535 using Tapatalk 2

buhohitr said:
The issue was you already have none working superuser as root on the phone (from previous install) then you tried to install supersu through saferoot and your phone is using the old superuser as default instead of the new supersu. So basically the command execute the right root which is supersu, then removed the old superuser, this will allow the supersu to update the binary and now your phone is using the default supersu as root.
Click to expand...
Click to collapse
Gotcha, thanks again! I appreciate the prompt responses :good:

i cnt see $ prom
buhohitr said:
Give this a try while phone connected to PC, run "adb shell" command, you should see $ prompt, then run "/system/xbin/su", you see root's # prompt. Please verify this before we proceed further.
Click to expand...
Click to collapse
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.

DrunkenZombie said:
i also got the same problem whre i cnt root,,its always failed. so now when i run using 'adb shell' i cant see the $ promt. i just see ''install and memo file'' what should i do? sorrry my bad english.
Click to expand...
Click to collapse
Just continue with the following command:
/system/xbin/su hit enter, you should see the # prompt. Then do the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
Now run SuperSU app in the phone, it should update binary ok and prompt you to reboot.