Develop Bugs

[GUIDE+FAQ] SLCD Desire bricked! Stuck with black screen.

HOW TO UN-BRICK A BRICKED DESIRE by
{
"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"
}
Elementary Frequently asked questions have been included at the latter part of this post..
If this thread helps you understand more about your device or solve your problems, don't forget to Rate and Vote for this thread. That will make sure that other people who face the same problems find it easily, without having to sift through hundreds of useless posts.
Caution! CREATING A GOLD CARD IS THE MOST IMPORTANT AND PRIMARY STEP TO DO BEFORE YOU ROOT OR UNROOT YOUR DEVICE, WHETHER IT IS BRANDED OR UNBRANDED.
IF YOU EVER WANT TO RETURN YOUR PHONE FOR WARRANTY, THIS IS ESSENTIAL, AND CAN GET YOU OUT OF MOST CASES OF SLCD BRICKS.
What was my problem (a.k.a What is an SLCD bricked Desire? a.k.a Why is there nothing on my Desire screen after running an RUU/flashing an incompatible ROM)?
I had an SLCD Desire. When I ran Alpharev on it, it did S-OFF. When I ran the RUU (which was incompatible for my SLCD, and actually meant for an AMOLED Desire), I effectively unrooted it, though not restoring it to the factory state (which is the function of an RUU). Because the version of RUU was incompatible with SLCD displays, I ended up with No Display on Screen (Black screen) and a phone without a working Recovery. The only way I know the phone's hardware is ok is because on pressing power button it vibrates.
Steps to try unbricking an SLCD bricked Desire:
Symptoms: Powering on the device just makes a vibration without anything on screen.
Previous History: You may or may not have done an S-OFF, then tried flashing an incompatible RUU for your device. You might have had an SLCD Desire, then flashed an RUU meant for an AMOLED Desire
If you had made a Goldcard earlier, you're in luck. You can restore your device with a generic SLCD RUU available for your device, by either running the RUU or by flashing the rom.zip from the RUU.exe file (Tip. This file gets extracted to %TEMP% folder when you run an RUU)
Things you need to know before you try solving your problem:
Know how to use adb from the command prompt. If you dont have adb or dont know how to use it, read this. (Courtesy: VanillaTbone )
Be familiar and identify the RUU for your device on shipped-roms site. [An RUU (ROM Upgrade utility) is an application released by the manufacturer to upgrade/install ROMs). Installing RUUs essentially unroots the phone and reverts it to stock (what you got when you bought the phone. An RUU is usually flashed and the rooting process reversed when you want to return your phone to service for warranty purpose]
How to create and use a goldcard. (Just download this tool (Credits and All Rights by [email protected]), and run it.)
How to navigate to the temporary folder of your Windows PC (Hint: In the run box, type %TEMP%
How to turn your device on into Recovery mode and Fastboot without seeing the screen (Please see below)
Understand the various options and sequences of keypresses required to perform an RUU update with a PB99IMG.zip, and the various options and sequences to enter the Android Bootloader, Hboot, Recovery menus (This complete guide can guide you through the process of performing a RUU, OTA update, and the various options of Hboot and Recovery without seeing anything on screen.)
Simple search on XDA can unravel more details about these simple mysteries.
Now, the steps to go about solving your problem: (All methods used to unbrick the Desire, essentially try to unroot it with an original manufacturer's version of files and revert to stock. In fact, the methods are same as the ones to Unroot your device. The only problem is that the issue is compounded because you cant see anything on your screen. Ironically, the problem of SLCD bricks happen when you try to unroot and the solution itself is to unroot it! )
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code (Customer ID) which prevents you from flashing a ROM meant for any other brand and also blocks a Generic WWE RUU. If you're from India, it is branded with HTC_038. If you're unbranded, things are looking much easier for you, as generic WWE RUUs for SLCD are easily available. Run the following code from the sdk folder to find out if your device is branded
Code:
fastboot oem gencheckpt
This displays the CustID Code as HTC__ (and a number). If these numbers are the same as included in the cidnum value in the file android-info.txt, your device is unbranded. I have noted the following cidnums are unbranded: HTC__001, HTC__E11, HTC__N34, HTC__203, HTC__102, HTC__K18, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__016, HTC__032. I'm not sure whether it is an exclusive list. To find out if an RUU is compatible for your ROM, the value displayed by fastboot oem gencheckpt has to be included in the cidnum list of the RUU. If it isnt included, you will need to use a goldcard to bypass the cidnum checks done by the RUU.
Check if you have made a goldcard (A goldcard is a normal microsd card modified to become special while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA or allow you to switch between software meant for different regions). The purpose of a goldcard is that when apparently incompatible ROMs are flashed with a goldcard inside the device, the flashing process skips certain checks like the Customer ID check (and hence no CID error). Note however that you cannot ordinarily install software of a lower version just because you have a goldcard. Note also that it is the software version which is important, and not the Bootloader version. Note that if you want to downgrade your software to a lower version, it is easiest to use Teppic74's utility (Link1 or Link2), and downgrade to his version of the RUU (1.21), then upgrade to your version of RUU. If your device is SLCD, always make sure the software you're about to flash does support an SLCD screen. As a general rule of thumb, flashing any version <2.0 may be dangerous. Teppic74 assures us that the version 1.21 his utility comes with, is compatible with SLCDs.
If you dont have a goldcard, you might try to create one at this point. (This may work only for some people. In fact I found that I could not get adb to interact with my device in Hboot/Recovery mode) Try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone might get detected (if the recovery is working) in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
After creating a goldcard (See the start of the post for how to do it) , it will allow you to run a generic SLCD RUU. Check this link for a latest RUU.
Note that you can flash an RUU in three ways. One is to just run it from Windows. . The Second is to run the RUU, and monitor your TEMP folder for changes. A directory starting with weird characters in its name appears while the RUU is run. Within that you may find a rom.zip file, which can be flashed onto your device with Fastboot.exe. The advantage is that in most bricked cases, even if the recovery wont run, Fastboot will.
If you dont have a goldcard, and adb doesnt show the device in Recovery mode, it means Recovery is corrupted too. In this case, check if the device can interact with adb in FastBoot mode. Power off device. Then Poweron by pressing Back key and Power on key. Again try adb devices command. If it shows the device, follow the steps of previous step. Some people ask you just power on the device and wait for 3-7 mins and then to check if the device interacts with adb. Note that if adb successfully displays the device serial code, you can successfully create a goldcard.
You can also create a goldcard by putting your microsd card into a friend's phone and following the steps needed to create a gold card, provided that your friend's phone was purchased in the same country. Note that you have to do this with YOUR goldcard. You cant have him create a goldcard, and use his CID. But you can have him mail his goldcard to you, again if you have the same brand of device from the same country.
If adb doesnt show your device in either Fastboot (previous step) or in Recovery, then you're in trouble. The only way to unbrick your softbricked device is to get a Generic RUU for your device (Check shipped roms site, or search XDA), and flash it. There is also a method if you have the original OTA zip for your device. Note that the generic ROM wont flash (without a gold card) if you have a branded device. Check teppic74's posts on XDA for this method.
For those, who have searched forum after forum for any solution, note the following:
IF YOU SOFT BRICKED AN SLCD BRANDED DESIRE WHICH HAD AN UPDATED VERSION OF HBOOT BY FLASHING AN INCOMPATIBLE RUU, AND IF THE DISPLAY WONT TURN ON NOW, YOU CANNOT RESTORE THE PHONE TO WORKING CONDITION UNLESS YOU HAVE A CORRECT RUU FOR THE UPDATED HBOOT, OR A GOLDCARD. Dont waste your time looking for more solutions online. You wont find them. There is a method for downgrading an updated HBoot to a lower version. I can't assure you that it works on a bricked Desire though.
AN INDIAN HTC DESIRE IS A BRANDED DEVICE. IT IS BRANDED AS HTC_038. IT IS ALSO AN SLCD DEVICE IN MOST CASES. So, before Rooting an Indian HTC Desire, keep a gold card ready.
Dont worry about Warranty being lost if it is a new phone. HTC has to repair it according to their Warranty policy.
FREQUENTLY ASKED QUESTIONS (FAQ)
1. What is an RUU?
RUU stands for ROM upgrade utility. These are officially released by HTC for upgrading ROMs. Many ROMs have been leaked over the years, and they have been hosted at Shipped-Roms. Running an RUU essentially reverts the ROM on your device to stock (what came on the phone when you bought it), unrooting it in the process.
2. Is running an RUU safe?
It depends. If your device is an SLCD, running anything less than version 2.x has the potential to brick your device unless it is specifically certified to work with your device.
3. What do I need to do before I run an RUU?
Decide that you definitely want to unroot your phone
Create a goldcard. Never mind whether you think your phone is unbranded. You never know. I did not know when I ran an RUU, that my phone was actually branded, though it wasn't locked to an operator. I ended up bricking this phone, but creating this thread.
Install the pc drivers for HTC Sync. But Exit from HTC Sync app or uninstall the app. Dont uninstall the HTC driver though.
Connect the device to pc. Put the goldcard in the device, and run the RUU.
4. How to Unroot your HTC Desire to stock.
This is a repetition of the above FAQ. Unrooting essentially involves running the RUU, either as .exe from PC, or as a PB99img.zip from phone.
I've dedicated a whole thread on How to Unroot your Desire Safely. Read about it here.
Whatever you do, DO NOT turn off the device manually unless the software tells you to. If something goes wrong, dont switch off phone. Keep the phone on while trying a solution. Newer RUUs dont usually wreck a phone, and with a goldcard, you can always recover. But, the flash SHOULD NOT be interrupted by switching off or disconnecting the cable.
Always start with a battery with >50% power (full recommended).
5. What is PB99IMG.zip? How do I use it?
It is the actual ROM in zip format.This is a part of the RUU. The RUU is an exe file, and when you run this file, it creates a folder in your Temp folder(Type %TEMP% in your Run Window, and press Enter). Delete all the files and folders in your Temp and then run the RUU. You will see two folders created when you run RUU. One of them (name starts with { curly brackets). Within that is another folder which contains many files, one of them is rom.zip. You need to put it in the root of your sdcard, and rename it to PB99IMG.zip. Then, when you start phone by Back Button + Power button (Fastboot), this file is automatically found by the device and prompts you to update ROM with this file. Note that you may need a gold card. Note also that in Windows, if you try renaming the file, it may get renamed to PB99IMG.zip.zip. Delete the extra trailing extension.
I've dedicated a whole thread on How to Unroot your Desire Safely with PB99IMG.zip. Read about it here.
6. Why do I need to create a goldcard?
When an RUU is run, there are many checkpoints which need to be passed before your ROM can be updated. One is the version check. Ordinarily, you cannot upgrade to a lower version. Another is the CID check (cidnum variable). CID is different for different regions. There are some regions which have unbranded devices (the WWE edition). Branded phones cannot be normally upgraded to a ROM meant for another region, including the unbranded WWE RUU.
Note that I've written normally
CID check and (But not the software version check ) can be bypassed by putting a goldcard in the phone while running the RUU or upgrading from the PB99IMG.zip. The software version check cannot be bypassed. You can downgrade however with Teppic74's utility, and then upgrade with the RUU of your choice.
6.1 What else do I need to know about a goldcard?
A goldcard is a modification of the sector bytes of the sdcard, replacing the initial bytes of its Sector 0 (Offsets [FONT=&quot]00000000 - 00000170 [/FONT]) with a certain code. Once a phone is booted into FastBoot, the device automatically checks the memory card for a few files. One of them is PB99IMG.zip in case of the Desire. This file is the upgrade utility/RUU in zip format. If this is found on th card, the system will automatically check the integrity of the file and prompt the user to upgrade his system ROM.
If the file PB99IMG.zip is presented in a Goldcard at the time of Fastboot, the upgrade will ignore CID checks (Ignores the region code locked on your device). Thus you can essentially debrand (flash software meant for another region) a phone with a goldcard and a PB99IMG.zip. The other way of course as I've already described is by simply running an RUU while the phone is booted/in Fastboot with a goldcard in. But I've had weird problems with RUUs. PB99IMG.zip method of unrooting can work even when battery is very low, does not need a connection to a pc at the time, and hence is a lot safer, since you wont brick your phone just because your power went off/computer crashed!
Note that Running an RUU=Flashing the PB99IMG.zip. They are the same thing, PB99IMG.zip is a zip file obtain by extracting the zip from an RUU exe file.
6.2 Can I use a Goldcard as my usual Sd-card?
You can, but it is better not to. A goldcard is your magic ring, a device to use if all else fails, an almost sure way of unbricking your phone. If you keep it in your phone all the time, you increase the chances of corruption. I advice you to keep your goldcard safe and secure someplace. Let's hope you don't need to use it, but if woe betide, you have to, then you can get your system back.
6.3 Is a goldcard destroyed when formatted or partitioned?
Definitely Not. Formatting does not write to the Sector 0 offsets used by a goldcard. Note however that defective partitioning or formatting can interfere with the ability of the Android system to "view" the files on the goldcard. The PB99IMG.zip may not work. But it can immediately be corrected by formatting the card to FAT32 and recreating the file.
6.4 Do I need to have the goldcard formatted by the phone?
Not really, though this has been recommended.
6.5 Can I use a goldcard from someone else?
Yes you may.
It is true that if someone else can read the CID of YOUR sd card (from his phone) and give it to you, with the CID code, you can make it a goldcard without a phone. Once you have a CID code, the other steps don't need a phone. Note that CID is unique to the card and not to the phone/region of the phone. You can have anyone anywhere read the CID code of his/card amd mail it to you. You can make it a goldcard without your phone. See also 6.6 below.
6.6 Can I create a Goldcard without a phone?
You can if you have Linux. You need a Laptop card reader slot and Linux. Once in Linux, navigate to a folder like /sys/block/mmcblk0/device/cid
I havent tested it out in a LiveCD. Check it out and tell me.
Programmers have tried writing applications to interface the sdcard in USB mode to get its CID number, but it needs a PCI slot or device-a phone-Either Android/Windows Mobile. A PC application may be specifically written for a PCI based card reader to read the CID, but such an application would be hardware specific for the particular brand of PCI card reader. You cant use it unless you are a programmer and know to do that. As far as I know there are currently no Windows programs that do that.
To clarify, Once again,
The only thing you need from your memory card to create a goldcard, is its unique CID number (which is inserted by the manufacturer of the card)
The CID is unique to a memory card. It is not specific to the device
You can get the CID of the sdcard from:
Any Android phone which can connect and use the adb command.
An Android phone with the GoldCard Helper market app.
A Linux operating system running on a Notebook with PCI slot which can read a memory card. Note: YOU CANNOT GET CID FROM LINUX FROM A USB CARD READER of a PC/Laptop. You need the PCI card slot.
You can even get the CID from a Garmin proprietory OS or a Windows mobile based phone. There are utilities available online using these, which can be seen in a Google search.
Do not try to get CID from any PC via USB cable. It can display a CID code but not the correct one. It is said that "USB lies about the CID".
6.7 I am not interested in Rooting/Debranding. Do I need to create a Goldcard?
No. Not until you you think of rooting it.
6.8 I have an unbranded device. Do I need a goldcard?
First, be 100% sure that yours is an unbranded device. Just because you bought it from HTC and because there is no branding does not mean you have an unbranded Desire. There may not be visible branding, but it may be branded with HTC.
In short, Create a goldcard whether you have a branded or unbranded Desire. You cant do harm by making a 1Gb (Any size greater than around 256 Mb) card a goldcard. But in case you inadvertently brick your system, a goldcard is the way you may get it back!
7. What if my device is not recognized in Recovery? (Cannot get adb in recovery)
It's a driver issue. You need to install a driver. First make sure that HTC Sync has been installed with all its drivers. Go to Computer, Rightclick and choose Properties>Device Manager. You can see an error code in one of the devices. Right Click it and choose Update Driver. Next, Choose, Choose from a list of Devices. Choose Android device. Windows gives a list of three drivers. Choose the one labelled adb interface. Windows says that the driver may not be compatible. Ignore and choose Ok. When you click Done, Unplug the usb cable and reconnect it. You can now get Adb in Recovery.
8. How to recover from an Alpharev Joker Loop (a.k.a How to Recover from a Corrupted Recovery/Boot)
I got a boot loop at the Alpharev Joker today while trying out Data2SD on my Desire. Basically, the Stock rooted Teppic rom was working fine for 15-20 reboots, then suddenly a lot of force closes happened. On rebooting, The Joker started to appear and disappear. In short, Boot was corrupted. I tried getting into Clockworkmod Recovery. It was corrupted too. I tried searching for an explanation. Got none.
The Solution:
Copied my Nandroid backup files (*.img) to Tools folder
Then,fastboot flash boot boot.img
fastboot reboot
It rebooted and got me into Android home, then promptly restarted..Which meant half the problem is over. Tried to get into recovery again, but Joker looped.
fastboot flash recovery recovery-clockwork-2.5.0.7-bravo.img
fastboot shutdown
fastboot reboot-bootloader
It worked! I got back my recovery
Alternately, try flashing either Clockworkmod or Amon-Ra recovery from Fastboot, and then install a Custom ROM
9. You said I can run PB99IMG.zip in Fastboot/Recovery by pressing a combination of keys, waiting for some time etc. What is actually happening?
When you press Vol- and Power, your device boots to Hboot and checks for certain system files in the root of your system, One of them is PB99IMG.zip, which is actually a part of the RUU which comes as a Windows executable file (exe). If PB99IMG.zip is found in the root of your sdcard, the system automatically checks it, and prompts you to use it to update your system. We know what the prompts are, and by asking you to wait for some time and press Vol, Power keys etc, we're walking you through the various prompts which you cannot see on your screen because the SLCD is bricked
10. My system was rooted and I then applied an OTA update. It's now giving me bootloops. What should I do?
Try the following:
Wipe the phone from Recovery menu.
Access recovery by pressing Vol- and Power button till system boots up.
Press Vol- to select Recovery, press Power button to choose recovery .
When the red triangle is shown, press Both Vol+ and Power button together.
Choose: Wipe data/factory reset, and then Choose: Reboot system.
If it still gives an error, you may need to apply an RUU.
FAQs Continued Here
(Newbies to the world of Android are encouraged to ask questions here. As you ask, I will update the FAQs )
DID THIS POST HELP YOU? If it did, you can show your appreciation by Voting (top right) for it to remain on the first page!

Is that the ROM that came on the phone as standard? You could try extracting the ROM.zip from the RUU, rename it PB99IMG.zip and try updating through HBOOT

FREQUENTLY ASKED QUESTIONS (FAQ) Continued..
11. How to unroot to my region's software if the only RUU available online is incompatible with my SLCD phone.
This is especially important for Indian Desire users. You can safely run any RUU>2.0 version. Below that, you need to confirm with those who have run it, whether its safe for SLCD. If you create a goldcard, though, you can get back to your manufacturer version of the software even after bricking it. Be careful here.
Method:
Get the OTA update for your region. Save it to pc as "update.zip"
Use an SLCD-unsupported RUU (supposing that only that version is available from your carrier). This will temporarily brick the phone.
Put the OTA as update.zip in the root folder of sdcard,
Use the key combinations for running the update.zip (without seeing anything on screen) from the Android recovery
The OTA restores system to an SLCD-compatible Froyo version.
It's a bit tricky, but workable for those who dont have the proper RUUs
12. What do I do if my phone does not get detected by Windows?
You could try uninstalling all HTC Drivers (uninstall+delete) from Programs & Features in Win, and the Device manager. Then reboot pc, dc from internet and connect the phone. Your phone should get connected, but you should be prompted for driver install. If instead of getting prompted, you find that the driver gets automatically installed, you should manually repeat the above process to remove the drivers. Restart once again.
Now install HTC Sync once again, uninstall HTC Sync program alone (keeping the drivers and driver installation in place). Now connect phone in Recovery and Fastboot. The right drivers should now get installed. Format the sdcard as FAT32, try the Downgrade tool once again. This process should take care of any driver issues.
13. What is a USB Brick and how do I fix it?
Read this post by Rudolfje. The fix is here
14. What is True Bricking and "Semi-Bricking"?
Note that the term "Semi-Bricking" is a neologism. I use it to refer to the state of a phone where you are unable to restore it to a usable state either because of flashing an incompatible rom for an slcd phone leading to the phone being unusable, and further you cannot flash an RUU because a gold card is unavailable and a CID-appropriate RUU is unavailable
A true bricking means you are not able to reset it even with an RUU. This happens because of flashing an Radio incompatible for the SPL (Second Program Loader). So, remember: Don't flash a radio until you understand fully the process of flashing and it is absolutely essential. If you flash a radio meant for another device, your device is Bricked! You cant fix it yourself!

Sounds like you've got an SLCD Desire and used an AMOLED RUU

EddyOS said:
Sounds like you've got an SLCD Desire and used an AMOLED RUU
Click to expand...
Click to collapse
I believe it's AMOLED..I was under the impression that the Desires released in India were AMOLED. And I used Unrevoked. Is it supposed to work on SLCD too? Is there a way to confirm this on the product specs? The tag says HTC Desire A8181. Model ID PB99200.
IT WAS AN SLCD DESIRE. Thanks, Eddy, for pointing that out!

The box says if its AMOLED, Desires built in the last few months are SLCD

This box doesnt. It just says "9.40cm touch sensitive screen". Nothing else.

Yea it sounds like you have a SLCD desire. It's not bricked you just can't see what your doing. Is there a RUU out for SLCD desires?
Sent from my HTC Desire using XDA App

ste1164 said:
Yea it sounds like you have a SLCD desire. It's not bricked you just can't see what your doing. Is there a RUU out for SLCD desires?
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Search brings up other similiar queries, but no files. So what would you suggest I do?

Only thing I could think was to flash san ruu that is SLCD compatible but that will debrand your phone.
Sent from my HTC Desire using XDA App

Thank you. That would be perfect. My phone isnt branded anyway! I cant find an SLCD RUU. Can you give me a link? I dont want to risk any incompatible RUUs after what happened!

Wouldnt I need a generic SLCD compatible RUU? Since my phone isnt branded, I dont need a goldcard, right?

Try this guide should work
http://forum.xda-developers.com/showthread.php?t=748498
Sent from my HTC Desire using XDA App

ste1164 said:
Try this guide should work
http://forum.xda-developers.com/showthread.php?t=748498
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thank you, ste1164. I had also reached that guide after searching. Unfortunately HTC has taken down the first file..The OTA. I'm downloading the second one from shipped ROMS..

Yea try and flash that ruu and see if it works for you.
Sent from my HTC Desire using XDA App

Seen as you can't see what your doing on your phone remember to do a battery pull then hold volume down and power to get into fastboot connect phone top computer and run the ruu.
Sent from my HTC Desire using XDA App

One quick qn, if I may..
I read that the SLCD backlight is off. In that case, shouldnt a Nandroid Restore, restore it to normal, if I can press the required keys in proper sequence without seeing?

Well you flashed the ruu so it unrooted the phone so a nandroid back up won't work.
Sent from my HTC Desire using XDA App

do you have a goldcard?

Rastaman-FB said:
do you have a goldcard?
Click to expand...
Click to collapse
No I don't. I dont have a branded phone either. I had almost created one, then saw in a forum that a goldcard wasnt needed unless one had a branded phone.
Edit: I had a branded phone. Just didnt know that. It was branded not to an operator, but to HTC itself
The RUU should still work without a goldcard, right? I'm still downloading it. The Broadband is down, and I'm using an old Nokia N95 to download the RUU..So it should still take an hour and half..
I hope I can flash the generic RUU without a goldcard. Otherwise I'm swamped! The other flash did run after I had pressed Vol Down and Power combo. It vibrated, and the USB driver popped up in Win..Trying to Flash got all the prompts..But finally gave me a 140 error. Will have to retry with this version. If this doesnt work, my phone is a goner. I saw just these two methods for a semi-bricked SLCD..The weird thing is that I realized just today that my phone was an SLCD (thanks to the response to this post). I always thought it was an AMOLED.

Idiot's guide to flashing the Xoom (for fun and profit)

This guide is for you that have a new Xoom (WiFi only, US model) with Android 3.1 and want to
- get root access
- enable the external SD card unit
Please note that Android 3.2, which now is available for the US Wifi models, make this guide more or less obsolete. If your aim is to have root access, then there are probably simpler methods.
What you need to do can be encompassed in these following short steps (will be detailed later on) in the following order. Each step is required before you can proceed to the next one. However, make sure that you are very very careful and dont try to take any shortcuts. That may soft-brick your device, and you may have a difficult time to explain that to your wife ... You have been warned!
I strongly recommend you to read the entire guide before trying this. In fact, read it twice to ensure that you have understood everything. If there is wierd stuff that you dont understand, dont hesitate to ask. The reason for me writing this down is that I like to document what I have learned. This is to me an excellent way to ensure that I will remember what I just did. Another reason was that I could not find a single thread that encompassed all steps required. There are many different threads, but noone (that I could find) that really guides you from start to goal. So enjoy and good luck!
I would like to thank LandMaster and cam30era for helping out with advice during my initial trail-and-error session. I soft-bricked my device once and had big problems to get by point 4.3 (avoid overwriting of CWM), but with their encouragement I finally succeeded.
If someone else adapts this guide for the EU model or the 3G model, feel free to drop me an IM and I will update the guide for these devices too. Until then, this has only been tested on a WiFi only, 32 GB device bought in the US. If you brick your 3G or EU bought model, dont call me ...
0. Overview of the 6 required steps
1. Install Motorola USB drivers for your computers (for USB connectivity)
2. Install Java SDK and Android SDK tools (for adb and fastboot commands)
3. Unlock the device for flashing (allowing replacement of recovery and boot images)
4. Install a modified recovery image (ClockWorkMod recovery for Android)
5. Root the device (Allow r/w access to the device filesystem)
6. Flash a kernel that supports the SD card (SD card access, overclocking etc.)​
Steps 1, 2, 4, 5 and 6 require that you download install, image and zip files needed for the flashing.
All this was performed on a Windows XP x86 SP3. Windows 7, Mac and Linux users will probably have to do some steps differently.
Update July 7: I have tested the procedure on Windows 7 x86 now and the procedure is identical to Windows XP.
1. Install the latest Motorola USB drivers
The installation file can be found here
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
1.1 Install the drivers and ensure that your Xoom is recognized by the computer
2. Installation of development software
Java SDK 6 and Android SDK (for Honeycomb at least) need to be installed. You can find the installation kits here.
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
http://developer.android.com/sdk/index.html
2.1 Install them as any other software.
2.2 What I had to do was to manually modify the PATH environment variable. I use Windows XP so I did that by right clicking on My Computer, choose Properties and select Advanced. Here I added the path to platform-tools and Tools
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\QuickTime\QTSystem\;D:\Java\Android-sdk\platform-tools;D:\Java\Android-sdk\tools
Note: If the Android SDK complains that the Java Dev Kit cant be found, just press Back and then Next again. Wierd, but that seems to do the trick ... go figure.
2.3 Test that ADB and FASTBOOT works. You should open a command window and go to your Android installation directory. Plug in your Xoom to your computer and write 'adb devices'. Your Xoom should now be listed like this
C:\Documents and Settings\Anders>adb devices
List of devices attached
0288414343813157 device​
Did your device not show up? Make sure that you have USB debugging enabled in Settings / Applications / Development
3. Unlocking the device for flashing
This step will effectively erase the internal storage, including all your apps and settings. Use whatever backup you want to rescure important data before you start.
3.1 Power up and start the Xoom
3.2 Ensure that your device is fully recognized by the computer. A good sign is that the 'Portable device' dialog is activated on Windows when your Xoom has booted. The Xoom should also be seen in 'My Computer'. If not, go back to step 2 and double check your USB drivers.
3.3 Use the command 'adb reboot bootloader' to go into Flash mode
3.4 Use the command 'fastboot oem unlock'. This will trigger a dialog on your Xoom. Follow the instructions on the screen to complete the unlocking. I repeat, this *will* do a factory reset and all data will be lost!
3.5 Once unlocked, the Xoom will restart and work as normal, but now ready for step 4
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
4.1 Boot into flash mode with 'adb reboot bootloader'
4.2 Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img​
4.3 Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo section 4.
4.4 Enter CWM with the following procedure
4.5 Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
4.6 When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. There are ways to prevent this (see posts below), but I recommend you to redo step 4 instead of messing with removal of system files. But both methods would probably work. Experiment!
5. Rooting the Xoom
The root zip file is located here
5.1 You need to transfer the ROOT zip file to a working micro SD card. You can do this on a computer or cell phone, but the ROOT zip must be located in the root directory of the SD card.
5.2 Insert the now prepared SD card in the Xoom
5.3 Boot into recovery (as described in 4.3). Navigate using the volume buttons and press the power button to select the active option
5.4 Select 'Install ZIP from sd card'
5.5 Select 'Choose ZIP'
5.6 Navigate to the ROOT zip file with the Volume buttons and select it with the Power button. Confirm that you want to install it.
5.7 Everything should indicate success, so back out to the main CWM menu and reboot the device.
5.8 From Android Market, install the ROM Manager app and start it. If the rooting was successful, then ROM Manager should start without any complaints.
6. Flashing a new kernel that supports SD cards (and maybe more ...)
The kernel that I used is described here http://forum.xda-developers.com/showthread.php?t=978013
The kernel zip file is located here
6.1 This step is identical to 5, but swap the ROOT zip towards the KERNEL zip. For simplicity, you may want to prepare the SD card with both zip files at the same time in step 5.1 ...

Looks great. You just might want to give credit to LandMaster and cam30era, too.

Also is this for just USA or all, cos many people brick there xoom if its just for USA only

okantomi said:
Looks great. You just might want to give credit to LandMaster and cam30era, too.
Click to expand...
Click to collapse
Of course, done

juDGEY2k10 said:
Also is this for just USA or all, cos many people brick there xoom if its just for USA only
Click to expand...
Click to collapse
This is only tested on a US device. OP updated.

Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".

I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.

BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
When you unlock your Xoom, it will wipe all user data.

bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
You're right. I rooted 1st and flashed CWR later. I then used brd's method to update to 3.1, re-root and flash the new bootloader and kernel. So there is a step missing after Step 3. I'm sorry, I don't remember exactly how to do this from HC 3.1. (meaning what files to use) as I was on HC 3.0 at the time.

BrokenPixel said:
Will this wipe all USER data?
Also, is the location of the zipped root file fine? the title says "[BOOT] Wifi-Only Charge Light Off".
Click to expand...
Click to collapse
Yes it will. Read 3.4 again, it will do factory reset.
The root file may vary from case to case, but the procedure is the same AFAIK. I used the one that "charge light off"... There are probably others too.

bwcorvus said:
I only see one problem, you have recovery before boot.img. If you flash the recovery, without a rooted boot.img and happen to boot into honeycomb, it will erase your recovery and load stock. So you can remove /system/etc/install-recovery.sh and /system/recovery-from-boot.p or flash the boot.img BEFORE rebooting out of recovery.
Click to expand...
Click to collapse
This is true, and I will update the OP to reflect that.

So has anyone followed this guide successfully yet? I don't really want to be the first...

yordikins said:
So has anyone followed this guide successfully yet? I don't really want to be the first...
Click to expand...
Click to collapse
Hi
I did!. And you know that someone gotta be first (actually second). Why not take the credit?

pingvinen said:
This is true, and I will update the OP to reflect that.
Click to expand...
Click to collapse
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App

Abracastabya said:
So I'm guessing the OP has been updated? I think I'm ready to dive in
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.

cam30era said:
Instructions are good to go. Just make sure that you don't reboot after flashing recovery, and before flashing boot image. If you do, by mistake, no harm done. You will just have to flash recovery again.
Click to expand...
Click to collapse
Sounds good and thanks B-)
Sent from my Xoom using XDA Premium App

Tnx . Very help full .

I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).

rmcsc said:
I don't know but ROM Manager just isn't budging showing any signs of root... or Superuser (+Elite)... or MarketEnabler...
I don't know, I'm kinda lost here. Let me retry (for the tenth time).
Click to expand...
Click to collapse
Try again, and remember that timing (3 seconds) are key to success ...

I'll retry being more precise. I do get into Recovery and I flash the file mentioned. It seems it flashes correctly but when I boot into the OS, there's no signs of root anywhere.
I'll update in a few. Thanks!
Sent from my T-Mobile G2 using Tapatalk

Regarding to rooting

hi All,
i new user of android os i was used and make lot of roms of Windows mobile. i m new with android i broth htc wildfire to online and they are send i think rooted phone becoz my hboot loader showing following
BUZZ PUT SHIP S-OFF
HBOOT-6.01.1002
MICROP-0622
RADIO-3.35.20.10
but when i install root checker software on mobile it find result this phone has not rooted properly.if it 's not then how to root this hboot version?
so i need help to flashing my phone with other custom rom.

First if all,wrong section.........use the Q and A section for questions
Second....your phone is just S-OFF(Security OFF),you will need to root your phone and install a custom recovery before you can flash roms

Firstly Welcome to our small(i feel its gettin' smaller everyday,nice to see new member :laugh: )community,but pay attention to this:
Wildfire Android Development-Threads for ROMs,MODs,PORTs,something that you made,something that you are developing and need some help,and some other things like guides for rooting etc.
Wildfire Q&A-Pretty self-explanatory,just questions and answers.
Your thread is for the Q&A section obviously,but on the question:
Your phone is S=OFF'ed ,which means unlocked bootloader. Now you should just install custom recovery (if it isnt installed yet, you should check it by getting into the bootloader and selectig recovery,use vol up&down + power button to select.)
For more information i suggest you to read the whole index thread:here.Everything is explained very well , just read carefully

csoulr666 said:
First if all,wrong section.........use the Q and A section for questions
Second....your phone is just S-OFF(Security OFF),you will need to root your phone and install a custom recovery before you can flash roms
Click to expand...
Click to collapse
sorry for wrong post but if i rooting my device so it will going to brick or dead ?
the members of this community was not given proper step by step instructions. android rooting i think lite hard. how many percentage to brick the device ? or is it safe?

Great, my phone is now S-OFF, meaning with a completely unlocked bootloader.
1] so i need to root it?
now i have to do this method first ?
◄●Instructions●►
Make sure you downloaded Unrevoked3 for your OS.
If you're on Windows, make sure you "uninstall HTC Sync or any other program that might talk to the phone over USB (doubletwist, etc). They will cause problems" (Unrevoked.com).
Plug your phone into your computer with USB.
Drag down from the notification bar on your phone and select "Charge Only" and "Remember this"
Make sure your phone has USB Debugging turned on by going to Menu>>Settings>>Applications>>Development and checking USB debugging.
Run the Reflash application that you downloaded.
Unrevoked will run its processes. Follow the few instructions it gives and thats it!
2] Then second is this?
Via PC49IMG.zip Process (Needs S-OFF) - Download anyone of the PC49IMG ZIP file of the recovery you wish to install, place on your SDcard, and reboot into HBoot Mode (Power Off, then Vol Down + Power Simultaneously). It will detect the file, and ask to install. Simply select Yes. If you wish to install another version which isn't present below, simply get the IMG file of the recovery version you wish to install,and replace in an existing ZIP. (Without Unzipping)
or 2] will first and 1] will second?

