Wtf its not rooting? - AT&T, Rogers HTC One X, Telstra One XL

I just tried rooting my phone and it keeps saying unable to copy the file on everything and it`´s not permitted.... I tried rooting with some old guides I found because I was checking my phone and I´m still on android version 4.03 and builder number 1.85...it would just not do anything not It´s not letting me install any kind of apps in the app store, but everything else is working. So i tried the 2.02 version and it doesn´t give me the 11111111 code at the end. Is there something wrong with the phone or could it be the drivers? All the guides I found gave the drivers that installed them on their own.
Also could it be that I´m in mexico and the phone was sent from the us? its the at&t one. I´m so lost now that I had the guts to root it. -.-

LocDeMty said:
I just tried rooting my phone and it keeps saying unable to copy the file on everything and it`´s not permitted.... I tried rooting with some old guides I found because I was checking my phone and I´m still on android version 4.03 and builder number 1.85...it would just not do anything not It´s not letting me install any kind of apps in the app store, but everything else is working. So i tried the 2.02 version and it doesn´t give me the 11111111 code at the end. Is there something wrong with the phone or could it be the drivers? All the guides I found gave the drivers that installed them on their own.
Also could it be that I´m in mexico and the phone was sent from the us? its the at&t one. I´m so lost now that I had the guts to root it. -.-
Click to expand...
Click to collapse
You will have to use the 1.85 method which is best. To use the 2.20 method you would need to download the 2.20 update. But best to use the 1.85 method I think. I'll see about fetching a link.
Here ya go. http://forum.xda-developers.com/showthread.php?t=1709296
I do not suggest rooting/unlocking bootloader If it seems too difficult.
Sent from my One X using xda app-developers app

I don¨t understand the su and adb thing it asks me... I saw in a post that there is still a one click rooter, which is what I was using and I get the error of
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
I get a longer message, but it goes too fast and closes the cmnd window....I will be trying the going to the future for 2 days lol see if that does anything

exad said:
You will have to use the 1.85 method which is best. To use the 2.20 method you would need to download the 2.20 update. But best to use the 1.85 method I think. I'll see about fetching a link.
Here ya go. http://forum.xda-developers.com/showthread.php?t=1709296
I do not suggest rooting/unlocking bootloader If it seems too difficult.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
The 2.20 root will work on any of them...it exploits the same thing ...

