Related
Noticed that there weren't any tools which rooted the Sensation and overclocked for the Mac platform, so just made a simple .command file based on the work of the Devs on here.
Special thanks goes out to teamwin and Utking;
with thanks to eugene373, idanfima, coolbho3000 and wisefire (sorry if I have forgotten any!!)
Pre-requisites
- USB debugging enabled and usb connection set to charge only.
- S-ON
- A Mac OS computer
- more importantly a HTC Sensation (any model)
Instructions
Step 1. Unzip TempRoot.zip to your Documents folder (it should be "/Documents/TempRoot"), if you want to overclock skip to step 3 otherwise follow step 2 to run root without overclock. MAKE SURE YOU RENAME YOUR FOLDER TO "TempRoot" - I will fix this shortly!!.
Step 2. Restart your device.
Step 3. Run the Fr3voMacSTART.command file.
Step 4. Copy the correct kernel file for your kernel into the TempRoot directory and press enter.
Step 5. Now your device should be rooted and overclocked!
Step 6. Profit.
Link to latest TempRoot.zip:
http://www.multiupload.com/FBS0R85ZVS
28/7/2011
v0.14
- Overclocking should now work, please follow instructions in the command file.
- Added custom overclocking option
- Spring cleaning of script .
27/7/2011
v0.13 - http://www.multiupload.com/2QYEMNXMF0
- Overclock and script are working perfectly for me now...
- All feedback still appreciated!!
v0.12 - http://www.multiupload.com/HWZ5VIF4M9
- Tidied up the script, exploit should work now
- Having problems with OC modules and inserting still... Looking into this!
26/7/2011
v0.11 - http://www.multiupload.com/R80EXFI0WH
- Changed the scripts, should work now. Please unzip to Documents/TempRoot for now.
v0.1 - http://www.multiupload.com/D0XCLEP3B5
- Release
Please leave any feedback , enjoy.
I don't think it works, and i tried all sorts of things to make it work, wish i could tell you why so as to help you better, thank you for trying to show us mac users some love though.
Thanks for your reply, sorry but could you be more specific as in it won't root or it won't overclock?
EDIT - should work now, please give me feedback. Tested working fine at 1.8ghz on my HTC sensation .
Well at first I just double clicked it to launch it and I said permissions were wrong, so I had to chmod it so I could make it an executable and then after every line it file not found so no root or overclock.
Sent from my HTC Sensation 4G using XDA Premium App
could you try the updated script in the op please . need to save the dir to documents/temproot just for consistency .
Same problem i got with my mac root, if only i had a mac myself
Sent from my overclock'ed Sensation
Thank you soooo much for this tool but please can you straight the instructions ?
1) in the file TempRoot / Drag the overclock module here - we put path to proper OC module (?)
2) we click command at one of the folders
that's it ?!
I seriously don't get it at all.
Why drag OC module to text file which isn't mentioned at the command lines ?
jackolus said:
Thank you soooo much for this tool but please can you straight the instructions ?
1) in the file TempRoot / Drag the overclock module here - we put path to proper OC module (?)
2) we click command at one of the folders
that's it ?!
I seriously don't get it at all.
Why drag OC module to text file which isn't mentioned at the command lines ?
Click to expand...
Click to collapse
Will do, updating first post as we speak .
no matter what I try I always get permissions error,even as admin.
ok so i tried the new script and nothing it doesn't work, it seems to have a problem when it gets to the insomod portion of the code
This is what i get during the command........
975 KB/s (9704 bytes in 0.009s)
Locating access point...
Exploit area found. Please wait.
The exploit has failed.
remount succeeded
mkdir: can't create directory '/vendor/bin': File exists
chown: unknown user/group root:shell
3869 KB/s (1448982 bytes in 0.365s)
3084 KB/s (26324 bytes in 0.008s)
3818 KB/s (1120536 bytes in 0.286s)
chown: unknown user/group root:shell
chown: unknown user/group root:shell
chown: unknown user/group root:shell
ln: /system/xbin/su: File exists
ln: /system/bin/su: File exists
ln: /system/xbin/busybox: File exists
ln: /system/xbin/sqlite: File exists
2682 KB/s (196640 bytes in 0.071s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
cannot stat '8x60_oc_g9cef70d.ko': No such file or directory
cannot stat '8x60_oc_ga76ba0d.ko': No such file or directory
cannot stat '8x60_oc_gae358b5.ko': No such file or directory
1034 KB/s (5828 bytes in 0.005s)
cannot stat '8x60_oc_ge52b0af.ko': No such file or directory
cannot stat '8x60_oc_gfbbd430.ko': No such file or directory
cannot stat '8x60_oc_g6d6a25c.ko': No such file or directory
insmod: can't read '/data/local/tmp/8x60_oc_g9cef70d.ko': No such file or directory
insmod: can't read '/data/local/tmp/8x60_oc_ga76ba0d.ko': No such file or directory
insmod: can't read '/data/local/tmp/8x60_oc_gae358b5.ko': No such file or directory
insmod: can't insert '/data/local/tmp/8x60_oc_gb7a86da.ko': invalid parameter
insmod: can't read '/data/local/tmp/8x60_oc_ge52b0af.ko': No such file or directory
insmod: can't read '/data/local/tmp/8x60_oc_gfbbd430.ko': No such file or directory
insmod: can't read '/data/local/tmp/8x60_oc_g6d6a25c.ko': No such file or directory
usage: sleep seconds
Script is working but doesn't bring any effects. On 1.8ghz quadrant score is still 2100
I think problem is caused by unable load busybox - it's the only fail in terminal
EDIT:
OK I modified code a little and worked - at 1728mhz my Linpack max score is 89.96 but quadrant go nuts and benchmark takes forever !
There's some problems with performance becouse at heavy stress setcpu backs to 1128mhz automatically.
I will test it how battery handle, I wish it would be better becouse of scaling
Thanks for this thread
Ah brilliant, care to share what code you modified to get it to work? I've spent all this morning trying to get overclock to work all the time...
I get SU no problem.
everything was working fine but before it can finish my phone freezes and shuts off, during the waiting for kernel to update part
tw33k8opr0of said:
everything was working fine but before it can finish my phone freezes and shuts off, during the waiting for kernel to update part
Click to expand...
Click to collapse
you are trying to use an overclock to high for your phone ... try again at a higher voltage or lower frequency!
thats impossible if i have had my phone at 1.8 using the windows method for over a week i just wanted to try the mac method so if my phone would freeze like it did once before i didn't have to borrow my sisters laptop, I've tried all of the over clocks and my phone works fine on all of them, but for some reason it doesn't work with this method for mac, i thought it could be that my phone couldn't handle it and i went to try it on my sisters computer and it worked fine on windows about 10 minutes ago.
Updated first post. I made a mess in the command with regards to where files are located so please MAKE SURE YOU RENAME YOUR FOLDER TO "TempRoot" - I will fix this shortly!!
Directory structure should be "/Documents/TempRoot"
Thanks and enjoy .
thanks for the effort but the script is still faulty....no such files...etc....why do u have adb in your script?...never noticed it in the other mac script
MAKE SURE YOU RENAME YOUR FOLDER TO "TempRoot", Directory structure should be "/Documents/TempRoot"
Adb is necessary... Please ensure the above is followed until I have fixed the script to work in any directory (simple fix!! I'm just not in the office at the moment, back on my PC - thank god!).
so i tried the new script, every option on the over clock menu and......
Locating access point...
Waiting for device to become ready
Device is Ready
/ remounted as Read/Write
Creating directory
remount succeeded
Installing bin's
---Installing sqlite3
4229 KB/s (1448982 bytes in 0.334s)
---Installing su
2775 KB/s (22228 bytes in 0.007s)
---Installing busybox
3676 KB/s (1372660 bytes in 0.364s)
Done installing bin's
/ remounted as Read-Only
Installing apk's
---Uninstalling old Superuser if it exists
Success
---Installing Superuser
3142 KB/s (196640 bytes in 0.061s)
pkg: /data/local/tmp/Superuser.apk
Success
Done installing Superuser
1. No Overclock
2. 1.5Ghz Overclock Undervolted
3. 1.62Ghz Overclock Undervolted
4. 1.62Ghz Overclock
5. 1.8Ghz Overclock Undervolted
6. 1.8Ghz Overclock
Please choose an overclocking level [1 - 6]
3
9 KB/s (224 bytes in 0.022s)
Place relevant kernel module in TempRoot directory, then press enter
Pushing kernel module to device
cannot stat '8x60_oc_g9cef70d.ko': No such file or directory
cannot stat '8x60_oc_ga76ba0d.ko': No such file or directory
cannot stat '8x60_oc_gae358b5.ko': No such file or directory
610 KB/s (5828 bytes in 0.009s)
cannot stat '8x60_oc_ge52b0af.ko': No such file or directory
cannot stat '8x60_oc_gfbbd430.ko': No such file or directory
cannot stat '8x60_oc_g6d6a25c.ko': No such file or directory
Waiting 5 seconds til kernel has updated
Inserting attributes to kernel
insmod: can't open '/data/local/tmp/8x60_oc_g9cef70d.ko'
insmod: can't open '/data/local/tmp/8x60_oc_ga76ba0d.ko'
insmod: can't open '/data/local/tmp/8x60_oc_gae358b5.ko'
error: device not found
error: device not found
error: device not found
Overclocking profiles complete, please navigate to setcpu and clocks should be automatically detected
logout
My SE Xperia Pro MK16i was previously rooted using DooMLoRD's Easy Rooting Toolkit. The software has just been upgraded to version 4.0.2.A.0.62 which then resulted in the complete loss of Root Access. I tried to re-root using DooMLoRD v4, but without success. This resolved the problem after the last software upgrade, but this time it has not worked and now I am really stuck. Any help would be much appreciated.
The script reads as follows:-
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
866 KB/s (23060 bytes in 0.026s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
3511 KB/s (1075144 bytes in 0.299s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
53 KB/s (439 bytes in 0.008s)
--- Free space on /system : 156260 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Thanks
to me it's the same
i don't find the form to root my phone mk16 with the new version, and i read in too much sites and i dont find anything.
Hi,
Sorry that you are having the same problem rooting version 4.0.2.A.0.62.
I have ended up using WotanClient to flash the software back down to version 4.0.2.A.0.58 to enable me to re-root my Xperia Pro with DooMLoRD v4. Flashing wiped the phone's settings as expected, and losing root meant that I could not make backups of everything before going down this path. It took me quite a while to reconfigure the phone even though all the apps were easy to re-download from my Google account at Android Market. I was hoping that OTA Rootkeeper could then be used to help upgrade to version 4.0.2.A.0.62, but the filesystem does not seem to support root protection. Creating a separate Ext3 partition on the SD card did not make any difference and I cannot find any other information on how to make it work. This is a real pain.
Anyway, at least I now have a rooted phone with the previous software and Titanium Backup is functioning once again. I have used Titanium to freeze the update service in order to stop the constant OTA notifications regarding the availability of the software version 4.0.2.A.0.62. There is no way that I shall upgrade unless somebody discovers a straightforward exploit to root the new version. I am now beginning to doubt whether this will happen anytime soon.
I downgraded my SE Xperia Pro to 4.0.2.A.0.58 and rooted it. Will I lose root if I update OTA? Also, will I lose my apps and settings?
I used to backup my rom data via ClockworkMod on my HTC Desire Z and restore it after an update, but there's no CWM for the Xperia Pro.
SE Xperia Pro OTA Software Update
My understanding is that you will not lose root or settings and apps with an OTA software update for the Xperia Pro. However, for some reason the update failed when I tried using this method to upgrade from version 4.0.2.A.0.58 to version 4.0.2.A.0.62. I am still looking for a solution to this problem. Please post here if you are successful.
I have flashed my phone over wotan server to. 42, after that I have rooted over the flash tool, and instaled titanium backap pro and uninstaled all necesery apps (facebook...moxier, fun and downloads and others) and try to upgrade to .62, and phone says me that is unable to upgrade software... Phone works great, but why I cant upgare software? Is it because I uninstaled some sistem apps which doesnt have any thing whit system works?
Sent from my MK16a using XDA
SE Xperia Pro OTA Software Update
I did exactly the same and had identical results. The fact that we have both uninstalled some unnecessary apps using Titanium and then been unable to upgrade using the OTA software update method could be the reason why it does not work. It probably counts as having modified the system folder. However, I am not prepared to go through all the trouble of re-flashing my phone in order to reinstall the missing apps and then try again.
The best solution would be if somebody could find an exploit to root version 4.0.2.A.0.62 directly. I would then simply upgrade the phone using SE PC Companion and avoid all the other problems.
Xperia pro software
Now i flashed again my phone to .42, roted, and upgradet sucsefuly to .62, root is still here, and now i will remove all necesery apps.
So, first flash than root, than upgrade, and make your phone like you want.
Hi guys, I have bought a new Xperia Pro MK16i with 4.0.2.A.0.58, not rooted yet. I get a notification about availability of OTA update to 4.0.2.A.0.62. What are the best steps to root my phone? Note: I want to uninstall some SE apps too.
muchotravka said:
Hi guys, I have bought a new Xperia Pro MK16i with 4.0.2.A.0.58, not rooted yet. I get a notification about availability of OTA update to 4.0.2.A.0.62. What are the best steps to root my phone? Note: I want to uninstall some SE apps too.
Click to expand...
Click to collapse
Hey! Don't update your phone until you root it (I'm sure you already know this). To root it, you can use this method: http://forum.xda-developers.com/showthread.php?t=1320350
It's very easy to follow.
Before you do it, though, you'll need to install the ADB (Android Debug Bridge) drivers, which you can find here, in Sony's website: http://developer.sonymobile.com/wportal/devworld/downloads/download/sonyericssonxperiaproxperiarayxperiarayso-03cdrivers?cc=gb&lc=en. Or you can also install it using a tool called SDK Manager (that's how I installed the driver). An easy tutorial: http://www.invialgo.com/2011/install-adb-for-android-phone/
After you root it and before you make any changes (unnistalling system apps...), update via OTA (not through PC Companion!) to firmware .62 and after that's done, you should still have root and will be able to do what you want with your XPro. It's very easy.
Is using the wotanclient the best way to downgrade to be able to root my phone, I have already upgraded the phone and it is not unlocked/modded in anyway at present.
Suition Shinobi said:
I downgraded my SE Xperia Pro to 4.0.2.A.0.58 and rooted it. Will I lose root if I update OTA? Also, will I lose my apps and settings?
I used to backup my rom data via ClockworkMod on my HTC Desire Z and restore it after an update, but there's no CWM for the Xperia Pro.
Click to expand...
Click to collapse
I just tried to downgrade my phone from .62 to .58 using WotanClient.
For some reason there was an error during firmware flashing
[SSL] Error 12152
Error: file header write failed!
CUST file write failed
and the whole process just stopped. I tried to restart but the WotanClient
said no credit which means the Euro1.99 i just bought was gone with the error
This is so disappointing. I tried to recover my phone which is now just a piece of brick by installing a new software (repair phone) via it SonyPCcompanion but it seems like the PCcompanion couldn't connect to
the phone.
Help please!!!
donno what to do now. if I try to flash it again with WotanClient, will it work? should I go to version .58 or .42?
Can you Please tell me how to do that?
MutleyB said:
My understanding is that you will not lose root or settings and apps with an OTA software update for the Xperia Pro. However, for some reason the update failed when I tried using this method to upgrade from version 4.0.2.A.0.58 to version 4.0.2.A.0.62. I am still looking for a solution to this problem. Please post here if you are successful.
Click to expand...
Click to collapse
Can you Please tell me how to Downgrade from 4.0.2.A.0.62 to 4.0.2.A.0.58?
Flash it with flashtools using a ftf image?
Sent from my MK16i using XDA
I know this is a very old post, but it describes exactly my problem.
I recently bought the Xperia Pro, and it has version MK16i 4.0.2.A.0.62
I tried to root it but it gave me the error as described in the first post.
I assume there is no real solution, so I am asking for advice if it is worth the trouble by downgrading, rooting and then upgrading again?
Currently the phone has locked boatloader.
Honestly, all I want to do is to get root access so I can disable some pre-installed apps from "Disable Service"
Any advice is appreciated:good:
EXPLOIT NO LONGER WORKING DUE TO OTA UPDATE. BE WARNED.
Thanks to beaups for his exploit!
Download the zip file below, unzip it somewhere, run root.bat with your phone plugged in and usb debugging enabled. Currently this is for windows only.
Includes a fully working su binary and Superuser.apk, make sure to update the su binary the first time you run SuperSu!
Follow the instructions on the screen, they are very simple, only one thing to do!
Download:
http://www.gigashare.in/738af
HELP SECTION:
After you are rooted, I strongly suggest you unlock your bootloader immediately!!
http://briefmobile.com/how-to-unlock-att-one-x-bootloader
Make sure HTC sync is NOT RUNNING (down in system tray)
Make sure phone is set to "charge only" and usb debugging is enabled!
Make sure Wifi is enabled and connected! (seems to help, but not required)
If you are stuck at "waiting for device to reboot" for a long time or you get "/data/local.prop was not created, exit the script, try again." followed by lots of junk, reboot your phone and push your clock forward two days, reboot, and try again.
If the update fails to check for updates, reboot your phone and push your clock forward two days, reboot, and try again.
usb drivers, if you need them: http://binary100100.googlecode.com/files/HTCDriver3.0.0.007.exe
You're the man and you know this...
Sent from my HTC One X using Tapatalk 2
Damn. I'm already rooted yet disappointed I can't be part of this . Lol well Friday I will be donating like I said I would. Good job
Sent from my HTC One X using xda premium
Great work! Wonder how long this will last.
Sent from my HTC One X using xda premium
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Pumpiron579 said:
Pure awesomeness, worked make sure you let it reboot a few times, I think mine rebooted 3 or 4, I just left it in the cradle. I now have root
Click to expand...
Click to collapse
should only reboot twice
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
StrykerGT said:
I got this error when I tried it.
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Any suggestions?
Click to expand...
Click to collapse
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
designgears said:
should only reboot twice
Click to expand...
Click to collapse
Is that taking into account the unstableness and the potential for it to spontaneously reboot on its own?
Mine doesn't get past "waiting for device to reboot"
Thanks for the script sir!
skatin707 said:
Mine doesn't get past "waiting for device to reboot"
Click to expand...
Click to collapse
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
designgears said:
should only reboot twice
Click to expand...
Click to collapse
mine rebooted once after checking for update, but when it ran all the code, prior to rebooting, i got errors in the code. looked and no SU on my phone. not sure what i did wrong. didn't reboot the first time, so i pushed the date ahead two days and then it did with the code that everyone is reporting.
designgears said:
well, its waiting for the update process to create files, once it does it will reboot, if it sits there to long, reboot your phone and try again
Click to expand...
Click to collapse
I'll keep waiting, it hasn't even been 10 minutes.
hahaha...that was magical!!!! works!!!!
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
did you run the updater on the phone? if it is completed or still spinning after a few min just reboot and try again.
skatin707 said:
I'll keep waiting, it hasn't even been 10 minutes.
Click to expand...
Click to collapse
I set my date ahead and turned on my WiFi, checked for updates and it rebooted right away.
love you guys.
designgears said:
check out the bolded part
kick the date forward two days and reboot your phone, run the script again
you might have to do that a couple times...
Click to expand...
Click to collapse
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
beppomarx said:
heres what i get... i did get the reboot after checking for updates though.
Exploit by beaups, script by designgears
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
32 KB/s (334 bytes in 0.010s)
rm failed for /data/data/com.redbend.vdmc/lib/libvd*, No such file or directory
Go to Settings, ATT Software update, check for updates.
Waiting for device to Reboot...
/data/local.prop was not created, exit the script, try again.
remount failed: Operation not permitted
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file sy
stem
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rm failed for /data/local.prop, Permission denied
Done! Rebooting...
Press any key to continue . . .
Click to expand...
Click to collapse
reboot and try again! push your clock up two days.
StrykerGT said:
Thanks! I didn't read the message. I'm an idiot.
Rooted! Woot!
So the next step is to follow these instructions right?
http://forum.xda-developers.com/showthread.php?t=1671396
Click to expand...
Click to collapse
YUP! but there is a one click for that too
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'm trying to root my SE WT19i, but it's being impossible. I´ll tell you all what I've tried so anyone can see any solution:
I followed this thread for downgrading from andoid 4.0 to 2.3. First, flashed the phone with the 4.0.2.A.0.62 version.
Then, for installing adb drivers, tried installing PC Companion, but it wasn't able to install any driver. So, I searched and installed the drivers this way (installing the “Google USB Driver” package).
Then, following the first thread, downloaded the DooMLoRD's Easy Rooting Toolkit [v4.0] , and followed the instructions (USB debugging, unknown sources, even the 10 minutes screen timeout). Don't worked.
So, I flashed again the phone, with the 4.0.2.A.0.42, and tried one more time (and changed the options again according to the script's instructions). Don't worked.
Same for 4.0.2.A.0.58, that is the version that runs my phone now.
Then, I tried this method, by using the Super One Click. That program prompted me to install drivers, so I installed all I was prompted, but don't worked any exploit method of it (yeah, I know the other method "maybe won't work in Android 2.3 and higher", but I had to try).
As there were new drivers installed, I thought the DoomLord's script now, finally, will be able to work, so I tried again. Well, the console output is this (and it is generated in a few seconds...)
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
--- pushing zergRush
cannot open 'files\zergRush': No such file or directory
--- correcting permissions
--- executing zergRush
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
2262 KB/s (1075144 bytes in 0.464s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
53 KB/s (439 bytes in 0.008s)
--- Free space on /system : 172928 bytes
--- no cleanup required
--- copying busybox to /system/xbin/
/system/xbin/busybox: cannot open for write: Read-only file system
--- correcting ownership
Unable to chmod /system/xbin/busybox: No such file or directory
--- correcting permissions
Unable to chmod /system/xbin/busybox: No such file or directory
--- installing busybox
/system/xbin/busybox: not found
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
--- rebooting
ALL DONE!!!
Press any key to continue . . .
Click to expand...
Click to collapse
Well... the "files\zergRush" actually exists. I haven't modified anything in the files more than unzipping them. I don't know why don't recognise it, but because of that, I downloaded directly the zergRush script and replace it, but didn't worked either even when the DoomLord's script found it. I've also tried to unzipping it directly in C:\, but the results are the same.
I'm using Windows 7, but have tried to run in compatibility mode with xp sp3, and with admin permissions without results.
I don't know what more to do, I think I've tried all. Can anyone help?
PS: I was going to post this in the thread of DoomLord's script (that is the correct place for this, I think), but I'm not allowed yet, sorry.
Accordingly to the rules, bumping thread so it can be seen by anyone who could know about it.
I'm currently trying to contact someone in the IRC, but it'is a bit dead... :-/
install stock rom again and try again
That's already done. Several times. Now, I think the problem is more of the computer for not founding the zergRush script than of the phone. I need a way for getting the script working, but don't know how to...
--------------------------------------------------------------------------------------
Edit: I give up. I can't have my phone useless for more time (because is stupid reconfigure it each time you flash it...). I'm interested no more in rooting the phone. Thanks to all who have read this thread.