Develop Bugs

[Q] Which root method to use?

I just upgraded to the Evo 4G.
It came stock with the Froyo Sprint 3.30.651.2
I was told by a friend that its hard to root the 3.30 builds, and I couldn't find reference to that on here.
Just want to make sure T_T

it is HARD to root 3.30 build. what is your hardware? i am willing to help you command by command (because i am nice?) do you have adb installed? pc or mac? first step is install adb. then i can help you more.

uhm, did i forget to say i am very noob at this T_T what is adb?
and in terms of hardware,. did you mean..
Hardware version 0003?

I was in the same boat as you last week. I had WM for years and was familiar with unlocking and flashing things, had to learn quite a bit of new stuff moving to android. These two threads helped me immensely.
http://forum.xda-developers.com/showthread.php?t=828437
http://forum.xda-developers.com/showthread.php?t=829045
I am not sure how well the first one works, but would be easier. Personally I used the 2nd link and followed the manual method, not only to make sure every step was correct, but it also taught me quite a bit about android.
Let me, the other gentleman in this post, or someone in one of those posts if you need an assistance.

wow both those tutorials root while turning s-off?!?!? i guess i haven't been reading up on those enough. i thought that they were to turn s-off once shell permissions were gained. if you want to do it manually, you still can, but the first link seems the best since it somehow magically downgrades you to .76.2 hboot. i'm not sure if anybody else has been able to do this in hboot 2.02. or maybe i'm wrong. maybe you just have to flash a pc36img.zip after s-off.
answering your question: adb is the driver that allows for your phone and your computer to talk. it was developed by google to help app developers, so it is perfectly safe and legal. it is used for just about every manual hack/mod on these forums. really, it is the most useful tool you can have. once again, pc or mac?

pc =]
either one running xp x32 or one running 7 x64

dkdude36 said:
wow both those tutorials root while turning s-off?!?!?
Click to expand...
Click to collapse
Yea I had read up all on rooting, flashing, etc before getting my Evo last week only to have to search more when none of the other methods worked. Fortunately those posts got me everything I needed.

Maybe you guys can shed some light for me on this issue. I attempted to root my phone using the tutrial on this site named How to root evo 2.2. Everything went well got into bootloader and when it was time to load the image files from the pc36img.zip it would never load the files. My guess is because the hboot file in the zip is hboot 0.93.0000 and i have hboot 0.97.0000. All the info i see about rooting is relating to hboot 2.0.2 which is not the hboot on my evo. Any ideas? Thanks
Android Version
2.2
Baseband Version
2.15.00.09.01
Kernel Version
2.6.32.15-ge2fb08e
[email protected] #11
Build Number
3.29.651.5 CL252548 release-keys
Software Number
3.29.651.5
Browser Version
Webkit 3.1
PRI Version
1.77_003
PRL Version
60671
supersonic evt2-3 ship s-on
hboot-0.97.0000
microp-041f
touch panel-atmelc03_16ac
radio-2.15.00.09.01
Click to expand...
Click to collapse

Stroid01 said:
Maybe you guys can shed some light for me on this issue. I attempted to root my phone using the tutrial on this site named How to root evo 2.2. Everything went well got into bootloader and when it was time to load the image files from the pc36img.zip it would never load the files. My guess is because the hboot file in the zip is hboot 0.93.0000 and i have hboot 0.97.0000. All the info i see about rooting is relating to hboot 2.0.2 which is not the hboot on my evo. Any ideas? Thanks
Click to expand...
Click to collapse
The hboot 2.0.2 like we have is the one that is more difficult to root. I have mine rooted, but I did not downgrade it like some have tried or possibly have done. If you have an older hboot and are on the 3.29 stock rom you shouldn't have too much problem following the basic guides, or even many of the 1-click root options. I personally don't know which to recommend because none of them worked for me, I would read through the android development subforum and see what has worked for others though.

hah ya you need to redo the mtd-eng.img step. that is why it wasn't accepted. i sort of went off on my own boat last night and rooted 3.29 flawlessly by running 4 pc36img.zips (from 3.29 to 1.47 to 1.32 to rooted 1.32 to eng spl 1.32) and 3 different exploits (mtd-eng exploit, flash lite exploit, no security exploit, and simple mtd-eng exploit). it really worked well, but took hours of downloading. thats like over half a gig of files. if you have questios about my method just ask.

