Database Info

[Program]Bash simpleroot OTA 1.47.651.1 for Linux users - update01 rlsed

This is an adaption of Simpleroot for rooting OTA 1.47.651.1 in bash-script for linux users
In order to use this root you will need to have installed the android SDK on your linux machine, either via your distributions package management system or manually.
The user you are logged in with will need to have access to the adb tool that comes with the android sdk. Usually this means adding the user to the android group after installing the sdk, but specific methods of attaining access may differ by distribution.
- One method of setting up the sdk can be found Here
To begin using the bash simpleroot after installing the sdk and verifying access to adb, navigate to the directory where you extracted the simpleroot files in a terminal (read: console or command prompt if you prefer that terminology) and do an
"sh p1.sh"
to begin step 1 of the process,
then follow the instructions that you will be given as the script runs (it will tell you when to run the next script in the chain, etc).
SPECIAL THANKS to ItsMeCD for being a guinea pig on irc and successfully rooting his evo using bash simpleroot.
UPDATE 24-July-2010, 14:45 (2:30pm): Download replaced due to nasty evil bugs that crept into the original scripts and prevented them from running. if you downloaded before this time/date, please re-download
Simpleroot Bash Edition, by netarchy
Bugfix update: Update 01
- Fix some confusion in script execution feedback during p2.sh that may lead the user to believe the process has failed when it has not
- Clarified output during p4.sh to better reflect how long the user should wait before confirming the attempt to root has failed
Extract the update to the same place you extracted the original download, and overwrite files if prompted.
Simpleroot Bash edition Update-01

Great job! This will make my life so much simpler when more of my coworkers ask me to root their Evos. Good looking out for us lazy Linux vets

jmlott said:
Great job! This will make my life so much simpler when more of my coworkers ask me to root their Evos. Good looking out for us lazy Linux vets
Click to expand...
Click to collapse
Windows has no place on any computer of mine ;D
Be sure to lemme know if you run into any issues. Eventually I'll streamline it to need less interaction, maybe even make a gui for the cli-fearful.

Running it now...re-downloaded and extracting.

Posted a bugfix update to clean up script errors and clarify output.

Worked First Time
Didn't see any success stories yet, so I thought I'd post mine. Downloaded and ran the scripts and got root first time.
Now rockin Froyo courtesy of CyanoGenMod6. (Tried to leave a url to the ROM, but I'm too much of a noob on the forum

damnit ! - linux n00b - i gotta be close - errors on scripts... help ?
[email protected]:~/a/t$ ls
adb ddms hprof-conv p2.sh ra-rec.img
amonra.sh dmtracedump layoutopt p3.sh README.txt
android draw9patch lib p4.sh simpleroot-bash
apkbuilder emulator mksdcard part1 source.properties
cleanup.sh etc1tool mtd-eng.img part2 sqlite3
clockwork.img flash_image NOTICE.txt part3 traceview
clockwork.sh hierarchyviewer p1.sh PC36IMG.zip zipalign
[email protected]:~/a/t$ sh p1.sh
adb not found, exiting.

xda98052 said:
[email protected]:~/a/t$ ls
adb ddms hprof-conv p2.sh ra-rec.img
amonra.sh dmtracedump layoutopt p3.sh README.txt
android draw9patch lib p4.sh simpleroot-bash
apkbuilder emulator mksdcard part1 source.properties
cleanup.sh etc1tool mtd-eng.img part2 sqlite3
clockwork.img flash_image NOTICE.txt part3 traceview
clockwork.sh hierarchyviewer p1.sh PC36IMG.zip zipalign
[email protected]:~/a/t$ sh p1.sh
adb not found, exiting.
Click to expand...
Click to collapse
Putting the sdk tools binaries in the same dir with the scripts isn't going to make them magically find them (you're thinking windows style here), you need to put the android sdk tools in your PATH variable. The wiki referenced in the first post has an example of how to do this.
An example for you:
let's say you extracted the android sdk to /home/foo/androidsdk
and the tools are in /home/foo/androidsdk/tools (this is just for the sake of example mind you)
you would want to edit your .bashrc and add in
export PATH=$PATH:/home/foo/androidsdk/tools
You can then make that kick in by logging out and logging back in.

