Develop Bugs

[Guide] Subsidy Unlock, SuperCID, and Radio S-OFF

Update 12-29-10: Due to problems reported with v03, we now link to v02.
Update 12-23-10: A new version of gfree, v02, has just been released by Guhl. Links have been updated to the new version, which allows you to set Sim Unlock, CID, and Radio S-ON/OFF independently. If you have previously run gfree, you will receive no additional benefit from running gfree v2, unless you want to change one of the settings.
Notice: gfree is known not to work for radio firmwares with higher versions then 26.03.02.xx -- the reason for this is that HTC patched the hole that allowed scotty2 to power cycle the emmc chip to drop its write protection. So if you installed a radio version with a higher version number, downgrade the radio firmware before using gfree.
Guhl also released gfree_verify, which allows you to verify your phone's settings (regardless of which gfree you used). See the wiki for more on that.
The wiki is usually up to date on the latest of everything, so be sure to check it frequently.
---------------
scotty2 delivers again!
His "gfree" program should do the following for your g2, dz, or dhd:
* Radio S-OFF -- the real deal. This means the g2 will permit permanent root.
* Subsidy Unlock -- AKA "Sim Unlock" AKA "Network Unlock" AKA "Use a foreign SIM Card"
* SuperCID - enables the flashing of any carrier's firmware for the phone.
If you don't know what this means or why you might want it, check the wiki.
INSTRUCTIONS:
NOTE: If you have NOT permarooted your phone previously with the HBOOT/wpthis method, doing so using the new "gfree" method should have the added effect of sim-unlocking the phone, setting superCID and turning Radio S-OFF. In fact, it's the new method for permarooting for G2/DZ and DHD. So if you haven't yet permarooted, look at those instructions.
Again, the instructions below are for people only who have already previously "permarooted" through the earlier hacked-HBOOT method. See the wiki if you are starting from scratch with a new G2/DZ/DHD and have not yet done anything "root-ish".
WARNING: Be aware that by following these instructions you are messing with your phone with potential for screwing things up. Do so at your own risk. The many authors of this guide assume no responsibility for any damage to your phone, health, general well-being, or anything else untoward with respect to these instructions or you following them.
gfree uses a dynamic in-memory patch of the kernel to remove the kernel's write protection of the radio partition.
So, for those of you who have permarooted the old HBOOT way and put on new kernels --The following kernel versions that are known NOT to work yet with gfree. If you have one of the following kernel versions on your phone install a different (stock, OTA or cyanogen) kernel before starting this procedure:
| pershoots 11/30 build
| pershoot's 2.6.32.26 – OC-UV-NEON_FP (1.516GHZ) – G2 - 12/3
| Cyanogen Kernel / release 6.1.1
| 2.6.32.26-cm-virtuous-v1.0 [email protected]#1
Other newer kernels may also not work with gfree. So if you experience problems with this procedure (either the phone reboots during the process or the procedure completes correctly but the verify still shows that the phone is locked) then you may think about downgrading the kernel to an original stock kernel or even better to this kernel.
Okay. So we're assuming you've permarooted already and usb debugging is on (Applications > Development, then enable USB debugging). You'll also need about 5MB free on your sdcard.
You might want to back up your phone with nandroid on the Clockwork recovery image first, just in case.
Note: If you hanker to do it the longer, manual, harder, and more dangerous way, or are just curious what gfree does, see the wiki history for the old instructions.
No? Then let's begin.
==== 1. Download gfree and verify sdcard is not mounted by your computer ====
You will need to download a program called gfree (v02) that will first copy partition 7 of the phone, then patch it, then reflash back to your phone. (verified to work with the g2 and desire z as well as the desire hd). (You will also need adb, which you can download as part of the Android SDK.)
Unzip gfree_02.zip to your computer.
Make sure your computer is not mounting your phone's sdcard.
==== 2. Run gfree on the phone ====
On your computer's terminal/command line, navigate to where the gfree file is, and then...
Code:
adb push gfree /data/local
adb shell
This copies gfree to your phone, then puts you in your phone's terminal. Then do this:
Code:
su
cd /data/local
chmod 777 gfree
./gfree -f
sync
Wait a few moments for the sync to "take". Then reboot your phone. That's it!
gfree created a backup of your original partition 7 at /sdcard/part7backup-<time>.bin you might consider copying this to a safe location on your computer.
Now you can try using a new SIM card to verifiy that it worked. Also, if you had to flash a different kernel before running gfree, you may now reflash the kernel you originally had.
Thanks to the gang at #g2root, including IntuitiveNipple, scotty2, tmzt, rhcp, ciwrl, and guhl... among many others.
Wiki: How to enable Radio S-OFF, SuperCID, and SIM-unlock (with some informational background)
File: gfree_02.zip
File: gfree_verify_v01.zip
Feel free to use the "Thanks" button below. Also, Scotty2's paypal email is walker.scott AT gmail.com if you want to make a contribution.
Finally, Americans might consider making a donation to the Electronic Frontier Foundation who fight to defend your legal right to root or unlock your own phone when the carriers and phone manufacturers may lobby or otherwise try to stop you. The EFF can always use your tax-deductible support.

