Database Info

[GUIDE] getting titaniumbackup (and other root apps) temporarly working

first off, big thanks @teamwin for fre3vo!
this guide is for advanced users only, so I will not explain the adb stuff etc.
you will need to do this stuff FAST, as temp root only works for a short amount of time, but it was enough for me to restore some apps and settings
* install titaniumbackup & busybox installer from market (do not start them)
* reboot the phone and DO NOT start any application
* do the fre3vo stuff:
Code:
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell /data/local/tmp/fre3vo
* install superuser, su and set permissions
Code:
adb shell mount -oremount /dev/block/mmcblk0p22 /system
adb install Superuser.apk
adb push su /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell ln -s /system/xbin/su /system/bin/su
* start busybox installer and install busybox
* start titaniumbackup and do your stuff
again, this has to be done fault free and FAST, like within 2-3 minutes
attached are su & superuser used

Nothing attached

Thank you for this tuto, i try other from 3D Evo and don't work for me, now im not at home, but will try this one once at home.
Thank a lot!!!
Sent from my HTC Sensation Z710e using Tapatalk

<delete please>

Great man!! Thanks
I am guessing that all these files fre3vo, SU, Su.apk should be in the platform-tools folder? where adb is?

We can delete some apks,right?

jerrylzy said:
We can delete some apks,right?
Click to expand...
Click to collapse
No, but you can disable them

prateekgujral said:
I am guessing that all these files fre3vo, SU, Su.apk should be in the platform-tools folder? where adb is?
Click to expand...
Click to collapse
the 3 files have to be in your current working directory (which should not be the platform dir), and adb should be in your ${PATH}
but yes, you can also put the files where adb is located

blubbers said:
the 3 files have to be in your current working directory (which should not be the platform dir), and adb should be in your ${PATH}
but yes, you can also put the files where adb is located
Click to expand...
Click to collapse
I will have to put them where the adb is located as I havent changed the environment variables for accessing adb from anywhere.. i think it should be ok.. as I have been flashing radios and other apps like that only!! (previous Androids!)
I would usually just copy the file on to the platrform directory.. ADBed the thing and deleted the file oonce the job is done!

prateekgujral said:
I will put them where the adb is located as I havent changed the environment variables for accessing adb from anywhere.. i think it should be ok.. as I have been flashing radios and other apps like that only!! (previous Androids!)
I would usually just copy the file on to the platrform directory.. ADBed the thing and deleted the file oonce the job is done!
Click to expand...
Click to collapse
of course it will work, but it's not the proprer way to do things

blubbers said:
of course it will work, but it's not the proprer way to do things
Click to expand...
Click to collapse
Oh well!! as long as it works!!!
Anyway... thanks man!!

Found this!!
Excellent video tut
http://www.youtube.com/watch?v=1t9AXZWcFQU

prateekgujral said:
Found this!!
Excellent video tut
http://www.youtube.com/watch?v=1t9AXZWcFQU
Click to expand...
Click to collapse
might want to put this in the fre3vo thread, as this is thread goes beyond that

Followed your procedure above but just before I installed busybox - I pushed a new hosts file over which was taken from an adblocker program.
adb push hosts /etc/hosts
Edit: - hosts gets overwritten after few minutes
Pity - thought it might have been useful

Awesome worked great!

EddyOS said:
No, but you can disable them
Click to expand...
Click to collapse
I have uninstalled anything related to "stocks"
The widget , the app and one other have been uninstalled and are no longer present on my phone
Sent from my Nokia 3310 using Tapatalk, 2 carrier pigeons on crack and a cab

j2kquest said:
I have uninstalled anything related to "stocks"
The widget , the app and one other have been uninstalled and are no longer present on my phone
Sent from my Nokia 3310 using Tapatalk, 2 carrier pigeons on crack and a cab
Click to expand...
Click to collapse
Reboot and they'll probably come back

I get this
failed to copy 'su' to '/system/xbin/su': Read-only file system
Click to expand...
Click to collapse

I get all the way to Titanium backup saying its restoring an app and it hangs there. It gets superuser and everything it just doesnt seem to want to actually restore anything.

I get this problem
C:\android\tools>adb shell mount -oremount /dev/block/mmcblk0p22 /system
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\android\tools>adb shell mount -oremount /dev/block/mmcblk0p22 /system
adb server is out of date. killing...
* daemon started successfully *
mount: Operation not permitted
C:\android\tools>adb shell mount -oremount /dev/block/mmcblk0p22/system
adb server is out of date. killing...
* daemon started successfully *
Usage: mount [-r] [-w] [-o options] [-t type] device directory
C:\android\tools>adb install Superuser.apk
adb server is out of date. killing...
* daemon started successfully *
2180 KB/s (196521 bytes in 0.088s)
adb server is out of date. killing...
* daemon started successfully *
pkg: /data/local/tmp/Superuser.apk
Success
adb server is out of date. killing...
* daemon started successfully *
C:\android\tools>adb push su /system/xbin/su
adb server is out of date. killing...
* daemon started successfully *
failed to copy 'su' to '/system/xbin/su': Read-only file system
Click to expand...
Click to collapse

