Database Info

How 2 Root 1.33.0006 SPL & Flash SPL || MyTouch3G / 32B Magic || Without Goldcard ||

How 2 Root 1.33.0006 SPL & Flash SPL || MyTouch3G / 32B Magic || Without Goldcard ||
Tutorial : Rooting the "perfect" 1.33.0006 SPL & Flashing a new SPL
Newb Difficulty Level: 5/10 (A learning android newb)
Advanced Root User Difficulty Level: EASY!
GIVE CREDIT WHEN ITS DUE!
Note to readers:
I actually found a easy fix for 1.33.0006 for 32B Magic or MYTouch3G phones
KEEP IN MIND THAT I AM USING A MERLOT MYTOUCH3G, Stock 4GB SD card & BROKEN "Market" Application SO MAKE SURE YOUR DOWNLOADING THE FILES THAT WORK BEST FOR YOUR DEVICE and I am only providing steps used to bypass the "PERFECT SPL 1.33.0006" & YOUR RESPONSIBLE FOR THE RESULT OF YOUR DEVICE!
FILES I USED:
*ADB is a MUST so make sure to watch this video to safely install ADB
(NOTE: The video is using 1.6 donut spk... the steps are the same but use the 1.5 r3 spk on the same page given on the video.)
*flashrec-20090815.apk
MAKE SURE YOU USE THIS VERSION...!
* "Rooted" Recovery Image
I am using Amon_Ra's recovery-RA-magic-v1.2.3G which in my opinion is the best as it has flashed every rom perfectly if you know what your doing but it depends on what rom you will be flashing in some cases.
* A NEW SPL!
I am currently using Engineering-SPL-HBOOT-1.33.2009-signed by Amon_RA (BIG UPs TO Amon_RA for these files) on my T-Mo MyTouch3G but it depends on your device.
NOW TO WORK!
Step One - Enable USB Debug/Development Mode:
*Load up your device till you reach your home screen. Once your device is up and running hold menu and go to settings>applications>development then enable "USB Debugging" then press home & plug the device up to your PC & DONT MOUNT.
Step Two - Install Recovery Image Loader via ADB:
*Open CMD and as the video above stated you must navigate to your ADB folder. Once that is done you should install flashrec-20090815.apk (Recovery Image Loader) though CMD by placing it on both your SDCARD & the ADB Tools Folder (For me its C:\android\tools\).
~Now type these commands within CMD:
cd c:\android\tools (press enter)
adb install flashrec-20090815.apk (press enter)
*Now you have installed Recovery Image Loader and you may now close CMD but dont restart your device
Step Three - Rooting the unrootable (Sorta):
*Now find your recovery image ( Example : Recovery-RA-Magic-v1.2.3G.img or Recovery.img). Once found rename it as "cm-recovery-1.4.img"! Save this file to the root of your SDcard & delete the "flashrec-20090815.apk". now press backup recovery image and wait till its done (quick 2secs) then erase everything but "cm-recovery-1.4.img" within the text box. Now type " /sdcard/cm-recovery-1.4.img ". Now press FLASH RECOVERY IMAGE and wait till its done. Once its done restart the device and be aware that you will lose everything that isnt saved to your google account or backed up to your PC.
SMART COMMENT: WOW DID I JUST ROOT THE UNROOTABLE? I guess I did lol
Step Four - Change SPL to Prevent this issue in the future:
*Move the SPL ( & the ROM if you want to start installing it right away ) you downloaded earlier to your SD card and delete everything else if you want. Now select "WIPE/FACTORY SETTINGS" and follow on screen instructions and then do this a additional 2 times to be safe. Now flash the SPL and once it starts to reboot on its own (after it shows the picture of a box and a device) hold the home button and then FLASH YOUR ROM
THATS IT! YOUR DONE AND YES I DID SHOW YOU HOW TO ROOT 1.33.0006 but it doesnt run properly so make sure you flashed a new SPL before flashing any new "Radio" or "ROM" images or you could brick your device.
HOPE THIS HELPED MANY WHO HAD PROBLEMS ROOTING THE DEVICE!​

isn't this just the same as the one click root? cuz on the one click root you don't need adb. It just seems like you are adding necessary steps to it. Please correct me if I am wrong. I don't mean to bash your work by any means.

I don't see why no one else has congratulated you on compiling one of these for those people that might eventually NEED THIS GUIDE! Lol.
Great work. Simple.
I had the "perfected SPL" when I picked up my MT3G on the release date. Pretty unfortunate...but I rooted it like two days later. Lol.

I never got an answer in the other SPL thread so here it goes...
Can we safely go from one SPL to another?? The reason I ask is I have the problem with the blurry screen at boot but I only encountered it when I flashed a new SPL. Now I have read up on it & it looks like some people running the same ROM with different SPL's don't have the blurry screen.
Seeing how so many people had problems bricking with haykuro's DangerSPL, the SPL is something I don't wanna mess with unless I have a definate answer. So anyone wanna chime in on this?

Beast84 said:
I never got an answer in the other SPL thread so here it goes...
Can we safely go from one SPL to another?? The reason I ask is I have the problem with the blurry screen at boot but I only encountered it when I flashed a new SPL. Now I have read up on it & it looks like some people running the same ROM with different SPL's don't have the blurry screen.
Seeing how so many people had problems bricking with haykuro's DangerSPL, the SPL is something I don't wanna mess with unless I have a definate answer. So anyone wanna chime in on this?
Click to expand...
Click to collapse
yea... could i go from 2005 one to the 2009 one? any help there?

bogdi1988 said:
yea... could i go from 2005 one to the 2009 one? any help there?
Click to expand...
Click to collapse
@Everyone above (excluding Reignzone)
Lol really? okay try flashing 1.33.0006 haha
It wont be as easy as you all think
@Reignzone
Thanks

