Database Info

[Guide] Installing the Hero Rom on your HTC Magic

Since the original link to this guide is buried in another thread, I've re-posted it here (and the guide in full) in order to help people that might've missed it. The latest version of the guide will always be available at http://www.karrderized.com/romguide/ however, and is a more printable version as well, so please check there too.
Installing the Hero ROM on your HTC Magic
Version 1.2 - 13 August 2009 - by KarrdeNZ
Disclaimer: I am not responsible if you brick your phone. This is only a guide. These instructions have worked for me, but there is no guarantee that they will for you as well. Follow this guide at your own risk.
Feel free to print off this guide if it makes things easier to follow. Please do not, however, steal this guide and claim it as your own. Updates to this guide will be posted here - http://www.karrderized.com/romguide/ - link, but don't steal. Thanks.
Things you'll need
Back up your settings
Installing the Android SDK
Determine your phone's version
Download the correct recovery ROM for your version
Download the correct Hero ROM for your version
Setting up the fastboot connection
Boot the recovery ROM
Back up your phone with Nandroid
Wipe your phone
Load your new ROM
Boot into your new ROM
Things to note
Acknowledgements
Changelog
1 . Things you'll need
A HTC Magic phone (obviously) running Cupcake (1.5) and with a SD card
A USB cable for your HTC Magic
A PC. These instructions assume you're running a Windows variant, though the same procedures can be performed on a Linux machine. Don't ask me about Macs. If you're running Windows, note whether you have a 32-bit or 64-bit OS, it becomes relevant later on.
The Android SDK - current release as of this writing is 1.5 Release 3, available here.
Recovery ROM - Which particular one you want to use will depend on your phone's version (I'll cover this later on).
A signed Hero ROM to install. Again, this is version dependent.
Got all that? Good.
2. Back up your settings
Now, before we start, back up. I'm of the opinion that you can never have too many backups. Take a copy of everything on your phone's SD card, make sure your contacts etc are synced, any apps you want that you can't easily get back from the Market are backed up, all that stuff.
Another thing you should note are the APN settings for your particular provider. These are in Settings, Wireless Controls, Mobile Networks, Access Point Names. You may have multiple APNs listed - go into each one and note down all the settings. You'll likely need to re-enter these manually once you've installed your new firmware.
Once you're satisfied you've got everything backed up, we can start setting up our environment.
3. Installing the Android SDK
Download the latest release of the Android SDK - here at the time of writing - for your relevant OS. I'll be using Windows from here on in. Extract the .ZIP file to somewhere convenient - I've got mine on my C: drive under C:\android-sdk-windows-1.5_r3. We need the SDK for the tools it provides in the tools subfolder, fastboot in particular, as well as the USB drivers for your phone.
4. Determine your phone's version
As of this writing, there are two distinct versions of the HTC Magic - PVT32A and PVT32B. The primary differences between these two versions is the amount of RAM (288MB on the 32A, 192MB on the 32B) and the radio (Qualcomm MSM7200a for the 32A, Qualcomm MSM7201a for the 32B). Generally, if your phone is HTC branded, it's a 32A, and if it's carrier branded (Google, Vodafone, etc) it's a 32B. Mine's a PVT32B from Vodafone NZ. But let's find out for sure what yours is.
Grab your phone and turn it off. Now, while holding the Back button down, power it back on. Your phone should now boot to a screen with a white background, some lines of text, and some skateboarding androids at the bottom. Welcome to fastboot.
The first few lines on the screen, in green, are what we're looking for. Mine reads as follows:
Code:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0004 (SAP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:30:40
Yours will likely differ slightly. The number we're looking for is in that very first line - PVT 32B in my case. Make a note of this. The next item we're looking for is the second line, which indicates your SPL version. Some SPL versions do not allow ROM flashing, notably those of T-Mobile's myTouch3G variant of the HTC Magic. At this writing, HBOOT-1.33.0006 and HBOOT-1.33.0010 are the two known "perfect SPL" versions that do not allow flashing. If you have either of those versions, stop now. There is a complicated procedure you will need to follow first.
Otherwise, for now you can turn your phone back off (by pressing MENU).
5. Download the correct recovery ROM for your version
Head to this thread and download the recovery ROM for your particular phone version, as we determined in step 4. Save it in the tools subdirectory of the Android SDK (in my case, C:\android-sdk-windows-1.5_r3\tools).
6. Download the correct Hero ROM for your version
If you have a 32A, this thread should help you find a signed ROM (I'd suggest Fatality's Hero ROM): here
If you have a 32B like me, try Qteknology's Hero port here- the swap version is the fastest Hero ROM I've found so far. It does however require you to repartition your SD card in order to provide swap space to speed the ROM up - a guide for this is available from the linked forum post.
Note I have only tested the one I linked for the 32B as that's the version I have. Download whichever ROM you need to somewhere handy, and rename it to update.zip. Please note: if you have file extension display turned off (default in XP) then just rename the file to update instead - the .zip extension will already be set. Once you've done this, copy it to the root directory of your phone's SD card. You can do this using the standard USB connection system that the phone provides, or if you prefer using a card reader.
7. Setting up the fastboot connection
Start your phone in fastboot mode as we did in step 4 (hold down Back while turning the phone on). Once the fastboot screen is up on the phone, plug the phone into your computer with the USB cable.
At this stage, my computer asked for drivers for the phone - these are included with the Android SDK, in the usb_driver subdirectory. Users with 32-bit versions of Windows should use the drivers in the x86 subdirectory under that, and 64-bit versions should use those in the amd64 subdirectory. Once the drivers have installed, leave the phone attached to your PC - you're ready to proceed with booting the recovery ROM.

[Guide] Installing the Hero Rom on your HTC Magic - part 2
8. Boot the recovery ROM
We're going to use the Android SDK's fastboot utility in combination with fastboot mode on the phone to perform a one-off boot of the recovery ROM so that we can back up the existing setup, wipe the phone and then load the new ROM. At this stage, it would be wise to make sure you've synced contacts and backed up whatever you want to hold onto.
Open a command prompt window on your PC (Start, Run, cmd) and change to the tools subdirectory of where you installed the Android SDK, for example:
Code:
cd\android-sdk-windows-1.5_r3\tools
The prompt should change to indicate you're now in that directory. Now we make sure the phone is properly configured to communicate through fastboot. Type the following:
Code:
fastboot devices
If you see your device listed, we're about ready to go. Let's boot into the recovery ROM:
Code:
fastboot boot recovery-RAv1.2.0G.img
If the recovery ROM you downloaded is named differently, substitute it's name for recovery-RAv1.2.0G.img.
All going well, your phone should kick into the recovery ROM now - you'll come to a pretty green texted menu with the HTC logo in the background. This ROM is being loaded via the fastboot software and is NOT on your phone, just in it's memory. We have yet to make any modifications to your phone at all.
9. Back up your phone with Nandroid
Let's make one more backup to be safe. The recovery ROM we booted into provides us with Nandroid backup and restore, which we can use to backup the firmware and data currently on the phone to the SD card.
On your phone, use the trackball to scroll down to Nandroid v2.2 backup and click. This will start the backup process, and you'll see some yellow text start to appear at the bottom of the phone's screen. Once it's complete, you have a backup.
Use the trackball to select the Reboot system now option and click. It should load back into it's normal firmware. You can now mount the SD card as usual and copy the nandroid directory from the SD card to your computer. This is also a prime opportunity to back up your entire SD card.
10. Wipe your phone
WARNING: This is the absolute LAST point at which you can back out of this procedure. After this, it's all or nothing. Proceed at your own risk.
Boot your phone back into fastboot with USB attached (see step 4) and then load the recovery ROM again:
Code:
fastboot boot recovery-RAv1.2.0G.img
Use the trackball to move down to Wipe data/factory reset. This will erase all the data on your phone, ready for you to install the new ROM. Click. Congratulations, you have just wiped your phone! You are now ready to load your new ROM.
11. Load your new ROM
Still in the recovery ROM menu, scroll to Apply sdcard:update.zip. This process extracts the ROM from the update.zip file we placed on your SD card earlier and installs it onto your phone. It may take a little while so be patient. It'll tell you when it's done.
12. Boot into your new ROM
Select the Reboot system now option and click. Your phone will now restart with it's shiny new ROM! First boots can take a while, so bear with it. You'll probably see a new splash screen or two on startup, and eventually you'll get into your phone. You may or may not be prompted with a request about giving an app root access on your first boot - you can safely Always Allow this, as it's writing a swap file to your SD card in an effort to speed things up. You'll also need to go through the setup process on the phone again as if it were new, because for all intents and purposes it is. This includes setting up your Google account syncing, as well as the new Hero functionality such as your Facebook, Flickr and Twitter integration (if you so desire).
And from here on out, it's all up to you! Enjoy your new firmware, make it your own. There's some great new functionality in Hero over the standard Magic firmware.
13. Things to note
This firmware isn't perfect. I'm loving it and see myself using it from here on in, but there are some quirks. These may or may not be fixed with your particular versions of ROM, especially once this guide has aged a little, but I'll try and keep it up to date.
The main thing you'll likely notice (especially if you're using a 32B like me) is the slowness. There's a lot going on with this new ROM so lag is fairly common. The phone will speed up a bit once you've used it some more, so bear with it. Your initial setups and playing around will be slow because of initial caching and your non-typical use of the phone, but this should clear up. Various ROMs have tried for workarounds for this, for example Qteknology's Hero port uses a swap partition on your SD card to help speed things up. CompCache is also a popular method, but my own experience with CompCache hasn't been very successful.
There are also reports of SMS messages sometimes not arriving on the latest Qteknology ROM - I mostly didn't experience this until recently, but it seems to be an occasional issue. The ROM builders are working hard on the issues they come across so fingers crossed for resolution on this one.
14. Acknowledgements
This guide wouldn't exist without the xda-developers forum. The bits and pieces I gathered from thereabouts are what I used to run this procedure on my phone, and hence build this guide. The people there are much more experts at this than I am, so I defer to their wisdom.
I must also give props to Jesse of Radix's Gadget Blog. His instructions were incredibly helpful in getting my head around what exactly to do.
And also to papalazarou, whose forum thread prompted me to write this guide.
- KarrdeNZ
15. Changelog
Version 1.2 - 13 August 2009
Added Changelog
Updated links and references to ROMs to account for new versions
Changed ROM recommendations to Qtek for 32B based on personal experience
Removed references to now fixed bugs, added reference to SMS bug on Qtek's ROM
Added "perfect SPL" note
Version 1.1 - 29 July 2009
Added note about update.zip naming with regard to file extensions
Added SD card issue
Version 1.0
Initial release

