Database Info

[Q] HTC Desire Bricked?

I recently tried (foolishly) to do an OTA update from Eclair to Froyo on my rooted Desire and suddenly my device is stuck in a reboot cycle. I do have access to the stock recovery mode and fastboot seems to be working properly. I rooted using unrevoked3 and I don't know if it give me access to any custom recovery tools. I also do not have a goldcard, and as I understand it, I can't make one since I can't get adb up and running.
I have tried pretty much everything I can find that applies to my device, which isn't much since I seem to have some odd bootloader/radio specs which make all the ROMs and RUUs I can find not work. When I boot into fastboot or hboot, my device lists these specs:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-WYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
I can get to the recovery tool and try running update.zip, but I have only found one which gets past signature verification and then errors with a Status 2. I have also tried running the WWE RUUs from: http://forum.xda-developers.com/showthread.php?t=695667 which will run once I give the device the "fastboot oem rebootRUU" command, but they all fail with a code 130 which means the device doesn't match. Also, the RUUs are all for a 1.1x or 1.2x revision and the loader says I have the 2.25.661.2 when it goes though the "are you sure" messages.
Is there anything else I can do to get this back up and running?
edit: An additional note, I have the SLCD screen which I know causes a bunch of issues since it uses a different driver than the AMOLED one and many of the ROMS, RUUs, etc. don't support it.

Hi tahosa,
I am suffering from the same issue but wondring if the Volume -/+ is working in your case or not, another observation that on the "SHIP S-ON" is this mean anything in locking or security issue?
my device gives :
BRAVO PVT3 S-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.09.00.08
Jan 10 2010, 12:12:05
thanks, and I am also doing some research till find solution.... :s

Volume +/-
My volume buttons are working fine. I can navigate through all of the HBOOT and fastboot menus and get to the stock recovery menus. Any information you have would be awesome. I have been bashing my head against this problem for a couple weeks now and gotten nowhere.

Please try to check this link :
http://forum.xda-developers.com/showthread.php?p=7618995
In my case the volume is not worked :s

No change
Nope, the only image I could find linked from there fails with the same error as the RUU. I think it is mainly to do with the fact that my HBOOT version is higher than what everyone else seems to have.
When the image gets loaded during the HBOOT, it verifies just fine, but when it tries to run the device check, it errors with "Model ID incorrect!"

Fixed: Process
EDIT: I don't know how I overlooked this for so long, but since I did my root using unrevok3d I got clockworkmod recovery and a backup of my old image, which is probably why this method worked for me. These instructions may still hold if you are stock, but no guarantees.
I was able to fix my Desire using the following method:
You first need to identify which version of the software you device has using the HTC reflash tools. To do this, boot your device into FASTBOOT and connect it to USB. Start the fastboot tool and reboot it into the OEM RUU mode using "./fastboot oem rebootRUU". This brings you to the OEM reflash mode and you can run any of the available RUU tools from this page: http://forum.xda-developers.com/showthread.php?t=695667. When you run them, they give you the version of the software on the device as well as what they are trying to overwrite with. Write down your software version if the first two groups don't match since you will most likely need a different version. From here, you can try running the update but it may fail. If it doesn't you should be all set.
If you can, find another one of the RUUs on the xda-developer page which matches your software version. Most of those link back to the shipped-roms page, but if you don't see yours on that list, look at http://www.shipped-roms.com/shipped/Bravo/ for the full list of Desire ROMs and RUUs. Mine happened to be the TELUS_WWE_2.25.661, which is a zip file. If the matching file is an exe, you have the HTC install tool, and can use the instructions above to flash it. If not, rename the .zip to update.zip and put it on your SD card and boot into HBOOT.
From HBOOT, choose recovery, and when you get to the black screen with the red error message press VOL-UP and POWER to get to the options and choose "Apply update.zip from SD Card." If everything matches, it will apply the update, and you should be able to boot up into a stock (or somewhat stock, mine was rooted) ROM for the Desire.
Let me know if this is confusing and I will rewrite it to be easier to follow.

[Resolved] [Q] How to unroot and turn s-on on HTC Incredible S?