Azuske said:
@Everyone above (excluding Reignzone)
Lol really? okay try flashing 1.33.0006 haha
It wont be as easy as you all think
@Reignzone
Thanks
Click to expand...
Click to collapse
No, you are right it won't be, but if you downgrade back to cupcake, you can one click again. Anyway, nice post man. Great job.

Thanks
Thats exactly why I posted this because I had a hard time getting back to cupcake because of the spl

Hello there, thanks for the guide.
I try to follow your guide to root my HTC Magic and I have some questions.
1. I run the command "adb install flashrec-20090815.apk " and it installed the flashrec to "/data/local/tmp" directory. Is this correct?
2. I copied the recovery image to the sd card and insert into the phone. then based on you guide. I should delete the flashrec I installed while ago. But I cannot delete the file. Can you give us more details regarding this one? Thanks.
3. Sorry but I have some hard time to sollow the step three. Can you give us more details about this.
thank you and good day
Steven

To be 100% honest im not sure where it is saved... i just happened to run into a working solution at random.
I do know that the older version i tried (Recovery Image app) didnt want to install

Reignzone said:
I don't see why no one else has congratulated you on compiling one of these for those people that might eventually NEED THIS GUIDE! Lol.
.
Click to expand...
Click to collapse
Umm because it doesn't do anything. flashrec ANY VERSION does NOT work on a phone with 1.33.0006

scrufy Originally Posted by Reignzone I don't see why no one else has congratulated y for those people that might eventually NEED TH. Umm because it doesn't do anything. flashrec ANY VERSIO phone with 1.33.0006 Today 03:28 Pm. Yes it did for me. at least in cupcake.I'm not sure in donut.guess you have to downgrade to cupcake.

scrufy said:
Umm because it doesn't do anything. flashrec ANY VERSION does NOT work on a phone with 1.33.0006
Click to expand...
Click to collapse
LOL WOW he had the same problems dude and he is a developer...
Maybe you did something wrong when installing it

Azuske said:
@Everyone above (excluding Reignzone)
Lol really? okay try flashing 1.33.0006 haha
It wont be as easy as you all think
@Reignzone
Thanks
Click to expand...
Click to collapse
So basically what you're saying is you don't know?? If you don't, that's cool. But don't laugh & then not give an answer. Just makes you seem arrogant, like you feel better than us. Which, by the way, YOU AREN'T!

Beast84 said:
So basically what you're saying is you don't know?? If you don't, that's cool. But don't laugh & then not give an answer. Just makes you seem arrogant, like you feel better than us. Which, by the way, YOU AREN'T!
Click to expand...
Click to collapse
Sorry if you took it that way but that isn't what runs through my head when I laugh or anything... My bad -_-
ANYWAY I only know what I posted... I am a learning newb and I am getting better at this stuff as I go. My tutorial explains exactly what I did.
EDIT:
P.S. My smartass comment was for the people that was calling this useless just because they didn't experience this issue

Azuske said:
Sorry if you took it that way but that isn't what runs through my head when I laugh or anything... My bad -_-
ANYWAY I only know what I posted... I am a learning newb and I am getting better at this stuff as I go. My tutorial explains exactly what I did.
EDIT:
P.S. My smartass comment was for the people that was calling this useless just because they didn't experience this issue
Click to expand...
Click to collapse
Eh no hard feelings, I was just looking for a straight answer. I just wanna get rid of that damn blurry screen, thats all. Thanks for the step by step tho. I did it the easy way with one click root but I did my G1 the hard way so I know how frustrating things can get. Thanks again

i was able to flash SPL 1.33.0006
I had rooted my MYTOUCH 3G in August using the one-click method. I have been running several ROMS since then. But I never tried to flash a new SPL. However, after reading this post I decided to give it a try. I booted into recovery mode/ wiped and then flash 1.33.2009 SPL. It loaded and rebooted into recovery again. I then wiped and loaded a ROM. everything is fine.
Later I checked and I now have 1.33.2009 SPL the perfect SPL 1.33.0006 is gone.

so im on a rooted mt3g, i have been running different roms, cyan, hero, dwang, i am at dwang 1.13. so to flash the 1.33.2009 spl do i have to wipe and flash to dwang 1.12 then flash the spl then dwang 1.13?
also what are the advantages/disadvantage?
which spl should i use?
thanks

Hi
I have 1.33.0004 on my 32B Sapphire and Android 1.6. Will this method help me root my phone? If not then is there an easy way to root my phone?
Thanks in advance

Is there no hope for 1.6 users on a UK voda magic?

Hi folks.
I am desperate to get Cyanogens mod on my phone but I can't downgrade to 1.5 because i'm on 1.6 with a UK vodafone Magic (32B).
Any chance a serious andoid expert could step in and tell me:
Will there be a new image made to fix this issue?
is there a method I will understand? It says on the Cyanogen Wiki that there has been "some success" with my version but I can't find where it says how to downgrade for my version
I keep hearing about gold card or summink but i'm a noob and I don't have the foggiest idea where to start.
Please help!! and try to make your responses understandable