Hey thanks for posting this!
So I guess this is like perm-perm-root.
Giving it a shot now.
Sent from my HTC Vision using XDA App

thenefield said:
Hey thanks for posting this!
So I guess this is like perm-perm-root.
Giving it a shot now.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah it's sim-unlock too. Which is nice.

Nice thanks going to try it to.
Sent from my HTC Vision using Tapatalk

shouldnt one image work for every phone

Word up scotty2. You the man.
EDIT: And you too fattire for writing up what no one else wants to

thatruth132 said:
shouldnt one image work for every phone
Click to expand...
Click to collapse
No. If it did, then this would be a lot easier, huh?

I cant wait until some juicy stuff comes out of this.

Now, what does this mean
"make everything better."

This is freaking awesome.

andrewklau said:
Now, what does this mean
"make everything better."
Click to expand...
Click to collapse
You know.... everything.

...
I just bricked my phone LMAO!!!
I did the perm root that was easy... this jeez... followed the [Guide] How to recover your semi-brick (OMFG Thank you guys over there!) BUT I'm back... I literally almost **** my pants. Well... Gonna try this again maybe after finals LOL

Question though (going to try it later tonight LOL =P) the guide says I need a "custom cyanogenmod based kernel and provides the boot image that contains it.. I am using the nightlies do they contain that same function or no? also when I did flash that boot image and ran "insmod /sdcard/wpthis-cyanogen.ko" it said error function not implemented? Anyone not run into this issue? or have any ideas?

nycjv321 said:
Question though (going to try it later tonight LOL =P) the guide says I need a "custom cyanogenmod based kernel and provides the boot image that contains it.. I am using the nightlies do they contain that same function or no?
Click to expand...
Click to collapse
Nope.
nycjv321 said:
also when I did flash that boot image and ran "insmod /sdcard/wpthis-cyanogen.ko" it said error function not implemented? Anyone not run into this issue? or have any ideas?
Click to expand...
Click to collapse
"Error function not implemented" means it worked.

well this time it didn't brick... I think I got it time to verify it

Ok I ran it all again and worked but when I was verifying it I got all the supposed feedback except at "echo -e 'AT$QCPWRDN\r' > /dev/smd0" I got AT$QCPWRDN and then +CME Error: 0.... (No OK as said in the guide? ) and then it rebooted? what didn't work?

Got it to work!
SuperCID, Radio S-OFF, Subsidy Unlock is a reality!
Thanks to scotty2.
Thanks also to guhl (guhl99).
Read my post for more details: http://forum.xda-developers.com/showpost.php?p=9495073&postcount=363
Thread: http://forum.xda-developers.com/showthread.php?p=9495073#post9495073

This may be a stupid question but doesn't 0 also equate to no error? (In my older post) (Its just not stated in the guide, I don't want to overlook something which is why I asked ) You guys are AWESOME!!!

nycjv321 said:
This may be a stupid question but doesn't 0 also equate to no error? (In my older post) (Its just not stated in the guide, I don't want to overlook something which is why I asked ) You guys are AWESOME!!!
Click to expand...
Click to collapse
After entering the following into ADB Shell command prompt:
# echo -e 'AT$QCPWRDN\r' > /dev/smd0
The reply I got was a bunch of numbers (which filled the screen and wrapped to a new line) from what I can recall and then the phone rebooted. I didn't save the command window so I don't have the full details.
When the phone re-booted, I get signal from the local Thailand carrier AIS using a pre-paid SIM card.
The first time I went through the process I made a mistake setting the following using the Hex Editor:
"...set the 4 bytes at 0x807fc to 49 53 F4 7D"
The second time around I figured out what the "c" in "0x807fc" meant in terms of location on the Hex Editor. That was it.

