• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Black Screen

Hadron said:
Custom ROMs are always installed by flashing a zip through a custom recovery. Not as PB99's, and not via fastboot. So if you want to try this you need a custom recovery (also linked in my earlier post). And that you do install using fastboot flash.

But note: if that RUU isn't working, you may not be able to undo this. On the other hand, it sounds like you can't get into recovery mode right now.
Click to expand...
I don't know how to do what you said. (fastboot flash) What programs are needed and how?

You're right, I can't get into Recovery menu.
 
"fastboot flash" means flash an image using fastboot. In fact it's the only thing that your fastboot commander does (though I never use that - I prefer to use command line fastboot, so that I can see/control exactly what I'm doing).

So if you download the custom recovery image (post #19 had a link to an XDA thread, and tells you how to find the recovery image within it) you can then flash that to the recovery partition using fastboot (and hence I assume fastboot commander). Then if you can get into recovery (i.e. if you can get into hboot mode) you can do the rest.

My only hope here is that the reason you are stuck in fastboot mode is that your recovery is bad, and so it's booting into the only mode that still does something useful. But I'm far from certain. As I keep saying, the RUU .exe should have fixed everything when you ran it.

I don't think revolutionary will work again now that you have hboot 1.09. I mentioned earlier that when this forum was more active we told people not to use the HTCDev update for this reason. However, (a) you'd already used it, and (b) with a USCC device you don't have a lot of RUUs to choose from, so frankly I'd probably have tried it anyway in this case.
 
Although this is a US Cellular, but I'm not using the phone for text and call.
I mean I just use wifi and camera. I don't need US cellular. So can I install other providers' Rom and other stuff?

For using fastboot command in CMD in windows, it doesn't recognize the phone, because it's in fastboot mode. So the only program that can contact phone is Fastboot Commander.
By the way can you please tell me how to use the Stock2.2.zip (149mb) file?

Thank you so muchhhhhhhhhhhhhhhhhhhhhh.
 
Actually I already have told you how to use it. I also quoted it again in post 24. But you need a working custom recovery to do it.

You can use fastboot commander to flash the recovery image.

But if the phone is in fastboot mode then command line fastboot should be able to communicate with it, becauase that's what fastboot mode is for. I suspect it's that you haven't got command line fastboot set up, because all that Fastboot Commander is is a GUI and a set of pre-defined scripts for running fastboot (so if fastboot commander can work then fastboot would be able to as well).

The problem with using another provider's ROM is not the phone bit. It's that the RUU package will check the phone ID, and won't run if the ID is wrong for the software. So if you had say a Sprint RUU and try to run it on a USCC phone you'll just get error 130 or 131 ("customer id error") and it won't run. There's a way to modify the SD card to trick the RUU into running - it's called making a "goldcard" - but I've never done it, and I have a feeling it's not so simple if the phone is not working. And it still won't let you downgrade the software, so you'd need an HTCDev RUU anyway (because those were the most recent which were ever released for the Desire).
 
Actullay I have the goldcard file. I made one for my cellphone, but it's a .img file, and I don't know how to use it.

When I want to flash image recovery (149mb), the Fastboot commander gives an error as I stated in post 23.

###Calling fastboot with: flash zip C:\****\Stock2.2.zip###
sending 'zip' (152451 KB)... OKAY [ 22.688s]
writing 'zip'... FAILED (remote: not allowed)
finished. total time: 22.688s

Is there anyway to completely format the phone memory? Or at least reset to factory with fastboot or other commands?
 
That's not the recovery you are trying to flash, that's the ROM. There's a link to the recovery (4Ext) in an earlier post, and directions for how to find the right file.

Maybe you should read some of the guides in the Desire All Things Root Guide sticky post first. I know you are new to this, but you need to slow down and work out what you are doing before trying stuff. I did this stuff over a much longer period than you are trying to.
 
As for goldcards, the rooting faq in the post I just mentioned will point you to what you do. You'll need a card reader as you don't have a working phone.
 
I extracted the rom.zip from image recovery file (Stock2.2)
I changed it to PB99IMG.zip and copied it to the sd card(with card reader), then I put the sd card into the phone, and turnet it on, but it didn't work.
What is update.zip? There is a parametr for fastboot which I can reFlash device through this command.

If I could go to recovery menu, I was almost done.
 
When I wanna fastboot the rom.zip which I extracted from the image file and changed the name to PB99IMG.zip, it gives an error:
Whoops: didn't find expected signature
read_central_directory_entry failed
 
By the way, in Fastboot Commander, I chose the Misc tab, then I checked recovery,system,cache,userdata,boot and clicked on Erase chosen partitions.
I think the recovery was deleted because of this :(
I'm working on it non-stop.
 
I installed the Stock2.2.zip from recovery menu, and now my phone is ok.
But it's android 2.2
How can I install the latest official android version, and also the latest rooted rom (Android 4.x)? I think there are 2 ways to do that, one way is to copy the .zip file to the sd card and install it through recovery menu, and the other way is to install it by executing a .exe file(but I don't know what to do if it is .zip). Am I right?

Thank you so much Hadron, you really helped me a lot. I really appreciate you. I don't know what to say. Just thank you a lot. I wish the best for you in your life. You're really a good person.
Thanks, thanks thanks, thanks, thanks
 
Glad to hear it's working (did you find that 4Ext link in post #19, or from one of the guides?).

Official ROMs can be downloaded in .exe form and installed that way, but the .exe you tried earlier in the thread is the most recent official ROM for the USCC Desire (and for some reason wasn't working). A 2.3.3 ROM was released for the GSM model, but not for CDMA.

Unofficial (rooted) ROMs are installed by copying a .zip to the SD card and installing through recovery. You should do a factory reset in recovery before installing, as usually system settings are incompatible between ROMs unless they are very similar, and hence you can get weird bugs or a phone that just won't boot. There are apps such as Titanium Backup which can be used to back up user-installed apps and their data to SD, which speeds setting up again after changing ROMs.

The most important thing if you start trying different custom ROMs is to take a full system backup first. Go into recovery and select the backup option. That backs up your ROM as well as your apps and data, so if something goes wrong when loading a different ROM you can just restore and have your phone working again. Always do this before loading a new ROM and you should be OK.

The problem with getting anything recent is that you have a CDMA device. There are a few brave souls still working on ROMs for the Desire (I see that Nikez is trying to port 4.4 to it!), but those are inevitably GSM ROMs, and won't work on your phone. The CDMA models were much rarer, and so didn't attract the same level of developer support. This thread has an index of ROMs for the Desire - I previously posted a link to post #3 in that thread, which has the CDMA ROM section, but none of the ROMs in that section was newer than 2.3 (and the one 2.3 ROM I looked at there was a dead link). It may be that some of the other ROMs in that thread have a CDMA version, but you'd have to search the individual threads to see whether this is so. That's even less likely for Android 4 ROMs, where even for the GSM model there were not so many developments going on (most of the android 4 ROMs listed there are based off just a couple of sources, and those were GSM). All you can do is look, but I can't promise anything.

If it's any consolation, I kept my Desire on 2.3 right up to June this year, when I finally upgraded. I reckoned it worked better on that hardware than 4.x.
 
I have installed the Cyanogenmod 7.2 (Android 2.3.7) It's working fine.
As you know HTC Desire RAM is 512MB. Can I install Android 4.x Roms?
Which Rom do you think is the best?
 
There are 4.x ROMs which work on the GSM Desire. I have run Nikez's JellyBean ROM (4.2) with more success than any 4.0 ROM I tried on that device. I used that one because it seemed that most others were based on it anyway. However, it was still slower than an AOSP 2.3 ROM would have been (AOSP = Android Open Source Project, i.e. without HTC Sense). So from my experience you should not expect improved performance from 4.x on the Desire.

The catch was what I said in the first line: "GSM Desire". I don't know about all of the 4.x ROMs, but those I do know about are GSM only. So it would be possible to run 4.x on your phone, but I don't know whether such a ROM exists.
 
Since I installed 2.3.7 wifi signal is not good.
Wifi was working till yesterday, but it can't connect now.
Is there a better Radio file that I can flash in my phone?
 
ADB works, Fastboot doesn't work. I installed intel USB3 driver for win8 64bit, but didn't work. I also installed 3 versions of HTC Android phone.

2-The hboot version is 1.09. how can I change it to 1.06 ?

Thanks
 
I'm afraid I don't know a way of downgrading that hboot. To change hboot you need S-Off or an RUU. The RUU won't downgrade hboot, and the S-Off tool won't run on that version. :(

Radios suffer the usual problem of CDMA devices: you can find every GSM radio ever released in a flashable form, but I've never seen this for CDMA. Do NOT attempt to flash a GSM radio because that will be the end of your device if you do.

But before we get too carried away with the radio, the important question is whether your WiFi reception is really worse, or whether it just shows fewer bars than before? There is no universal calibration for signal bars, so the same signal may show more or fewer bars with different ROMs. The real test is whether it works the same, not how many bars it shows.

Edit: sorry, read it again and it says you can't connect. Can you see the network if you scan for it? I use a little app called WiFi Analyser to check WiFi signals. Just need to work out whether the problem is reception (may be radio related) or connection (more likely ROM or settings). I had a CM ROM become very finicky about connections once, and clearing all saved networks fixed it.
 
Hadron said:
I'm afraid I don't know a way of downgrading that hboot. To change hboot you need S-Off or an RUU. The RUU won't downgrade hboot, and the S-Off tool won't run on that version. :(

Radios suffer the usual problem of CDMA devices: you can find every GSM radio ever released in a flashable form, but I've never seen this for CDMA. Do NOT attempt to flash a GSM radio because that will be the end of your device if you do.

But before we get too carried away with the radio, the important question is whether your WiFi reception is really worse, or whether it just shows fewer bars than before? There is no universal calibration for signal bars, so the same signal may show more or fewer bars with different ROMs. The real test is whether it works the same, not how many bars it shows.

Edit: sorry, read it again and it says you can't connect. Can you see the network if you scan for it? I use a little app called WiFi Analyser to check WiFi signals. Just need to work out whether the problem is reception (may be radio related) or connection (more likely ROM or settings). I had a CM ROM become very finicky about connections once, and clearing all saved networks fixed it.
Click to expand...

About wifi, actually it's just the bar. It can find the wifis but it get stuck at Obtaining IP and then it gets Disabled. I installed the Rom again, and it's working ok. But I don't want it to happens again.
Can you please answer my last post? about fastboot and hboot. My phone is S-On and I can't work with Revolutionary while it just works with hboot lower than 1.06
 
Your fastboot problem is probably due to Windows 8. A number of people here have reported problems getting W8 to even recognize the phone.

Hadron answered your question about downgrading hboot. He said he doesn't know. If he doesn't then you are unlikely to find anyone who does. There's very little he doesn't know about the Desire.
 
You must log in or register to reply here.
Back
Top Bottom