Dont worry...
Hi there
I think is possible what you're trying to do, but in order to change your rom you don't need downgrading nowadays (HTC are not PSPs, hehe).
I have a magic from Vodafone ES, and what you have to do first is check your model, can be 32A (HTC) or 32B (Vodafone, less ram in cell phone), so you'll probably have 32B like me.
After this, you need Android SDK and drivers to connect your device usb, load a modified SPL via ADB/fastboot (there's a thread in the forum with the HBOOT collection, you need one of those in your cell in order to change the rom).
Summarizing:
1. check if 32B
2. get Android SDK to use the commands fastboot/ADB
3. replace SPL
4. continue with the cyano's wiki
I followed this: http://www.htcmania.com/showthread.php?t=74683 (sorry is in spanish and a bit outdated, but the apps you need like the SDK are in there, and you have some screenshots, you can skip the root part since cyano's mod is rooted already).
About the goldcard method, I dont know because mine hadn't had perfect SPL, I only had trouble with the usb driver, and downloaded HTC sync (look for it on google if you need) and adb/fastboot detected my device.
A good idea is to install a recovery image once you change your SPL, I personally recommend Amon_RA's recovery 1.5.2.
Last but not least, these explanations are the basics, I know it sounds like chinese to you but read more posts in the forum, there's a cyanogen flashing guide as well, with all the information and these steps you'll do fine.
Hope you'll succeed, let me know your issues

I do understand reasonably well but you cannot use the guide on here with a UK magic as the SAPPH.img file or whatever has an incorrect ID. it's at this point the process cannot be completed.
Thanks so much for your lengthy reply but in this case I believe my phone is unique and the problem cannot be be as easily resolved as you suggest. I must downgrade to 1.5.
Are any of the extreme android geeks able to shed light on this?

I can shed light on you as I have a Vodafone HTC Magic 32B. I used the instructions at the link below and got my phone back to Cupcake, but oddly enough I used the MyTouch instructions and searched online for a suitable sappimg.nbh file as the one they provided didn't work for me. Now I am running Qteknology MagicSense Hero ROM with working LEDs. Forget about ADB, SDK and the Goldcard method... I am sure you want the simplest way to unroot so you can get back to 1.5 and the reroot to whatever you like. Here it is: http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/

This is great news but I have tried that method with the sappimg.nbh and it says incorrect ID every time.
Are you using a UK vodafone magic then? If so, where did you find a SAPPIMG that worked?
Please try and remember!

It doesn't matter that your phone is a UK Vodafone Magic.. if you google sappimg.nbh and download a few until you get the one you need you will have your phone reverted back to it original state... ready to root. If you stop your search after one attempt you will not have done all you needed to do. You don't have to know any codes or get another SD card.. just put some effort into it from your computer. Google is your friend.

but being a bit of a noob to all this, surely trying sappimg files at random might risk bricking my phone? I heard there was a good sappimg for all but my version of the phone which is why I mentioned it.
Maybe someone on here has a sappimg known to work with my phone?
But yes, i'm off to do some intense googling.
Thanks

Hi
I have a UK Voda Magic and I followed this http://forum.xda-developers.com/showthread.php?t=579328 and worked perfectly for me

It truly is lovely of you all to try and help and I appreciate it but I suspect you have not read my comments properly.
Those of you that have commented here were only able to get it to work because you were flashing from/rooting from a 1.5 cupcake build. Once the OTA 1.6 donut update is on a UK magic it cannot be downgraded and so all comments thus far are superfluous. contrary to other comments it is necessary to flash SAPPIMG.nbh first and this does not work on my phone - incorrect CID.
Is there anyone on here that can help with MY issue?
Thanks.

Strange, because I have no issues flashing UK Voda 1.6 phones, just fastboot and use ADB to load recovery image, then flash whatever 32B ROM I like (Dwangs 1.17.1 is great). I did a work collegues before Christmas and his phone had never been modified, only received the OTA update from 1.5 to 1.6 around October time.

I'm on it. That's the way I used to flash roms back when i first got my magic. Now i've been thrown by all the simple guides to put cyanogen and I thought the sappimg method was the only way. I'll just download the sdk and get on my merry way

I don't understand what the issue is? I have a UK vodafone 32B and have been flitting between CM's mods, Hero mods backwards and forwards with no issues whatsoever?
I'm on CM's latest right now (well, a few back now 4.2.11 latest), just followed the instructions and it worked....?

I certainly did read your OP correctly and I also was on 1.6 when I followed the link I posted. In that link it has instructions on how to do it if you are on 1.5 OR 1.6

Started out with 1.5 Vodafone UK Magic which i've flashed many times using the fastboot boot cm-recovery-1.4.img method.
At one time i went back to stock 1.5 but let it update itself (OTA) to 1.6. Since then i've continued to flash new ROMs without problem.

Alfieg said:
but being a bit of a noob to all this, surely trying sappimg files at random might risk bricking my phone? I heard there was a good sappimg for all but my version of the phone which is why I mentioned it.
Maybe someone on here has a sappimg known to work with my phone?
But yes, i'm off to do some intense googling.
Thanks
Click to expand...
Click to collapse
hi alfieg
ive vodafone magic 32B with donut and perfect SPL, in present day, I tried all the guides and methods in many forums, without success, for example, if you follow the guide in wiki cyano, already the first step there are problems, how I try to update with sappimg. (cupcake 1.5) as the ends' update writes "main version is older," "update failed "... if you do not then a way to get cupcake is impossible to have root on magic 32b with donut and Perfect spl ....
Indeed in the wiki says, if you have donut Downgrading to 1.5 FAILED: HTC Magic Vodafone ES (Spain) (32B) Official 1.6 updated OTA "
wait a few geek we solve the problem ...

I don't see what the problem is. You should have been reverted back to 1.5 and flashing new ROMs. The instructions are simple.. someone else has done all the hard work.. all you have to do is download a file and hold your phone.

blackvyper said:
I don't see what the problem is. You should have been reverted back to 1.5 and flashing new ROMs. The instructions are simple.. someone else has done all the hard work.. all you have to do is download a file and hold your phone.
Click to expand...
Click to collapse
download a file, to make what? If you can not root for real?

Will you lot please listen to me!
There are two methods reccommended:
1) Flash the SAPPIMG.nbh to downgrade back to 1.5 - this does not work on a UK magic on vodafone 32B at all! It reports Invalid CID, update failed!
2) use the fastboot boot cm-recovery-1.4.img via the SDK - This does not work on my phone! - I have the device listed when I use "adb devices" so the drivers are ok but it hangs at <Waiting for device> when i try to fastboot boot cm-recovery-1.4.img!!!!!! No ammount of killing the server and remounting as per the cyano instructions works!!!!! in fact, it wont let me remount (Operation not permitted)!!!
If you don't understand please don't post. People who have not updated to 1.6 OTA and people who don't have a UK voda 32B - stop posting here.
Grrrr

