Database Develop

Wifi Tether for Root users says I dont have root on my ADP1?

Hi!
Well, I just downloaded the newest version of Wifi Tether for Root users on my ADP1 running HTC's Official 1.5 Firmware. I am pretty sure I would have root but upon launching Wifi Tether it reports that I dont have root access. How is this possible? Is the problem on my end or with the app itself?
Kind Regards!
EDIT: Oh, and I have installed the modified kernel image they posted too.. Still no luck :/

"su"-binary was removed on 1.5-update (official ADP-firmware) ...
You could do the following via adb:
adb remount
adb shell
cd /system/bin
cat sh > su
chmod 4755 su
This way you will get a proper root-environment BUT netfilter-support (kernel-option) is still missing (and this is required for tethering).
You need a new kernel - info is here
!!! ATTENTION - THIS IS ONLY FOR ORIGINAL ADP-FIRMWARES PUBLISHED BY HTC!!!
http://code.google.com/p/android-wifi-tether/wiki/ADP15KernelUpdate
(This will install the su-binary as well.)
Good luck.

Thanks for the reply, however adb remount gave me:
remount failed: Operation Not Permitted :/

Got it working using
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Tethering works perfectly again! Thanks!

[FIXED] Remount failed: operation not permitted

Ok, I'm not a total noob. I've been trying to return to 1.5 as cleanly as possible, but now I'm having an error when trying to remount my phone.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
This is what I did:
Flashed the 1.5 RUU that Flipz has had out for months. No errors
Ran the Avalaunch PRI fix to get rid of the flipz_01 PRI name
updated my profile
updated my PRL (which is now 65000??)
rooted through the normal sequence without error, I can boot to the recovery just fine, but when I adb shell into the phone I end up at $ instead of #. I have to su to get to # and at the c:\windows-sdk-windows\tools\adb remount fails with "remount failed: operation not permitted"
Is it possible that the PRI update has foiled the root exploit? I even restored a nand backup that I know had a working root and I still have the same results. This is too weird.
Anyone else have this issue? I searched the forum but I came up empty.

Try adb remount before adb shell. I'm pretty sure anythig with adb should be ran at just the command prompt.
Someone feel free to correct me if I'm wrong.

right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#

Yeah the wording got me. I was hoping it was as simple as that for you tho. Defiantly Strange. Believe me I've had plenty of those moments where hours would have been saved if someone could have just said "no your just doing it wrong".
Maybe try rerunning the RUU and start from scratch the PRI fix should hold thru the RUU but if it did affect something else running the RUU again may correct it.

I RUU'd about 4 times so far on two different laptops, one with XP and one with Win7, running both versions of the HTC Sync drivers.
Something is definitely different. I'm thinking of doing the PRI fix again to see if that helps. The PRL being 65000 instead of the normal 60664 is another anomaly I'm curious about.

looks as if the 65000 PRL is a new one. I can't confirm (not with Sprint) but there is a thread over in General talking about it.
http://forum.xda-developers.com/showthread.php?t=684873

YEAH! I fixed it....well....actually Flipz fixed it for me. I created a custom ROM in the kitchen and flashed it. Now the remount miraculously works. I'm back to being happy...though I don't know why. Its not like I was using root for anything

Nextelian said:
right, this is at the c:\android-sdk-windows\tools\ prompt. I guess I need to re-word that last bullet point to be more clear.
Code:
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT9C1HF03306 device
C:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
C:\android-sdk-windows\tools>adb shell
$ su
su
#
Click to expand...
Click to collapse
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?

mrsato said:
Can someone splain how to fix this issue w/o flashing? Like maybe from command prompt/shell? Pleeeeease?
Click to expand...
Click to collapse
I found something that help me and you. it properly works!!
I can't spell out instructions for the above mentioned suggestion, since I
don't know which file editor comes on the shipped device, but I have an
alternative solution.From the SDK's tools directory, run adb shell. In the
prompt run the following:
# su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system (Or any subdirectory you want to push to inside system)
# exit
adb push <local file> <device location>
and eventually you should restore the original directory permissions by:
# chmod 755 /system (Or any subdirectory you modified permissions to)
Hope this helps,
Yoav
Click to expand...
Click to collapse

still no Read/Write on /system
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.

mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
I'm not at my computer but I think the command is off... check to make sure its exactly how it should be... maybe the coma after the rw
Sent from my HERO200 using XDA App

mojotexas said:
I tried the above, and I could not mount /system as read/write:
Code:
adb shell
$ su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Permission denied
$ mount: Operation not permitted
My Android 1.6 is rooted, so I feel like I should be able to do this. But any help would be...helpful.
Click to expand...
Click to collapse
Just cd to your tools directory and adb remount

