Develop Bugs

[GUIDE] Turkeys' Ultimate Guide to Root Desire v42.1.1 "Misc Errors are History"

[GUIDE] Turkeys' Ultimate Guide to Root Desire v42.1.1 "Misc Errors are History"
Turkeys' ULTIMATE Guide to Rooting v42.1.1
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot (Adding Now)
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me you can do so below
GBP
EUR
USD

Root Guide - Pt. 1 - Info
So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...

Root Guide - Pt. 2 - UnrEVOked
So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...

Root Guide - Pt. 3 - Flashing Your First ROM
Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF

Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!

Apps2SD
A2SD
First, we need to get S-OFF to flash Amon-RA Recovery. You can use clockworkmod/ROM Manager to do this although it is very error prone so don't!
Now, I'll be honest, I really cba to write and provide support for people S-OFFing, so I'll link to someone elses instead.
But you can still post on this thread with questions, post there if the S-OFF doesn't work.
S Me OFF!
Download the AmonRA recovery image here before continuing. (Make sure you save it in the adb folder inside. the other stuff file below)
1) Make sure USB Debugging is on and make sure you downloaded the 'Other Stuff' file in post 2 and have extracted it to somewhere you can get to easily. (I always reccommend C:\root)
Next we need to flash Amon RA recovery. We will do this via the command line using fastboot. Your phone needs to be in booted Android mode for this next step.
2) Open a command prompt (Start > Run > cmd) and type the following: (you will need to replace some bits if you extracted the other stuff file to a different location.
Code:
cd \
cd root
cd adb
adb-windows reboot bootloader *let your phone reboot into fastboot before continuing*
fastboot-windows flash recovery what-you-called-amonra-recovery.img
fastboot-windows reboot
Next we are going to reboot into your newly flashed recovery image and repartition your SD card. This will format your SD card so please BACKUP your SD Card before continuing.
3) Open the Quick Boot app you downloaded in Pt. 4 and tap Recovery to reboot into recovery mode. Once you are in Recovery scroll down to and select Partition SD Card then select Partition SD. Now use the TRACKBALL to scroll up and down until you get the partition size you want and press trackball to continue. Now select 0 swap unless your ROM supports it and you know what it is. Then set the rest of the SD Card to FAT32 and press the TRACKBALL followed by the HOME BUTTON to confirm and start partitioning!
Note: If you want to use an ext3 or ext4 partition and your ROM supports it, select the SD:ext2 to ext3 option to upgrade to ext3 and the other one to upgrade to ext4. However, I would advise against doing this as you will wear out your SD Card faster.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.

Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Bravo. Now, you need to recall what version of Android you were on before you rooted. If you were on 2.1, you need to choose one of the RUUs which say 1.21.xxx.x. If you were on FroYo, you need to choose one that says 2.xx.xxx.x. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.

Fixing the annoying unrEVOked misc errors
Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse

Reserved for when I think of some awesome idea I just have to put here. #2

just say WOW! really Great!

Please don't forget radio info.

What a super great guide I really appreciate it, I think we all will

Nice one turkey, I just want to hug you so hard!
{
"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"
}

gascanieto said:
Please don't forget radio info.
Click to expand...
Click to collapse
Whoops forgot that, I'll add it in now
EDIT: Added quickly from an old guide, rewrite soon

Brilliant post
Really Really useful for nooblits

Great, easy guide. wish I had this when I rooted my desire ages ago.

There needs to be more stuff written in plain english - like this guide.
Very easy to read. I'm sure it will find its way into the sticky threads soon enough!
V42 beta....hehe
Anyway, good work! I love it.
Josh.

Can I make a suggestion and ask for a quick guide on updating your recovery image? I have clockwork recovery mod from the first unrevoked tool and thought ROM Manager updated it (it says I am using 2.5.0.7) however whenever I flash a ROM it always says I am on 2.5.0.1. Not sure on how to update it and if I should rather apply the rule if it aint broke dont fix it .

Real nice, one flaw: you use volume keys to navigate in Clockwork (which is default for unrevoked) and trackball in amonra IIRC
Sent from my HDfied HTC Desire

Actually, Clockwork uses the trackball too
Sent from my HTC Desire using XDA App

[Q] Confused and Overwhelmed. After some Clarity!

Hello!
I recently purchased a HTC Desire HD through a carrier in Australia after being a nokia dumbphone owner for my "connected life". I have done some reading into the Custom ROM scene and I am loving the potential benefits and modifications that are possible with them, however being new to Android, new to Smartphones and new to Custom Roms I am to say the least a little confused.
I decided this carrier added bloatware just has to go and after a little reading I like the idea of LeeDrOiD HD v1.2.
I have attempted to follow the instructions in the Leedroid HD thread.
http://forum.xda-developers.com/showthread.php?t=842802
Which tells me i Need to flash.
http://forum.xda-developers.com/showthread.php?t=842819
Which in turn tells "You will need the ENG HBOOT installed on your device to flash this recovery!"
and of course I could not find any details on what ENG HBOOT is let alone how to install it.
How deep does the rabbit hole go Alice? The multiple tears are becoming confusing and complicated and I am wondering if this is just a LeeDroid thing, or are these steps necessary for all custom roms? Or just the Desire HD. I am fairly confident with the safety of replacing a rom but the more steps by more people are adding uncertainty in the safety of the whole procedure and of course raising the probability of an under informed and maybe slightly reckless newby to brick a perfectly acceptable phone.
Is anyone able to reccomend a resource to better acquaint a Newby with this new territory? Is thier a more comprehensive guide to installing LeeDroid or "Rom-ing" an android phone.

Hi,
Give me a few minutes to pull together a few guides for you.
This Guide with Video is very helpful at performing all the little tasks that allow you to flash custom ROMs.
In short the ENG HBOOT allows the flashing of an unsigned recovery "Clockwork Mod", which then allows you to flash custom ROMs. Flashing the ENG HBOOT is a one time process, once you have done it there is no need to do it again.
Just a few questions,
1). Do you have a Stock HTC Unbranded & Unlocked ROM or a Carrier Branded ROM?
2). Have you rooted you DHD yet?