First rate stuff mate, thanks very much. Now all I need is the new release of Jerp's ROM and I'll be embarking upon my first upgrade. Makes so much difference having everything you need in one coherent place. This post really should be stickied.

+1 for sticky.
Needs to be in one place, will cut down on 'how do i' and 'where can i find' threads
(note i said cut down, and not cut out lol)

This applies to all roms actually.

Great write-up! Thx for the effort, this will surely be handy in all other topics, where these questions are asked again and again (logically IMHO, as it isn't basic stuff for everyone).
Well done!

Now that is a quality tutorial cheers!
+1 sticky

I had posted these replies elsewhere before I realised you had posted the guide in it's own thread. I've run into a problem and it's really confusing me as to why it's not working
---------------------------------------------------------------------
KarrdeNZ, mate I followed your guide to the letter. I got all the way down to step 11 and then a problem occurred.
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
----------------------------------------------------------------------
Well I tried downloading the same file again. No luck this time either!
This is what it says when I click the install from sdcard button:
--install from sdcard...
Finding update package...
Opening update package...
E: Can't open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Now I get that it's saying that it can't find the file but I really don't understand why? I mean the file is there, do I have to unzip the file onto my computer 1st and then put it on the sdcard?
I thought i just stuck the zipped file onto the root of the card making sure i renamed it 'update.zip'
Please help me out guys, thanks.

i did have the same issues, sorted it by:
Formatting the sd card (fat32)
Changing the permissions on the zip file
Moving files to the sdcard then sticking the sdcard into another computer to check that the files had been moved.
And it worked!

Roy_Drage said:
When I clicked 'Apply sdcard:update.zip' it just said cannot find or cannot load update.zip, or something like that, then said operation aborted?
I was trying to install the EXACT same ROM as you, I downloaded it to my laptop, renamed it update.zip and moved it to the root of the SD card.
Yet it didn't work, I can't for the life of me think where it's gone wrong as everything else up to that point had gone smoothly.
Any idea's?
Click to expand...
Click to collapse
don't know if this is the exact same error, but i had a similar situation and it freaked me out, all you have to do (in my situation) is wait a few seconds or so. i think the phone is still in the process of mounting the SD card or initializing the card component. give it a few seconds (30 sec) and try the update again.

I formatted the card in the phone before I started, did u format yours in the actual computer itself?
Also how do I change the permissions on the zip file?
n1ck75 said:
i did have the same issues, sorted it by:
Formatting the sd card (fat32)
Changing the permissions on the zip file
Moving files to the sdcard then sticking the sdcard into another computer to check that the files had been moved.
And it worked!
Click to expand...
Click to collapse

this is 5 star
thanx works gr8

Excellent guide. All the other tutorials/guides/instructions totally went over my head. Yours was extremely clear and easy to understand. Two thumbs up!

Excellent
Thank you for an excellent guide.

KarrdeNZ said:
I must also give props to Jesse of Radix's Gadget Blog. His instructions were incredibly helpful in getting my head around what exactly to do.
- KarrdeNZ
Click to expand...
Click to collapse
Sweet.. I get a mention! Glad my guide helped you get started and now you're writing a guide too to help others - this is what a community is all about!!!!
KarradeNZ - you've made a great start to a guide here - but I really think this should all be in the XDA Wiki so everyone can contribute/update/maintain it. Then we just get one link stickied at the top and everyone goes there..
I just started to write up a skeleton of what I think should be in the 'Ultimate Guide to Sapphire Hacking' on the Wiki page at:
XDADeveloperWiki - HTC_Sapphire_Hacking
You want to help me improve it?
Heck.. if you want we can use your guide as a basis if you like - I just braindumped what _I_ think should be in it and I can immediately see stuff I've overlooked that's in your guide!

Feel free to take inspiration/snippets/whatever from my guide for it - just throw a link to it in there as well. I prefer to keep the guide itself separate but am happy to have it contributing to the wiki.
And there's only one A in my name.

When I apply sdcard:update.zip I get the following Error
E:cant open/sdcard/update.zip
(No such file or directory)
installation aborted
Please help and suggest what could be wrong ?

Just rename the file update mate.
Then try again.

Thanks Roy_Drage for the fast reply you sorted my .zip problem.
Also well done and thanks to KarrdeNZ for putting such a great guide together that even a noob like me could follow. My new Magic is now running Hero looks awesome !

bajax said:
Thanks Roy_Drage for the fast reply you sorted my .zip problem.
Also well done and thanks to KarrdeNZ for putting such a great guide together that even a noob like me could follow. My new Magic is now running Hero looks awesome !
Click to expand...
Click to collapse
BT works? (can you connect to a BT headset?)
Facebook integration works?
have you notice any issues?

Flashing ROM on HTC Magic Perfected SPL

After a bit of research, I finally got a solution to flashing non-official ROMs on my Magic with [perfected SPL|]:
Download [FlashRec|http://zenthought.org/content/project/flashrec]. Since you cannot remote fastboot recovery ROMs, you have to use this app to flash a recovery ROM locally on your phone
Get your favourite recovery ROM (I used [this one|http://forum.xda-developers.com/showthread.php?t=530492])
Copy both files on your SD card; leave the ROM on root folder of SD card
Install FlashRec on your phone (remember to allow non-market apps in Settings->Application Settings)
Back up applications (optional, using ASTRO)
Back up your APN settings (following the "How to backup your APN details" section on [this page|http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking_2]. Note that this is not optional since my phone turned out to be unable to remember these settings after the ROM flashing. You cannot access data connection if you do not provide correct APN information
Get your favourite ROM at the bottom of [this page|http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking]; put it in root folder of SD card; rename it to update.zip without upzipping
Run FlashRec; click "backup current ROM" first; then type "/sdcard/##YOUR_RECOVERY_ROM_FILE_NAME_GOES_HERE##" into the text box, then click "flash ROM"
Power off the phone; Hold HOME and POWER until the recovery ROM appears
Follow the steps in Section 5 on [this page|http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking_2]
Type in the backed up (written down) APN information and enjoy
Good thing about this approach is that you do not need to do crazy things to fix perfected SPL, which I somehow believe is quite bricking-prone.
(http://lineardependence.blogspot.com/2009/12/flashing-rom-on-htc-magic-with.html)

What is new about your instruction that we can't find in other threads ?

I ended up flashing an engineering spl but it's good to know that it can be done with perfected spl. Thanks for the info!

Thanks a lot, I just bought a Magic for my dad, and he wanted Sense and root.. Turns out it have Perfect SPL. I was reading the howto for GoldCard, fortunately I found this guide after a bit reading

1.33.0014
Does this method work om this SPL??
If not I don't want to start all over with my apps, contacts and widgets

This metod work only Perfect SPL.

not suitable for g2 3.03 official roms. flashrec failed to work.

thanks dude
used this method myself. very useful posting in amongst all the (unecessary?) talk of flashing SPLs if you have 1.5 installed and want to get in on the ROM fun. (Even clearer than the method in the Newbie guide too)

flash failed: could not run command

I will ask the same question as I did on the 4th december.
Does this method work on 1.33.0014
If not I wont use this method, cause my phone is working with officiel rom, it's just slow and batteryconsuming

Does not work.....
I took the chance and tryed this, and it does not work. So I guees the only way out for me is the goldcard method

Do you need to be root?

The Complete Guide 2 Return Rooted Phone Back 2 Stock for Vodafone Australia Warranty

---Update Jan 31st 2011---
I have now included my own backups of the original HBoot and Recovery images from a newly replaced (stock Vodafone) Desire HD. I have edited the guide to include these image files.
--The reason for this guide is that when I tried to restore my phone to it's original state for warranty purposes I found that each of the 4 or more threads or guides I read on XDA and elsewhere had parts missing, weren't complete and seemed to trail on with questions about how to actually get the whole job done (with no one clear answer). After finally getting it all to work I decided it may be a good idea to put everything together in 1 complete guide.--
This is a complete, no nonsense guide to restore your HTC Desire HD back to it's original state for warranty purposes. This guide is for restoring to Vodafone Australia stock ROM version 1.32.178.5. This guide also covers restoring the corresponding radio version 12.28b.60.140eU_26.03.02.26_M. To the best of my knowledge this this is the correct ROM & radio versions as shipped at the end of December 2010 by Vodafone. This guide will also complete the process of putting back radio s-on, eng s-on, original hboot and unroot. This guide is aimed to include everything so the beginner could do it, in that sense I apologise if there are too many unnecessary details for the rest of you, please skip through to the important parts. Please note all Unix commands (such as those after you type "adb") are case sensitive. Be sure to put the exact upper case and lower case for the the file names you have chosen. Be sure your phone battery is well charged. If you can, use a laptop with the battery in and running on AC power or a desktop PC with a UPS, this is just to reduce any chance of your computer or phone powering off during flashing. Lastly the normal disclaimer you see everywhere, that procedures here could brick your phone or brick your phone if not carried out correctly, basically this should all work like it did for me but I can't be held responsible if your phone is reduced to a paper weight.
INSTALL ANDROID SDK
Firstly you need to have the Android SDK installed. If you don't follow this link: http://developer.android.com/sdk/installing.html
Make sure to follow the section on installing optional components as you need to install the USB driver components once Android SDK is installed. If you don't have Java SDK installed, trying to install Android SDK will let you know it needs this before it will install. One issue I found here is with Windows 7 64-bit the Android SDK 2.3 version will not install on to Java SDK 64-bit version, so make sure you download and install the Java SDK that says for "Windows" and not the 64-bit version. It is also a good idea to install the HTC MySync software that comes straight from the HTC website for your phone, this has USB drivers too.
HAVE INSTALLED FULL ROOT ACCESS & HBOOT
(CLOCKWORK RECOVERY, CUSTOM HBOOT, ENG S-OFF & VISIONARY+)
Most of you will already have all this done. Just check this easy guide and make sure you have already done all of these steps from where is says Method 1 to the end of the page: http://whirlpool.net.au/wiki/desire_hd_installing_roms
I make reference back to this step later in the guide so you will need to do this again.
MAKE A BACKUP
Seeing as this procedure will wipe everything from your phone you may want to backup everything for one easy restore after phone warranty/replacement. To make a Nandroid backup enter bootloader (power off phone then whole holding volume down press power button once to power on). Select recovery then backup/recovery and start a backup. It will be saved under a folder clockworkmod/backup/xxxxxxxxx/ on your micro SD card. One you get your phone back from warranty you follow the same procedures to restore just make sure you complete the One click Radio S-Off as linked to below and also install the full root access and hboot as described above. For restoring the backup, once in the bootloader and Recovery again (I'd recommend choosing factory wipe in the bootloader) just choose restore and select the following folder from the backup you made above.
IF LOCKED OUT USING 1.72.405.3 THEN USE THE DOWNGRADE PROCEDURES
Now if you are using 1.72.405.3 (or higher) or a custom ROM based on 1.72.405.3 it is quite likely you from the added HTC security features in these ROMS you have lost root access, custom hboot or the ability to change radio back to s-on with stock CID. If this is the case then follow this downgrade first by jkoljo: http://forum.xda-developers.com/showthread.php?t=905003
After the downgrade is complete make sure to remove file "PD98IMG.zip" from your micro sdcard and then follow the link above to carry out the full root procedures & hboot again.
INSTALL STOCK VODAFONE (AU) ROM
Follow this link to download Kazuroka's Vodafone Australia Stock Branded ROM 1.32.178.5: http://depositfiles.com/files/3x1c6v6hj
Create a folder on you micro SD card such as "stockrom" as follows: "/clockworkmod/backup/stockrom/" then copy the zip file there. Enter bootloader as described above. Choose recovery, then wipe/factory reset, choose backup/restore, then restore and select the zip file from the folder you just copied to your MicroSD card. After everything is done it will ask you to reboot. If so some reason when you select the option at the end to reboot and you just get a blank screen, wait for a while and be absolutely sure your phone your phone won't turn on then just remove and replace battery and then turn on.
CHECKING / INSTALLING STOCK RADIO
This stock ROM you just installed in the last step does not in my experience reload this stock radio. Here's how to check... At the home screen press menu, settings, About phone, Software Information and look under Baseband version to check which radio version you have installed. The stock radio that ships from Vodafone that matches this ROM is I believe 12.28b.60.140eU_26.03.02.26_M. If you have any other numbers here it means you have a different radio version installed than the one that came with the phone. I would suggest you follow this guide to install the stock radio version back if you have a different one installed. You will need to redo everything in the link above that was for titled installing full root access & hboot. Now download the stock radio file (thanks to Drakknar) from this link: http://www.multiupload.com/EUAUJCXGPN
Now if you've installed full root access & hboot as in the link above you will have a folder on your PC where you extracted fastboot. For me it is "C:\fastboot\". Open the radio zip file you just downloaded on your PC and copy the "radio.img" to the folder you have containing fastboot. Reboot phone into the bootloader as described above. Connect your phone via the USB cable to your PC. Make sure you've selected fastboot on your phone. It will display something like fastboot USB connection. On your PC open a the command prompt (Windows key + R to bring up the run box then type cmd and press ok). Go to the folder where fastboot is. For me without the "" marks I type:
"cd\fastboot"
then to install the radio I type:
"fastboot-windows flash radio radio.img"
This should all finish well then you can reboot your device and close command prompt. Sometimes flashing the radio can result in a line across the screen on the first time booting up but in my case it goes away the next time I restart the phone. Now once started up check in settings again to be sure you now have the the right radio version installed.
PUTTING BACK STOCK CID & RADIO S-ON
Reboot into the bootloader and check what it says under system info. If you have CID-11111111 it means you have super CID and radio s-off. You may have used jkoljo's One Click Radio S-Off to do this, no matter even if you haven't this is the easiest way restore it back also. Follow this link (thanks to jkoljo) for his One Click Radio S-Off: http://forum.xda-developers.com/showthread.php?t=857537
In his 2nd post you will see the link to download "Easy Radio tool v2_2.zip". Connect phone to PC using USB cable. Select charge only on phone and also make sure USB debugging is selected in settings, apps. Extract the zip file to a folder on your PC somewhere. Run "Desire HD easy radio tool_V2_2". While running make sure phone does not sleep and the screen stays on as it will pop up with a superuser request you will need to select yes to. On the Desire HD Radio Tool select Stock CID then put in "VODAP021" without the "" marks. Making sure the first "O" is the letter and the second "0" is the number zero. Click Do it! and be sure it all finished without any error displayed. Next select Radio S-On and click Do it!. Close program and restart phone. Check system info in bootloader and you should now see CID-VODAP021.
PUTTING BACK STOCK HBOOT & ENG S-ON
--edit Thanks to dazweeja for pointing this out. I've been told replacing the hboot and the recovery image to stock have quite a risk of bricking your phone if anything goes wrong. I'd suggest extra caution making sure you type the commands correctly.--
Tell tale signs your phone is modded are ENG S-OFF on the top line of entering the bootloader and also when you click on recovery it goes though to another list saying Clockwork Recovery. You will also want to remove root (superuser access) during this proccess. Now to remove root you can either run Visionary+ and select Unroot Now or what I did is just redo the step above that was to flash Kazuroka's Vodafone Stock ROM. After reflashing you only need to install a file browser from the market such as Astro or Androzip and then use it to install Visionary+ from you micro SD card. The only option you need to select in Visionary+ is Temproot now. This means root access will be gone after reboot. Now to remove Eng S-Off and put back the stock hboot & recovery image. Download my backup of the original recovery image from here: http://forum.xda-developers.com/attachment.php?attachmentid=504042&stc=1&d=1296394732
Also download my backup of the original HBoot from here: http://forum.xda-developers.com/attachment.php?attachmentid=504041&stc=1&d=1296394732
Extract the two zip files "Original_VHA_HBoot.zip" and "Original_VHA_Recovery_Image.zip" and you will get "recovery_orig0.bin" and "hboot_orig0.bin". Connect your USB cable to your phone and select "Disk drive, Mount as disk drive" and select "Done". The MicroSD card will now pop up as a drive in Windows. Copy the two files "recovery_orig0.bin" and "hboot_orig0.bin" to the new drive that popped up which is your MicroSD card on your phone. Make sure you copy these two files to the root folder of your MicroSD card (root folder means the base not a folder named "root"). After copying these two files, then on your phone, pull down the status menu sliding your finger from the top down. It should say "Ongoing" and underneath Select "Disk drive" now choose "Charge only" then select "Done" and make sure USB Debugging is on (in Menu, Settings, Applications, Development, USB debugging). On your computer open a command prompt and go to the "platform-tools" folder of your Android SDK installation. For me its:
"cd\program files (x86)\android\android-sdk-windows\platform-tools\"
then type
"adb shell"
"su" (if you get permission denied, you have to do run Visionary+ and select temproot now)
"busybox dd if=/sdcard/recovery_orig0.bin of=/dev/block/mmcblk0p21"
"busybox dd if=/sdcard/hboot_orig0.bin of=/dev/block/mmcblk0p18"
"sync" (wait 10 seconds then after that, you can close the command prompt)
Power off phone and then re-enter bootloader. If everything worked you will now see:
ACE PVT SHIP S-ON
HBOOT-0.85.0007
Also you'll notice that System Info is gone and also if you do select RECOVERY it will no longer go to Clockwork Recovery list but instead to a screen showing a picture of a phone with a red exclamation mark. Selecting Recovery means you'll need to pull the battery to reboot your phone. If you don't want to pull the battery, don't select RECOVERY but instead select FASTBOOT then POWER DOWN.
REMOVE VISIONARY+ (AND OTHER APPS) AS WELL AS CHECK FOR UNROOT
As described in the last section to check your device is unrooted... Make sure you've rebooted since you last did a temproot in Visionary+. Open a command prompt and go to the "platform-tools" folder of the Android SDK. Make sure phone is connected to PC with charge only and USB Debugging. Type:
"adb shell"
"su"
If you get permission denied then all good, your phone is unrooted, you can close command prompt. At the home screen go into apps then hit the menu button and select remove app. You will see a list of apps on the left tab that are downloaded apps. For me the apps I uninstalled were Visionary+, Superuser, and Androzip. Choose clear data, force stop, and uninstall for each app. Now depending on if you are going to keep your MicroSD card or send it in with the phone for warranty, will depend on if you need to to backup and wipe the MicroSD card. If you do need to send it in, connect the phone to your PC with the USB cable and select Disk drive Mount as disk drive and done. In windows you'll need to make sure you can see hidden files & folders. In Windows 7 open explorer (Windows Button + E) then select Organise, Folder and search options and select the View tab. Make sure you have selected Show hidden files, folders, and drives. Make a folder on your hard drive such as "phonecard backup". Go to your phone memory card for example "removable disk f:" or whatever the drive letter may be, select everything (ctrl + A) and then holding ctrl drag and drop everything into the "phonecard backup" folder on your hard drive. Once finished In Windows right click the taskbar icon and select eject removable disk. On your phone, remove the usb cable. Under settings, SD & phone storage, select Unmount SD card, then select Format SD card, Erase everything. The other optional thing you can do is a factory reset. On talking to HTC regarding warranty or repairs they asked if I'd done a factory reset. They also said this was the first thing they would do to try and resolve my issue. I figure it's a good step to do and you can tell them you've done a factory reset without it resolving your issue. In the same menu, SD & phone storage, select Factory data reset, reset phone, erase everything.
DONE! YOUR PHONE SHOULD NOW BE BACK TO STOCK & READY TO TAKE BACK FOR WARRANTY IF NEEDED!
--Note I have put together this guide from the works of a number of XDA members. Full credit for all the files, guides, tools (and help) I used here go to, jkoljo, sfjuocekr, Drakknar, Kazuroka, dazweeja, OzJD and leith51. Thank you--

Well done, Yoshi. This guide will be very useful for the many people who've been asking for it. I followed a very similar procedure when I returned my phone for warranty so your instructions look very solid to me.
Just a small point, the clockwork recovery mod *is* the custom image you flash to the recovery partition so it's still present after flashing the Voda nandroid/clockwork backup. In your instructions, you overwrite it with "busybox dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21" but you just as easily use fastboot to flash the stock recovery image while you're flashing the radio, eg. "fastboot-windows flash recovery recovery.img". Either way works but fastboot is safer because you're more likely to be warned if something goes wrong. There's no way around using 'dd' to flash hboot though (like you suggest). I held my breath at this point because if you get this part wrong, it's an instant brick. Luckily everything went smoothly.
Again, great work.

Actually if you just flash the vodaphone stock rom completely, you get rid of eng s-off, new radio and clockworkmod in a single shot
Also instead of android sdk you could use the radio flash guide attachment, because it has all the required files for adb.
Sent from my Desire HD using Tapatalk

jkoljo said:
Actually if you just flash the vodaphone stock rom completely, you get rid of eng s-off, new radio and clockworkmod in a single shot
Click to expand...
Click to collapse
There's no RUU available for Vodafone Australia branded ROMs unfortunately, only a nandroid/clockwork backup. I guess you could just run the stock 1.32.405.6 HTC RUU, install clockwork mod, flash Vodafone AU clockwork backup, temproot with Visionary, dd stock recovery, and then unroot. It's a little simpler but I was a bit hesitant to try it though as the Vodafone AU ROM is 1.32.178.5 so some of the other eMMC partitions overwritten by the 405.6 RUU might differ from Voda ROM. It would probably still work but Voda might be able to tell if they cared to look (for warranty).

Nice work mate
Cheers

I had to send one back, and it took me a while to gather all the info, so many thanks for the single shot guide.
As an aside, my returned device was in fact returned to me as
"Uneconomical to Repair" due to liquid Ingress
So the first contact was... "tough matey, it's not covered, your screwed"
I 'pushed' them as this was not acceptable and in the end *2 hours and 4 people later* I got a replacement.
The phone they sent back wasn't working, no response off the screen, so I took a 'look' at it, turned out, all the missed was connecting the screen back up correctly.
I did this for them and lo and behold it worked, so I spent the next two weeks whilst my new one arrived, getting to know how to flash/mod/change the thing, when I returned it to them, I re-disconnected the screen ;-) for them.
Not sure if they have tools to tell other obvious things, but date stamps and versions would be a clear indication that you have been playing
But judging by the standard of the return I had, I would not be concerned after following this guide.

dazweeja said:
There's no RUU available for Vodafone..
Click to expand...
Click to collapse
Ah, I see
Nice guide!
Sent from my Desire HD using Tapatalk

silashack, that's crazy! Well I'm glad I cought this before my 28days are up so holpefully as HTC have said so far they should just completely replace the phone if they find the same problems I've found. They would make me nervous about repairing my phone if that's their standard here in Aus.
silashack, I'm interested to know how did you open up the phone without tearing all those little void stickers on the screws? I would love to see a disassembly guide. I have looked but found nothing on the net so far... did you take any photos? Did you find any water sensors in this phone (ie the white litmus paper or some kind of paper that changes colour permanently on moisture and voids the warranty)??
I'm guessing DHD will have water sensors like other HTC models. I just don't like this idea. I mean I don't know how sensitive this paper stuff is but these are the current scenarios I am afraid of voiding my warranty idea because of stupid water sensors... having the phone with me on a rainy day, replacing the screen protector with the water method, having my phone with me at a rave or nightclub and getting sweaty pockets from a night of dancing.

Originally Posted by dazweeja
There's no RUU available for Vodafone Australia branded ROMs unfortunately, only a nandroid/clockwork backup
Click to expand...
Click to collapse
Once I get my replacement phone back from HTC & Vodafone (and before I start modding the crap out of it again ) I was wondering if there is a way to create a full backup that would include the radio version, be completely unmodified and not have clockwork recovery, modified hboot, eng s-off ect? If there is a way and someone would be kind enough to explain it then I'd be happy to do it and post up the backup ROM so others have a 1 shot method to return their phones to stock 4 warranty for Vodafone (AU).

Thanks alot for this info, its good to know my voided warranty can be unvoided. I'd like to thank you but I can't seem to see a thank button, I'll try again on my desktop tonight...

Props Yoshi!!
Man this will help a few people for sure.

Yoshi_523 said:
silashack, that's crazy! Well I'm glad I caught this before my 28days are up so hopefully as HTC have said so far they should just completely replace the phone if they find the same problems I've found. They would make me nervous about repairing my phone if that's their standard here in Aus.
silashack, I'm interested to know how did you open up the phone without tearing all those little void stickers on the screws? I would love to see a disassembly guide. I have looked but found nothing on the net so far... did you take any photos? Did you find any water sensors in this phone (ie the white litmus paper or some kind of paper that changes colour permanently on moisture and voids the warranty)??
I'm guessing DHD will have water sensors like other HTC models. I just don't like this idea. I mean I don't know how sensitive this paper stuff is but these are the current scenarios I am afraid of voiding my warranty idea because of stupid water sensors... having the phone with me on a rainy day, replacing the screen protector with the water method, having my phone with me at a rave or nightclub and getting sweaty pockets from a night of dancing.
Click to expand...
Click to collapse
Tell me about it, don't get me started on the 'support' issues so far
When the phone was returned, I saw no void stickers on the screws as such.
I to could not find a tear down on the HD, but watching a normal Desire gave me the confidence to examine the HD, for all intentional purposes this thing was classified as dead by them not me, so nothing to loose. I did not take any pictures, which is not my normal style, I tend to do that for my own pedantic reasons on all my projects, but as this was DOA I did not bother, sorry
As for a water sensor... The single sheet of paper that came back with the phone describes the possible reasons for "Liquid Ingress" by Vodafone something like:-
Use in a steamy bathroom
On the Train
In a humid climate
In your pocket
You get the gist, all pretty normal day to day possibilities, so I not only didn't consider any sensors, I couldn't care less, it was a pathetic list, will try and find it and post on here.
The flat cable that connects the screen to the device wasn't seated right, using a small jewellers flat blade, I lifted it , blew it clean with compresses air and then reseated it.
The removal of screws was easy, but there is something about the way the top end is connected, for the life of me I could not remove the fascia at all, I ended up with it slightly off the device but still connected, I did not push this as it looked like it could bend the fascia where the speaker grill area was, so when I put it back together, I could see a slight gap at the top right between the case and the screen, less than a mm but enough that it would have bugged me.
I have since bought a gel case for my new one, but in light of the pathetic reasons given for possible liquid ingress I am concerned about the sticky residue that occurs when you hold it for any length of time, if this is transferred to the inside of the case during our summer months... I can see a few people getting warranty denied for this.
I also was NOT aware of the ridiculously short period of manufacturers warranty, and considered the need for insurance as pointless due to the advertising by vodafone about 24 month repair warranty, covers jack **** to their benefit
As for any 'offers' made by HTC or Vodafone, make sure you have that in either writing, or confirm the conversation has been recorded (if support on 1555)
When I deal with them, my last two questions are
1. Could you please repeat your name and how to spell it?
2. Can you please confirm that THIS call HAS been recorded
Allegedly, all calls are recorded, so you can use this to get them to go back and confirm any agreement or discussion/decisions that transpired between you.
All this seems a little harsh, but having dealt with them (and still dealing with them and the TIO) these are steps you need to take to get things moving how they should and not be treated like a third rate citizen, fobbed off with lame support and excuses.

jkoljo said:
Ah, I see
Click to expand...
Click to collapse
Yeah, it seems every other country/carrier has a leaked RUU. You think we Aussies would have one too - after all we produced Julian Assange

I think i am the only one cant solve this problem, hopefully u can guide me.

Yoshi_523 said:
"busybox dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21"
"busybox dd if=/sdcard/DHD/hboot_orig.bin of=/dev/block/mmcblk0p18"
Click to expand...
Click to collapse
If I've read this properly, it doesn't look like you've given the steps to actually copy the recovery.img and hboot_orig.bin files to the SD card before trying to re-write them.

^^ Oh sh*t! Sorry about that... Thanks matm for the picking that up! I've just rewritten that part so it now says to copy recovery.img and hboot_org.bin to the sdcard folder of the MicroSD card rather than to the Android SDK folder (which would have been useless).
Ok so as of today the 23rd of January the guide should be okay on that.
By the way guys I just got my new phone today from Vodafone. They didn't even look at it they just replaced it on the spot. I was within the 28day of purchase. I've noticed reception is showing more bars especially when I put in the 3 SIM card compared to before. I've also noticed there is a problem quite noticeable when I hold my left hand covering the bottom MicroSD & Sim card cover plate. This is most noticable with the Vodafone SIM in which holding it makes it go from 3 bars to 1 or zero bars. The position I'm holding the phone is pretty much identical to the "death grip" that messes with the iphone 4. As soon as I move my hand so it is not touching the bottom cover the reception bars come back. Strangely using a gel cover doesn't fix this.

I think that's a known problem. Mine does the same and has from day one.

Also change this line:
"busybox dd if=/sdcard/DHD/hboot_orig.bin of=/dev/block/mmcblk0p18"
to
"busybox dd if=/sdcard/hboot_orig.bin of=/dev/block/mmcblk0p18"
Because in your instructions, you say to copy the files to your sdcard, not copy the hboot to a folder on your sdcard named 'DHD'.

^^ Oh Sh*t. Sorry about that. Fixed the guide again. Thanks again guys. If any more problems with the guide please let me know. I don't want to "root" peoples phones (Aussie slang for "f*ck"). I want to "unroot" them. heh heh
Also if you wanna see some video's I put together on the Desire HD "death grip" reception issue. Have a look at this link:
http://forum.xda-developers.com/showthread.php?p=10842571#post10842571

I should have also said before, that this is an awesome guide!
It always makes me feel better to know someone has already done this before I try.

[REF] All in One guide for NOOBS! With Vidoes Now!

I don't take any credit I Googled everything. I do take credit of modifying some stuff in word. The idea came from here. I may have took some of his work. SO credit him and Pirateghost for the information about Android.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
ASOP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.

This is how to flash Ice Cream Sandwich!
How to Root Your Skyrocket????
>You will need Samsung drivers download here OR Here!
>>IF running 2.3.5 than click here Or Here for root.
>>>On your Samsung Galaxy S II Skyrocket go to Enable “Unknown Sources” in Settings >> Applications. This is located in the menu by going to Menu, Settings, the Applications.
>>>>Enable USB debugging by going to Menu, Settings, Applications, Development and checking USB debugging.
>>>>>Once you’ve downloaded and installed the above, plug your Skyrocket into your computer USB port. If you have a USB in the back plug it up in the back. Some ports work better than others that is key.
>>>>>>Make sure you’ve extracted the Skyrocket-Easy-Root.
>>>>>>>On a Windows computer, especially Windows 7 you will need to right click on the root.bat file in the extracted folder and run as Administrator. For some it might work without doing it, but I highly advise running as administrator. Now, I got confused because my phone keep failing after all yellow screen and all the text…KEEP TRYING. If it fails and you don’t see the Super User app on your phone then try another port. I tried and tried on my desktop but for some reason I ran it on my laptop and it worked perfectly. Remember to run as Administrator by right clicking the root.bat file.
If you have a Mac or Linux computers, install “Linux-Mac.sh”
>>IF running 2.3.6 than click here for root. Follow instruction on the thread!!!!!!!
<;> You have Done it NOOB!! Congratulation On Your first step!!!!
How to Flash CWM Recovery????
After Rooting your phone.
# Go to market and Download Rom manager.
## Go To Rom manager.
### Press Flash ClockworkMod Recovery.
#### And Chose T-mobile Galaxy s2.

Video about how to get ready to start flashing!
How to Flash a ROM????
Basic Steps
! Choose the ROM that you want and download its .zip file
!! Transfer the zip file to your phone’s sd card. Do not put it into any folder.
!!! Turn off your phone and reboot into recovery, usually by holding the down button and power button at the same time.
!!!! Do a Nandroid backup
!!!!! Wipe the phone 3 times by clearing cache/factory restore 3 times and wiping dalvik cache and system format
!!!!!! Flash the zip file that you put on your sd card
!!!!!!! Reboot phone
You can find all ROMS here.
How to backup your current ROM????
Easy Way!
-Open ROM Manager.
--Tap Backup Current ROM.
---Leave the filename as the date or change it to whatever you want.
Hard Way!
Get into CWR!
Scroll down to backup and restore!
Press backup.
How to Restore Your backup????
If You used ROM manager than!
Go to manage and restore backups!
And press the one you like to restore!
If you have Nandroid than!
Go to CWR!
Scroll down to backup and restore!
Press restore!

How to flash Kernel????
_Download the Kernel You want to flash and put it in sd card.
__Boot in to CWM!
___Wipe cache!
____Press install from Sd card!
_____Select the kernel that you dloaded!
______Flash it!
_______Reboot!
________Check in CPU SPY to see if you successfully flashed Kernel.
You can find all the Kernel here!!!

These will set you back to Stock and Unroot Your phone.​
Welcome Finally You have made it here. Well now I know that you are little worried bout your phone but Let me tell you that there is noting to worry about.
Make sure you are relaxed because if you are tensioned than you will most likely screw things up. Do me a favor and watch this video. Relax get beer or Watch Funny videos on Youtube.
“Never ever unplug your phone when you are Flashing”
Drivers You will need!
! Odin 1.85
!! USB Drivers
!!! Skyrocket Stock Recovery.tar file ATT Or Rogers
Extract the contents of odin-185.zip and the 7zip archive.
Run Odin3+v1.85.exe, and prepare Odin:
Check "auto-reboot", and uncheck all other options.
Install Usb Drivers and Unzip the Recovery file and put it to safe place.
Main Process.
Try to get in Download Mode.
) Connect USB to computer but not your Phone.
))Take out and put back in the battery.
)))Then, hold Vol + and Vol - , now plug in USB and you will at the following screen that’s in picture.
))))Press Volume Up button now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally You have made it to Download mode.
If in case this does not work for you than and you are still luck enough to go into CWM than do factory reset and flash any stock rom. And do all this steps again.
Ok so after getting into Download Mode.
-Go ahead and Go to Odin (Check "auto-reboot", and uncheck all other options).
--In Odin check PDA and find the recovery.tar file that you downloaded.
Now Press Start (Check "auto-reboot", and uncheck all other options.)
When you are done Your screen will look like one below.
It should now reboot to recovery and delete cache and data. Then, it will boot.