No need to downgrade
Alfieg said:
Hi folks.
I am desperate to get Cyanogens mod on my phone but I can't downgrade to 1.5 because i'm on 1.6 with a UK vodafone Magic (32B).
Any chance a serious andoid expert could step in and tell me:
Will there be a new image made to fix this issue?
is there a method I will understand? It says on the Cyanogen Wiki that there has been "some success" with my version but I can't find where it says how to downgrade for my version
I keep hearing about gold card or summink but i'm a noob and I don't have the foggiest idea where to start.
Please help!! and try to make your responses understandable
Click to expand...
Click to collapse
I have a New Zealand Vodafone Magic 32B and they share the same Hboot 1.33.0004 (SAPP10000) SPL with the UK (and NL and AU) vodafone phones. That means they are VERY easy to load alternate ROMs onto. The horrible stuff many Americans and others have to go through to root their phones isn't required for us.
You do need to get the Android SDK installed and talking properly to your phone.
Assuming you have the SDK set up and you can see your USB-connected phone listed when you enter the "adb devices" command, then the rest should be easy. See the Cyanogen Mod wiki for the details. You want the section on "non-Tmobile 32B magics" on this page:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod
It starts with:
"Non-TMobile 32B Magics
If the above doesn't work for you, don't despair. Some non-US Magics are shipped with a fastboot compatible SPL installed. If you see 3 skateboarding androids when you boot to fastboot, you should be able to do the following:"
..............
This is the part you want to pay attention to, assuming you have the SDK installed properly. Our phones are actually MUCH easier to load others ROM on because we have those fastboot-enabled SPLs already in place and this is the first, BEST way for us to do it.
Whatever you do, do NOT flash the "Danger SPL". There is no need to for an HTC Magic with the Hboot 1.33.0004 (SAPP10000) SPL.
If you're hopelessly lost at this point, seek hands-on local help. You don't know enough to do this by yourself without risking screwing up. if no one can help you, then take your time. Learn the stuff you need to know....Being in a hurry is a great way to go wrong. I spent 3 months reading and thinking about it before I loaded my first ROM. Much of the advice is for the Dream / G1 or locked MyTouch3G or Magic 32B phone from telcos who lock them....and simply isn't relevant for the HTC Magic 32B from Vodafone. the single section I'm pointing you to above is all we need to get it done.
Finally, here is my own "simple guide" for getting loading alternate ROMs on a Vodafone HTC Magic 32B. This is about OUR phone...and should work if you work your way through it.
http://truthseekernz.blogspot.com/2009/11/simple-guide-to-loading-new-roms-on.html
You don't need to worry about "gold cards" and all that stuff. You'll be flashing an already rooted ROM and you will have backed up your un-rooted original load with "nandroid" before you change ANYTHING. That backup is your path back to the way your phone was before you rooted it by flashing an already rooted system ROM. in loading ROMs like Cyanogen's you're not baking a cake, you're buying one....so you don't need to know how to make one, you just need to know where to get one and how to serve it....if that analogy makes sense.
Simply, you start by: fastboot boot RA-recovery-1.5.2G.img:
Then, from the recovery menu of functions you do these steps:
1. Backup (nandroid)
2. Wipe system / data
3. Wipe cache
4. flash from any zip on sdcard (the one you want to flash today, you may have put several different ROM images in /sdcard)
5. reboot to brave new world.
6. Make a backup copy on your PC of the /sdcard/nandroid folder on your sdcard so you won't lose it accidentally if your sdcard is corrupted, lost or stolen.
Done.
To save time and let you backup / flash ROMs anywhere you happen to be standing, you can flash Amon-RA's recovery onto your phone or you can load it via fastboot every time and leave the default recovery in place. The very first nandroid backup you made will have backed up the factory recovery image as well as the factory system image as they were at the time you backed them up. So they can be restored if you want to at some point update them with an OTA update. I suspect Vodafone / HTC will be rolling out an Android 2.0 / 2.1 update to Magic phones at some point. If they don't that would be a black mark against them....something to remember when thinking about buying any future phone from anyone: "WILL THEY SUPPORT IT FOR THE SAME 2 YEARS YOU'VE SIGNED UP FOR".
If the answer isn't YES......then that's worth remembering. Vodafone / HTC's record so far is good. The last OTA update was barely 3 months ago.

Alfieg said:
Will you lot please listen to me!
There are two methods reccommended:
1) Flash the SAPPIMG.nbh to downgrade back to 1.5 - this does not work on a UK magic on vodafone 32B at all! It reports Invalid CID, update failed!
2) use the fastboot boot cm-recovery-1.4.img via the SDK - This does not work on my phone! - I have the device listed when I use "adb devices" so the drivers are ok but it hangs at <Waiting for device> when i try to fastboot boot cm-recovery-1.4.img!!!!!! No ammount of killing the server and remounting as per the cyano instructions works!!!!! in fact, it wont let me remount (Operation not permitted)!!!
If you don't understand please don't post. People who have not updated to 1.6 OTA and people who don't have a UK voda 32B - stop posting here.
Grrrr
Click to expand...
Click to collapse
Get latest version of fastboot binary. I had problems with original one and htc magic. Drop fastboot.exe into the sdk tools folder.
Reboot your phone holding back and power simultaneously.
Then plug usb cable.
in Dos prompt go to sdk tools folder and type "fastboot devices"
if your device is listed you are good to go.
then "fastboot boot cm-recovery-1.4.img"