huedawg said:
Just cd to your tools directory and adb remount
Click to expand...
Click to collapse
Is there a solution for this?
I have a rooted HTC Desire.
When I type adb remount I get permission denied.
When I type adb shell and then su , i get permission denied!
This was a stock 2.2 rooted with unrevoked 3.
Any idea?
[edit]
i noticed root permissions pop-up on the phone and allowed so su worked.
[/edit]

Hi,
I have a Desire with stock froyo rooted with unrevocked 3 too and cannot use adb remount:
D:\android-sdk-windows\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
D:\android-sdk-windows\tools>adb shell
$ remount
remount
remount: permission denied
$
Click to expand...
Click to collapse
I have allowed ADB via the Super user app popup.
Any idea?
EDIT: I have set S-OFF using AlphaRev's recovery fastboot and I am now able to remount in rw (well no access denied anymore)
still missing some access as I fail to remove the Google Maps app (want to use Brut maps only)

ghost_boy1412 said:
I found something that help me and you. it properly works!!
Click to expand...
Click to collapse
This worked perfectly! Thank you!

Good freakin lord why the heck did you feel the need to bump this thread thats almost a year old just to say that!!!!!!!! I rarly shout like this, but this crap is starting to drive me crazy!!!!!!!!!!!!
Grrrrrrrrrrrrrrr

same thing for me. i get permission denied

DannyMichel said:
same thing for me. i get permission denied
Click to expand...
Click to collapse
thank you for letting us all know, and in such detail, and with new valuable information no less
/me shakes fists in rage.

Post deleted.

Don't mean to bring up this dead thread but a more simple solution would be this
adb shell
$ su
# busybox mount -o remount,rw /system (or another desired directory)
# chmod 777 (or another desired permission set) /system (or another desired directory)
# exit
$ exit

Help with terminal emulator?

I'm trying to copy a Camera.apk from my sdcard into the /system/app/
so far this is what i've come up with and I get an error saying I don't have the permission to Change the original Camera.apk:
su
cp /sdcard/Camera.apk /system/app/
reboot
Can somebody please help me with this? I just switched from Win7 to Linux and I realized that using the terminal emulator might be the fastest way to do this without installing the sdk.

http://forum.xda-developers.com/showpost.php?p=4900207&postcount=1
Use the mount line from this thread:
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
that should work..

Thank you

thatdudebill said:
Thank you
Click to expand...
Click to collapse
Assuming it worked?
No problem man, welcome to the rooting world.

[GUIDE] How to Remove Pre-Installed Apps for FREE

First, you need to install the drivers:
http://www.samsung.com/us/support/d...R&prd_mdl_name=SPH-D700&prd_ia_sub_class_cd=P
Then you must be rooted:
http://forum.xda-developers.com/showthread.php?t=775110
Next, get the most current SDK:
http://developer.android.com/sdk/index.html
Extract the zip and put it where it's easiest for you to get to on Command Prompt. I put it in my C:\ for extremely easy access.
Now, open up Command Prompt and put in these commands in order
1.
Code:
cd C:\android-sdk-windows\tools
2.
Code:
adb devices
3.
Code:
adb shell
4.
Code:
su
5.
Code:
mount -t rfs -o remount,rw /dev/block/stl9 /system
6.
Code:
cd /system/app
7.
Code:
ls
Now you should see a list of all the pre-installed Apps on your device. To remove these apps you must use this command:​
Code:
rm "app_name.apk" or rm "odex_name.odex"
Here is a list of all the pre-installed apps on the stock Epic ROM and an explaination for most of them:
http://forum.xda-developers.com/showthread.php?t=773142
-------------------------
Here is my suggested list to use:​
Code:
rm amazonmp3.apk[LEFT]rm Asphalt5_DEMO_ANMP_Samsung_D700_Sprint_ML.apk[/LEFT]
rm MediaHub.apk
rm nascar09-prod-release.apk
[LEFT]
rm sfl-prod-release.apk
[LEFT]
rm SN28-1092-sprint-signed.apk
[LEFT]
[LEFT]rm SprintTV.apk
[LEFT]rm SprintTVWidget.apk[/LEFT]
[/LEFT]
[/LEFT]
rm SprintZone.apk
[LEFT]rm MobileAP.apk - Only if you don't pay for the $30 hotspot[/LEFT]
rm MobileAP.odex - Only if you don't pay for the $30 hotspot
[/LEFT]
[/LEFT]

Titanium backup is easier and less time consuming then messing with ADB and is free.

Eh, not really. ADB is much more resourceful and has alot more uses and options if you learn how to use it. This is only one of it's uses. Titanium Backup is just a waste of space IMO. It is very limited on the free version.

Or you can use SDX App Removal if your interested in only removing the preinstalled apps (must be rooted).
Sent from my SPH-D700 using XDA App

At the expense of sounding like a noob, which I guess I am when it comes to Android, I'm getting a real-only error. I rooted with noobnl and Titanium Backup tells me I'm rooted. What might I be doing wrong?

