Database Users

Rooted Hero Fails adb remount, can't move files from SD

I rooted my hero last night and tried out a few different ROMs but eventually decided to revert to stock and make some manual changes. I used nandroid to restore to just after the root (1.56.651.2). I was able to remove some apps using adb, but the adb remount command fails (permission denied), and I'm unable to push a new bootscreen on to the phone. I also tried a Root File Manager and pre-kitchen as alternatives for the bootscreen, and neither one works. The Root Manager won't paste the files from SD into /system/media/ and pre-kitchen just reboots the phone.
Any suggestions?

Any chance this has something to do with downloading only up to SDK Platform 1.5? I'm at a total loss. I RUU'd my phone, did a clean root at startup using adb shell, and I still have the same problem. The adb remount command won't work, and I can't push anything into the system directory. For what it's worth, when I still had Root Manager installed I was able to toggle RO R/W in any directory with no problem, and I could move files around within the ROM... but I couldn't move anything into it from the SD. I'm new at this, so I have no idea what the problem might be. Anyone else had this problem or have any suggestions?

If anyone else runs into this problem, this solution worked for me:
adb shell
# 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>
Restore modified permissions when done.
Though I'm still not sure why this is necessary in place of adb remount.

I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

dametzg said:
I'm pretty sure the adb remount command will not work on the stock rom. You should be able to do it with just this command instead:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Thanks... didn't realize stock wouldn't accept adb remount. If I use the above line from within shell, that doesn't help me push anything on to the phone though... so I needed to enable global permission and then do the push. Oddly enough I tried the same approach last night using Root Manager, and the transfer from SD still failed, even after I applied 777 to the dir I was trying to modify. The current solution may be kind of tedious, but at least it works.

you really shouldn't do 777 on your filesystem, ANY app can then write to your system, overwrite things, or install malicious code. Just remount manually and you should be able to push anything you want, just remember that w/ the stock rom you also don't get a full busybox either.

I'm not positive, but I would think after you remount, you should be able to "adb push" to /system. I suppose it might be specific to that shell, but I would think not.
You just may have to do it once each time you boot your phone.
Edit - err nevermind... you're having permission errors.... um... change adbd on the phone to run as root? not sure how off the top of my head...

Titanium Backup working

Thanks for all the help from the forum on rooting.
Titanium backup is working great on the DI.
Got Root, Manually installed Superuser, Manually install busybox. Used Titanium to install a new Busybox to the app, everything backs up great.

It's missing from the market for some reason

xvenom89 said:
It's missing from the market for some reason
Click to expand...
Click to collapse
I pulled it from the market just a few hours ago.

xvenom89 said:
It's missing from the market for some reason
Click to expand...
Click to collapse
Did you make your root persistent? You're not going to be able to see root apps if you're not rooted, I don't think.

heavensblade23 said:
Did you make your root persistent? You're not going to be able to see root apps if you're not rooted, I don't think.
Click to expand...
Click to collapse
I could see Titanium on the market before I rooted. I would check the spelling or better yet, use appbrain.com to locate it.

how did you get superuser.apk to install?

See this post for installing superuser.apk
But how did you get busybox installed so Titanium would work?

When you go into Titanium, go to the Menu -> Problems. It will prompt you to download a version of busybox that works with it.

Skapunker said:
See this post for installing superuser.apk
But how did you get busybox installed so Titanium would work?
Click to expand...
Click to collapse
After Superuser.apk and su are setup
while still in recovery root (this does not seem to work if rebooted and using persistance root and remounting /system rw),
cd /system/xbin
/system/bin/cat /sdcard/busybox > busybox
chmod 777 busybox
./busybox --install -s /system/xbin
Reboot, Run Titanium, use Problems? button to download and install a new busybox into the Titanium app
For me, Titanium would not run to a point to use the Problems button until I put a version of busybox on the phone first.

da_knowledge said:
When you go into Titanium, go to the Menu -> Problems. It will prompt you to download a version of busybox that works with it.
Click to expand...
Click to collapse
That was easy, can't believe I didn't bother to try that, thanks
Thanks for the replies

Got it working!! Great, thanks!!

I just got my Incredible rooted and installed Titanium Backup when I run it it says "BusyzBox works but the "su" command does not elevate to root:"whoami" reports "whoami:unknown uid 10108" instead of root?uid 0. I think your "Superuser Whitelist" system app does not work. Please check with your ROM provider." how do I fix this? or is it even a problem? Thanks.

same problem here
I am sure it is just a linux issue, but I am getting it too, but i am not a guru and do not know how to handle it ;-)

Can anyone explain titanium backup a little more??? Do I need to backup every app individually or just let the schedule take care of it? Which schedule option should I pick (in terms of all the options of what function you want titanium back to perform)?
I figured it out.

Just wondering, updating the version of busybox will do nothing to the root access, correct? It'll just allow titanium to work properly and root will remain?

My problem was from a not working superuser.apk. rerooted using the files from the 10min root video and now all is well. To answer the above question in regards to updating busybox, I assume you are refering to letting Titanium Backup update busybox. If so it is ok to update busybox.

Yep, that's what I was wondering. Thanks
Sent from my ADR6300 using Tapatalk

Looking at what this backs up, I am a bit curious if it can actually restore some of it. Many sections it appears to be backing up are not writable even with root access at the moment on the Dinc.
I'm guessing it will require NAND access for this to truely be useful unless I am missing something...