**SOLVED** Consolidated Info to HOPEFULLY Root Rogers 3.05.631.7 ROM-updating via RUU

(If ROM installed via official HTC RUU- RUU_Sapphire_Rogers_WWE_3.05.631.7_R_release_signed_NoDriver.exe)
UPDATE!! **SOLVED** April 25, 2010
Download new RUU
http://www.multiupload.com/XQEH9NVGY7
Flash with Goldcard method http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
1. Download RUU linked above.
2. Install update using RUU.
3. Turn on phone and connect to computer.
4. Get RA recovery and SPL also linked above and drop them to sdcard root directory.
5. Run SDK: adb shell
6. Install recovery: flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img http://forum.xda-developers.com/showthread.php?t=561124
6. Turn off phone and turn on again holding Power+Home. RA Recovery should appear.
7. Flash zip from sdcard.
8. Use file: update-hboot-1762007-signed
9. Done. PSPL broken.
10. Build a shrine for orange_24
****************************************************
**Not Successfully Rooted: Feb. 2, 2010 (AFAIK)
I decided to start this thread because the info for again obtaining root, for those of us dumb enough to update to the official Rogers ROM 3.05.631.7 via the RUU, is all over the place in about a million different threads. My hope is that we can organize it all in 1 place.
At this point, yes, we all know we were impatient and newbs and everything else. Ok, lesson learned. So, lets move forward and try to get this thing rooted.
If you are a developer who has the talent to help root this ROM and have lost interest in the Magic or moved on to the Nexus One or Droid, we ask that you please try to spend a few moments on this and help out those of us who are really stuck here. Personally, I'm getting pretty desperate and thinking of even replacing the phone.
Please post what you've tried in attempting to again obtain root, your failures and hopefully successes.
*One Click Root: http://theunlockr.com/2009/08/29/how-to-root-the-htc-magic-in-one-click/ Cant' back up Recovery.img Error(Tried clicking the hidden Star next to "Back Up Recovery" and skipping this step...and just flashing recovery-RA-sapphire-v1.5.2H.img. Didn't work either) Tried with Amon_RA Hero recovery.img also, without success.
*Tried downgrading to Rogers' last official ROM via the RUU for (Rogers)_RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed. Attempted several times both with and without a goldcard installed.
*ADB: Will see the device, initially, but a command of "adb remount" kills the connect. same with "adb root" **EDIT
*Fastboot: Error- Does not allow access
*Relentless Rooter: http://forum.xda-developers.com/showthread.php?t=556200 No luck obtaining root
*Fix Perfect SPL: http://forum.xda-developers.com/showthread.php?t=548218&highlight=create+gold+card With one GoldCard getting Update Fail error that SAPPIMG is older than one installed. When trying the other GC, get Update Fail Error that Model ID is incorrect. Tried 2 different micro sd cards, one Sandisk and one Patriot. The card was recognized by my pc after I was done creating the GoldCard, so unless I'm doing something wrong the GC was created properly. Is the goldcard.img supposed to dissapear or remain on the card after your copy/paste write/save to the sd card disk?
* Tried RUU for RUU_Sapphire_HTC_Europe_3.04.401.2_HTC_AT_test_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=625108 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU for RUU_Sapphire_HTC_Europe_3.05.401.3_release_signed_NoDriver.exe http://forum.xda-developers.com/showthread.php?t=621415 RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
*Tried RUU_Sapphire_HTC_Asia_WWE_2.53.707.2_SEA_test_signed_NoDriver.exe RUU would not let me proceed because the ROM was older than the one installed or Device ID was wrong. Attempted several times both with and without a goldcard installed.
I've probably tried a few more methods to obtain root. Those were all fails, too. I'll post the links, as well, when I find them again.
Hopefully this thread will lead us all in the right direction.
Here is the link to the same topic in the HTC Dream Forum-in case they find out something that might help us out: http://forum.xda-developers.com/showthread.php?t=625732

i guess its time to play doctor with my new phone from rogers and swap the board from my old one.....

considering nothing works, i think any new idea would be a good idea

novadoc said:
considering nothing works, i think any new idea would be a good idea
Click to expand...
Click to collapse
like i said my idea was to swap my old motherboard into the new phone

you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware

novadoc said:
you can give it a shot
but personally, unless you know exactly what your getting into, i wouldn't mess with the hardware
Click to expand...
Click to collapse
i already did it lol im more of a hardware then software

I know it might be nothing but when the Rogers RUU unpacks the img file loads as sappdimg and not sappimg. I don't know if the extra d in there means anything or if its something that shows up later.

I also try every method above and not luck also...

is there a possible way of tricking the system... with a higher build number and SPL with a custom installation from files that I see from one of the post where rogers send the user some files because they were running Win7?

I think that's the problem
We have the highest spl# and its perfected
So until someone gets their hands on a higher version than ours that is imperfect or engineering...
We are SOL, although I am hopeful someone is working on this for us.

shael said:
i already did it lol im more of a hardware then software
Click to expand...
Click to collapse
Did it work?

I have an Rogers HTC Magic and I didn't apply any update from Rogers since I bought it on June 2nd.
It's very strange that "adb devices" doesn't see the device?
have you enable the "USB debugging" ?
That part should work (when the devices is started).

novadoc said:
Did it work?
Click to expand...
Click to collapse
pfft ya ofcourse it worked... i have my older motherboard with my old rom and my old info all i did was swap the screen and case.... done deal... 5 min job lol

Would someone please report the radio and SPL versions (for the result of the 3.05.631.7 update)?

feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18