You need not use Unrevoked. Since your device is already S-OFF, you will just have to install a custom Recovery. There are 4 methods outlined in my guide here:
http://forum.xda-developers.com/showthread.php?t=1029318
How to Install a new Clockworkmod Recovery Image?
There are 4 basic ways:
1) Via Terminal Emulator (Needs S-OFF) - Guide Here. If you get an error "flash_image: Not Found", follow Steps 1-5 from Here, then, back to the original (first) link. Pushing of flash_image is a 1 time process. You need not repeat it everytime.
2) Via Fastboot (Needs AlphaRev / Revolutionary S-OFF or HTC DEV Unlocked Bootloader) - Guide Here. Refer the part called "To install Clockworkmod after Revolutionary"
3) Via PC49IMG.zip Process (Needs S-OFF) - Download anyone of the PC49IMG ZIP file of the recovery you wish to install, place on your SDcard, and reboot into HBoot Mode (Power Off, then Vol Down + Power Simultaneously). It will detect the file, and ask to install. Simply select Yes. If you wish to install another version which isn't present below, simply get the IMG file of the recovery version you wish to install,and replace in an existing ZIP. (Without Unzipping)
4) Via Unrevoked (No Pre-Requisites. Works on S-ON / S-OFF devices) - Guide Here
Click to expand...
Click to collapse
Personally, I go with the Fastboot technique since I feel its the easiest of them all. But you can also use the PC49IMG method if you don't have ready access to a PC.
Once CWM is installed, follow this guide to install Custom ROMS (Part 3 onwards)
http://forum.xda-developers.com/showthread.php?t=824396
Good Luck