:O i cant believe how awesome scotty2 is...

Prem Root MyTouch 4g 0.86.0000 bootloader!

Alright kids I'll try to make this a simple as possible those of you that are scratching your heads and wondering why you cant get S-on to say OFF..... on the newer MT4G with bootloader 0.86.0000 HERE WE GO.
Step 1:
Download Androzip,Terminal Emulator,Root Explorer and Superuser
Download - Visionary11(yes its an old build, but its simple and less confusing for you noobs.)
Once you have these apps put them on you MT4G homescreen page(doesnt matter in what order just as long as these apps are quickly accessible to you.)
Step 2:
Make sure you go into Settings on your MT4G.
now that you have selected Settings select Applications Make sure that Unknown sources has been selected
On the same Settings screen you will also see Fast boot Make aure to deselect it!
Once the Fast boot has been deselected, select the Development you be transfered to another screen the only items that should be selected is USB debugging. Once you have finished this go back to you home screen.
Step 3:
At this point you should be at the home screen with all the apps you downloaded in Step 1.
Now Select Visionary, once Visionary is open select Set system r/w after root.
Now press Root Now!. let Visionary temproot your MT4G(CAN TAKE UP TO 10-30 SECONDS BE PATIENT!)
Ok that part is Done. go back to your home screen.
Step 4:
Select Terminal and type - su you should see "Terminal Emulator has been granted superuser permission", it will be a real quick pop up saying this. Ok you are now temp rooted. go ahead and select the hardkey arrow and press it until you get to the home screen.
Step 5:
With theMT4G's internet browser find the gfree file on the TRUE PermaRoot and the ULTIMATE S=Off!!! forum
Open the gfree file with Androzip, that you download onto your MT4G NOT with what your computers
unzips this file with!
Step 6:
Once you have Unziped the gfree file from your phone into your phone, you will need to locate and transfer everything that is in the gfree folder DO NOT TRANSFER THE FOLDER ITSELF WITH THE CONTENTS IN IT. Just open the gfree folder and transfer everything inside there. Time to locate where Androzip placed the gfree file
Open Root Explorer scroll down until you see the sdcard file, ok open it!
Scroll down until you see the AndroZip file open it! WALA.... I present to you the extracted gfree scripts. Now that your looking at them, I need you to select the Menu Hardkey Button which is next to your home Hardkey Button. Once you've pressed the Menu hardkey it will options will pop up on your MT4G screen, select Multi-select now select everything inside of the gfree folder.( youll notice the green checks when selecting ) you will also see another option of commands, select move
Now with move selected, navigate those files with the arrow hardkey on your MT4G to /data/local and paste them in that location. Done with that process! close your Root Explorer and return to your home screen.
Step 7:
Open Terminal Emulator and type the following:
type "su", and hit enter
type "cd /data/local" and hit enter.
type "chmod 777 gfree" and hit enter to make the program executable.
type "./gfree -f" and hit enter.
Wait for the program to finish and then reboot into HBoot you'll see that S=Off. Also, check your bootloader version. If it says s=off and has bootloader version 0.86.0000 it worked!
You will need to run visionary11 again (w/set system r/w after root checked and then press Root Now!) to make root privileges permanent and then reboot again. Now "su" should work properly for you.
This will work 100 percent if you read these instruction very carefully and follow these steps exactly!

Thats the same instructions from the gfree thread.
How is this different?

if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help

mine had bootloader 86 and it rooted just fine. People just need to follow the directions better.

easeback said:
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
Click to expand...
Click to collapse
My phone has 86. Bootloader and it took me bout 15 min using gfree method still has 86. Bootloader i didnt do eng but root was easy as pie
Sent from my HTC Glacier using XDA Premium App

He took out the the extra talk and just put it very simple it shouldn't take no more the 5 min to do

easeback said:
if this is the same then why the hell are people not getting it?! im seeing a lot of people regarding that the newer MT4G with bootloader .86 is extremely hard or damn near impossibly to S-off if this doesnt explain how to do it in lamens term then these people are true NOOBS and should stick with their STORM 2 stick with the basics and not with the FAKE Sh**t!. just trying to help
Click to expand...
Click to collapse
this thread is beyond unnecessary.
i told those guys over n over they were doing it wrong lol. my phone came with .86 also and never had any issues.