feisty_noodle said:
would someone please report the radio and spl versions (for the result of the 3.05.631.7 update)?
Click to expand...
Click to collapse
apphire pvt 32a ship s-on h
hboot-1.76.0010 (sapp50000)
cpld-12
radio-6.35.10.18

Well, until it gets cracked, here's something that will make you feel a little better about being stuck on this ROM.
Google Search by Voice, installable .apk from Euro Android Market. Just run the installer through Astro, etc., and G Search by Voice is back on the Search button of your phone. You might need to launch the app first via the icon in the app tray, then reboot the phone to make the search button recognize its there. But it will be there.
http://www.eclosion-android.com/com.google.android.voicesearch.apk
BTW, not my link in case mods want to get involved.
Enjoy!

i think the first step would be to getting ADB working again
any ideas?

novadoc said:
i think the first step would be to getting ADB working again
any ideas?
Click to expand...
Click to collapse
I can used adb devices to see my connected htc magic.... but other function permission not allow...

Is this thread in the Dream Forum a path to follow to try, or just a good way to brick your Magic? I haven't fully read through it to see if this is to keep root, if you already have it and flash the Rogers Dream ROM for data/ or to regain root if you flashed the official Rogers RUU with a Dream. The post says should work on all Rogers phones, but i feel a brick coming on for me.
http://forum.xda-developers.com/showpost.php?p=5480955&postcount=416

How To UN ROOT. TUTORIAL. Your Problems are solved!

UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....

Thanks op.

Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.

arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.

Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?

sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!

Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...

sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!

Well, worry even less! Special thanks to Calkulin!

thankssssss

Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop

I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...

I'm getting error 155 running Ava Froyo and trying to go back.

blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.

How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?

joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.

tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!

tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.

Yes. I have .79, thanks!
Sent from my PC36100 using XDA App

[GUIDE] How to root MT4GS with any HBOOT (updated 11/14/12)