Try using this as the mount command:
mount -t rfs -o remount,rw /dev/block/stl9 /system
Or better yet use one of the GUI options unless you are familiar with linux and save the headache. If all you want to do is remove apps there are far easier methods that are less time consuming. Titanium backup and SDX removal tool are both free.

Sesquipedalian said:
At the expense of sounding like a noob, which I guess I am when it comes to Android, I'm getting a real-only error. I rooted with noobnl and Titanium Backup tells me I'm rooted. What might I be doing wrong?
Click to expand...
Click to collapse
Hmmm see I got that error too when I first did it, but then I did it again and it worked perfect lol...

Mine is Wildfire, I have some issues:
Can not do this:
mount /dev/block/mtdblock4 /system
or
mount -t rfs -o remount,rw /dev/block/stl9 /system
But actual there exists a directory /system/app, in which I can see all the .apk and .odex files. When I tried to delete a file, it says that 'rm failed for File-Name, read-only file system'
What should I do? thanks

xirochanh said:
Mine is Wildfire, I have some issues:
Can not do this:
mount /dev/block/mtdblock4 /system
or
mount -t rfs -o remount,rw /dev/block/stl9 /system
But actual there exists a directory /system/app, in which I can see all the .apk and .odex files. When I tried to delete a file, it says that 'rm failed for File-Name, read-only file system'
What should I do? thanks
Click to expand...
Click to collapse
Well this is for the Samsung Epic...so i have no idea what you have to do

Whosdaman said:
Mine is Wildfire, I have some issues:
Can not do this:
mount /dev/block/mtdblock4 /system
or
mount -t rfs -o remount,rw /dev/block/stl9 /system
But actual there exists a directory /system/app, in which I can see all the .apk and .odex files. When I tried to delete a file, it says that 'rm failed for File-Name, read-only file system'
What should I do? thanks
Click to expand...
Click to collapse
Now I can mount, to over come the read-only problem, however whenever I delete a file, it says that: rm failed for filename.apk, Directory not empty
You guys have any advice? thanks

xirochanh said:
Now I can mount, to over come the read-only problem, however whenever I delete a file, it says that: rm failed for filename.apk, Directory not empty
You guys have any advice? thanks
Click to expand...
Click to collapse
hmmmm idk....thats seems really strange. Maybe its something you cant delete

I tried to reboot in HBOOT/Recovery/ Partition Menu, then mount /system. Then I could remove apps in adb shell successfully. can anyone confirm that doing like this is ok?
My wildfire was rooted with unrevoked3

If it works then it should be fine
Sent from my SPH-D700 using XDA App

This is confirmed to still work with the DI07 update

My noob question is I am using titanium backup to remove the sprint bloatware like media hub and it looks like the program removes it but when I exit titanium it is still on the phone.

Aridon said:
Titanium backup is easier and less time consuming then messing with ADB and is free.
Click to expand...
Click to collapse
Titanium backup is the mark of the noob in my opinion.

thanks, i had been searching around for the adb commands to mount the system r/w so i could remove the bloat.

SDX Stock App Removal is tops in my opinion.
Quick, simple, and allows for back-ups.
And I also don't think Titanium is the "Mark of the noob". It would be more like the "Mark of the ADB is unnecessary for stock application removal"
Also I don't think this should be in development. And if you know ABD commands you should know that.

This thread is okay....but sdx..and root uninstaller are awsome. Thanks for this guide though my friend very useful info for those that want to experiment with adb....
Sent from my Nexus S 4G using XDA Premium App

More options is a good thing. This is also helpful for the noobs who want to get their feet wet with unix/linux shell commands.

[Q] Busybox install, after rooting

Has anyone been able to successfully install Busybox after rooting? I grabbed it from the market but the install FCs.
For the install I picked v1.19.0 installing to /system/xbin.
The requirements page states the following are necessary:
A fully rooted device
A device that is nand unlocked
A device that does NOT have any sort of write protection on the file system
A ROM that supports installing Busybox to partitions that are NOT re-written on every boot
At least 1600KB free in your chosen installation path
Are we missing #2 on req. list even though we can fully root the device?

Yes busybox does work. Im wondering if that app is not remounting /system as writabe.
Try this, from adb or a terminal emulator. Type su . Then mount -o remount,rw /system
then try to run the app again.

eww245 said:
Try this, from adb or a terminal emulator. Type su . Then mount -o remount,rw /system
then try to run the app again.
Click to expand...
Click to collapse
Thanks but this command does not seem to have complete syntax. In Terminal, after elevating to su, I run that and am prompted with "Usage: mount....etc".

g3m1n1 said:
Thanks but this command does not seem to have complete syntax. In Terminal, after elevating to su, I run that and am prompted with "Usage: mount....etc".
Click to expand...
Click to collapse
Well that was the busybox way. lol
mount -o remount,rw /dev/block/system /system

Thanks, I think that did the trick.