Hes just trying to help but, it doesnt matter how many people post this, some of them still don't know how to follow instructions. Thanks for helping the noobs.
Sent from my HTC Glacier using XDA Premium App

Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.

TeeJay3800 said:
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
Click to expand...
Click to collapse
Version 0.86.0000 is what ur phone comes with u have yhe eng
Sent from my HTC Glacier using XDA Premium App

elry567 said:
Version 0.86.0000 is what ur phone comes with u have yhe eng
Click to expand...
Click to collapse
I have the engineering bootloader? I don't know how that's possible since I never changed it. I just rooted and installed CWM.

TeeJay3800 said:
Call me naive, but where do I obtain version 0.86.0000? My phone has 0.85.2007.
Click to expand...
Click to collapse
You have the eng bootloader. Your better off with it.

Yes, ALL the MT4Gs (at least all the ones I've seen) come with the 0.86.0000 bootloader. There shouldn't be any reason for this preventing you from rooting. The 0.85.2007 is the engineering bootloader. You get this either by manually flashing it (as per the instructions in grankin's true permroot thread) or if you used the root.sh script (such as those of us who followed theunlockr.com's walkthrough).
If you aren't succeeding with the gfree method, either you aren't following instructions properly or something else is interfering. My friend couldn't get VISIONary to temproot, but after uninstalling one of his file explorer apps, all of a sudden VISIONary worked.

Same here. Got mine the 11th of this month and rooted first try no problem.
option94 said:
mine had bootloader 86 and it rooted just fine. People just need to follow the directions better.
Click to expand...
Click to collapse
Sent from my HTC Glacier using Tapatalk

jdkoren said:
You get this either by manually flashing it (as per the instructions in grankin's true permroot thread) or if you used the root.sh script (such as those of us who followed theunlockr.com's walkthrough).
Click to expand...
Click to collapse
The method I used did include running the root.sh script, so that must be how I got the engineering bootloader. Thanks for the info.

TeeJay3800 said:
The method I used did include running the root.sh script, so that must be how I got the engineering bootloader. Thanks for the info.
Click to expand...
Click to collapse
That is correct... The root.sh includes the engineering bootloader within it and it is the better of the 2. I suggest installing it and you will not have any more problems.

SWEET! Thanks! I missed the other 50 threads with these directions!

Just a tip for people having problems rooting using the gfree method. Follow the instructions to the "T" and it works. As for the commands for terminal emulator...copy and paste them to a word document so you can be sure where there are spaces, and make sure that your 0's are not O's and so forth...Don't be afraid to ask for help, there are alot of nice people on this forum that will help you out.

thnx
thanks alot for this, idk why people on xda don't know how to speak in laymans terms, i guess it's to drive the noobies away, i've been around here since cyanogen had 3.0 on the G1, and i shyed away from using the gfree method on my buddies phone since it looked complicated (didn't want to do alot of reading and work) and i was just wanting to do it fast.
this thread simplified things for me so i can know what i'm doing, also i didn't want to download root explorere (dont' wanna pay $4) so i just pushed every file manualy using adb.
"adb push c:/blah data/local"

aalsmadi1 said:
thanks alot for this, idk why people on xda don't know how to speak in laymans terms, i guess it's to drive the noobies away, i've been around here since cyanogen had 3.0 on the G1, and i shyed away from using the gfree method on my buddies phone since it looked complicated (didn't want to do alot of reading and work) and i was just wanting to do it fast.
this thread simplified things for me so i can know what i'm doing, also i didn't want to download root explorere (dont' wanna pay $4) so i just pushed every file manualy using adb.
"adb push c:/blah data/local"
Click to expand...
Click to collapse
ES Filer explorer does what root explorer does as well, but it's free.

Trying to run Ad Free

Hi everyone!
I am trying to make Ad Free from the Market work but it won't. My HTC Desire is rooted with unrevoked (so, not S-OFF, but I've read that it's not necessary. Is it?).
I have tried two different things:
1) Run the program WITHOUT the symlink option enabled. The phone automatically reboots and nothing happens, adds are still shown in all the apps.
2) Run the program WITH the symlink option enabled. The program seems to work and a message appears saying that my phone should now be add free. But, in fact, it is not, adds are still visible everywhere.
I have been looking for solutions in this forum and in Google but I have seen a lot of different procedures suggested by users and I am not sure it would be safe for the phone to try them one by one.
It would be great if someone has been in the same situation and could tell me how to solve my problem.
Thank you in advance.