LocDeMty said:
I don¨t understand the su and adb thing it asks me... I saw in a post that there is still a one click rooter, which is what I was using and I get the error of
Click to expand...
Click to collapse
The 1.85 one-click method no longer works (hasn't for a long time). The one linked by exad above is the only working method that is specific to 1.85.
But as stated by kittens above, the X-factor exploit not only works on 2.20, but should also work on previous firmwares. Try either the toolkit, or the "manual" X-factor method.
If you don't understand what SU and adb are, you probably shouldn't mess around with any of these things. Do a lot more research and learning, before you get rooting.

Ah I wasn't sure that the X Factor method works on 1.85. Whenever I suggest it people reply that it says explicitly that it doesn't work on 1.85. Though, when I read it, I did not notice that. In any case, *shrug* there ya go op. Good luck! Read lots.
Sent from my One X using xda app-developers app

Aye I just tried it with a one click installed and got a Supersu app...when I try opening it, it says that "there is no su binary installed, and the super su cannot install it. This is a problem"???

LocDeMty said:
Aye I just tried it with a one click installed and got a Supersu app...when I try opening it, it says that "there is no su binary installed, and the super su cannot install it. This is a problem"???
Click to expand...
Click to collapse
I think that message it gave you was kinda clear there is no Su files or binary installed to give you root access..

I see...so do I have to do it again? I don't get the su going in adb...I tried posting there, but it doesn't let me post >.<

[*]
[*] X-Factor: HTC One X Root Exploit (Windows version)
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Greets/thanks to Michael Coppola
[*]
[*] Before continuing, ensure USB debugging is enabled, that you
[*] have the latest HTC drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: this will overwrite your CID, and potentially void
[*] your warranty. I am not responsible for the repurcussions
[*] of this or any other damage this exploit may cause.
[*]
[*] Press enter to exploit your phone...
Presione una tecla para continuar . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[+] Restoring first backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Presione una tecla para continuar . . .
[+] Restoring second backup...
[+] Please authorize the backup on your phone, and
[+] press enter when the backup restore has completed.
Presione una tecla para continuar . . .
2520 KB/s (64526 bytes in 0.025s)
[-] Failed.
[+] Rebooting into bootloader mode...
[+] Press enter once the device has finished booting into bootloader mode.
Presione una tecla para continuar . . .
[+] Getting CID:
... INFOcid: CWS__001
OKAY
[+] If your CID is not "11111111", the exploit has failed, and you should close
this window.
[+] Otherwise, press enter to retrieve your unlock token.
Presione una tecla para continuar . . .
I tried doing the root of 2.20 as stated above that would work on my 1.85, but I ge the error above. Error as in CWS__001 not the 11111111.....could it be the drivers?? I downloaded the HTCDriver3.0.0.007 version
the guide I´m followin is this one http://forum.xda-developers.com/showthread.php?t=1952038

who can help me lol I will give you my runescape account if you help me through this >.<

LocDeMty said:
I tried doing the root of 2.20 as stated above that would work on my 1.85, but I ge the error above. Error as in CWS__001 not the 11111111.....could it be the drivers?? I downloaded the HTCDriver3.0.0.007 version
Click to expand...
Click to collapse
I think its because you didn't unlock your phone's bootloader?
Sent from my Nexus 7 using xda premium

panda_mode said:
I think its because you didn't unlock your phone's bootloader?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don´t you need to be rooted tho? All the guides I´ve seen are for rooted phones

LocDeMty said:
Don´t you need to be rooted tho? All the guides I´ve seen are for rooted phones
Click to expand...
Click to collapse
Idk the steps for unlocking a phone under 1.85, but I'm sure you will need to know how to set up and use adb. Take your time. Don't rush
Edit #3: Lol forget what I wrote
Sent from my Nexus 7 using xda premium

Related

How to DOWNGRADE Desire S with S-ON

Warning! I don't recommend this to users who are new to Android since there is a possibility of bricking your device. I will not be responsible if this happens.
It will downgrade everything even the HBoot using a HTC signed ROM. I've downgraded RUU_Saga_Telstra_WWE_1.36.841.3 with HBoot 0.98.0002 to Hboot 0.98.0000 of RUU_Saga_HTC_Thailand_1.35.1113.2.
First you need below tools and applications. I will not explain everything since I'm assuming you already know how to use it and make it.
1. ADB tool to access you device thru shell.
2. ADB driver - you may install HTC Sync since it has ADB driver in it.
3. HEX Editor - I used HxD.
4. Spare micro SD with Goldcard.
5. Card reader to make your life easier.
6. Update.zip ROM you will use to downgrade(rename it to PG88IMG.zip).
6. GingerBreak-v1.20.apk to temp root our device.
Step 1: Copy GingerBreak-v1.20.apk to your spare micro SD and insert it into your phone.
Step 2: Enable USB debugging in your device and connect it to your PC(Charge only). Make sure the drivers are installed properly. If not, install HTC Sync.
Step 3: Install and run GingerBreak-v1.20.apk. It will force close other apps(this is normal just close it). The gingerbreak application will promp that something goes wrong with the rooting(can't remember the actual spiel) but actually we already have our temp root.
Step 4: Run you ADB tool and issue command su to have root access. You can now see in your device that Superuser app is prompting you to allow the ADB root access. Accept it.
Step 5: On the # prompt, issue command dd if=/dev/block/mmcblk0p17 of=/mnt/sdcard/mmcblk0p17.img (to copy mmcblk0p17 to your SDcard). Power off your device and copy mmcblk0p17.img to your PC.(You can also use the command shell to copy it into your PC if you know how to do it).
Step 6: Open mmcblk0p17.img using your Hex editor. On the 11th line(I think), modify the current version to 1.28.401.1(since this is the lowest version I know). Save it and copy back to SDcard. Insert the sdcard and turn your phone on.
Step 7: Run GingerBreak-v1.20.apk again and follow step 3 to 4.
Step 8: On the # prompt, issue command dd if=/mnt/sdcard/mmcblk0p17.img of=/dev/block/mmcblk0p17 (to copy back mmcblk0p17.img to your phone). Do this as quickly as possible since the temp root access sometimes loose its effect.
Step 9: Power off your device and remove your SDcard. Using your card reader, delete everything(not format) in your microSD(with Goldcard) and paste your PG88IMG.zip.
Step 10: Hold volume down + power to boot to recovery and the phone will do the installation itself. Wait until you have your downgraded ROM.
This is how I do it. Hope you won't encounter any problem with this procedure. Good luck!
I want to give thanks to all the XDA members for the knowledge I acquired for this procedure and to the developer of Gingerbreak.
You may also check sonikz procedure on post #4. I think his procedure is faster. You may use which one is easier for you to follow.
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
panosfx said:
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
Click to expand...
Click to collapse
Good question i think, if i remember well, on the desire (or HD?) sometimes downgrading was a way of getting to a version of software where you then could get root again !From that point on you could get a recovery installed and install some nice roms. I dont know if thats whats going on here, i wouldn't dare to hope that ...?
Me n00b me downgrade
Newrad67, I have compiled a n00b way to achieve very similar results:
First off you need to create a Gold Card
Use the memory card that came with the phone, may as well hey!
Install Goldcard helper from market, run it and copy the CID for MMC2
This number has already been reversed so go to here, fill out the required fields.
That will then email you an image file. You can then using Gold Card Tool flash your image file to your phones SD card via the phones USB cable.
Next for the actual downgrade
You'll need this unzipped
in a command prompt, goto the directory you unzipped to
connect the phone via USB
then:
adb push misc_version /data/local/tmp
adb push GingerBreak /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/GingerBreak
Click to expand...
Click to collapse
This copies the files to the phone and changes the permissions so they will function
adb shell
Click to expand...
Click to collapse
This will enter the terminal for the phone
./data/local/tmp/GingerBreak
Click to expand...
Click to collapse
This will then temp root the phone you should now have # at the terminal prompt instead of $, which means you have higher privileges
From this point you can then run misc_version (Thanks to Blezz for the version number) This changes the version reported by the phone to 1.27.405.6, you cannot check this on the phone tho, as it will still report the other number.
cd /data/local/tmp
./misc_version -s 1.27.405.6
Click to expand...
Click to collapse
From here you can then install the update/downgrade from the exe, no need to dump zip files or anything. As with anything here, results may vary and I won't be buying new hardware if it breaks yours! But it works a treat on mine.
This can be used with paulobriens test signed RUU HTC update to get root/boot/recovery installed on s-on .
If it just were public
Sent from my HTC Desire S using XDA Premium App
panosfx said:
Downgrade to what?To Froyo?
And for what reason?
Sorry for that noob question...
Click to expand...
Click to collapse
This is why I recommend this only to advance users.
Our Desire S with S-On was released with Gingerbread ROM and Hboot that still not possible(as of now) to have custom boot recovery. Since we are on S-On, it is still not possible to be rooted and use custom ROM.
As far as I know, we don't have any official ROM except for Gingerbread. Correct me if I'm wrong. The list can be seen in this post. http://forum.xda-developers.com/showthread.php?t=1002506
I'm just sharing this to people who wants to change their ROM if they want to change to a different one. Like me who installed the latest ROM from TELSTRA and find the bloatware annoying. I've done this to get back to the ROM I'm more comfortable using.
Yeah I'm pretty much with you mate, no way to do anything more practical than flash a clean European Rom currently..... Not really a vast amount of progress either. Anything we should be doing to help get permanent root? Anyone?
Sent from my HTC Desire S using XDA App
Thankkssssss
It works on my s-on DS
Thanks a lot
i really like it how sonikz is doing now like it was his idea how to downgrade it using adb gingerbreak and misc_version lol
i'm gonna stop my rooting tries + supporting here for the desire s, hating such people like him
I never said it was my idea and I have in a posted my thanks to the relevant people in other threads, I didn't mean to rub anyone the wrong way... I hadn't seen a adb version of gingerbreak until Friday and I'm sure you know the apk is very unpredictable or at least it is on my phone so I couldn't use misc_version, it just kept kicking errors.... Hey I just threw it out there, my bad
okay
no it isnt the apks fault, maybe u forgot to use "su" in adb shell after using the apk, which u dont need for the command line version
anyway, maybe there is a way to get past the s-offf
in titanium backup there's a recovery exploit to remove files from s-on phones
we just need to know how the exploit is working and if it still working with 2.3
2nd option is i am getting a 2nd desire s soon.. it's a bugged on, radio destroyed and he don't get it repalced so he gives it me
maybe i can get the desire hd bootloader running somehow.. even if i am sure it will be a lot of work to get in
Plz guys... Get a grip.. we share.. whocares about credit.. come on..
Keep sharing.
Sent from my HTC Desire S using XDA Premium App
Worked
Sent from my HTC Desire S using XDA Premium App
@Rexton270: what worked?
@brokenworm: what you meant by the paulobriens test RUU?
@brokenworm:
it's not paul's ruu, the files he published been released 1 day before at 911snipers blog
sadly without ruu too
what ROM to get root
after doing that, what ROM is it better to download in order to become root ?
thanks
pdaGeek13 said:
after doing that, what ROM is it better to download in order to become root ?
thanks
Click to expand...
Click to collapse
If you are on S-ON, none as of now.
Sent from my HTC Desire S using XDA Premium App
> 2 hours
running for more than 2 hours now, normal ?
sonikz said:
Newrad67, I have compiled a n00b way to achieve very similar results:
First off you need to create a Gold Card
Use the memory card that came with the phone, may as well hey!
Install Goldcard helper from market, run it and copy the CID for MMC2
This number has already been reversed so go to here, fill out the required fields.
That will then email you an image file. You can then using Gold Card Tool flash your image file to your phones SD card via the phones USB cable.
Next for the actual downgrade
You'll need this unzipped
in a command prompt, goto the directory you unzipped to
connect the phone via USB
then:
This copies the files to the phone and changes the permissions so they will function
This will enter the terminal for the phone
This will then temp root the phone you should now have # at the terminal prompt instead of $, which means you have higher privileges
From this point you can then run misc_version (Thanks to Blezz for the version number) This changes the version reported by the phone to 1.27.405.6, you cannot check this on the phone tho, as it will still report the other number.
From here you can then install the update/downgrade from the exe, no need to dump zip files or anything. As with anything here, results may vary and I won't be buying new hardware if it breaks yours! But it works a treat on mine.
Click to expand...
Click to collapse
no not normal, restart your phone and try again
cause it's s-on nothing can happen to your system so don't worry and just restart
Blezz said:
no not normal, restart your phone and try again
cause it's s-on nothing can happen to your system so don't worry and just restart
Click to expand...
Click to collapse
same thing with this log:
$ ./GingerBreak
./GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 s
[**] (C) 2010-2011 The Android Exploid Crew. All rig
[**] Kudos to jenzi, the #brownpants-party, the Open
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found system: 0xafd17fd5 strcmp: 0xafd38065
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 25104 GOT start: 0x00014360 GOT end: 0x000
[*] vold: 25104 idx: -1024 fault addr: 0xfffb2284
[*] vold: 25162 idx: -2048 fault addr: 0xfff4e284
[*] vold: 25212 idx: -3072 fault addr: 0xffeea284
[*] vold: 25262 idx: -4096 fault addr: 0xffe86284
[*] vold: 25312 idx: -5120 fault addr: 0xffe22284
[*] vold: 25363 idx: -6144 fault addr: 0xffdbe284
[*] vold: 25414 idx: -7168 fault addr: 0xffd5a284
[*] vold: 25466 idx: -8192 fault addr: 0xffcf6284
etc ....
and sometimes:
[+] fault address in range (0x000132b4,idx=-3072)
[+] Calculated idx: -2005
[-] sendmsg() failed?
[-] sendmsg() failed?
[-] sendmsg() failed?
:-(

[Q] SE Xperia Pro - Unable to root with DooMLoRD v4

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:

[Q] Unable to root device after unbrickin (actual versio v21e)

Hello ppl.
First of all i have to say that this is my first post but i've been reading this forum for a quite long time and you guys rock!
Well let's get to the problem i'm facing.
I have an P920H from Brazil and i've rooted it with mastermind method (dunno if that's the exactly name, but it's master something, sorry )
No problem with that, all worked flawlessly.
Then i decided to flash Prometheus custom rom and kernel v21 version
No problem with that either, all good to go.
But the thing is that i realized that i flashed the wrong baseband (didn't read about it to be honest.. guess i should have flashed 1.5 [based on v20 and not 1.5+]. ok i'm a dumbass) and then i got no signal from my operator.
After that i tried to restore a backup that i had made with rom manager... an error ocurred and my phone bricked, got stuck on LG logo.
And then, after reading tons of topics I could restore it and made it boot.
That's when my problem came.
My phone still is using prometheus kernel i guess, and is on v21e (originally was on v20a).
Master method and superone click just can't root it and I cant install another firmware over it. It just warns about errors and said it can't find SU bla bla.
What do you guys think I should do? I want to go back to my original firmware or install the correct custom rom but can't get root.
Thanks in advance.
Dan Rosenberg to the rescue... Thanks Dan!
To make it short try using Megatron Root by Dan Rosenberg (thanks Dan) which is designed for v21e. A link you can find it here or search the Optimus 3D forums (or LG Thrill). Hope that helps. It worked for me, using now WaterBear Rom on v21e
thanks man, will give it a try on that link.
I dunno if i had an previous version of that (magatron root) but I've tried it with no luck. Perhaps I did something wrong.
Anyway thanks :good:
perna84 said:
thanks man, will give it a try on that link.
I dunno if i had an previous version of that (magatron root) but I've tried it with no luck. Perhaps I did something wrong.
Anyway thanks :good:
Click to expand...
Click to collapse
U can root 100% with megatron. At least i did it 20+ times cause returning to stock kdz so often
Sorry for that small help first...
perna84 said:
thanks man, will give it a try on that link.
I dunno if i had an previous version of that (magatron root) but I've tried it with no luck. Perhaps I did something wrong.
Anyway thanks :good:
Click to expand...
Click to collapse
I forgot to put my posts where I was asking for help.
Anyway... go to http://forum.xda-developers.com/showthread.php?p=27380826#post27380826 and see post number 142 to 145, especially last one cause I've used that link to download Megatron Root. And it worked.
Just be patient, read all about it and try it again. Good luck
BigBadSheep said:
I forgot to put my posts where I was asking for help.
Anyway... go to http://forum.xda-developers.com/showthread.php?p=27380826#post27380826 and see post number 142 to 145, especially last one cause I've used that link to download Megatron Root. And it worked.
Just be patient, read all about it and try it again. Good luck
Click to expand...
Click to collapse
Still got no sucess
This is what i got with megatron method...
[*]
[*] Megatron: LG Optimus 3D/Thrill Root Exploit (Wind
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Before continuing, ensure USB debugging is enable
[*] have the latest LG drivers installed, and that yo
[*] is connected via USB.
[*]
[*] Press enter to root your phone...
Pressione qualquer tecla para continuar. . .
[*]
[*] Waiting for device...
* daemon not running. starting it now *
* daemon started successfully *
[*] Device found.
[*] Deploying payload...
1531 KB/s (564396 bytes in 0.360s)
pkg: /data/local/tmp/evil.apk
Success
[*] Owning phone...
run-as: Package 'com.ti.fmrxapp' is unknown
[*] Rebooting device...
[*] Waiting for phone to reboot.
[*] Writing to block device...
4 KB/s (4322 bytes in 1.000s)
[-] Failed to open block device.
[*] Pushing root tools to device...
2183 KB/s (22364 bytes in 0.010s)
2377 KB/s (843503 bytes in 0.346s)
[*] Rebooting device again...
[*] Waiting for phone to reboot.
[*] Getting root...
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
run-as: Package 'com.ti.fmrxapp' is unknown
[*] Cleaning up...
run-as: Package 'com.ti.fmrxapp' is unknown
su: permission denied
su: permission denied
Success
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
Pressione qualquer tecla para continuar. . .
Ideas?
try reflashing kdz and start completely over
Sent from my LG-P920 using xda app-developers app
[SOLVED]
Thanks guys! Solved my problem
Here is how
First ive tried the method above and it didnt work, actually i was still with the same firmware version (21e)
So no good.
(Btw i`m running Windows 7 64 bits on bootcamp, but it should work for Windows 7 in general)
The solution is quite simple, right click ond adb.exe and under preferences set it to compatibility mode Windows XP and check run as administrator.
then execute the bat file as administrator also and you should be rooting just fine.
In other posts that you ask for help...
perna84 said:
Thanks guys! Solved my problem
Here is how
First ive tried the method above and it didnt work, actually i was still with the same firmware version (21e)
So no good.
(Btw i`m running Windows 7 64 bits on bootcamp, but it should work for Windows 7 in general)
The solution is quite simple, right click ond adb.exe and under preferences set it to compatibility mode Windows XP and check run as administrator.
then execute the bat file as administrator also and you should be rooting just fine.
Click to expand...
Click to collapse
...Please give all the infos, even those that you consider not important. In that way you could find help fast. Anyway, glad to hear that you solved it.
perna84 said:
Thanks guys! Solved my problem
Here is how
First ive tried the method above and it didnt work, actually i was still with the same firmware version (21e)
So no good.
(Btw i`m running Windows 7 64 bits on bootcamp, but it should work for Windows 7 in general)
The solution is quite simple, right click ond adb.exe and under preferences set it to compatibility mode Windows XP and check run as administrator.
then execute the bat file as administrator also and you should be rooting just fine.
Click to expand...
Click to collapse
Had this issue myself I wanted to help you but i forgot how I solved it... after I read this post I remembered
Sent from my LG-P925 using xda app-developers app

[Q] Please help me for rooting AT&T One X

Hi guys, I'm in Turkey and my friend went to USA 4 months ago. He promise bought me a HTC One X, when he bought my htc one x in amazon, amazon sent my friend a AT&T One X. This is not intentionally, and we sent message to amazon. And they sent me network pin to unlock my network. And I want to root, unlock bootloader, super cid . But I can't make this at the moment. I installed over and over htc drivers, and opened usb debugging mode, and opened root exploid. but this exploid says:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: cannot create /data/local.prop: Permission denied
AGAIN REBOOT
I can't unlock bootloader, and I can't root and I cant make super cid.
Please help me and I am sorry my English
What method are you attempting to use?
Sent from my HTC One XL using Tapatalk 2
I used to root-one-x exploit, hasoon exploit,..... I used all methods
Sent from my HTC One X using xda app-developers app
xenonflash7 said:
I used to root-one-x exploit, hasoon exploit,..... I used all methods
Click to expand...
Click to collapse
You need to figure out what hboot and firmware version you're on first. Different root methods for each.
Check your Settings>About>Software information and see what it says under Android version and Software number.
Then reboot to bootloader and see what it says next to HBOOT.
2.20.502.7 710RD my software number and 4.0.4 my android build
Sent from my HTC One X using xda app-developers app

I am very desperate! Will donate as well! Rooting issue with Asus TF700T

Hi amigos on the internet!
I recently purchased an Asus TF700T about a week ago and still I'm having trouble rooting it.
Tried basically every method I could. I desperately seek help!
My device is unlocked though SU say's there is no binary installed.
I don't have fastboot on my device it only shows three images which is the RCK logo ANDROID logo and WIPE DATA logo.
There is not USB logo.
I have JB 4.2.1
Build number :
JOP40D
If you need anymore information I would be glad to provide! Please and thank you for taking the time! I just want to root and have TWRP on it
Unfortunately I do not know how to get TWRP
When trying to root it with DeBugfs I get this
Waiting for device to be detected…
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Found system partition at: /dev/block/mmcblk0p1
Step 1 – Pushing files…
failed to copy ‘debugfs’ to ‘/data/local//debugfs’: Permission denied
failed to copy ‘su’ to ‘/data/local//su’: Permission denied
failed to copy ‘debugfsinput’ to ‘/data/local//debugfsinput’: Permission denied
failed on ‘/data/local/tmp’ – Permission denied
link failed File exists
Rebooting…
Once your devices has finished restarting,
Press any key to continue . . .
Step 2 – Rooting…
For this step, ignore any error messages that say “File not found”
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can’t open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on ‘/data/local/tmp.bak’ – No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
Rebooting…
Once your devices has finished restarting,
Press any key to continue . . .
Finally the following appears:
Rooting FAILED! You may want to try running this tool again.
Your device region may not be supported if you see this message again.
Press any key to continue . . .
Your help will be greatly appreciated it! I will also donate through pay-pal since I'm very desperate, haha. Thanks again!
You need to run the tool as administrator
Also, have you used the unlock file from Asus. You must be unlocked, bootloader unlocked, for this to work.
http://forum.xda-developers.com/showthread.php?t=2094746
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Mkami said:
Your help will be greatly appreciated it! I will also donate through pay-pal since I'm very desperate, haha. Thanks again!
Click to expand...
Click to collapse
What is your firmware version? If you are on anything later than 10.6.1.14.8, then you have to downgrade in order to root... You are already unlock and why don't install custom recovery and custom rom...
You don't have to donate to me because I am here trying to help out new user....
Mkami said:
My device is unlocked though SU say's there is no binary installed.
I don't have fastboot on my device it only shows three images which is the RCK logo ANDROID logo and WIPE DATA logo.
There is not USB logo.
Click to expand...
Click to collapse
Apparently you didn't read the text in the upper left corner - recent bootloaders activate fastboot already in the bootloader menu.
So you can use fastboot to install TWRP (read the guide on the teamw.in website or here on xda), then TWRP will offer you to install a root app.
And ignore the "you have to downgrade to root" advice - that's only relevant if you don't want to or can't unlock.
Hey guys thanks for replying to this post! Luckily I was able to get full step by step help by a member on XDA he was super helpful! Got my tablet rooted and rommed Thanks for looking at my post! Much obliged

Categories

Resources