Just to Clarify...
Can I get root access without having to wipe my phone?

Having a problem
UPDATE: booted into clockwork and flashed Fresh ROM, ROM Manager works fine now. Thanks again for the awesome root method Netarchy, you are my hero!
Hey Netarchy, first want to say thank you for giving us Linux users some simpleroot love. Good job.
I ran all the scripts and everything seemed to go as you said it would. No error messages, all was well, I ran clockwork.sh and my phone booted in to clockwork just fine!
Code:
Pushing ClockWork Recovery
1534 KB/s (2752512 bytes in 1.751s)
Clockwork image pushed!
pushing flash_image
610 KB/s (26172 bytes in 0.041s)
flash_image pushed!
Changing permissions...
Permissions changed...
Moving recovery image...
Recovery moved...
Rebooting...
===============================================================
===============================================================
Recovery Flashed! please run sh cleanup.sh
===============================================================
===============================================================
Yay! So I installed ROM Manager on my phone and then my hopes are dashed. When I try to download roms it says I have to have ClockworkMod Recovery installed, so I tell it to install from ROM Manager, and I get this...
An error occurred while attempting to run privileged commands!
Click to expand...
Click to collapse
Any idea what I might have done wrong? Or should I just start the whole process over again? I noticed in my settings my software number was showing 1.17.651.1 now instead of 1.47.651.1 before I rooted.

netarchy said:
- One method of setting up the sdk can be found ...
Click to expand...
Click to collapse
Not allowed to post links (yet?)
Thanks for this but there's no info at that link just this...
AndroidSDKLinux
From Villain ROM
Jump to:navigation, search
There is currently no text in this page. You can search for this page title in other pages, or search the related logs.
Click to expand...
Click to collapse

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] HTC Desire HD - Can't Downgrade from Gingerbread to 1.32.405.6