You either have to be s-off in order for the app to place the modified "hosts" file in /system/etc/ Otherwise you have to have the file symlinked to a specific place on the data-position(this is the place the app places the "hosts" file if you check the option for symlink.)
You can also just push the modified hosts file from recovery
edit: my suggestion is to s-off it, as it makes everything so much easier, and if you screw something up, you can almost always recover your phone without running a ruu.

mortenmhp said:
You can also just push the modified hosts file from recovery
Click to expand...
Click to collapse
I have been trying to do that before opening this thread but I didin't manage to do it successfully. Could you please help me through the process?
Anyway, how could I do the "you have to have the file symlinked to a specific place on the data-position(this is the place the app places the "hosts" file if you check the option for symlink.)" part?

You need to edit the ROM to symlink the hosts file to the /data partition

EddyOS said:
You need to edit the ROM to symlink the hosts file to the /data partition
Click to expand...
Click to collapse
Is there any place where I can get info to do that? I am kind of inexperienced...

don't do it just push the goddamn file in recovery or for god sake please just run s-off.
If you want help pushing it, pm me.
edit: host file added

You need to have s off, this is easy with alfarev!
Sent from my HTC Desire using XDA Premium App

Have been suggested(twice by me), but as you might get from reading his replies, he doesn't want to do that. I guided him through pushing the file though, so the problem have been resolved.

Willem Mulder said:
You need to have s off, this is easy with alfarev!
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
With some help from mortenmhp by private messaging I got it to work without s-off. Anyway, I tried alfarev this morning and it detects my phone but gets stuck in the next step...
By the moment is one thing I don't need, but it would be fine to know what the problem is...

Willem Mulder said:
You need to have s off, this is easy with alfarev!
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
S-OFF doesn't work with all kinds of desire phones ...
some PVT-4 (like mine) cant be S-OFF u may brick it trying so just push files its safer using terminal emulator from market or using ADB
this may help u with commands http://forum.xda-developers.com/showthread.php?t=688820

Well, in alfarev web site they say their software is compatible with PTV4 HTC Desire, but anyway mine is PTV3, so the problem can't be that.

Xgeda said:
S-OFF doesn't work with all kinds of desire phones ...
some PVT-4 (like mine) cant be S-OFF u may brick it trying so just push files its safer using terminal emulator from market or using ADB
this may help u with commands http://forum.xda-developers.com/showthread.php?t=688820
Click to expand...
Click to collapse
Yes it does, or at least it works with all gsm ones for now. From their website:
Supported devices:
HTC Desire GSM (Bravo), all hardware models (PVT4 too)
Click to expand...
Click to collapse
Also no you cannot use terminal emulator to push files, and you most certainly cannot use it to manage files on the /system partition without s-off.
Dj Telo: the most common problems with alpharev is connected to the computer the software is run on. Are you using an emulator to boot the disk, or are you actually booting it?
If the first one is the case, you will need to burn the image and boot it, however, if that doesn't work, you might need to try another computer. Just borrow one, as it is a onetime thing, and it only takes a couple of minutes.
Also make sure your current rom is not using d2sd, d2ext or something similar, as the tool uses the data-partition and may not work with the ext-partition,

I am very sure, you do not s-off to run adfree!!
Did you run "download & install hosts" directly after starting adfree and requested the superuser request to "yes" and "remember"? Which ip do you use?

MatDrOiD said:
I am very sure, you do not s-off to run adfree!!
Did you run "download & install hosts" directly after starting adfree and requested the superuser request to "yes" and "remember"? Which ip do you use?
Click to expand...
Click to collapse
Well as already explained the relevant file (/system/etc/hosts) is placed on the system partition(obviously). And as such it cannot be edited while the system is booted without s-off, so an app won't be able to do so.
So unless the system has been edited to load the file from the data-partition(as in the symlink option i referred to earlier) yes you do indeed need s-off to use the app. However as you might get from actually reading through the thread, the actual problem has been resolved, and currently he is just trying to gain s-off.