*****
EDIT: PLEASE READ!!!!!!! Before proceeding, you need to find out which hboot your device has and if your device is S-ON or S-OFF. Ensure that Settings>Power>Fast Boot is unchecked and power down your device. Once your device is powered down, hold Power+Volume Down until you reach the bootloader screen.
On the second line, it should say "DOUBLESHOT PVT SHIP S-ON" or "DOUBLESHOT PVT SHIP S-OFF." If you are already S-OFF, great! You can flash a custom recovery in step 5 of this guide (although you need to have ADB/Fastboot installed on your Windows PC).
Your device is most likely S-ON. If so, continue reading. On the third line, your hboot information should be listed. If you have HBOOT-1.45.0013, you have the newer hboot and can follow this entire guide to achieve root. Most newer devices have HBOOT-1.45.0013.
If by chance you have the older HBOOT-1.44.0007, you have two options for rooting your device:
1. Use Revolutionary.io to gain S-OFF on your device. After using Revolutionary to achieve S-OFF, you can install adb/fastboot on your computer (in case you haven't done so already) and continue from step 5 of this guide to flash a custom recovery and Superuser for root,
OR
2. Update to latest OTA release and use this guide from beginning to end. You can update to the latest OTA release by going to Settings>About Phone or by using Blue6IX’s post “How-To: Restore to Stock.” Either method will update you to the latest OTA release (1.63.531.2) and HBOOT-1.45.0013.
IMPORTANT NOTE: If you update to latest OTA release with HBOOT-1.45.0013, you will NOT be able to revert back to the older hboot and S-OFF unless you use JuopunutBear to S-OFF. This involves a "wire trick" that some people are not comfortable with.
Many users have successfully achieved S-OFF with JuopunutBear (including me), but others have reported that it bricked their phone. This is usually because they do not follow the directions that say not to touch the bare wire. Check out the JB S-OFF threads here and here for other users’ experiences.
Confused about S-ON vs S-OFF? S-ON, Revolutionary S-OFF, and JuopunutBear S-OFF are described in detail here.
Revolutionary S-OFF is for HBOOT-1.44.0007. JuopunutBear S-OFF is for HBOOT-1.45.0013. Got it? Good.
*****
This is a step-by-step guide for rooting the MT4GS, designed specifically for new users (aka NOOBS), by a noob. The process is slightly more complicated than rooting other devices (i.e. Samsung), but it is well worth it.
The MT4GS is one of the best qwerty phones on the market and has some of the best developers. Don’t let the process discourage or intimidate you. Just FOLLOW EACH STEP IN SEQUENTIAL ORDER and you’ll be fine.
Here’s a breakdown of the process:
1. INSTALL HTC DRIVERS ON YOUR PC.
2. INSTALL ADB AND FASTBOOT ON YOUR PC.
3. REGISTER AT HTC DEV.
4. UNLOCK BOOTLOADER THROUGH HTC DEV.
5. INSTALL A CUSTOM RECOVERY.
6. ROOT YOUR DEVICE.
7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).
-PREREQUISITES-
Before getting started, please visit the MT4GS Compendium and read over Section One to learn the XDA Lingo. You really need to know this stuff if you’re going to tinker with the MT4GS.
Also, all information in the guide assumes you are using a Windows PC and a MT4GS with the STOCK ROM AND HBOOT-1.45.0013. If you are not on the Stock ROM, please use Blue6IX’s post “How-To: Restore to Stock.” Be sure to use the latest OTA (1.63.531.2). Once you're all set, let’s begin, shall we?
Disclaimer: I am not responsible for anything that happens to your phone. You assume all risks associated with modifying your phone.
-1. INSTALL HTC DRIVERS ON YOUR PC.-
Install the HTC Drivers on your PC from here.
Before connecting your phone, make sure USB Debugging is enabled (Settings>Applications>Development>USB Debugging).
Tip: to save time later, turn off your phone, hold down Power & Volume Down simultaneously until you reach the bootloader. Use the volume buttons to navigate to FASTBOOT and select it with the power button. Connect your phone via USB and the bootloader should now say FASTBOOT USB mode. Allow your PC to install the required drivers automatically. It may take a few minutes for your PC to search for and install drivers, so be patient.
-2. INSTALL ADB AND FASTBOOT ON YOUR PC.-
Installing ADB and fastboot on your PC is easy. Follow this guide and you’re good to go. To confirm that you have successfully installed ADB and fastboot, connect phone (with USB Debugging enabled) to PC via USB, open command prompt, and type “adb devices”. Your device ID number should be listed. Here are some useful commands for ADB and fastboot.
-3. REGISTER AT HTC DEV.-
Self-explanatory. Visit HTCDev.com and sign up with a valid e-mail address, as you’ll be receiving your Unlock_code.bin from HTC through this e-mail. Use an alternate browser such as IE, Google Chrome, or Mozilla Firefox if HTC Dev doesn’t play nice with your current browser of choice. Personally, I had to switch between Chrome and Firefox to get the HTC Dev website to cooperate.
-4. UNLOCK BOOTLOADER THROUGH HTC DEV.-
Make sure you’re logged in to HTC Dev and follow on-screen instructions to unlock bootloader. FYI, our device is listed as “myTouch 4G Slide (T-Mobile US)”. You can skip HTC’s instructions until step 5 since they're just telling you how to install ADB and fastboot, but you should already have ADB and fastboot installed .
After you finish unlocking the bootloader, the first line in your bootloader should read “*** UNLOCKED ***”.
-5. INSTALL A CUSTOM RECOVERY.-
Download official ClockworkMod Recovery 5.0.2.7 from the ROM Manager website or download another custom recovery from the MT4GS Development section. For instruction purposes, I will assume that you use official CWM Recovery 5.0.2.7. Save the img file to C:\.
Put your phone in bootloader FASTBOOT mode and connect to PC. Go to command prompt on PC and type “fastboot devices”. Once your device ID is listed, type “cd\” to get to “C:\” directory. Then type “fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img”.
After fastboot finishes, disconnect your MT4GS, go into bootloader, and go to “RECOVERY.” You should now be in ClockworkMod Recovery 5.0.2.7. The first thing I would do in CWM Recovery is make a backup of your stock ROM for safe keeping.
NOTE: Use volume buttons or trackpad to navigate through CWM Recovery 5.0.2.7. Select items by pressing the trackball. Power button may make your screen go blank and Back button returns you to the previous menu.
-6. ROOT YOUR DEVICE.-
Now that you have a custom recovery, you can flash custom ROMs. These custom ROMs are already rooted with Superuser and binary files.
NOTE: If you are S-ON, installing a custom ICS ROM will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
HOWEVER, if you want to root the STOCK ROM and/or continue to step 7 to achieve JuopunutBear S-OFF, you’ll have to root the device yourself. This is very simple. Download Superuser ZIP from androidsu.com/superuser. I can only recommend version 3.0.7 efgh because that is the only one I have tested, but newer versions may work.
Place the “Superuser-3.0.7-efgh-signed” on the ROOT of your SD card. Go to CWM Recovery and use “install zip from sdcard” to flash the Superuser zip. If installation aborts or fails the first time, try to flash the zip again until installation is complete. Reboot your phone and check in your apps to see if Superuser app is there. If so, congratulations, you have successfully rooted your stock MT4GS!
-7. USE JUOPUNUTBEAR TO GAIN S-OFF (OPTIONAL).-
Achieving S-OFF will make your life a lot easier if you want to flash custom ROMs, especially ICS ROMs. Follow instructions for JuopunutBear at unlimited.io and check out the JB S-OFF thread for other users’ experiences.
As I said before, if you are S-ON, flashing ICS ROMs will require an extra step in fastboot. You will have to extract the “boot.img” from the ROM and flash it with fastboot after installing the ROM in CWM recovery. More information from Limewirelord.
If you are S-OFF, you can bypass this step. For this reason alone, I highly recommend JB S-OFF if you have a half hour to spare and some courage for the wire trick. In this post, Indirect explains why JB S-OFF is superior to S-ON and Revolutionary S-OFF. Also, S-ON Unlocked, Revolutionary S-OFF, and JuopunutBear S-OFF are described in detail here.
However, if you plan on staying on stock-based/Gingerbread ROMs, S-OFF may be unnecessary for you. There are pros and cons to staying on 2.3 Gingerbread vs. upgrading to 4.0 ICS (like the stock HTC camera), but I’ll let you make that decision for yourself.
JB S-OFF NOTE: Users have reported that certain SD cards prevent JB S-OFF from working properly. If the wire trick doesn't work for you, try using another SD card and make sure it's formatted to a "FAT" file system and over 512mb in size (thanks to demkantor for this tip).
/ENDGUIDE
Hopefully this guide has helped you in some way. XDA has helped me out a lot and I simply wanted to contribute to the community that has given me so much. Feel free to share this guide with noobs in case they have questions about rooting their device (for the millionth time).
It is my hope that this guide aids in answering MOST noob root/modding/”this ROM broke my phone” questions. Noobs, please use the search function and many of the resources at your disposal BEFORE posting another thread. Everyone is here to help, so do your best not to annoy the MT4GS devs and vets.
We all were or still are noobs, so we understand your plight. However, we have seen WAYYYY too many threads that ask the same question over and over. Please consider the devs and XDAers that help you for free. Use the search function and remember to hit the “thanks” button. Thank you!
/ENDPSA
P.S. Shout out to the awesome MT4GS devs and contributors. You guys rock!
-Blue6IX
-tbalden
-kornyone
-xmc wildchild22
-strapped365
-sun_dream
-Riyal
-WeekendsR2Short
-anyone else I forgot, you go here!
P.P.S. If any links are broken, click on WeekendsR2Short's name above for alternative mirrors. Be sure to press the 'Thanks' button for him!
P.P.P.S. Thanks to ac3theone for this tip. If you begin experiencing an intermittent data issue on any ICS ROM (where your data turns on and off rapidly with a the 'H', '3G,' or data symbol flashing), try going to CWM Recovery and doing a wipe cache/dalvik and FIX PERMISSIONS. Hopefully this solves your intermittent data issue. This issue is ICS specific, so flashing back to a stock-based Gingerbread ROM should also fix the problem.