HTC OneX AT&T Manual root process (No Desktop)

I wanted to share my experience with following this thread
http://forum.xda-developers.com/showthread.php?t=1709296
i unfortunatly do not meet the 10 post limit
Following the process i got stuck here
Code:
Now it's time to reboot
adb reboot
After phones reboots
adb remount <-----------------HERE---------------------------
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm /data/local.prop
adb reboot
ADB told me that i dod not have the correct permissions to push the SU file to the phone. The phone would boot, but would not load the widgets or bottom menu. Attempting to open settings would prompt Android.Core to crash.
Scary stuff
The problem was with the ADB Reboot command. It normally reboots the phone properly, but when i ran ADB Reboot, the phone cut power (off) instead of rebooting. Something did not go as intended and i needed to power on my phone, and reboot it manually without the USB cable connected (lagged too much).
After that, the ADB Remount was successful and the rest of the process ran smoothly. I am happily rooted
Thank you to all
~Can someone copy this into the actual thread? I want to help spread rootsauce.

[Root] Please test new rooting idea

Hi all,
well i made a small script to root Xperia devices, as it turns out more devices are affected to this.
Paul O'Brien over at Modaco tested it on his Nexus 7 [UK] and it worked, well some users in my thread over @ Xperia S section report it not working and some report it working.
I am opening this thread to get the idea why it is working for some users and why not for others.
So, as i don't have this device i cannot test it myself, so if you are a interested user or maybe a dev feel free to test it. Maybe you even get the idea why it is working on some and not on others. (BTW, are there any diffs between UK and other devices? How many firmwares are out for the device? Can i download somewhere firmware dumps?)
Paul's test: http://www.modaco.com/page/news/_/android/a-new-and-effective-root-method-for-ics-jb-r715
Best Regards