I like this alot! Ill definantly save this page
Sent from my NookColor using xda premium

Will Ask MOD to see what he thinks about sticky.
Android311 said:
I like this alot! Ill definantly save this page
Sent from my NookColor using xda premium
Click to expand...
Click to collapse

appdroid said:
How to backup your current ROM????
Easy Way!
-Open ROM Manager.
--Tap Backup Current ROM.
---Leave the filename as the date or change it to whatever you want.
Click to expand...
Click to collapse
Cannot have spaces in the file name though.
Sent from my SAMSUNG-SGH-I727 using xda premium

I wish this kind of guide was around when I was a noob back in the captivate days I had to read for weeks before I learned how/decided to root. Great job!!!
Sent from my SAMSUNG-SGH-I727 using xda premium

This is what happens when i wake up in middle of the night and don't have anything to do. I have problem with sleep once I wake up in middle of sleep its almost imposible for me to go back to sleep. Last night I was little sick so woke up and had idea about doing this long time ago but last night was the time dedicated to this work. On top of all this I had 8 hour of work. I just got of and about to pass out. Any way thought I would share my little story. This is only a little help from me to this great community. Thanks all and Enjoy11!!

Very well done. Did you pm jay harper and ask him to sticky this yet?
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
I just pm'd mr harper and asked him to sticky it. I hope he does very informative, and well typed.

