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?

Clockwork-mod Recovery MD5 mismatch! error FIX

For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Another way: for Example TWRP Cache.ext4.win
most recoverys now have a option to turn off MD5 checking
You can copy your backup folder to your computer, use attached app to check the md5 number , edit md5 file and check and verify and change
this thread is old so md5 file may not be named the same. the picture is TWRP custom recovery
example was with cache.ext4.win that has md5 file named cache.ext4.win.md5
another short cut to try
----------------------------------------------------------------------------
@aeneas1 Thanks!!
i did another google search and found a very simple fix, at least it worked for me, on the first try, and i have tested it successfully with some of my other backups that were also getting the mismatch error.
1. using your phone, navigate to your backup folder using a root browser, i use romm tool box root browser.
2. locate and delete the nandroid.md5 file
3. create a new file and name it nandroid.md5
4. boot into recovery, select restore your backup, and watch the magic begin!
---------------------------------------------------------------------------
Update: thanks @Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
DO NOT renamed your backup with spaces Thanks ltredbeard and those who verified
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965

carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
Click to expand...
Click to collapse
Wished I'd have seen this before deleting 4 different backups. Can you tell me what exactly this zip does ?

crz6662 said:
Wished I'd have seen this before deleting 4 different backups. Can you tell me what exactly this zip does ?
Click to expand...
Click to collapse
Never mind, opened it up & read the PDF file. Wanted to also thank you for this.

This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick

Using these methods fixed my error! Thanks.
BTW: I name my backup and it contained a space. I ended up having to rename the backup w/o the space. Ex. From - Backup Froyo To - BackupFroyo