3xeno said:
You need not use Unrevoked. Since your device is already S-OFF, you will just have to install a custom Recovery. There are 4 methods outlined in my guide here:
http://forum.xda-developers.com/showthread.php?t=1029318
[/B]Personally, I go with the Fastboot technique since I feel its the easiest of them all. But you can also use the PC49IMG method if you don't have ready access to a PC.
Once CWM is installed, follow this guide to install Custom ROMS (Part 3 onwards)
http://forum.xda-developers.com/showthread.php?t=824396
Good Luck
Click to expand...
Click to collapse
i success installed Custom Recoveries but when i run rommanegar /titanuimbakup like app it say you need to root your phone so i think i need to root my device supersu install via sdcard, is it ok?

Now you have to install su binary and superuser.apk(or supersu)

[Q] help me to get root my htc desire 820 dual sim..

Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........

subinoy.bose said:
Dear Sir,
I have followed all the steps but still not rooted my htc desire 820 dual sim
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064..............this link I have followed.....
but didn't sucess.......
plz....help...Sir
HTC Desire 820 can be easily rooted with few simple steps.
I am not responsible for your warranty loss or device not functioning properly.
Steps
1] Unlock Bootloader if you don't know how to do it visit this page
2] Download TWRP Recovery from here
3] Download Super Su from Here and transfer it to your device
4] Reboot to Fastbboot mode using Volume Down and Power Key
5] Connect Phone to PC
6] Extract files from Recovery.zip in one location and simply click on flash-recovery.bat
7] After Step 6 is finished Using volume keys navigate and select recovery option and go to recovery
8] After rebooting in recovery select Install zip > and selecting supersu.zip transferred in first step to obtain root access.
9] Reboot
Very much urgent.......plz. reply...........
Click to expand...
Click to collapse
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843