Hi,
I was following the article :
[GUIDE] How to downgrade 1.7x/1.8x/2.x to 1.32.405.6
@ http://forum.xda-developers.com/showthread.php?t=905003
.
The cursor blinks after this line:
Code:
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
I have waited for almost an hour, but nothing happens, and I have to break using Ctrl+C.
My questions is, what am I doing wrong/ what needs to be done? Cause I see other posts where the output shows many more lines similar to the one above, and then the # (root) prompt, but I don't get it.
-- Phone: HTC Desire HD [Unlocked]
-- OS: Just received OTA Gingerbread: 2.3.3; s/w version: 2.37.720.3
-- Factory Reset Done
-- PC Connection is in : Charging mode and USB Debugging
Complete output:
Code:
G:\htc desire hd\Mod\Setups\Downgrade>adb push misc_version /data/local/tmp
1104 KB/s (15837 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb push GingerBreak /data/local/tmp
1173 KB/s (16830 bytes in 0.014s)
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/misc_version
G:\htc desire hd\Mod\Setups\Downgrade>adb shell chmod 777 /data/local/tmp/GingerBreak
G:\htc desire hd\Mod\Setups\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
Thanks in advance,
Gautam

Downgrade Failed
I got the same result.. Needed help.. :sad:

Same here. Any help would be appreciated

Ok guys even I am stuck here too and I had posted about this, but no one replied, however I got down to googling tactics and the most statisfying reason that I have come up with (reasoning is based on the countless articles and websites about gingerbread and gingerbreak) is that the gingerbreak crack is for a different version of of gingerbread, a version which was launched before we Indians, got out version of gingerbread and thats why our DHDs are getting stuck at the same place over and over again. It's all because of different s/w version numbers.
I guess we all have to wait for a gingerbreak version that is applicable across all DHD ROMs, only then can we be able to downgrade. There might be other way(s), but I know none. This is my two bit about what all of us, are going through when following the downgrade guide. I may be wrong, I may not be. If you have a different thing to say about it, then by all means let all of us hear it.

Thanks Ruben for the clarification. I think you're right. The following two links suggest that as well.
Check out (Google them as I can't paste links due to the less # of posts that I have):
Google Patches GingerBreak Exploit, But Don’t Worry – We Still Have Root (For Now)
Change Iab98d71c: Detect Android devices vulnerable to CVE-2011-1823
I was trying to downgrade so that I could install Android Revolution HD 5.1.7 on my DHD. Any other way to achieve the same? I wish I knew this; just updated to Ginger a few days ago.

The pleasure was all mine Gautam, just trying to do my part to help other Indian DHD users. anyways check out this page http://forum.xda-developers.com/showthread.php?t=905003&page=149 and I believe jkoljo is already on the job.
Unfortunately there is no other way to downgrade the gingerbread 2.37 hoping for an exploit from, The Android Exploid Crew and jkoljo.

is it cuz we are indians?
Same exact problem. Spent more than 24hrs finding a solution. Really bored of the stock ROM and the gingerbread update does not even have enough visual changes. Zzz really wish someone does something about it
Once again Indians have a disadvantage.

Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)

ericjennings said:
Android Version: 2.3.3
HTC Sense Version : 2.1
Baseband : 12.54.60.25U_26.09.04.11_M2
Kernel : 2.6.35.10-g0956377 ([email protected]#1)
Build Number : 2.36.405.8 CL47853 release-keys
Software : 2.36.405.8
I too was following the instructions. The first time I tried I had my sdhc card in and gingerbreak got a little further than you quoted above but just kept saying 'sendmsg fail'. I googled this and found a post which said that gigngerbreak could run without the sdhc card. So I tried that and got the same problem you reported. I waited a few minutes with nothing happening then decided to pop my card back in...at which point gingerbreak started running again.
If your card is in when gingerbreak starts it might be worth ejecting/inserting when you reach the sticking point.
(In the end it didn't help me, gingerbreak finished OK but then I got an error from misc_version which I have not yet been able to get past)
Click to expand...
Click to collapse
1st you will need the following files
GingerBreak from http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
misc_version from http://www.multiupload.com/A9PNGVBWBE
Default rom http://forum.xda-developers.com/showthread.php?t=905003
and Android SDK http://developer.android.com/sdk/index.html
Also you will need a clean SD card 1 gig or more should be fine (smaller is better)
Unzip GingerBreak and misc_version into a folder say c:\Downgrade (I normally use 7Zip)
You should have:
c:\Downgrade\GingerBreak with 5 Files
c:\Downgrade\misc_version with 4 Files
Make sure you installed Android SDK's Platform tools and updated your path to reflect this
IE: run SDK Manager and install Android SDK Tools and Google USB Driver pack if you don t have HTC Sync driver running.
Format the SD card and copy the rom.zip into the base of the card, not a sub directory. (Do not unzip)
Now: Plug in the phone to the USB and make sure Debugging is on and the phone is set to charge only.
Then open Command prompt ie: run cmd.exe
Go to your Downgrade directory and test if your adb command is in the path. ie: run it and make sure it lists switches and not say file not found
Then run as follow
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
adb shell
./data/local/tmp/GingerBreak
if you fail to get root ie: prompt does not return to # or get a endless sendmsg() failed? Error, reboot the phone and repeat the commands above. The phone I used, took 3 tries to get this right.
at the # run the following
cd /data/local/tmp
./misc_version -s 1.31.405.6
When its done exit cmd and goto your phone, Reboot it while pressing volume down.
It will come up with a menu and follow the update instructions.
You should then be on Android version 2.2 when done.
Please note the rom that is supplied works with unbranded phone only if you have a branded phone you will need to make a goldcard. If you want to know how to make one, google is your friend sorry.

You must have htc sync installed!
**** I TAKE NO RESPONSIBILITY IF THE BELOW PROCESS DOES NOT WORK FOR YOU & IF YOU BRICK YOUR PHONE - DO THIS AT YOUR OWN RISK ****
What you need :
- MicroSD card with SD Adapter
Procedure :
1. You need to setup ADB on your PC and download the Android SDK, guide here:
How To: Set Up ADB/USB Drivers for Android Devices | The Unlockr
2. Create a GoldCard here (remember to open the SD Card as a PHYSICAL DISK) :
How To: Create a Goldcard | The Unlockr
3. Download the Generic Software here :
http://androidfiledepot.com/Storage...ravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
4. Insert the Goldcard into the Desire and connect it to your PC. Run the software downloaded in step 3.
5. This will flash your Desire with a generic HTC version of the OS.
6. Enjoy!

If you see error 131, you don't have htc sync!

Nilseby, thanks for the suggestion.
I tried your method, and the process starts; phone switches off and HTC in displayed in White. After a few minutes, it says, that it can't go through with this, and the program just hangs. I powered on the phone and it's back to the way it was. Flashing didn't go through. I created a gold card as well and formatted, still no luck.

2.37.720.3
Why, oh why did I upgrade to 2.37.720.3?
I actually wanted to root my DHD so that I could take screenshots of its screen. Now that it is being reporting that as of now 2.37.720.3 is not downgradable, is there any other way to take screenshots of my phone's screen? Other than, of course, taking pics with another camera.

Thank God!
I am using RCMIX HD Kingdom v 1.2 with Sense 3.0 on my DHD and when I saw I downgrade guide from Gingerbread to get root access, I decided to upgrade to the official 2.3.3 in India. I saw the initial posts in that thread say that the method worked really well.
I had almost made up my mind to try the official update knowing that I can downgrade using the guide, but just before doing that I thought I'd read the more recent posts and guess what I realized the Indian software number 2.37.720.3 cannot be downgraded! Which means no root access and no custom ROMs (at least for now). I immediately changed my mind and didn't upgrade.
Thank God!

Good decision av. Just wait till this issue gets sorted out and then dive in. I was too eager to see what was up with Mr.Ginger and curosity killed the cat.
Sent from my Desire HD using XDA App

We in Australia have the same problem regret upgrading.

Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out

guitarist7 said:
Just got my UK 2.37 upgrade a few days ago...why, oh, why did I accept it!? Hopefully not long until the 2.37 gingerbreak is out
Click to expand...
Click to collapse
yeah..
now i cant do anything with it

I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases

DotNetRules said:
I can't even get a GoldCard to work on 2.37x , I know its not the cards I'm using as they still work for older releases
Click to expand...
Click to collapse
What do you mean by getting a GoldCard to work? Is the phone not mounting it or something?

[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:

Temporary root via motochopper

Hi, I was experimenting on rooting without registering to HTCDev, testing many Linux kernel exploits. (I don't write the exploits myself, I compile exploits source codes and try to make it run on One SV kernel)
The exploit I found working is motochopper, with some minor modifications, it could also be used to gain temporary root on One SV.
I tested this exploit on Taiwanese version of One SV, which is k2u and Android 4.1.2, kernel version is "3.4.10-gb590306 [email protected] #1 SMP PREEMPT"
First download motochopper.zip from the link above, unzip it.
Code:
adb push pwn /data/local/tmp/
adb shell chmod 755 /data/local/tmp/pwn
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
Now, adb shell into it and execute /data/local/tmp/pwn , this would push the su executable to /system/xbin , then "su -" , you should now become root!
But due to HTC modified kernel, which has eMMC write protection, /system partition is unwritable. Some time later you would find the su executable you pushed to /system/xbin disappear, this would also happen on reboots. This means you would need to re-run this exploit every time you reboot!
The motochopper exploit is based on CVE-2013-2596, which affects Linux kernel before 3.8.9 and some Android builds. Since the vulnerability came from Linux kernel, I predict it would also work on all versions of One SV's kernel 3.4.10, perhaps even all HTC 3.4.10 kernels.
With temporary root, you could read & write memory (dump kernel image), dump any partition (but some of them is readonly as above mentioned), etc.
I'm still thinking how to get permanent root from this point, post here if you have any ideas!
ps. I have less then 10 posts so I can't post to development boards. But this post should go there I guess.

Did someone try on the LTE version ?
Doest it work?
I would like to use that to remove few Stock apps; like Best Deals, Flicker for HTC Sence, FB for HTC Sence etc...
But once it's over, before reboot, is it possible to delete the files ?

If you're on hboot 2.0 (if you updated to jb) you won't be able to remove anything, since the system partition is write protected. Apps'll come back after reboot.
On hboot 1 no problem though , afaik.