hopefull we get this sticky'd so that we gett less questions how to root. Nice guide tho

Nice topic and very helpful informations!thanks for the guide .

John9, how many phones do you have? I see you on every forum

i was originally s-off with the rev method and i followed blues how to on how to return to s-on then i updated all the way to the newest ota. I followed this guide and every link posted in the op and a couple hours later im back to s-off ( wire trick ). this guide should really be stickied! im very appreciative that you took the time to lay this out for new users! even though im not i still dont know it all

Make this thread like a cheap hotel cover!
Sent from my Bulletproof_Doubleshot using Tapatalk 2

Thanks for getting this stickied guys. If you think some info or links need to be added, let me know and I'll be glad to update the OP.

Nice guide! Thanks a lot!

Thanks for this guide, there are a lot of threads explaining how to do this but they were all over the place. Until last night, I was S-ON, unlocked but I decided to brave the wire trick and after about a million attempts, am now S-Off. I used this page as my reference starting point throughout since I had to go back to stock. Much appreciated!

I was going to unlock my device and get Clockworkmod installed, but hold off on anything else for the time being. When I went to HTC's website to obtain the unlock file, they indicated that unlocking the device would also wipe it clean. Is this the case or can you use the HTC Unlock and retain all of the current data on your device?
I was hoping to get CWM installed and then do a full backup of everything on my device as it currently stands before starting to play around with any custom roms.

HTCDev factory resets your phone no matter what. You need to do it in order to get CWM on your phone.
If you absolutely need to backup stuff that isn't on your SD card, look into finding an app that can do a backup without root (i.e My Backup). I can't personally recommend one because I've never used one.
Once you're rooted, you can use CWM and a good backup app like Titanium Backup (paid version is definitely worth it).

jjbz said:
HTCDev factory resets your phone no matter what. You need to do it in order to get CWM on your phone.
If you absolutely need to backup stuff that isn't on your SD card, look into finding an app that can do a backup without root (i.e My Backup). I can't personally recommend one because I've never used one.
Once you're rooted, you can use CWM and a good backup app like Titanium Backup (paid version is definitely worth it).
Click to expand...
Click to collapse
Alright, I figured that was going to be the case but I was hopeful that maybe I was wrong.
Thanks!

What about mytouch q non-slide?
Does this work for the new tmobile mytouch q that DOESN'T have the qwerty keyboard? Since there's no forum for this phone yet...

This won't work for the LG/Huawei MyTouch Q's. The MyTouch 4G Slide is an entirely different device made by HTC.

on HTCdev under Unlock Bootloader is doesn't show myTouch 4G Slide?!?!:crying:

It's there, I just checked. It's listed as "myTouch 4G Slide (T-Mobile US)."

jjbz said:
It's there, I just checked. It's listed as "myTouch 4G Slide (T-Mobile US)."
Click to expand...
Click to collapse
I found it now thanks, but none of the links for either custom recovery are working? What's with that? I'm doing this for my friend and unlocked his bootloader last night, but when I went to get the custom recovery none of the links work?

E4GTUser94 said:
I found it now thanks, but none of the links for either custom recovery are working? What's with that? I'm doing this for my friend and unlocked his bootloader last night, but when I went to get the custom recovery none of the links work?
Click to expand...
Click to collapse
I just checked the link CWM Recovery link in step 5 and it worked for me. Download from here if that doesn't work. Recoveries are in the first post. WeekendsR2Short was kind enough to host most of the dev-related files so make sure to press the "Thanks" button for him.

had to thank you for this well written/up to date guide
things went smooth until the wire trick, tried like 5 times and kept sober!
funny thing in the warning it said may fry sd card, so hell i had an old 128mb sd
from like 8 years ago that i have no problem throwing away. guess i need to use a
bigger card! swapped to a 4gb class 2 (next worse card i own)
worked perfect the first time! maybe add a note with the smallest amount of space
required on card (almost 100% certain the card was to blame as i didnt do anything different)
thanks again for the tut, and thanks to the unlimited.IO team, Fuses and hyuh, WeekendsR2Short and whomever else helped!
*side note, flash crashed at the very moment the phone rebooted after the successful wire trick... strange

demkantor said:
had to thank you for this well written/up to date guide
things went smooth until the wire trick, tried like 5 times and kept sober!
funny thing in the warning it said may fry sd card, so hell i had an old 128mb sd
from like 8 years ago that i have no problem throwing away. guess i need to use a
bigger card! swapped to a 4gb class 2 (next worse card i own)
worked perfect the first time! maybe add a note with the smallest amount of space
required on card (almost 100% certain the card was to blame as i didnt do anything different)
thanks again for the tut, and thanks to the unlimited.IO team, Fuses and hyuh, WeekendsR2Short and whomever else helped!
*side note, flash crashed at the very moment the phone rebooted after the successful wire trick... strange
Click to expand...
Click to collapse
I'm glad the guide helped you get root and JB S-OFF. As for the minimum SD card size, I'm not sure why your 128mb card didn't work for the wire trick.
It probably has more to do with the way a card is partitioned (FAT32, NTFS, etc.) rather than size. I'll add a note about the SD card partition to the guide for anyone else that may encounter the same issue.
Now that you're S-OFF, enjoy flashing all the awesome ROMs from the Dev section!