Please let us know what is the exact message your getting are you not able to get to Recovery ???
I have been able to successfully root my device by following the steps outlined did not face any challenges hence wanted to check.

Same Probleam here pls help me
I AM SUFFERING FROM SAME PROBLEAM.
i am using desire 820q.
bootloader unlocked.
but when i enter in recovery then that says entering recovery then come back.
pls help me...

problem with htc 820q root
mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?

tah3r said:
I'm following this instruction and could not root my device,
My HTC 820q is unlock but when I want read SuperU.zip from Sd card at fastboot>recovery my mobile goes to restart and procedures been uncompleted.
Please help me, is this instruction only for HTC 820?
How we can root HTC 820q?
Click to expand...
Click to collapse
http://forum.xda-developers.com/desire-820/general/htc-desire-820-root-easily-t2913064

mukulatri said:
Try thishttp://forum.xda-developers.com/attachment.php?attachmentid=2784451&d=1402084843
Click to expand...
Click to collapse
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message

尚雷諾 said:
Well I have the same issue, recovery looks installed after pressing power button to launch it goes to a screen and go back almost instantly on fastboot screen. I also tried last version of framaroot, does not help either... just get a failed message
Click to expand...
Click to collapse
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.

T0ark said:
Hi there, let's go step by step without "shortcuts" that are typically working on PC/WIn.
1. Unlock bootloader of your phone at HTCdev[dot]com [replace 'dot' with . - sorry for confusion I haven't earned reputation to post external links yet]. All necessary tools (fastboot) will be provided to download during process as well as necessary instructions. You need Windows/Linux or OS X computer to complete this step.
2. Download custom recovery .img file and save it to same directory you have fastboot files (e.g. from step 1) on you computer
3. Start phone in fastboot mode (mind fast boot option in Power settings must be unchecked if you using VolDown [-] start option (not necessary if you use adb reboot bootloader). Battery must be charged over 10% (I suggest 30% to stay secure); connect to computer (phone shall display Fastboot USB)
4. Navigate command/terminal window on your computer to location of recovery image file from step 2 (fastboot files must be there or have a correct path specified).
5. On computer terminal window run command: fastboot flash recovery filename_of_recovery.img . Red section must be exact custom recovery file name.
6. You'll get some communication in terminal. If completed OK will be among them, if failure, there will be FAIL with description of reason (e.g. low_power). If only "waitng for device" dislays, check connection with phone.
7. Navigate phone to HBOOT, then select recovery. If recovery don't start, check step 1 and restart from step 3. If only icon with red ! appears, it means you have stock recovery installed. Please verify from step 1.
8. Once custom recovery is installed and working, use it to flash SuperSU or any other superuser app (must be flashable .zip to be applied). Install just 1 root application, to avoid problems. At this point, you may consider flashing busybox also if you plan extensive file modification, but it's not necessary for root. For any sake, clear cache befor restart.
9. Restart the phone - you shall view SuperSU application or any other superuses app you've flashed i step 8.
Hope now works.
Click to expand...
Click to collapse
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...

尚雷諾 said:
Thanks for your answer, I have to say I properly unlocked the phone so I do not think there is a way I messed up with this step as when I start bootloader it clearly shows on the top of the screen ''UNLOCKED".
When I flashed recovery on my phone I had no errors prompted or any message of failure. The process went well until a success notification.
Now when I start my phone into bootloader I repeat, I clearly see that recovery has been installed but when I attempt to start it then I'll be almost instantly brought back to the bootloader screen... now I started to wonder if... if an update of android could cause this kind of issue? The point is my phone is using android 4.4.4 and not the factory version 4.4.2. I remember having updated my android version which was perhaps a mistake as this phone is not very old and I was planning to root it in the next days... Now I'm not expert just try to figure it out.
I tried different system to auto root via different apps, some using the PC some using directly the phone, I never get any success...
Click to expand...
Click to collapse
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...

T0ark said:
Ok, please try twrp from Original Android Development tread (it works for me, mind, I'd question it's stability) or Philz recovery (sorry, I found only Chinese, but it's for verivication only: h...ps://drive.google.com/file/d/0BygOvRquk4z8S05kRC1XMXdSbXM/view?usp=sharing - please adjust tt in address - rookie rules).
I'd suggest test running from Fastboot: fastboot boot custom_recovery.img - replace with actual file name from directory you're running terminal.
This shall verify if it's problem with recovery file or any remaining protection...
Click to expand...
Click to collapse
Does having S-ON bother? I was also wondering about that but all tutorials I found no one mentions anything about the S-ON or S-OFF thing.
But I do have a S-ON under UNLOCKED

what is stock recovery.img name
i dont know what is the real stock recovery.img name.

htc desire 820q dualsim
I can't root my htc desire 820q by this method, is any alternative way?

I just root my phone with same procedure but my phone still show s-on..... How can i s-off my phone.....

HTC One m9 - Stock 2.10.401.1 is here!

Getting the 2.10.401.1 step by step, crystal clean instructions.
This guide is mostly for the people who are stuck on lower versions where "About" says that there are no updates and that their device is up to date. Especially users who previously did 1.32.401.17 RUU. This version is know to have some major flaws and it tends not to read any updates, accept auto and manual OTAs nor zipped RUUs.
- Alright so I saw good number of people being stuck on European 1.32.401.17, 1.32.401.15 and 1.32.401.8 and unable to grab auto OTA and unable to manual OTA install due to various errors being thrown in twrp. There are also users who are having issues with SD transfers, transfers from PC to to phone especially when they transfer zipped RUU (0PJAIMG). Do not worry, I am going to help you with this. Just follow my simple steps. Note that you can forget about custom recoveries, microsds, system dumps, zipped ruus that "wont copy" to your device and others. You won't need any of these in my procedure. Simply ignore them. Now focus on my steps.
Step 1; Download the 1.32.401.17 exe RUU from here; DO NOT RUN THIS YET.
Step 2; Download the 1.40.401.8 0PJAIMG (ZIPPED RUU). Do not open/modify this yet.
Step 3; Backup your data on the phone such as contacts, SMS and so on. I personally use Wondershare mobilego for those things.
Step 4; Navigate to temp folder by typing %temp% in the search bar or C:\Users\Username\AppData\Local\Temp\ >>
Step 5; Under that folder you may or may not delete the files you don't need for easier navigation. Now this part is very important. Focus on that folder.
Step 6; Go back to 1.32.401.17 exe you downloaded in the step 1. Right click on it and Run it as admin. Once ran, it might take several minutes to open actual installer. Let it load all they where you see next/cancel. Stay there and do not cancel it or hit next.
Step 7; Go in your temp folder under step 4. You will see two newly created folders. You only need this one. Under that folder you should see another one with few random files. Go into other subfolder and navigate to the file named rom.zip. Delete this folder.
Step 8; Now go back to the file you downloded in step 2. Name that file to rom.zip and place it where you previously deleted the zip file from temp subfolder.
Step 9; Go back to the RUU installer interface and press next and do the procedure like you did with version x.17. You should see this. Now let the RUU installer updates your phone.
Step 10; Go under Settings > About > Updates. Now if you did all right you should see the magic: http://i.imgur.com/aqR4YwD.png >> Grab this new 100% fresh and stock OTA update and enjoy.
- I tested this few times on several devices and it works for every one of them. I am not aware of the other carrier users are having issues but same procedure can be done. Do not install custom recovery or root your device before you updated your device to 2.10. If in any case updater wont pick the 2.10 update you can flash your recovery and firmware from 1.40.401.8 version (prior to the 2.10 update). Do not panic if update is taking a while, it will reboot your device few times and thats it. To be on more safe side you can always flash the firmware once device is properly updated to 2.10.
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola

Nikolay82 said:
*Flashing the firmware to 2.10*
Download from here and put it where your ADB interface is;
Put your device to download mode and open up the cmd where adb interface and latest firmware is.
do the following commands:
a.) fastboot oem rebootRUU
b.) fastboot flash zip firmware.zip
c.) fastboot reboot
- Make sure the phone is not rooted or tampered with. If something is not clear feel free to ask. I hope this helped to you.
Nikola
Click to expand...
Click to collapse
S-ON Users should not try to do this if they weren't able to get and install the 2.XX.XXX.X uptdate before they get to this step. The firmware pack does not update the rom and it can only be flashed on S-ON devices if the bootloader is locked or relocked. HTC introduced a new "security feature" with the 2.XX.XXX.X firmware. This "feature" blocks the Bootloader Unlock if the option "OEM unlocking" in the Developer Options isn't activated. Without an up to date rom you won't be able to activate this option because it does not exist in earlier versions. Since there are no international 2.XX.XXX.X RUUs S-ON Users who follow this part of the guide and did not install the OTA beforehand would then be stuck with the 2.XX.XXX.X firmware and a 1.XX.XXX.X rom.
Except for that missing warning it's a very nice written guide.

