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="]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.
Related
Hi guys,
I'm in trouble, I'm a little confused, I cannot use my desire anymore.
I just would like to know how to recognize if my desire is SLCD or AMOLED before to do anything else.
BRAVO PVT3 SHIP S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-4.08.00.09
Original Image: 1.24.161.3 with 32.41.00.32U radio
How can I know that??
Secondly I would like someone can confirm me the meaning of branded or unbranded: am I right if I say that my mobile is unbranded if I can use it with different operator SIM?
I'm I right if I say that I don't need any gold card if my mobile is unbranded?
thanks a lot for confirming me this steps, after that I can take the right way to recovery it!
Regards
Miniera77
Hboot 0.82 indicates that it is a SCLD
As for question 2 here goes (no offence meant to anyone but I will be a bit blunt)
The terms branded and debranded are not often used on android forums, at least by people with knowledge. it is usually used on mainly non-smartphones to denote removing of carrier specific firmware and changing it to default or stock firmware.
Now on here I have seen it used in many different ways
- to root
- to root and flash a stock rom
- to just remove carrier crap, but not root
Its best to just avoid that terminology altogether. It has nothing to do with being able to use another sim card, that is "sim lock" and you will need to get your phone "sim unlocked" in order to use it on a different network.
Edit: as far as I can remember you should just be able to use the one click root method without any need for a goldcard.
Lennyuk said:
Hboot 0.82 indicates that it is a SCLD
As for question 2 here goes (no offence meant to anyone but I will be a bit blunt)
The terms branded and debranded are not often used on android forums, at least by people with knowledge. it is usually used on mainly non-smartphones to denote removing of carrier specific firmware and changing it to default or stock firmware.
Now on here I have seen it used in many different ways
- to root
- to root and flash a stock rom
- to just remove carrier crap, but not root
Its best to just avoid that terminology altogether. It has nothing to do with being able to use another sim card, that is "sim lock" and you will need to get your phone "sim unlocked" in order to use it on a different network.
Edit: as far as I can remember you should just be able to use the one click root method without any need for a goldcard.
Click to expand...
Click to collapse
Hi Lenny,
thanks for your answer.
The point now is that I cannot use one click root method because I cannot switch on my mobile system. I can only switch it on in fastboot way.
Can you please suggest me a way to flash my rom in that mode?
Thanks
regards
Miniera77
edit:
if I try unrevoked 3.1 with a custom recovery image (recovery-clockwork-2.5.0.1-bravo-slcd) I get this error:
Device "/sbin/sh: getprop: not found
"is not supported at this time.
Miniera77 said:
Hi Lenny,
thanks for your answer.
The point now is that I cannot use one click root method because I cannot switch on my mobile system. I can only switch it on in fastboot way.
Can you please suggest me a way to flash my rom in that mode?
Thanks
regards
Miniera77
edit:
if I try unrevoked 3.1 with a custom recovery image (recovery-clockwork-2.5.0.1-bravo-slcd) I get this error:
Device "/sbin/sh: getprop: not found
"is not supported at this time.
Click to expand...
Click to collapse
ok, what happened to cause your phone to stop booting then?
Does the screen work for the HBOOT menu (volume down and power on)
yes I can boot my phone only by pressing volume down and power button I cannot enter to recovery menu the screen became black, I tried to follow the procedure http://forum.xda-developers.com/showthread.php?t=748498 method 2 without success and method 1 many times but nothing happen, always black screen.
thanks for help me and sorry for my english.
edit:
what I did:
I rooted my phone with unrevoked but with the default recovery image so I coudn't see Recovery menu anymore, than I've download Rom Manager and I said reboot in recovery mode after I put update.zip file in my SD. Thats'all! Tried to change update.zip but always black screen.
try this guide
http://rootmydroid.co.uk/category/guides/desire/
Sorry lenny,
I cannot switch on my phone and set parameters:
2.With your Desire go to Settings > Connect to PC > Default connection type > Disk drive then Untick ‘Ask Me’
3.Then go to Settings > Applications > Development > Make sure USB Debugging is ticked.
4.Then go back to Applications and make sure Unknown Sources is ticked.
so the unrevoked tool doesn't work.
Miniera77 said:
Sorry lenny,
I cannot switch on my phone and set parameters:
2.With your Desire go to Settings > Connect to PC > Default connection type > Disk drive then Untick ‘Ask Me’
3.Then go to Settings > Applications > Development > Make sure USB Debugging is ticked.
4.Then go back to Applications and make sure Unknown Sources is ticked.
so the unrevoked tool doesn't work.
Click to expand...
Click to collapse
ah yeah forgot about that, ok thinking hat time.
Lennyuk said:
ah yeah forgot about that, ok thinking hat time.
Click to expand...
Click to collapse
thx! Hope to recovery my phone soon!
edit:
I've tried to use adb tools from windows, I can see the phone and use commands by command line. Tried with AM Recovery Application but it doesn't go on.
Ok
1) where did you get the phone from, was it brand new?
2) has it ever worked?
3) have you flashed or changed anything since getting it?
You may have to get a rom.zip from a SLCD comaptible ruu (might be in top thread of dev section)
rename it to pb99.img
put it on your sd card
boot into hboot
it should ask you to flash
that should fix it.
BUT ONLY DO THIS IF YOU HAVE NEVER FLASHED A NEW HBOOT AND REALLY DO HAVE AN SCLD SCREEN
(thanks 42Turkeys)
well:
1) just bought 2 days ago I'm in switzerland,
2-3) sure it was working before I've tried to flash it with Rom Manager. I've rooted it succesfully because I could use applications like titanium backup and Rom Manager... but with the wrong recovery image (you said my phone should be SLCD, I used the default recovery image in unrevoked)
Miniera77 said:
well:
1) just bought 2 days ago I'm in switzerland,
2-3) sure it was working before I've tried to flash it with Rom Manager. I've rooted it succesfully because I could use applications like titanium backup and Rom Manager... but with the wrong recovery image (you said my phone should be SLCD, I used the default recovery image in unrevoked)
Click to expand...
Click to collapse
There is a chance you used an old unrevoked that flashed a non-SLCD version of clockwork.
You need to do what I posted above to fix.
Lennyuk said:
You may have to get a rom.zip from a SLCD comaptible ruu (might be in top thread of dev section)
rename it to pb99.img
put it on your sd card
boot into hboot
it should ask you to flash
that should fix it.
BUT ONLY DO THIS IF YOU HAVE NEVER FLASHED A NEW HBOOT AND REALLY DO HAVE AN SCLD SCREEN
(thanks 42Turkeys)
Click to expand...
Click to collapse
Lenny on my SD card I have a folder \clockworkmod\backup and there is my original backup I've done before to do any operation.
there are 3 files:
- boot.img
- recovery.img
- system.img
should I be able to use that? In witch way?
thanks!
Miniera77 said:
Lenny on my SD card I have a folder \clockworkmod\backup and there is my original backup I've done before to do any operation.
there are 3 files:
- boot.img
- recovery.img
- system.img
should I be able to use that? In witch way?
thanks!
Click to expand...
Click to collapse
no, they are part of a nandroid
You want the rom.zip file from an RUU
Lennyuk said:
no, they are part of a nandroid
You want the rom.zip file from an RUU
Click to expand...
Click to collapse
can you please suggest me the right one?? I wouldn't get my situation worse.
thx
http://forum.xda-developers.com/showthread.php?t=695667
This is a link to all known RUU's
You will just need to try to find the one that came with your phone originally.
Lennyuk said:
http://forum.xda-developers.com/showthread.php?t=695667
This is a link to all known RUU's
You will just need to try to find the one that came with your phone originally.
Click to expand...
Click to collapse
Sorry lenny,
should I choose one of this:
OTA_Bravo_HTC_WWE_1.21.405.2-1.15.405.4_release_P4ohim1mtp6zggcyon.zip
OTA_Bravo_Vodafone_UK_1.19.161.5_1.15.161.4_releas e_P2q1fwy34gicxsiqaq.zip
OTA_Bravo_TMO_UK_1.15.110.11-1.15.110.10_releasez3xlhzglzlds8gg2.zip
OTA_Bravo_TMO_UK_1.21.110.4-1.15.110.11_release0grz58nlwns0d5mw.zip
OTA_Brav2_DE_1.20.207.3-1.17.207.3_releasez9b8rc8nxxq8cosz.zip
even if my original one is 1.24.161.3 and is not there.
than you said to rename the zip files with pb99.img (is that the right file name?)
put it into the SD root and switch on the phone in hboot
that's right?
thx
Miniera77 said:
Sorry lenny,
should I choose one of this:
OTA_Bravo_HTC_WWE_1.21.405.2-1.15.405.4_release_P4ohim1mtp6zggcyon.zip
OTA_Bravo_Vodafone_UK_1.19.161.5_1.15.161.4_releas e_P2q1fwy34gicxsiqaq.zip
OTA_Bravo_TMO_UK_1.15.110.11-1.15.110.10_releasez3xlhzglzlds8gg2.zip
OTA_Bravo_TMO_UK_1.21.110.4-1.15.110.11_release0grz58nlwns0d5mw.zip
OTA_Brav2_DE_1.20.207.3-1.17.207.3_releasez9b8rc8nxxq8cosz.zip
even if my original one is 1.24.161.3 and is not there.
than you said to rename the zip files with pb99.img (is that the right file name?)
put it into the SD root and switch on the phone in hboot
that's right?
thx
Click to expand...
Click to collapse
yes you need to open the ruu up, find the folder rom.zip and rename it to what you just said.
Lennyuk said:
yes you need to open the ruu up, find the folder rom.zip and rename it to what you just said.
Click to expand...
Click to collapse
found firmware.zip on
extracting OTA_Bravo_HTC_WWE_1.21.405.2-1.15.405.4_release_P4ohim1mtp6zggcyon
rename it in PB99.img or PB99IMG.img??
The HTC DESIRE Z
ROOT / S-OFF / FLASHING / DEBRANDING
EASY TUTORIAL and FREQUENTLY ASKED QUESTIONS
INTRODUCTION
- Before anything, please scroll down to post 2 to read the ROOT | FLASHING | BASICS | FREQUENTLY ASKED QUESTIONS
You will graduate with an Android flashing degree in 9 minutes guaranteed
Then you can come back here and proceed reading the rooting / debranding / flashing guides.
- This guide/tutorial is a LEARNING and RESOURCES centre written in plain english for the average user.
- Don't be shy: please feel free to ask any questions, but don't be dumb: READ first before asking !!
HOW TO ROOT and S-OFF
- For rooting questions, please refer to the proper thread (rooting methods).
- Rooting an HTC Vision is a pain in the arse because there are many variants/versions, and not all rooting methods can be used on all of them.
- There are many ways to get root access: "rage" (ADB command line type) "visionary" (an APK installable app by paulobrien from Modaco) "gfree", etc. Using "Rage" is safer, "visionary" is simpler but many problemshave been reported, and "gfree" safer and most up to date.
- After using any of these, you can go further and turn S-OFF, CID-unlock and SIM-unlock the phone with "gfree", a safe and neat script written by scotty2 et al @ #G2root IRC. Sounds confusing ?? Just follow the instructions on the Wiki.
- TO ROOT, FOLLOW THE STEPS IN THE WIKI
VISION WIKI: ROOTING
- To check if your phone can be rooted you can check this neat thread:
[GUIDE] Root AND Downgrade ANY Desire Z or G2
Thanks to Aegishua
- Before "gfree" was available, transitory ("fake") S-OFF was achieved by flashing an engineering hBoot, but it is not safe and not recommended for newbies.
- As for reference, qpop made a neat a simple guide to get root S-OFF and CID unlock with visionary and gfree. It works a treat with Bell-NAM phones, but visionary sometimes doesn't work for some Asia/Voda versions.
The thread is located here: http://forum.xda-developers.com/showthread.php?t=857390, download the "UberRoot" package from the post footer, and follow qpop's guide.
(thanks scotty2 for your hard work and qpop for the guide !!)
- fattire has another neat and clear guide/tutorial for using gfree version 2, the thread is located here: [Guide] Subsidy Unlock, SuperCID, and Radio S-OFF
- UPDATE July 2011:
The MOST RECENT rooting guide/method dated 30 JUN 2011 from aegishua here:
http://forum.xda-developers.com/showthread.php?t=1055581
- More instructions and several methods to root in the WIKI:
WIKI - Rooting the HTC Vision,
and HTC Vision Permanent Root,
- NOTE: You will need an ADB shell to run gfree and for other stuff. Please read the FAQ if you don't know what this is. If you don't have an ADB shell already set up and running, download the ADB drivers and the Mini ADB from this post's footer or download the full Android SDK (which includes ADB) and the HTC Sync software (to install the USB drivers on your PC).
- The older rooting guide and the older (and not so safe) "hBoot" way to ("fake") S-OFF have been moved to post 3 for reference purposes only. Plese scroll down to post 3 should you want to read the older guides.
HOW TO DEBRAND
"Debranding" means replacing an original operator-customized frimware (Bell, Vodafone, etc) for the generic, stock HTC Sense firmware.
METHOD 1: Unlocking CID security
You can use this method if you don't have a Goldcard.
- Make sure your phone's battery is charged at least 50%.
- Make sure your PC has the phone's USB drivers installed.
If not, download the HTC USB Driver (for Windows) from this post footer or you can also get them installed by downloading the "HTC Sync" software. After installing the drivers, connect your phone to the PC with the USB cable at least once and the USB drivers will be installed to your PC.
- Your phone must be fully S-OFF and CID-unlocked with scotty2's "gfree" script.
- Download the World Generic HTC shipped official ROM (firmware) with its flashing utility (RUU) from this thread:
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
(thanks football for sharing !!).
- From your PC, run the RUU, follow the on-screen instructions, and let it finish the process.
METHOD 2: Using a Goldcard
You can use this method if you don't want to S-OFF/CID unlock your phone.
- Make sure your phone's battery is charged at least 50%.
- Make sure your PC has the phone's USB drivers installed.
If not, download the HTC USB Driver (for Windows) from this post footer or you can also get them installed by downloading the "HTC Sync" software. After installing the drivers, connect your phone to the PC with the USB cable at least once and the USB drivers will be installed to your PC.
- You need to put a Goldcard SD card inside your phone during the flashing process, otherwise you'll get an "Incorrect Version" Error when flashing. Scroll down to "Resources Centre" to find out how to easily create a Goldcard in a couple of minutes.
- Download the World Generic HTC shipped official ROM (firmware) with its flashing utility (RUU) from this thread:
[ROM] RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M
(thanks football for sharing !!).
- From your PC, run the RUU, follow the on-screen instructions, and let it finish the process.
RESOURCES CENTRE
HOW TO CREATE A GOLDCARD
- To easily create a Goldcard in a couple of minutes without ADB skills or commands, check this thread.
TIP: After reading post 1 and downloading the automated software, be sure to read post 5 there for a neat guide.
- To manually create a Goldcard (requres ADB skills) check this thread.
(thanks Apache14 !!)
TIP: Put the SD card you want to convert to "Goldcard" into your phone, connect your phone to the PC, select "Disk Drive" in your phone, and follow only the step 2 of that post. The other steps mentioned there are not required to create a Goldcard to debrand/downgrade.
EXTRACTED OFFICIAL ROMS AND OTHER UTILITIES
- Here's the World/Euro generic 1.34.405.5 rom.zip (aka "PC10IMG.zip"), extracted from the official RUU [megaupload].
BEWARE: This is a signed officila image, it should be flashed only to a phone originaly shipped with this firmware, or to a CID unlocked phone.
WHAT TO DO IF SOMETHING GOES WRONG
- If something goes wrong, eg. you erroneously flashed a T-Mobile official image and now your phone is looping at boot or seems "bricked", you can check fastludeh22's thread: How to recover my semi-brick
or his other thread about flashing a wrong image
(thanks fastludeh22 !!)
HTC ADB DRIVERS FOR WINDOWS VISTA/7, 32/64 bits
- Attached to post footer is a package with the ADB HTC USB drivers for Windows Vista / Windows 7 PCs
- These drivers are required for ADB
- Just in case you don't want to download and install the full "HTC Sync" software
ADB MINI PACKAGE
- Attached to post footer is a package with a basic, mini ADB SHELL for Windows Vista / Windows 7 PCs
- Just in case you don't want to download the full "Android SDK" software
- The ADB USB phone drivers are required
- There's a good ADB learning guide here: ADB for noobs
(thanks steviewevie !!)
---
- Also, and for reference only, the older Visionary R12 app is attached to this post footer
ROOT - ROOTING the HTC DESIRE Z:
FREQUENTLY ASKED QUESTIONS
1.- What is "root" ??
"Root" is the user account in Linux with all priviledges: The "root user" can edit anything on the system. For safety reasons, users do not have all those priviledges out of the box.
Remember: Android is Linux based. When you "root" your phone you gain write/read-access to areas of the phone you couldn't previously access.
Rooting the phone is optional of course.
2.- Why should I "root" my phone ??
Mostly, rooting is useful only for developers, unless you want to run a root-requiring app/mod or you want to flash your phone.
When you root your phone you are allowed to:
a) Run more linux (Android ADB) commands and use Superuser priviledges.
b) Use many apps that require root priviledges (Titanium Backup, Root Explorer, etc).
c) Change important system settings. In our case, rooting lets us turn off the ROM security in order to flash other firmwares and run some interesting tweaks like overclocking and installing hardcore recovery apps.
3.- Is "rooting" safe ??
Yes, if you read carefuly and follow the instructions nothing will happen.
4.- Will "rooting" erase all my info ??
No, it's just a change on system permissions.
5.- Will "rooting" void my warranty ??
Hmmm... good question, anyway you can always go back and un-root to pretend nothing ever happened
6.- After I have rooted my phone, can I uninstall the VISIONary tool ??
Yes.
Be aware that removing the VISIONary tool will NOT remove root ("un-root" your phone), it will only remove the rooting tool, obviously.
7.- Will I loose "root" if I uninstall (remove) the VISIONary app ??
No.
Paul's VISIONary app is just a rooing tool, root changes will stay.
8.- Is the process reversible ??
Yes it is.
9.- How do I "un-root" my phone (remove root) ??
Should you need to do so, just open VISIONary again, and tap "Unroot Now!"
10.- Can I flash a different ROM after I "root" my phone ??
No. To flash a non-official ROM (custom or unsigned) you need S-OFF. To flash an official (but not your orginal) firmware you need CID unlock.
Piece of cake, ain't ??
FLASHING the HTC DESIRE Z:
FREQUENTLY ASKED QUESTIONS
1.- What is a "ROM" ??
"ROM" is "Read Only Memory". It refers to the phone's non-accessible, read-only internal memory. It contains the Android Operating System and all the original software that runs your phone.
Usually a FULL ROM (aka "firmware") consist of: a Recovery image, a Boot image (which contains the Kernel and the ramdisk), a System image (the operating system or "OS"), and a Radio image.
Frequently, we use the term "ROM" losely: we refer to a "ROM" or "firmware" as an image that can be flashed to that inetrnal memory.
There are "official" ROMs from HTC, and "custom" ROMs modified by users.
2.- What is "flashing" ??
Flashing is writing a new full firmware image ("ROM") or a portion of the firmware into your phone's internal memory.
You can flash a Recovery (like ClockworkMod), a Kernel (or boot image), a System (the OS), a Radio, or a full firmware which contains all of them.
3.- Why should I ever want to "flash" my phone ??
If you ever want to:
- Update your phone to a newer official firmware (since it's "official", this doesn't require root or S-OFF, and won't void your waranty).
- Debrand or downgrade your phone to another official firmware.
- Replace your stock ROM for a custom ROM, eg. with or without HTC Sense, other Android builds, etc..
- Install a better Recovery utility (like ClockworkMod or Amon_Ra).
- Change your Radio ROM.
- Replace the Kernel for an overclocked or modified one.
- Etc...
4.- What is "S-OFF" and why do I need it ??
Every phone has Security ON (S-ON) by default.
In order to get full write access (eg. to flash a firmware or install a custom Recovery tool) you need to turn S-OFF.
S-OFF is different from "root": S-OFF lets you flash unsigned images using the Fastboot option on the Bootloader or through a custom Recovery (ClockworkMod Recovery is the most used).
You need to run gfree (full S-OFF) or flash an Engineering hBoot (partial S-OFF) to switch S-ON to S-OFF. You only have to do this once, not every time you want to flash.
A flashed Engeneering hBoot S-OFF will be lost if an original ROM is flashed with an RUU, but getting S-OFF with gfree will stay even if an original ROM is flashed again, because gfree modifies partition 7 of your phone to disable the emmc's write protection, and removes the brq filter from the kernel: full S-OFF.
5.- How do I return to "S-ON" ??
If for some reason (sending phone for warranty or repair, etc) you want to go back to S-ON:
- If you got S-OFF by flashing an Engineering hBoot, download the official HTC RUU for your phone version and flash the stock firmware back again. S-ON will be restored. This forum contains many threads with official RUUs.
- If you got S-OFF with gfree, it saved a backup copy to your SD card called "part7backup-xxxxxxxxxx.bin". It can be flashed back from a terminal emulator or from an ADB shell:
"dd if=/wherever/your/part7backup-xxxxxxx.bin of=/dev/block/mmcblk0p7"
6.- What is CID unlock and why do I need it ??
HTC uses CID lock to secure their phones.
The CID, or "Carrier ID", is a string that identifies carrier and language of your device; it is also contained on RUUs and is used to check that you only flash your device with the right, original ROM from your carrier/region.
CID unlock (aka "SuperCID", similar to Windows Mobile's "HardSPL") allows to flash any official RUU and install any ROM you like: from other regions, debranding, downgrading, etc.
gfree easily does both S-OFF and CID unlock.
7.- What is an "RUU" ??
RUU means "ROM Update Utility". It is a flashing tool.
RUUs are "official" shipped from HTC, they contain the flashing tool and a full firmware in a single package. RUUs are executed from a PC.
8.- What is "Radio" and what is the deal with different "radios" ??
They improve your phone signal, Bluetooth, WiFi and GPS reception, and perhaps battery life.
(Thanks Lennyuk !! you are da stig's radio cousin )
The official radios thread is located here
9.- Will "flashing" erase all my info an installed apps ??
- If you are flashing a Kernel, a Radio or a Custom Recovery, NO.
- But if you flash a system or a full firmware ROM, then YES: everything will be wiped off, so be sure to backup your stuff.
There's plenty of backup apps available for download from the Market.
(I use and recommend Titanium Backup, but it needs root )
You can also do a NANDroid backup.
10.- Will "flashing" void my warranty ??
Aha !! Good question again...
Anyway if your current stock firmware RUU is already available for download you can always flash it back, or you can backup your current ROM image, save it in your SD card or PC, and restore it later to go back to stock.
Enjoy your Desire Z the EZ-DZ way !!
BASIC SKILLS and FLASHING TERMINOLOGY:
FREQUENTLY ASKED QUESTIONS
1.- What is "Bootloader" ??
The Bootloader is a firmware management tool included on every stock ROM, it lets you reset to factory default, use "Fastboot" to flash official images, or launch the Recovery utility.
From the Bootloader you can also check your S-ON or S-OFF state, your firmware and Radio version, etc.
You don't need root or S-OFF to enter the Bootloader because every HTC phone has it.
2.- How do I enter the Bootloader ??
Power off your phone, then, hold the volume down key and the power key.
(You need to disable "Fast boot" from Settings -> Applications, or remove the battery to really power off the Desire Z. Otherwise, power off will just hybernate the phone, and when restarting you will not be able to enter the Bootloader).
To exit Bootloader you have to remove the battery.
If you have a custom Recovery installed, you can select "Recovery" to go there and rebot the phone from the Recovery menu.
3.- How can I backup my current ROM (firmware) ??
With a NANDroid backup from a custom Recovery.
4.- What is a "custom Recovery" and how to do it ??
A custom Recovery (eg. ClockworkMod, aka CWM or just CM) replaces the original Recovery from your firmware with an enhanced version.
A custom Recovery is better than the stock Recovery because it lets you safely flash unsigned or unofficial ("custom") ROMs, and lets you make full backups of your current whole firmware (memory) image (a NANDroid backup).
5.- How do I install ClockworkMod (CWM) Recovery ??
You need root and S-OFF.
Download ROM Manager from the market, install and open it.
Tap "Flash ClockworkMod Recovery", it will ask "Confirm phone model: HTC G2", tap yes (thanks for the tip stridger !!). When finished, it says "Successfully Flashed ClockworkMod Recovery!"
I recommend rebooting the phone after flashing the Recovery.
Now let's test it:
From ROM Manager, tap "Reboot into Recovery", it will ask "Are you sure you want to reboot into ClockworkMod Recovery?", tap OK.
Inside ClockworkMod Recovery, use the trackpad to navigate and select an item, or the volume buttons to scroll, and power button to go back.
Select "Reboot system now" to exit ClockworkMod.
If ClockworkMod Recovery doesn't start and you see a red triangle with an exclamation mark, flash it again. Sometimes it requires a second flash to work properly.
6.- What is a NANDroid backup ??
A complete system image that can be restored at a later date. It is more than a backup because it includes everything you currently have on your phone's internal memory: Boot, Recovery, System, Data, Cache, etc. It's a snapshot of your whole ROM.
To make a NANDroid backup, go to the "Backup and Restore" option in Clockwork and proceed. A NANDroid backup will be saved to the SD card's ClockworkMod folder.
TIP: Save a copy of your NANDroid backups to your PC. It will be useful if the SD card fails, your phone is stolen, or gets bricked.
7.- How can I restore a NANDroid backup ??
If you can access ClockworkMod Recovery it will be very easy to restore from its menu:
Enter the Bootloader (Vol down + Power), select "Recovery" and you will be redirected to ClockworkMod, from where you can restore your NANDroid backup
If you phone is bricked and you can't access the Bootloader, there's still a last chance:
You can try to flash ClockworkMod Recovery to your phone from your PC using an ADB shell and the "Fastboot" command. Tricky, but life saving.
Download the PC-flashable ClockworkMod Recovery image from here and copy it to your Andoird SDK/tools folder.
Then, open an MS-DOS command prompt, connect your phone to the PC, and flash it with this ADB command: fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
8.- What is ADB ??
ADB is the Android Debug Bridge. It uses linux commands to send instructions to the phone.
You can use ADB commands straight from an MS-DOS prompt or open an ADB shell to type linux commmands.
With ADB you can install apps, remove apps, flash images to your phone, and make many changes, all from your PC.
If you are not familiar with MS-DOS / LINUX commands this can be a bit complicated, so this is for slightly advanced users.
To get an ADB shell setup and running you need to download the Android SDK, add your SKD's path to the environmental variables, and then open an MS-DOS command line box on your Windows PC.
There's a good ADB learning guide here: ADB for noobs
(thanks steviewevie !!)
9.- What is a "Goldcard" ??
A Goldcard is a modified SD card which bypasses HTC's RUU SPL/CID check.
When inserted into your phone, it will let you override HTC's firmware flashing protection.
You can take an old spare SD card you may have laying around and convert it to a Goldcard. Size of the card doesn't matter.
When a Goldcard is inserted into the phone you can flash any official HTC firmware, even if it doesn't match your region (aka "debranding") or is older.
Of course the Goldcard is required inserted into the phone only during the flashing process. You can remove it afterwards.
10.- What is an "MD5 checksum" ??
It is a unique algorithm generated from any file, very useful to confirm a file's integrity after downloading/uploading/copying. It looks like a large alphanumeric number.
Many cookers and developers often offer the MD5 checksum number of their files, so the ROM, Radio or Kernel can be checked after download and before flashing, using any MD5 checksum app/program from a PC or the phone.
I use a free Windows app called winMD5sum to check the integrity of my downloads.
Enjoy your Desire Z the EZ-DZ way !!
Original, obsolete ROOT / S-OFF method from November 2010
(for reference purposes only)
STEP BY STEP INSTRUCTIONS: HOW TO PERMANENTLY ROOT the HTC VISION
(aka "HTC Desire Z", european or american version, not valida for UK Vodafone, Asia Desire Z and newer serial numbers)
1.- On your PC, download paulobrien's VISIONary+ R14 rooting tool app installer from his thread [click here], and copy it to your phone's SD card.
(Thanks to the authors of the rage exploit and to paulobrien for the rooting tool)
2.- On your phone, download any File Explorer from the Android Market and install it.
TIP: I use and recommend EStrongs File Explorer, but Astro or any other is OK.
3.- From the "All apps" menu, go to Settings -> Applications
There, check "Unknown sources", and turn off (uncheck) "Fast Boot".
Now tap "Development" and check "USB debugging".
Press back, and back again.
TIP: After you have finished this tutorial and rooted your phone, you can come back to Settings to re-enable Fast Boot and disable the USB debugging, if you wish.
TIP: Make sure your USB cable is unplugged form the phone during the rooting process (thanks for reporting, Thedeadcpu)
4.- Open your File Explorer, scroll and search for the VISIONary app you just copied to your SD card, and tap to install.
Now press back, back, and exit the File Explorer.
5.- From the "All apps" menu, tap VISIONary+
Check the "Set system r/w after root" option, leave the others unchecked.
Tap "TempRoot Now!" and wait... let it finish...
Tap "Attempt PermRoot Now!" It will ask for SuperUser permissions: allow.
Phone will reboot by itself.
NOTE: Remember you disabled "Fast Boot" ?? Be patient and let it boot, takes time, its normal, that's a real boot.
TEST: To test if you successfuly achieved permanent root: turn phone off, remove the battery for aprox. 30 seconds, reinsert the battery and power on.
Now you can test if your "root" is still there:
Go to "All apps", search for an app called "Superuser" and open it. If it's there and opens, well, CONGRATS: you have permanent root.
Also, you can try downloading some root-requiring apps from the market (like Titanium Backup, Root Explorer or Bernacle WiFi); if they run is because you still have root after the full reboot, which means your root is permanent.
TIP: Hey, paul spent many hours making this shizz happen, please consider following this link and saying "thanks!"
EZ-DZ GUIDE to INSTALL the ENGINEERING BOOTLOADER (hBoot) and TURN S-OFF
WITHOUT "ADB" or "SDK" SKILLS
- Again: please scroll down to posts 2 and 3 to read the FAQ to learn what's this !!
- After rooting, and if you want to flash unsigned images or make a full NANDroid backup, you need an Engineering Bootloader to switch "S-ON" to "S-OFF".
- S-OFF is different from root: S-OFF lets you flash unsigned images using the Fastboot option on the Bootloader, or through Clockwork Recovery.
- This guide will install an Engineering hBoot to get full write access to your Desire Z.
(Thanks MrPavel for the Engineering hBoot for the Desire Z !! Also, many thanks to scotty2, tmzt, adwinp, unforgiven512, vro25, schriss, and especially stridger for their efforts, testing, sharing, writing instructions; I modified it to avoid ADB shells and USB PC connection bugs)
1.- You only need to get two files: wpthis-Z.ko and hboot_7230_0.84.2000_100908.nb0. You can find them on stridger's guide thread. Download both files and come back.
Get any MD5 checksum software and check both downloaded files to see if they match the MD5 checksums listed on stridegrs post (I use WinMD5sum on my Windows PC, which is free).
It is VERY IMPORTANT to check the MD5 checksums of the downloaded files because flashing a corrupted hboot will brick your phone !!
Now, do yourself a favor and rename hboot_7230_0.84.2000_100908.nb0 to hbooteng.img (you'll thank me for this on step 5 ).
Copy both files to your phone's SD card, make sure you have a good SD card without errors, and make sure the SD card is inside your phone.
2.- Just as you did when rooting, first you need to temporarily disable "Fast boot" and enable "USB debugging" from your phone's Settings -> Applications
3.- On your phone, download "Android Terminal Emulator" from the market and install it.
Open your Terminal Emulator, and using the hardware keyboard type "su" and press Enter to gain Superuser priviledges; if you are asked for Superuser permissions, tap "Allow".
The $ prompt should have changed to #, confirming you are now typing commands as a Superuser.
4.- Now, to temporarily diasble the write protection, type this and press Enter:
insmod /sdcard/wpthis-Z.ko
It will say "insmod blah blah failed (Function not implemented) blah blah" but that's OK: your phone is complaining because you just pulled down his pants This temporary change will be gone next time you reboot, but for now, it will let you flash the engineering hBoot in the next step.
NOTE: The "wpthis-Z.ko" file you downloaded is specific for the stock Desire Z kernel, if it says something different ("exec format") is because you have a different kernel (cyanogenmod or a newer build).
5.- Now let's apply the Engineering hBoot, but PLEASE BEWARE, make sure to type the memory address mmcblk0p18 (zero p one eight) EXACTLY as you see it here, if you type something different you could brick your phone forever, so be careful and double-check you didn't mistype anything before hitting Enter !!
(don't worry, nothing bad should happen if you checked the MD5 checksum to confirm the file downloaded correctly, and you type this right)
dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18
6.- Now type sync and press Enter to make sure your changes are loaded to memory, type exit and press Enter, close the Terminal Emulator and breathe.
7.- Reboot the phone: Power off, then power on. Let it boot completely.
TEST: Let's check if you got S-OFF.
After the reboot, Boot to Bootloader and in the first line you will notice if you are "S-ON" or "s-OFF".
To enter Bootloader, power off the phone, then hold the volume down key and the power button, and you are there. To exit Bootloader, remove and reinsert the battery and power on.
Congrats !! Now you can install Clockwork Recovery (read the FFAQ !!) and use it to flash images or make a full NANDroid backup.
Kudos.
Nice. Was waiting for someone to post a thorough, step-by-step pretty much foolproof method. who knows how many people borked their D-Z's already b/c of a lack of solid information out there.
Nicely done sir.
Yeah a lot of people are calling their T-Mo G2 a Desire Z, and it is getting sketchy to know which phone is being talked about...
Tried flashing the world RUU to my Bell Desire Z and it didn't work. Even with perm root.
It says
Error 130: MODEL ID ERROR
aerok said:
Tried flashing the world RUU to my Bell Desire Z and it didn't work. Even with perm root.
It says
Error 130: MODEL ID ERROR
Click to expand...
Click to collapse
let me finish the guide please
If you've been messing around with other methods previously, better reset to stock first and the proceed.
I flashed the WWE euro firmware on my NAM "Bell" hardware using the official HTC RUU and EVERYTHING is working OK (full HTC apps, 3G over 850/1900MHz, Market, etc: easily "debranded")
So I am sure it's easy and works
Gimme a couple of hours to finish it pls
.
Allright, I'll be patiently waiting. =D
Successfully rooted my Bell Desire Z using the instructions posted; thank you gtrab! I look forward to reading your finished guide.
After permanent root, here's an interesting test (and a way to restore to factory settings
Power you phone off, now, hold the volume down button and the Power button simultaneously. Keep them pressed untill you go into a white menu saying:
VISION PVT SHIP S-ON
H-BOOT-0.85.005
MICROP-0425
RADIO-26.03.02.26_M --> this is your radio version
eMMC-boot
Oct 11 2010,20:10:38 ---> this is the date of your current firmware (ROM)
You will also see menu with these optins:
FASTBOOT
RECOVERY
FACTORY RESET ---> you can use this option to "clean" your firmware to a pristine MINT state (everything will be erased)
SIMLOCK
IMAGE CRC
PS: to get out of this screen without restoring your firmware, just remove the battery and power on
Great guide for the noobs dude Should be made a sticky,
Just have to add the s-off tutorial when released today by POB and it will be a complete winner
JD
@JupiterDroid please keep me posted !!
PS: Interestingly enough, if you check my previous post (post 10), I have S-ON
(well, by flasshing the EURO ROM I was flashing an HTC signed firmware indeed)
Nice work mate
Please explain
1)what is radios and what is the deal with different radios. What is safe, what is not. What it is for?
2)how to create a full backup of your current phone/rom/state and be able to recover it anytime later if you wish...
This is two of the initial concerns that Noobs like me need to know to, Thanks..
yudhistre said:
Please explain
1)what is radios and what is the deal with different radios. What is safe, what is not. What it is for?
They improve your phone signal, bluetooth, wifi and gps inproving the quality and purhapse battery life (in theory)
2)how to create a full backup of your current phone/rom/state and be able to recover it anytime later if you wish...
once you have a custom recovery installed (Clockwork Mod or Amon_Ra) you can do a nandroid backup which is a complete system image that can be restored at a later date.
This is two of the initial concerns that Noobs like me need to know to, Thanks..
Click to expand...
Click to collapse
answers in the quote
In the tutorial it says to disable Fast Boot... can we re-enable it afterwards?
1) Does this interfere with the functionality of HTCSense.com?
That was one of the nice things about HTC Sense UI 2.0
2) Doing this gives no more OTA updates I assume, will I have to flash the latest RUU each time?
3)Just thought of another "issue". If this is the EU version, would HTC Locations only have EU maps?
Lennyuk said:
answers in the quote
Click to expand...
Click to collapse
thanks lennyuk, will paste to front post
CWolfCW said:
In the tutorial it says to disable Fast Boot... can we re-enable it afterwards?
Click to expand...
Click to collapse
yes, this will also be included once I finish the tuto
whodere said:
1) Does this interfere with the functionality of HTCSense.com?
That was one of the nice things about HTC Sense UI 2.0
2) Doing this gives no more OTA updates I assume, will I have to flash the latest RUU each time?
3)Just thought of another "issue". If this is the EU version, would HTC Locations only have EU maps?
Click to expand...
Click to collapse
Yes I will also talk about that when I finish writing the tuto
Flashing my phone now.
Doing it via a Parallels Windows 7 VM on OSX....
Was a little worried in the beginning when the phone rebooted and Parallels asked me if I wanted to keep the phone attached to the VM - but it looks like it's going through now as there is a progress bar "Sending"...
Oh oh. Said it could not update due to incorrect model?
Hmmm...
gtrab said:
thanks lennyuk, will paste to front post
yes, this will also be included once I finish the tuto
Yes I will also talk about that when I finish writing the tuto
Click to expand...
Click to collapse
You should also include what to do the the "Connect to PC" message comes up. I just ignored it.
HTC DESIRE UNROOTING PROCESS, AND THE ANDROID HBOOT, FASTBOOT, AND RECOVERY MENU OPTIONS
(How to Revert to Stock/ What to do before taking my phone back to the service centre?/ How to restore my phone after a failed OTA update on a Rooted phone/My phone is stuck at the HTC Quietly brilliant screen/My boot animation keeps looping, What to do?)
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"
}
Courtesy:
To EddyOS for the Tutorial on getting the PB99IMG from the RUU
I didnt find any newbie friendly guides for unrooting the HTC Desire, on XDA. Even some external ones arent that easy to follow, unless you have a very good idea about what is going on.
The main purpose of this post is to benefit people who have got an SLCD bricked device on their hands with nothing displayed except a blank screen, and cannot remember the key sequences necessary to activate the unrooting process, or to run the OTA Update and get to Android recovery. You will note that I have added the time taken at each step in the process. This will benefit people with SLCD bricks waiting anxiously without seeing anything on screen.
For a complete guide on Unbricking an HTC Desire, please see my thread here.
There are two methods of unrooting an HTC Desire.
Methods:
Get the latest RUU for your region from Shipped Roms. This is an exe file. You can run this file directly from PC. Then connect your device when so prompted.
The second method is to flash the rom.zip directly from the Android bootloader interface, after renaming the Rom.zip (which is actually obtained from the RUU) to PB99IMG.zip [See EddyOS's excellent step-by-step guide for dummies, in the FAQ below]
Method1 does not need any explanation (If necessary, I will add illustrations of this process later along with error codes)
Method2 is illustrated below.
Note: The following post illustrates the actual steps necessary to unroot your HTC Desire by running the PB99IMG.zip. This is also the method to upgrade the software with the RUU, the last method to fix bootloops cause by a bad boot, and also the way to unbrick an SLCD bricked Desire. Note that another simple method exists to unroot the device, and that is by directly running the exe file of the RUU from Windows. Though simple, this is slightly riskier, since complications with Windows drivers, or a sudden power surge or PC reboot can semibrick/brick your device. The following method using PB99IMG.zip eliminates those problems.
Unrooting is just one of the steps necessary to unbrick an SLCD bricked HTC Desire. The process is a pain for these users because they cant see anything on the screen and left pressing keys in sequence, whose function they can only guess. Also they need to wait specific amounts of time before pressing the sequences.
I'm making visible the steps which the Android system proceeds through, when you run a PB99IMG.zip to unroot your Android device. I've also included the time taken before each step while running the WWE 2.29 RUU as PB99IMG.zip. The time isnt much different for other ROMs. To be sure, just give it about 30secs more than the time I've noted.
Initial steps:
Create a goldcard if you want to convert a branded Desire to unbranded, or vice versa, or to make a Desire of one region (CID) accept software written for a phone of another region.
After creating the goldcard, format it as FAT32. If more than one partition exist, delete the rest, and format one as Primary and FAT32.
Put the file PB99IMG.zip into the root of the goldcard. Note that the name must be PB99IMG.zip and not PB99IMG.zip.zip. Windows has a tendency to rename it as the latter.
If you dont already have the PB99IMG.zip, you can get it by running the RUU, and while the RUU is loaded (dont start the RUU upgrade. Just click on the exe, and when the welcome screen of RUU shows up,) search in your Temp folder for the file rom.zip. Hint: To quickly navigate to Temp, Type the following into the Run window: %TEMP% [If you still get this step confused, see EddyOS's excellent tutorial on this, in the FAQ below]
To run the PB99IMG.zip, just reboot with Vol- and power button pressed.
I'm describing the whole boot process below for Reference, though.
Hboot mode (Vol- & Power key. Key them pressed for a 5-6 secs
FOR INSTALLING ANY RUU AS PB99IMG.ZIP
Press Vol- , then w/o releasing it, press Power button + Vol –
After 3-4 secs, the following screen shows up momentarily:
· Fastboot
· Recovery
· Clear Storage
· Simlock
This shows the above few options for 2-3 seconds, and then directly checks for PB99IMG.ZIP. It displays:
SD Checking…
Loading…
PB99DIAG.ZIP
Pb99DIAG.nbh
PB99IMG.ZIP
When it finds PB99IMG.zip, it starts to load it (13 secs after you press the Vol- & power key)
It gives the next options after 2min 20seconds (for the WWE 2.29 RUU) from the initial key press of Vol- and Power key.
Parsing………………….[SD zip]
1. Bootloader
2. Radio V2
3. Radio_Cust
4. Boot
5. Recovery
6. System
7. Userdata
8. Splash1
9. Splash2
Do you want to update device?
<Vol Up> Yes
<Vol Down> No
So, net key sequences involved:
· Back+Power
· Power again
· Vol Up
If we chose No, next option:
Do you want to reboot device?
<Vol Up> Yes
<Vol Down> No
If you pressed Yes, then:
Update is in progress..
Do not power off your device.
1. Bootloader -OK
2. Radio V2 -OK
3. Radio_Cust -OK
4. Boot -OK
5. Recovery-Unzipping/Updating
6. System
7. Userdata
8. Splash1
9. Splash2
It cycles through each of these in turn. For me, it took exactly 2 min 17 secs for time when I chose to apply update, to when update was completed.
(Note: At times, it may update the bootloader and reboot. If you have an SLCD screen, when the device reboots, you may not see anything onscreen (black). At this point, it is notable that the device boots to Fastboot instead of Bootloader, so you will need to press Power button again to get it to resume the update process. Once it completes, you will be presented the options to reboot the device. So you just need to Press Vol + after some time)
It displays:
Update complete
So you want to reboot device?
<Vol Up> Yes
<Vol Down> No
Congratulations. Your phone is now officially unrooted.
On rebooting, HTC screen shows up for a few seconds.
Then a green Down arrow in a green circle shows up for another 5-6 seconds.
Then, HTC screen again.
Finally, HTC screen disappears and the HTC Quietly brilliant logo shows.
Your device now boots into the Android phone.
Total time taken: 6min 30 seconds.
If the Rom is incompatible with your SLCD device, at the reboot stage, you will hear the momentary vibration. Then after about 10-20secs, you will hear the HTC Quietly Brilliant tone. The phone will boot, and the keys light up after about a min, indicating that the Android system has booted up. Since the Rom is incompatible, there's still nothing on screen. To shutdown the booted up phone, press power key, then swipe your finger vertically up-down like you do to unlock your phone normally, which is exactly what you're doing. Then keep Power button pressed until the phone vibrates. This means it is presenting you with the Power menu. At this point press the trackball once, then once more. The phone will now shutdown. At this point you can flash your SLCD compatible update.zip (OTA) and unbrick it.
FASTBOOT mode
Back+Power key:
4 options:
· Bootloader (For running PB99IMG.zip)->Choose with Power key (This loads the Bootloader/Hboot mode)
· Reboot
· Reboot bootloader
· Power down
Bootloader (Hboot mode) or PB99IMG update mode.
Performs the following check on the PB99IMG.zip:
1. Bootloader
2. Radio V2
3. Radio_Cust
4. Boot
5. Recovery
6. System
7. Userdata
8. Splash1
9. Splash2
Do you want to start update?
Vol Up: Yes
Vol Down: No
So, net key sequences involved:
· Back+Power
· Power again
· Vol Up
If we chose No, next option:
Do you want to reboot device?
<Vol Up> Yes
<Vol Down> No
No brings up the following options:
· Fastboot
· Recovery
· Clear Storage
· Simlock
Frequently Asked Questions (FAQs) for Newbies
Frequently Asked Questions (FAQs) for Newbies
1. Why do I need to Unroot?
To take the device to service centre for warranty
To fix problems with Boot and Recovery unsolved by other methods
2. What are the methods of unrooting? Which is safer?
Basically both methods are the same. It is the process of flashing an original HTC software onto your ROM. One method involves running an .exe file from Windows, and the other is by running a file extracted from this exe file from the sdcard. The latter method is called the PB99IMG.zip method, because it involves renaming the rom file so extracted as PB99IMG.zip. This method is generally safer because the whole process can be completed from your phone itself. The method of running the exe is prone to corruption because of problems with Windows drivers, your Usb cable, Battery issues, and even a Windows System Failure or System Crash or Power Failure!
3. How do I get a PB99IMG.zip? [EddyOs's complete tutorial for Dummies]
(The illustrations and answer to this question has been provided by EddyOS)
If you still get lost, dont even bother to ask!!
1. Double-click on the RUU file and wait until you get to the first main screen
2. Move the window to the bottom of your screen because it can’t be minimised and will sit on top of all other windows
3. 3. Click on Start>Run and type ‘%temp%’. Then click ‘OK’
4. Look for the newest folder in the temp folder. Double-click on it
5.Copy the file called ‘rom’ to your Desktop
6. Rename the file called ‘rom’ to ‘PB99IMG’
7. Copy this file to the root of your SD card (root = not in any folders)
4. Do I need a Goldcard?
If you have a recent version of the RUU for your Device, available on Shipped Roms, you dont need a goldcard. This is the usual scenario for people who purchased their Desire in Europe, and so have an unbranded Desire. All Branded Desires need a correct branded version of the RUU, and any other RUU including WWE (Worldwide English, or European) RUU will not work for them. Also if an unbranded Desire user wishes to change RUU to a branded version, he will need a Goldcard. This is because all Desires have a particular software tag in the Rom, called the InfoCID. This dictates the Region code. For Eg. An Indian Desire is branded and has InfoCID of HTC__038. When you change a RUU to different region, what you actually do is reset the InfoCID setting. Changing the InfoCID setting requires a Goldcard.
5. What is a Goldcard?
It is a normal MicroUSB card specially prepared in such a way that its Sector 0 (which normally doesnt hold anything useful) is modified, so that it signals to the HTC RUU that the InfoCID may be changed.
6. How do I create a Goldcard?
Just download this tool (Credits and All Rights by [email protected]), and run it.
In case your card in phone cannot be detected by the PC, download and install Goldcard Helper from the market and use it to generate the Reverse CID
7. Can you tell me more about Goldcards?
Sure. I've already posted it for you. Read the FAQs in this thread.
8. I think I've bricked my Desire. I cant unroot it with your method. What can I do?
Follow my thread on Unbricking a Bricked Desire. Though it's written for SLCD device, it will work for AMOLED too. The chance of success depends on two essentials: 1-That you have a working goldcard, and 2-You have a compatible RUU (of version higher or equal to the current version)
Reserved for the future...
Hi,
Thanks for informative article. Can I install PB99IMG.zip using the standard clockworkmod @ recovery mode?
Edited: I tried using windows, it failed. I tried the 2nd method, but Desire does not reconize the PB99IMG.zip file and so nothing happens.
medomedo said:
Hi,
Thanks for informative article. Can I install PB99IMG.zip using the standard clockworkmod @ recovery mode?
Edited: I tried using windows, it failed. I tried the 2nd method, but Desire does not reconize the PB99IMG.zip file and so nothing happens.
Click to expand...
Click to collapse
When you mean you tried it in Windows, do you mean you connected the cable and ran the exe file? If so, what error did it give you?
You cant flash it via Clockwork. And you dont have to.
Assuming you have only one partition on your sdcard and it is formatted correctly as FAT32 and the PB99IMG.zip is placed in the root folder, and you press Vol- & Power button to start your Desire, it will detect the file and start the update process. Problems usually happen when the card is not formatted correctly, and the file is named PB99IMG.zip.zip and not just PB99IMG.zip. This is because Windows may not display the full filename including the zip extension.
one simple question
i wanted to root my phone so i could flash to a custom ROM, but i have since updated to 2.13.707.2 OTA, but i cant seem to find the RUU in shipped ROMs site...
could i use the 2.13.707.1 RUU to unroot?
Hi droidzone,
Thanks for the quick response. The error I got from windows 7 pro was (translated from German):
error 170: USB connection failure. The update software was not able to connect to mobile. Make sure the cable is connected to both PC and mobile.
My SD card is partitioned into FAT32 and a small parition ext3 for apps. This configuration is defacto for DeFrost, OpenDesire, and Oxygen ROMs. I moved the rom.zip file and renamed it using rootExprorer application to be 100% sure. When I go to recovery mode and then to Clockwork I can see the exact file name and its correct PB99IMG.zip (I am not sure if the system is case sensitive) but PB99IMG.zip is the exact name. Of course I restarted win7 few times but nothing changed. I need this because my mic is bricked like described in this thread
http://forum.xda-developers.com/showthread.php?p=9951668&posted=1
What can I try next? thanks!
medomedo said:
Hi droidzone,
Thanks for the quick response. The error I got from windows 7 pro was (translated from German):
error 170: USB connection failure. The update software was not able to connect to mobile. Make sure the cable is connected to both PC and mobile.
My SD card is partitioned into FAT32 and a small parition ext3 for apps. This configuration is defacto for DeFrost, OpenDesire, and Oxygen ROMs. I moved the rom.zip file and renamed it using rootExprorer application to be 100% sure. When I go to recovery mode and then to Clockwork I can see the exact file name and its correct PB99IMG.zip (I am not sure if the system is case sensitive) but PB99IMG.zip is the exact name. Of course I restarted win7 few times but nothing changed. I need this because my mic is bricked like described in this thread
http://forum.xda-developers.com/showthread.php?p=9951668&posted=1
What can I try next? thanks!
Click to expand...
Click to collapse
i wanted to root my phone so i could flash to a custom ROM, but i have since updated to 2.13.707.2 OTA, but i cant seem to find the RUU in shipped ROMs site...
could i use the 2.13.707.1 RUU to unroot?
Click to expand...
Click to collapse
It's worth a try.Normally an older version cant be used on top of a newer version. It will give a "main version is newer" error. A newer version will always work. If it still doesnt work for you, downgrading may be the only resort. Get Teppic's downgrade tool for that.
error 170: USB connection failure. The update software was not able to connect to mobile. Make sure the cable is connected to both PC and mobile.
Click to expand...
Click to collapse
Could be a Windows driver issue. The PB99IMG.zip method should work for you though. Remove the ext partition, and partition the whole card as one big FAT32 partn, format it once, and then put the file there again. It should work.
If it still wont work, use another sdcard, repeat these steps.
droidzone said:
It's worth a try.Normally an older version cant be used on top of a newer version. It will give a "main version is newer" error. A newer version will always work. If it still doesnt work for you, downgrading may be the only resort. Get Teppic's downgrade tool for that.
Click to expand...
Click to collapse
Thanks for clearing up for me...i know now what to prepare...
FYI, I used another SDcard with only FTA32 partition and it worked. Howerver it did not fix the mic problem. Thanks!
medomedo said:
FYI, I used another SDcard with only FTA32 partition and it worked. Howerver it did not fix the mic problem. Thanks!
Click to expand...
Click to collapse
Good..If even a new RUU installation didnt work, I'm guessing Hardware issues. Maybe a good time to get it checked.
I have a debranded Desire on 2.2, accidentally updated with an OTA yetserday without goldcard and have now lost wifi.
trying to downgrade with goldcard but it failing
tried PB99IMG method but get the following
On HBOOT , loads PB99IMG but states main version older update failed.
In recovery fails to open E: signature verification failed.
Any help gratefully received
stevep999 said:
I have a debranded Desire on 2.2, accidentally updated with an OTA yetserday without goldcard and have now lost wifi.
trying to downgrade with goldcard but it failing
tried PB99IMG method but get the following
On HBOOT , loads PB99IMG but states main version older update failed.
In recovery fails to open E: signature verification failed.
Any help gratefully received
Click to expand...
Click to collapse
You have a debranded Desire, you said.
Well then, the PB99IMG of the latest RUU should work for you.
Just flash it as I've described from Hboot.
Put the goldcard in just for safety, and do it.
Should work.
Hi Droid
Thanks for quick reply.
Can I just confirm a few bits . . .
Goldcard leaves 3 folders on SD ( android_secure, footprints,lost.dir)
Then copy and rename the RRU to PB99IMG and copy to SD.
Reboot to HBOOT and then get previous messages :-(
stevep999 said:
Hi Droid
Thanks for quick reply.
Can I just confirm a few bits . . .
Goldcard leaves 3 folders on SD ( android_secure, footprints,lost.dir)
Then copy and rename the RRU to PB99IMG and copy to SD.
Reboot to HBOOT and then get previous messages :-(
Click to expand...
Click to collapse
To be safe, do the foll verbatim:
Delete any additional partitions on goldcard (if any). The goldcard should have one big FAT32 partition
Format it as FAT32 once again with original allocation size
Transfer the PB99IMG.zip that I have linked in my post to the root.
Check the filename and be sure that it is not PB99IMG.zip.zip
Reboot in Hboot by Pressing the Vol- & Power key
The file will be detected and presented with menus
Follow the instructions in the OP
I'm guessing I don't need a goldcard with my unbranded desire?? But screwed if it does. Also what is the unbranded ruu currently as there is literally hundreds? Thanks
Sent from my HTC Desire
BTW, what does it mean WWE rom?
WWE - World Wide English
To others, if you've flashed the OTA without your gold card do it again manually WITH your gold card and you're good to go. Flashing a full RUU is only need if you can't fix it manually
HTC 123 said:
I'm guessing I don't need a goldcard with my unbranded desire?? But screwed if it does. Also what is the unbranded ruu currently as there is literally hundreds? Thanks
Sent from my HTC Desire
Click to expand...
Click to collapse
medomedo said:
BTW, what does it mean WWE rom?
Click to expand...
Click to collapse
EddyOS said:
WWE - World Wide English
To others, if you've flashed the OTA without your gold card do it again manually WITH your gold card and you're good to go. Flashing a full RUU is only need if you can't fix it manually
Click to expand...
Click to collapse
Try what Eddy said. If it still gives you trouble, do what I listed.
WWE ->European Unbranded version
The latest is what I linked.
Eddy
Got the link, can you just confirm process, please
Thanks in advance
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.
Hello. I have a problem with usb connection after flashing firmware. I tried
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8 _Radio_01.01_U11440261_56.02.50306G_2_F_release_42 5571_signed_2
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.1 5_R1_Radio_01.01_U11440261_56.02.50306G_2_F_releas e_426891_signed_2
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.1 5_R2_Radio_01.01_U11440261_56.02.50306G_2_F_releas e_427846_signed_2
and many others, actually i flash this
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip
I have cid_032 , s-off, unlocked . While i'm flashing firmware all files are flashing correctly except tp_Syn3351.img and tp_MXM11976.img . On the screen you also see problem with sensor_hub.img, but i solve this problem (flashing 1.32................. and 4.28.................... ruu, but 3.35................. causes this error).
For this moment i can:
- flash firmware, RUU (from 0PJAIMG.zip), recovery ( Combined, Nowipe zips) and full stock from this link https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
- everything works, i can call, send messages, wifi also works.
I can't:
- connected phone via usb isn't recognized, device manager doesn't show anything, fastboot and adb not work. I have also HTC M8 and this device is recognized properly.
-
When flashing the phone did you use the original fastboot.exe or the htc_fastboot.exe?.
Beamed in by telepathy.
gumiak9 said:
Hello. I have a problem with usb connection after flashing firmware. I tried
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.8 _Radio_01.01_U11440261_56.02.50306G_2_F_release_42 5571_signed_2
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.1 5_R1_Radio_01.01_U11440261_56.02.50306G_2_F_releas e_426891_signed_2
0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.1 5_R2_Radio_01.01_U11440261_56.02.50306G_2_F_releas e_427846_signed_2
and many others, actually i flash this
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.28.401.3_Radio_01.01_U114401011_117.00.61117G_2_F_release_498151_signed_2.zip
I have cid_032 , s-off, unlocked . While i'm flashing firmware all files are flashing correctly except tp_Syn3351.img and tp_MXM11976.img . On the screen you also see problem with sensor_hub.img, but i solve this problem (flashing 1.32................. and 4.28.................... ruu, but 3.35................. causes this error).
For this moment i can:
- flash firmware, RUU (from 0PJAIMG.zip), recovery ( Combined, Nowipe zips) and full stock from this link https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
- everything works, i can call, send messages, wifi also works.
I can't:
- connected phone via usb isn't recognized, device manager doesn't show anything, fastboot and adb not work. I have also HTC M8 and this device is recognized properly.
-
Click to expand...
Click to collapse
It looks like you've attempted to flash several different versions of your SKU's firmware. What was your original OS version?
shivadow said:
When flashing the phone did you use the original fastboot.exe or the htc_fastboot.exe?.
Beamed in by telepathy.
Click to expand...
Click to collapse
I'm sorry, i don't understand. I use method :
- i put RUU or firmware on sd card (external usb memory card reader)
- i change the file name to 0PJAIMG.zip
- i turn the phone in download mode, "start flash" and done
Computerslayer I'm from Poland, phone i bought from Germany and when he arrived had status like on the screen. I was wondering if the phone was different cid (maybe T-Mobile DE), but like i said he had s-on and cid_032. This guy told me that this problem appeared after OTA update. I use sunshine method, now it's s-off but i don't have supercid because pc doesn't recognize phone. I have a pendrive Sandisk dual micro usb and when i turn on the phone in recovery mode (TWRP 3.1.0.0) and i plug the pendrive this phone does not recognize it.
That pic says your phone is s-on.
Supercid is no longer valid so no point in trying it.
There is 2 different versions of fastboot.exe. "fastboot.exe" is the standard one. "htc_fastboot.exe" is specifically written for htc phones.
Double check that the firmwares you're flashing match your phone variant. The fail to write on those specific files could highlight a variant mismatch.
Beamed in by telepathy.