Database Develop

tatoo M7 root completed but applications say it is not rooted

I have completed my Tattoo M7 root however applications say it is not rooted.
basically if i do ADB SHELL and then SU i get the root console but can not write to /system folder via adb push since i get permisison denied which means i always have to adb shell and su.
I believe this is somehow creating problems also to applications (i am testing Titanium Backup) which require root permissions and say i am not.
Anyone can help understanding why i can su only in console or terminal emultor but cannot use apps requiring root permissions.

Dude, you have to remount EVERY TIME /system and /data if you reboot, otherwise it says permission denied because system is read only...
Get RootExplorer, there is a little button which lets you remount partitions with one tap...

pardol said:
I have completed my Tattoo M7 root however applications say it is not rooted.
basically if i do ADB SHELL and then SU i get the root console but can not write to /system folder via adb push since i get permisison denied which means i always have to adb shell and su.
I believe this is somehow creating problems also to applications (i am testing Titanium Backup) which require root permissions and say i am not.
Anyone can help understanding why i can su only in console or terminal emultor but cannot use apps requiring root permissions.
Click to expand...
Click to collapse
hi
as ur question in the related thread
see link : http://forum.xda-developers.com/showthread.php?t=637927
CLOSED

New member, have a few questions.

Ive had the hero for a while now and now feel its time to root it since there doesnt look like there will be anymore major updates.
I had first tried to root it through the unrevoked method and couldnt get passed code #8: su
It just kept saying that su wasnt a valid code or something like that. so after a couple other tries i scrapped it. eventually found the 1-click way and did that on my phone. But nothing seems to have changed. The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
If you guy could give me a little insight on what i need to do or point me in the right direction i would appreciate it.
there is just so much info on this site that it makes it a littl overwhelming for somebody just getting into the game.

best way to test if you have root is open terminal emulator and type su if you get a # in the prompt you have root.
Or from adb try
adb remount
adb shell and if you have a # instead of a $ in the prompt you have root.
If that works then to remove the crappy sprint apps open a cmd and type
adb remount
adb shell
cd system/apps
ls
then look through and find the ones you dont want and type this
rm my_bloat_app.apk (replace my_bloat_app with the app you don't want)
and hit y to comfirm and its gone.

madeSICC said:
...The frst thing i wanted to do was uninstall the useless sprint apps such as sprint tv etc... but was unsuccessful in finding a way.
Click to expand...
Click to collapse
Titanium Backup can do it. Download it and learn how to use it. It will become your friend.
If it can't do it, you still aren't rooted!

Rooting

Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..

cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
Do you have the "superuser" app on your phone?

cryo.burned said:
Alright, so I've used the SuperOneClick application to root my phone, which tells me was done successfully, however, I don't seem to be able to access files in the system folder through adb.
Is there some way I can positively confirm whether my phone is or isn't actually rooted? Like I said I was using adb to push a file into the system folder, and was given a permission denied message. At this time the only thing I'm attempting to do to the phone is this:
/showthread.php?t=820749&page=3
It seems pretty basic and it's my first android phone, so I'm starting off small here..
Using the leaked 2.2 FW, other than the being rooted (attempted), the phone is stock 2.2..
Click to expand...
Click to collapse
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.

TheRomero09 said:
Do you have the "superuser" app on your phone?
Click to expand...
Click to collapse
Yes, I have it on my phone
miztaken1312 said:
If you type:
adb shell
su (after hitting enter, you should get a popup on your phone asking for superuser permission, click allow)
If you see this:
C:\Users\*yournamehere*>adb shell
$ su
su
#
Then you have root permissions.
Click to expand...
Click to collapse
I have the app on my phone, but when I try this, I do not get a prompt for super user permissions, and the CL shell returns permission denied
EDIT: I was going to look at the superuser app to see what was in it to give you more info, but it the "app" that I assume is actually my computer had denied permissions. After changing it back to allow, the shell returns
Code:
su
#

Temp root for apps required root access (for s-on IS)

Psneuter exploit is working on IS, but because /system is locked on s-on phones, we can't copy su and superuser.apk into /system, apps required root access can't work.
The following procedure uses psenuter exploit to gain adb shell root, and then copy su (without privilege control ) and busybox into /sbin (which is on rootfs and in the global PATH list) to gain root access for apps.
The procedure:
1. Unzip the attached .zip into a directory (like c:\adb)
2. Open a command prompt and cd to the directory where you extracted the .zip (like cd \adb)
3. run pushroot.bat (simply type pushroot)
4. adb shell /data/local/tmp/getroot
5. adb shell
6. you are now in # prompt. Type /data/local/tmp/pushroot
You have to redo steps 4,5,6 once you reboot your phone.
The procedure will have all apps gaining root access.
!!USE ON YOUR OWN RISK!!
Known working programs: Root explorer, Titanium backup, gscript lite, trasproxy 2.04, ...
Some apps check existence of su in /system/xbin , and reject to proceed if the su binary is not exist (like transproxy 3.08). For this kind of apps, this procedure won't help.

Nice but old news mate...
Sent from my HTC Incredible S using XDA Premium App

Good job...thanks

Thanks for writing this up, might quell the thirst for S-OFF a little longer

/system/ is writeable btw, if you remount it, but after reboot everything u done will be changed to the way it were before.
so a temp root in xbin is possible also, only it will be gone afterwards (atleast i never tried this, but should work also...)

Yes. /system could be remount in rw with root. However, the files you wrote will be gone after you remount ro, and then you won't be able to copy the same filename into the same location again before next reboot ( I don't know why, actually!!). This is why I put su in sbin instead of /system/xbin.