krelvinaz said:
Looking at what this backs up, I am a bit curious if it can actually restore some of it. Many sections it appears to be backing up are not writable even with root access at the moment on the Dinc.
I'm guessing it will require NAND access for this to truely be useful unless I am missing something...
Click to expand...
Click to collapse
That was the main purpose of me getting titanium, i'm not expecting to have the need to restore anything until i flash a custom rom. Having the backup now is awesome because i know i won't lose anything once they figure out how to unlock NAND and flash a recovery and roms

when i'm in recovery mode trying to gain persistant root i get an error.
Code:
# cd /system/bin
cd /system/bin
# cat /sdcard/su > su
cat /sdcard/su > su
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
# rm /system/xbin/su
rm /system/xbin/su
rm: cannot remove '/system/xbin/su': No such file or directory
# ln -s /system/bin/su /system/xbin/su
ln -s /system/bin/su /system/xbin/su
ln: /system/xbin/su: Permission denied
when in Titanium and I hit the "problems ?" button it downloads busybox, but says it failed because it doesn't have root.
any help?

[Q] remove app from rooted g2 (not disable)

Hi,
Now that i've rooted my tmobile G2, i'd like to remove completely some of the apps that i disabled previously (like amazon or photobucket)
I've done some research and found this out
su
mount -o rw,remount /data (or /system)
rm -f /system/app/<apkname>.apk //Replace the blue text, <apkname>, with the name of the APK you want to remove.
pm uninstall <package name> //Replace the blue text, <package name>, with the name of the APK you want to remove.
however, when i run the mount command, i get
Usage: mount [-r] [-w] [-o options] [-t type] device directory
if i try to remove the app directly without running the command
package:/system/app/PbAndroid.apk=com.photobucket.android
i get
rm -f PbAndroid.apk
rm failed for -f, Read-only file system
how do i do this now?
thanks

try
mount -o remount,rw /dev/block/mmcblk0p25 /system

Best app is root explorer from the market... it deleted anything from the phone.
Sent from my HTC Glacier using XDA App

OR HERE'S THE FREE *AND* EASY WAY: download the free version of titanium backup, go to the middle tab, find your app, tap on it, then tap the uninstall button. App uninstalled!
Obviously this requires perma root.
Sent from my T-Mobile G2 running Cyanogenmod.

umm is it supposed to reboot my phone into recovery everytime i remove a stock app?

dietotherhythm said:
umm is it supposed to reboot my phone into recovery everytime i remove a stock app?
Click to expand...
Click to collapse
You're using the force uninstall in titanium backup. This was only necessary for nand locked devices, you can use the normal uninstall function now. Just tap, don't long press -- it'll give you a list of options.

so finally i have a chance to test this.
Thanks all for responding.
I tried the easier way with titanium backup.
I did the mistake of doing the long press and it rebooted.
But after that i just tried the "uninstalled" and it worked like a charm.
Thanks a lot.

Used titanium backup to delete all that crap. =)
Posted on my T-mobile G(spot)2 xD
Please check out my amazing blog- http://elgamerlife.blogspot.com/

i ended buying root explorer ( lcd density mod) my question is...
should i do a backup with titanium and then delete bloatware with root explorer?
I want to use R.E as it did cost me $

-FuRBz- said:
i ended buying root explorer ( lcd density mod) my question is...
should i do a backup with titanium and then delete bloatware with root explorer?
I want to use R.E as it did cost me $
Click to expand...
Click to collapse
If you have any doubt in your mind about whether you want to remove proprietary system app or not then yes, back them up with TB.

Terminal Emulator Won't Work On My Rooted CM7.1 Mytouch!

I go through the process to delete the stock apps:
# SU(superuser permission)
# mount -o rw,remount /system
# rm -f /system/app/Calculator.apk
and it gives me this:
rm: can't remove '/system/app/Calculator.apk' : Directory not empty
PLEASE HELP. This apps are just taking up space and i wanna get rid of them.

Salviikiddd said:
I go through the process to delete the stock apps:
# SU(superuser permission)
# mount -o rw,remount /system
# rm -f /system/app/Calculator.apk
and it gives me this:
rm: can't remove '/system/app/Calculator.apk' : Directory not empty
PLEASE HELP. This apps are just taking up space and i wanna get rid of them.
Click to expand...
Click to collapse
I assume you don't have s-off. i don't either. I use titanium backup. I long press on an app and almost the last option is to force delete. It reboots and takes care of it.

ok thanks.
but whats s-off?

S in S-OFF stands for security, so basically it "locks" the phone and prevents anybody from gaining true root access. If you have HBOOT 1.02, you won't be able to gain S-OFF, if you have HBOOT .5, there's AlphaRev 1.8 utility that will give you S-OFF.
Since you don't have S-OFF, you'll have to use Titanium Backup to force delete those system apps.

[Q] removing stock apps correctly (busybox and terminal emulator)

Alright, so checking up the system folder with root explorer I noticed that there are several applications related to the stock music player.
I can't just simply remove these "apks", right? Pretty certain there'd be leftovers of this app somewhere.
So, I realize, there's no "uninstall" script for the music app, but I was wondering, what is the most correct way to delete music application?
Simple doing this won't cut it, right?
Code:
su
cd system/app
mount -o rw,remount /system
rm -r MusicCommonUtility
rm -rMusicLiveShare2.apk
rm -rMusicPlayerWT.apk
mount -o remount,ro /system

For that kind of things I use Titanium backup app. With that app you can backup ANY app before uninstalling it or just simply uninstalling it. After that reboot the phone and that app is gone.