Extract Proprietary Files
This only has to be done the first time you build. If you have already done this part, you can skip this box.
You will need to have a vibrant with a working rooted ROM and working ADB. This script pulls the proprietary files from your phone. Connect your phone to you computer and insure that ADB is working properly.
cd ~/android/system/device/samsung/vibrant/
./extract-files.sh
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vibrant
I'm having an issue with this step, I've tried:
./extract-files.sh
bash: ./extract-files.sh: Permission denied
and
sudo ./extract-files.sh
sudo: ./extract-files.sh: command not found
the file it there, I'm not too sure what the issue is, any help would be appreciated
If it's something stupid I missed, dont hesitate to flame me
stefan.buddle said:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vibrant
I'm having an issue with this step, I've tried:
./extract-files.sh
bash: ./extract-files.sh: Permission denied
and
sudo ./extract-files.sh
sudo: ./extract-files.sh: command not found
the file it there, I'm not too sure what the issue is, any help would be appreciated
If it's something stupid I missed, dont hesitate to flame me
Click to expand...
Click to collapse
chmod 755 extract-files.sh
or run
sh extract-files.sh within the directory
thanks for the response, I'll try this when I'm back to my computer, sorry for my lack of the Unix commands, in new to linux, havent learned all the nifty commands yet.
stefan.buddle said:
thanks for the response, I'll try this when I'm back to my computer, sorry for my lack of the Unix commands, in new to linux, havent learned all the nifty commands yet.
Click to expand...
Click to collapse
No problem, everyone starts at some point, being new does not disqualify you from the linux user base
new problem with the same step
./extract-files.sh: 2: cannot open !DOCTYPE: No such file
./extract-files.sh: 2: html: not found
./extract-files.sh: 3: Syntax error: newline unexpected
Not asking to be spoon fed answers a simple point in the right direction would suffice, thanks in advance
stefan.buddle said:
new problem with the same step
./extract-files.sh: 2: cannot open !DOCTYPE: No such file
./extract-files.sh: 2: html: not found
./extract-files.sh: 3: Syntax error: newline unexpected
Not asking to be spoon fed answers a simple point in the right direction would suffice, thanks in advance
Click to expand...
Click to collapse
That is within the script itself.
Did you follow Andy Rubin response to Steve Jobs advise?
http://www.engadget.com/2010/10/19/andy-rubin-responds-to-steve-jobs-with-a-tweet/
On a more to the topic in hand, there was a thread in dev section not a long ago about building the CM environment with all the git instructions, etc.
Try searching that, or go to the source - CM team
Sorry, I couldn't be of more help, your problem seems to be related to your particular setup or incomplete documentation.
stefan.buddle said:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vibrant
I'm having an issue with this step, I've tried:
./extract-files.sh
bash: ./extract-files.sh: Permission denied
and
sudo ./extract-files.sh
sudo: ./extract-files.sh: command not found
the file it there, I'm not too sure what the issue is, any help would be appreciated
If it's something stupid I missed, dont hesitate to flame me
Click to expand...
Click to collapse
to anyone who had this same issue,here is how to get past permission denied:
navigate to the proprietary folder where the extract-files.sh file is
make sure you have the phone on with usb debugging on
now run this command in the terminal cd'd into the proprietary directory
./extract-files.sh
now everything should run correctly...just spent the last hour trying this..once i navigated into the directory where extract-files.sh is and ran the command,it worked fine..
hope this helps someone..i know im a little late.lol
./extract-files.sh
same issue here.
i have root explorer and mounted as r/w, ran chmod 755 extract-files.sh and got right past the issue.
hope it helps someone.
I rooted my phone and I was able to install Superuser and Titanium Backup and both appear to be running successfully. My question is when I run adb shell from my PC and I get the $, I get permission denied when I type SU or whoami? Did I miss something?
C:\>adb shell
$ su
su
Permission denied
$ whoami
whoami
whoami: permission denied
$
just wondering why you need to use superuser when you use adb shell
OK, so why the permission denied response from the OS?
http://forum.xda-developers.com/showthread.php?t=1002203
that prob has something to do with it, push that kernel and try again
OK thanks, I will keep that in mind if I run into issues. Everything else is working fine otherwise, so I will well enough alone for now, while I read the docs on the Android Dev site.
I have looked everywhere for a solution but I cannot find any postings. I went to WotanServer and paid to have 4.0.2.A.42 reflashed to my phone so I could it root it using zergrush or flashtool as a necessary step before upgrading to ICS with root. Bootloader is locked. I got that done but then neither tool would root the phone. I tried to flash an st15i rom that I found but it just screwed things up worse. Flashtool still would not recognize the phone and kept asking me to select the model from a list just like it did when I had the proper st15a rom on it. Zergrush did nothing either but continued to give constant error messages about the abd server being outdated. With the st15i rom, Sony PC Companion wouldn't even let me upgrade to anything more current, telling me that I had the most current software. I want root the phone so I can use Barnacle to tether my tablet. I have never gone through such fits trying to root a phone and I've done it on a few.
Can anyone help please? Thanks -
zentrek said:
I have looked everywhere for a solution but I cannot find any postings. I went to WotanServer and paid to have 4.0.2.A.42 reflashed to my phone so I could it root it using zergrush or flashtool as a necessary step before upgrading to ICS with root. Bootloader is locked. I got that done but then neither tool would root the phone. I tried to flash an st15i rom that I found but it just screwed things up worse. Flashtool still would not recognize the phone and kept asking me to select the model from a list just like it did when I had the proper st15a rom on it. Zergrush did nothing either but continued to give constant error messages about the abd server being outdated. With the st15i rom, Sony PC Companion wouldn't even let me upgrade to anything more current, telling me that I had the most current software. I want root the phone so I can use Barnacle to tether my tablet. I have never gone through such fits trying to root a phone and I've done it on a few.
Can anyone help please? Thanks -
Click to expand...
Click to collapse
wrong forum, put in general section
try this
http://www.xda-developers.com/android/root-many-ics-and-jelly-bean-android-devices/
this worked fine on my friend's xperia p with the latest update.
follow this tutorial http://talk.sonymobile.com/thread/41119
gandhar said:
wrong forum, put in general section
try this
http://www.xda-developers.com/android/root-many-ics-and-jelly-bean-android-devices/
this worked fine on my friend's xperia p with the latest update.
Click to expand...
Click to collapse
Same issues and no success but thanks for the suggestion. "ADB server is out of date. killing..." and "*failed to start daemon* error" messages constantly. Even though the script does claim at the end of running that it's accomplished its mission, it hasn't. The phone is still not rooted.
zentrek said:
Same issues and no success but thanks for the suggestion. "ADB server is out of date. killing..." and "*failed to start daemon* error" messages constantly. Even though the script does claim at the end of running that it's accomplished its mission, it hasn't. The phone is still not rooted.
Click to expand...
Click to collapse
well i did it on my linux machine, try with a different pc, as the adb problems are not phone side.
gandhar said:
well i did it on my linux machine, try with a different pc, as the adb problems are not phone side.
Click to expand...
Click to collapse
I just tried it from my laptop after booting both Win7 and Ubuntu. No joy on Win7 though it looked different from the desktop process and seemed like it might go through. The shell script opens in gedit in Ubuntu - how do I get the runme file to open in a bash shell and do somethng? Thanks
zentrek said:
I just tried it from my laptop after booting both Win7 and Ubuntu. No joy on Win7 though it looked different from the desktop process and seemed like it might go through. The shell script opens in gedit in Ubuntu - how do I get the runme file to open in a bash shell and do somethng? Thanks
Click to expand...
Click to collapse
the script has a linux version, its v2 i think. that has a runme.sh file.
change permissions and run with
Code:
bash runme.sh
gandhar said:
the script has a linux version, its v2 i think. that has a runme.sh file.
change permissions and run with
Code:
bash runme.sh
Click to expand...
Click to collapse
This did not work unfortunately. This what I get:
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice:
1
Xperia T mode enabled!
Please connect device with ADB-Debugging enabled now....
RunMe.sh: line 23: ./stuff/adb: Permission denied
RunMe.sh: line 24: ./stuff/adb: Permission denied
RunMe.sh: line 25: ./stuff/adb: Permission denied
RunMe.sh: line 26: ./stuff/adb: Permission denied
RunMe.sh: line 27: ./stuff/adb: Permission denied
RunMe.sh: line 43: ./stuff/adb: Permission denied
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
RunMe.sh: line 46: ./stuff/adb: Permission denied
Successful, going to reboot your device!
RunMe.sh: line 48: ./stuff/adb: Permission denied
Waiting for device to show up again....
RunMe.sh: line 51: ./stuff/adb: Permission denied
The Xperia T will reboot 2 times! This is normal please be patient!
RunMe.sh: line 57: ./stuff/adb: Permission denied
RunMe.sh: line 58: ./stuff/adb: Permission denied
RunMe.sh: line 59: ./stuff/adb: Permission denied
RunMe.sh: line 60: ./stuff/adb: Permission denied
RunMe.sh: line 61: ./stuff/adb: Permission denied
RunMe.sh: line 63: ./stuff/adb: Permission denied
RunMe.sh: line 64: ./stuff/adb: Permission denied
RunMe.sh: line 65: ./stuff/adb: Permission denied
RunMe.sh: line 66: ./stuff/adb: Permission denied
RunMe.sh: line 68: ./stuff/adb: Permission denied
RunMe.sh: line 69: ./stuff/adb: Permission denied
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Press [Enter] key to quit...
try,
Code:
sudo bash runme.sh
if running an easy distro like ubuntu / fedora.
About being adb version out of date ,probably a process using adb is running constatly in background like flashtool .
Try this method
Get the DoomLord's zergrush kit .
Close all programs using adb like flashtool ,Droid explorer and so on ...
Open CMD in windows
(commands with > are executed in cmd ,with $/# in adb shell
navigate to Doomlords' extracted folder and navigate to files folder in it
type
Code:
>adb shell
Step 1.
Code:
$mkdir /data/tmp
$exit
after that
Step 2.
Code:
>adb push zergrush /data/temp/zergrush
Go back to shell with adb shell
//fix permissions
Code:
$cd /data/tmp
$chmod 777 zergrush
//execute
Code:
$ zergrush
Wait for a while for it to execute
Restart adb shell if it is successful
if it is successful you will get a insecure shell(#) prompt
then go back to adb shell
//remounts system
Step 3.
Code:
#mount -o remount,rw /system
#exit
//Push files
Code:
>adb push su /system /xbin/su
>adb push superuser.apk /system/app/superuser.apk
go to adb shell
//fix su permissions
Code:
#chmod 755 /system/xbin/su
#chmod 644 /system/app/superuser.apk
//Permanent shell for ICS upgrade
Step 4.
Code:
#echo ro.kernel.qemu=1 >/data/local.prop
Step 5.
Code:
#reboot
If you are planning to upgrade to ICS right away ,there is no need for Step 3.(But it is advised anyway )
Step 4. is to prepare for ICS upgrade ,it gives you permanent insecure shell but has some hitches like vibration doesnt seem to work ...so it is best to be left temporary .
Repeat Step 3 after the ICS upgrade ,reboot and delete local.prop from /data and again reboot ...
zentrek said:
This did not work unfortunately. This what I get:
Device type:
1) Xperia T
2) LT26,LT22 etc.
3) Other
Make a choice:
1
Xperia T mode enabled!
Please connect device with ADB-Debugging enabled now....
RunMe.sh: line 23: ./stuff/adb: Permission denied
RunMe.sh: line 24: ./stuff/adb: Permission denied
RunMe.sh: line 25: ./stuff/adb: Permission denied
RunMe.sh: line 26: ./stuff/adb: Permission denied
RunMe.sh: line 27: ./stuff/adb: Permission denied
RunMe.sh: line 43: ./stuff/adb: Permission denied
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
RunMe.sh: line 46: ./stuff/adb: Permission denied
Successful, going to reboot your device!
RunMe.sh: line 48: ./stuff/adb: Permission denied
Waiting for device to show up again....
RunMe.sh: line 51: ./stuff/adb: Permission denied
The Xperia T will reboot 2 times! This is normal please be patient!
RunMe.sh: line 57: ./stuff/adb: Permission denied
RunMe.sh: line 58: ./stuff/adb: Permission denied
RunMe.sh: line 59: ./stuff/adb: Permission denied
RunMe.sh: line 60: ./stuff/adb: Permission denied
RunMe.sh: line 61: ./stuff/adb: Permission denied
RunMe.sh: line 63: ./stuff/adb: Permission denied
RunMe.sh: line 64: ./stuff/adb: Permission denied
RunMe.sh: line 65: ./stuff/adb: Permission denied
RunMe.sh: line 66: ./stuff/adb: Permission denied
RunMe.sh: line 68: ./stuff/adb: Permission denied
RunMe.sh: line 69: ./stuff/adb: Permission denied
You can close all open command-prompts now!
After reboot all is done! Have fun with Root!
Bin4ry
Press [Enter] key to quit...
Click to expand...
Click to collapse
i told you to change permission. you skipped that
do a
Code:
sudo chmod 777 filename
do this to all executables like adb the bash script, the stuff folder
then try again
I have an unrooted Sony Tablet S 32GB Wifi model #SGPT112US/S Android Version 4.0.3 (release 5) Kernel 2.6.39.4 [email protected] #1.
Desktop trying to root from is Windows 7 64 bit (never had any issues rooting when it was on HC and or other devices in the past)
I have attempted the automated way from http://forum.xda-developers.com/showthread.php?t=1886460 , & http://forum.xda-developers.com/showthread.php?t=1828107 all 15 scripts, one at a time, all failed, all factory reset after including erasing USB storage so it is clean.
I have tried to re-sign step by step, copy/paste line by line from http://forum.xda-developers.com/showpost.php?p=31582941&postcount=42 and then follow instructions from http://forum.xda-developers.com/showthread.php?t=1828107 and tried the auto scripts again and still no luck.
I already have latest drivers from the afore mentioned http://forum.xda-developers.com/showthread.php?t=1828107 & and tested ADB as well. After each reset I enable Unknown Sources from Settings, Security, and Settngs, Developer Options, USB Debugging.
Wifi enabled, I also run Google Play and download Zinsigner2. (obviously for re-signing), tablet is plugged into wall outlet in case any issue with power and the update.
Files Extracted to root of C:\ using 7-zip using latest version of 7-zip in case of any directory length limitations.
I have tried running ADB from both the directory itself and enviornment path from afore mentioned link, and same adb version as from link.
I have also attempted the manual mode from http://forum.xda-developers.com/showthread.php?t=1886310 with both re-signed vpnfaker and not and no go.
I have also tried multiple people's other vpnfaker files just to eliminate I am somehow a total [email protected] and cant copy/paste but no go either (didnt really expect that to work but figured worth a shot).
Below is what I receive from Automated script 1st, and 2nd manual typing it out from manual link. If you have any suggestions/personal experience with this model and have success, please let me know what else I may be missing. I have way to many hours into this so far.
Thanks in advance.
Manual
C:\Root>adb restore settings.ab
C:\Root>cd /data/data/com.android.settings
The system cannot find the path specified.
C:\Root>adb shell
[email protected]:/ $ cd /data/data/com.android.settings
cd /data/data/com.android.settings
[email protected]:/data/data/com.android.settings $ rm -r a
rm -r a
rm failed for a, Permission denied
255|[email protected]:/data/data/com.android.settings $
I then run the while : ; do ln -s /data a/file99; done and it starts the loop.
I continue with the following
C:\Root>adb shell ls -ld /data
drwxrwxrwx system system 2012-10-15 18:42 data
C:\Root>adb push busybox /data/local/tmp
1313 KB/s (1867568 bytes in 1.388s)
C:\Root>adb push rootkit.tar.gz /data/local/tmp
1337 KB/s (469979 bytes in 0.343s)
C:\Root>adb push Superuser.apk /data/local/tmp
1259 KB/s (1468798 bytes in 1.138s)
C:\Root>adb push su /data/local/tmp
1323 KB/s (380532 bytes in 0.280s)
C:\Root>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ chmod 755 busybox
chmod 755 busybox
[email protected]:/data/local/tmp $ ./busybox tar zxf rootkit.tar.gz
./busybox tar zxf rootkit.tar.gz
[email protected]:/data/local/tmp $ exit
exit
C:\Root>adb push VpnFaker.apk /data/local/tmp
1254 KB/s (200436 bytes in 0.156s)
C:\Root>adb shell
[email protected]:/ $ touch -t 1346025600 /data/local/tmp/VpnFaker.apk
touch -t 1346025600 /data/local/tmp/VpnFaker.apk
[email protected]:/ $ exit
exit
C:\Root>adb shell
[email protected]:/ $ cd /data
cd /data
[email protected]:/data $ /data/local/tmp/busybox cp -r system system2
/data/local/tmp/busybox cp -r system system2
cp: can't open 'system/entropy.dat': Permission denied
cp: can't open 'system/batterystats.bin': Permission denied
cp: can't open 'system/users/userlist.xml': Permission denied
cp: can't open 'system/users/0.xml': Permission denied
cp: can't open 'system/accounts.db': Permission denied
cp: can't open 'system/accounts.db-journal': Permission denied
cp: can't open 'system/called_pre_boots.dat': Permission denied
cp: can't open 'system/wallpaper_info.xml': Permission denied
cp: can't open 'system/appwidgets.xml': Permission denied
cp: can't open 'system/netpolicy.xml': Permission denied
cp: can't open 'system/netstats.bin': Permission denied
cp: can't open 'system/netstats_xt.bin': Permission denied
cp: can't open 'system/netstats_uid.bin': Permission denied
1|[email protected]:/data $ /data/local/tmp/busybox find system2 -type f -exec chmod
666 {} \;
d system2 -type f -exec chmod 666 {} \; <
[email protected]:/data $ /data/local/tmp/busybox find system2 -type d -exec chmod 7
77 {} \;
system2 -type d -exec chmod 777 {} \; <
[email protected]:/data $ mv system system-
mv system system-
[email protected]:/data $ mv system2 system
mv system2 system
failed on 'system2' - Permission denied
255|[email protected]oid:/data $ mv app app-
mv app app-
[email protected]:/data $ mkdir app
mkdir app
[email protected]:/data $ mv /data/local/tmp/VpnFaker.apk /data/app
mv /data/local/tmp/VpnFaker.apk /data/app
[email protected]:/data $ TZ=0 ls -l /data/app
TZ=0 ls -l /data/app
-rw-rw-rw- shell shell 200436 2012-08-27 00:00 VpnFaker.apk
[email protected]:/data $ /data/local/tmp/busybox sed -f /data/local/tmp/packages.xm
l.sed system-/packages.xml > system/packages.xml
tem-/packages.xml > system/packages.xml <
/system/bin/sh: cannot create system/packages.xml: Permission denied
1|[email protected]:/data $ /data/local/tmp/busybox grep vpndialogs system/packages.
xml
p vpndialogs system/packages.xml <
grep: system/packages.xml: No such file or directory
2|[email protected]:/data $
Device reboots on its own after putting in /data/local/tmp/busybox grep vpndialogs system/packages.xml
Although it seems silly, still following directions I type in and perform the following.
exit
adb reboot
Auto script (version 15 in this example)
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Mike>cd\
C:\>dir r*
Volume in drive C has no label.
Volume Serial Number is B637-CD90
Directory of C:\
10/15/2012 05:37 PM <DIR> Root
10/13/2012 05:11 AM 10,236 RunMe.bat
10/13/2012 05:12 AM 11,695 RunMe.sh
2 File(s) 21,931 bytes
1 Dir(s) 285,418,246,144 bytes free
C:\>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
1093 KB/s (314540 bytes in 0.280s)
pkg: /sdcard/tmp/Term.apk
Success
1281 KB/s (1085140 bytes in 0.826s)
1151 KB/s (91980 bytes in 0.078s)
1273 KB/s (996704 bytes in 0.764s)
1337 KB/s (469982 bytes in 0.343s)
mkdevsh
onload.sh
onload2.sh
packages.xml.sed
remount.sh
VpnFaker.apk
_su
rm failed for /data/data/com.android.settings/a/*, No such file or directory
Please look at your device and click "Restore my data"
1st RESTORE OK, hit ENTER to continue.
Press any key to continue . . .
rm failed for /data/data/com.android.settings/a, Permission denied
Please look at your device and click "Restore my data"
Achieved! hit ENTER to continue.
Press any key to continue . . .
cp: can't open '/data/system/entropy.dat': Permission denied
cp: can't open '/data/system/batterystats.bin': Permission denied
cp: can't open '/data/system/users/userlist.xml': Permission denied
cp: can't open '/data/system/users/0.xml': Permission denied
cp: can't open '/data/system/accounts.db': Permission denied
cp: can't open '/data/system/accounts.db-journal': Permission denied
cp: can't open '/data/system/called_pre_boots.dat': Permission denied
cp: can't open '/data/system/wallpaper_info.xml': Permission denied
cp: can't open '/data/system/appwidgets.xml': Permission denied
cp: can't open '/data/system/netpolicy.xml': Permission denied
cp: can't open '/data/system/netstats.bin': Permission denied
cp: can't open '/data/system/netstats_xt.bin': Permission denied
cp: can't open '/data/system/netstats_uid.bin': Permission denied
Need to reboot now!
Waiting for device to come up again....
Unlock your device, a Terminal will show now, type this 2 lines, after each line
press ENTER
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
after this is done press a key here in this shell to continue!
If the shell on your device does not show please re-start the process!
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does
not exist.
Press any key to continue . . .
201 KB/s (1241 bytes in 0.006s)
/data/local/tmp/script1.sh[1]: /dev/sh: not found
/data/local/tmp/script1.sh[2]: /dev/sh: not found
/data/local/tmp/script1.sh[3]: /dev/sh: not found
/data/local/tmp/script1.sh[4]: /dev/sh: not found
/data/local/tmp/script1.sh[5]: /dev/sh: not found
/data/local/tmp/script1.sh[6]: /dev/sh: not found
/data/local/tmp/script1.sh[7]: /dev/sh: not found
/data/local/tmp/script1.sh[8]: /dev/sh: not found
/data/local/tmp/script1.sh[9]: /dev/sh: not found
/data/local/tmp/script1.sh[10]: /dev/sh: not found
/data/local/tmp/script1.sh[11]: /dev/sh: not found
/data/local/tmp/script1.sh[12]: /dev/sh: not found
/data/local/tmp/script1.sh[13]: /dev/sh: not found
/data/local/tmp/script1.sh[14]: /dev/sh: not found
/data/local/tmp/script1.sh[15]: /dev/sh: not found
/data/local/tmp/script1.sh[16]: /dev/sh: not found
/data/local/tmp/script1.sh[17]: /dev/sh: not found
/data/local/tmp/script1.sh[18]: /dev/sh: not found
/data/local/tmp/script1.sh[19]: /dev/sh: not found
Almost complete! Reboot and cleanup.
Waiting for device to come up again....
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
I am having the exact same issue. Only main difference is I am running Windows XP not 7.
Same here.
I don't get "Android is updated" after the reboot. Terminal emulator doesn't start, when I start it manually and enter "id", the UID is 10076, and not 1000 (as it should be as a system app). I think the problem is that we don't get a write permission that others get.
Edit:
in the instructions of the manual rooting method there is a line that reads"Start the injected Terminal Emulator". I know almost nothing about adb, but before this line the emulator "Term.apk" has been mentioned NOWHERE, so it hasn't been injected, or am I getting something wrong.
daClaus said:
Same here.
I don't get "Android is updated" after the reboot. Terminal emulator doesn't start, when I start it manually and enter "id", the UID is 10076, and not 1000 (as it should be as a system app). I think the problem is that we don't get a write permission that others get.
Edit:
in the instructions of the manual rooting method there is a line that reads"Start the injected Terminal Emulator". I know almost nothing about adb, but before this line the emulator "Term.apk" has been mentioned NOWHERE, so it hasn't been injected, or am I getting something wrong.
Click to expand...
Click to collapse
I also don't get android upgated as well (my line of same exact issue might need to be tweaked a bit, I was half asleep when I compared the OP situation to my own) As far as your edit above when I go through manual rooting I get nothing but permissions errors. My understand, forgive me if I am wrong, is that much of it will cause permissions errors and that is okay. I also think the guys here are light years ahead of the game for me as well as many others, so it may just be that everyone else picked up and understood what they were saying to do and I completly missed it.
I did run a AIO script yesterday and it came back as unrootable, which bothers me to say the least, exspecially since I've seen everyone get the thing rooted here.
Good luck, I'm subscribed to this and if I find anything I'll be sure to share here with you
Rob
I have posted to other threads to see if anyone has gotten the root to work with our model SGPT112US/S. I tried to skim through and see (although there are dozens and dozens of pages) but dont think I saw one that did as of yet. Wondering if there is some sort of bug/something different that has to be done for SGPT112US/S.
Time will tell I guess.
Well, I solved the problem. The whole thing worked the first time when I copied everything to C: on my hard disk. I have to admit that I have the SGPT111AT/S, but I think that doesn't make a difference. RunMe.bat and RunMe.sh are in root, the rest is in the "stuff" folder. Rooting rel. 1a worked instantly, and rooting Rel. 5 after the upgrade worked also at the first attempt. Before that I had the files on my desktop and always got the errors mentioned in the first post.
daClaus said:
Well, I solved the problem. The whole thing worked the first time when I copied everything to C: on my hard disk. I have to admit that I have the SGPT111AT/S, but I think that doesn't make a difference. RunMe.bat and RunMe.sh are in root, the rest is in the "stuff" folder. Rooting rel. 1a worked instantly, and rooting Rel. 5 after the upgrade worked also at the first attempt. Before that I had the files on my desktop and always got the errors mentioned in the first post.
Click to expand...
Click to collapse
I have the same problem but moving the file to c:\ didn't work for me- same result
Did you re-sign the VpnFaker.apk?
daClaus said:
Did you re-sign the VpnFaker.apk?
Click to expand...
Click to collapse
I didn't will give that a try. Thanks.
I tried resigning the VpnFaker.apk but still didn't work. Just for the hell of it I tried running the script in Normal mode rather than Tablet S mode with the results shown below. Based on the results of this i.e. no backup and restore on the system I installed back up and restore apk from the forum and tried the script again with the results shown below. During this I noticed that there was a message on the tablet saying that backup and restore had stopped working and in fact neither of the two backup and restore apk's from the forum will actually run on my tablet s so at the moment I'm assuming that this is the problem and looking for ways to resolve this.
Output in Normal Mode:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Normal Mode enabled!
.
Pushing busybox....
1057 KB/s (1085140 bytes in 1.002s)
Pushing su binary ....
1087 KB/s (91980 bytes in 0.082s)
Pushing Superuser app
1122 KB/s (996704 bytes in 0.867s)
Making busybox runable ...
.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
Output in Tablet S Mode:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (13.10.2012) v15 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
929 KB/s (314540 bytes in 0.330s)
pkg: /sdcard/tmp/Term.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
1255 KB/s (1085140 bytes in 0.843s)
1299 KB/s (91980 bytes in 0.069s)
1180 KB/s (996704 bytes in 0.824s)
1229 KB/s (469987 bytes in 0.373s)
mkdevsh
onload.sh
onload2.sh
packages.xml.sed
remount.sh
VpnFaker.apk
_su
Please look at your device and click "Restore my data"
1st RESTORE OK, hit ENTER to continue.
Press any key to continue . . .
rm failed for /data/data/com.android.settings/a, Permission denied
Please look at your device and click "Restore my data"
Achieved! hit ENTER to continue.
Press any key to continue . . .
cp: can't open '/data/system/users/userlist.xml': Permission denied
cp: can't open '/data/system/users/0.xml': Permission denied
cp: can't open '/data/system/usagestats/usage-20121018': Permission denied
cp: can't open '/data/system/usagestats/usage-20121019': Permission denied
cp: can't open '/data/system/usagestats/usage-history.xml': Permission denied
cp: can't open '/data/system/registered_services/android.accounts.AccountAuthent
icator.xml': Permission denied
cp: can't open '/data/system/registered_services/android.content.SyncAdapter.xml
': Permission denied
cp: can't open '/data/system/sync/status.bin': Permission denied
cp: can't open '/data/system/sync/accounts.xml': Permission denied
cp: can't open '/data/system/sync/pending.bin': Permission denied
cp: can't open '/data/system/sync/stats.bin': Permission denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permis
sion denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Per
mission denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permissi
on denied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permi
ssion denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/even[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission de
nied
cp: can't open '/data/system/dropbox/[email protected]': Permission d
enied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/dropbox/[email protected]': Permission
denied
cp: can't open '/data/system/throttle/temp': Permission denied
cp: can't open '/data/system/inputmethod/subtypes.xml': Permission denied
cp: can't open '/data/system/shared_prefs/log_files.xml': Permission denied
cp: can't open '/data/system/entropy.dat': Permission denied
cp: can't open '/data/system/batterystats.bin': Permission denied
cp: can't open '/data/system/accounts.db': Permission denied
cp: can't open '/data/system/accounts.db-journal': Permission denied
cp: can't open '/data/system/called_pre_boots.dat': Permission denied
cp: can't open '/data/system/wallpaper_info.xml': Permission denied
cp: can't open '/data/system/netpolicy.xml': Permission denied
cp: can't open '/data/system/appwidgets.xml': Permission denied
cp: can't open '/data/system/netstats.bin': Permission denied
cp: can't open '/data/system/netstats_xt.bin': Permission denied
cp: can't open '/data/system/netstats_uid.bin': Permission denied
failed on '/data/system' - Permission denied
failed on '/data/system2' - Directory not empty
failed on '/data/app' - Permission denied
mkdir failed for /data/app, File exists
failed on '/data/local/tmp/VpnFaker.apk' - Permission denied
/system/bin/sh: cannot create /data/system/packages.xml: Permission denied
Need to reboot now!
Waiting for device to come up again....
Unlock your device, a Terminal will show now, type this 2 lines, after each line
press ENTER
/data/local/tmp/onload.sh
/data/local/tmp/onload2.sh
after this is done press a key here in this shell to continue!
If the shell on your device does not show please re-start the process!
Starting: Intent { cmp=com.android.vpndialogs/.Term }
Error type 3
Error: Activity class {com.android.vpndialogs/com.android.vpndialogs.Term} does
not exist.
Press any key to continue . . .
148 KB/s (1241 bytes in 0.008s)
/data/local/tmp/script1.sh[1]: /dev/sh: not found
/data/local/tmp/script1.sh[2]: /dev/sh: not found
/data/local/tmp/script1.sh[3]: /dev/sh: not found
/data/local/tmp/script1.sh[4]: /dev/sh: not found
/data/local/tmp/script1.sh[5]: /dev/sh: not found
/data/local/tmp/script1.sh[6]: /dev/sh: not found
/data/local/tmp/script1.sh[7]: /dev/sh: not found
/data/local/tmp/script1.sh[8]: /dev/sh: not found
/data/local/tmp/script1.sh[9]: /dev/sh: not found
/data/local/tmp/script1.sh[10]: /dev/sh: not found
/data/local/tmp/script1.sh[11]: /dev/sh: not found
/data/local/tmp/script1.sh[12]: /dev/sh: not found
/data/local/tmp/script1.sh[13]: /dev/sh: not found
/data/local/tmp/script1.sh[14]: /dev/sh: not found
/data/local/tmp/script1.sh[15]: /dev/sh: not found
/data/local/tmp/script1.sh[16]: /dev/sh: not found
/data/local/tmp/script1.sh[17]: /dev/sh: not found
/data/local/tmp/script1.sh[18]: /dev/sh: not found
/data/local/tmp/script1.sh[19]: /dev/sh: not found
Almost complete! Reboot and cleanup.
Waiting for device to come up again....
/system/bin/sh: su: not found
/system/bin/sh: su: not found
/system/bin/sh: su: not found
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
I have still had no luck either manual or automatic as of yet. I did find someone with a US model and they provided there VpnFaker.apk file. If someone wants to give it a shot, here is the link.
http://forum.xda-developers.com/showthread.php?t=1886460&page=83
I had no luck with it, but, beginning to wonder if mine is cursed lol.
Note - I did find one odd thing, if I use Internet Explorer, it saves the file as Vpnfaker.zip , Firefox/Chrome saves it correct as Vpnfaker.apk . Just a heads up there because it doesnt "look" any different via Explorer. (didnt notice it until I did a DIR from DOS prompt.
I tried to the root of C:\ as well and no luck, I really think it is something with this specific model. Just a matter of what.....
Thanks for the post though.
daClaus said:
Well, I solved the problem. The whole thing worked the first time when I copied everything to C: on my hard disk. I have to admit that I have the SGPT111AT/S, but I think that doesn't make a difference. RunMe.bat and RunMe.sh are in root, the rest is in the "stuff" folder. Rooting rel. 1a worked instantly, and rooting Rel. 5 after the upgrade worked also at the first attempt. Before that I had the files on my desktop and always got the errors mentioned in the first post.
Click to expand...
Click to collapse
FINALLY!
Here is what I did.
Factory reset including wipe USB
Setup wireless & google account
Settings, Security, check Unknown Sources
Settings, Developer, USB Debugging checked, Stay Awake checked, and Allow mock locations checked.
Download attachmetn from post by k4syx from http://forum.xda-developers.com/showthread.php?t=1886310&page=31
From there, resign the vpnfaker.apk from the extracted folder from instructions http://forum.xda-developers.com/showpost.php?p=31582941&postcount=42
Then replace the vpnfaker.apk file in rootkittablet.tar and inside that rootkit.tar .
run the runme.bat, choose Tablet S,
Follow along until the point the terminal emulator loads.
From there open a new dos box , type adb shell and start from "Still in the Terminal Emulator, ignore the script error" from http://forum.xda-developers.com/showthread.php?t=1886310
Note - I attempted the backup of Backup /system (you may just skip it) but then all I got was a blank screen, and had to start over in new dos box and start over.
One thing I have learned from attempting various scripts, various methods I wanted to pass on.
1. Always factory reset after failed attempts
2. Re-extract original zip file to different location on additional attempt (I think there is something goofy with the backup files after trying to run a 2nd time)
3. Re-sign vpnfaker file after each attempt.
Hope it helps!
mikeblahblah said:
FINALLY!
Here is what I did.
Factory reset including wipe USB
Setup wireless & google account
Settings, Security, check Unknown Sources
Settings, Developer, USB Debugging checked, Stay Awake checked, and Allow mock locations checked.
Download attachmetn from post by k4syx from http://forum.xda-developers.com/showthread.php?t=1886310&page=31
From there, resign the vpnfaker.apk from the extracted folder from instructions http://forum.xda-developers.com/showpost.php?p=31582941&postcount=42
Then replace the vpnfaker.apk file in rootkittablet.tar and inside that rootkit.tar .
run the runme.bat, choose Tablet S,
Follow along until the point the terminal emulator loads.
From there open a new dos box , type adb shell and start from "Still in the Terminal Emulator, ignore the script error" from http://forum.xda-developers.com/showthread.php?t=1886310
Note - I attempted the backup of Backup /system (you may just skip it) but then all I got was a blank screen, and had to start over in new dos box and start over.
One thing I have learned from attempting various scripts, various methods I wanted to pass on.
1. Always factory reset after failed attempts
2. Re-extract original zip file to different location on additional attempt (I think there is something goofy with the backup files after trying to run a 2nd time)
3. Re-sign vpnfaker file after each attempt.
Hope it helps!
Click to expand...
Click to collapse
Thanks for the perseverance will give it a go. One question does your tablet have the sony backup and restore program on it? Mine doesn't and I cant get any of the posted apk's to run.
I did not install any seperate app, just what was built in with 4.0.3. release 5. It does prompt after a reset if I wish to restore my settings, I am assuming it is using the new options with release 5 (I dont remember this with release 1a)
Hope it helps.
tippo88 said:
Thanks for the perseverance will give it a go. One question does your tablet have the sony backup and restore program on it? Mine doesn't and I cant get any of the posted apk's to run.
Click to expand...
Click to collapse
mikeblahblah said:
I did not install any seperate app, just what was built in with 4.0.3. release 5. It does prompt after a reset if I wish to restore my settings, I am assuming it is using the new options with release 5 (I dont remember this with release 1a)
Hope it helps.
Click to expand...
Click to collapse
Ok thanks. I'm still on 1a. Notsure if can get to release 5 guess you are in the US?
I solved my problem too! Apparently it just was a matter of selecting unknown sources.
Sent from my Sony Tablet S using XDA Premium HD app
Correct, US model
tippo88 said:
Ok thanks. I'm still on 1a. Notsure if can get to release 5 guess you are in the US?
Click to expand...
Click to collapse
Good deal, enjoy the root!
kandemirb said:
I solved my problem too! Apparently it just was a matter of selecting unknown sources.
Sent from my Sony Tablet S using XDA Premium HD app
Click to expand...
Click to collapse