mortenmhp said:
If the first one is the case, you will need to burn the image and boot it, however, if that doesn't work, you might need to try another computer. Just borrow one, as it is a onetime thing, and it only takes a couple of minutes.
Click to expand...
Click to collapse
I did burn a CD but it did not work. I will borrow a computer, as you suggest. There's a busy week for me coming but I'll try that afterwards. I'll insist on this thread in case I can't succeed.
MatDrOiD said:
I am very sure, you do not s-off to run adfree!!
Did you run "download & install hosts" directly after starting adfree and requested the superuser request to "yes" and "remember"? Which ip do you use?
Click to expand...
Click to collapse
I did exactly what you say, but adds would still appear. The IP used was the default one.
Anyway, I already managed to make it work.

Can gain temporary root, but Permanent root will not stick.

Hello xda, in accordance with the signup video I have scoured the earth looking for an answer. However I'm not sure how much necro posting is frowned upon here so I thought it would be safer to just start a new thread.
I have an HTC Desire HD from Telus(for use on the Rogers network). I am in the process of rooting it but have encountered a problem. I can gain temporary root on the terminal emulator(Because the $ turns to #) however when attempting to run clockwork flash clockworkmod recovery I get the error "An error occurred while attempting to run privileged commands!"
I get the same error when attempting the "Fix Permissions" so I'm currently at a loss of what to do.
I have the ninja superuser icon in the apps menu however when I open it the screen is blank. I am unsure if this is how it is supposed to be or not. I have seen several references to a permission box that pops up during some of the steps but I haven't seen that at all.
I've tried four separate methods, the last of which coming from this thread http://forum.xda-developers.com/showthread.php?t=954997
I am currently at step B.d which involves running the S-OFF tool and Easy Radio OFF tool. But still clockwork will not flash a backup, and when I restart the phone I can not get super user to work on the terminal (ie by typing su) and must use the rage method to regain temporary root.
Also, I don't know if this is related or not, but when I restart the phone and attempt to boot in recovery mode, the volume buttons don't allow me to select other options, and instead the phone just forces me to reboot normally.
Some more facts:
model HTC Desire HD A9191
Build # 1.32.405.6
Android 2.2
Anymore info I'm probably forgetting just ask away!
So my question is: Can anyone identify what the issue is?
Thanks much for taking the time to read my question.

Does visionary not work for you?
I've seen that alot of success has been gained by doing temp root and perm root through it?
It does sound like the rage method might not be working for you from what I can tell..
I do want to check all the steps you followed before where fine?
Sent from outer space on my DHD running beatmod gingersense v1.3

Visionary was how I rooted mine. Worth a try if you havent tried it: http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/

Thanks for the visionary suggestion, but Visionary still isn't working :/
Has visionary been tested with the Telus Desire? I heard there was a difference. What happens when I attempt to temproot is it moves to a blank screen then goes back to the menu.

When I used visionary on 1.32 it did not always work first try ... generally always worked after 2 runs. then used it to perm root

It works. You do not have Telus software in your phone anymore.
Sent from my Desire HD using Tapatalk

Try my method (I made it because the methods I found for my Telus desire HD were flaky at best and only got temproots from it.)
Since you already flashed to 1.32 start at step 2
If you want to go gingerbread, dl the 2.36.405 ruu and use that and your pc to put 2.3.3 on it (dont worry, it works fine, i was using it since it came out and built a rom based off that, kingdom, and pyramid roms for my own sense 3 rom) and use the gingerbreak method.
http://driphter.com/index.php?topic=3867.0

Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.

lemonpartyz said:
Still haven't managed to get root. JSLEnterprises my antivirus won't let me download your file :/
I'm at a loss for what to do.
Click to expand...
Click to collapse
Disable your Antivirus (Avast say's its malicious), Norton or F-Prot says its clean.
and Internet Explorer 9 says its not trustworthy (because there's .bat files in the zip), Firefox says its fine.
There is no malicious code in the zip, you can edit each individual batch file in the Resource folder to see the code. Its very simple and basic.

I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.

lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Click to expand...
Click to collapse
go into the resource folder, edit the visionary install batch in notepad, delete the "cls" line, save and exit
rerun it with the phone attached. See if it truly installed successfully.

lemonpartyz said:
I disabled my antivirus, but when I run Install Visionary nothing happens. The CMD window opens and says it has been succesfuly installed but nothing has been installed, and nothing appeared in the app menu.
Edit: I went into the resource folder and then followed the steps from there and everything worked, except I still don't have the # symbol in terminal (even when entering "su") and ROM manager still gives me the same error.
Click to expand...
Click to collapse
you dont need to use the termial in my method.
Once visionary is installed, and you run it, and everything is done exactly whats described in my 9 easy steps thread (along with outcomes along the way), then you should be perm rooted, with s-off and eng-off with supercid.

I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML

lemonpartyz said:
I managed to install visionary with your method, however when running Eng-S I encountered the error "Bootloader corrupt, DO NOT REBOOT! Seek help from XDA!"
Help?
Edit: Followed the advice here http://forum.xda-developers.com/showthread.php?p=14936635 and s-off worked properly this time. Hopefully my DHD won't brick on reboot. Could super user be the problem? it never asks me for permissions or anything, all I have is an icon and a blank screen when i open the app.
Edit2: Rom manager took three attempts to install correctly. Still the same result "An error occurred while attempting to run privileged commands!"
FML
Click to expand...
Click to collapse
looks like the superuser application isnt running properly.
I would use the 1.32 ruu (not the pd98img.zip off the sd) and then from a fresh install (without resoring any data other than google account to visit the market)
run through the visionary, s-off tool, eng-off tool, and then reboot again, then install rom manager from the market, run it, it should ask you for permission and may hang for a second, and then say you have about 5 seconds to allow root permissions.
Then install rom's away. if you're not into making seperate rom specific app folders on your sd card, google JSL Er3BuS. its a sense 3 rom without the extra scripts.

How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!

lemonpartyz said:
How do I install the 1.32 RUU if I can't install it from the SD card?
Thanks!
Click to expand...
Click to collapse
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!

I tried following the steps here http://forum.xda-developers.com/showthread.php?t=841890
But got the error "ERROR [120]: Low MAIN BATTERY POWER. When the battery is above 30%.
This is getting ridiculous lol
I'm sorry I'm such a bother.

naailalzuhir said:
It is very easy mate,
1. Download the RUU of your choice from http://shipped-roms.com/index.php?category=android&model=Ace
2. Put your phone in charge mode only with USB debug on.
3. Make sure you have HTC Sync installed on your PC, and close HTC Sync application from your system bar in windows (make sure that HTC Sync is not running as all you need is the driver)
4. Right click on the RUU file and select "Run as Administrator"
5. Connect your DHD by the USB cable to your PC.
6. Click some boxed and "next"s.
7. Waiting!
8. Profit!
Click to expand...
Click to collapse
Tried this, now the update process has taken 45 minutes.

Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help and kind words.
Fingers crossed cryogen works.
I'm going away for the weekend, but when I come back I'll update this thread with the full details of what went down so hopefully someone will be helped by my many many hours spent raging.
-Lemonpartyz

lemonpartyz said:
Well, it took 5 hours to finish, but finish it finally did. Rom manager installed no problem, flashed no problem and I am in the process of installing cryogen. Thanks everyone for their help.
Click to expand...
Click to collapse
Glad its sorted for you , and hoping it status that way...enjoy your custom roms setting your phone free
Look forward to your post letting us know how its going.
Sent from outer space on my DHD running beatmod gingersense v1.3

A new method for ROOTing your xoom!!!

I do not know why you say this...
MOD EDIT: Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
***EDIT***
I have also tried on a HK 3g xoom (which shows MZ601 in MTP but MZ602 in fastboot). It works without any problem, and internal storage preserved untouched.
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.

eddielo said:
Hi,
I am here to provide you a new method in rooting your xoom, it does not require to flash the decrypted boot.img image.
I have tried it only on my Wifi XOOM, which is a UK version. (With a Japan version of ROM, downloaded from Motodev and upgrade to 3.1)
===============================================================
I am NOT a xoom developer, nor a rom cook. I am just a user of xoom, which know
a little on developing and are willing to try new things.
So, I can not be sure that the method below works on your device. By following the
things below, your xoom may have a chance to brick.
I am not responsible for any brick or mulfunction device.
===============================================================
To root your xoom, you should start with flashing your device with the clockworkmod recovery (Please refer to the post by solarnz).
After flashing the clockworkmod recovery, do the following.
1. Download the attached ROOT.zip, place it on the root directory of the external sd card, and rename it to update.zip
2. Restart your device to the recovery by:
Type "adb reboot recovery" from your pc
OR press volumn down ~2 seconds after the motorola logo appears when the device starts,
then volumn up when "-->Android recovery" appears.
3. Apply the update in the recovery.
That's it. Your device should be already rooted.
=======================================================================
I am not the inventor of the method, I think about this since I have a Samsung i9000,
and the method of rooting the i9000 is by applying a update.zip file.
I have created the ROOT.zip file by changing the i9000 root zip file with the newer su and superuser.apk (From here: http://forum.xda-developers.com/showthread.php?t=1010568)
I have also changed the updater-script in order to let the updater mount the correct partition for the update.
I am not sure if this update applies to other devices (especially for the 3g ones). This should work if the system partition have name "/dev/block/platform/sdhci-tegra.3/by-name/system".
I would like to thank solarnz for providing the clockmodwork recovery for xoom,
the one who invented the method of rooting the i9000 with a update.zip (I cannot find who make that, sorry...),
and also Xaositek for providing the su and superuser.apk files (I am too lazy to find it by myself...).
========================================================================
That's all. Please try on your device (especially for those stock 3.2) if you would like to take some risk, and report if it is success or not.
Thanks.
Click to expand...
Click to collapse
How do you flash cwm if your device if locked? Also the purpose of the rooted boot.img is to allow you to mount your device for adb commands.
Sent from my PG86100 using Tapatalk

yeah no offense but this sounds a little sketch... I see you make a quote at the bottom asking people to report success if they try... I personally would not try this.
Unlocking and rooting is really not that hard and not very time consuming using current methods

Of course, for installing CWM, you have to unlock your device by using "fastboot oem unlock", but that will not brick your device anyway.
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Also, for the current rooting methods, it is not 100% work on some device (like the HK 3g version, which reported missing of internal storage after rooting with currently available method), I would like to see if this work on that.

Rooters beware. Proceed with extreme caution, as these are highly uncharted waters.

eddielo said:
For this method, you do not need to issue adb commands to root your device, so no need to have a modified boot.img.
Click to expand...
Click to collapse
I think you missed my point. Rooted boot.img isn't used for rooting. Its used for adb commands like adb remount. Say i want to adb push a file to my xoom, ls a directory on my xoom, or adb rename system files. Those are all reason you need the rooted boot.img.

Sorry, this is not a rooting method. All what this is doing is flashing su, busybox and Superuser.apk.
There is more to rooting a device than this. You also need an insecure boot image.

I am sorry if I do not catch the real meaning of rooting a device.
What I think of rooting is to let my device, starting from everything stock, untouched, to a state that applications that need root, like Titanium backup or root explorer, works without problem.
I have tried on my two devices with this method, titanium backup works perfectly, root explorer can remount the system partition to rw and can successfully copy files and delete files from that.
The insecure boot.img image, as far as I know, provides everyone to use "adb remount" and make changes to the system directory. But my method do not need adb in copying the binaries and chmod them. You may call it flashing, but after that, su works without problem.
Please, try it first. If you think it is not a method of rooting, I am sorry about that.

Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.

So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App

roughneckboren said:
So does this mean just "rooted".....like can't flash a rom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Rooting has nothing to do with installing a rom. To install a rom, you just need to unlock and fastboot flash CWM. This guide in noway helps you flash a rom.

alias_neo said:
Actually guys, don't dismiss him just yet, over in the Galaxy S II forums we only flash insecured images long enough to root the OS then flash back to a secure one, so you have root access but no remount or system r/w.
It's a (fairly) legitimate method and is exactly how I rooted my xoom this time round, well not exactly, I did it like this:
unlock
flash solarnz CWM
adb mount system r/w
push su and busybox
reboot
install superuser from market
done
This is how most people run their GSII and means you can use root apps but no insecure boot image (because the GSII shows a warning on every boot with insecure images and keeps a binary flash counter, cheeky samsung).
This will at least get you to the point where you can su from within android and dump your boot image to modify it yourself, which is what I just did to update my Euro 3G root guide.
Click to expand...
Click to collapse
Without an rooted boot.img your recovery will get wiped out every time you boot the OS.

So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?

silvinoa said:
So will this let you make a titanium backup of your data? That way you could recover your data after using the regular unlock method that erases everything?
Click to expand...
Click to collapse
Yes and NO...
Yes this method will allow you to run titanium backup. But to use this method you have to unlock, which erases everything.