Looks good
Stuck like Chuck......
Sent from my PG86100 using xda premium

Thank you. MR. Boss man SIR

silver03wrx said:
Thank you. MR. Boss man SIR
Click to expand...
Click to collapse
Watch it
Sent from my PG86100 using xda premium

silver03wrx said:
Very well done. Did you pm jay harper and ask him to sticky this yet?
---------- Post added at 08:48 PM ---------- Previous post was at 08:44 PM ----------
I just pm'd mr harper and asked him to sticky it. I hope he does very informative, and well typed.
Click to expand...
Click to collapse
Thank You. Seen Many thread about this stuff so thought I would write one for noobs. haha
jayharper08 said:
Looks good
Stuck like Chuck......
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Thank You Mr. BOSS MAN!!!!!!!!!

appdroid said:
Thank You Mr. BOSS MAN!!!!!!!!!
Click to expand...
Click to collapse
Eeeeeeaaaaaaasssssssyyyyyy
Sent from my PG86100 using xda premium

Not a N00B by any means (I have a N00B Guide too ). Anyways, I don't even own this phone, but will be rooting and tinkering with my friends Skyrocket tomorrow. In preparation I had a couple of questions, as most all other brand phones seem to be so different from my Motorola Atrix. Thanks in advance for your help.
- Ok root seems pretty straight forward, no issues here.
1) After I've rooted the phone, do I install CWM via ROM Manager? If yes, I'm assuming I choose Samsung AT&T GS2, or should I choose the T-Mobile version (don't know why I would since he's on AT&T)?
2) Have seen posts that ROM Manager both works and it doesn't... which is it? Should I only use it flash CWM, and boot into CWM (as a shortcut)? What's this about installing CWM via a kernel which has it baked in; how can I install a kernel without first booting into CWM?
3) So is the bootloader on this thing locked or unlocked? If it's locked, is there an unlock process yet; i.e. fastboot?
Thanks again for the help... like I said, not my phone, just helping a friend... info. ought to come in handy though when I move to a Samsung phone in the future; waiting on the SGS III.