where does it say what hboot you have?

boot into bootloader (turn phone off. once fully down, hold power and volume down) should say hboot-(version) or something like that.

I, too am confused as to what method to use or if I have to wait.
My hboot version is 0.97.0000
Hardware is 004
Software 3.29.651.5
PRI 1.77_003
Has anyone applied the unrevoked3 method for this config? Also, if 3.30x is a new release, it's weird why my "System Update" does not find any new OTA updates.

That is the weirdest verson combo I have ever seen. really no idea.

20$ for your Time!

i need my phone rooted, Android 2.2- 0004 hardware- 3.70 Softy- 2.15.00.11.19 Baseband..... I will pay Via Paypal, I just needed rooted before I sell it! If any body can help Developers pls..... Remove this if it is pointless.
Thank you for your Time

Have they found a root method for 3.70 yet?

i dont know if they have yet...

Yes they have. Zikronix has a thread on how to do it.
Sent from my PC36100 using XDA App

Will unrevoked work?

No it doesn't...the unrevoked dev team is working on one.
leenypost was refering to this thread:
[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - Root! The Final Frontier Edition - Upd. 12.21.10

i think they have but im not the one that wants to do it, i cant cuz my other evo got rooted with Simple root so i didnt have to do it the long Way but i dont have that phone anymore. Any takers?

All you need to do is follow the link ICEReaction posted. It's very straightforward.

just downgrade using a stock RUU then use old root methods

im VERY noob wen it comes to cmd, shell cd to etc. and all that i guess the hard part is the Command prompt i can open but wen changing or anything i get path not found etc

rayveno said:
just downgrade using a stock RUU then use old root methods
Click to expand...
Click to collapse
This will not work. If your phone is new and came with hboot 2.02 or 2.10 it is a no go. If you have an older EVO you can flash a rom with a lower SW version and then use an RUU that matches that version if you like and then use unrevoked to root... But that's way more work to then get back up to 3.70 than just following the supplied thread.

Thread moved to Q&A.

[Q] Unrevoked 3.21 not rooting Evo 4G....

Even though Unrevoked is telling me "This was a triumph."
I went through the process and it looks to be working, but when I boot the phone back up into Android, there's no Ninja and when I install ROMManager, it tells me SU access was not found on the device.
Am I doing something wrong here? Is there a detailed how'to somewhere so I can see if I'm missing a step?
Thanks!

What HBOOT version is your phone? Boot into bootloader and itll say it at the top!
What hardware version is your phone?

M Diddy said:
Even though Unrevoked is telling me "This was a triumph."
I went through the process and it looks to be working, but when I boot the phone back up into Android, there's no Ninja and when I install ROMManager, it tells me SU access was not found on the device.
Am I doing something wrong here? Is there a detailed how'to somewhere so I can see if I'm missing a step?
Thanks!
Click to expand...
Click to collapse
You probably have a new phone with hboot 2.02 or 2.10 and unrevoked does not work with them...
Or, You upgraded your phone via the OTA and lost root... And now you are trying to use the same old unrevoked that you used to unlock the phone before..
If you have a new HBOOT listed above unrevoked will not root your phone. In the development section there is a thread with instructions on how to root hboot 2.02 or 2.10 phones.

leenypost said:
You probably have a new phone with hboot 2.02 or 2.10 and unrevoked does not work with them...
Or, You upgraded your phone via the OTA and lost root... And now you are trying to use the same old unrevoked that you used to unlock the phone before..
If you have a new HBOOT listed above unrevoked will not root your phone. In the development section there is a thread with instructions on how to root hboot 2.02 or 2.10 phones.
Click to expand...
Click to collapse
That'd be it. HBOOT is 2.02. I just got this thing out of the box and looks like I'll have to use the other way.
I'm coming from a Droid 1 and I have to say, at least that phone, rooting was cake.

M Diddy said:
That'd be it. HBOOT is 2.02. I just got this thing out of the box and looks like I'll have to use the other way.
I'm coming from a Droid 1 and I have to say, at least that phone, rooting was cake.
Click to expand...
Click to collapse
Yeah you will have to use the other way, the thread is by Zikronix, and I have used it on a friends phone. Takes some time to do and make sure you follow every step carefully!

IIRC, to get ADB, I need to download and install the SDK, correct?

[Q] [SOLVED] Final question before rooting my DZ

Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.

prazzo said:
Hi,
I've got my DZ a couple of days ago. It's a secondhand DZ. Previously i've used HTC Touch, Touch Dual, TP2, so this is my first Android experience. I did lots of ROM playing on previous winmo phones, but after reading for these couple of days of Android modding, i learn that flashing another Android ROM is not so simple as winmo ROM.
This is my DZ info:
Android version 2.2.1
Baseband version 12.28e.60.140fU_26.04.02.17_M2
Kernel version 2.6.32.21-g6e170e7
Build number 1.82.707.1 CL317545 release-keys
Software number 1.82.707.1
VISION PVT SHIP S-OFF
HBOOT - 0.85.0009
MICROP - 0425
RADIO - 26.04.02.17_M2
eMMC - boot
Dec 13 2010
I've check with root checker and Titanium Backup, it says NO root access.
I've learned that with 1.82, i will have to downgrade first to 1.34.
In the steps for downgrading, i found that i will have to flash signed PC10IMG. But i also found in the sticky thread there's a warning, not to flash signed PC10IMG if i have S-OFF. So before i can downgrade, i have to get the S-ON.
I've read in a thread :
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7
The problem is, i got a secondhand unit without microSD card. How can I get S-ON? I don't know how (what method) my DZ got S-OFF at the first place.
Any help is much appreciated.
Click to expand...
Click to collapse
You are already S-OFF? I'd find it strange that you'd be S-OFF and not be rooted.

install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App

You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot

Spastic909 said:
install rom manager and check if there has been a recovery already flashed. Might answer your question
Why do you want s-on? S-off is a good thing
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
I've already installed Rom manager and there's no clockwork recvery installed.
I want to flash custom rom. I need a root to do that. To get a root, i need to downgrade. To downgrade, i need to flash signed pc10img. And there's a warning here that said DONT flash pc10img with S-OFF. That's the problem.

Shinfang said:
You can check if you got S-OFF or S-ON
by entering bootloader
Power off your phone, then, hold the volume down key and the power key.
You might need to disable fastboot
Click to expand...
Click to collapse
I already did that. Bootloader says VISION PVT SHIP S-OFF. So that means i definitely have S-OFF.

I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?

prazzo said:
I've learned some more from the post here and there. I think i figured out what happen with my DZ. I think the previous owner rooted and S-OFF the phone in the old firmware 1.34 then got an OTA update to 1.84. That update destroyed the root but somehow still S-OFF.
If I follow the direction in this thread, i assume that i can downgrade and root again. I will not need a goldcard to downgrade because currently i have S-OFF.
http://forum.xda-developers.com/showthread.php?t=905261
Am i right?
Click to expand...
Click to collapse
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers

silverwind said:
I am not sure whether it will work. But I am curious too.
I once upgrade via OTA and then I downgrade it following the instruction as per your link reference too. I rooted succesfully.
But, my DZ was S-ON.
Now you are in a different situation. You want to downgrade and root it but you already S-OFF.
Do you want to try it?
Cheers
Click to expand...
Click to collapse
I guess i have to try it.. will report after trying. Thnks all for the help..

Your theory on the previous owner having used the over the air update after rooting seems right to me. I've read more than a few times it will still show S-OFF but not be true S-OFF. Because you can't get S-OFF without root (well surely not on the newer 1.82's)

I'm not familiar with the 1.82 issues (why normal root methods fail on 1.82) but I wonder if temp root works, if you have radio S-OFF and temp root works it might be as simple as:
1. Obtain Temp Root (even Visionary could work)
2. Flash CWM Recovery (I'd use the flash_image method and not ROM Manager)
3. Reboot into CWM recovery
4. ...
5. Profit (Install a new pre-rooted ROM)
Of course this all depends on if temp root works with 1.82 and if your S-OFF is really S-OFF but it seems like a quick & easy thing to try.

I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!

prazzo said:
I did it guys. It went smooth. Still needs goldcard though due to unmatched CID.
I'm on 1.34, rooted and S-OFF. Next find out ROM that i like most. Any recommendation? it has to be cool and fast..
So i figured that the warning "do not flash signed PC10IMG if you have S-OFF" is before we have the misc_version method. With misc_version "main is older" problem will never occur, provided misc_version done correctly.
Thank you all guys for your help and time especially for those guides starter. You guys are the ones who make this forum SO GREAT!
Click to expand...
Click to collapse
Congrats .
The first time I did after rooting was install ROM MANAGER premium version.
There a lot of rom to try with the easiest way..
Good luck

[Q] HTC Incredible running 2.3.4 and 2.15.10.07.07 - Please help get S-OFF

I was able to run an older version of Unrevoked to establish SU access, but Unrevoked Forever is incompatible with my radio version. So, I have SU access, but I cannot remove or convert any applications using Titanium Backup. TB runs, but it reboots the phone if I try to remove system apps. HBOOT shows S-ON since Unrevoked Forever was not able to complete due to the radio version. So, am I stuck with S-ON? Is Unrevoked Forever going to continue developing releases to cover 2.15.10.07.07?
If I understand correctly, I cannot flash an older radio version with S-ON. Please correct me if I am wrong.
Thanks!
HTC Incredible
2.3.4
Baseband: 2.15.10.07.07

you are correct,s-on will only let you go forward with "approved by htc" files. that means no backpeddling firmware to a rootable version,no flashing only a radio or recovery. im surprised that unrevoked even worked to get you su access,i was under the impression that all exploits had been patched in 2.3.4 source code. what happens if you try and install clockwork?
if you truly have su access,it seems it may be possible to use adb to rewrite the misc image,and thus be able to flash backwards in firmware.
however,from the sounds of the behavior youre describing for tibu,i dont believe you have su access. it prolly only put the app in the drawer,and was unable to place the matching binary.
we have been telling folks for months that they should become s-offed before the GB update,as it would be unrootable.
i bought an xtc clip awhile back that is supposed to support the incredible. i dont know that it will actually work,ill know for sure when it gets here. im told it only works with sim card phones,wich the inc is not,but its clearly listed in the supported devices.
your only real hope at this point is that someone finde a new exploit that will allow temp root and re-writing of the misc image so that you can flash older rootable firmware,or that alpharev/unrevoked can add the incredible to its supported devices list,as they use some sort of hboot trickery to get a hard patched permanent s-off hboot onto the phone first. from there you load a recovery thru hboot,then flash su in recovery.
sorry this isnt the news youre hoping for.

Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!

efizzle said:
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
Click to expand...
Click to collapse
If you already have clockwork mod, flash the unrevoked forever zip from here

When I flash the zip file, I get E:/ unsupported radio version. E: update failed.

Do you have adb set up and running? Are you fairly comfortable copy/pasting commands?
Sent from my ADR6400L using XDA Premium App

still with us? waiting for an answer to the above so we can procede
also is it possible you can post or PM me a link to the version of unrevoked you used?
if you dont have a link,just email me the whole file( [email protected] ) im extremely interested in trying to duplicate your condition and figuring out a reliable way for folks to downgrade and root.

Scotty,
I'm sorry for the delayed response.
I do not have ADB setup, but I have no problem following directions to get S-off and reclaim some memory!
I have emailed you the Unrevoked file to your email address. This should run perfectly on 2.3.4 with the exception of the last step of flashing unrevoked.zip for S-off. You will see the "unsupported radio version" errors on the phone's screen. Please let me know if there is anything else that I can do to help. Thank you for your help with this.

I got your email. I will put some stuff together for you,and try it out and see if it all works the way I hope it will. If so ill upload a mini-adb with some exploits files and post a guide. Basically,were just going to rewrite the misc image so you can downgrade back to froyo and run unrevoked forever. After you reroot and get s-off back,you can restore a backup of what you have now.
Sent from my ADR6400L using XDA Premium App

Subscribing to thread. Looks interesting, Im hopeful it works out. Good luck!
Sent from my ADR6300 using XDA App

Ok after reading this thread again. My guide for the merge on froyo or the stuff I have for gingerbread for the merge will not work on a non emmc device. 2nd who buys a xtc clip and doesn't look what they buy? The way it works is with the sim card slot. Inc doesn't have one so it isn't going to work. It also isn't listed as supported as it would be pointless to say it does.
If I am not mistake with s-on you can't flash the recovery partition. So how did you get clockworkmod? If you have clockworkmod then you can flash non htc files. Well actually I am not sure how that would work as you have s-on but clockworkmod. Since I have never been in that boat I am unsure.
So are we talking about the inc or inc 2? If inc I am trying to think back to the desire and what was possible on s-on. If I remember right you can dump the misc then flash a lower version ruu. I just can't remember if it doesn't even flash or if it does and doesn't downgrade the radio. By the way I got it in a pm/here scotty was planning to base helping you off my merge guide. By the sounds of it anyway.
Where the commands are not the same. As the partitions would be different. The misc-image is also not the same so if he had you flash the merge misc it will more than likely bork stuff. I am more than willing to help though. How ever I do not check the forums so you are better off pming me. I will say that nothing will probably work until unrevoked supports the new radio.
Edit: If the incredible works with a goldcard. Dump the misc partition and edit it for the firmware version you want to downgrade to. Then run a lower version ruu. When that is done run unrevoked. Of course I don't have a inc so I am not sure if that will work either. I also jumped a bit to conclusions so sorry for that. I also do not get your one post about the xtc clip here, yet in that other post say the clip doesn't support the inc.

thanks for your input,but rest assured we are in no way shape or form refering to anything to do with drellisdees's guide,your copy of it,or any other files,guides,etc. you have linked or posted on this site or yours.
he allready has root access and a recovery partition.
again,thanks for your input,but please stop confusing the issue with your references to merge guides.

for others watching this,a crude guide is now up on android forums:
http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
root 2.3.4 with unrevoked 3.22 has now been done successfully twice,and 1 has successfully roled back to 2.2.
more testers welcome

Confirmed. Worked for me. Was s on 2.3.4.
Sent from my ADR6300 using XDA App

My Incredible also is S-on with Verizon 2.3.4 OTA and never rooted. I'll give that "crude guide" a try tonight and report back how it went.
I'm just tired of all the low memory notifications and the constant force closes. Hopefully, I can have a custom mod installed tonight if things go well.

SUCCESS!!
Instructions from the website flawlessly for me.
I first rooted the phone. Then I tested it with some root only apps. They all worked. So ideally you can stop here if all you want is root but next OTA will take away root and then you'll be stuck again.
I completed all the steps and they worked. I was able to downgrade to 2.2 and then run unrevoke3 to root and also turn S-off. It did wipe the data clean. No files from my SDcard were deleted.
This is the time i've rooted my phone and the whole process took me an hour because I was being extra careful not to miss any steps. It all went smoothly.

glad it worked out for you. we finally worked out enuff bugs i put it up here as well: http://forum.xda-developers.com/showthread.php?t=1306400
efizzle seems to have dropped off the face of the earth everyone who reads this should make sure to click the "thanks" button in his first post. we wouldnt have it if hadnt figured out the 3.22 secret.(we would still have zergRush,but not root with access and the ability to make nandroids and backups with tibu so easily).
once again,thanks efizzle

Worked like a champ. I did a recovery back to 2.3.4 and it worked as expected. Also brought back all my force close issues. So I used ROM Manager and installed Cyanogen7 and am loving it.
clicking the thanks button a few times for this help

Ok, I'm on Linux, Ubuntu Lucid Lynx 10.04.3 to be exact, and I have adb installed. Where can I find the Linux version of unrevoked 3.22. I have found several places on the interwebz but I'm not sure if I trust those sources.
Help Please
Just like the op I have a Dinc that is on Gingerbread 2.3.4 and baseband 2.15.10.07.07 and desperate to have root. S-OFF would be nice, but root would be just fine for now.
More than happy to be the Guinea-pig on a Linux system.

sorry,i have no idea. i did a quick search and couldnt even find the windows version of 3.22 that i uploaded... i wanted to link it at its source,since it was emailed to me,but im not sure where he downloaded it from. you might follow the link in the first post credits to the original xda thread and ask on that thread,or send efizzle a private message and see if he can help you. in a worse case scenario,as long as you have 3.32 for linux,you could get temp root and downgrade with the "zergRush" method described in past #2. it doesnt require 3.22,but you wont be able to make a backup,or run titanium unless you can push SU,the binary,and busybox to their respective locations after acquiring a temp root.