Related
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Faud said:
Has anyone gotten Adfree android to work on the my touch slide 3G?
I either get a reboot or error about writing to hosts
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
See this post:
http://forum.xda-developers.com/showthread.php?t=664532
Ignore the installation commands, you need to boot in to recovery and push the hosts file to /system/etc/ on the phone.
Adfree works fine. The reason it doesn't work on slide has nothing to do with the app. The hosts file goes in /system/etc/ and since we don't have r/w access to /system, the app can't do what's its supposed to do. It works great I used it the whole time I had a G1, its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Til then you gotta adb push the file thru recovery...
I dunno if you know this, but adfree temporarily d/l's the hosts file to your sdcard, then deletes it when its done. But since it couldn't replace the file on my slide, it left it on the sdcard! All you gotta do is run the app and wait for it to error out, then go get the file and put it on your pc and adb push to /system/etc...
-BMFC
Sent from my ROOTED myTouch3G Slide
bmfc187 said:
its just cus your phone isn't PROPERLY rooted. Neither is anyone elses til we get that SPL...
Click to expand...
Click to collapse
Actually, its rooted just fine (you can run anything you want as uid 0). The SPL security has nothing to do with root.
It is like saying you don't have the proper key to a door just because after you open it there is a guard standing there not letting you in to the next room.
Just being picky...
i think what he meant is that with all the other phones most of us have had we had an SPL to flash once we had done the original tweaks(or before on some phones) so as of right now i agree that the phone is not rooted properly yet as i don't have full control over the phone whenever i want, i want to be able to mv stuff to system partition from android terminal
just being picky...
could anyone please post the actual commands? im new to adb and wold really appreciate the help adfree is the entire reason i even rooted
among others but it was the number one
adb push hosts /system/etc
-BMFC
Sent from my ROOTED myTouch3G Slide
thank you so very much
Other than removing a few of the stock apps, this is one of the things I'm looking forward to rooting for, I loved it on my G1.
With all of the folks having so much trouble rooting this sucker though, I may wait awhile.
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
and if i type su it asks for a password and if i try to run in root it says that production models wont run in root
but i rooted and have the superuser permissions apk installed and has granted me permission to other things
ParkerOviedo said:
it said this
' failed to copy 'hosts' to '/system/etc': Permission denied '
Click to expand...
Click to collapse
Were you booted in to recovery with /system mounted?
i was able to figure it out
i never tried typing su into the adb shell after i rooted
i got the prompt on my device and accepted it now i have full permissions
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
ParkerOviedo said:
well it accepted the command and it pushed the host file to /system/etc but it still isnt disabling ads |:<
Click to expand...
Click to collapse
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
poetik517 said:
same thing happened to me. but as falken mentioned before, you have to make sure the system is mounted before running the command. so..
boot into recovery.
go to 'partitions'.
select 'mount /system'.
run adb command "adb push hosts /system/etc".
reboot system.
*you might wanna might wanna be sure the comp sees the device in recovery before running the command via "adb devices". i do this before i do any adb'ing.
*be sure the hosts file is in the root of your sdk directory, otherwise your command will vary.
Click to expand...
Click to collapse
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
jnight666 said:
All I get is "failed to copy 'hosts' to '/system/etc': Permission denied"
And yes my Phone is Rooted..
I did everything above. do I have to be in su or something...
Can you not do this on the stock rom. Do I have to flash one of the other roms to be able to push to System...
Click to expand...
Click to collapse
You need to have flashed the engineering rom so you have a root shell in recovery.
Does the Hosts file even block ads?
droctii said:
Does the Hosts file even block ads?
Click to expand...
Click to collapse
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
dumfuq said:
Yup, and it makes the internet soo much faster. Adfree works fine as is if you add the rw overlay
Click to expand...
Click to collapse
BINGO! Thanks!!!
This was created when we didn't have S-OFF yet.
If you have S-OFF or /system overlay script you won't need to go through all the steps simply download adfree android.
I know most of you will be able to do this. But I believe that it might not be as easy for the beginners. So here is a little walk through.
!NEEDs ROOT!
1. Download Adfree Android
2. Wait for it to determine local hosts then click on download and install hosts.
Now it will try to replace /system/etc/hosts but fail (it should reboot the phone but it didn't reboot mine)
4. go to adb and reboot your phone into recovery (with power on+volume down OR the command: "adb reboot recovery")
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
6. mount your system and sdcard you might be able to just use mount and mount everything but I've mounted them serperatly.
Here's how: "adb shell mount /system" next "adb shell mount /sdcard"
7. Now we're going to put it in the etc directory where it should be: "adb shell cp /sdcard/hosts /system/etc"
8. reboot the phone ("adb reboot")
That should remove most of the adds.
I know it's explained on a really low level of knowledge but I wanted to make it accessible for all of you.
Only the needed codes:
Code:
1. adb reboot recovery
2. start recovery-windows
3. adb shell mount /system
4. adb shell mount /sdcard
5. adb shell cp /sdcard/hosts /system/etc
6. adb reboot
has it the option to only block browser ads? when I tried it time ago it couldn't. I don't like to block the app ads
No it removes the adds everywhere. It simply blocks the links to adds. it doesn't actually remove them. they are still being called but they just don't show up.
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
PirateNL said:
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
Click to expand...
Click to collapse
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
A good guide, if a little misplaced, but another option is the /system overlay.
JonasDroid said:
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
Click to expand...
Click to collapse
Yes and yes
where is the most recent hosts file? I'm using a vibrant and it says it worked, but of course, it doesn't. And it doesn't copy the hosts file to my sdcard either ? odd
Hello ,
Finally I got Adfree working
Ok it's not perfect because app continue to reboot the phone after updating the hosts file ,
and we need to copy it manually in recovery mode but it better than nothing
Thank you very much JonasDroid for this little How to .
PS:
For me step 5
JonasDroid said:
Code:
5. adb cp /sdcard/hosts /system/etc
Click to expand...
Click to collapse
was
Code:
adb shell cp /sdcard/hosts /system/etc
Bye.
Yeah indeed its adb shell cp thx for letting me know
Sent from my Legend using XDA App
Can you link me the apk of adfree? I can't download the app from my phone
BTW it's 'ADs" single d
short for advertisment (notice the single d?)
Fixed that English is not my main language
Sent from my Legend using XDA App
JonasDroid said:
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
Click to expand...
Click to collapse
Can't get "start recovery-windows" to work. What is the "right directory"?
Things seems to have worked for me without that portion. Many thanks, I will now change my review in the market for that app from one star to three stars. If they include a note describing this problem upfront I may bump it up further.
It could simply be called start recovery (depending on where you got your rooting tools)(if you've got the from The Unlockr you'll need the -windows)
If you have S-OFF or if you use an /system overlay script these steps aren't needed. (It was created when we didn't have S-OFF for our legends yet.)
Anyone having problems with adfree scripts on Legend since Froyo update? Neve had a problem witha rooted 2.1, but have lots of problems since rooted Froyo 2.2
It seems HTC may have some service which is checking for modifications to symlinks etc.
When I run adfree in my S-off CM7, i get an java.io.EOFException.
Someone else having this?
I had some problems at first, but reinstalling adfree android from market seemed to help. No problem now with CM7 (01/03 from ali ba) and s-off.
adfree no block ads!
Hi,
i install the adfree on my legend with 2.2 with sense.
i did download the host from the app all work ok got a message say it was success install and need to restart the phone.
i did it but still get all the ad like before on all apps.
pls help!
Have you followed the steps? (explained in first post)
Note that you should have a rooted legend (if you don't know what that is then you don't have one)
Hi, I posted a similar question about this under the OneRoot thread, but I don't see a lot of activity there anymore, so I was hoping to get more responses in a separate thread. I've scoured this forum and everywhere else on the Net and I haven't seen anyone experience this same issue. Hopefully someone will understand the problem and have some idea how to rectify it.
So, I have an AT&T Samgsung Captivate with the stock 2.1 Android "Eclair" build on it. I do believe there was an AT&T issued OTA update for it not long ago that put the build number up to UCJH7. I followed the instructions for TGA_Gunnman's One Click Root/UnRoot method documented here. Everything seems to work fine, in terms of booting into the recovery mode and selecting the update file. After the phone reboots, however, I do not see the Superuser Permissions app with ninja icon in my Applications area. If I browse the directory tree in my internal SD card in /system/apps, I do see a SuperUser.apk file. However, clicking on that shows me the message "Install blocked: For security, your phone is set to block installation of applications not sourced in Android Market." So it appears that rooting procedure worked, all the necessary parts were installed, but I don't have permission to execute su. I see that the xbin folder has been created, and it does contain busybox, su and something called ipctool. Also, a link does exist in /system/bin between su and /syste/xbin/su. If I use the Terminal Emulator and type "su", the prompt sits there for 10 seconds and says "permission denied".
Any ideas on what could be preventing me from gaining superuser access here?
Thanks for your help,
Mike
Download and install "SuperUser" from the Android market
OK, so here is another strange thing about this. This doesn't seem like it'd be related to my original su permission problem, but you never know. I decided to try to un-root using the one click method. Now, during the un-root script, I see the adb daemon start, but it fails on the push command writing unroot.zip to update.zip in the /sdcard folder; it says that permission is denied!. Of course, after booting into recovery, applying the update file fails, as it wasn't found in /sdcard. I'm not sure how this could have happened, as the root script was able to push the root.zip to sdcard just fine initially. Now, after I open a shell against my phone using adb, I check the permissions for the sdcard folder, and this yields rwxrwxr-x. I'm not sure, but I believe there should be another w flag set for other on sdcard. How the heck could that have been cleared?
It does look like I can copy the update.zip to sdcard manually through Windows Explorer and just manually boot into recovery using volume up + down + power, so I'm not completely dead in the water. Yet, I'd like to fix the permissions for sdcard, or else I can no longer use the one-click method.
id10terror said:
Download and install "SuperUser" from the Android market
Click to expand...
Click to collapse
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
mskelton said:
Thanks for advice. I will definitely try this, but I did not see this step listed in the oneclick root method? I do see an .apk file for SuperUser in /system/apps, so it seems like the app is already resident. The problem is that it doesn't show up in my main application area on the phone, and I can't run the app; it says it is blocked.
Even if there was a superuser app in the market, wouldn't I need to enable sideloading to get it (which AFAIK need root access)?
Again, thanks for the advice, I appreciate you taking the time to help.
Click to expand...
Click to collapse
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
End points are HIGHLY important, and if you read your post carefully, you have not yet demonstrated that superuser access is broken, only the icon from which you inferred it is broken. Let me know then we can go from there
Sent from my SAMSUNG-SGH-I897 using XDA App
fatttire said:
Mods please move to Q&A
Try adb root before adb push
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks, that was one of the first things I tried last night, but that did not work.
fatttire said:
Its blocked BC u are trying to install it, not run it. Read that error message again.
What happens if you open ROM manager and try to flash clockwork recovery? Or load titanium backup?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah, you're right, now that I see that error message, I guess it is trying to install it. That's odd, because I thought that the oneclick method would have already installed this app during the recovery boot load?
Regarding ROM manager, funny you should ask, that was the entire genesis of why I'm trying to root, so I can backup my phone and install the custom ROMs. After I installed ROM manager and tried to run it was where I initially noticed I must not have root access. When I try to flash clockwork recovery, the app hangs for (oddly enough) around 10 seconds. I never see any prompt for granting root access to clockwork recovery, nor does it boot into the recovery mode.
Okay I have another idea.
If your goal is to simply make a backup to flash a ROM, try this:
1. Download Cog 2.3b6. Other ROMs may have the file I'm looking for but I know it is here. Also you may be able to search and find this file directly but I'm too lazy to find the link for you lol
2. Open the zip file on your computer and extract /sdcard/update.zip
3. Adb push update.zip /sdcard/update.zip
4. Reboot recovery, reinstall packages, you are in clockwork recovery and can back up your ROM.
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to try that, except that it appears there is some type of permission snafu on /sdcard. I believe the permissions on that folder *should* be 777, but it is 775 (other has no write access) for some odd reason, and I have no clue how that happened. Hence, when adb tries to push the update.zip to the internal SD folder, it gets permission denied. As I mentioned, not sure if this is related to not being able to execute su, but it is strange nonetheless.
Guys, please disregard what I mentioned earlier about adb and not being able to push the root/unroot.zip to /sdcard. I'm a moron, and I had left the internal SD card mounted to Windows after connecting the phone via USB. Clearly for adb to push/pull off of /sdcard, the internal SD card must *not* be mounted by Windows. My mistake, sorry for the confusion.
The original theme of the thread is still unanswered though, which is how the one-click root could have worked and not installed the SuperUser app onto my phone.
I will try the recommendation earlier in the thread, to download and install the SuperUser app from Android Market to see if that fixes things.
OK, so I downloaded and installed the SuperUser app from the Market, and for whatever reason, this seems to have addressed the issue. I am now prompted to allow applications root privileges. I'm not sure why this was necessary or how it fixed things, perhaps because it overwrote the version of su that was on my phone with a newer one. In any case, it's working.
Remember, This is still a Temp Root & any Changes made will be Rest back to stock on a Reboot
Its stable & works 100%
I personally have not lost root with this method in over 48 hours.
Zero com.noshufou.android.su crashes.
Before Using!!
HTC Sync Must be Turned OFF
Put the Phone into Charge Mode only ( Not Disk Drive )
USB Debugging Must be Turned on
Restart your phone!
Lastly, if you're getting com.noshufou.android.su force close errors
Uninstall superuser prior to running scripts.
If you Lose Root, all you have to do is open Terminal Emulator & type fixsu
No More Rebooting & running the exploit again for R/W on system to get Root back in place!
Q. Is this permanent?
A. no, it's a temp root method..
Q. Will I lose SU Access at some point while running the OS?
A. You might, but open terminal and type fixsu to get root back.
Q. What about apps that need a reboot to use superuser?
A. Use Fast Reboot form the market for app that need a reboot.
Q. Can I push & remove items to system and will it work?
A. Yes, but all changes are reset on a reboot.
~~~~~~~~~
For Mac/Linux users
Once downloaded, extract vividtemproot.zip to your home/root folder.
(Typically named after your login, has a house icon in Finder's sidebar of places)
Open folder vividtemproot, double-click run_me_mac (or run_me_linux)
and thats is all!
Click here to download for Mac/Linux
(Updated 11/14 - 23:50)
~~~~~~~~~
For Windows Users
Once downloaded, extract where ever you please.
Double click _RUN_ME
and enjoy!
Click here to download for Windows
(Updated 11/14 - 23:50)
Link for Windows is the Mac file...
CharlieMurphyIVXX said:
Link for Windows is the Mac file...
Click to expand...
Click to collapse
Thank you :]
Fixed
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
thecubed said:
Looks interesting, but my method of using a bind mount from /data/local/bin to /system/xbin (apparently I could have used /vendor/bin instead) doesn't loose root after any time unless you reboot.
Bind mounts stay in memory, and aren't like symlinks that get flushed away when the system tries to re-read the filesystem, hence why I suggest using it rather than symlinks.
The bind mount eliminates the need for a 'fixsu' script at all, since there's no links that could potentially dissolve.
With that said, nice work!
Click to expand...
Click to collapse
I haven't lost root in going on ~60 hours, as as a newbie here, you definitely know far more than I do!
As you'll see in the fixsu, I redundantly copy su from /vendor/bin
to /system/xbin/ from which I hardlink (as you'd know is virtually the same as bind mounting in this case) to /system/bin
I added the fixsu, as a last resort, in case the something would dissolve, but unless someone really fudges something up, the fixsu shouldn't be needed
As my programming teacher once told me: the code doesn't need to be pretty as long as it works.
And through that philosophy I've used a lot of redundancies, that may or may not need to be there,
but they'll definitely keep anyone from having any sort of issues using the scripts!
P.S. Thank you :]
Thanks, I'll try this out and report back.
Sent from my HTC PH39100 using xda premium
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
The device rebooted itself -- the "root" is lost
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
rinnycoop121 said:
guys i cannot get this to work for me
i get thefollowing error
Congrats, zergRush worked! Moving on...
Mounting file system as writeable
Installing Busybox
2759 KB/s (777216 bytes in 0.275s)
1518+0 records in
1518+0 records out
777216 bytes transferred in 0.187 secs (4156235 bytes/sec)
Installing Superuser
1808 KB/s (22228 bytes in 0.012s)
rm failed for /system/xbin/su, No such file or directory2852 KB/s (785801 bytes in 0.269s)
All done!
Exiting...
Press any key to continue . . .
Click to expand...
Click to collapse
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
drewdatrip said:
http://pastebin.com/MkGHWadW
appears to have failed for me
Drew
Click to expand...
Click to collapse
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
3f62011 said:
It worked fine, I've got root access -- Thank you!
However, there's this error message at the end of the _RUN_ME.bat script:
"The syntax of the command is incorrect" -- please take a look at the attached image.
Thank you again for the root!
Click to expand...
Click to collapse
I don't own a Windows box, an had to write the Windows bat file
without giving it a test run for errors.
I'm sure I did mess up the syntax, an probably left some command that isn't windows relavent at the end of the script.
No worries, you've got root, and shouldn't loose it.
bjg222 said:
The rm failed for /system/xbin/su, No such file or directory is not actually an error, that's my fault. In my original script, I try to remove that file in case it exists, but if it doesn't exist, it'll just do nothing. So there's no worries there!
Click to expand...
Click to collapse
I tried to pipe all errors out to null, as I took a mash up of your code, my code, and and another guys code, and left a lot of "in case it exists" type of lines in the code, to make sure no one would have any issues.
Apparently I didn't pipe it all to null well enough
The mac/linux version you only see 'starting' and 'finished' haha
rpendrick said:
Tends to be what occurs when the files aren't extracted to the correct place.
You can change the opening line in the script to the direct path to the folder 'resources' and you won't have any issues.
Click to expand...
Click to collapse
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
drewdatrip said:
I thought the same with the read out.
Your recommending to place them at the root of the user correct?
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
rpendrick said:
PM's were sent, I uploaded the wrong zip to megaupload for macs.
All is fixed now.
Click to expand...
Click to collapse
Yes, works much better with something in the folder.
Scrog said:
Yes, works much better with something in the folder.
Click to expand...
Click to collapse
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
I was able to update superuser, but titanium back up doesn't see either SD card.
drewdatrip said:
Yup. Im registering root now. However Superuser is crashing and im able to use the fixsu command
Im looking into it more now
Drew
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Superuser crashes when it is the lastest versions.
Do a google search for superuser.apk 3.0
I thought I included it in the package, but perhaps, once again in a rush
fudged that up too...
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
The Magician Type 0 said:
So far no way to reset the counter has been found. The best you can do is unroot and get a 0/1, but that's practically pointless. I'll let you know if things change.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Has anyone try to format the entire phone, and then fast boot back?
Someone mentioned trying that, but I never heard the results.
Sent from my DROID4 using Tapatalk 2
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
It's almost like Motorola has us all figured out! This and the unrootable Atrix HD... I think we just have to get better. I'm sure there is a root check somewhere in nvram or something
Sent from my Nexus 7 using Tapatalk 2
jsnweitzel said:
Fastbooting back to stock will show qe 0/1, tried it yesterday on my spare D4
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Whoa. I mean, it probably just writes a value somewhere we can't touch (yet?), but still.
repeated shell auto-granted permissions
fade_to_red said:
I noticed this morning that there were repeated messages stating that "shell is requesting/granted superuser permissions". After rebooting my phone, nothing looked different. Then I read an article online on phandroid (unable to post links currently.) that mentioned a "rootchecker". I confirmed what I found after going into recovery "q/e 1/1" on my phone. Sorry about the noob type question here. Has anyone come up with a counter reset for this? Or are we more or less due to the locked bootloader?
Click to expand...
Click to collapse
highlandsun said:
Pretty sure the two things you saw are unrelated. The repeated superuser requests come from /system/bin/dumpstate. It was doing that on my phone too but I just manually killed it and that stopped. For qe you need to remove qe from the boot partition, some of the custom roms here have removed it already.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
aidfarh said:
I've written this in another thread, so I figure I'll just repost this here for everyone's reference.
There's a workaround for this problem. Just remove the execute permission from /system/bin/dumpstate so the error log is not generated. There's a few ways you can do this:
Using ADB. Just type in the computer command prompt with the phone connected via USB. Of course, you need USB debugging enabled and have the android SDK installed on the computer.
Code:
adb shell chmod a-x /system/bin/dumpstate
Using Terminal Emulator on the phone. Just type the following commands:
Code:
$ su
# chmod a-x /system/bin/dumpstate
Using a root enabled file explorer on the phone such as Root Explorer or ES File Explorer. Browse to /system/bin/, find dumpstate, tap-hold to open the properties and remove all the Execute permissions.
Click to expand...
Click to collapse
Morlok8k said:
I too have the repeated shell granted superuser permissions.
Its been so annoying, that I've just kept it temp-unrooted until i need root.
You say that it comes from "/system/bin/dumpstate", how do i go about fixing this?
Note: I rooted my phone with the D4 ICS tool. I had been thinking that the problem was with that - maybe it didn't clean up properly after rooting. Now I know that wasn't it.
EDIT: Found out how:
Click to expand...
Click to collapse
After doing this, here is what i did in a terminal emulator:
Code:
su
mount -o remount,rw /system
chmod 644 /system/bin/dumpstate
i had to do the "644" instead of "a-x" because i kept getting an error message "Bad mode 10|"
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file??
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
No such file???
When I entered "chmod a-x /sys/bin/dumpstate", it returned "Bad mode". So I too tried
"chmod 644 /sys/bin/dumpstate" in the adb shell. It returned "No such file or directory". Has something changed from when the instructions in this thread were posted? Or am I doing something wrong.
It's /system/bin/dumpstate not /sys/bin/dumpstate
removing execute permissions does not do anything.
Should I or shouldn't I?
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
supraket said:
Got my new D4 some 2 months back, unrooted.
Was planning to root it. Now going through this thread, brings me to a question "Should I or shouldn't I?"
Click to expand...
Click to collapse
I say.....
You should:
unlock tether, free apps, better phone, harder to replace if something goes wrong (worth it to me)
You shouldn't:
warranty risk, stock performance, easy replacement
je2854 said:
removing execute permissions does not do anything.
Click to expand...
Click to collapse
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
intellitek said:
I haven't personally tried this, but is this executable required for anything else?
Why not rename it and leave a dummy script in it's place?
Click to expand...
Click to collapse
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
je2854 said:
I think it would still try to read it (the coding) seeing it is coming from Moto themselves... IDK though.
the file is meant for QE warranty purposes
Click to expand...
Click to collapse
Okay, well, let's say, hypothetically-speaking, somebody was willing to experiment with this.
When exactly does this "rootchecker" run? I guess I'd need to rename/replace it before it runs, but after I've rooted. Or somehow before, although I believe that's currently not possible. I'll try and see if the bin is signed.. not sure how to check if it's actually verifying it on exec, though, without rooting.
EDIT: Nevermind, it looks like it's built into the boot and recovery .img files?