1) After I've rooted the phone, do I install CWM via ROM Manager? If yes, I'm assuming I choose Samsung AT&T GS2, or should I choose the T-Mobile version (don't know why I would since he's on AT&T)?
Chose T-mobile Galaxy S2
2) Have seen posts that ROM Manager both works and it doesn't... which is it? Should I only use it flash CWM, and boot into CWM (as a shortcut)? What's this about installing CWM via a kernel which has it baked in; how can I install a kernel without first booting into CWM?
Well i don't know about kernel that has baked in it. All Kernels on Skyrocket are .zip files and can flash in CWM. And you can flash it through Rom manager.
3) So is the bootloader on this thing locked or unlocked? If it's locked, is there an unlock process yet; i.e. fastboot?
Sammy always has bootloader unlocked so its unlocked.
Swiftks said:
Not a N00B by any means (I have a N00B Guide too ). Anyways, I don't even own this phone, but will be rooting and tinkering with my friends Skyrocket tomorrow. In preparation I had a couple of questions, as most all other brand phones seem to be so different from my Motorola Atrix. Thanks in advance for your help.
- Ok root seems pretty straight forward, no issues here.
Thanks again for the help... like I said, not my phone, just helping a friend... info. ought to come in handy though when I move to a Samsung phone in the future; waiting on the SGS III.
Click to expand...
Click to collapse