This is the way I personally went about the whole process, its a guide that zexbig posted and can be found HERE
Summary:
1) Download Paul's Visionary+ tool (I have used version r12) (google removed this app from market) so You will have to download it from Paul's website.
This tools enables root and removes new HTC protection.
2) Install engineering version of HBOOT to get S-Off (HTC bootloader, something like BIOS for Your PC)
This step is optional and it's not required in order to flash custom ROM's on Your DHD but gives You more freedom with Your device.
3) Install custom recovery image (recovery is special program which is invoked from HBOOT
in order to flash ROM onto Your device.
Detailed description:
1) Download Paul's Visionary+ tool
1.1) Click here to download http://android.modaco.com/content/ht...ne-click-root/ or download it from here http://forum.xda-developers.com/atta...3&d=1290501865
1.2) Install Visionary+ on Your DHD
1.3) Run it, enable "Set system r/w after root
1.4) Click "Temproot Now!" - Wait until it's finished
1.5) Click Attempt Permroot Now!
1.6) DHD automatically reboot's
To test that everything went fine download from market application "terminal emulator"
run it, type su
If You get after that sign # it mean's that everything went fine.
Time for next step!
2) Install engineering version of HBOOT to get S-Off
2.1) Download sfjuocekr DHD script for flashing HBOOT from here
http://forum.xda-developers.com/showthread.php?t=835746
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory.
(I have run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
2.3) Run Terminal Emulator
2.4) Type su
2.5) Type "sh /sdcard/DHD/check
(Please be aware that You have to type "sh" in front of command)
2.6) If everything went OK type
sh /sdcard/DHD/backup
2.7) If this also went OK proceed with
sh /sdcard/DHD/hboot
This command will install engineering hboot which have S-Off turned off.
3) Install custom recovery image
3.1) Since ROM manager now officially support's Desire HD, we will use it to download and install custom clockwork image.
3.2) Run android market app on Your DHD and download and install ROM Manager app from market.
3.3) Download and install ROM manager.
3.4) Run ROM manager and select first option (Flash ClockWorkMod Recovery).
3.5) Wait until ROM Manager say's that installation went successfully (Current version of ClockWorkMod is 2.5.1.3)
3.6) After installation tap in Rom manager option Reboot into Recovery to test that everything went well.
3.7) DHD should reboot in clockwork recovery manager.
Click to expand...
Click to collapse
-Visionary is now v14+, not 12 as posted.
If you have any problems, just let us know.

Quick Response thanks!
It is unfortunatly a Carrier Branded rom. Full of widgets that are just links to webpages. What is even worse is I bought my phone through a company who leases lines off the carrier so because I am technically not with the carrier I can't use their aps even if i wanted to.
I believe I have temp rooted it so far. I have downloaded VISIONary +

Epic.. Thank you kindly. I am in the process.

I don't understand why carriers have to ruin the whole "Android Experience" by bundling awful apps that nobody wants, otherwise they would of downloaded them themselves.
The last guide I posted is the one I used. Once you have followed all of the steps then your in a position to flash a custom ROM. If you are planning to overclock or underclock then you will also need to find a suitable "Kernel" to flash with your ROM. Most ROMs do come complete with a custom kernel but that may not be the best for your particular needs.
Once bit of advice. Always, always a backup of your ROM before you flash anything else.
Flashing custom ROMs is easy once the above steps are complete.
1). Download your chosen ROM.
1a). Optional Download your chosen Kernel.
2). Transfer ROM (+ Kernel) to your SD Card, place in the root of the card.
3). Boot into Recovery. Power off (Ensure HTC Fast Boot is disabled), Power on whilst holding VOL DOWN, using volume keys select Recovery, press power to enter.
4). Create Backup, backup and restore > backup.
5). Wipe All Data including cache
6). Install .zip from SD Card, Select the correct ROM zip and confirm.
7). Optional, repeat with Kernel, if necessary.
8). Reboot.
9). Bask in glory, you have conquered your smartphone.
Again, if you want more info feel free to ask. We all had to learn once, or twice.