I will try it now with my UK device.
The device is STOCK, Bootloader locked and updated to the latest JB Build via OTA.
Will report back after my try.
EDIT:
It doesn't work for me:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= (13.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1252 KB/s (1085140 bytes in 0.846s)
1039 KB/s (22364 bytes in 0.021s)
1305 KB/s (843503 bytes in 0.631s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
With Version 2 I get the following output:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= version 2 (14.09.2012) =
======================================================================
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice: 3
Normal Mode enabled!
Please connect device with ADB-Debugging enabled now....
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
1290 KB/s (1085140 bytes in 0.821s)
992 KB/s (22364 bytes in 0.022s)
1285 KB/s (843503 bytes in 0.641s)
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
rm failed for /data/data/com.android.settings/a, Permission denied
Please look at your device and click RESTORE (once again)!
If all is successful i will tell you, if not this shell will run forever.
Successful, going to reboot your device!
Waiting for device to show up again....
mount: permission denied (are you root?)
remount failed: Operation not permitted
/system/xbin/su: cannot open for write: Read-only file system
Unable to chmod /system/xbin/su: No such file or directory
/system/app/Superuser.apk: cannot open for write: Read-only file system
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Drücken Sie eine beliebige Taste . . .
Click to expand...
Click to collapse
Ad Version 2: It doesn't ask me to restore 2 times. Only the first time it asks me and then the Nexus 7 reboots.

Ok thanks for this test.
Can you tell me if there is a /data/local.prop already present in you firmware version? If yes we need to alter the script a little, hopefully it can work then.
I am not sure which firmware version Paul tested, but i have a few feedbacks telling it works, so i suggest it is a firmware version "problem".
Regards

Bin4ry said:
Ok thanks for this test.
Can you tell me if there is a /data/local.prop already present in you firmware version? If yes we need to alter the script a little, hopefully it can work then.
I am not sure which firmware version Paul tested, but i have a few feedbacks telling it works, so i suggest it is a firmware version "problem".
Regards
Click to expand...
Click to collapse
Thanks for your answer.
Since I don't have root I can't answer you this question because /data is inaccessible.
The rooting success of Paul is the same as with the HTC One X. He could achieve root trough such a script with his One X, all the others couldn't.
Sent from my Nexus 7 using xda premium

Strange thing.
Can you try something for me ?
Do this manually:
adb restore stuff/fakebackup.ab
Do not click restore YET!
next command:
adb shell "while ! ln -s /data /data/data/com.android.settings/a/file99; do :; done" > NUL
this command will automatically stop when it "worked". Once this command runs please click restore on device!
Now please give me a:
adb shell "ls -ld /data"
I want to know if it changes the permissions of data folder, if all is fine it should be permissions of 777. Maybe then you can check for local.prop and if present rename or remove it
Regards

Bin4ry said:
Strange thing.
Can you try something for me ?
Do this manually:
adb restore stuff/fakebackup.ab
Do not click restore YET!
next command:
adb shell "while ! ln -s /data /data/data/com.android.settings/a/file99; do :; done" > NUL
this command will automatically stop when it "worked". Once this command runs please click restore on device!
Now please give me a:
adb shell "ls -ld /data"
I want to know if it changes the permissions of data folder, if all is fine it should be permissions of 777. Maybe then you can check for local.prop and if present rename or remove it
Regards
Click to expand...
Click to collapse
My output:
C:\Users\user\Desktop\stuff>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
xxxxxxxxxxx (censored) device
C:\Users\user\Desktop\stuff>adb restore fakebackup.ab
C:\Users\user\Desktop\stuff>adb shell "while ! ln -s /data /data/data/com.and
roid.settings/a/file99; do :; done" > NUL
C:\Users\user\Desktop\stuff>adb shell "ls -ld /data"
drwxrwx--x system system 2012-09-15 20:55 data
C:\Users\user\Desktop\stuff>
Click to expand...
Click to collapse
It seems it didn't get chmod 777

Ok thanks for the test. Too bad, it does not change the permissions, maybe there is something preventing it. For now i have no idea, but any dev can freely adapt the intial idea of the script. If someone owns this device i think it the basic idea maybe useful. As for now it seems all devices are initially vulnerable to the "problem", only a way to use it have to be found.
Regards

FYI here also, doesn't work on my fully stock 3568A-ME370T JRO03D Nexus 7

Bin4ry said:
adb shell "while ! ln -s /data /data/data/com.android.settings/a/file99; do :; done" > NUL
Click to expand...
Click to collapse
I think this, and things similar to this, are your problem as you already need root to access those folders.
Without root any running app/process is only allowed to access it's own subfolder in /data/data, nothing else.

This kind of works for me, clockwork mod says I'm rooted but titanium backup says I'm not.
I can't install clockwork mod recovery from the app. Something about assigning permissions.
My boot loader is unlocked. Dunno if that helps.
Sent from my Nexus 7 using xda app-developers app

Have you got Superuser or SuperSU installed?
Sent from my Nexus 7 using my toiletpaper

Yes SuperUser only because the script bin4ry posted contains the superuser.apk and installs it.

HellcatDroid said:
I think this, and things similar to this, are your problem as you already need root to access those folders.
Without root any running app/process is only allowed to access it's own subfolder in /data/data, nothing else.
Click to expand...
Click to collapse
This is not true, it is exactly the trick my scipt uses, in the moment you press restore in the Android Restore Service you will gain access to the partition
@Spazz Monk3y: I added v9 maybe it works now properly, in some old versions i had a nasty bug for giving permissions to su binary. Introduced because i wanted to make a singleline command and forgot atleast 1 command inside my line :crying:
Regards

Code:
mount: permission denied (are you root?)
With v9 and German Nexus 7

Nex 7 is really crazy, you some working some dont. i have no idea -.-

Welcome bin4ry! I remember you from my x10 days! Glad to see you doing well.
Sent from my Nexus 7 using XDA Premium HD app

I have bricked my phone I think please help.

Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me

sunny342 said:
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
Click to expand...
Click to collapse
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone

sunny342 said:
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
Click to expand...
Click to collapse
When you try and mount your phone, since you factory reset through Hboot, you'll need to reformat your SD card because you corrupted it. Just some information for you.

Factory reset in bootloader, plug it in to comp, bring up "my computer" on your computer. Right click removable storage and choose "format"
Sent from my One X using Tapatalk 2

[Q] S-off issues * SOLVED *

Ok......... First specs
Windows 8.1 update 1
adb installed correctly
cmd in the correct folder
firewater in the correct folder
Phone will not stay online through adb reboot, I unplug the usb and then reconnect and eventually it will show up again. Then I follow the steps through to fire water says first bottle is open , chugging, opening bottle 2, chugging. Then the phone just shuts off completely and displays the charging icon... I am at a total loss for what the hell is going on, any thoughts?
I entered the command in the following way and it worked:
adb reboot
waited for the device to boot all the way up then : adb push firewater /data/local/tmp
adb shell
chmod 755 /data/local/tmp/firewater
su
/data/local/tmp/firewater
And it worked that way.

Did you grant the RSA prompt? And grant firewater root privileges?
Sent from my HTC6525LVW