appdroid said:
1) After I've rooted the phone, do I install CWM via ROM Manager? If yes, I'm assuming I choose Samsung AT&T GS2, or should I choose the T-Mobile version (don't know why I would since he's on AT&T)?
Chose T-mobile Galaxy S2
2) Have seen posts that ROM Manager both works and it doesn't... which is it? Should I only use it flash CWM, and boot into CWM (as a shortcut)? What's this about installing CWM via a kernel which has it baked in; how can I install a kernel without first booting into CWM?
Well i don't know about kernel that has baked in it. All Kernels on Skyrocket are .zip files and can flash in CWM. And you can flash it through Rom manager.
3) So is the bootloader on this thing locked or unlocked? If it's locked, is there an unlock process yet; i.e. fastboot?
Sammy always has bootloader unlocked so its unlocked.
Click to expand...
Click to collapse
Thanks for the quick reply... simple enough... just wanted to make sure.

This is the n00b thread... so I have a n00b question. What does SOD stand for?

[Q] Lost functions after deleting bloatware from rooted Sensation 4G

Hi all, I have a rooted HTC Sensation 4G, which still has T-Mo provided ICS 4.0.3 and I assume Sense 3.6. I never put any other ROMs in, not sure how, just wanted root for stuff like tethering, call recording, etc. The phone has been getting more and more slow as time goes on, and has gotten to the point lately I have nothing left to lose. When making a call, the Contacts lists stays up a good 60 seconds or so before the screen comes up where t is actually dialing for you, or if I manually put a phone number in, it just hangs there just as long before the phone takes over to actually make the call. And do just about anything else, when getting out of what your were doing, I get the white HTC screen, then loading the screen with the time and temp which takes a good 30 seconds. Using the browser often just cuts me off and reverts to the home screen.
I thought finally getting rid of the bloatware may help, got rid of NOVA, Lookout, a lot of wallpapers and widgets I don't use, something called CS and a couple others I looked up online which says is OK to delete, as well as Facebook, Youtube, TV apps, etc.
After I was done, first thing I noticed, no time and temp. display. I used an app called NoBloat and checked "backup and delete" on all I wanted to get rid of. I started trying to install from NoBloat's back-up folder, and even though says installing, I could tell they weren't when I looked for the installations. I found the NoBloat folder on my SD card, and tried the .apk's from there, and the majority would say "Can't install" or something similar. I then wanted to take a screenshot of something, and that function is gone.
I would like to do a reset to start from scratch without losing root. I found out the Senastion is a tough one to root and I paid someone to do it and it took 2 days before I could pick it up. Is there a way to reset without losing root since I still have stock 4.0.3 in it? Thanks much.

