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.
friends would you help me my htc one m8 it stuck of a htc logo with 4 error signs and wont work .i attached pictures of the error and the bootloader
Was it you trying to update the firmware ? Reinstall firmware.zip again to fix that.
Or .. run the official RUU from here : http://www.htc.com/us/support/htc-one-m8-att/news/
(one thing to note : there is no need to relock bootloader to do anything when your device is S-Off)
how to do that my friend iam a nowbie in these thing also i dont want an at&t thing also for your notice i dont have a recovery in it , its simply empty
You just need to install that AT&T RUU to bring it back to life.
Once it is working normally, you can install other ROM on it.
What you need is a Windows PC with USB 2.0
Latest HTC USB drivers installed on PC. Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Download the RUU that I gave link earlier.
Connect to PC
Right click the RUU exe and select run as Administrator and follow the intructions
my friend do you have a youtube link showing how to do all this
No ... no idea as I never rely anything on youtube.
What I gave you, you don't need youtube.
Just download and install those three items.
1. ADB/Fastboot - when you install, it asks to install adb/fastboot, type Y
then it asks to make it system wide - type Y
then it ask to install drivers - type N
2. Install the HTC Sync Manager as it will install the drivers. Once completed, uninstall HTC Sync Manager but leave all other things
3. The RUU.exe, right click on it and in select run as administrator then follow the pop-up instructions accept - next - next - blablabla until it says completed.
Most important your PC must have USB 2.0
i did what you said but then i get this error
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
it says on the bootloader
I was away due to not feeling well (down with high fever .. still recovering ..)
Your problem here is mainly wrong MID... your current MID is 0P6B17000 (which I believe is the GPE MID)
To run the RUU, the MID must change to 0P6B12000
Can you unlock the bootloader again ? If not .. I give to give you other alternative.
ckpv5 said:
I was away due to not feeling well (down with high fever .. still recovering ..)
Your problem here is mainly wrong MID... your current MID is 0P6B17000 (which I believe is the GPE MID)
To run the RUU, the MID must change to 0P6B12000
Can you unlock the bootloader again ? If not .. I give to give you other alternative.
Click to expand...
Click to collapse
Yeah my friend i realized this and install the gpe ruu and its now working fine with 6 thanks alot hope you feel much better
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Markieboy said:
Hi all,Any help will be greatly received,
my stock 10 started having random lock ups,freezes and reboots ,
it has now even decided to give itself a factory reset on its own WTF?
so i thought software has gone corrupt, so ive downloaded the correct firmware and put it on the sd,when i boot into download
mode from bootloader it says sd not mounted?? tried formatting sd card to fat 32 and ntfs.
it also has lost its recovery as just get the red exclamation icon,
and because it factory reset itself without me entering my pin google has set the 24hrs timer so i cant even get further than the google sign in page to root it and flash it that way...
please help
cheers
Click to expand...
Click to collapse
Have you checked your Google account on a PC or other device ? check all is well there first
Lol flash twrp and install any rom.
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
diagonals said:
if you are ok with losing all your data you can use a RUU to restore the system from your current state.
1. download this: https://androidfilehost.com/?fid=24671318762849095
2. rename the zip file to 2PS6IMG.zip
3. put it on your SD card and put it in your phone.
4. boot into download mode, it will recognise the zip and begin the ruu process.
5. once it's finished it will reboot; it might take a little longer than usual to boot but just wait about 5min or so.
done.
at a guess i'd say that if it doesn't work or it happens again then your board is probably cooked and you should start looking for a new phone...
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
also when booting into stock recovery the red exclamation mark screen is normal; what you have to do is hold down the power button and press vol up and the recovery menu should appear.
Click to expand...
Click to collapse
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hello, i have exactly the same issue battery health is like 65 percent when i look at accubattery and it crashes often wen battery is lower than 25% or so. It closes and never opens. Enters a boot loop. Sometimes it shuts down and enters boot loop too. Here is information that i see at download mode :
hTC download mode
*** LOCKED ***
htc_pmeuhl PVT S-ON
LK-1.0.0.0000
RADIO - [email protected]
OpenDSP - v.20.0.8996.00007_0809
OS-2.41.401.41
Aug 2 2017, 12:18:15(857212)
system info
show barcode
bla bla
Security checking falied GT_CONNECT_FAI
L
Security Warning
if you flash this phone with any rom bla bla
SD Mounted
OTG NOT MOUNTED
File NOT FOUND
xunholyx said:
Are you sure this is the proper RUU for him? First of all, that RUU is super old. Probably too old for the OP to use unless he's S-Off (you can't go backwards with firmware while S-On)
Second of all, you don't even know which model he has. That RUU is for WWE/European. It won't work on US Unlocked/Sprint/Verizon/o2/T-mo etc...... but ONLY on a WWE branded device. You need matching MID and CID for the RUUs to work.
@Markieboy don't use that RUU. Boot to download mode and post here what it says next to "OS" and I or someone else can provide you with the appropriate one to use (although I'm not sure if it will work in this case).
Try this: If you can boot to download mode, you should be able to flash TWRP via fastboot (your bootloader is unlocked, correct?).
Then boot to TWRP > advanced > file manager then navigate to /data/system/ and delete the locksettings.db file. This will disable your lockscreen PIN/password.
Click to expand...
Click to collapse
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
i'd say pay for the s-off, there's no other way to fix your phone. but i still think your board is cooked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Sorry for taking so long to respond. This is the RUU.zip you should use. You can follow the instructions a few posts back, just use this download instead of the one linked.
Markieboy said:
Hi no unfortunately the phone is bog standard I haven't unlocked the bootloader or anything. It's a non branded wwe firmware version....
Click to expand...
Click to collapse
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
Are you saying they replaced those? on the house? I'm
Markieboy said:
Many thanks... Things have been resolved now,, the missus took it into carphonewarehouse, and they said because it's a software issue it'll be repaired free! Phones about a year old...
Well it came back with the repair report...
NEW MAIN BOARD firred
NEW USB C PORT fitted
NEW BATTERY fitted
wow.. Don't mind if I do.. Lol
Click to expand...
Click to collapse
The question is, what were doing on that phone to cook all these? Mining Bitcoin?