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.
Related
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:
Hey guys this is my first time trying to root so i really need some help doing it. When ever i use oneclickroot i go through all the steps that it says to do. When its in the processing of rooting this comes up
*server not running*
*daemon not running. starting it now*
*daemon started successfully*
Getting temp root
[1] Segmentation fault app_process /dev...
cannot create /data/local.prop: permission denied
deleting all yo stuff
mount: Operation not permitted
46 KB/s (4292 bytes in 0.090s)
Coping files onto phones...
failed to copy 'su' to ' /system/xbin/su': Read-only file system
failed to copy 'superuser.apk' to '/system/app/Superuser.apk': Read-only file system
failed to copy 'busybox' to '/system/xbin/busybox':Read-only file system
failed to copy 'remount' to '/system/xbin/remount': Read-only file system
Setting permissions..
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/remount: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
link failed Read-only file system
Installing busybox...
/system/xbin/busybox: not found
Cleaning up files...
rm failed for /data/local/zergRush, No such file directory
"You should have root!"
Press any key to continue...
When i check my phone i dont see any superuser or anything saying that have been rooted. Am I missing something that I need for this to work? I am using the Samsung Galaxy Prevail.
Help please.
you have all the proper drivers installed? it mentions to try it a few times without your SD card and in airplane mode.
I installed the Samsung drivers for the phone thats all. What else do I need. I tried it without th SD card but not in airplane mode yet.
If you installed the samsung drivers you should be good, make sure the phone is in USB debugging mode and let it install any drivers that come up.
I just tried to root it with usb debugging on, airplane mode on and the SD card out. The thing that i saw was different was it showed Error: Device not found 4 times. This rooting thing is really fustrating me lol just saying . And do I need to install anything else to do this?
you sure you have the proper drivers installed? oneclick isnt recognizing your phone being connected to your computer, hence device not found. I'd reinstall the proper drivers again, maybe install Samsung Kies, and let the device install some drivers will on usb debugging mode and try again.
follow the link below...
http://androidforums.com/galaxy-pre...oot-samsung-prevail-replenish-shabbyfied.html
Ok i will reinstall the samsung drivers. What does Operation not permitted mean and Permission Denied? And its not coping the files to my phone.
Rooting Samsung Galaxy Prevail Gingerbread 2.3.6
.na
check it out. Now, for the rooting procedure on the Galaxy Prevail running Android 2.3.6, read on!
I. Before You Begin
1. This procedure roots your device by flashing a prerooted ROM, which means you will most definitely lose all your data; so back up what’s important before you proceed.
2. Make sure you have the necessary drivers installed before you proceed; if you aren’t sure, download the package in the next section and run SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from it before you proceed.
II. Necessary Downloads
III. Rooting the Galaxy Prevail
1. Put your device into Download mode. To do this, with your device powered down, press and hold the Camera, Volume Down and Power buttons until you “Downloading” on your device’s display.
2. Connect your device to your Windows PC.
3. Extract the FF19_ROOTED.zip you downloaded above to a folder on your desktop.
4. From the extracted folder, double-click on odin Multi_Downloader_v4.43to run it.
5. Load files from the extracted folder on to Odin by clicking on the relevant buttons as you see in the screenshot below.
6.Click start let it go by itself trust me it works i did mines
7.Now you rooted and have cwm pick up a rom for it
8.when everything is done you like it
Roms for this phone only
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
Hello
I am new / a noob... [For Below I have highlighted what the issue is in RED on the code part of the issue]
I have looked on this site for three days running. I have made steady progress towards rooting my HTC Sensation XE, as a noob I have download alsorts of unecessary things and misunderstood alot of what is describe but I have done well so far - I believe.
Brief run down of things done:
- Installed all required drivers
- used this awesome guide: http://forum.xda-developers.com/showthread.php?t=1660831][All In One][Guide] How To Root...
- Follwed guide and currently down at Step 2.3 - open extracted zip folder and click runme. thats all. (if experience any daemon hanging problems pls install htc sync and plug in phone so drivers are installed. once done delete htc sync and repeat root procedure) PC will open a cmd screen with prompts that you need to follow. The app does rest... So its nice and easy
Ok so to the point of this thread.
I downloaded DooMLoRD's root.zip doo dar (Lack the correct terminollogy - Im a noob so handicap is allowed)
Extracted all files
Opened up the 'Run Me.exe'
A cmd pops up, with info of preparation before hiting any key.
I hit the any key and below is what I get:
--- STARTING ----
--- WAITING FOR DEVICE
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
1443 KB/s (23060 bytes in 0.015s)
--- 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.
[-] Not a 2.2/2.3 Android ...
--- 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
862 KB/s (1075144 bytes in 1.216s)
--- correcting permissions
--- remounting /system
mount: permission denied (are you root?)
--- checking free space on /system
0 KB/s (439 bytes in 1.000s)
df: /mnt/secure/asec: Permission denied
df: /data/DxDrm/fuse: Permission denied
--- Free space on /system : 87% bytes
test: 87%: bad number
--- NOT enough free space on /system!!!
--- making free space by removing Google Maps
--- 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/bin/sh: /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, No such file or directory
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 . . .
This restarts my phone but nothing else.
I have the su apps on my phone, I have root explorer too.
I've looked in the \system\bin and \system\xbin for an su or something titled su or su binary
Can't find anything so I am worried about that. - does my phone have an su?
Also from the code above it mentions 'cannot open for write: read-only file...' how do I change this if this is the source of the problem?
If not, further down it mentions not being able to copy 'superuser.apk' over - do I remove this from the extracted files and replace with a current version?
Please can you experts help me out - I have searched the forums but they only resolve other makes / models.
Additional info is I didn't S-OFF as I couldn't understand what to do, but skipping that step I still got this far so unsure if I needed it.
I appolagise for the lengthy post but it should help shortlist possible problems down abit.
Thanks for reading.
Dude the guide u used is for sensation xl and it is not suitable for sensation/xe/4g
Basicly I think u want to root it phone so plzz give the bootloader info
Arey u unlocked bootloader?
Hboot?
Etc if u hve unlocked your bootloader
Thn install a custom recovery and install su.app for details search at development sectors of HTC sensation
U can use sensation files for HTC sensation/xe/4g but cannot use sensation xl files
HIT THANKS IF I HVE HELPED YOU
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
U may also get some hlp.from here
http://forum.xda-developers.com/showthread.php?t=1631861
HIT THANKS IF I HVE HELPED YOU
shrex said:
Dude the guide u used is for sensation xl and it is not suitable for sensation/xe/4g
etc....
Click to expand...
Click to collapse
Whilst waiting for a reply I had a browse through the search again and realised exactly what you told me.
used HTCdev and I am unlocked via bootloader.
so if I can't use DooMLoRDs stuff I decided to find others.
I found this: http://forum.xda-developers.com/showthread.php?t=1497404
I download his zip but not doing anyhting yet.
All i bloody want to do is customise system sounds and its insane how much you gotta do just to get it haha. But yeah I just need it rooted and an updated su so I'll go ahead with the above downloaded zip and I'll see what happens.
Thanks for replying you were helpful appreciate it
The link wch u hve mentioned is grt u can go ahead with that but b sure u read everything n fill the prerequisites
HIT THANKS IF I HVE HELPED YOU
HTC Inspire 4G - AT&T
Android - Stock GB 2.3.5 + HTC Sense 3.0
Build - 3.20.502.52
PC OS - Windows XP Pro SP3
Method - Easy Ace Root Tool
Noob - Yes
Problem - Bootloader unlock successfully achieved, but installation of BusyBox, Clockworkmod, and SuperUser interrupted during process.
Text from Post-Unlock on shown below. Trouble Areas Colored Red
Summary of Problem according to Tool - "Parameter Format not correct," "Read-Only file system," and "No such file or directory"
USB Debugging and Unknown Sources enabled when errors occur
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
< waiting for device >
sending 'recovery' (3554 KB)... OKAY [ 0.641s]
writing 'recovery'... OKAY [ 0.953s]
finished. total time: 1.594s
rebooting...
finished. total time: 0.297s
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Make sure that USB debugging is enabled and charge only is set as default
Achieving Temp Root
cannot stat '/tools/tmp/fre3vo': No such file or directory
Unable to chmod /data/local/tmp/fre3vo: No such file or directory
/data/local/tmp/fre3vo: not found
Pushing Busybox, SU and Superuser
1 KB/s (536 bytes in 0.312s)
1829 KB/s (380532 bytes in 0.203s)
1906 KB/s (1372660 bytes in 0.703s)
Trying to gain Perm Root
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
failed to copy 'tools\su\su' to '/system/bin/su': Read-only file system
failed to copy 'tools\su\Superuser.apk' to '/system/app/Superuser.apk': Read-onl
y file system
Unable to chmod /system/bin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
FIND: Parameter format not correct
rm failed for EasyAceRoot.cmd, No such file or directory
Perm Root achieved...
I too am looking for the answer. I'll edit this post if I find something
If CWM would install, that wouldn't be a problem
Scozzar said:
I too am having this issue at the moment. The bootloader is unlocked, but I will not get perm root, even though it says it was achieved...
EDIT: Turning off Fastboot yields different results. But still no SuperSU.
EDIT2: I GOT IT! Basically, I downloaded the latest SuperSU .zip off XDA, put it on the phone, then flashed it in CWM. SuperSU now appears as an app!
Click to expand...
Click to collapse
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Prestige0813 said:
I'll try turning off fastboot, but I can't get CWM to install at the moment either. SuperSU and Busybox also can't install.
Again, I'll try turning fastboot off and see how it behaves.
Click to expand...
Click to collapse
What have you done? Also, you can't turn off fastboot; it's a mode selected from the bootloader. Do you mean ADB? Turning that off won't do anything either, other than making your phone's system inaccessible from the computer.
Scozzar said:
Fastboot, as in the check box in the stock ROM. You can't get into bootloader with it on. Also, if I was able to flash a new ROM, does that mean busybox is installed?
Click to expand...
Click to collapse
Depends on the ROM.
Scozzar said:
V2 Oxygen JB is what I'm using.
Click to expand...
Click to collapse
Er, I don't know for every ROM. If it's a custom ROM, probably. If you're rooted (and again, if you're using a custom ROM, you probably are), you can always install it from the play store.
Update:
First off, I've already downloaded the SuperSU App from Google Play, and it's failed to obtain root abilities, so a perm root is not being acheived.
Also, I've downloaded the latest SuperSU via PC, and it's ready to go once I manage to successfully install CWM (however, if the Ace Root Kit succeeds, then using CWM to install root isn't a needed method)
I've tried continuing the process with the Fastboot setting disabled, and I didn't see any difference in the end result. It seems that recovery is successfully written, but it doesn't succeed in installing SuperSU, CWM, or busybox.
On another note, I've downloaded the busybox installer app from Google Play, and it states the phone is rooted; but runs into errors when I attempt to install (regardless of the version I select). I've run two root checking apps, and both say that the phone is not rooted.
In short, All I've been able to achieve is getting the Boot Loader unlocked.
Can you flash recovery manually from fastboot?
New Update
I just found that CWM is in fact installed. I did not realize until just now that from the HTC bootloader I had to select recovery to access it.
I placed the SuperSU.zip on the phone and installed it via CWM, as scozzar had suggested, and the phone is now rooted (verified by two root checking apps)!
From there I installed busybox via Google Play with no hiccups.
I apologize for not trying this sooner I hope that others find success. The Inspire's a great phone, and now I've made mine even better!
Yess
bananagranola said:
Can you flash recovery manually from fastboot?
Click to expand...
Click to collapse
Yes! here is the tutorial
1- Download Android.zip and unzip it
2- make a folder called "Android" in C:/ like that: C:/Android.
3- put inside of the folder Android the files: adb.exe, fasttboot.exe, AdbWinApi.dll and the recovery.img
4- go to cmd and write:
cd \Android
fastboot flash recovery recovery.img
READY! now you have a CWM Recovery
Sorry for my bad english