Okay, i have a problem with an old phone, I believe its perm bricked, but wanted to check...
It is currently S-ON, and i have no way to turn off, its has no operating system, and the screen does not turn on. however i can turn the phone on, it does vibrate, and i can use fastboot commands.
Anyone got any idea's or shall i bin it?
C:\and\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: 1.21.405.2
(bootloader) serialno: **************************
(bootloader) imei: ********************
(bootloader) product: bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.006s
C:\and\sdk\platform-tools>
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
eddiehk6 said:
It's not a permanent brick if you can send and receive commands...
Your other posts have been for desire s, are you sure you're posting this in the right place? This is desire (bravo) forum.
If it's definitely a desire, look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
If it's actually a desire s, search over there, although looks like you've tried running an ruu before
Click to expand...
Click to collapse
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
mike989e said:
Yep got the Desire S because i couldn't fix this one years ago.
This is the HTC Desire (Bravo), it was s-off, i tried turning it back to factory settings, IE: S-ON, and a RUU on it, and then it ended up not booting up and the screen stop turning on, i was thinking I may have put the wrong RUU on it, as I believe I was drunk at the time (future warning to all, never flash your phone when drunk!)
When i try to run a RUU, i get errors, normally error with Signature Error. (its a Vodafone locked phone) I have used the RUU for Vodafone UK (latest).
Click to expand...
Click to collapse
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
eddiehk6 said:
sounds like you might have used an SLCD RUU form AMOLED or something like that, which is why you can't see screen.
so can you still get to bootloader screen (turn it off, then vol down + power)? post the output.
are you on a custom hboot?
can you still get into recovery and simply flash another rom just to get it to boot up at least?
you can also try flashing another recovery, recommend 4ext (see my sig), flash it through fastboot, guide if you haven't already set it up. then try to boot into it, full wipe and flash a new rom.
otherwise, if you are looking to get it to s-on and sell it:
post the exact output if you're still getting errors. however i'm pretty confident it was never a "permanent brick" and you can get it to boot up
Click to expand...
Click to collapse
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
mike989e said:
Nope the Screen doesn't come on at all, it comes on for a split second as in, the screen powers up, nothing on the display, then stays like that. it does boot to bootloader(fastboot) though by default, don't need to press vol down + power.
screen works though, so its confusing...
Oh also i cannot get to adb only fastboot
Click to expand...
Click to collapse
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
look at the troubleshooting guide stickied to the top of q&a. Likely you'll just need to run an RUU, use the 2.3.3 GB one
Click to expand...
Click to collapse
number 5 on the guide
eddiehk6 said:
almost certain you flashed wrong SLCD RUU for amoled or vice versa like i said. which is why you don't see anything...
(actually i realised you can't flash a recovery because it's now s-on, ignore that bit of previous advice about fastboot commands etc.)
so i believe all you have to do...i'll keep mentioning it until you try it:
number 5 on the guide
Click to expand...
Click to collapse
I get a bootloader version error, code 140 when i try to install lol
mike989e said:
I get a bootloader version error, code 140 when i try to install lol
Click to expand...
Click to collapse
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
eddiehk6 said:
done a bit of research for you, i thought the bootloader 140 error was for trying to install an older version. 2.3.3 GB RUU is the newest, so should work.
found another guide for you. didn't have time to read it all for you, not sure if a goldcard is required, no harm in making one anyway.
i'm still certain it's possible to get your phone working again, just takes some reading
Click to expand...
Click to collapse
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Thanks for your help though, i think it is dead, think i'll just bin it
mike989e said:
cannot make a goldcard mate, i cannot get to ADB, as device does not boot past fastboot, and even according to that guide you need to boot the device up to use adb.
Click to expand...
Click to collapse
no, you don't need to be booted into the OS:
If you dont have a goldcard, you might try to create one at this point. This may work only for some people. 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 gets detected 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.
Click to expand...
Click to collapse
the goldcard is just very useful to have in case you have this kind of situation.
i'm still very surprised the 2.3.3 RUU doesn't work. another thing you could try is to use the 2.3.3 GB RUU again, but use the PB99IMG.zip method, by extracting the rom.zip from the RUU
Thanks for your help though, i think it is dead, think i'll just bin it
Click to expand...
Click to collapse
as long as you can get to a bootloader screen, it's almost certainly not dead. your symptoms are EXACTLY as that guide states. it's your device, might as well get it working again
a real brick is literally nothing, no response, no LED, nothing. most people who think their device is 'bricked' is never actually bricked.
as long as you get to fastboot no problem. just download the pb99img from the latest 2.3 official upgrade then throught fastboot (back+power) enter in to fastboot RUU update mode then flash the zip with the command fastboot flash zip rom.zip . you dont need even an sd card to do that. just wait to procces to finish then fastboot reboot and your done. first boot takes few minutes longer but you wont have problems.
theres a couple of problems i have, 1 i have no screen, even when i fastboot. so i wont know if it fails, secondly my issues is that the image version number is to high on my phone. hence why i am getting the 140 error. as i have installed a number of roms off here the version number is to high.
off the top of my head, i cannot remember the number, however, on 2.3.3 is got a .17. in it, mine instead of that has .27. which means mine cannot install the standard 2.3.3 software, if i knew how to change the image number to higher than mine, and repackage it i could install it. but i don't know how. as i recall there was a thread about this years ago, but not sure if it was ever solved. i did look for it.
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
mike989e said:
Okay, this is not fixable in my opinion.
Summary:
I have a HTC Desire GMS, I flashed it along time ago, which buggered something! Now the screen does not come on, there is no system installed, and i can only access fastboot from usb.
I cannot use commands like "fastboot oem", It can find the device. I believe this is because the phone is S-ON, and HBOOT is 0.80
My device has a Customer ID of VODAP001 so i assume i need to use a Vodafone ROM
I have tried a number of different versions of ROMs in a few different methods.
RUUS Tried - RUU_Vodafone_UK_2.33.161.2 - RUU HTC_WWE_2.29.405.5 - RUU HTC_WWE_2.09.405.8 - OTA_2.29.405.5
I have tried changing the rom.zip to PD99IMG.zip, but as the screen doesn't work, i do not know what the error is.
When i try to use FASTBOOT to run the ROM, i get a number of different errors, ranging from CUSTOMERID Error to Signature Error.
Installing via RUU i get the same errors as above, or more often than not, i get USB Connection error (i have installed drivers)
So i'm thinking lost course. As i would need a Vodafone UK Customer ID, with a worldwide (405) Signature higher than 1.2x.405.x
Thanks everyone for your help!
Click to expand...
Click to collapse
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
eddiehk6 said:
i'm confused whether the screen comes on at all now. you said previously you could get into bootloader screen, is this still the case?
can you try to get to select recovery, then connect and see if it connects to adb at all as stated in the guide? if so then you're in luck and can create a goldcard. once that's done you should be able to run any SLCD RUU as it will skip the CID check. you need to find some way of communicating via adb. some links are down, so manual method may be another way.
have you read those guides very slowly and tried everything? posting there may also help. droidzone is still active and will be the expert on solving this.
your issue is one of the more difficult to solve, i think it's still possible, goldcard is the key here.
Click to expand...
Click to collapse
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
mike989e said:
Sorry there was some confusion there, the screen does not come on at all, i get to the bootloader as in it loads on the phone, i cannot see it though, and can connect using my pc to use fastboot. i do not believe i cannot get into recovery, as i am not sure where im loading into, it is somewhere that i can use fastboot. yes i have read through them, and thank you for those! and tried everything other than the gold card. will try to do that but as i don't have a screen that works as i installed a SLCD instead of the correct screen firmware i'm not sure how it will help.
Click to expand...
Click to collapse
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
eddiehk6 said:
i'm still a bit confused as i've never experienced it, only read others. so you can't even see the bootloader screen at all anymore, i thought that still works even in your situation (for clarity it's the white background with BRAVO SHIP S-ON at the top). does it still boot to bootloader screen straight away every time you try to power on normally?
or if you leave it after trying to power it on normally, does it get to boot sound? if so it still installed, you just have no screen. wait a minute until it boots up, then try connecting and see if you can communicate with adb.
at least fastboot is communicating so it's doesn't feel like a lost cause.
if above doesn't work boot to bootloader anyway (vol down + power), wait for a few seconds. then press volume down once, then power to select recovery. then try as before to get it to communicate as stated in the guide. have you tried this?
i haven't read all of it, but i believe you need at least 'adb devices' to work! then goldcard...
Click to expand...
Click to collapse
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
mike989e said:
Ok, It does not have a white background, the screen simply does not power on at all. (this happened after a flash, no knocks or bangs to the phone. So i don't think the screen is damaged.)
Before, it did have the white background. Yes, i believe it is booting into the bootloader when i try to start up. as thats how i am using Fastboot.
There is nothing in the system folder, "fastboot oem boot" shows nothing. i believe the phone is completely blank other than the HBOOT 0.80
i have tried that, it simply reboots back into bootloader, as i had a 3rd party recovery.
I was returning this to unrooted when this happened.
I cannot get the gold card to work on any of my microsd cards... so i will need to purchase a few to see if i can get it to work!
Click to expand...
Click to collapse
you shouldnt have a custom recovery installed any more, the RUU should overwrite it to stock recovery. you won't be able to do anything with stock recovery per se, but the guide seems to indicate that you may be able to communicate with the device via adb.
still surprised the 2.3.3 RUU didn't work, I thought it's the highest version number so shouldn't have any problem.
I'm running out of ideas tbh, I'd still recommend posting the issue in the droidzone guide, hopefully he'll reply as he'd most likely know how to solve it.
Related
Hi All,
Sorry another n00b making a n00b thread.
I bought a second hand desire very cheap under the understanding that "stopped booting one day" - so first thing first, if it is bricked, so be it.
Currently it only gets as far as the white HTC screen.
Now, when booting with PWR + Vol Down:
-Revolutionary-
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
RADIO-5.17.05.23
Obviously the PO has been playing around given the unlocked bootloader. I can get into fastboot fine. fastboot devices shows the Serial of the device.
So following the Troubleshooting guide here I attempted to flash a Recovery image as per recommendation. It shows sending and writing recovery.img OK, and the two progress bars display on the phone in line with that. However, when rebooting (fastboot oem gencheckpt), I still can't get into recovery - it goes back to the HTC screen again. Same with fastboot reboot-bootloader if it matters.
***EDIT - kept looking on this forum and it seems as if this bootloader would be write protected against RUU updates? So you can probably disregard what was here. I'll keep looking around, but if anyone has advice feel free!
If I'm missing something silly here, feel free to abuse me while you tell me what it is. Just thought I'd check to see if I'm on the right track or I've failed miserably.
Thanks.
Download the HBOOT downgrader from alpharev.nl (and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.
davebugyi said:
Download the HBOOT downgrader from alpharev.nl(and the stock HBOOT, too).
Flash the
1. stock HBOOT,
2. the downgrader
3. then the RUU of your choice (2.3.3/2.2 depends on you).
As you said, you can get to fastboot, it'll work.
You'll get a stock, unrooted device, but you can root it later on.
Click to expand...
Click to collapse
Thanks for that - I flashed these in this order from fastboot and then rebooted - I can see that it has taken effect due to seeing "AlphaRev Unlock" now, however, can't get the RUU to go - gets to Rebooting to bootloader, phone reboots and gets stuck in a bootloop (I suppose - HTC screen, black screen, and so on). Eventually it gives up and gives [171] USB CONNECTION ERROR. "Reboot Bootloader" from the fastboot menu does the same thing.
I actually have an Atrix so this is not my daily driver, so nothing too urgent, or in fact tragic if it is a hardware issue. I do appreciate any help though all the same!
Hmm - can be the cable, the drivers.
Even some people said, that using win7 64Bit will get you this error.
I'd check first the drivers. Maybe you have USB Brick as well - search the Dev Thread for a fix - basically 2 commands.
I was just reading up on the USB brick actually, as you say doesn't seem like too much effort anyway.
I am using Win 7 x64 in fact... I will copy all the necessaries to a USB stick and use a WinXP box at work just to make sure. Thanks again!
OK, update -
Same result on a WinXP machine trying to flash via RUU.
When I try fastboot oem enableqxdm 0, I get:
partition_read::Too many bad blocks(out of range)
It does say OK after that though?
If I try to flash a mtd0.img via fastboot (I assume I can't use an SD card given I can't boot) with SuperCID as the CID (either hex edited or with the script) I get:
sending 'misc' (640KB) OKAY
writing 'misc' (640KB) ... FAILED (remote: image update error)
It's late here so I'll search more in the morning, but any guidance would be appreciated.
Should I be erasing the misc partition before attempting to flash mtd0.img? If that's where I've gone wrong I'll kick myself, but thought I should confirm before I break the phone more.
Update:
I grabbed the rom.zip from the temp folder, renamed it to PB99IMG put it on a MicroSD and let the phone do its thing. It worked, in that it performed the update, but Radio_v2 failed - so I assume this means either I have a branded handset that has nothing on the outside (how do I check?) or there is a hardware fault?
Of course, I have S-ON now because everything else worked...
radio failure means you're kinda fu*cked IMO... I mean I know a user who kept trying a RUU who eventually undid the radio fail but ermm.. yeah usually it means a real brick
I figured that might be the case. Given the bootloader was already unlocked when I received the phone, one can assume the previous owner actually knew what they were doing and had already tried to fix it and come to the same conclusion.
I'll update the thread if I manage to fix it, but if anyone else stumbles across this due to similar circumstances, looks like you have your answer.
PS: bortak your troubleshooting thread was an amazing help.
Thanks to all!
yeah just try the RUU a couple of times (like 10 or something) and see what happens.. if you're lucky you might get a break..
or what you could do is flash the 2.3.3 RUU, hope it works, and if you do get stuck in splash HTC will cover you warranty!! just tell them you try to upgrade and it broke!
I am in really desperate need of help! I know many see me as a noob and a new user or whatnot but I just had a major accident with my HTC Desire with U.S Cellular. The phone is about 14 months old now but it is working like new still because I take good physical care of it.
Anyways, today I wanted to install a new Rom with Sense 3.0 from my current 2.2 Froyo from RUU. The Thread for the rom I wanted said that the CM7 r2 partition table was recommended and so I went on following the aplharev site were I had to download the CM7 r2 hboot.img (I already had S-Off and Hboot 1.06.0000 with Root)
I went my way booting into Hboot and then Fastboot on my pc. I used Fastboot commander 1.51 and made the flash for the hboot using CM7 r2. This however, is when the problem resulted. After I flashed my Hboot from the previous 1.06.0000
to the new CM7 r2, my phone screen instantly Blacked out. It was as if it died. Then I figured it may be part of the partitioning, so I Deleted my cache, boot, and entire system (I figured that with a nandroid backup, I was invincible... I was very wrong...)
After everything started getting worse, I figured it was time to reverse back to my nandroid. I clicked the "Flash all/Restore Nand" button but instantly I was given:
STARTING FLASH OF NANDROID FILES.
Flashing "boot" - PLEASE WAIT.
"boot" flash FAILURE.
FLASH OF NANDROID FILES FAILURE - "BOOT" FAILURE.
This is were I knew I was... finished... I can't use my phone as the screen is pitch black, the system is deleted because of my "Genius" self, and because the screen is black as if turned off, I can't access the "Recovery" since I am blind of my actions. I tried looking and spending literally 5-6 hours searching forums, downloading, attempting, and of course, failing.
The only thing I CAN ACCESS is Fastboot. When I power my phone, it vibrates with a dead black screen. If i power on with Volume down following power button again, I can access fastboot on my PC.
If anyone out there with a good heart can help me, that would be the best thing ever for me! I feel soo depressed now because this is my everyday phone and now... I am phoneless... The sooner I get help, the better. I need to know the possibilities to fix this issue :0
Additional Info:
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
Nandroid folder found.
Nandroid "boot" file found.
Nandroid "data" file found.
Nandroid "system" file found.
All nandroid files set - Restore button enabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 6.93.9999.
Radio version: 2.15.00.11.16.
Main software version: 2.11.573.5.
cid: utsi_001.
cpld: none.
product: bravoc.
mid: pb9940000.
security: off.
build-mode: ship.
I think Alpharev meant to be for Bravo not Bravoc, flash downgrade reboot fastboot and flash RUU, hope this helps
Sent from my HTC Desire using XDA Premium App
Alright. So how would that be in a step by step situation?
How do I flash the RUU? I'm sorry but I am still a noob learning
Jesus. Why do you cdma users keep doing this?
You're going to be lucky if you haven't bricked your device.
All you can really do is see if you can ruu. Of course, the Rom won't fit in the cm7 so you're going to have to hope your ruu's hboot will be a higher version. If not you'll have to flash the downgrade image first.
Best of luck
Sent from my HTC Desire using Tapatalk
Ok then. I have downloaded the HTC 2.2 Froyo RUU from U.S Cellular linked by HTC website but now how do I flash it? It is an exe file. I am still trying to understand how to do all this :0 I am really sorry for annoying anyone
It runs from a windows pc. Put your phone in Fastboot (from off hold back and press power) connect usb and run ruu
Sent from my HTC Desire using Tapatalk
Alright. I powered on phone into Hboot then fastboot (Windows 7 makes the USB detection sound when fastboot is detected). I am still blind since the black screen shows no image. Anyways, I started off running the "HTC Desire Froyo 2.11.573" RUU that I downloaded from HTC/U.S Cellular website (171Mb) and then I clicked the "Next" screen following up by another "Next" and then the big rectangular box saying "Verifying Information on your Android phone. Please wait..." but after about 30 seconds I get a error:
"ERROR [170]: USB CONNECTION ERROR
This error message will appear when the Android phone is not correctly connected to the host PC. It might be a USB connection problem or a PC USB driver problem. Make sure the Android phone is connected to the host PC correctly and/or check if the PC driver matches the Android phone."
I have Fastboot Commander V.1.51 running and it detects usb just fine as I can display the system info with it, so I don't see how the RUU is not finding the Desire under Fastboot.
So then I flashed the hboot with the "bravo_downgrade.img" from AplhaRev website
like you guys stated and then re approached the situation with the same process. Still keep getting the errors of "ERROR [170]: USB CONNECTION ERROR"
I don't know what to do now... Any additional advice? Am I on the right track? Maybe I'm missing something? If all goes or seems worse, I do have a school friend with the SAME HTC Desire CDMA with U.S Cellular carrier like me. He is updated with Froyo 2.2 and his phone works just as fine as mine once did before my idiot self caused this mess. He however, has no root nor S-Off.
So what can I do now? Gold card attempt maybe? I have not read anything about this but I only heard that it helps recover "bricked" Desire that is SLCD. Another slight problem, I don't know if my Desire is SLCD or not... I know only that it is CDMA *I know, frustrating dealing with a noob like me*.
It sucks not having a phone. 1 day already. I can only have patience until I finally fix my phone with the help of a good heart.
Power to fastboot power and back button..
Will fastboot recognize your phone?
Fastboot devices
If you get long number that is a good sign
You must run RUU or any fastboot command while you are in fastboot mode, not hboot
Should be long number
Sent from my HTC Desire using XDA Premium App
Ok still no go. I ran what you said "fastboot devices" using Fastboot Commander V.1.51 and got the following:
-----------------------------------.
Running fastboot command - PLEASE WAIT.
###Calling fastboot with: devices###
HT0BTHM01381 fastboot
********************************
After I got this, I ran the RUU again, and still getting "ERROR [170]: USB CONNECTION ERROR"
fastboot see your device that is good
extract rom.zip from ruu (see video in step 7 of bortak guide)
then
1 fastboot oem rebootRUU
2 fastboot devices - if you see your htxxxxxxxxxxxx no. then go to step 4
3 if not pull battery out anf boot to fastboot and start from step 1 again
4 fastboot flash zip rom.zip
5 fastboot reboot-bootloader
Alright then. Sorry for late reply. I had an intense amount of much school work to get done from Calculus and other major subjects but I managed to follow your directions and the RUU just won't detect the darn phone! Keep getting USB Error not stop. So I decided to use my brain.
I extracted the ROM from RUU in the "%TEMP%" folder and kept it in "MY Documents". After, I took a deeper look into the Rom using Winrar, and found this file "hboot_8x50_1.06.0000.img". I wondered... Hm.... What if I extract it from Rom, and flash it into my current 6.93.9999 Hboot? So I did.
After, the minute It was flashed, WOLA! I have a working SCREEN AGAIN! I can SEE! Now however, a few things have changed.
SPL/hboot version: 1.06.0000.
Radio version: 2.15.00.11.16.
Main software version: 2.11.573.5.
cid: utsi_001.
cpld: none.
product: bravoc.
mid: pb9940000.
security: on.
build-mode: ship.
My S-ON is back and I have no boot screen what so ever. EX: If I power off phone and back on, it INSTANTLY goes into hboot screen. Doesn't even bother with an "HTC LOGO". *May be because I deleted all the partitions of boot, system, ect.
Moving on, tried running RUU again. Not a single working method! USB ERROR.
Then I tried flashing the "rom.zip" extracted from the RUU using Fastboot Commander but after about 1 minute I get this:
********************************
###Calling fastboot with: flash zip C:\Users\Jona\Downloads\HTC Desire Froyo 2.11.573 ROM\PB99IMG.zip###
sending 'zip' (167226 KB)... OKAY [ 28.390s]
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 53.580s
********************************
Any idea's what to approach next? I am SUPER happy I can see my screen again, but I must repair what is broken first. Should I take action to "S-OFF" again?
I am trying to think now and here is what I suppose I should/can do.
S-Off then somehow flash Clockwork Mod into Recovery and then from there, Flash back my Nanodroid through Recovery. Would that work? What do you all think?
Why did you flash hboot only? Whole rom flashing via pb99img method not working?
For s-off you need system booted, you can't s-off from fastboot/hboot. Youre booting there because no boot and recovery been flashed. Try to flash it with goldcard via pb99img zip in root of your sdcard?
Sent from my HTC Desire using XDA Premium App
Aww man really? I totally forgot about that... I tried copying the pb99.img on my SD card and now that I can see, attempted waiting in hboot for the files to load but after they did, I't quickly should something like "SD Checking: PB99DIAG.zip"
But then it said
No image file.....
No image file.....
No image file.....
And it returned to hboot.
At this point, I started losing hope. I wanted to cry... What could I do?! No phone for 3 days.... I was a failure...
But then, only then, I took a break and powered off phone. Looked around my shallow apartment and thought, what now...
5 minutes I returned to the phone, took SD card out, blew on it, inserted it back in my Desire, and powered on into Hboot, waited again for the *Miracle* to happen, and WALA! It started loading the zip?!!! WHAT?! NO WAY! Heart pounding I eagerly stared at the phone. "Click Vol + Start Update" I clicked!
Then the 6 steps for updating appeared! 1 = OK 2 = OK
10 minutes later, I booted and back to normal From here, I can S-OFF, Get back Recovery ClockMod, and restore Nandroid. Thanks guys for assisting me well I have never been happier! I shall give you all Thumbs Up and close thread.
Out of curiosity, I should never bother to flash the Hboot EVER again correct? Only GSM phones can do this... So as a CDMA user, I should only flash roms under recovery and leave the hboot radio, recovery, and hboot alone?
Glad to hear that... Take this as warning you can flash anything what you want but only one condition: all stuff MUST be designed for Desire CDMA
Sent from my HTC Desire using XDA Premium App
Alright. I will just stay away from flashing Radio, Hboot. No reason to do so anyways :7 Thanks again!
Sent from my HTC Desire (CDMA)
Definitely as all radios and hboots are gsm and would usually brick your device. You've been very lucky
Sent from my HTC Desire using Tapatalk
I know. I am simply grateful and glad it is over. But hey, I learned soo much more about all this hboot and fastboot because of this. Good experience ^.^ Oh, one final noob Question. How to close the thread as solved? Using XDA Premium app
Sent from my HTC Desire (CDMA)
Jonicraw said:
I know. I am simply grateful and glad it is over. But hey, I learned soo much more about all this hboot and fastboot because of this. Good experience ^.^ Oh, one final noob Question. How to close the thread as solved? Using XDA Premium app
Sent from my HTC Desire (CDMA)
Click to expand...
Click to collapse
Leave it as it maybe somebody will learn from it
Sent from my HTC Desire using XDA Premium App
kotag82 said:
Leave it as it maybe somebody will learn from it
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Yes, however, there is no harm in going to advanced edit on post one and putting [Solved] at the begining of the thread title
Hi,
I always power off my phone at night and yesterday morning it booted to recovery so I thought that I must had pressed the vol key but it was frozen, removed/replaced the battery, booted into recovery again, still frozen.
Pressing the volume keys won't change the selection, pressing power will not make the device do anything. I believe that it is somewhat working because HBOOT will change to HBOOT USB PLUG when plugging it.I can also see it looking for "P98IMG" for a little moment.
If I connect it to my PC, it will be detected as "Android 1.0". I did install the drivers as specified at : http://forum.xda-developers.com/showthread.php?t=737728 I have Androik SDK installed & working (I am a developer).
The phone is detected by fastboot as :
HT12NTZ00637 fastboot
but I was not able to do anything with it.
Code:
fastboot reboot
rebooting...
finished. total time: 0.000s
The phone doesnt do anything
Code:
fastboot -w
erasing 'userdata'...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I've discovered Ace Think Tank post while searching the forums : http://forum.xda-developers.com/show....php?t=1824379
I was running ViperDHD1.1.0 if it makes any difference.
Thanks for helping me out.
HTC Desire HD (Telus)
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
MICROP-0438
RADIO-26.06.04.06_M
eMMC-boot
Oct 11 20120, 12:47:02
Tried to put PD98IMG.zip from this post on my SD : http://forum.xda-developers.com/showpost.php?p=20203105&postcount=5
It looks like the phone is trying to install it however once the "blue loading bar" finishes, I see all the folder such as bootloader, boot, recovery, system, ... but it has been displaying this for 4 hours now. I thought it could take a while but I really doubt that this is every gonna finish.
Any help?
SOuellet said:
Tried to put PD98IMG.zip from this post on my SD : http://forum.xda-developers.com/showpost.php?p=20203105&postcount=5
It looks like the phone is trying to install it however once the "blue loading bar" finishes, I see all the folder such as bootloader, boot, recovery, system, ... but it has been displaying this for 4 hours now. I thought it could take a while but I really doubt that this is every gonna finish.
Any help?
Click to expand...
Click to collapse
well, it seems that you failed to read...why being S-OFF you flashed a RUU? was that RUU froyo? Sounds like you might have messed the bootloader.
glevitan said:
well, it seems that you failed to read...why being S-OFF you flashed a RUU? was that RUU froyo? Sounds like you might have messed the bootloader.
Click to expand...
Click to collapse
First, I'm going to thank you for being the only person to try to answer but it seems that you did failed to read too as the phone was stuck in HBOOT before I tried this out. If I remove the SD card, the phone will act the same as described earlier as the install does nothing.
Any other suggestions?
SOuellet said:
First, I'm going to thank you for being the only person to try to answer but it seems that you did failed to read too as the phone was stuck in HBOOT before I tried this out. If I remove the SD card, the phone will act the same as described earlier as the install does nothing.
Any other suggestions?
Click to expand...
Click to collapse
Why not flashing a rom from recovery? If your phone is not flashing anything in fastboot or hboot, then might be a hardware issue.
Sent from my GT-N7000 using xda app-developers app
glevitan said:
Why not flashing a rom from recovery?
Click to expand...
Click to collapse
I wish I could go into recovery but I'm stuck into HBOOT and to quote myself :
Pressing the volume keys won't change the selection, pressing power will not make the device do anything
Click to expand...
Click to collapse
SOuellet said:
I wish I could go into recovery but I'm stuck into HBOOT and to quote myself :
Click to expand...
Click to collapse
have you tried navigating without the sdcard?? power the device off and take the sdcard out...then boot in hboot..
glevitan said:
have you tried navigating without the sdcard?? power the device off and take the sdcard out...then boot in hboot..
Click to expand...
Click to collapse
Yes I did, I am no SIM, no SD, even tried a different SD...
SOuellet said:
Yes I did, I am no SIM, no SD, even tried a different SD...
Click to expand...
Click to collapse
You mean that you can not move in hboot nor select anything? then it seems to be a hardware issue...
glevitan said:
You mean that you can not move in hboot nor select anything? then it seems to be a hardware issue...
Click to expand...
Click to collapse
Exactly, pressing vol up / vol up / power buttons won't make the selection change. The display will change from HBOOT to HBOOT USB PLUGwhen plugging/removing USB cable tho so it's not completely frozen...
In the mean time, I have been trying to do a couple things, like fastboot update bleh.zip but it'll give
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I thought that I could try flashing with a RUU so I got this file :
http://goo.im/ruu/RUU_Ace_Sense30_S...60.29_26.14.04.28_M_release_225512_signed.exe
but it doesn't work. If I remove/replace the battery from the phone and plug it in the USB, my PC will not find any drivers for my phone and it'll be detected as "Android Phone", trying to run the RUU will fail because it will not recognize the phone. If power it up before trying the RUU, it will say that my battery is less than 30% even if the green led (fully charged) was on.
Any ideas or maybe I'm just doing something wrong?
Thanks a lot for taking the time to help me out.
Found the Telus image T : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
extracted recovery.img as another post points out but no success so far, after typing this command :
Code:
fastboot flash recovery recovery.img
my cpu stays at 100%, and even after 2 hours and got no feedback whatsoever.
trying to update using fastboot update telus.zip will result in :
Code:
Whoops: didn't find expected signature
read_central_directory_entry failed
╗±ýpïð7'@=z«▼Gñ▼äò̪¦╝WDÙh¬Ð秬)↓ø┌温§h█←àV*PѲ╠╗[ø×e┐§¨v╗ÚY}╬áDƒ▒ýrÙ®│E█¸ÄÝÐþ\
é·\ËÜÈ⌂▓☼ÐÌõ╬PO↑pm5üå饧sÌéä]ÚâÍ▒á▼ÈØ░▼üÐ↑ggGÊè¯ãÿuÛ¸0uÁ¿Ã¾´Éë♠S%¹ ¸÷u$,gRÛÐ─3X/
═ÀE╬⌂¢↕J▄½u'LÃoáK▀Ò¥L8┴rÞ/³┌öò©7qg▀⌂¢r÷ñxrX²o¦ÆDGb8Ê☼ï■ÍÁóSR¶q¥8A_YƒKË?♦´å(E¹╩ðÄ
î/█t¬÷³4yÛ÷*←█├9▒}®Ò´m4s▓║╝Ã]╬¨ÞÞH¼
ܨXâ¨'
Yes, all the weird chars were outputted to console.
I also copied the zip to my SD, renamed it to PD98IMG.ZIP but it looks like doing the same at the other ROM I've tried earlier, the blue progress bar will complete, then when a "directory parsing" appears, it will stays there _forever_.
Hope these details can help you find a solution.
Since I haven't found any solutions yet, I am willing to offer a monetary compensation if anyone can help.
would appreciate if somebody can help, i've exactly the same problem here
Have you (both) flash a froyo RUU or ENG S-OFF and you were running Gingerbread?
I was running ICS (ViperDHD 1.1.0) and I wasn't able to flash anything as it freezes as explained in previous posts.
What happens if you just try running the RUU in hboot? I mean, connecting your phone to the computer and running the exe.
SOuellet said:
I was running ICS (ViperDHD 1.1.0) and I wasn't able to flash anything as it freezes as explained in previous posts.
Click to expand...
Click to collapse
Sorry, have you also tried with the sim card out?
Question :
sashank said:
What happens if you just try running the RUU in hboot? I mean, connecting your phone to the computer and running the exe.
Click to expand...
Click to collapse
Answer :
SOuellet said:
I thought that I could try flashing with a RUU so I got this file :
http://goo.im/ruu/RUU_Ace_Sense30_S...60.29_26.14.04.28_M_release_225512_signed.exe
but it doesn't work. If I remove/replace the battery from the phone and plug it in the USB, my PC will not find any drivers for my phone and it'll be detected as "Android Phone", trying to run the RUU will fail because it will not recognize the phone. If power it up before trying the RUU, it will say that my battery is less than 30% even if the green led (fully charged) was on.
Click to expand...
Click to collapse
I also did try a Telus image : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Maybe Ì'm just doing it wrong? or wrong image? or ...
glevitan said:
Sorry, have you also tried with the sim card out?
Click to expand...
Click to collapse
Yep, tried to flash w/ SIM, w/o SIM, w/ SD, w/o SD (from PC)
It seems to always give the same result...
SOuellet said:
Question :
Answer :
I also did try a Telus image : http://shipped-roms.com/download.ph...60.25_26.10.04.03_M_release_194001_signed.exe
Maybe Ì'm just doing it wrong? or wrong image? or ...
Click to expand...
Click to collapse
If you are S-OFF and have superCID, any RUU should be flashing. I am afraid that it can be a hardware issue...
glevitan said:
If you are S-OFF and have superCID, any RUU should be flashing. I am afraid that it can be a hardware issue...
Click to expand...
Click to collapse
Wow, quick reply.
I believe that I am S-OFF as it is displayed at the top of the screen : ACE PVT SHIP S-OFF. I don't really know about the superCID.
When looking for one of my previous posts to quote myself, I figured that I didn't explicitly said that when I plugged my phone turned off in my PC, I had no drivers for "Android Phone". If powered on, it will use the Google ADB drivers.
Dear all,
I have been looking around the forums and downloaded a few things and looked at various solutions, but I am stuck at the first hurdle.
I have been given an htc Desire Bravo that just will not boot. I do not know how it failed originally but I can only get it into the boot screens, either the fastboot/hboot logon ot the 5 buzzes and the htc logo lock. Also it takes about 30 minutes with the battery out after every failed boot attempt to restart the boot screen.
I have run adb but it cannot tell me a cid number, I have a micro sd card in it but it does not have the pb99diag.zip on it. When I put such a file on the sd card it does not find it. Communication via adb and the phone has varied success. I suspect it is drivers and what I read is an old adb bug where server is out of date.
I have never done this before this weekend so please be gentle with me!
If I can get it to work, even to use it like a wifi tablet without phone I would be happy. I am in the UK and if we have real success I would get it on tesco PAYG
I get the "cannot find pb99diag.zip etc" dialogue when going into hboot.
The logon says
BRAVO PVT-1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.27
AUG 10 2010, 17:52.18
Can someone suggest where to start? I have tried a number of guides on the forum but no success so far. Even just getting an os running would be success. I will be looking at this each evening so apologies if I seem slow to respond
Thanks
Adrian
First make S-Off. I forgot how but if i think right, you must it do via revolutionary, If it success, then download 4ext recovery.IMG and flash it via fastboot and reboot in bootloader in your recovery
Sent from my HTC Desire using XDA Free mobile app
battlekaier said:
First make S-Off. I forgot how but if i think right, you must it do via revolutionary, If it success, then download 4ext recovery.IMG and flash it via fastboot and reboot in bootloader in your recovery
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Thank you battlekaier, I will try this out tonight when I get home and will report back.
A
ukubuntu said:
Thank you battlekaier, I will try this out tonight when I get home and will report back.
A
Click to expand...
Click to collapse
After you s off u can flash hboot the easy way but first s off.
Sent from my HTC Desire using XDA Free mobile app
If u phone does not boot then u can NOT s-off, ur phone needs to be booted.. also if ur s-on and not rooted then all u can do is flash a ruu.
Did u try factory reset from bootloader menu? Try that first, u never know but chances r ul prob need to ruu a ruu.
jmcclue said:
If u phone does not boot then u can NOT s-off, ur phone needs to be booted.. also if ur s-on and not rooted then all u can do is flash a ruu.
Did u try factory reset from bootloader menu? Try that first, u never know but chances r ul prob need to ruu a ruu.
Click to expand...
Click to collapse
Hi jmcclue,
Thanks for the comments. I can boot to the HBoot and Fastboot screens, thats how I could find the S-ON and version data. If I get it to reboot, I get either a white screen with just "htc" on it, or 5 buzzes and a screen with no life at all. I am hopeful to get it to S-OFF as I have had some communication through the usb to pc connection. I am not sure if I can do an RUU update as I don't seem to have a CID. I do not have a factory reset option on the HBOOT screen. I have tried clear storage but that has no effect. Perhaps I need the S-OFF first.
Cheers again,
A
Use the 2.3gb update ruu its wwe (world wide english) so dont worry bout cid. U can find it in bortaks troubleshooting guide in resources section and its naned 2.3.3 ruu. U will find it easy enough in google aswell. Search for "htc desire 2.3gb update" its a exe file so just boot ur phone into fastboot, plug in ur phone and run the ruu, hopefully it willvwork. Im a bit worried tho about the 5 vibrations u get, maybe a sign of hardware failure. But try that ruu anyway. And again u can not get s-off unless ur phone is fully working/booted.
jmcclue said:
Use the 2.3gb update ruu its wwe (world wide english) so dont worry bout cid. U can find it in bortaks troubleshooting guide in resources section and its naned 2.3.3 ruu. U will find it easy enough in google aswell. Search for "htc desire 2.3gb update" its a exe file so just boot ur phone into fastboot, plug in ur phone and run the ruu, hopefully it willvwork. Im a bit worried tho about the 5 vibrations u get, maybe a sign of hardware failure. But try that ruu anyway. And again u can not get s-off unless ur phone is fully working/booted.
Click to expand...
Click to collapse
Many thanks
Well that was a bit wierd
If anyone can see where I went wrong, feel free to say.
I could not seem to get the link between the phone and the pc so I removed the htc sync and restarted the pc. I could then connect to the phone in some way as abd gave a command error when I sent a fastboot oem readcid which it normally does. So leaving it in fastboot with usb I ran the wwe~.exe file and it all seemed to be doing installing. There were tens of installations going to the phone I guess each reaching 100%. Suddenly I had a web page popup in my browser s.rev2pub.com/ul_cb/player.html?a=19471543&context=c23573548&size=800x600&rt=popunder&ci=10&cb=[CACHEBUSTER] recommending I download latest drivers. The wwe ruu vanished and I have no continuing processes in Task manager that I can see.
So, should I have installed in hboot? Thankfully I can still get the phone to power on. What should happen after the exe file installs?
I am able to get some response from the phone as adb devices returns the phone device number. So I hope I can try again.
Any thoughts?
Many thanks
Revolutionary S-OFF and recovery
ukubuntu said:
Dear all,
I have been looking around the forums and downloaded a few things and looked at various solutions, but I am stuck at the first hurdle.
I have been given an htc Desire Bravo that just will not boot. I do not know how it failed originally but I can only get it into the boot screens, either the fastboot/hboot logon ot the 5 buzzes and the htc logo lock. Also it takes about 30 minutes with the battery out after every failed boot attempt to restart the boot screen.
I have run adb but it cannot tell me a cid number, I have a micro sd card in it but it does not have the pb99diag.zip on it. When I put such a file on the sd card it does not find it. Communication via adb and the phone has varied success. I suspect it is drivers and what I read is an old adb bug where server is out of date.
I have never done this before this weekend so please be gentle with me!
If I can get it to work, even to use it like a wifi tablet without phone I would be happy. I am in the UK and if we have real success I would get it on tesco PAYG
I get the "cannot find pb99diag.zip etc" dialogue when going into hboot.
The logon says
BRAVO PVT-1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.27
AUG 10 2010, 17:52.18
Can someone suggest where to start? I have tried a number of guides on the forum but no success so far. Even just getting an os running would be success. I will be looking at this each evening so apologies if I seem slow to respond
Thanks
Adrian
Click to expand...
Click to collapse
Hey Adrian, I had the same problem as you did, hopefully I can be of help.
First, like everyone else is saying you will need S-OFF.
To do this head to this site on your PC revolutionary.io hit download for windows or Linux or whatever your pc is running, then you will need to fill out information about your device (see attached screenshot). Device, HBoot number, and serial number, (the serial number can be found behind the battery of your device). Once you have done that, click "Generate Key". it will give you a key, remember it or write it down.
Then, open the file that was downloaded, and extract the contents to your documents and Run the revolutionary( should look like the screenshot attached). Plug your device in (assuming you have the drivers) and it should ask you to enter the beta key we had before. Enter that and hit enter. it will then S-off your Desire and soon ask if you would like to install a custom recovery. hit Y and then enter, once that is finished, unplug your device and in HBoot go to "Recovery". Now you can flash a ROM of your choice.
Hopefully I made sense!
Best of luck
Neibaf97 said:
Hey Adrian, I had the same problem as you did, hopefully I can be of help.
First, like everyone else is saying you will need S-OFF.
To do this head to this site on your PC revolutionary.io hit download for windows or Linux or whatever your pc is running, then you will need to fill out information about your device (see attached screenshot). Device, HBoot number, and serial number, (the serial number can be found behind the battery of your device). Once you have done that, click "Generate Key". it will give you a key, remember it or write it down.
Then, open the file that was downloaded, and extract the contents to your documents and Run the revolutionary( should look like the screenshot attached). Plug your device in (assuming you have the drivers) and it should ask you to enter the beta key we had before. Enter that and hit enter. it will then S-off your Desire and soon ask if you would like to install a custom recovery. hit Y and then enter, once that is finished, unplug your device and in HBoot go to "Recovery". Now you can flash a ROM of your choice.
Hopefully I made sense!
Best of luck
Click to expand...
Click to collapse
Thank you Neibaf97
Can I confirm that I can do this from the HBOOT screen or the fastboot screen? Also where jmmclue said if I can't boot then I can't S-Off, does that mean boot to the HBOOT screen or into Android? Then if I want to load say WWE, do I put that on a microSD to get it to recover?
thanks again
A
ukubuntu said:
Thank you Neibaf97
Can I confirm that I can do this from the HBOOT screen or the fastboot screen? Also where jmmclue said if I can't boot then I can't S-Off, does that mean boot to the HBOOT screen or into Android? Then if I want to load say WWE, do I put that on a microSD to get it to recover?
thanks again
A
Click to expand...
Click to collapse
He means into android.
Sent from my HTC Desire using XDA Free mobile app
lilsafbig said:
He means into android.
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Thanks lilsafbig, that was a little too ambiguous to understand, but I have a few developments.
I am able to communicate to some degree with adb between phone and pc. Before I was unable to get anything back but now with the right syntax I have got back the CID as HTC_001 and the device number. But when I run revolutionary from the fastboot USB screen the revolutionary continues to wait for the device to show. Is it likely that USB degugging was off prior to the failure, is there a way to get it on. I suggest this as when I connect it to my pc it recognizes the device and shows in the device manager as an htc unspecified device (this is progress). As I cannot boot android it does not show as an additional drive in file manger. when I try some of the fastboot oem commands I get bad command errors, whilst fastboot getvars is ok. Could this be why I cannot get revolutionary to S-OFF!
Thanks
additional info, when usb is in an in fastboot usb, the device manager sees it as android 1.0
ukubuntu said:
additional info, when usb is in an in fastboot usb, the device manager sees it as android 1.0
Click to expand...
Click to collapse
also tried "fastboot oem writecid 11111111" and got "FAILED(remoteartition is not existed).."
ukubuntu said:
also tried "fastboot oem writecid 11111111" and got "FAILED(remoteartition is not existed).."
Click to expand...
Click to collapse
So..... does this mean I am bricked?
BUMP!
ukubuntu said:
So..... does this mean I am bricked?
Click to expand...
Click to collapse
If you can still get to bootloader / fastboot screen, then you are rarely ever bricked.
1. Ignore anything and everything to do with revolutionary and fastboot for now. I'm afraid the first few posts while trying to be helpful have been misleading. Get your phone booting up into Android OS first, i.e. into a stock ROM using an RUU
2. Use the 2.3.3. GB RUU, nothing else, it doesn't need a goldcard or care about CID etc.
3. Download it from the bottom here, then use Bortak's troubleshooting guide stickied to the top of Q&A, Point [7] to run it as a PB99IMG.zip from the root of your sdcard. That way you don't need to run it through USB or care about what drivers are installed.
Thank you Eddie, I will try that. I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)
I hope it can work out ok. I guess I format the sd card to fat32 not ext4
Will let you know how it goes.
Thanks,
A
ukubuntu said:
Thank you Eddie, I will try that. I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)
I hope it can work out ok. I guess I format the sd card to fat32 not ext4
Will let you know how it goes.
Thanks,
A
Click to expand...
Click to collapse
That's a custom rom.
Here's the link for the 2.3.3 ruu.
http://www.theandroidsoul.com/downl...uu-now-to-update-to-to-the-latest-android-os/
Sent from my HTC Desire using XDA Free mobile app
ukubuntu said:
I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)/
Click to expand...
Click to collapse
That did not work because the file is not an RUU...it is a stock rooted custom ROM with A2SD (the clue is in the name). It is designed to flashed in recovery like any other ROM. Renaming it to PB99IMG.zip won't do anything.
Use the actual shipped roms RUU link provided.
Reformat your sdcard to a single FAT32 partition if necessary, then follow Method [7] of the guide, place only the PB99IMG.zip on the root of the sdcard (not in any folder)
Hey all. First of all, let me thank you in advance for any and all help. Here's the low-down.
I bought this phone today on craigslist (I know, I know). I confirmed, however, that the phone was not reported lost or stolen and that the IMEI was not blacklisted. The guy I bought it from said he was having issues after an attempted update, but after spending the last 6+ hours combing through forum posts, trying every software combination I can find, etc. I think my issues may be bigger.
Here's what I'm experiencing. When turning the phone on, I see the following:
***Software status: Official ***
*** LOCKED ***
*** S-ON ***
Click to expand...
Click to collapse
I have 5 options at that point:
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
Click to expand...
Click to collapse
If I select Reboot, the phone reboots and the message at the top changes slightly to show:
***Software status: Modified***
*** LOCKED ***
*** S-ON ***
*** Security Warning ***
Click to expand...
Click to collapse
If I select reboot to bootloader, it goes back to "Software status: Official"
If I try to boot to download mode, I get
Failed to boot to download mode
Press volume up or down to back to menu
Click to expand...
Click to collapse
followed then by the HTC Logo and the following text
This build is for development purposes only
Do not distribute outside of HTC without HTC's written permission.
Failure to comply may lead to legal action.
Click to expand...
Click to collapse
If I boot to recovery mode I get the same thing as download mode, with the text saying "Failed to boot to recovery mode" and all of the rest matching.
I have tried signing up for an HTC dev account and going in to get the Identifier token, but because I can't boot the phone into download mode I can't get the token. When I try running the
fastboot oem get_identifier_token.
Click to expand...
Click to collapse
command it just tells me
FAILED: unknown remote command.
Click to expand...
Click to collapse
I've also tried using the HTC One M9 toolkit found here on the forums (though maybe there's some functionality I missed, I tried to be thorough).
I've also tried using the HTC sync software and downloading the RUU but after running the RUU executable nothing happens. I then dug into trying to make sure the MID and CID are correct but again, the command
fastboot oem getvar al
Click to expand...
Click to collapse
returns the "unknown remote command" message.
I'm really hoping someone else has run into something like this. Again- thanks for your time and any help you can give.
I Have the Same issue as you describe, brought Mine Back to the retailer to get it replaced ><
Failed root attempt. Most likely to be a corrupt emmc. When you get to that menu with the mode options, what happens when you immediately select "download mode", does it reboot or go to download mode?.
Beamed in by telepathy.
I have the same issue I can't get to download mode or recovery mode, when I boot to download mode I get the message "Failed to boot to download mode". Please anyone can help with this??
Redfox511 said:
I have the same issue I can't get to download mode or recovery mode, when I boot to download mode I get the message "Failed to boot to download mode". Please anyone can help with this??
Click to expand...
Click to collapse
What model do you have exactly?
OPJA100 or wich?
Android 6.0 or 5.1 ?
Firmware running ?
need some information....
shivasrage said:
What model do you have exactly?
OPJA100 or wich?
Android 6.0 or 5.1 ?
Firmware running ?
need some information....
Click to expand...
Click to collapse
I have OPJA100 before the device crashes I as on android 6.0 now I think there is no firmware on the device as it just boots to bootloader, the thing started with a reboot loop then I did a hard factory reset but it didn't work out so I tried to install a new firmware but I couldn't as S-On after multiple tries I ended up can't boot to download or recovery mode with the message "failed to boot to download/recovery mode". That's everything
I had same problem last week.
I don't have warranty on my device, so I look forward for a user solution.
throcker said:
I had same problem last week.
I don't have warranty on my device, so I look forward for a user solution.
Click to expand...
Click to collapse
same problem
guys, there are so many threads about self-bricking devices...I never saw anything since this month...what's happening?!
throcker said:
guys, there are so many threads about self-bricking devices...I never saw anything since this month...what's happening?!
Click to expand...
Click to collapse
Like the Nexus 5X and Nexus 6P, the M9 has reached the age (~1.5 years old) where hardware issues begin to show.
computerslayer said:
Like the Nexus 5X and Nexus 6P, the M9 has reached the age (~1.5 years old) where hardware issues begin to show.
Click to expand...
Click to collapse
after m9 died I switched to nexus 5x. wrong move ahahah
at least I have warranty on this
I purchased two Nexus 5X phones days before the problems started getting reported. My folks are using them. Ah well. They're great devices and I'll just have to hope that these two don't have the problems they some others do. So far, so good.
socrates23 said:
I've also tried using the HTC One M9 toolkit found here on the forums (though maybe there's some functionality I missed, I tried to be thorough).
I've also tried using the HTC sync software and downloading the RUU but after running the RUU executable nothing happens. I then dug into trying to make sure the MID and CID are correct but again, the command returns the "unknown remote command" message.
Click to expand...
Click to collapse
Hey there, the command is not fastboot oem getvar al, you should try:
Code:
fastboot getvar all
or you can return specific thing like:
Code:
fastboot getvar cidnum
And wow...I'm finding my self reading this topic, because i have the exact same issue with one of my customers phones that brought me his soft bricked M9 device.
You described the problem perfectly and this is the exact troubleshooting results i get too.
I was never a fan of HTC replacing the classic fastboot bootloader with the damn download mode, which bring us to such a situation where we get to dead end when no download mode and no recovery mode with locked bootloader.
If we could just unlock the bootloader, then we could flash easily a recovery and then flash the stock rom or custom rom, but what makes things more complicated is when we are not even able to get there due to that new download mode thingy in htc.
My only solution and work around i can give you regarding this, is finding the exact RUU specific to your model since the current state of the device will ONLY be able to accept the stock RUU firmware since it is S-ON.
Finding the stock RUU for your device can be quiet challenging, since you have to know the cidnum with the command:
Code:
fastboot getvar cidnum
That will basically help you know the right RUU for your device.
But in my case, it didn't display the cidnum since i guess the guy before me tried to flash a wrong software or run some fastboot commands that removed the data partition.
And he can't even tell me to what company it was belongs too, because the whole idea of figuring out what the cidnum is, helps you know the cellular provider that responsible on that device which will basically help you at the end of point finding the right RUU to make the device accepting it.
There are 2 methods flashing RUU's:
1. Downloading the exe file and running as admin and hoping for good.
2. Downloading the zip file and renaming it to the matching name and putting it in the sd-card and letting the device recognize it while you starting download mode(even though it doesn't load download mode).
It would basically flash the whole thing including recovery, download mode, software, firmware and put it into factory setting.
So yea, that's pretty much my direction regarding this problem. I would also really appreciate some of the proffis here to give us a hand here which would be a great help!
Let me know in the comments if you solved it somehow.
That's my getvar all status atm:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54MYJ03126
all:
finished. total time: 0.141s
reichrepairs said:
And wow...I'm finding my self reading this topic, because i have the exact same issue with one of my customers phones that brought me his soft bricked M9 device.
You described the problem perfectly and this is the exact troubleshooting results i get too.
I was never a fan of HTC replacing the classic fastboot bootloader with the damn download mode, which bring us to such a situation where we get to dead end when no download mode and no recovery mode with locked bootloader.
If we could just unlock the bootloader, then we could flash easily a recovery and then flash the stock rom or custom rom, but what makes things more complicated is when we are not even able to get there due to that new download mode thingy in htc.
Click to expand...
Click to collapse
Try to flash the hosd.img (fastboot flash hosd hosd.img) that corresponds to the current firmware of the phone while it's booted to bootloader. If that doesn't work try to flash it as soon as it reaches the error while booting to download mode. If the flash was sucessful, shut off the device and reboot to download mode and flash the RUU that corresponds to the current firmware. (According to this post the whole procedure needs S-OFF but I got told that it's possible with S-ON, as well, some days ago.)
reichrepairs said:
My only solution and work around i can give you regarding this, is finding the exact RUU specific to your model since the current state of the device will ONLY be able to accept the stock RUU firmware since it is S-ON.
Finding the stock RUU for your device can be quiet challenging, since you have to know the cidnum with the command:
Code:
fastboot getvar cidnum
That will basically help you know the right RUU for your device.
But in my case, it didn't display the cidnum since i guess the guy before me tried to flash a wrong software or run some fastboot commands that removed the data partition.
Click to expand...
Click to collapse
There are better ways. If you look at the firmware version (version-main in the getvar output or stated in the line with "OS" at the beginning while the phone is booted to download mode) you know exactly which RUU version you need to look for. This way you don't need to guess the correct RUU from the CID.
reichrepairs said:
And he can't even tell me to what company it was belongs too, because the whole idea of figuring out what the cidnum is, helps you know the cellular provider that responsible on that device which will basically help you at the end of point finding the right RUU to make the device accepting it.
Click to expand...
Click to collapse
This actually is a problem. Unfortunately, I don't have a solution, sorry.
reichrepairs said:
There are 2 methods flashing RUU's:
1. Downloading the exe file and running as admin and hoping for good.
2. Downloading the zip file and renaming it to the matching name and putting it in the sd-card and letting the device recognize it while you starting download mode(even though it doesn't load download mode).
It would basically flash the whole thing including recovery, download mode, software, firmware and put it into factory setting.
So yea, that's pretty much my direction regarding this problem. I would also really appreciate some of the proffis here to give us a hand here which would be a great help!
Click to expand...
Click to collapse
Step by step instructions are already posted several times here on xda. One example can be found here.
reichrepairs said:
Let me know in the comments if you solved it somehow.
That's my getvar all status atm:
Code:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54MYJ03126
all:
finished. total time: 0.141s
Click to expand...
Click to collapse
You can't get a proper getvar outputs while the phone is booted to the bootloader. It needs to be in download mode. However, I'm not sure whether the command will give you a proper output if the download mode is broken.
Yeah, there are many, many reports in the last weeks about this "downloadmode" issue
and dying emmc´s
I don´t know if it´s true but I heared somewhere that it´s
happenig to M9 with emmc´s produced by hynix.
Do you think this rumour coud be true?
Appreciate your very detailed reply @Flippy498! Thanks for that.
Long story short, in that case the only solution would be getting one of these JTags tools like XTC 2 Clip and do the S-OFF and only that way we can basically flash any software or RUU.
I was doing some re-search and sadly i had one of those clips 4-5 years ago and too bad i didn't keep it with me. But the price for that xtc2clip is ridiculously expensive that it's better finding someone who owns it and pay for his service just for the S-OFF part.
I found someone in Berlin who actually does that and hopefully he'll help me out.
Because without finding the right RUU, there is no way solving this problem. But the thing is, no matter in what mode i type the getvar all command, i don't get the cidnum number or main version since there is no download mode or recovery which disabling me from finding the right RUU for that specific m9 phone.
Hey everyone, kinda new to the forum. I pop back on every time I funk up a phone lol, started with a windows pocket PC ages ago.....ANYWAYS
Same problem.
Lost the phone for months and booted it up to the *software status modified*locked*s-on*security warning*
as soon as it has power it goes to this screen. reboot to download or recovery end in errors. Powerdown if it has juice just boots it back to the white reboot screen.
I never tried to even unlock the bootloader, flash or root anything, I got this phone for my wife.
Good news, though. I've been working with a 3rd tier HTC tech...whatever that means, and we have been working through everything step by step, soon enough I'll have an answer and I've saved all our logs, so I can share it here. We might even find out what causes this to happen. Stay tuned.
Repair was the only solution
I had the same issue as srqgeek. Worked through some options with HTC tech support and the ended up sending the handset away. Now I have it back it appears that it may have been a software issue as no parts are listed as replaced. I have noticed I have a different version of the ROM installed with the HTC standard global ROM as opposed to the carrier updated version (EE-UK in my case). I've had no issues since the re-image.
srqgeek said:
Hey everyone, kinda new to the forum. I pop back on every time I funk up a phone lol, started with a windows pocket PC ages ago.....ANYWAYS
Same problem.
Lost the phone for months and booted it up to the *software status modified*locked*s-on*security warning*
as soon as it has power it goes to this screen. reboot to download or recovery end in errors. Powerdown if it has juice just boots it back to the white reboot screen.
I never tried to even unlock the bootloader, flash or root anything, I got this phone for my wife.
Good news, though. I've been working with a 3rd tier HTC tech...whatever that means, and we have been working through everything step by step, soon enough I'll have an answer and I've saved all our logs, so I can share it here. We might even find out what causes this to happen. Stay tuned.
Click to expand...
Click to collapse