Database Users

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?

Swype

Would it be possible for someone to upload a titaniumbackup of the stock Swype app from the XXJPF rom? I incidentally removed it to install an update, which won't work :')

Second this, I also need the languages (finnish) from Eclair swype

Bump.
Come on, there has to be someone with the latest i5800 ROM and Titanium Backup.
I really really hate the stock Samsung keypad :')

http://www.multiupload.com/5WTBYMAG68

stubborn_d0nkey said:
http://www.multiupload.com/5WTBYMAG68
Click to expand...
Click to collapse
Thanks, but unfortunately that won't work. I really need the titanium backup files or an APK of that exact version of Swype.

AFAIK Titanium Backup doesn't backup the stock apps except the data. A quick but rude fix that you backup every 3rd party apps, then reflash the firmware.

scipicore said:
Thanks, but unfortunately that won't work. I really need the titanium backup files or an APK of that exact version of Swype.
Click to expand...
Click to collapse
That is the titanium backup file
edit: copied swype.apk from system/app
uploading...
edit2: woah 11.14MB
edit3: finally uploaded (took about 8 minutes) http://www.multiupload.com/T0SCBUCWSD

Thanks again, but it won't install. I guess the only remaining option is to reflash.

Try pushing it to system/app
adb push Swype.apk system/app
adb push Swype.odex system/app (edit: obv you don't have it)
then reboot

Thom47 said:
Try pushing it to system/app
adb push Swype.apk system/app
adb push Swype.odex system/app (edit: obv you don't have it)
then reboot
Click to expand...
Click to collapse
Well, it says "read-only file system".
I've had this before, then i tried to gain superuser access using adb shell su, but then it just gives me "#" and i can't type anything.
I've tried almost anything i could find on the interweb to gain acces to my system files, but all failed.
Things i've tried:
Code:
mount -oremount,rw /dev/block/mtdblock3 /system
mount -oremount,rw /dev/block/st16 /system
adb shell
$ su
su
# mount -o,rw remount /dev/block/st16 /system/
mount -o,rw remount /dev/block/st16 /system/
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#cp Swype.apk system/app
cp Swype.apk system/app
cp: not found
adb shell sysrw
sysrw: not found
adb shell
$ su
su
# mount
# mount -o rw,remount -t yaffs2 /dev/block/st16
# chmod 777 /system
unable to chmod /system: read-only file system
I think i've tried about anything...
I just wish I weren't a total noob in this kind of stuff.

Your phone is rooted right? And you've got busybox installed?
You could try copying it with root explorer or absolute system root (or similiar software) to system/apps
Well I'm also a big noob so this could look very stupid to some advanced user but what can I do

Thom47 said:
Your phone is rooted right? And you've got busybox installed?
You could try copying it with root explorer or absolute system root (or similiar software) to system/apps
Well I'm also a big noob so this could look very stupid to some advanced user but what can I do
Click to expand...
Click to collapse
Yup and yup.
I'll try that just now.
*edit*
Doesn't work either

in root explorer at the top you have the ability to change between r/o (read only) and r/w (read/write). try that

^ That came into my mind, since it whined exactly about that
Also, this might look stupid to some but try instead:
adb push swype.apk /system/app/

Guys...you will not be able to update swype if it comes preinstalled on your phone.
Reason: All the release by swype are beta and if it comes preinstalled, that is an official release and as per swype you cannot install or overwrite a beta over official
The only workaround is if someone can make a firmware after removing swype from it completely. Then only latest swype can be installed.

jaskiratsingh said:
Guys...you will not be able to update swype if it comes preinstalled on your phone.
Reason: All the release by swype are beta and if it comes preinstalled, that is an official release and as per swype you cannot install or overwrite a beta over official
The only workaround is if someone can make a firmware after removing swype from it completely. Then only latest swype can be installed.
Click to expand...
Click to collapse
If you would've read my first post correctly, you'd know I just want the official swype that came with the ROM. Which, in theory, should work.
Thom47 said:
^ That came into my mind, since it whined exactly about that
Also, this might look stupid to some but try instead:
adb push swype.apk /system/app/
Click to expand...
Click to collapse
Okay, i'll try both those things. Thanks again.

scipicore said:
Thanks, but unfortunately that won't work. I really need the titanium backup files or an APK of that exact version of Swype.
Click to expand...
Click to collapse
Can you tell me which files exactly ? I can make it from JPA

uninstall system application

I used this:
su
mount -o rw, remount/system ENTER
rm -r/system/app/maps.apk ENTER
but then it writes that -r failed, no such application found. Can anybody help me

what is it S-OFF and how to do it? I want remove factory aplication out of my HTC Click and terminal.apk writes me read-only system or something like this. Any help? Somebody adviced me that I must change S-ON to S-OFF

I think the -r should take a space before writing the directory location, that's why the directory does not exist. Type rm -r /system/app/maps.apk or just navigate into the directory like cd /system/app/ and then rm -r maps.apk.
Answering your S-OFF question, if you are rooted, and already have a custom rom I can't see the need to do that. Stay away from SPL and Radios updates if you don't know what you are doing. You can brick your phone.
Post your results.

if I do HBoot holding END+VOLUME DOWN button, there is on the top of the creen written S-on

su
mount -o rw,remount /system
rm -f /system/app/<apk name>.apk
pm uninstall <package name>

where is written package name? Thanks

in data/data have the package.You have to look which corresponds to the application you want to uninstall.Be careful what you uninstall, make a backup before.

Type cd /system/app/ and then l or ls to list the content. Select the apk name and paste on the remove command

Just install RootExplorer on your phone... Go to System/app/ and find Maps.apk that u wanna delete. Make sure it is in "Mount R/W" mode(The white button on top). Then press and hold the Maps.apk and click delete. You don't even need adb...

RootExplorer is for kids, not geeks!

jj_95nano said:
Just install RootExplorer on your phone... Go to System/app/ and find Maps.apk that u wanna delete. Make sure it is in "Mount R/W" mode(The white button on top). Then press and hold the Maps.apk and click delete. You don't even need adb...
Click to expand...
Click to collapse
With these explanations you have given only get you delete the application, and leave the data of the application and consumes space,you could also delete with rootexplorer searching for the package in data/data.Uninstall applications from system in the phone is best titanium backup.and here we were not talking about adb ...talk phone terminal.

Titanium backup can uninstall system app

Thank you for ur post, it helped me o lot.

[Q] SU files installed but not giving permission via ADB

I've been trying to fix my kindle fire for a while now. My ultimate problem is that my build.prop is not in my /system/ but I have been trying to push a replacement build.prop to that directory to no avail. It looks like I have superuser installed. Superuser.apk is in system/app/ and there are a few SU directories around my file system.
My problem is that even though I have SU in my file system, I am not getting the correct permissions when accessing the KF through adb. Whenever I type in su it says permission denied. Similarly, whenever I try to change the permissions for /system/ I am denied as well. Whenever I type in su, it says "segementation fault".
It seems to me that there are three possibilities:
1. I somehow have the superuser files in place but the SU program itself is not installed.
2. SU is installed but because I can't fully boot up my KF, I can't give ADB Root access through SU because I can't pull up the "allow access" dialog box.
3. Something stupd like I"m trying the wrong commands.

Maybe your kindle auto updated and broke root? But if you've already updated and re-rooted I'm not sure what the issue would be.
Sent from my Nexus S 4G using XDA App

hmmm...I think a main thing I need to know for sure before I continue is if my phone is even rooted for sure. I have the superuser.apk in system/app. I don't have anything in data/local. I have a SU directory in a couple places. Is there any way for ADB to recognize if a phone is rooted (perhaps if the file system is set up a current way?) without having access to root priveledges itself?

Same here, BurritoRoot, I've tried this on both Linux/Mac, but either way, I can never get su to work so my Kindle can be r/w.

Maybe try
adb shell
$su
If $ changes to # you have root.
When installing su check the file permissions on the directory as well.
Sent from my Kindle Fire using Tapatalk

just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w

b63 said:
just a try:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
what's the answer ?
if the response is not a failure you should have r/w
Click to expand...
Click to collapse
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.

Jessical said:
That worked, thank you!
---------- Post added at 02:37 AM ---------- Previous post was at 02:29 AM ----------
But then I lose them after a reboot.
---------- Post added at 02:44 AM ---------- Previous post was at 02:37 AM ----------
$su doesn't give me a # anymore either.
Click to expand...
Click to collapse
that command only remounts the system partition r/w - not permanent !
but after issuing the comand:
you can copy files, change permission or whatever
you can also run kfu to permantly root with superuser

Fixxxxxxxxxx!
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue

taseedorf said:
http://forum.xda-developers.com/showthread.php?p=21034648#post21034648
That thread I started has the fix for your issue
Click to expand...
Click to collapse
It just stalls at:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
downloading 'boot.img'...
Then nothing.

Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory

taseedorf said:
Did you download the image file? You can just renamed the command and use the twrp from fire utility recovery directory
Click to expand...
Click to collapse
How would I do that? I downloaded twrp-blaze-2.0.0RC0.img
I have used the terminal in the past, even compiled stuff like Chrome OS, but I don't know anything except the stuff that people put in the instructions...
Where is the boot.img itself coming from?

[Q] After JB update, have partial root; only for existing approved apps [SOLVED]

So I seem to be having odd rooting issues, and I can't find anything that really explains it. Apologies that some of this might be obvious...
I rooted without any issues before the Jelly Bean update. Since then, I did the Voodoo Rootkeeper, updated to Jelly Bean, and have since restored root. Everything that had root before seems to still work, however, I can't provide new root access to any applications (it doesn't even ask), SuperUser can't update the SU binary, Root Checker reports me as not rooted, but I can adb shell and do "su" and that works....and the binary is clearly there with the su bits set. And things like ES File Explorer are clearly getting root access....just not anything new. Seems like I have "partial root". Any ideas on what I need to tweak?
thanks!

You did a good job of explaining the situation. I am in the same position.

Here, more information, below. Again, looks like I have su available (/system/sbin/su), but nothing seems to work...superuser is not granting root....strange. Thoughts?
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 22364 2012-11-12 10:52 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your XT907 device by Root Checker Pro version 1.3.1 from joeykrim in the Android Market

I agree good job explaining. But I think a lot of us are in this situation right now. I miss the root! But also love jb (;
Sent from my XT907 using Tapatalk 2

FIXED!
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Nice,
I am going to try using SU and Superuser.apk from that site and rooting JB with those files replaced in motofail2go run.bat Think I'd still have to change permissions that way?

Not sure....I don't think so. Good luck!

RoboCuz said:
I fixed it. Not sure if this was the best way or not, but anyway, I went to this site, and downloaded the latest copy of Superuser.apk and su (extracted from the Superuser-3.1.3-arm-signed.zip , the ARM version of course). I then pushed both those files (su and the apk) into /data/local/tmp. I then when into adb shell, did su, then REMOVED my existing su (actually moved it to su-backup), then copied the su to /system/bin/su and the apk to /system/app/Superuser.apk, chmoded the permisssions correctly (644 for the apk, 06755 for su), and voila! Everything started working again.
Click to expand...
Click to collapse
Any chance you could provide step-by-step details starting from where you pushed the files into data/local/temp?
I'm not a total novice with android but rooting is something I prefer to be very careful with! Sorry to bug you.

I had the same issue. Wiping Cache, Factory Reset, and re-root with JB exploits solved it.

I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!

RoboCuz said:
I'll try to recreate my steps, but since I am doing it from memory, and not re-doing, I might have missed something. I don't think so though.
Go to http://androidsu.com/superuser/ and download Superuser-3.1.3-arm-signed.zip
Open up that file, and copy out the files Superuser.apk and su, put them somewhere on your desktop, say c:\tmp
cd c:\tmp
adb push Superuser.apk /data/local/tmp
adb push su /data/local/tmp
adb shell
su
(you should have the # prompt at this point...if you don't, you don't have "half-root" like I did, and this won't work.)
cd /system/bin
mv su su-backup
cp /data/local/tmp/su .
chmod 06755 su
cd /system/app
cp /data/local/tmp/Superuser.apk .
chmod 644 Superuser.apk
Hopefully that should do it. I don't remember if I needed to reboot after this. Good luck!
Click to expand...
Click to collapse
This fixed the "half-root" on my Razr Maxx HD, thanks!