Exca said:
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
After follow this easy procedure on my ASUS TransformerTF101, here's the result in my clockworkmod recovery (v3.0.2.8):
1. Checking MD5 sums is OK
2. Restoring system is OK
3. Restoring data is not OK, there is message: ".android_secure.img not found. Skipping restore /sdcard/.android secure.
4. Restoring cache is OK
5. Backup complete
Then after reboot, all my data on that backup file is not restore as expected. I am afraid my data is gone :-(
Can someone help me?

Araf said:
After follow this easy procedure on my ASUS TransformerTF101, here's the result in my clockworkmod recovery (v3.0.2.8):
1. Checking MD5 sums is OK
2. Restoring system is OK
3. Restoring data is not OK, there is message: ".android_secure.img not found. Skipping restore /sdcard/.android secure.
4. Restoring cache is OK
5. Backup complete
Then after reboot, all my data on that backup file is not restore as expected. I am afraid my data is gone :-(
Can someone help me?
Click to expand...
Click to collapse
I'm guessing by following the zip instructions, you deleted the ".android_secure.img" since it says it's safe to delete if there's a nandroid.md5 file already. But that .md5 file does not match the original. So the backup was likely messed up when trying to fix it with the .zip instructions.
I believe the easier method in post #4 should be tried first on a fresh backup dir.

Whyzor said:
I'm guessing by following the zip instructions, you deleted the ".android_secure.img" since it says it's safe to delete if there's a nandroid.md5 file already. But that .md5 file does not match the original. So the backup was likely messed up when trying to fix it with the .zip instructions.
I believe the easier method in post #4 should be tried first on a fresh backup dir.
Click to expand...
Click to collapse
For future reference to all. What I do all the time is when I make a backup, I hook the tablet up to my pc and back the backup to my PC. This saved me from having to do those steps. I just rewrote the backup on my sdcard and it worked.

Thanks that worked for my mytouch 4G.
Works like a charm, Thanks Again!
carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
Click to expand...
Click to collapse

CWM 3.0 stable

carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
This is what I did to fix mine and get my backup working again after getting MD5 mismatch! error
I was trying to restore my backup after trying another Rom.
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
Click to expand...
Click to collapse
he... good work, thanks very much.
it helps me

Thanks for this, really did the trick! I was so scared I lose my DarkSide Sense backup! thanked!

Can anyone tell me quickly why i can't execute "md5sum"?
when i execute the md5sum command, I get:
"/system/bin/sh: md5sum: not found"

fkng awesome <3! this helped me out!!!

Eschmacher said:
Can anyone tell me quickly why i can't execute "md5sum"?
when i execute the md5sum command, I get:
"/system/bin/sh: md5sum: not found"
Click to expand...
Click to collapse
same problem. any1 got a solution? trying to restore MIUI rom backup.. no luck. restores stock rom backup with no probs.
I am on SGSII.

The MD5 checksum fix *worked* for me! TY!
HTC Evo 4G 2.3.3 / 2.16.0000 / CWM 5.0.2.2

carl1961 said:
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
THANKS SO MUCH!!! I thought that I was going to lose a bunch of stuff after I formated my SD card (thankfully I had a backup on my computer) while watching Netflix. This really saved my life and I'll be bookmarking this!

Yes I met it before.
But now there is not an issue anymore.

thank you
i used your code now hopefully i will have my 4g back with the back up im restoring right now
UPadte:
I restored a backup from when my 4g was working and nothing changed I still can't get 4g to connect!

This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
thank you so very much!!

[Answered] File System read-only after permroot S-OFF

So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.

jdkoren said:
So I just rooted a Glacier out of the box using VISIONary and gfree. Did everything exactly as was supposed to: temprooted, ran gfree, permrooted with "Set system r/w after root" checked, flashed engineering bootloader. Still running stock ROM.
Whenever I try to use adb remount, it fails saying "Operation not permitted." I want to use adb push to write to the file system, but I can't do that without the remount command.
I've tried using terminal emulator to copy a file from the sd card and failed:
Code:
$ su
# cd /sdcard
# cp -f hosts /system/etc
cp: cannot create '/system/etc/hosts':File exists
I've also tried outright deleting a file and failed:
Code:
# cd /system/etc
# rm hosts
rm failed for hosts, Read-only file system
I'm stupefied.
Click to expand...
Click to collapse
To be sure you could download a root explorer and see if you can mount R/W
Sent from my HTC Glacier using XDA Premium App

Is there a free application that does this?
Unfortunately, I won't have access to it for the next few days (someone else's phone, and he's going out of town).

the stock rom doesn't except the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.

option94 said:
the stock rom doesn't accept the remount command.
I believe that astro has the remount ability in it. You might want to consider flashing a custom rom though, even if its one of the stock based ones.
Click to expand...
Click to collapse
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.

jdkoren said:
I see, thanks very much for the explanation. Is that also why the terminal commands didn't work? Does the stock ROM not allow r/w permissions even if you have superuser permission?
Since it's not my phone, I didn't flash a ROM, only ClockworkMod recovery 3.0.0.6. Next time I see him I'll ask whether he wants to do any firmware changes or not.
Click to expand...
Click to collapse
That's correct... I think. all I know is that the stock Rom doesn't usually play well with root lol so yes flash a custom rom
Sent from my HTC Glacier using XDA Premium App

You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may br right, but if not it wont do any damage. just give you a syntax error.

option94 said:
You can make the stock rom rw, but its a pain and I dont really remember the command. Its something like
Code:
mount -o,rw remount /dev/block/mmcblk0p25 /system
That may b right, but if not it wont do any damage. just give you a syntax error.
Click to expand...
Click to collapse
Ah yes, I remember using that once before. I've since forgotten it since I never use it with my own phone. Alrighty, I'll mark this as answered.

[Q] can't preserve ownership... ADB Error

Hey folks,
just a quick question. I tried to backup my /efs folder with ADB since I am planning to mess around a little. I have my phone rooted, latest busybox installed and usb debugging enabled. I succesfully connected the device and granted SU permissions. Then I typed
busybox cp -a /efs /sdcard/
as stated in the guides. However it tells me the following error for all files in the efs directory and doesn't copy one file:
cp: can't preserve ownership of '/sdcard/efs/.android': Operation not permitted
Any ideas on what I am doing wrong?

That's true, you can't preserve that kind of ownership when moving stuff to sd. Just change the -a to -r and you'll be fine. You'll just have to redefine the ownerships if you ever copy the files back, to what they are now.
Sent from my GT-I9000 using Tapatalk

Well thanks, that did the trick! However, someone should then change that in the guides for us Newbies. Besides that I might need to get back to you for redefining the ownerships of the /efs folder once I need to restore it ;-)

[Solved] [Stock .27] ADB only work in recovery mode

Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !

Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Click to expand...
Click to collapse
Go to the play store, download & install Goomanager, install TWRP. CWM seems to have a few issues with teh TF101's.

Hello, i have a CWM flashable TWRP recovery, i even tested it, but wasn't able to work with it, it was very slow and didn't found files i was looking for, i will regive it a try.
Edit : I have the exact same problem when flashing SuperSU from TeamWin recovery, everything act as i don't have SU, i can grant rights to anything i want it will still act as i don't have root, and SuperSU is unable to update it own binary at startup

Magissia said:
Hello, i have a problem with my TF101 (B70 if i'm right), ADB only work when i'm in recovery mode.
I lost root i don't know how and tried to regain it, but every rooting tools failled, i then discovered that commands wasn't working (even ls), but they do work in recovery mode (from /sbin).
When i try to flash a .zip from CWM , it seems that changes suposed to be applied to /system/bin aren't applied (SuperUser/SuperSU never find /system/bin/SU) but /system/bin/app correctly get updated.
I'd prefer to not wipe the device's data and repair it from it's current state if possible.
TF101's current state : Stock .27 guevor kernel 717, CWM non touch recovery
From recovery
ls -l /sbin
http://pastebin.com/tmyZagUk
ls -l /system/bin
http://pastebin.com/6tsPaPF0
ls -l /system/xbin
http://pastebin.com/D3jW5Sy3
If you need more info please tell
Bounty : I'll send Russian chocolat and candies to the one that will find how to fix this !
Click to expand...
Click to collapse
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app

idcrisis said:
Hi, your busybox installation seems corrupt (ie busybox binary is missing). You can reinstall busybox to /system/bin (do make sure that /system is mounted) from inside CWM and everything shall be fine. Your root su also seems to exist and should be fine.
If you can't do it in CWM then you can try and connect to the tablet in normal use mode and then run /system/bin/su and you should be root. Then you can install busybox manually ( you'll need to upload the busybox binary to /data/local/tmp or something) and run:
/system/bin/toolbox chmod 755 /data/local/tmp/busybox ( or if you're in CWM make sure /data is also mounted and then run: /sbin/chmod 755 /data/local/tmp/busybox )
/data/local/tmp/busybox --install /system/bin ( Please verify syntax ).
Good luck!
Sent from my Transformer TF101G using xda app-developers app
Click to expand...
Click to collapse
Hello, i cannot do anything if not under CWM (even ls gives a "not found" if not in CWM)
I tried /system/xbin/su and got a
"sh: /system/etc/mkshrc[8]: id: not found"
Rebooted in CWM and tried to install Busybox
i mounted /system /data and /sdcard
i created the folder /data/local/temp
cp /sdcard/busybox /data/local/temp
applied /sbin/chmod 755 to /data/local/temp/busybox
ran /data/local/temp/busybox --install /system/bin and got a "Invalid cross-device link" error on every commands busybox tried to install
http://pastebin.com/g3DMHbJz
Tried to install it on /system/xbin too, but same error
Note : When i use /system/xbin/su in CWM, it change name to [email protected] from ~# while it doesn't in normal mode
Edit : Titanium backup rework :
In CWM, i copied busybox to /system/bin, and i installed it to /system/bin from /system/bin
cp /data/local/temp/busybox /system/bin
/system/bin/busybox --install /system/bin
I'm now checking if only Titanium backup works or if everything else too
Thanks for your help, i don't know if it's done yet, but i made a progress using your information !
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat

Magissia said:
Edit 2 : Seems everything works, please send me a private message to talk about candies and chocolat
Click to expand...
Click to collapse
Good to see everything works. Give the candy to some children in the neighborhood mate, I'm watching the calories
Cheers!
Sent from my Transformer TF101G using xda app-developers app