Database Info

PLEASE Help - I think i bricked my phone. [SOLVED]

Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg

I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck

Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?

MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access

kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks

ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.

kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.

ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?

kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks

ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).

kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?

While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.

Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks

...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?

Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"

eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?

And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)

OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.

Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers

BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.

How to unbrick HTC Sensation ??????????

First of all thanks for this great forum !!!!
This will be my first post. I have to thank all developers to get the sensation s-off.
I made a stupid mistake with the eng hboot. I played a little round and typed
"fastboot oem fdisk erase_emmc.
Now Phone is completly dead and bricked. Can not power on and no charging.
But it must be possible to bring the sensation back to life. I downloades QPST an drivers and see, that the device is in download mode.
I tried cdma workshop and DFS CDMA Tool too.
Can somebody make a dump with QPST and backuo the nv file and firmware image to unbrick the sensation.
Please no commands why I have done this. I said it before. I have no second sensation to try it by myself.
Has anyone an idea ??? (without to send it back or jtag flash)
Thank you for any help.
Kindly regards Woody01
Sorry for bad English

Send me the commands and i do it for you!
No comment on what you have done

I'm sorry man, but we can't help you. Once you erase something like that, it's over for that device. If i'm reading correctly, the internal sd card is completely wiped, no recovery, no HBOOT, no / (original mount point). The thing that bothers me, if you didn't know what it did, why would you run that command? That is idiocy at it's finest. The only thing you could do is send it back for a warranty replacement, since it's bricked like that, they won't able to tell you ever rooted or flashed anything. If you do send it back, play dumb, say you woke up one day after charging it all night and it just wouldn't turn on any longer. Once you get your replacement, do not install the ENG HBOOT, it isn't for noobs for this exact reason.

Download mode could be a mode where it wait for flash ... keep it off until someone comes with ideas....

Thank you for your answers but I expectet such replies.
It must be possible to bring it back. In QPST you have the ability to flash back the Multi-Image file. But i am missing the the phon image hex and boot hex. I think if someone make a backup from the Multi-Backup and NV file we could unbrick it.
For the Galaxy S someone wrote at tool (One click unbrick). There will be everything restored. (partition, boot, etc).
Is someone interestet to help me trying this ????
Kindly regard Woody01

I say again tell me how i do it .... backing up should be no problem for a device

@xtcislove
First of all you must dwonload QPST (I found it by google). I have version 2.7 buil 355.
You need the QHSUSB Drivers. I found the drivers on google. I think the phone must be in diag mode. Use QPST Software download. There is an option backup. There you can backup the firmware. It will be restored as an qcn file.
To restore the NV File you can try DFS CDMA Tool. There is an option to read the NV file. At that point I could write the file from Wildfire. I could delete it too. I used the free version 3.2.0.0
For Diag mode you need the HTC Diag driver.
It is possible for me to upload these files here in forum and is it allowed ???.
Thank you
Be careful with the NV file. There is your imei and serial number. It would be nice if someone send the file with edited imei and serial.
I need the hex files for QPST. Some wrote in the www something about CDMA-Workshop to get the hex dump.
Kindly regards Woody01

Sry i cant edit my imei etc out ...
and with 3 posts i dont trust you really ... sry i think u should ifnd someone

@ xtcislove
I understand you and is absolutly O.K . I would not send the NV file with my emei and serial too. (only the file with editet imei and serial)
I hope someone is interestet and crazy to unbrick the device and help me.
Kindly regards Woody01

Get a warranty replacement and don't even S-Off your phone. You obviously can't handle it.

In curious, why were you doing what you were doing?
Sent from my HTC Sensation Z710e using XDA Premium App

WorldWide60 said:
In curious, why were you doing what you were doing?
Click to expand...
Click to collapse
Haha i was wondering the exact same thing

I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?

massasshadows said:
I have similar situation. my phone won't boot, no LED anywhere.
what i stupidly did was, i tried to reinstall the stock ROM and between shuffling the screens around i skipped one step. that step was actually opening the stock ROM and running it and following the commands. so i tried to unroot and S-on without selecting a ROM to flash...... now i'm screwed.
i checked my SD card in my old phone and all the data is still there. will that make a difference. or am i helpless?
Click to expand...
Click to collapse
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone

Bricked mine too (Yes, very stupid indeed)
aramis73 said:
I have my sensation bricked...it's dead with screen black...someone has a solution? Thanks to anyone
Click to expand...
Click to collapse
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!

choas2009 said:
I was stupid enough to brick mine too by an S-OFF -> S-ON transition . No solution I guess? I e-mailed three different repair centers, but no response yet. I wonder if it is possible at all to flash the Sensation's bootloader without a functional USB connection.
For other phones it can be done by a JTAG interface, but this is very delicate job which I can't do myself.
For now I consider it bricked. I bought some Apple stocks (AEX ING Sprinters Long, Dutch stock market) and will let these pay (I'm already there after today) for the new Sensation that I bought already. If it is repairable after all I will sell one of them again. I'm not going for a warranty return. Beside the fact that it is possibly detectable that I voided the warranty by touching the bootloader, it is my own mistake that I have to pay for....
By the way I have been looking for more people who killed their HTC Sensation, but I could only find you two guys and a german who is mentioned in this thread as well.
Please keep in touch!
Click to expand...
Click to collapse
I'm actually doing the whole return process. Since mine is so badly inoperable, I'm hoping that after they inspect it they will be able to give me a new one. I was able to S-On the phone (as far as i know) during the process so if they are able to read it, it should be cool. If anything i'll either be turned down or have to pay for a new one.
Planning on blaming it on the over night charging + the 2.3.4 update they released the day i bricked it haha. It's all just a game of chance.

i did it too my friend , some mistake S-off ---> s=on transition , do you have any solutions

Hello everyone, I'm a noob and this my first post. I had been reading blogs for years now on all sort of advice and solutions, so yes this is my first reply or post on any blogs. I usually find the answer I'm looking for so posting anything was unnecessary. Now I really need help. I screwed up some how. I was attempting to turn S back to ON because my device was not taking the new update, and by doing so bricked my phone (wont power on. I'm guessing I had restored a rom and not original back up which xl VipeR lx had warned about in his instructions. I have SD with su-2.3.6.3-efgh-signed.zip on it. Can someone please help I really should had not rooted my phone because I dont have the knowledge. I can take instructions very well (was Soldier in the U.S Army for 8 years (2 years in Iraq). So if some one would please give me instruction on how to fix this, I would really appreciate it.

Is there any solution ?
Thanks !

Would this tool allow me to make a backup of my phone that can be restored if ever it is bricked? In other words, would it make my phone nearly unbrickable? I mean, there is very little chance of my phone being bricked, I make sure I know exactly what command does before I execute it. I realised I have spent most of my days in the last couple of weeks reading XDA and thinking about my soon to be gf in Hong Kong XD. I just worry that when flashing a firmware file I may be left with a brick, or even get one of those bricks people speak of that just happens randomly. I really don't want to lose my phone, it means so much to me lol. I just get so worried with these things....
What I'm trying to ask is, a partition backup created with this tool can be flashed to the phone with what functioning partitions? ie do you need a working radio partition or not? working hboot? Cause what I'm scared most about is flashing a bad radio and creating a phone that can not get into hboot... i'm also scared about getting a random brick which at the moment seems to be unfixable.
Mind you, it would make a pretty impressive paperweight....
EDIT: found this guide... can someone explain what NV items are? A small understanding of this may allow me to make a backup using this tool that could then be used to unbrick sensations... I couldn't find what NV items are... I also found this....

Bricked, I think?

so get this...
I just rooted my sensation and was waiting for a custom ROM to download through the phones browser. My buddy came over and I was setting him up with root for his Aria and for some reason his phone got stuck after getting s off. I tried to use adb to flash the recovery to his phone but it just said "waiting for device" forever. After about 10 mins I said forget it, too nice outside and unplugged his phone, I didn't think to close adb first but I put my phone on the usb to charge and then it instantly flashed the Aria recovery to my phone.................
Good news is I can root his phone knowing it was the wrong installed driver before. Bad news is I now can only get into fastboot (white screen, skating androids at the bottom) where it still says revolutionary at the top but I can see the Aria's radio and the wrong HBOOT version. I still have the factory reset, recovery etc options but if it boots up it'll get stuck at the stock HTC image. I tried flashing CWM recovery through adb the exact same way but it just says waiting for device now too? I may have typed the code wrong or do I need Aria drivers now? I assume there is a way out since I'm still in fastboot but not sure.
Any help would be appreciated and thanked! Until then, its back to my g2x, its not so bad...

you would need to download the RUU (Rom Update Utility) for your phone, where you get it I have no idea, hopefully another more skilled member will be able to point you in this direction..... I got the Vodafone uk one from a thread on here but I for the life of e can not remember where.

Nah I figured it out, I downloaded the img file and flashed the zip in hboot, then used adb to push the stock radio back up. I was really scared there for awhile but thanks to this place I got a bunch of help.. Love this place.. Thanks anyway though man!

It's good to know that a bad radio no longer prevents booting to hboot. I bricked a g1 back in the day from having an hboot and radio that were incompatible with each other. The thing wouldn't boot to anything other than a special service mode that is only useful if you solder in a hardware jtag.
Sent from my HTC Sensation Z710e using XDA Premium App

[Q] HELP - Broken HTC Sensation

So here is the story.
I'm more of a linux user than anything else. I use Ubuntu Studio and Linux Mint on my home computer, and when I heard about the developers preview of Ubuntu Touch, I got excited.
Following the instructions in one thread here, I found it fairly simple to install Ubuntu Touch, and it looked perfect. However, it was much too early in development for use. Everything was kind of a placeholder, there was no network connectivity, phone capabilities, etc. So I went back and installed the rom I had used previously.
Here's where the problem happened. After successfully flashing the Rom to my phone and booting up into the GUI, if I clicked on anything it would reboot. Seems kinda funny, so I had tried about 5 other working roms, and they all did the same thing.
So I assume that when I installed ubuntu touch, it had actually removed a lot of the drivers for my Sensation.
HTC has been NO help at all in obtaining the correct software so I can fix my phone. Additionally, they don't even answer back my emails with comprehensible responses. I've explained this problem to them in great detail, and the extent of their responses are "if u can not find the softwares on htcdevs.com you will have to send your device in for repairs. If the damage is not covered under warranty we will let you know how much repair will cost, if you dont want repair you pay for shipping of unrepair device back to you."
Like, really?
I would like to do a fresh installation of the kernel, drivers, OS, etc so that I can use my phone again.
If you need more information don't hesitate to ask.
I hope someone has had a similar scenario, or at least know what I'm talking about and might be able to help me a bit.

What you probably need to do is flash (is it flash?) a RUU (Rom Update Utility). You can find them here.
EDIT:
Hmm.. You probably can't run .exes on Linux, can you? Maybe with Wine?

ridder215215 said:
What you probably need to do is flash (is it flash?) a RUU (Rom Update Utility). You can find them here.
EDIT:
Hmm.. You probably can't run .exes on Linux, can you? Maybe with Wine?
Click to expand...
Click to collapse
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)

rzr86 said:
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
Click to expand...
Click to collapse
Oh thank you, I will check that, because I had just downloaded a RUU and booted into my windows partition, and attempted to run it. Since I can really only boot into recovery, it was only mounting my SD card, not my internal storage (i seem to recall it used to mount the device itself). So, the RUU for pyramid wouldn't run. If I can flash it, that would be best, I will have a look at that thread, thank you.
I think what happened is Ubuntu Touch stripped down android on my phone... I'm not sure if roms run as a replacement for that, or on top of it, I'm really still a beginner when it comes to phones, but usually I can manage to find the information I need to fix a problem... This is the most difficult problem I've had. Thanks again for the link.

rzr86 said:
he can extract the rom.zip from ruu and flash it from bootloader
see here for that
http://forum.xda-developers.com/showthread.php?t=1672425 (step 4)
Click to expand...
Click to collapse
Thank you again. You pointed me in the right direction and I got my phone working once again. Re-rooted and s-offd and now installed CM9. Thanks again for your help.

completely stock (never tampered) Mini won't boot past hboot into OS

Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.

iceterminal said:
Hello XDA members,
My wife's HTC One Mini's battery drained yesterday and when we charged it up, it will not boot into the OS. I'm quite familiar with rooting, loading ROMs, and stuff like that for my HTC One, but it's really odd that the stock AT&T ROM and everything is getting this behavior. I would ideally not have to wipe everything right away because she took pictures of our new born daughter (3 months) and she unfortunately did not setup G+ to backup her photos. I'm a little hesitant to bring it to AT&T right away (we have insurance on this phone) because I feel like they might not explore all the options as we would here on XDA.
here is what the boot screen says.
*** LOCKED ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.19.0000
OS-1.32.502.3
eMMC-boot 1024MB
Sep 3 2013,11:06:59.0
FASTBOOT
usual volume button commands
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I can get into BOOTLOADER which lists, recover, factory reset, clear storage, simlock, image CRC, and show boarcode.. but nothing happens when I select them with the power button.
I'm at a loss here. I'm going through the process of getting my Windows 8.1 drivers to connect to fastboot to see if I can access the card to pull down the images but I'm not sure if I can do that since I didn't have any opportunity to unlock it in ADB prior to booting into hboot.
Click to expand...
Click to collapse
I gotchu my friend ;D http://www.htc.com/us/support/htc-one-mini-att/news/ That is the ruu for the htc one mini

abzboi said:
I gotchu my friend ;D That is the ruu for the htc one mini
Click to expand...
Click to collapse
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!

iceterminal said:
Thanks! Unfortunately the executable requires the phone to boot into the OS to be recognized and the phone isn't booting into it. Trying to find the RUU stock ROM now to see if maybe I can push it over via fastboot. Crossing fingers!
Click to expand...
Click to collapse
Ah I read that it will work too if it is fastboot which is why you were suggesting it. I'm wrestling with fastboot drivers and windows 8.1 so it is recognized so I dualbooted into ubuntu which can communicate via fastboot so I'm hoping WINE will run and flash the RUU .exe

So I ended up rebuilding an older laptop to Windows 7 and ran the RUU executable and it looked promising at first with the updater recognizing the device and displaying what software version and stuff.... but then when it rebooted into hboot with it's process, the update failed.. not sure if it matters but it was "updating" from the same version as the current version. I was hoping this would be a fresh install. So now I'm looking into maybe doing a fastboot oem unlock and flashing a rom myself. Not sure if this will help me get the phone back from the dead, but going to do some more reading and exploring. If anyone has some shots-in-the-dark they would like to offer, I'm up for trying them.

I hope you would be able to fix it.

Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.

iceterminal said:
Ok so here is the latest and hopefully someone can confirm what I'm thinking for next steps.. I attempted to unlock the bootloader from HTC Dev. I was able to extract the keys, and I loaded the BIN with the new keys that will unlock the bootloader. Interestingly enough, I was expecting the HTC dev splash screen warning to come up where I would have to Accept the new terms and stuff, but that did not come up at all. So it was like I could go through the process and communicate to the device to unlock the bootloader, but something must be corrupt about it because it is just not responding the way it should on certain commands/tasks.. My bootloader is still locked (S-ON)
SO.. I stumbled upon someone mentioning that we are able to load CWM recovery even on a locked bootloader. Is this true and available for the HTC One Mini as well?? Couldn't find a definite answer on that for this device.
Click to expand...
Click to collapse
Have sent you a PM re your issue.....
Re flashing recovery without fastboot (locked bootloader), it can be done, but only, as far as I know, via the phone os using CWM manager or Flashify (which is a cool app!)

wanted to close the loop on this thread that nelvinchi and I literally tried everything we could think of to bring the phone back to life with no avail. Much respect out to nelvinchi for taking his time to help me out! We've determined that the device has a faulty memory chip and cannot be recovered...

Mine just did the same thing and I can't get through to anything I need help also if you have found a solution

Help my
provided you solve a problem with one htv mini.my I have the same problem, please help me