Hi to all, i'm jauffre and i'm new in XDA. I have a problem and, as i searched all the forum without finding an answer, i need your help.
Last week i rooted my htc incredible s using the revolutionary tool, wich upgraded the hboot to 6.13.1002. i installed with the clockwork mod recovery tool a modded rom, and it was great. but sunday my phone crashed to the ground, and now the cover is broken (so i need to send it to the warranty).
i spent last day searching a guide for dummies to unroot the phone, and using the signed RUU (downloaded from this site) it appeared to work, but my htc is still s-off.
now, i know i need to downgrade the hboot, and i tried everything (i reinstalled froyo, updated the radio and then updgraded to 2.3.3), but this is still a problem.
please, help me!
Hey guys, this is the procedure i did to solve my problem. do it at your own risk.
first of all i must say that with this process i'll have the hboot back, but NOT the bootloader (so when you hold "volume back+power on" you will see the modded bootloader, not the stock one). i don't know how did you rooted your phone, what programs did you use, and i cannot assure you this procedure will work. if you're not sure, don't do anything.
first, you have to look for the original RUU of your phone (you can find it on this site). then follow this thread to find the rom.zip file (http://forum.xda-developers.com/showthread.php?t=790022), where you can find several files. you need the android-info.txt and the hboot_xxx.img files.
open the hboot.img file with a text editor; in the first line you can find many strange symbols, and after that there will be a string of numbers (that is the hboot version).
you have to know what version of hboot have you currently on your phone (if you used the revolutionary tool, it will be probably 6.13.1002) and simply change the hboot.img string so that the release number is higher (than the modded hboot; i.e. you can write 7.09.0000).
after that you have to make a zip file with the android-info.txt and the hboot_xxx.img file you have just modified, and if you have an incredible s, call it "pg32img.zip".
if you have another device, simply you can turn on your phone in the bootloader mode, and if there's a memory card the device will look for a file, which name appears (it's the code you need).
then put that pg32img.zip file on the root of your sd card, reboot in bootloader mode (volume down+power) and follow the instructions to do the upgrade. after that, if you restart in bootloader, you'll see that the hboot version will be 7.09.0000 (the same you wrote) and will be s-on.
now, search and download the latest version of "superoneclick" (an application that should root and unroot your phone), and start it. link your phone to the pc and start the unroot process.
when it is done, simply leave your phone linked to the pc and start the RUU.exe file you downloaded. start the update process and if you have done everything good, at the end you'll have your phone with the stock hboot and the s-on.
i'm not a serious programmer, i simply was really lucky (i really didn't know if that could have worked) but i did it. i don't know how did you do the root, and how does the superoneclick work, so i am not responsible for any bricked phone.
if you are not sure, simply send your device to the htc assistance (better pay than have a new paperweight).
good luck

download superoneclick select unroot and uninstall the superuser app.Oh and download and flash your phone's stock rom

ok, thank you for the help!
there's a little problem: at the end of the superone process it says me "superuser not found", so it can't be deleted.
so i remade the root (using superone) and unrooted; then installed the RUU, but nothing: it's still s-off. what can i do now?

i tried to make superoneclick work, but with no success... although i have installed the superuser.apk, the program still says me there's no SU, and can't unroot my device.
Any suggestions?

ok guys, i did it...
first i remade the root process, and flashed the superuser.apk. then i wanted to "upgrade" the hboot, from 6.13.1002 (revolutionary) to 7.13.0000 (simply i changed the 1 to 7 opening the hboot signed image with a text editor). then i launched superoneclick, and started the unroot process. at the end, i launched the signed htc RUU with gingerbread, and now i have my htc incredible s with s-on and hboot 1.13.0000.
=)
the last thing: does someone know hot to put the original htc bootloader?

cant someone build a uniform high performance rom

i added a guide to do the process go to the first post and read it all

thanks for the guide, just one confusion here, that after putting the pd****.img into the sdcard, i need to goto bootloader right? (not recovery)
Edit: worked in first attempt . Just one suggestion if you can replace word "Recovery" with "Bootloader" inorder to avoid confusion for other users

thank you fshami! i just corrected the guide

Hi I just tried following the guide posted on the first post using the android-info.txt and the hboot_xxx.img files received by the OTA update released recently as well as one downloaded from the net "OTA_Vivo_Gingerbread_S_hTC_Asia_India_2.12.720.5-1.36.720.1_release_190041sn70bk4icw74exvv"
On both occasions the bootloader update failed.
I am unable to install the OTA update. This has been downloaded quite a few times already and the phone just hangs with the android logo screen.
P.S. My phone is an Incredible S purchased legally in India around June 2011.
Thanks.

then put that pg32img.zip file on the root of your sd card, reboot in bootloader mode (volume down+power) and follow the instructions to do the upgrade. after that, if you restart in bootloader, you'll see that the hboot version will be 7.09.0000 (the same you wrote) and will be s-on.
Sorry my friend , but this don´t work....
Sorry.....

I thought this is what I was searchinf for years but...What if I have an USB issue? Like usb brick? So I cant connect my htc with the pc x.x for superoneclick