I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on. That part is probably not something many people will need, but its there just to be on safe side. The RUU itself will throw an error if there is a CID conflict anyway. Personally, I am not a fan of tampering with CID unless it is a must. User should be able to find proper RUU/OTA to match their CID.
I am working with the phones and I often have people who likes to tamper with their device. Good number of them will even write different CID, or even "universal" one just so they can go through RUU process and update. However, later they stuck on "no mobile data" unable to fix things. 99.9% of them failed to update their current model to latest so they resort to changing CID and putting in different country ROM just because it is newer. As for HTC introducing new security feature I wont go much into detail about it because it falls under hacking and reverse engineering in order to benefit from said action. Let's just say they never got around some crucial elements which pretty much made their security feature vain. Apple claimed similar thing. One day I sat down and put in the windows OS just because "tiles" were trend back then. I am yet to see a safe and totally secure update. Apple was the closest with their icloud and findmyphone but I decided for droid mostly because i wanted more freedom for what I pay. Cheers.

Nikolay82 said:
I've tested this on S-ON device. I've successfully flashed 2.x for the sake of testing, both s-off and s-on.
Click to expand...
Click to collapse
I never said that you won't be able to flash the firmware with S-ON. And please don't get me wrong. Your guide is very good.
The problem is that there is a special kind of xda readers which tends to skip some of the important steps that are described in instructions. If those people flash the firmware without installing the OTA beforehand they will be stuck with an unlockable, (re-)locked bootloader and a 1.XX.XXX.X rom on a 2.XX.XXX.X firmware. There are already plenty of threads which describe similair scenarios here on xda. That's the reason for the warning in my last post.