Database Info

How to root the Droid 2

All credit for the binary goes to Sebastian Krahmer at http://c-skills.blogspot.com/. Please see fit to donate via Paypal to [email protected]
If you want a simpler 'one-click' process, go to this thread: Easier 1-2-3 Droid 2 Root for Windows / Linux / Mac
***NOTE: Proceed at your own risk. I and the providers of this code are not responsible for anything you do to your phone!***
Setup:
- Install adb (here) and Motorola drivers for windows(32-bit or 64-bit)
- Download attached archive
- Extract to a directory, I used c:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open command prompt
- cd c:/wherever-your-sdk-tools-folder-is
- adb devices (to verify the connection)
- cd c:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- let the process run until it 'kicks' you out (may take a minute or two) to c:/Droid2Root
- cd c:/wherever-your-sdk-tools-folder-is
- adb kill-server
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt, if not return to ./rage step above)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
- exit
I'm sure there are certain steps that could be streamlined or eliminated, so please feel free to make a suggestion and I'll edit the post.
Additional thanks to @rainabba and AllDroid.org for their excellent Droid X rooting tutorial, which assisted me greatly in this process.

waiting for a recovery, glad to see its rooted

Android n00b here, I can remove the Verizon crapware with this right? And tether?

thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
yes and yes

thelolotov said:
Android n00b here, I can remove the Verizon crapware with this right? And tether?
Click to expand...
Click to collapse
I wouldn't remove anything yet since we don't have a sbf file to recover from partial bricks. However, tethering and any other apps that require root can be used now.

I'm new to doing this all the adb way.
When you say extract to a directory what do you mean to extract. After it downloads the achive files its done.....
i understand the rest of the commands but im lost there

Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?

Right click the downloaded archive and "extract files". You need to do this so adb can push them to the phone.

thelolotov said:
Hmm, alright, that's still worth it, will I lose my data/have to hard reset to root?
Click to expand...
Click to collapse
Nope, it just gives you access. Nothing deleted.

I'm retarded i didnt realize it was attached to the post, i thought it was what adb downloaded when i first opened it cause it called them archives.

cannot access
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?

Anybody actually try this?

Hello,
I am following your directions and when I get to the "adb push Superuser.apk" step I receive the following error:
"failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system"
I get this same error for the other adb push steps that follow.
Edit: To verify, I get a # shell.
Edit 2: I tried pushing the Superuser.apk to /data/local/tmp then cp to /system/app/, this also popped up a read-only file system error.

I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver

GSletta said:
I got as far as pushing super user su and busy box onto my phone but it says that system in read only.. how do i fix this?
Click to expand...
Click to collapse
Did you verify you have the # prompt three steps before that?

Yeah i get the # but it wont let me push superuser su and busybox

GSletta said:
Yeah i get the # but it wont let me push superuser su and busybox
Click to expand...
Click to collapse
Weird.. I didn't need to mount the system manually, but let me if there's a step I left out.

and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg

djh816 said:
and some more screens (feel free to use in first post):
http://i.imgur.com/nPllt.jpg
http://i.imgur.com/COTEA.jpg
http://i.imgur.com/open3.jpg
Click to expand...
Click to collapse
Did you add any steps to mount the system? I don't believe I did, but it seems others are finding it to be read-only.

jerseyh22accord said:
I'm currently trying it.
I have a 64 bit driver on my computer that i used to use for my D1 but it doesn't recognize my D2 when doing adb devices and i cant install the 32 bit driver
Click to expand...
Click to collapse
Don't know if it will help you, but if it's anything like the DInc, you could just use the SDK's drivers and add a few device identifier lines to the INF file before installing them.

[Huawei IDEOS U8150] How to gain root access

I hold no responsibility to how you use or not use this info and if you brick phone - you do this at your own risk
There is a couple away you can go about gaining root access with this phone I have tested all 3 ways but only had success with 2 of them.
a) You can download 'z4root' from the Android Market (If is still available) or search XDA forums for it.
b) Search the XDA forums for 'SuperOneClick' which requires mono to work on Linux. I have read people that have had success with 'SuperOneClick' but that was not the case for me.
c) My preferred method:
Prerequisite:
knowledge of Linux and Terminal
knowledge of ADB (guide available in forums)
I did all this using Debian (testing) 64bit, Android SDK.
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Downloading and/or Installing required software:
1) Downloading and installing the android-sdk from: developer.android.com/sdk/index.html
2) Downloading and extracting 'SuperOneClick' (you will only need these 5 files: rageagainstthecage, sqlite3, su, busybox and superuser.apk)
3) Copy rageagainstthecage, sqlite3, su, busybox and superuser.apk into the platform-tools directory of android-sdk. Put phone in debug mode.
4) From a terminal (command line) change to the android/platform-tools directory and carefully do these steps.
Check to see if adb can see your phone properly:
Code:
./adb devices
You should see the serial number of you device, if you see bunch of '?' you have done something wrong.
Now for the fun part rooting the phone: <= no phun intended hehe
Code:
./adb push rageagainstthecage /data/local/tmp/rageagainstthecage
Code:
./adb shell
Code:
cd /data/local/tmp
Code:
chmod 0755 rageagainstthecage
Code:
./rageagainstthecage
5) Now wait until you get kicked out from adb before you do the following:
Code:
./adb shell
If everything worked now you should see a "#" instead of the "$" you saw previously in the adb shell which means you shouldn't get "permission denied" in the following steps:
Code:
mount -o rw,remount /dev/block/mdtblock4 /system
Code:
exit
Code:
./adb push su /system/bin/su
Code:
./adb push busybox /system/bin/busybox
Code:
./adb push sqlite3 /system/bin/sqlite3
Code:
./adb push Superuser.apk /system/app/Superuser.apk
Code:
./adb shell
Code:
cd /system/bin
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Code:
./adb reboot
Now you should be able to use apps like 'Cache Cleaner NG', 'Root Explorer', 'SetCPU' etc that require root access to work correctly.
Enjoy