thanks to your files 非常感谢你的工作。

Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?

faf said:
Does anyone know whether steps 4, 5 and 6 can be run from the device itself?
Can I put these commands into some sort of script and run it everytime I need temp root or would I need to do this from a computer every time?
Click to expand...
Click to collapse
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk

pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....

itandy said:
I believe you can do it from a terminal emulator but haven't got the chance to try it myself though.
Sent from my HTC Incredible S using Tapatalk
Click to expand...
Click to collapse
Definitely, this is the way to go.
Unfortunately, the root exploit I know could run on device itself, including
rageagainstthecage (ratc) and local root exploit (hotplug) both failed on IS.
The solution will be nearly perfect if we can get temp root on IS without a computer link.
Any input will be welcome.

sky1212 said:
pushroot error
c:/adb>adb shell ln /data/local/tem/busybox /data/local/tmp/cp
Link failed File exists
and
c:/adb>adb shell /data/local/tmp/getroot
mmap<> failed. operation not permitted
Why??THX....
Click to expand...
Click to collapse
Please then type adb shell.
If you see # but not $, do
cd /data/local/tmp
rm ./cp
ln busybox cp
./pushroot
Then you finished the install.
If you see $, please do all over again.

You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work

l0st.prophet said:
You can also add ShootMe (screen capture app) and SetCPU to the list of working apps. SetCPU will only allow you underclock for now due to the kernel, but it is a nice touch if you are worried about battery life. Adfree doesn't appear to work
Click to expand...
Click to collapse
Adfree is working for me. Are you getting some type of error message?
MetaMorph, screenshot and MyBackup Root are also working.
I had to mount system, then push su to /system/xbin. Then install BusyBox Installer from Market.

No erro, still got the ads. I've tried rebooting & rerooting, still no luck

l0st.prophet said:
No erro, still got the ads. I've tried rebooting & rerooting, still no luck
Click to expand...
Click to collapse
What site/app are you going to so I can see if I get the ads.

the anti-ads actually tries to modify the current host file... which is not allowed in your state as far as i know
what you can do is replace it by pushin it to the right spot
but after reboot gone,but sure u know

Adfee is working for me, you can also add Droidwall.

@eddycyf, did you test adfree with apps? Since it aint working for prophet...
Sent from my HTC Incredible S using XDA Premium App

Mhm AdFree isnt working for me. The App states that everything is okay, and that my hosts file is up to date, but I see ads everywhere.
But I am kinda happy now, because i can use Titanium Backup

One click root after update: "We have root, but couldn't push busybox. Not sure why!"

One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...

there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date

I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.

http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website

Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...

Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App

OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!