do you have a custom recovery installed?

Hi, if you mean a custom ROM, no. But if any of these will help, I have BusyBox Free, NoBloat, ROM Manager, ROM Toolbox Lite, Root Browser Lite, Root Checker, Super SU, SuperUser, SuperUser Whitelist, Terminal Emulator, and Titanium Backup installed. I never backed anything up with Titanium BU. Was one of those things I was going to lean to use, but didn't yet. I assume I need to install a custom ROM to get total functionality back without losing root, would be nice to get Kit Kat on this (or is this phone too old to do much with?)
I did manage to install "Sense flip clock & weather" from Google Play which broght back time and temp., and also Screenshot Ultimate which seems to work, but not as easy to use as the native app. A bunch of other screenshot apps seemed not to work at all, so now I can basically get by the way it is now, but still need to get the 60 second dialing lag fixed which is still there, so I'm assuming a fresh ROM install. Thankfully my Wifi Tether app still works. Thanks.

dannykewl said:
Hi, if you mean a custom ROM, no. But if any of these will help, I have BusyBox Free, NoBloat, ROM Manager, ROM Toolbox Lite, Root Browser Lite, Root Checker, Super SU, SuperUser, SuperUser Whitelist, Terminal Emulator, and Titanium Backup installed. I never backed anything up with Titanium BU. Was one of those things I was going to lean to use, but didn't yet. I assume I need to install a custom ROM to get total functionality back without losing root, would be nice to get Kit Kat on this (or is this phone too old to do much with?)
I did manage to install "Sense flip clock & weather" from Google Play which broght back time and temp., and also Screenshot Ultimate which seems to work, but not as easy to use as the native app. A bunch of other screenshot apps seemed not to work at all, so now I can basically get by the way it is now, but still need to get the 60 second dialing lag fixed which is still there, so I'm assuming a fresh ROM install. Thankfully my Wifi Tether app still works. Thanks.
Click to expand...
Click to collapse
not a custom rom
a custom recovery such as 4ext ,cwm ,TWRP
if you want to use a custom rom you must have a custom recovery installed
by the way all custom roms come pre-rooted
so don't worry about root(it is the easiest part)
can you post your bootloader details?

Hi rzr86, here is the screen I got, I didn't know if/how to proceed any further. I also noticed I have ClockWorkMod installed if that helps, I had the phone rooted around August of 2013 if that helps, so I think all the apps to do with rooting have not been updated, Thanks again.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dannykewl said:
Hi rzr86, here is the screen I got, I didn't know if/how to proceed any further. I also noticed I have ClockWorkMod installed if that helps, I had the phone rooted around August of 2013 if that helps, so I think all the apps to do with rooting have not been updated, Thanks again.
Click to expand...
Click to collapse
i suggest to change your recovery to 4ext(since you are on S-ON 4ext has smartflash feature which flashes the boot.img for you while flashing a new rom)
take here the latest version of 4ext recovery
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command
the command is fastboot flash recovery recovery.img
if you stay with cwm recovery you will have to flash the boot.img manually while flashing a new rom

Hi rzr86, thanks agin, I will do this later tonight when expecting no phone calls. So I would delete the clockwork app, and put the recovery.img from the zip file into my SD card, and tap that, or do I go into the bootloader menu again and tap FASTBOOT and put in the command? Any suggestions on what a good ROM for me would be? I assume the 4EXT Touch Recovery automatically backs up what I have now, or prompts me to? Thanks again.

dannykewl said:
Hi rzr86, thanks agin, I will do this later tonight when expecting no phone calls. So I would delete the clockwork app, and put the recovery.img from the zip file into my SD card, and tap that, or do I go into the bootloader menu again and tap FASTBOOT and put in the command? Any suggestions on what a good ROM for me would be? I assume the 4EXT Touch Recovery automatically backs up what I have now, or prompts me to? Thanks again.
Click to expand...
Click to collapse
no don't put the recovery.img in your sdcard
connect your device in your pc in fastboot usb mode
extract the recovery.img from the zip and place it in your adb/fastboot folder on your pc
on that folder open a command window and type the command
don't worry it will overwrite the cwm recovery
AFAIK 4ext restores backups made by cwm because 4ext is based on cwm
about rom you can try vipers 5.3.0 (jelly bean with sense)