For Clarification on HBOOT loading.
2.2) Unzip it and copy it to Your SDCard (It's important that You have on Your SDCard root directory with name DHD and all files inside this directory.
(I have run into the strange problem for which I'm not sure is it problem with my PC or DHD, each time when I connected my DHD via USB cable my SDCard was automatically mounted as Disk Drive instead of just being in "Charge only" mode. I resolved this by removing back cover and ejecting SDCard and inserting it again while phone was operational, which is very unsafe thing to do!).
I do want to be viewing the Android device as a disk drive?
Secondly Do I create a folder on the SD card in the root directory called DHD and then drop the 3 files contained in the Zip file into that folder?
Example
Root Directory
>.data
>Alarms
>Android
>bugreports
>DCIM
>DHD --Newly created folder
>>DHD-dumb --dragged and dropped
>>DHD-smart --dragged and dropped
RTFM.txt --dragged and dropped
>downloads
etc..

Yes you do want to view it as a disk drive.
You are also correct with the folders.
SDCard/DHD/ - place files here -

Ok my description failed.
Instead of the folders listed above
">>DHD-dumb --dragged and dropped
>>DHD-smart --dragged and dropped
RTFM.txt --dragged and dropped"
should I be taking the contents of (smart or dumb?) and placing that in the DHD created directory?
obviously the commands in the terminal dont correspond to having the files in a sub folder. I appologise for you having to answer obvious questions however I am a little weary of bricking.

I'd rather you post a question and get it answered before you post a problem and have an expensive paperweight.
Take the "DHD-smart" folder from wherever you extracted it, place that on your SD Card, then rename that folder to just "DHD".

Excellent. All Is working as planned. I'm in the process of D/L ing Leedroid rom.
Thanks for your help again.
I'll post back once I have things up and rolling.

No problem at all.
Just remember to make a backup from within "Recovery", it will save you one day.

I appologise I forgot to Post back.
Everything is running sweetly now, absolutley no bugs with the Root or new LeeRoid rom.
Thanks again for your help.

Daft Templar said:
I appologise I forgot to Post back.
Everything is running sweetly now, absolutley no bugs with the Root or new LeeRoid rom.
Thanks again for your help.
Click to expand...
Click to collapse
Welcome to the ranks of Android hackers. Health warning: flashing is addictive.
Sent from my performance enhanced Desire HD.

Yes it is
Sent from my Desire HD using XDA App

[Q] a little help plz

just got my HTC Desire HD back and its updated to latest fw
android version 2.3.3
htc sense 2.1
baseband 12.54.60.26U_26.09.04.11_M2
kernal version 2.6.35.10-gd2564fb
software number 2.50.405.2
can this be rooted now as ive tried visonary+ and gingerbreak.apk and it doesnt do anything just hangs
i really miss not have my desire rooted
if i can root it is there a tutorial that works that i can follow a fairly easy 1 lol
thanks guys for any help you give me

Yes you can still root but you need to downgrade. Search for a user named jkoljo he has two gives.
One for downgrading + rooting and another one for s-off using his simple but effective tool.
Sent from my Desire HD using xda premium

Gingerbreak does not work on the DHD.Just like the poster above me wrote first you need to make a gold card if you have a branded dhd and then you have to downbgrade.
Then you need to use visionary to temp root and then you use visionary to perm root.Then you need to use on click s-off and super cid tool which is in the developers forum I believe.And after that you can install custom recovery and rom.
They have here very good guides to guide you so take your time and read carefully.
Good Luck!

thanks
ill take a look into it now
thanks for replys
c:\downgrade>adb push psneuter /data/local/tmp 'adb' is not recognized as an internal or external command
operable program or batch file
please help me

Try this:
Introducing Ace Advanced Hack Kit
[*]COMPLETELY INTEGRATED/INVISIBLE GOLD CARD PROCESS
[*]Only ONE menu step - HACK ACE
[*]No ROM downgrade required (only radio/kernel)
[*]No wiping data
[*]Rom is fully working (yes, inc wifi)
[*]Fully rooted with insecure boot image (supports adb remount for rw system)
[*]Busybox manager app installed
[*]S-Off, superCid & carrier sim unlock
[*]Correct Radio is automagically restored for HSPA+ operation
[*]Clockworkmod Recovery and Rom Manager included
[*]Both stock Froyo and Gingerbread supported
[*]Easy return to stock
[*]Much smaller download
[*]Much smaller firmware flash to obtain the exploit - comparatively very fast processing.
Notes:
[*]Please do NOT run the hack step if you are already S-OFF and are running a custom ROM. It's pointless, and while it won't brick you, you can get jammed up a bit. This is for stock devices only.
[*]WINDOWS: IMPORTANT - disable all malware (Antivirus detection etc) detection before unarchiving the hack kit. Keep it off thoughout the hack kit processes. Many Windows malware detection programs report false positives, deleting or binding critical files required by the process.
[*]Do NOT try to run this from a VM - particularly VirtualBox. You WILL get jammed up and may wind up flashing an RUU to recover, losing data in the process.
[*]After kernel downgrade - video is lost - this is okay as adb is working and can be used to finish the process. When the process completes, everything is restored and fully working.
[*]Because the procedures have changed completely, whatever Youtube video people are watching is now completely wrong. READ THE EFFEN MANUAL. There is no substitute.
[*]Make sure you extract the hack kit to your pc maintaining the directory structure in the archive you downloaded. The docs will be in the root directory of the unarchived kit, as will the scripts. READ THE EFFEN MANUAL.
[*]I can't believe that so many people are asking where the effen manual is. THE EFFEN MANUAL IS IN THE EFFEN HACK KIT.
[*]This kit should work fine on ALL HTC Inspire and HTC Desire HD which require the radio/kernel downgrade before a root exploit is available.
Issues during downgrade:
[*]IMPORTANT: BEFORE SWITCHING FROM DISK DRIVE TO CHARGE ONLY MODE, ALWAYS EJECT THE GOLDCARD WITH PC SOFTWARE TO FLUSH WRITE BUFFERS AND AVOID CORRUPTING THE SDCARD.
[*]model ID incorrect update fail - this is because your goldcard is not working.
[*] Stop watching the out of date Youtube video, get latest version and READ THE EFFEN MANUAL. Reading is fundamental.
Download: aahk-03102011.zip md5: 73c37116324bd205bfbb9850dbcf1235
this (just below) is HUGE
viperbjk is with Revskills, and his contribution is key to finally allowing one step processing where a goldcard is required.
The entire process is now one menu step. A second step will be required to clear your conscience - DONATE to:
RevSkills http://psas.revskills.de/?q=goldcard [Donate here]
and
Electronic Frontier Foundation http://www.eff.org/ [Donate here]
Ace Advanced Hack Kit Changelog
AAHK 03102011
[*]Another DHD Bugfix - properly ID DHD model when checking adb connectivity
AAHK 26092011
[*]bugfix - froyo boot image restore
AAHK 25092011
[*]Added service and process stops for some known bad actors in windows
[*]Added boot images for both froyo and gingerbread for non-NAM device
[*]Stock ROMS should now be fully operational on all DHDs.
AAHK 19092011
[*]Increased Windows sleep setting
AAHK 16092011
[*]OSX wget bugfix
AAHK 14092011
[*]Froyo radio restore fix in hack process
AAHK 13092011-2
[*]Added additional serial prefix support for a EU DHD
AAHK 13092011
[*]Gold card creation now completely integrated/invisible - Only one step required
[*]Complete downgrade no longer required - no data loss
[*]Smaller, faster, process (uses small firmware update and not an entire RUU)
[*]Original ROM is retained and is fully functional, fully rooted
[*]New replacement ROM not required
[*]Correct Radio is automagically restored for HSPA+ operation
V12.3 (08-11-2011) (V12 has been moved here: http://tinyurl.com/3kwx5zt)
[*]Fixed Broken Windows script
V12.2 (08-11-2011)
[*]Fixed updated recovery
V12.1 (08-10-2011)
[*]Updated Recovery
[*]Added Missing OTA Radio update in Linux script
[*]Added clean step in options menu
V12 (08-08-2011)
[*]Froyo/Gingerbread automatically detected
[*]Android 2.3.3 (Software #2.47.502.7) support added via fre3vo. Possibly others.
[*]Downgrade failure detection
[*]Includes AT&T OTA Radio Option
[*]RCDATA included in both radios
V11 (04-29-2011)
[*]Menu Driven
[*]Now restores sound
[*]Perma rooted
[*]Rom Manager installed
[*]Fewer steps
[*]Far less user interaction
[*]Integrated cid reverser,
[*]Integrated Goldcard write
[*]No more phone term commands
[*]No more flashing CWM from ROM manager required
[*]Faster, more reliable - MAJOR UPDATE
V10 (Stone aged process)
[*]Integrated SDCard CID reverser (OSX/Linux versions (me) and Windows Version (shad0wf0x)
[*]Integrated Goldcard image writing for all supported platforms
[*]Far fewer Goldcard issues
[*]No more terminal commands
[*]Much simpler
[*]Much faster
[*]Far, far, far, far, far fewer user errors. Way less. Really.
< V10 prehistoric
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you have read this post and the effen-manual and get stuck during processing,
help is available in IRC at http://webchat.freenode.net/?channels=#liberatedAria
Yes, there are stupid questions.
Questions that will get you immediately kickbanned from the IRC channel with no further explanation:
[*]Q: Do I need to flash a ROM after the hack kit is finished?
[*]A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of "fully functional" is vague?
[*]Q: Do I need to flash a radio after the hack kit is finished?
[*]A: Kickban. The hack kit is a complete, one step process. If it finishes correctly, you are finished. What part of "fully functional" is vague?
[*]Q: The options menu has options to flash radios. Do I need to flash a radio?
[*]A: Kickban. What part of "optional" is vague? This option is to make it easy for people who may have flashed another radio and want to flash back to these particular radios.
[*]Q: Do I need to plug in the phone?
[*]A: Kickban. If you know how to enable usb debugging without a USB connection, then I'll change this policy. In the meantime, asking such a question just makes me think you have not read anything and/or have dedicated yourself to being an idiot.
[*]Q: What's the best ROM?
[*]A: Kickban. The whole point of this is to give YOU control and allow YOU to decide. Yes, we prefer CM7 and I think it's the only real Android choice available, but don't ask us to think for you. If you don't see that pretty much everything else is either ripped off or HTC Non-Sense, then you haven't done your homework and that's okay. Just don't ask, because in the end, it's YOUR choice.
[*]Q: Facebook doesn't work.
[*]A: Kickban. This has nothing to do with anything but Facebook. Go ask Facebook, not us.
This IRC channel is for people who read, attempt and get stuck because of PC issues or an occasional bug introduced with a new feature.
It's not for people to troll those who dedicate their time for support without any compensation by asking a series of mindless, inane questions and observations for attention.
We're too busy for that - even if we have nothing to do. It's beyond annoying and you will be kickbanned without warning. Read, search, think, try, then ask.
The people in liberatedAria have been helping noobs without compensation for over a year now, with generally very good results and a generally good nature, despite being abused by some on almost a daily basis.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks to:
Revskills for their fantastic gold card algorithym
GenePoole for the kickass android goldcard binary based on above
agrabren for fre3vo, the Gingerbread temproot used
scotty2, the author of psneuter, misc_version and gfree
shad0wf0x for his windows scripting contributions
ktilcu for DOC contributions
anthony1s for his review and unique perpective
The > 35,000 users who have already downloaded the hack kit, most of whom seem to get though it without issue.
from my Inspire 4G using xda premium.
Good luck.

[GUIDE][All-In-One]LG Optimus Me P350

So, I decided to write this guide here as I couldn't find a complete one and had to jump from thread to thread (and sometimes even the sub-forum) for finding the answer.
First I wrote it in my blog and I decided to post it here. Maybe some steps are vague in details but I'm planning to detail it even more (remember, I wrote it in my personal blog first). So, here it is:
AIO LG Optimus Me P350 Guide​
Some Personal History
My experience with Android. UF! Where to start? So, I got my phone from the United States. You have no idea how wonderful it was to have the phone in my hands. Anxiety and curiosity. For some reason I always read that the first thing anyone does is root the phone and then continue doing everyday activities that do not require root, so I tried to live without rooting the phone, but I couldn’t wait for the week to go by. I had to get the best! Small problems, fixes and updates. And since I have my phone on sale, I publish this step by step guide to modify it and not die trying.
Tech Specs
Let’s start from the beginning, know the phone. Mid/low-range phone created by LG for those in a short budget but want to have a good Android experience. It has a 600 MHz processor, 256 MB RAM and ROM capacity of 512 (140 MB available for applications and data). 2.8 inch capacitive screen, 240 × 320 screen resolution. Wi-Fi b/g wireless connection, Bluetooth 2.1 with EDR, and USB 2.0 up to 480 Mbit/s. 3.1 MP camera (no flash) and FM Radio. Not bad for a basic device. Complete specifications can be found here. Enough for a casual user. But if you’re not a casual user (hence a XDA member), read on.
First of all, everything you do on the phone number is on your own. You yourself are responsible for what you do, not do, stop doing, fail, fail to read and/or shortcut you may have taken. These steps are the ones that worked for me. I am not responsible if the phone dies in the process, the cat bites the cable in the middle process, the heavens begins to fall, the 3rd world war starts or if the neighbor has a heart attack … You’ll be calling 911 afterwards… You’ve been warned!
USB Debugging
The first thing you have to learn is to turn on USB debugging. Here is a guide how to do it (If you wanna see a pictorial guide). But essentially you have to go to Settings > Application > Development and check where it says USB Debugging. Pretty easy. What is this good for? Well, for starters. modify the phone however we see fit. But most important USB Debugging allows the phone to communicate verbosely with PC with the Android SDK installed. More on this later.
KDZ Updater
KDZ Updater is an application used by LG for flashing official operating systems themselves. How did this application saw daylight outside the company, I don’t know very well, but apparently a leak appeared on LG India, but not sure. In any case, this application is our last line of salvation and the main tool for our little friend.
To install official KDZs must follow these steps:
Install the updated drivers by following the steps listed on this page.
Connect the phone with USB Debugging activated
IMPORTANT: Disable the Virtual USB Modem device from Windows Device Manager. Omit this step and the device may brick in the upgrade process.
Run the application in Administrator mode (only required on Windows Vista / 7).
In the Type drop-down list select 3GQCT and in PhoneMode, DIAG. Where it says Version, will appear the version that is installed on the phone.
Select the KDZ file to install by clicking on the button with the folder icon. Preferably save the file KDZ in the root of the hard drive as there will be little chance for error when reading the file.
Press the button “Launch Software Update”. The phone will reboot into Emergency Mode. This is normal.
Pray all you know and go for a cup of tea. The process takes about 8 to 10 minutes.
If all went well, the phone will turn off and the program displays a line that says = FINISHED =.
To start, first go into recovery mode by pressing the following buttons: Vol- & Power. This will make any old or unnecessary information to be removed. The phone will reboot into the system normally.
Original Thread
Root (Gingerbreak and SuperOneClick)
Ok, what we came here for. Rooting the phone. How do I do? It’s scary! Says who?! Lets start with the choices we have. Ok, we have the phone, but we have not updated anything, How do I get root? Gingerbreak comes on the scene. Pretty simple process: download, Enable USB Debugging, run, press Root, wait for the restart, confirm. Simple, right? Also read the instructions and warning on the link above in case something I overlooked, but that basically is the process. By the way, install Busybox, very important for future processes.
Stop, stop, stop … And if I upgraded the phone? Gingerbreak seems not to work! What do I do?! Mainly, DO NOT PANIC! First things first. Go to “About phone” and see that version it says; something different than 2.2? Cool, no problem. SuperOneClick comes on scene. Download the application, unzip. I assume you already installed the drivers, right? Otherwise, do it and come back when you have done so. Ready? Continue. Turn on USB Debugging and connect the phone to the computer. Execute the application and press the button that says “Root”. Need more information? Here is a video explaining step by step (its in spanish, but graphics needs no language) and if the antivirus gets all paranoid, read the explanation here.
Recovery (Amon-RA and CWM)
Ok, moving on. Just as clarification: From this step on, the phone should already be rooted. Otherwise, you will mourn at the very end because the phone will brick and you’ll end with a very good and expensive paperweight. What is a Recovery? Here the answer.
This is essential before changing the insides of the phone and a step that I believe needs to be forever linked to rooting process. Why? Simple! Installing a Recovery allows full system backup and restore if something goes wrong. That linking to rooting process? Because if you install a root application, modify the system, and damage the system, it can be restored to a previous time and we’re all happy campers. See?
So this is where we get our hands dirty. Initially, I ask again, have you installed the drivers? (From this point on I shouldn’t ask) Have you rooted the phone? Responded twice yes? Perfect. Now, download the Android SDK or only the .zip attached here (unzip preferably in C:\ADB\) to continue this process. Also download the Recovery that you will install, we have Amon-RA and ClockworkMod (CWM) v5, v5 touch, and v6, extract the recovery.img file to the folder where adb.exe is (If you used the SDK installer, should be at C:\Program Files\Android\android-sdk\platform-tools\; if you used the .zip, and extracted as recommended, C:\ADB\). Which to choose? My recommendation, CWM v5 (either one). Connect the phone to the computer in with USB Debugging activated. By the way, how do you feel using command line in Windows? Moving on…
Open a command window, go to where adb.exe is and run the following commands:
Code:
adb push recovery.img /sdcard/
adb push flash_image /sdcard/
With this we have copied what we need into the phone’s SD card. Just to clarify: 1) the flash_image file can only be found in the recovery Amon-RA zip (not sure if it is generic or modified exclusively for the P350, then I’d rather play it safe) and 2) CWM recovery v5 and v5 touch files come in zip-installable, but you can open the file and use recovery.img in it. In CWM v6 there is an installable zip and another to follow this same process. Lets continue…
Code:
adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
Up to this we have only prepared the area to install the Recovery. It it recommended to reboot the phone in this step, in case you run out of virtual memory but is not really so necessary (If you see an error message, then reboot). That’s yours decision. Continue…
Code:
adb shell
$ su
# flash_image recovery /sdcard/recovery.img
# sync
To confirm that everything is installed without issues it must happen one thing and do another thing. What must happen is when you execute the flash_image command, no errors should appear, if otherwise reboot and repeat the last block of commands. What must be done is execute the command reboot recovery and if everything is alright, you should go into Recovery menu, if not then all the information has been erased and back to square 1 (it happened to me the first time).
Kernel
Just for safety: are drivers installed? Root acquired? Recovery installed? Already made a backup of the ROM in use at the moment (so far should be the LG ROM)? Do it!!
So, what’s a kernel? Here’s the answer. What choices do we have? Well not too many, it depends. Are we still on the LG Stock ROM or a Froyo-based ROM (oh, getting ahead aren’t we?!)? Well, the truth, with this ROMs there are not many: Team Pecan Kernel would be my recommendation, RoQ Kernel which also works quite well. CM7 ROM or any other Gingerbread-based? Ron's RM CAF Kernel (updated weekly), pax0r kernel (discontinued), Vivek Kernel (also discontinued but higher than pax0r). Read how to use Recovery for the installation of installable zip files from Recovery. This is also applicable for the installation of ROMs.
ROM
Still with me? Still no cardiac arrest? Relax, breathe! As we reach the last modification process of the phone. After surviving this, you will have the full capacity to recover the phone from any eventuality. Dictionary, which is a ROM? Here the answer.
ROM, What options do we have? Well, although it may seems, there are many options to choose from! We have some created from source code, based-on and others that have been “ported” to work with the device. Among those created from the source we have: CyanogenMod 7.2, Pure CM Invasion and CyanogenMod 9 (Work in Progress, not quite stable), based-on: Androm x4.2 (CM7) Arc XP (CM7), Gingerbread Optimus UI (CM7) Gingerblur (CM7) and MIUI v4 (based on CM7, Arc XP with a theme very close to the real MIUI, Japanese ROM). Ports: JoyOS, ICS (Discontinued unstable), BeautySense (Decent and functional).
Further Development/Tweaks
At the moment a new tool has been released called LG P350 Pecan Toolkit, developed by antdking. Its in early development and so far it roots, unroots and installs recovery. Saves some the hassle of the command line but if we haven’t gone through all the problems and commands, what have we learned? Anyways, here’s the original thread where you can follow the development and post ideas or bugs.
If you wanna go all-in into ROM cracking and research, we have also the LGExtract tool, which unpacks the KDZ file into bits and pieces. DZ Extract Tool extracts the files within a DZ package very much into source code. I've used these tools but as my experience with coding and android development is very close to none all I've done is extract the files and read them. Antdking reminded me of a simple yet powerful tool to continue decompiling the LG filesystem called unyaffsmbn. I came across it when we were trying to decompile baseband (amss.mbn) for CM9 without success, just lo later know that the tool just decompiled system.mbn. Oh well. Antdking compiled unyaffsmbn into a nice little tool ready to work, here it is.
The volume on this phone, as many may know, is low. But there is a way to elevate it. Execute the phone app and press: 3845#*350#. This will bring up a Hidden Menu. Go to: Device Test > Sound Test > Audio CAL Tool > Subsystem Calibration. In the Gain Type dropdown list, select Speaker Gain. Set Data textbox gets focus, input the number 90 and press OK button. In Gain Type, select Input1 Gain, and we press Ok button again. Exit the Hidden Menu. This will elevate the speaker volume but just temporary, it will be restored to default values when rebooted. So either don't reboot or repeat this process everytime you reboot.
And that would be all. Happy hacking!
Great kudos to the real developers here:
drapalyuk: For the first ever recovery for P350, Amon-RA
pax0r: Started it all, Kernel, ROM
ron gokhle: ROMs, Kernel and Recovery builds
vivekkalady: Kernel, Touch Recovery, first ICS port, and some other fix work
nikhil4186: For the KDZ Guide (although written originally for LG P500
antdking: For a great-to-be toolkit

great guide good job

Nicely written.Its a really good guide for all those who are new to P-350 and I believe that it will help them to learn some of the basic stuff.Well done!

to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy

antdking said:
to go on the end of this guide, how to extract the files out of the system.mbn to get the system files
http://db.tt/7VruqEzr
it returns similar files to what you find in a rom
I did not make unyaffsmbn
I made the tool that uses unyaffsmbn
enjoy
Click to expand...
Click to collapse
got the PM and you reminded me of that tool (I remembder I came across it when we were trying to crack amss.mbn for CM9)... I'll post the original thread and the tool you just mentioned...

Updated adding unyaffsmbn tool... Thanks antdking!

Added Volume tweak for speaker to sound harder.

Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me

dbarrera said:
Added P350 (and guide) to XDA wiki. http://forum.xda-developers.com/wiki/LG_Optimus_Me
Click to expand...
Click to collapse
thanks man :good::good::good::good::good::good::good::good:

Guys We have got Official Support From XDA Please Move This Thread To Our Device Section

Very good!!!
I placed some problem I am having, just in case you have time an patience for this case.
Tks
http://forum.xda-developers.com/showthread.php?t=2461183

Great Guide Man! Thanks a lot.

[GUIDE] [T-Mobile] Unlock Bootloader, Install Custom Recovery, Root, S-Off

This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
There was speculation that the phone's build date might be a reference for who's phone was compatible with firewater. This is not the case. There is no correlation between build date and compatibility. A further explanation is given under the S-Off instructions.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXXdevice
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXXfastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links​g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
>
And end with this line:
>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.​h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Hi Recipient
Attached in this mail is your unlock bootloader key file. To use this file to unlock your device, simply follow the remaining instructions on the website to complete the process and successfully unlock your bootloader.
Please remember that unlocking your bootloader may void all or parts of your warranty and your device may not function as intended by HTC. Unlocking the bootloader is for development purposes only.
* Click here to continue the bootloader unlocking process.
The bootloader unlock key file can only be applied to the device with which you generated the token.
Please do not reply to this email which is auto-sent by server.
If you need to contact us with questions please click here.
Sincerly,
HTC
Click to expand...
Click to collapse
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader​i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' ...
OKAY [ 0.151s]
writing 'unlocktoken'...
unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.​j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.​
​
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM​a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.​e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' ...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.​
​
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.​
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
There was speculation that the build date was an indicator of compatibility with firewater's S-Off method. As several people expected, there is no correlation. There are batches of components that HTC purchased from various manufacturers that vary in compatibility with the firewater exploit. At this point there is no known method to determine if your phone will be compatible with firewater. Unfortunately, it's just a shot in the dark. So, if you're comfortable, give it a shot and hopefully you're compatible.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)​Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.​
​
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522​
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones

FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app

jcase said:
FYI I didn't develop firewater, just weaksauce. That is @beaups baby
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the info! Changed in OP.

Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.

Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app

fryingpan0613 said:
Where do you find the build date
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's on the bottom edge of the box on the same sticker as IMEI.
Sent from my HTC One M8
egcthree said:
Your posting title is slightly misleading since a good portion of T-mobiles m8s are not compatible with firewater.
Click to expand...
Click to collapse
Updated OP to show that firewater may not work without having to show the contents of the S-Off info. Thanks for the comment.

I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8

OctoberNexus said:
I get the whelp yada yada and my build date is 4/10/14 do I need to have busy box installed?
Sent from my HTC One M8
Click to expand...
Click to collapse
Nope. That means that firewater won't work for you and S-Off isn't yet achievable for your phone.
OP updated with your build date.
Sent from my HTC One M8

Hopefully there will be another way in the future until then running GPE ROM which is a lot better than nothing still not what I had in mind when purchasing this thing.
Sent from my HTC One M8

Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:

thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list

VolcanicSkunk said:
This guide is for the T-Mobile HTC One M8. Bootloader Version: 3.16.0.0000
Disclaimer: I am not responsible for your device. You are performing the steps detailed in this post at your own risk. Support for any phone unlocked through this method falls upon you. Assume that this method voids any warranty that may have come with your phone. Also, currently there is no known way to restore the T-Mobile variant to complete stock settings after using HTC Dev Unlock and/or achieving S-Off. Maybe at a later date this could be possible, but not yet.
*Please do not quote this post. It's so long.*
Support for recoveries, firewater, or other tools used herein should be asked in their respective thread or forum.
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone. Right now firewater is the only method to achieve S-Off on our M8 variant.
This thread is for people that understand what this whole post means. If you are unsure of the terms, please search. The terminology is readily available and nothing should be difficult to find.
I work and go to graduate school, so this thread will be updated periodically, but I will not be able to provide a lot of support. This guide reflects my steps to achieve root and S-Off, and is just intended to give someone new to the phone an easy to read step-by-step guide of what the process will be.
I also hope we can condense the large amount of information floating around about achieving S-Off on our variant into one thread.
Required Files:
HTC Dev Unlock Process:
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Recovery (choose one):
Team Win Recovery Project (TWRP) 2.7.x for GSM Phones
http://teamw.in/project/twrp2/225
PhilZ Touch ClockworkMod (CWM) Recovery
http://forum.xda-developers.com/showthread.php?t=2703223
S-Off:
Firewater
http://firewater-soff.com/instructions/
Firewater M8 Original Thread
http://forum.xda-developers.com/showthread.php?p=51698035
Useful Commands:
adb devices
(after installing adb, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>adb devices
List of devices attached
FAXXXXXXXXXX device
fastboot devices
(after copying the fastboot utility downloaded during the HTC Dev Unlock process to your sdk\platform-tools\ directory, this will tell you if your phone is detected by the computer)
expected output:
Code:
C:\sdk\platform-tools>fastboot devices
List of devices attached
FAXXXXXXXXXX fastboot
1. Unlock bootloader via HTC Dev Unlock (http://www.htcdev.com/bootloader)
a. At the top of the page, either register for a new account or log in with an existing one
b. Under "Supported Devices" choose "All Other Supported Models"
c. Click "Begin Unlock Bootloader"
d. A prompt will ask you to continue. Read this. If this prompt scares you, stop immediately. Otherwise, press "Yes" to continue
e. Accept the legal terms and conditions.
f. Follow the on-screen steps provided.
Step 1
After powering down, press Volume Down and while pressing Volume Down, press Power holding both buttons to start the device into Bootloader mode. If you have difficulty, power up normally, go to Settings->Battery and deselect Fast boot. Power down and try again.
Step 2
Use the Volume buttons to select up or down. Highlight Fastboot and press the Power button.
Step 3
Connect the device to the computer via a usb cable
Step 4
Download the fastboot binary for your OS using the provided links​ g. Follow the on-screen steps provided
Step 5
Open a command Prompt: Windows: Start->"cmd" Mac: Applications->Utilities->Terminal.app Linux: Terminal
Type in Command Prompt: fastboot oem get_identifier_token.
Step 6
You will see a long block of text. Copy and paste this text into the the token field below (in the Windows command prompt: Right Click > Mark > highlight the block of text > Right click to copy. Mac users can use cmd-option to mark and select text.).
When copying the token, start with this line:
<<<< Identifier Token Start >>>>
And end with this line:
<<<<< Identifier Token End >>>>>
(Note: Do not copy the INFO or (bootloader) prefix)
Step 7
Paste this string of text into the token field and hit Submit in order to receive your unlock code binary file. You will receive this information in your email.​ h. After hitting submit, HTC will send you an email. Sender is HTC-Unlockbootloader. Subject is "The key to unlocking your HTC Device."
Email Message:
Attached to the email is Unlock_code.bin. This is the file you will need to download in order to unlock your bootloader. This file is device specific. You cannot use this file to unlock any other HTC phone. Please do not try as this will probably result in a brick.
Click the link provided in the email to continue the steps to unlock your bootloader​ i. Follow the on-screen steps provided
Step 8
You will receive an email with the attachment: Unlock_code.bin. Save this file in the same folder as your fastboot files (For Example: C:\Android).
If, after a short period of time, you have not yet received the mail, or you have received an email from HTC, but does not contain an attached file, it is possible that more stringent spam filters and anti-virus programs will block this mail or attachment.
In order to ensure that you receive the email with the attachment, we suggest you consider using a non-corporate email server as corporate servers tend to have more stringent attachment policies. If you have not received the email at all, please check your spam folder in your email client to check if the email was filtered out.
Step 9
In the command prompt type: fastboot flash unlocktoken Unlock_code.bin. In the command prompt you will see the following message:
Code:
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' <0KB>...
OKAY [ 0.151s]
writing 'unlocktoken'...
<bootloader> unlock token check successfully
OKAY [0.006s]
finished. total time: 0.158s
Step 10
On your phone you will now see the disclaimer. Please read this carefully as this action may void your warranty. Use the Volume buttons to highlight your choice, and the Power button to make your selection. If you select Yes, your phone will be reset to its’ factory default settings, and your bootloader will be unlocked. If you select No, your phone will reboot and no modifications will have been made.
Step 11
To re-lock your bootloader, in the command prompt, type: fastboot oem lock.
Note: This will not restore the factory default lock, but will simply re-lock the bootloader so no further changes can be made. Furthermore, if you want to unlock your bootloader again, simply repeat step 9 with your original unlock key file to unlock your phone again.​ j. Congratulations, your phone now has an unlocked bootloader! If your phone hasn't done so already, reboot it and let it sit at the welcome screen for the requisite 5-10 minutes to settle. Turn off your phone, and reboot to HBOOT with volume down + power button. Select fastboot.​
​
2. Install a custom recovery
As far as I know, there are two recoveries that are fully functional with our M8 variant:
TWRP
PhilZ Touch CWM​ a. Download your chosen recovery from the above links.
b. Rename it recovery.img
c. Drop it in the same folder as your adb and fastboot binaries.
d. After booting to fastboot mode, make sure your device is still plugged in and run the following command in your command window:
fastboot devices
Your computer shouldn't have any troubles recognizing your phone since we just went through the bootloader unlock, but it's always best to be safe.​ e. Now run the command:
fastboot flash recovery recovery.img
Expected output:
Code:
C:\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' <14,818KB>...
OKAY [ 0.871s]
writing 'recovery'...
OKAY [ 1.501s]
finished. total time: 2.543s
f. Congratulations! You now have a custom recovery installed.
g. I recommend immediately making a backup of your fresh operating system (pre-root) by selecting HBOOT from the fastboot menu, then selecting and booting into recovery
h. After booting into your new custom recovery select backup from your list of options and proceed to select your backup location (internal or micro sd) and continue to the backup. It will be quite large, but this will provide you a good starting point should you ever need to restore to factory settings for any reason.
i. I use TWRP, because it will automatically prompt you to install root and SuperSU upon rebooting from recovery.
I am unsure how to achieve root after flashing PhilZ Touch. If anyone provides the info I will add it to this guide.​
​
3. Achieve S-Off (Hopefully!)
The instructions to attaining S-Off are listed on the firewater s-off page linked above. They are really comprehensive and you should follow them to the letter. Make sure that you read through their prerequisites as well.
Note: On prerequisite number four, it states that you must be "HTCDEV unlocked/rooted." Please read this as you must be HTCDEV unlocked AND rooted.​
I didn't want to post the firewater team's instructions here (I didn't ask permission yet), so this section will be more for information regarding the S-Off process that I have gathered from other threads and this one going forward.
Issues seen with Firewater:
Firewater does not work on every T-Mobile M8. If, when running firewater, you see "Whelp, this sucks..." firewater will not work on your phone.
The speculation is, there are different components used during the builds due to sourcing those components from different companies. It seems that some people believe that the phone build date may indicate the devices that have components that are compatible with the exploit. So we'll document this to try to see who achieved S-Off on which build dates.
Issue: Firewater hangs but does not give the "Whelp this sucks..." message:
Possible Solutions: Your device is likely compatible. You must be persistent. Keep trying.
Hit Ctrl+C to exit the exploit and try again starting from "adb reboot" (from @Fenny)
Unplug your USB cable, reboot your phone manually. Once it boots up, plug in your USB cable (from @epsix)
Plug in your USB cable, adb reboot. Once it boots, go to Developer Options and uncheck and recheck USB Debugging (from @epsix)
Install BusyBox (from @renn9420)​ Issue: After running adb reboot command and pushing firewater phone shows up as "offline"
Possible Solutions: Make sure that you granted su permissions to your adb shell through SuperSU
I had this happen to me. I would go to run the command and suddenly, the phone is disconnected. I ran through the adb reboot steps a couple of times and finally when executing firewater it ran. Went through the steps 3 times before it ran.​
Build Dates S-Off Achieved On:
04/01/2014
04/04/2014
04/07/2014
04/12/2014​
Build Dates S-Off Not Achieved On:
04/03/2014 x2
04/08/2014
04/09/2014
04/10/2014
04/11/2014​
​
4: Other
a. @Fenny noticed that /data/preload/ gets emptied after HTC Dev Unlock. If you're hanging onto your stock ROM and don't plan to change to a custom OS you'll want to replace these files. Go here to replace them: http://forum.xda-developers.com/showthread.php?t=2714522​
Thanks go to:
@beaups - firewater
@Dees_Troy - TWRP
@Phil3759 - PhilZ Touch
@Fenny - Stock + ROM, Hacked HBOOT, Preload data & more
@Turge - ViperOneM8
@Chainfire - SuperSU
@jcase - for looking into getting weaksauce working on our phones
Click to expand...
Click to collapse
tks

tnez said:
thanks for writing this up!! got the dang Whelp message tho build date of 04/05/2014 if you want to add that to the list
Click to expand...
Click to collapse
Thanks for posting your results. OP updated with your build date.
abutran said:
tks
Click to expand...
Click to collapse
You're welcome. If you don't mind, please edit your post to remove the quote of the OP. It keeps the thread much shorter for people on mobile devices. Thanks.
Sent from my HTC One M8

uoY_redruM said:
Glad someone condensed everything down into an instructional guide. This should be stickied (if it's not already).
Thanks bro! :good::good:
Click to expand...
Click to collapse
Saw your post in the other thread and agreed with you! It was way too many pages to sift through.
Sent from my HTC One M8

Anyone good to go with a build date of 04/01/2014?

donciclon said:
Anyone good to go with a build date of 04/01/2014?
Click to expand...
Click to collapse
My build date is 04/01/2014 and I was able to achieve S-Off. If you try it, let us know the results. We haven't pinned down if the build date is the indicator. I'm hoping like hell it is though.
Sent from my HTC One M8

04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk

irrelephant said:
04/07/2014 build date no go... Got the whelp message as well.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.

Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day.
Click to expand...
Click to collapse
That's what I was thinking too. Multiple runs happen on any given day.
I was hoping it would be as simple as the build date. Of course we're not that lucky though. Lol. Whelp.... Back to the drawing board.
Sent from my HTC One M8

Behold_this said:
As I've said in the other thread it is the luck of the draw. Assembly date and location have little to do with it. It's a matter of what components were put into your device and that is a matter of what components were available at the time of assembly.
Just because one device was produced with exploitable components on one day doesn't mean another device wasn't produced with unexploitable components on the same day. A run of a particular component can run out at any time. When it does the next available run of components will be used.
Click to expand...
Click to collapse
Well what information might be of assistance and I will gladly provide it. I'm pretty good with adb, and willing.
Sent from my HTC One_M8 using Tapatalk