So what do I do now?

firstly, Im not asking for a detailed explanation of what to do here.. I can read up on various sections, but I do need steps to follow. This phone is the most complicated thing to flash, give me ODIN and a galaxy S any day.
Im trying to upgrade to the latet open Europe.HTC-SAGA 401_9 not a custom rom, my DS is the same Radio Version so thats ok.
After following the various guides, What I have so far is:
1) the Stock HTC 401_9 Rom from File Factory.
2) Ive downloaded Goldcard Helper, fitted my 2GB SD and gotten the reverse ID
3) Ive d/l'd the GoldCard Image for my DS reverse ID
4) Ive d/l'd the HexD editor for making the goldcard.
5) I know about having FastBoot OFF, USB debugging ON and the phone USB set to Disk Mode for making the Goldcard and the USB to "Charge only" when flashing.
So, now what. Can I just flash the HTC Stock 401, or do I root it first. My Hboot is 2.000.002 and its S-ON.
The phone has Virgin UK Software, but its not Locked.. Ive had both O2 and Orange sim cards in and they work fine.
I just need to know the 1, 2, 3 .. steps for flashing this stock rom
Thanks in advance

Always helps to write your full bootloader screen.

ben_pyett said:
Always helps to write your full bootloader screen.
Click to expand...
Click to collapse
Im all for protecting your product against time wasting "bricked" returns, but Whoever at HTC thought of this system wants slapped... hard, Bootloader says:
### Locked ###
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822. 10. 08. 04_M
eMMC-boot
Aug 22 2011, 15:22:11
HBOOT
Then it lists on screen:
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Hope that helps and hope you can give some steps. Seriously, Ive looked on here for days but there seems to be so many questions about different aspects and parts of the flashing, its confusing.
Thanks in advance

First of all, forget all about radios you know from Samsung.
At htc you can use every radio on every rom, there are only 3 possibilities you need to change radio:
It is shipped with a ruu you want to use
You face issues with radio related hardware
You want to be up to date
Ok, now to your question.
At HTC the bootloader version is important (only at stock roms).
If your bootloader has the same or a smaller version than the one from the ruu and your device had no branding, just reboot to bootloader plug it to your pc, enable fastboot usb and start the ruu.
If a branding is present and you want to stay with it, do the same with the fitting ruu.
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).