Thanks once more rzr86, I think I have enough info to handle it from here, and I'll look up the vipers 5.3.0. I know a lot of people say Sense is worthless and a memory hog, but I'm used to it now, and I'm sure with the new ROM some of that memory will be freed up from bloatware. I'll try the new recovery app later tonight, and I assume I can wait another day to put in the viper ROM if needed. Guess I should back my SD card up, even though I assume none of this touches the SD card. Does the SIM card need to be in, as I have an old Dash I can put the SIM in for now till I'm done. Thanks much again.

dannykewl said:
Thanks once more rzr86, I think I have enough info to handle it from here, and I'll look up the vipers 5.3.0. I know a lot of people say Sense is worthless and a memory hog, but I'm used to it now, and I'm sure with the new ROM some of that memory will be freed up from bloatware. I'll try the new recovery app later tonight, and I assume I can wait another day to put in the viper ROM if needed. Guess I should back my SD card up, even though I assume none of this touches the SD card. Does the SIM card need to be in, as I have an old Dash I can put the SIM in for now till I'm done. Thanks much again.
Click to expand...
Click to collapse
your simcard nad sdcard will be untounched

rzr86 said:
your simcard nad sdcard will be untounched
Click to expand...
Click to collapse
Not getting too far, give up for tonight. Used "Minimal ADB and Flashboot" app, stays on "waiting for device". I tried modifying the name as recovery in the file name twice. I tried command from the folder I unzipped the recovery.img to, as well as trying to copy recovery.img to the Minimal program folder and try from there. I read I don't need the whole huge ADB download for what I'm doing on another site. I used this to get Minimal:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

dannykewl said:
Not getting too far, give up for tonight. Used "Minimal ADB and Flashboot" app, stays on "waiting for device". I tried modifying the name as recovery in the file name twice. I tried command from the folder I unzipped the recovery.img to, as well as trying to copy recovery.img to the Minimal program folder and try from there. I read I don't need the whole huge ADB download for what I'm doing on another site. I used this to get Minimal:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
don't use any program
just open a command window in that folder where you have adb/fastboot files
edit: by the way did you select fastboot when you connected the device to pc?(from the bootloader screen)

I used the Fastboot under settings, I'll try the Fastboot by pressing Vol down and Power, wasn't sure which to use, thanks again, and will do without launching a program later in today. I should have known better to try the Fastboot screen if the other didn't work.

Hi rzr86, just tried again, powered up phone using vol down and power, have bootloader screen, selected Fastboot. Also gives other options like Bootloader, Reboot, Reboot Bootloader, and Power Down. If I hit power, says Hboot, then checks something real fast something about SD card and no image?. and the prompt is on Fastboot again, and it does say "Fastboot USB", and I can hear the sound on the PC that the USB is connected. I tried from the original adb-fastboot folder I made and also tried unzipping into a new folder as seen in the pic, still getting "fastboot not recognized, Thanks again.
...".

PS I noticed under Recovery Options says "install from SD card" or something to that effect, would this help? (I just rebooted my phone into normal mode), maybe I should try the other way?

dannykewl said:
PS I noticed under Recovery Options says "install from SD card" or something to that effect, would this help? (I just rebooted my phone into normal mode), maybe I should try the other way?
Click to expand...
Click to collapse
actually the zip isn't a flashable one
so you can't use that option
try this way
download and install 4ext updater app(link in my signature)
open the app and select to install 4ext recovery touch
it will do the job for you

rzr86 said:
actually the zip isn't a flashable one
so you can't use that option
try this way
download and install 4ext updater app(link in my signature)
open the app and select to install 4ext recovery touch
it will do the job for you
Click to expand...
Click to collapse
Success! Thank you! I downloaded and installed RC2, hope that's good, as I feel more comfortable with that vs. RC3 still in testing stage. I will take a night of rest since it's Saturday night here and feel like doing something other than phones the rest of the night, LOL. I assume I'm good to go with putting viper530 in, will try on my own tomorrow night, I assume done in a similar way. Funny last couple of days, haven't been getting as long as a delay making calls usually, sometimes go thru right away instead of lagging for often near a full minute, but regardless I think I should go ahead with a new ROM. I assume viper530 compatible with T-Mobile USA. Thanks much again, rzr86!
Image icon not working to add pic, will try posting URL:
http://www.dannykewl.com/misc/GEDC0277.jpg

dannykewl said:
Success! Thank you! I downloaded and installed RC2, hope that's good, as I feel more comfortable with that vs. RC3 still in testing stage. I will take a night of rest since it's Saturday night here and feel like doing something other than phones the rest of the night, LOL. I assume I'm good to go with putting viper530 in, will try on my own tomorrow night, I assume done in a similar way. Funny last couple of days, haven't been getting as long as a delay making calls usually, sometimes go thru right away instead of lagging for often near a full minute, but regardless I think I should go ahead with a new ROM. I assume viper530 compatible with T-Mobile USA. Thanks much again, rzr86!
Image icon not working to add pic, will try posting URL:
http://www.dannykewl.com/misc/GEDC0277.jpg
Click to expand...
Click to collapse
congrats mate:good:
it is compatible with T-MOBILE USA
but before flashing the new rom make a nandroid backup from 4ext just in case

rzr86 said:
congrats mate:good:
it is compatible with T-MOBILE USA
but before flashing the new rom make a nandroid backup from 4ext just in case
Click to expand...
Click to collapse
OK, I think I did the backup right. I just chose the 4EXT app, it booted into recovery screen, I found Backup from Recovery and backup, chose Backup, then went back to Advanced and chose all 4 from there, I think they were system, boot, data, and cache. Rebooted, saved my whole SD card to my PC via the USB "use as disk drive" option. On the backup screen, the word "nandroid" was nowhere to be found (as some other screenshots showed using CWM), just said 4EXT Recovery something, pic attached. I assume I did right. Does 4EXT store the backup in the ClockWorkMod folder on the SD card? Seems that way to me, as now folders showing a bunch of .tar files under the "backup" folder, and the system, boot, cache, and data folders under the "Advanced" folder, and I don't see much in the 4EXT folder. I also backed up what I could using Titanium backup the other day.
Next I went into your signature and clicked the viper 530 link, and all I see on the resulting page is viper 521. Is there a link you have to 530, or should I use 521? I assume I use 4EXT to flash the new ROM, but from the SD card, thanks again, guess almost there.

dannykewl said:
OK, I think I did the backup right. I just chose the 4EXT app, it booted into recovery screen, I found Backup from Recovery and backup, chose Backup, then went back to Advanced and chose all 4 from there, I think they were system, boot, data, and cache. Rebooted, saved my whole SD card to my PC via the USB "use as disk drive" option. On the backup screen, the word "nandroid" was nowhere to be found (as some other screenshots showed using CWM), just said 4EXT Recovery something, pic attached. I assume I did right. Does 4EXT store the backup in the ClockWorkMod folder on the SD card? Seems that way to me, as now folders showing a bunch of .tar files under the "backup" folder, and the system, boot, cache, and data folders under the "Advanced" folder, and I don't see much in the 4EXT folder. I also backed up what I could using Titanium backup the other day.
Next I went into your signature and clicked the viper 530 link, and all I see on the resulting page is viper 521. Is there a link you have to 530, or should I use 521? I assume I use 4EXT to flash the new ROM, but from the SD card, thanks again, guess almost there.
Click to expand...
Click to collapse
nandroid is the backup you made
and there is no need to make an advanced(advanced backups specific partitions of your rom)
just go backup/restore-> backup and you are done(it backups everything)
and yes the backup is located to the cwm folder of your sdcard
there are links for 5.3.0 in the rom thread but if you can't find them take it from here
http://www.4shared.com/zip/7AmgN5Boce/ViperS_C2_530.html