Related
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.
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.
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available. (boot to fastboot mode and type the following command "fastboot getvar version-main", This is the true version of your phone!)
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
Those with ICS hboot should works without any problem, someone had test it on JB hboot and works(updated in step 6, 7). but we need more testers.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost. Then wipe all data (including SD) using your custom recovery. (important! Otherwise, you may not be able to receive OTA).
1. You have to download a "custom RUU" that can be found here.
http://db.tt/z8ajRTuH
Feel free to give a thanks to billd2439, he provide this working link to download the custom RUU.
Just go to #115 http://forum.xda-developers.com/showthread.php?p=35139501#post35139501 and give him a thanks
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
you may want to find RUU here http://www.htcruu.com
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. type the following command to get the information from your phone.
fastboot getvar all
you should pay attention to the following information
modelid:
cidnum:
mainver:
hbootpreupdate:
7. edit the value of "modelid", "cidnum", "mainver" and "hbootpreupdate" to match the information you get from step 6.
by doing this your will try to fool the RUU to belive that you are going to flash a newer version e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
Thanks ahmedaljaf for telling me to modify hbootpreupdate to makes JB downgrade works
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock", remember to turn on USB Debugging, unplug the USB cable and reboot your phone, then goto fastboot mode and connect the USB cable.
(important, do the above to avoid error messages in RUU)
12. run the file "ARUWizard.exe" inside the folder "customRUU" (see the Attached Readme_Eng.pdf if the customRUU cannot display in correct language)
You can change the customRUU to English version by just delete or rename the language file "ARUWizard_Eng.lng" (Thanks ahmedaljaf for telling me this :good
13. follow the on screen instruction,
14. your phone should reboot and boot up with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
If you can return stock with this method, please reply and list the version here. And you can give me a "thanks" :good:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
There's NO way to downgrade hboot unless you have s-off.
Sent from my HTC One X using xda premium
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
HebeGuess said:
They are somebody on chinese forum who use this method claimed he was able to do hboot downgrade through this method, but no one seem suceed so for.
Well, technically this method able to get you spoof ROM version because it check on your PC. While for hboot it validate the signature and version on the phone before upgrading itself. You can see the process if you push the firmware yourself via fastboot.
Click to expand...
Click to collapse
What if we hex edit the 0.95.0000 before we put it into the rom.zip to make it think that it's a newer version, will that brake the signature?
Sorry but I don't have the guts to try it myself
a good link
hokoonho said:
Who should read this post?
You have updated your One X to a newer version via OTA, then you want to restore the software/ return stock but the latest RUU is not available.
You have some basic skills to flash things using "fastboot"
Those who want to back to stock and wait for the JB OTA.
The concept behind.
1. Fool the RUU to make it believe that it is flashing the latest ROM, but actually, we are flashing an older version.
2. after that, boot up the phone with older version of software, then OTA and update the phone to latest software.
How to do that?
0. backup all your stuff including those in SD, all your stuff in your phone will be lost.
1. You have to download a "custom RUU" that can be found here (you can also found a rom that for One X for HK only).
http://pan.baidu.com/share/link?shareid=64762&uk=1042525484
If your phone is from other region, you may want to find the rom or RUU here http://www.htcruu.com
2. Download the ROM file, it should be in zip format. (You can also extract the rom file by running a RUU, just run the RUU, don't click anything and search the computer for "rom.zip") (In my case, I have an older version 1.29.708.15 rom extracted from RUU)
3. unzip the customRUU.zip to a folder, e.g. "customRUU"
4. unzip and extract "android-info.txt", "boot_signed.img" and "system.img" to a folder
5. open android-info.txt with "notepad" (notepad++ is highly recommended)
6. edit the value of"cidnum" to match your phone, e.g. ("HTC__622" for HK, "HTC__621" for Taiwan)
7. edit the value of "mainver" to the current software version your phone. e.g (I have OTA my phone to 2.17.708.7, but now I want to fool the RUU with this old rom with a version number of 1.29.708.15, so I change the value to 2.17.708.7 )
8. save the file.
9. zip "android-info.txt", "boot_signed.img" and "system.img" and rename the zip to "rom.zip". (remember only zip the files, not the whole folder!)
10. place the "rom.zip" you just created to the "customRUU" folder
11. make sure your phone is still "unlock"
12. run the file "ARUWizard.exe" inside the folder "customRUU"
13. follow the on screen instruction,
14. your phone should reboot and boot with and old version of software.
15. restart the phone and go to fastboot mode.
16. extract the "recovery_signed.img" from your old "rom.zip" (not the rom.zip you create! ) and place it to some where.
17. flash the recovery by typing the following command "fastboot flash recovery recover_signed.img"
18. relock the phone
19. boot up the phone and try OTA
18. if the OTA download finish but fail to reboot to recovery update automatically, just manually boot to recovery and the update will be ok.
Click to expand...
Click to collapse
link to custom ruu its dead. any alternative?
ionut.micu said:
I wonder, if you put in the "rom.zip" the "hboot_0.95.0000.img" from an older RUU will you be able to downgrade the 1.28 hboot also?
Click to expand...
Click to collapse
No, if you include the old hboot, the process will be fail.
Sent from my HTC One X using xda premium
darckreign1984 said:
link to custom ruu its dead. any alternative?
Click to expand...
Click to collapse
link updated, enjoy
Sent from my HTC One X using xda premium
or you could just cook yourself a flashable zip from the rom.zip. Then fastboot flash rec and boot. Chances are ics wont boot on the newer hboots. Still the ota can be flashed as update.zip maybe.
usefull for some case
bookmarked
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
unsucces
speedofheat said:
BRILLIANT! Absolutely brilliant! Thanks a million hokoonho. This method worked like a treat on my HK_621 HOX which was running ARHD 9.7.2
Click to expand...
Click to collapse
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
darckreign1984 said:
arhd 12 and hboot 1.28 - not working
the 10 min time to flash its useles.... nothing its flashing in this time
Click to expand...
Click to collapse
The method works well with ICS, even with other HTC model as well, but I am not sure if it still work will JB and latest hboot. But it won't kill your phone.
Sent from my HTC One X using xda premium
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
A brief translation was made for those cannot Open the customRUU in correct language. go to OP for the pdf file
hokoonho said:
It's OK, The RUU may not be able to select the right language to display, but It still works, since the RUU only use adb and fastboot to finish its process, and all these adb and fastboot are run in English...
I am translating the Text to English and will upload a guide, just follow the guide to click the buttons... wait for a few minutes please.
Click to expand...
Click to collapse
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Could you provide a ling to the English version you've got ? Thanks
lukems said:
No problem, I have found an English version.
I am finding that I get a Error 170 USB error... I believe this is because I have an unlocked bootloader.
So I re-locked the bootloader... and found myself unable to get past the bootloader.
I managed to run the RUU whilst phone was at the bootloader screen,
Replaced the temp rom.img with the created rom.img in your guide,
But it ended up failing with a Error 132 signature check.
I am not sure how to proceed.
Click to expand...
Click to collapse
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
hokoonho said:
Don't relock at this moment, otherwise, you will not be able to flash the stock recovery. Unlock it first. Make sure USB debugging is on, then REBOOT to fastboot and start the RUU. Or...Try another USB cable, DON'T connect via a USB hub...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ok will try now.
Edit: I am now waiting for it to finish... we will see soon enough if it works.
Screenshot showing upgrade screen uploaded.
Edit 2: It completed successfully
build downgraded from 2.17.401.2 to 1.28.771.9
lukems said:
I have followed the instructions, and now I am at the point where I run "ARUWizard" and follow the onscreen instructions...
However, The test is not English, it is funny looking as if the language is corrupt/unrecognised.
See attachment.
Any advice?
Click to expand...
Click to collapse
lukems said:
Ok will try now.
Click to expand...
Click to collapse
I have updated step 11. should disconnect the USB cable during reboot. If it still not work, restart both your phone and PC.
Hello guys ,
i hope some one can help me in that case . i just a m8 one mobile from an online site
it's good but when i have tried to update it this message appeared :
'Variant system version - We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system please contact us via the support section at HTC - Mobile Phones, Smartphones, Cell Phones, Tablets'
And that some of information what i can got .
***Software status: Modified***
***UNLOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.24.21331147A1.09G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.18.708.12
eMMC-boot 2048MB
Jan 15 2015, 23:49:38.0
Software number : 3.28.709.5
Baseband Version : 1.24.21331147A1.09G_20.68.4196.01_F
Build number : 3.28.709.5 CL389838 release-keys
So If you want more information tell me how i can get it to you
So please help me guys
Hello,
Please provide your phone's CID & MLDELID. To solve this problem, you need to either restore a stock firmware & stock twrp backup, or flash a stock RUU. Either way, the firmware & software must have matching cid & modelid.
As of right now, the data you posted indicate that your phone has mismatching firmware & software (x.xx.708 and x.xx.709).
Cheers
I'm really sorry i don't know how to get the information so, Could you please tell me how i can provide you phone's CID & MLDELID ? i mean the steps for it !
Mike Smaan said:
I'm really sorry i don't know how to get the information so, Could you please tell me how i can provide you phone's CID & MLDELID ? i mean the steps for it !
Click to expand...
Click to collapse
Install Terminal Emulator for Android from Google Play Store. Run commands:
getprop ro.cid
getprop ro.mid
rv_30 ! Thank you man
i got them my cid : HTC_622
And my Mid : OP6B63000
shirreer said:
Hello,
Please provide your phone's CID & MLDELID. To solve this problem, you need to either restore a stock firmware & stock twrp backup, or flash a stock RUU. Either way, the firmware & software must have matching cid & modelid.
As of right now, the data you posted indicate that your phone has mismatching firmware & software (x.xx.708 and x.xx.709).
Cheers
Click to expand...
Click to collapse
i got them my cid : HTC_622
And my Mid : OP6B63000
Mike Smaan said:
i got them my cid : HTC_622
And my Mid : OP6B63000
Click to expand...
Click to collapse
Your device is Asia-HK-CHT variant.
Please visit the link below to find answers and links that resolve your exact issue:
http://forum.xda-developers.com/htc-one-m8/help/help-returning-to-stock-hon-kong-htc-t3005829
There are links to stock RUU directly from HTC as well as twrp backup+firmware for you.
Good luck
shirreer said:
Your device is Asia-HK-CHT variant.
Please visit the link below to find answers and links that resolve your exact issue:
http://forum.xda-developers.com/htc-one-m8/help/help-returning-to-stock-hon-kong-htc-t3005829
There are links to stock RUU directly from HTC as well as twrp backup+firmware for you.
Good luck
Click to expand...
Click to collapse
Thank you for trying help me , but unfortunately the link from jan,2015 it's not working or missed . and i'm really want back to to stop or do any thing to update the phone
I'm sorry for bothering you sir
Mike Smaan said:
Thank you for trying help me , but unfortunately the link from jan,2015 it's not working or missed . and i'm really want back to to stop or do any thing to update the phone
I'm sorry for bothering you sir
Click to expand...
Click to collapse
It's no bother, but, you missed the post that says:
Originally Posted by xunholyx *
Okay. So I did a little research and came up with an official HTC RUU for your phone. As far as I know, it is the latest for the Hong Kong version (4.4.3). I say as far as I know because I don't deal with HK versions very often here.
Hook up to your PC and get into ADB/fastboot.
Download the official RUU from HTC's website by clicking here.
http://dl4.htc.com/RomCode/Source_and_Binaries/m8uhl-3.4.0-gf17cce1.zip
Reply
Thanks to your help, I have successfully returned to stock! Thank you for the kind and quick reply!
shirreer said:
It's no bother, but, you missed the post that says:
Originally Posted by xunholyx *
Okay. So I did a little research and came up with an official HTC RUU for your phone. As far as I know, it is the latest for the Hong Kong version (4.4.3). I say as far as I know because I don't deal with HK versions very often here.
Hook up to your PC and get into ADB/fastboot.
Download the official RUU from HTC's website by clicking here.
http://dl4.htc.com/RomCode/Source_and_Binaries/m8uhl-3.4.0-gf17cce1.zip
Reply
Thanks to your help, I have successfully returned to stock! Thank you for the kind and quick reply!
Click to expand...
Click to collapse
that link isn't exist and when i downloaded the offical rom for M8 called :
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
while updating error came called " Model ID ERROR " ..
So what i should do now ?
Mike Smaan said:
that link isn't exist and when i downloaded the offical rom for M8 called :
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
while updating error came called " Model ID ERROR " ..
So what i should do now ?
Click to expand...
Click to collapse
Here's a thread with a link for the firmware you need. Follow the instructions on how to properly install your firmware. http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 01:58 PM ---------- Previous post was at 01:54 PM ----------
The firmware you tried to install is not the correct one for your phone. Scroll down to the firmware for your CID: HTC__622 and MID: 0P6B63000 and you should be fine.
Mike Smaan said:
that link isn't exist and when i downloaded the offical rom for M8 called :
RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
while updating error came called " Model ID ERROR " ..
So what i should do now ?
Click to expand...
Click to collapse
You can't just flash any file you please. RUU & firmware you want to flash MUST be specific for your device's region and variant model - in your case, you must flash ASIA-HK-CHT firmware & software. ATT & CINGULAR are US specific, and will not flash on your phone without modifications.
Instead, download the 1.60.x.x from the link provided by @Jerrel7, and the TWRP stock backup from 1.60.708.x provided below:
https://mega.co.nz/#!e8AFCCQZ!2-2Lx1vxkg1xBq_Yhg_Sk9AOzdZsPrX2oOlxy-PLTF0
Flashing the 1.60.x.x firmware and restoring the 1.60.x.x twrp backup will put your device in a stock condition that will allow you to receive official updates from HTC.
Cheers
P.S. let us know if you need help restoring the backup or flashing the firmware.
shirreer said:
You can't just flash any file you please. RUU & firmware you want to flash MUST be specific for your device's region and variant model - in your case, you must flash ASIA-HK-CHT firmware & software. ATT & CINGULAR are US specific, and will not flash on your phone without modifications.
Instead, download the 1.60.x.x from the link provided by @Jerrel7, and the TWRP stock backup from 1.60.708.x provided below:
https://mega.co.nz/#!e8AFCCQZ!2-2Lx1vxkg1xBq_Yhg_Sk9AOzdZsPrX2oOlxy-PLTF0
Flashing the 1.60.x.x firmware and restoring the 1.60.x.x twrp backup will put your device in a stock condition that will allow you to receive official updates from HTC.
Cheers
P.S. let us know if you need help restoring the backup or flashing the firmware.
Click to expand...
Click to collapse
Sir i'm going to try it .. but unfortunately i don't know the way to flashing firmware and install twrp or recovery ! i'm always got unknown error like in Fastboot i don't Device offline ... daemon not running - something like that .. ! so please i need step by step what i have to do first because it's my first time to do software
Thank you for your time
Hello. I had the same problem. Just solved it yesterday. The whole problem was in my MID. You have to change it for the RUU you want to install.
I was with MID for Singapore and i wanned to install European version. So i can't install the updates. After i changed the MID now i'm able to install every update.
Just follow this thread and you're done. Good luck, mate!
http://forum.xda-developers.com/showthread.php?t=2708581
Jared89 said:
Hello. I had the same problem. Just solved it yesterday. The whole problem was in my MID. You have to change it for the RUU you want to install.
I was with MID for Singapore and i wanned to install European version. So i can't install the updates. After i changed the MID now i'm able to install every update.
Just follow this thread and you're done. Good luck, mate!
http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
@Mike Smaan problem is a bit different from yours and he has a S-On device.
His problem is his device is running a Taiwan ROM on a Hong Kong variant device.
He needs to run a Hong Kong ROM to solve his problem and the right ROM version (4.18.708.12)
then he can OTA to the latest Marshmallow 6.16.708.1
Should he followed the link provided by @Jerrel7 on post #11, he should be able to fix his problem as simple as ABC.
Mike Smaan said:
Sir i'm going to try it .. but unfortunately i don't know the way to flashing firmware and install twrp or recovery ! i'm always got unknown error like in Fastboot i don't Device offline ... daemon not running - something like that .. ! so please i need step by step what i have to do first because it's my first time to do software
Thank you for your time
Click to expand...
Click to collapse
Very well. Assuming you downloaded the twrp backup and stock firmware from my previous post, proceed as follows:
1. Download HTC Sync from the link below:
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
If you already have HTC Sync installed, then upgrade it to the latest version. Otherwise, install the one from the link provided.
Reboot your PC.
2. Download the FASTBOOT PACKAGE from the link below:
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Extract the file to "c:\fastboot" folder.
3. Download twrp 2.7.0.2 from:
https://dl.twrp.me/m8/
Extract the file to "c:\fastboot" folder.
4. Put the 1.60.708.x firmware zip you downloaded from my previous post into the "c:\fastboot" folder but don't extract it.
Summary:
You should now have:
A. the latest HTC SYNC installed.
B. A folder called fastboot in the root directory of your C:\ drive.
C. Your fastboot folder has the following files:
I. twrp 2.7.0.2.img
II. The zip file for 1.60.x.x firmware
III. htc _fastboot.exe
Let me know when you're done.
shirreer said:
Very well. Assuming you downloaded the twrp backup and stock firmware from my previous post, proceed as follows:
1. Download HTC Sync from the link below:
http://www.htc.com/uk/support/software/htc-sync-manager.aspx
If you already have HTC Sync installed, then upgrade it to the latest version. Otherwise, install the one from the link provided.
Reboot your PC.
2. Download the FASTBOOT PACKAGE from the link below:
https://drive.google.com/file/d/0B8L4pkbzdlR3eTlJSjdKVEdHX1U/view
Extract the file to "c:\fastboot" folder.
3. Download twrp 2.7.0.2 from:
https://dl.twrp.me/m8/
Extract the file to "c:\fastboot" folder.
4. Put the 1.60.708.x firmware zip you downloaded from my previous post into the "c:\fastboot" folder but don't extract it.
Summary:
You should now have:
A. the latest HTC SYNC installed.
B. A folder called fastboot in the root directory of your C:\ drive.
C. Your fastboot folder has the following files:
I. twrp 2.7.0.2.img
II. The zip file for 1.60.x.x firmware
III. htc _fastboot.exe
Let me know when you're done.
Click to expand...
Click to collapse
I did all that but what do you mean about the zip file for 1.60.xx firmware .. do you mean M8_1.60.708.2.zip ?
And tell me the next step
Mike Smaan said:
I did all that but what do you mean about the zip file for 1.60.xx firmware .. do you mean M8_1.60.708.2.zip ?
And tell me the next step
Click to expand...
Click to collapse
Yes, I did mean M8_1.60.708.2.zip
Now, buckle up...
There are 4 easy steps to accomplish the task:
1. Flash twrp custom recovery. 2. Restore the twrp backup. 3. Flash the stock firmware. 4. Profit.
Let's get down to business:
1. Flash twrp custom recovery:
A. Boot your phone into fastboot. You do this by turning your phone off, then hold Vol- and power button. You're presented with a menu, choose fastboot (navigate the menu using vol+ and vol-) and press power to select.
B. connect your phone to your PC. Open a cmd window:
Type:
cd c:\fastboot
fastboot flash recovery twrp-2.7.0.2-m8.img
Flashing will take a few seconds, when its done, type:
fastboot erase cache
Now, on your phone, select "hboot", then "recovery", to boot into twrp.
2. Restore the twrp backup:
Unfortunately, twrp doesn't immediately create the directory structure for where you'll put the backup file you downloaded. So, we're going to start by creating a backup of your current ROM:
A. Select Backup button in twrp. Select "external sdcard" from the menu at the top, and proceed to create the backup.
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
E. Select fastboot.
3. Flash the stock firmware:
A. On your PC's cmd window, type:
fastboot oem rebootRUU
B. WAIT UNTIL your phone displays black screen with HTC in white, then type:
fastboot flash firmware M8_1.60.708.2.zip
C. Once more, type:
fastboot flash firmware M8_1.60.708.2.zip
D. Reboot by Typing:
fastboot reboot
4Profit.
shirreer said:
Yes, I did mean M8_1.60.708.2.zip
Now, buckle up...
There are 4 easy steps to accomplish the task:
1. Flash twrp custom recovery. 2. Restore the twrp backup. 3. Flash the stock firmware. 4. Profit.
Let's get down to business:
1. Flash twrp custom recovery:
A. Boot your phone into fastboot. You do this by turning your phone off, then hold Vol- and power button. You're presented with a menu, choose fastboot (navigate the menu using vol+ and vol-) and press power to select.
B. connect your phone to your PC. Open a cmd window:
Type:
cd c:\fastboot
fastboot flash recovery twrp-2.7.0.2-m8.img
Flashing will take a few seconds, when its done, type:
fastboot erase cache
Now, on your phone, select "hboot", then "recovery", to boot into twrp.
2. Restore the twrp backup:
Unfortunately, twrp doesn't immediately create the directory structure for where you'll put the backup file you downloaded. So, we're going to start by creating a backup of your current ROM:
A. Select Backup button in twrp. Select "external sdcard" from the menu at the top, and proceed to create the backup.
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
E. Select fastboot.
3. Flash the stock firmware:
A. On your PC's cmd window, type:
fastboot oem rebootRUU
B. WAIT UNTIL your phone displays black screen with HTC in white, then type:
fastboot flash firmware M8_1.60.708.2.zip
C. Once more, type:
fastboot flash firmware M8_1.60.708.2.zip
D. Reboot by Typing:
fastboot reboot
4Profit.
Click to expand...
Click to collapse
I did all steps and i got backup ! but unfortunately when i wrote fastboot flash firmware M8_1.60.708.2.zip i got error called " error : cannot open ' M8_1.60.708.2.zip '
Should i try it with that way :-
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
Mike Smaan said:
I did all steps and i got backup ! but unfortunately when i wrote fastboot flash firmware M8_1.60.708.2.zip i got error called " error : cannot open ' M8_1.60.708.2.zip '
Click to expand...
Click to collapse
I know that you ignored my previous posts and other people post who tried to help you with proper method .. but I still pity you and I don't want to see you'll end up in a brick or soft brick due to wrong commands/instructions.
You get error when flashing firmware - reasons :
1. That command given to you to flash firmware - fastboot flash firmware M8_1.60.708.2.zip - is wrong.
The right command is fastboot flash zip M8_1.60.708.2.zip
Running a wrong command may brick your device but you are lucky because your device is S-On, so no harm just error.
2. Being a S-On device, you won't be able to install a very low version firmware 1.60.708.2 when your current one is 4.18.708.12
Only S-Off device can do that. To have S-Off you need to spend USD25 for the app .. and are you willing to spend USD25 to S-Off when you can fix your problem with proper method free of charge and needs only 2 main steps : ?
1. Restore 4.18.708.12 TWRP backup
2. Install 4.18.708.12 stock recovery.img
then you can update to the latest - 6.16.708.1
Mike Smaan said:
Should i try it with that way :-
B. On your computer, extract the twrp backup file you downloaded, and copy the extracted directory to your phone's sd card. Put it in:
/sdcard/twrp/backups/"serial number"/
C. On your phone, tap restore, and choose the backup directory you just copied to your sdcard. Proceed to restore.
D. Choose to restart your phone and select Bootloader.
Click to expand...
Click to collapse
You can try these B., C., and D.
But, again using a very low version 1.60.708.2 backup on a Lollipop firmware 4.18.708.12, you may have one of these :
1. It will be successful updates but you need to do many OTAs
1.60.708.2 --> 2.11.708.2 --> 3.32.708.4 --> 4.18.708.12 --> 6.16.708.1
If it is successful then it's good but if it is not, you'll get below.
2. You may have a blank screen either between OTA 1.60.708.2 --> 2.11.708.2 or OTA 2.11.708.2 --> 3.32.708.4
3. You may lost your wifi connectivity either between OTA 1.60.708.2 --> 2.11.708.2 or OTA 2.11.708.2 --> 3.32.708.4 but you can proceed further with your mobile data or use a Internet Pass through on your PC
One last note ... never use a 2.7.0.2 TWRP recovery as that is the most buggiest TWRP which will remove your OS version on your bootloader.
Good luck.
The title should be "with s-on"
Hello. I have been searching for awhile. I have Sprint variant, sim-unlocked, running a clean de-odexed rom I found here. But I am looking to run a rom even closer to stock us unlocked version, without having to s-off and change CID. Is there any way to do it, and hopefully be able to recieve OTA's? I have tried extracting the rom.zip from a RUU, but it is filled with more zips, non of them containing the usual files (rom.img, modem, etc..). I know I have to keep my radio.img. Thats why there is no sense in paying to s-off.
Sorry my previous advice has not gotten you where you need to be. I have tried to go through the process again so as to not leave anything out this time. You indicate you wish to be able to take OTA's. I don't think you will ever be able to do that while you are S-On as you will need to change your CID and MID to take the OTA. You can't do that while S-On.
Here are your steps:
1. A new US Unlocked RUU was released this week. It included a new aboot. Therefore, this rom MAY not boot on an older aboot. To have the highest chance of it booting be sure you have at some point in time run the most recent Sprint RUU or taken all available Sprint OTA's so that your firmware is as upgraded as you can get while S-On.
2. Unlock or reunlock your sim if needed. If you run the official RUU in step 1 you will need to complete this step. Some of my previous replies have talked about backing up radio, modemst1, and modemst2. However since you are S-On you will not be able to flash the backups so this is unnecessary.
3. Download the most recent RUU.EXE for US Unlocked. It is available in that [stock] thread by @Kisakuku and was posted yesterday. It may also be available on the official htc download page. I know I pointed you to the .zip file last time but this time get the .exe.
4.Download the RUU decrypt tool here: https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
5. Extract the tool and place the RUU you downloaded in step 3 in the folder. For simplicity rename that long RUU name to something shorter like ruu.exe
6. Open a command window and navigate to the folder where the decrypt tool and the ruu.exe are stored
7. At the command prompt type: ruu_decrypt_tool ruu.exe
8. A few minutes later you will have a folder called OUT_2PS[version]
9. Under that folder will be three subfolders - firmware, romzip, and system. Under system folder will be boot.img and system.img. Copy these files to your sd card - either internal or external.
10. Install twrp if not already done
11. In twrp flash boot.img then system.img and reboot. I don't have twrp installed right now as I currently have stock recovery so I can't tell you exactly where but there is a checkbox to install an image instead of a zip.
12. If this most updated rom will not boot on the older sprint aboot, download an older RUU and try again.
Again, apologize for the bad advice earlier - that zip I pointed you to was in a different format than the one I used when I initially did this.
To stay up to date just download the new RUU exe anytime another one comes along, run the decrypt tool on it and flash the 2 files mentioned.
Flashing boot and system should not affect your simlock.
Thanks again. I will try it that way. I wanted to see if more people outsinde the sprint variant had success in doing what I want. Ill try it this way now.