Guide reflash FW for those who did some damage:
* Download from here that you want to install the FW
* Copy the folder in the microSD DLOAD (with the file inside UPADATE.APP)
* From phone off, Volume + Hold down RED BUTTON UP and power button.
* start the firmware upgrade, take a few minutes and then restart the phone . is a bit slow, do not be afraid, let him work and then back on (like the first time)
Help to get into recovery mode:
* down the 'volume up 'and 'green button'and then switch the device
Guide to bootloader mode:
* switch off, press and hold power button + volume down + red key

Overclock
Can this fone be oveclocked

SethIsHere said:
Can this fone be oveclocked
Click to expand...
Click to collapse
yes it can be OCed, I recommend using setCPU from the market

SethIsHere said:
Can this fone be oveclocked
Click to expand...
Click to collapse
Yes it can, to a Maximum of 600mhz (0.6 ghz) on the stock kernel
setCPU is no longer available on the market for free afaik.
Also can someone better translate the instructions to get into recovery mode? i can barely make sense of the above instructions ^^^

.produkt-R said:
Also can someone better translate the instructions to get into recovery mode? i can barely make sense of the above instructions ^^^
Click to expand...
Click to collapse
does this help:
http://forum.xda-developers.com/showpost.php?p=10371747&postcount=5

quail said:
does this help:
http://forum.xda-developers.com/showpost.php?p=10371747&postcount=5
Click to expand...
Click to collapse
Helped, Thanks.
Although after reading the entire page, i wonder if i should have a Recovery ROM installed. But i wonder if the phone will be left in it's current working state after installing it ?

i used z4root, worked fine for me

quail said:
Code:
chmod 4755 su
Code:
chmod 4755 busybox
Code:
chmod 4755 sqlite3
Click to expand...
Click to collapse
I think only "su" should be 4755 (setuid root), busybox and sqlite3 should just be 0755? Thanks for the instructions.

pb05life said:
i used z4root, worked fine for me
Click to expand...
Click to collapse
Ok I figured it ill shut up you have to use crappy dos command prompt and type everything in manually install proggies lol Google must die!

quail said:
Creating correct permissions to access the phone via USB:
i) create
Code:
/etc/udev/rules.d/51-android.rules
ii) in the file put
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
iii) then
Code:
chmod a+r /etc/udev/rules.d/51-android.rules
iv) restart udev or reboot
Click to expand...
Click to collapse
Anyone know this part for windows XP?Not linux?
I got to rageagainstthecage and it says permission denied.

fvckyougooglescammer said:
So would you tell us, exactly how you did it?
Without using the market place?
Because I have tried 100 things downloaded all that junk wasted 5 hours.
And I do not know how to run the z4root on my phone.
I do not want to install another ROM.
I do not know why you can not run z4root and a file manager from the SD card I have tried methods with the SDK they are total rubbish.
Once again *without* using the market place.
Thanks
Click to expand...
Click to collapse
Download it mediafire.com/u8150
Sent from my Ideos using XDA App

could you explain why you prefer this way instead using z4root?

nitro-ale said:
could you explain why you prefer this way instead using z4root?
Click to expand...
Click to collapse
I have Z4root on the phone and its supposedly rooted.
Yet, I can install apps from PC onto phone, but can not uninstall them.
Adb always gives me failure.
And if I try from shell it always says permission denied.

tilal6991 said:
Download it
Sent from my Ideos using XDA App
Click to expand...
Click to collapse
Hi thanks downloaded it fine its on the phone but this doesn't tell me how to remove apps.
I have been able to install but not remove adb always says failure.

Thanks man,
Just worked perfectly on my IDEOS brought from 2degrees in NZ.
The copy of SuperOneClick that I downloaded contained a file called su-v2 instead of su. In order to get the hack to work I had to rename su-v2 to su before running ./rageagainstthecage . Pretty obvious, but it might help someone out.
Thanks

fvckyougooglescammer said:
I have Z4root on the phone and its supposedly rooted.
Yet, I can install apps from PC onto phone, but can not uninstall them.
Adb always gives me failure.
And if I try from shell it always says permission denied.
Click to expand...
Click to collapse
I followed your instructions and installed SetCPU to test my phone was rooted. It worked great! Thanks.
I still have a problem. When I try adb root it still says "adbd cannot run as root in production builds". I'm trying this to be able to control my phone with pc mouse/keyboard with androidscreencast.
Any suggestions will be much appreciated.
Answering to myself: I updated my phone with FUSIONideos 1.5 and now adb runs as root without problems.