Tectas said:
If your version is higher or you want to remove a branding , you need a goldcard first and maybe the extracted rom.zip from the ruu, if the ruu fails with goldcard only, because you need to put it at the root of your sd renamed to PG88IMG.zip and flash it directly with your bootloader.
(also to change misc_version can be needed, but i guess not here because you don't want to downgrade)
For both cases are guides at the index (see my or bens signature).
Click to expand...
Click to collapse
Ok I used this guide for the goldcard:
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
So, because Im not changing anything about the kernel, just debranding to an offical ROM, once I set up my Goldcard, I activate debugging, copy the RUU 401_9 to SD Root of my Goldcard, click "Image CRC" from bootloader menu and it should install it.
Is that correct?.

Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?

NightOrchid said:
Ive just checked..
Wait and It detects the new ROM "update" automatically in bootloader menu
Yes?
Click to expand...
Click to collapse
Image crc just checks your rom, got nothing to do with updating.
The ruu itself is a exe, means a windows program , do the steps i described before with fastboot, the only difference is that you need to create the goldcard before, otherwise the bootloader won't allow (if your lucky) you to flash the ruu with the different branding.
If it fails that way run the ruu without attached device as far as you can go without closing, don't close it and search for the rom.zip at your temp folder, copy it to another folder and close the ruu, rename it, copy it to the root of your sd and reboot to bootloader and let it flash it directly, just to say it, you also need a goldcard before you do it this way.
One additional thing, be sure you got a ruu for the desire s, i just say it, because your goldcard guide is for the desire, what is no real problem there, but a wrong ruu will always fail and if it won't lead to a brick at worst case.

Sorry Tectas.. Just wont work.. I created my goldcard, extracted the RUU, changed the rom name from "disk1" to PG88IMG as you said, copied to root of goldcard, selected Fastboot then bootloader, but it just doesnt detect any image or file.
I am struggling a little with your english because you are telling me too many different ideas, Im confused... instead of telling me.. just 1, then do 2, then do.. 3, but Thank you for trying, i appreciate your help..
I will try again later..

Small thing the file you copy to the sd card must be called (case sensitive) PG88IMG.zip
Swyped form ym Dersie S unsig XAD Permuim

First method:
1. Create goldcard
2. plug in your device
3. Reboot to bootloader and enable fastboot
4. Start the ruu at your desktop and follow the instructions
5. Enjoy
If it fails make sure the drivers are installed, by downloading and installing htc sync, but uninstall it straight after you installed it, the drivers will still be present but the program itself can cause problems with ruus and/or adb.
If it still fails, try the second method.
Second method:
1. Create goldcard
2. Start the ruu without attached device
3. Go on till the only remaining possibility is to close the program, but don't close it
4. hit the windows button + r, a window should pop up
5. Type %TEMP% into the textbox of this window and hit enter, the explorer should open up and show your temporary folder
6. Search for the rom.zip (make sure hidden files are down if you can't find it)
7. Copy it to another folder i.e. the desktop
8. Close the ruu
9. Rename the rom.zip to PG88IMG.zip (case sensitive)
10. Copy it to the root of your sd
11. Reboot to bootloader
12. Choose bootloader
13. Confirm the update with vol +
14. Let it update
15. Reboot by hitting power
16. remove the PG88IMG.zip, otherwise it will update your device every time you access the bootloader
17. Enjoy

Thank you very much tectas for taking the time to sort and explain this. The 2nd methord worked just fine. However, at the end of the update flash, bootloader said:
"image on device is newer, update aborted"..
It does say that my virgin software is 2.13.351... the image is 2.10.401, so, in computer world, the numbers 2.13 is newer than 2.10. This may not be the case of the ROM itself, becasue the date is 22 Aug 11, but theyve engineered it that way probably so you cant flash it Open Europe.
The great thing is, youve taught me about the desire s and how the flash updater works, plus I have a 2GB goldcard out of it for future custom roms.. so all is not lost.. thanks for the lesson, its much appreciated.. Im gonna have a go at routing next.
It would be great to sticky this or copy it as a very Basic guide to flashing an HTC Rom.
Many Thanks again Tectas

This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.

I have now found that my phone is actually Locked to Virgin Mobile (has a Virgin media splash screen on boot up). Sorry for the confusion about that:
I followed the advice of Tectas and followed this:
http://forum.xda-developers.com/showthread.php?t=1399331
everything went great until I got to the end of the procedure and I only go the
"$" which after typing line 5: adb shell /data/local/tmp/misc_version -s
said "access denied" then mentioned "blue flames".
On page 6 or 7 of that thread, someone mentions this "blue flames" as being a new security mod that HTC have implemented to stop modding at all.
Is this true?.
Also, Virgin mobile and other places have quoted me £15 to unlock my DS. £15 seems alot of money, but would an unlock help (would it be worth it) for me being able to flash both Stock and custom ROMS.
I do enjoy the challenges of modding, so to me this is frustrating.
cheers

The $ indicates you have no root access, i must confess i never heard about the blue flame before, but also have to say, i never got deep into the downgrade stuff, because i used xtc clip to unlock my device, which made my device s-off and debranded.
If those Sellers use the same method, your good to go and spend the money, it saves you from a few traps you can run into with other methods (i paid €20 about a year ago), but you need to be aware that this is a hardware unlock which is irreversible, what can bring problems at warranty purpose (but must not).
Your second choice would be to use htcdev at first step and get root and so on afterwards, the downside here is also warranty, because your device is stated as unlocked at the htc database and if you leave it this way and won't use it to gain full s-off you also need to flash the kernel for each new ROM yourself with fastboot, because the recovery got no write permissions there.
If the seller would also use htcdev, safe the money, you can do it yourself, at xtc i can recommend it, but it's your choice.

Thanks for the advice Tectas. The guy in the street said it would take about 1 hour.. not sure if that helps to know. I suppose with Virgin, theyll be removing their own locks, so the virgin way might be better.
Also, the phone was bought from a 2nd hand shop, it was an unwanted upgrade someone just traded in without using it, the box it came in and the outer shell of the phone has no branding whatsoever.. thats why i was confused about it being locked.
Anyway, Ill have a think about who to go with and ill ask which methord they use before I hand it over.
Thanks again.

Tectas said:
This can also be solved, you need to change the misc_version for it as first step and afterwards do the same as this time.
About customs, you need to unlock or s-off your bootloader first.
For all three things are guides in the index thread.
Click to expand...
Click to collapse
Its Done.. phew.. hehe. After I got back to Virgin 1.31, just used the goldcard with rom.zip and it worked fine. 1 thing though, doing it this way flashes the rom in 7 stages, so what ever you do, when it reboots after the 1st install, do not think its repeating itself.. leave it. i Nearly did that, anyway, I sorted things using this thread:
http://forum.xda-developers.com/showthread.php?t=1443636
As long as you follow it to the letter, it all goes fine, the whole thread is really good support as well, so if anyones interested, read through the whole 13 pages (so far).
Also had access to the phones Recovery menu, so wiped Cach partition and did a factory reset, also probably not necessary, but backed up my SD card and formated it under the new OS.. I find this is always good on a new rom, for the file table and prevents app errors.
Happy i now know how to flash a rom, didnt quite root it yet, just flashed a stock RUU first.. which is what you should do if, like me, your new to this.
Anyway, Open Eu 2.10.401.9 is sweet and slick smooth.
Have a good one all, Thanks Tectas.

[Solved] Corrupted mid and serialno

Help, I need some [body] help! (sung to the Beatles song "Help")
Here are the symptoms:
Flashing PG88IMG file that I've used before now says "Model ID incorrect"
The serial number is now some corrupted text (see last bullet point)
If I install a ROM (I'm using CM9) after formatting all partitions (using 4EXT Touch) plus GAPPS, then Play comes up with a "Server Error". Also TB will not properly reload its settings. So I basically can't install new ROMs cleanly anymore.
ADB (with latest HTC drivers) cannot see my device. Yes, USB Debug is on.
Running 'cat /proc/cmdline' shows CID is TELST001, but some corruption in other fields. If I write it out to a file, the file is full of Chinese characters (using ES Text editor)
androidboot.batt_poweron=good_bat`#ry
androidboot.mid=uA}f
androidboot.serialno=].&_
androidboot.cid=TELST001
When did this all start?
I discovered that I could create a flashable zip file for the boot.img (looking at the updater-script for the ROM zip file.
I tried to do the same for recovery, but it - obviously - didn't work.
So I tried to copy the recovery file over the partition from the terminal emulator.
And that's where I think I screwed up.
What's working?
I'm currently running CM9 0611 with no problems. I can recover previous backups with no issues. I can update my recovery partition with no problems.
How can I get my phone back to normal?
What is it that I've screwed up?
All help will be most thankfully accepted.
Edit: Solution
The corrupted mid and serialno were the cause of all my problems. Once I'd fixed them, everything was back to normal
Things that I had to learn on the way
ADB, RUU, PG88IMG will not work if you have corrupted carrier id (cid), model id (mid) or serial number. Having a goldcard makes no difference.
A goldcard lets you flash PG88IMG files even if your cid is not in the android-info.txt file in the zip.
The simplest way to create a goldcard is this described here: http://forum.xda-developers.com/showpost.php?p=18748766&postcount=6
You can connect to ADB over WiFi. I needed this because my USB connection wouldn't work. Search for ADB Wifi in Google or Play. I used Wifi ADB. It worked like a charm. This allowed me to upgrade my hboot to an engineering version.
You need an engineering hboot (one that has the fastboot oem commands) to be able to set a serial number and model id. It took me a while to realise what the warning about it only working on an ENG hboot meant (see http://forum.xda-developers.com/showthread.php?t=1724475). I assumed that ENG meant English!
Set /Settings/Developer options/Root access to allow ADB to run su commands
To run fasboot commands you have to be in bootloader! It took me quite a while to realize this. I kept trying fastboot commands when phone had booted normally
How I fixed the problem
Installed ADB WiFi. I sourced it from http://androiddev.orkitra.com/downl...7663795511&download=com.ttxapps.wifiadb_v1.17 because I couldn't download apps from Play.
Connected to the phone using ADB over WiFi.
Flashed the engineering hboot (sourced from http://forum.xda-developers.com/showthread.php?t=1113820).
Rebooted into fastboot and executed the following commands:
fastboot oem writemid PG8810000
fastboot oem writeserialno xxxx (sourced from the number under the phone's battery)
Rebooted into Recovery and flashed a backed up ROM (I could have just wiped cache and dalvik)
Root Cause
I've finally discovered what caused the problem.
It was my writing to the recovery partition. I used this command:
dd if=<input file> of=</dev/block/mmcblk0p23
I got the information about partitions from http://forum.xda-developers.com/showthread.php?t=1545911, but those are for an HTC Amaze and, I now know, they are incorrect for a Desire S!
Just goes to show what a bit of knowledge and some ignorance can do. I have yet to come across an accurate and complete list of the partitions for the HTC Desire S.

Create goldcard, flash whichever PG88IMG you want.

Jack_R1 said:
Create goldcard, flash whichever PG88IMG you want.
Click to expand...
Click to collapse
Thanks, I'm looking into this. But that won't solve the issues I have with doing clean installs of new ROMs, will it?
Sent from my HTC Desire S using Tapatalk 2

Flashing RUU erases everything from the phone, replacing it with factory image.
It will solve everything but HW issues. Your issue doesn't look like one.

Right! I can see I've got a bit of work ahead of me. Thanks.
Sent from my HTC Desire S using Tapatalk 2

Jack_R1 said:
Create goldcard, flash whichever PG88IMG you want.
Click to expand...
Click to collapse
I used attn1's script to create the gold card, except that I ran it on my phone since I can't get ADB to work.
It seemed to work, but I still can't flash a PG88IMG - keep getting invalid id.
How can I tell if I have a gold card?
By the way, I started with an sdcard that already had files on it.
Sent from my HTC Desire S using Tapatalk 2

go here for my new guide on this issue http://forum.xda-developers.com/showthread.php?p=27713795#post27713795

htc-phones said:
go here for my new guide on this issue http://forum.xda-developers.com/showthread.php?p=27713795#post27713795
Click to expand...
Click to collapse
Thanks. I read your post, but I currently can't get ADB or fastboot on my PC to see my phone.
Is there a way of running the fastboot commands on the phone itself, just like you can run ADB?
Sent from my HTC Desire S using Tapatalk 2

Jack_R1 said:
Flashing RUU erases everything from the phone, replacing it with factory image.
It will solve everything but HW issues. Your issue doesn't look like one.
Click to expand...
Click to collapse
I downloaded an RUU, installed the HTC drivers (in HTC Sync from the HTC support web site), and ran RUU.
RUU gets an error 170 because it can't connect.
So, gold card doesn't work, RUU doesn't work, and ADB doesn't work.
Any other suggestions?
Sent from my HTC Desire S using Tapatalk 2

The only suggestion is - get one of them, or better all of them, to work. It's not rocket science, and there are zillions of guides how to make ADB work, and there are enough of them that show how to create a goldcard and how to flash RUU. If that proves to be too difficult for you - the next best advice is to leave your phone alone or to turn to paid phone service labs.

Wow! I agree it's not rocket science. The gold card process worked, but the phone still complains about an invalid id.
ADB installation worked just fine and I'm running the right drivers, but it can't see the device.
I've spent the last few days reading up on gold card and ADB installation.
I appreciate your help and suggestions as I hadn't come across gold cards before and hadn't thought of flashing RUU.
But let's please not make this personal and let's just stick to factual things.
Sent from my HTC Desire S using Tapatalk 2

It's not personal. But you've exhausted the possibilities of skipping things because they don't work for you - so the only thing that remains, is making one of the things you skipped actually work. Otherwise, I can't see how you can progress from the current situation.

Well, I finally managed to get things fixed again. I've updated the OP. Thanks for your nudging and help along the way.

Stuck in boot loop when trying to return to stock.

I'm stuck in a boot loop after trying to return to stock.
I followed precisely the instructions written by 5m4r7ph0n36uru in the section titled "Restore using a RUU".
On my BadBoyz unlocked rom where I was still on OS version 1.16.617.6 I did was flash with the latest full RUU version 2.42.617.7 then relocked my ROM with fastboot oem lock command.
I've tried clearing the cache and factory reset as instructed in HTC docs to try when stuck in boot loops. I can't get it to go past the boot screen.
Was I wrong to flash to the latest RUU I found in the spreadsheet section for my phone model? Should I have flashed with the RUU of the version I originally had on my phone to return to stock?
Any ideas would be greatly appreciated. Thanks in advanced.

I know that the OP had posted this about a week ago but I was wondering if you had your issue with the phone resolved? I found only when I used the SD card process to flash a RUU zip file I would be successful in flashing another OS/firmware. On my U11, I only was successful in first flashing a older version of the OS on to my phone before I was able to boot my phone up. On my U12+ I was successful in flashing the original (latest) OS. Good luck.
Sent from my coconut frond hut using Tapatalk

el80ne said:
I'm stuck in a boot loop after trying to return to stock.
I followed precisely the instructions written by 5m4r7ph0n36uru in the section titled "Restore using a RUU".
On my BadBoyz unlocked rom where I was still on OS version 1.16.617.6 I did was flash with the latest full RUU version 2.42.617.7 then relocked my ROM with fastboot oem lock command.
I've tried clearing the cache and factory reset as instructed in HTC docs to try when stuck in boot loops. I can't get it to go past the boot screen.
Was I wrong to flash to the latest RUU I found in the spreadsheet section for my phone model? Should I have flashed with the RUU of the version I originally had on my phone to return to stock?
Any ideas would be greatly appreciated. Thanks in advanced.
Click to expand...
Click to collapse
Hey mate can i ask did you boot the rom before locking the bootloader to see if the OS was functional ? Also how many times did you try flash the updated RUU before locking the bootloader,
Youve locked the bootloader down again anyway and will display as relocked in bootloader mode, youve made things a bit harder for yourself here,
Never ever relock the bootloader whilst the system is non functional keep it unlocked until you know the OS is ok, in general now youve locked it your device would usually require a very specific RUU full signed and exact main version match, however luckily for you if you havent already fixed it ive found a way to fix it without sending to HTC if you dont have the exact RUU needed to revive it,
What i want you to do is download the full RUU.zips for your model from the google spread sheet main version wont be an issue will be best to get all releveant RUUs with matching CID from there also
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Now download the HTC_10 batch tool and install it
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
After its installed, place your RUU.zip into your local drive "C://" as an example where your batch tool is installed place the RUUs 1 at a time into /android/com, no more than 1 at a time when flashing
Full length of where RUU needs to be put in simple termns is C://android/com
Now minimise to the desktop, then right click on the batch tool icon and run as administrator,
NOT the HTC FUU icon !
Once the batch tool has booted, press the number 3 on the keyboard and then enter, this will take you to the fastboot terminal,
Take note the screen should be purple and the location on the screen should be as follows C:// is only for example your drive letter may be different,
C://Android/com
Now boot the phone to download mode and connect to pc,
Now type the following,
Fastboot devices
If that didnt work type
htc_fastboot devices
Your device should display now with a serial number,
Now type
fastboot oem rebootRUU
If that didnt work type
htc_fastboot oem rebootRUU
Now type
fastboot flash zip example.zip
If that didnt work type
htc_fastboot flash zip example.zip
!!example is the name of your RUU if you dont want to type it out drag and drop from the minimised window in C://Android/com,
Now your device will start flashing the RUU to your device, in my experience this is the only fastboot terminal that will revive a dead htc in your case without the exact signed ruu it requires,
It will also let you rollback from oreo to nougat whereas any other fastboot terminal you use will give you RUU error Main version fail in info or RUU error zip from usb command,
Try this it will work if you need clearer instructions you can check my thread out, this is pretty much the same case but without the device saying corrupt either way you still have non functional OS and oem unlock will be off FRP lock will be enabled and you wont be able to unlock the bootlaoder again without a functional OS as the full RUUs wipe the device completely resseting everything
My thread link is here for more infomation if needed
https://forum.xda-developers.com/u11/help/fixed-htc-u11corruptrelockeds-t3855157
Thanks

Hey thanks for the reply! Actually I was able to get my phone back up and working again after having gleaned quite a bit of useful info from your very informative OP.
Fortunately I didn't have to go the route of running the HTC 10 batch tool, since I really wasn't looking forward to having to set up a virtual windows machine or having to trust a windows emulator like Wine just to run a dos batch tool. Actually I got the message pretty quick reading your first post that relocking the bootloader was a pretty terrible idea and set right away to unlocking it again. I was able to do it going through the HTC routine of cutting and pasting the ASCII key to HTC web form and having the Unlock_code.bin emailed to me again. It was different from the original ascii and unlock file they sent me the first time, but it did the trick.
It was smooth sailing from there, as I was able to boot to recovery and flash TWRP, which I then used to install the latest BadBoyz rom running Oreo and it just worked.
I was a little surprised, because I was under the impression I would have to apply all my OTAs manually since I was upgrading from Marshmellow. So even though I had a busted /system partition that wasn't letting me boot into the latest HTC RUU stock, that didn't seem to matter. Flashing with the latest RUU must hav the OTAs intact on a separate partition that the latest bad boyz rom just worked out of the box.
I'd been meeting to update this post, sorry to make you type all that out again when your first post was great. It tipped me off to scrutinize that HTC10 batch script line by line to see what was so special about it. Turns out, not a whole lot; I figured I could manage to do all that running the android bridge from my linux console just fine. But it was extraordinarily insightful in practically giving me a written line by line instruction set on how to recover my phone from command line. It was about as straightforward as it gets. I totally appreciate your help! :good:
Matty1993 said:
Hey mate can i ask did you boot the rom before locking the bootloader to see if the OS was functional ? Also how many times did you try flash the updated RUU before locking the bootloader,
Youve locked the bootloader down again anyway and will display as relocked in bootloader mode, youve made things a bit harder for yourself here,
Never ever relock the bootloader whilst the system is non functional keep it unlocked until you know the OS is ok, in general now youve locked it your device would usually require a very specific RUU full signed and exact main version match, however luckily for you if you havent already fixed it ive found a way to fix it without sending to HTC if you dont have the exact RUU needed to revive it,
What i want you to do is download the full RUU.zips for your model from the google spread sheet main version wont be an issue will be best to get all releveant RUUs with matching CID from there also
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
Now download the HTC_10 batch tool and install it
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
After its installed, place your RUU.zip into your local drive "C://" as an example where your batch tool is installed place the RUUs 1 at a time into /android/com, no more than 1 at a time when flashing
Full length of where RUU needs to be put in simple termns is C://android/com
Now minimise to the desktop, then right click on the batch tool icon and run as administrator,
NOT the HTC FUU icon !
Once the batch tool has booted, press the number 3 on the keyboard and then enter, this will take you to the fastboot terminal,
Take note the screen should be purple and the location on the screen should be as follows C:// is only for example your drive letter may be different,
C://Android/com
Now boot the phone to download mode and connect to pc,
Now type the following,
Fastboot devices
If that didnt work type
htc_fastboot devices
Your device should display now with a serial number,
Now type
fastboot oem rebootRUU
If that didnt work type
htc_fastboot oem rebootRUU
Now type
fastboot flash zip example.zip
If that didnt work type
htc_fastboot flash zip example.zip
!!example is the name of your RUU if you dont want to type it out drag and drop from the minimised window in C://Android/com,
Now your device will start flashing the RUU to your device, in my experience this is the only fastboot terminal that will revive a dead htc in your case without the exact signed ruu it requires,
It will also let you rollback from oreo to nougat whereas any other fastboot terminal you use will give you RUU error Main version fail in info or RUU error zip from usb command,
Try this it will work if you need clearer instructions you can check my thread out, this is pretty much the same case but without the device saying corrupt either way you still have non functional OS and oem unlock will be off FRP lock will be enabled and you wont be able to unlock the bootlaoder again without a functional OS as the full RUUs wipe the device completely resseting everything
My thread link is here for more infomation if needed
https://forum.xda-developers.com/u11/help/fixed-htc-u11corruptrelockeds-t3855157
Thanks
Click to expand...
Click to collapse

el80ne said:
Hey thanks for the reply! Actually I was able to get my phone back up and working again after having gleaned quite a bit of useful info from your very informative OP.
Fortunately I didn't have to go the route of running the HTC 10 batch tool, since I really wasn't looking forward to having to set up a virtual windows machine or having to trust a windows emulator like Wine just to run a dos batch tool. Actually I got the message pretty quick reading your first post that relocking the bootloader was a pretty terrible idea and set right away to unlocking it again. I was able to do it going through the HTC routine of cutting and pasting the ASCII key to HTC web form and having the Unlock_code.bin emailed to me again. It was different from the original ascii and unlock file they sent me the first time, but it did the trick.
It was smooth sailing from there, as I was able to boot to recovery and flash TWRP, which I then used to install the latest BadBoyz rom running Oreo and it just worked.
I was a little surprised, because I was under the impression I would have to apply all my OTAs manually since I was upgrading from Marshmellow. So even though I had a busted /system partition that wasn't letting me boot into the latest HTC RUU stock, that didn't seem to matter. Flashing with the latest RUU must hav the OTAs intact on a separate partition that the latest bad boyz rom just worked out of the box.
I'd been meeting to update this post, sorry to make you type all that out again when your first post was great. It tipped me off to scrutinize that HTC10 batch script line by line to see what was so special about it. Turns out, not a whole lot; I figured I could manage to do all that running the android bridge from my linux console just fine. But it was extraordinarily insightful in practically giving me a written line by line instruction set on how to recover my phone from command line. It was about as straightforward as it gets. I totally appreciate your help! :good:
Click to expand...
Click to collapse
Glad its sorted mate,
Always keep your bootloader unlockes so you can flash unsigned firmware as unfortunately finding signed_ruu.zip with specific versions is very difficult, and batch tool contains HTC official code for flashing and also lets you flash a lower main version and rollback the bootloader from oreo back to nougat no other fastboot terminal i used would allow it when i did it would always give RUU error main version fail,
Lucky the bootloader let you flash token, mine wouldnt even let me do that i got killswitches enabled on BL, FRP & OEMunlock please unlock lol
And thats no probs on the detailed tutorials i got kinda like ocd where i gotta explain stuff really into detail haha sometimes i dont even notice, keep the BL unlocked thouhh and you should be fine