Z4root
http://forum.xda-developers.com/showthread.php?t=833953
Worked for me

Does it removes simlock I have Huawei U8150 IDEOS Android phone with career lock ( Simlock ), so will this remove it

can there be a batch file / command / app for all this, too techy out there
also how to setup the environment to run these commands, i m windows user can i do it ?

su not updated

I have my Polaris NAND flashed with 2.6.25 kernel + casacristo's RLS18 ROM.
I have updated from the market the Superuser but now I get the pessage that SU is not updated and to download the new one (3.0.3.2).
I download the new one , the Root access is granted but at the end more or less I receive this message translated from italian:
...
...
md5sum ... OK
Mod file su 06755... OK
Moving su to its final position ... failed...
TRY Again
I tryed several times but ... no chance to update it... how can I manage ?
miazza

Here is latest su binaries v3.0.3.2. Download and unzip file. Push this to /system/bin and /system/xbin and then change rights with chmod to 6755. Reboot phone. Done.

Thanks, I will try.
Shall I do via ADB or can I try with RootExplorer for example ?
miazza

ADB, unless your root explorer can set 6755 rights

whitealien said:
ADB, unless your root explorer can set 6755 rights
Click to expand...
Click to collapse
It worked great. I managed with RootExplorer but it can be done also via FTP with Filezilla.
Thanks
miazza

file permissions doesn't work
Hi,
I use a HTC wildfire S, who have been rooted, but still in original ROM.
My SU doesn't want to be updated, as described in the first post.
So I downloaded the ZIP, and put SU on the sdcard. With ROOT BROWSER I copy it on /system/bin (SU have been copied automaticaly in /system/xbin).
I tried to change the permissions files, but after reboot, permissions are ---rwxr-x.
I tried with ADB. My phone is well recognised :
C:\Program Files\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH191TR05136 device
When I tried to change permissions file SU :
C:\Program Files\Android\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$ chmod 6755 /mnt/sdcard/temp/su
chmod 6755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$ chmod 755 /mnt/sdcard/temp/su
chmod 755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$
Do you have an idea ? Thanks by advance, because right now, my phone is not still root...

I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza

miazza said:
I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza
Click to expand...
Click to collapse
Root browser seems to work the same way.
How can you use FTP with a phone ? It's suppose to use an IP adress. But by USB, there is not... But I will,l try asap.
However, my apps couldn't take root permissions, so I feel bad...

Use SwiFTP (it should be free from the market).
It works over Wireless connection to your internal WLAN and provide you with an FTP address like 192.160.0.x.
While you are connected through FTP client (like Filezilla), you can see your mobile File System as well as your SD.
with a right click on the su file you can change your rights.
But I do not know if it works even if you are not rooted...
miazza

I solved my problem my re-rooting my phone, using http://forum.xda-developers.com/attachment.php?attachmentid=672519&d=1312136127.
My phone says that the binary SU was obsolete, but when I tried "AGAIN" to update it, it was successful that time.
Strange, I don't understand why now the update was ok. But all is right.
Thanks everyone for the help.

[Q] Using ADB from Terminal Emulator

I recently received my Transformer back after RMA-ing it for a non functioning screen. Of course, even though the problem lied with the hardware, they still unrooted and reinstalled stock firmware on it. Everything on it works, except for the USB cable that seems to be either not working, or because they installed all my apps and settings back on the tablet, something's wrong. This is a problem when it comes to rooting it again. What I'm trying to do is run the commands through the Terminal Emulator, but here is what happens:
Code:
[email protected]: /sdcard $ adb start-server
* Daemon not running, starting it on port 5038 *
* Daemon started successfully *
[email protected]: /sdcard $ adb connect localhost:5038
connected to localhost:5038
[email protected]: /sdcard $ adb push su /data/local/tmp
error: device not found
So my question is, is it even possible to do this? If not, is there another way to do it?
Thanks in advanced for any help!

adb is the android debugging bridge what it does is changes your shell from your computer to your device so you do not need to run anything that refers to adb from your device

Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)

Thing O Doom said:
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Click to expand...
Click to collapse
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found

aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
push is an adb command not a terminal command

mrevankyle said:
push is an adb command not a terminal command
Click to expand...
Click to collapse
I understand that.
I've been trying mv with no luck:
Code:
mv /sdcard/su /data/local/tmp
failed on '/sdcard/su' - Cross-device link

Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip

Thing O Doom said:
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Click to expand...
Click to collapse
Code:
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
EDIT: Also, I've tried chmod, and I get an Operation not permitted error.

This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.

Thing O Doom said:
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Click to expand...
Click to collapse
Yes It's running completely up to date (unfortunately) 9.2.1.24.

aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer

gee one said:
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
Click to expand...
Click to collapse
Yeah, I gotcha, but the only command I have that comes close to cp is mv, and all the commands are very strictly limited.

[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