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

Root Help making a goldcard for a slcd bricked desire

Hi loopingz, and welcome to AF :)

Yes, that's what the posts in this thread say - one member used a different model of phone, and the original advice was to use a card reader, so it definitely doesn't matter if you use a different phone.

What exactly is the problem though? Boot loop and frozen hboot would be different things (neither actually a brick). And by "frozen hboot" do you mean that you always boot into hboot, or that you cannot use the menu when you are in hboot? The latter is more serious if you are planning to use an RUU. Do you know what caused the problem - if it's boot looping and no changes have been made to system software a factory reset may fix it without running an RUU.

Final note: many GSM Desires can run the 2.3 upgrade without a goldcard. Ignore this if you already have the RUU you need, but it can be useful to know that.
 
Long story short... I was ebaying for an amoled screen to replace a broken amoled for my desire and I placed a bet on a boot looping english o2 desirewith not much details on how it happened(you may call that a stupid buy, but it is some kind of challenge now!).
Replacing the screen on my first desire was easier than expected so at least I have one working!
For the new one, I dont know much yet. Here is the vol down+power screen:
Bravo PVT1 Ship S-ON (I need to change that first after doing by goldcard if I understood well)
HBoot-0.93.0001
Microp-031d
Touch Panel-Synt0101
Radio-5.11.05.27
Aug 10 2010, 17:52:18

So far I have just tried clear setting and recovery, it just go to a fixed boot screen.
This morning it was plugged to my computer and it booted together. Strange the phone was working fine but after like one minute it crashed and back to a boot loop issue. I could not go back to this state yet.

Do you recommend to build the Gold card from the Phone or fromLinux + card reader, I can do both method.
 
I don't think it matters which you use for the goldcard.

Don't worry about S-On - changing that is optional in some rooting methods, included in others, but not an issue here.

If the goldcard doesn't work (RUU complains about a "cid error") then the 2.3 upgrade from shipped-ROMs should work without one. Either way, if it's a software problem then an RUU should fix it.

It might be hardware though, in which case this won't help, but as you know there's nothing to lose by trying :)
 
I only had a spare 8gb (kingston) sdcard. I did it gold with my other phone without particular issue.

Then I tried RUU. I passed the first steps but then when it is suppose to update it showed no progress number. First I stopped it after 30min and it really looked like it did nothing to the phone. Then I did another fire for the night, and I a CID error inn the morning. I will try to find a 2gb card or less and try again, sure the 8gb card does not help here!
Meanwhile I will try to RUU the o2 froyo (thanks for the link), it might give me a good idea if it is a software or hardware issue. I still hope it is software and I keep trying! If it works, I will still have to have to follow the debranding stuff (I am not even in England).

Anyway I am still learning here so it is cool. In the end I plan to update my current phone to 2.3 (still in 2.2) with additional 1gb of phone storage on the sd card (main weakness on the stock phone in my opinion).

I will keep this thread updated when I became progress.
 
Well, I have tried the o2 froyo rom 2.14.207.1
It told me my version was 2.14.207.3, I launched the update anyway.
It was showing progress (not like yesterday) and when I was almost done (I guess 90 something %) I had the following error 110.
The ROM Update Utility cannot open the requested files or the files are damaged. The RUU cannot continue with the update.

Please get a complete RUU package and try again.


I verified the md5, it is ok. The battery is 100%, checked on my other phone.

New symptoms: the phone doesnot boot all: black screen, no vibration.
:confused:

Is it correctly bricked now?
 
Any idea what file it had trouble with? Might tell us what our chances are.

It sounds like it thinks the RUU is bad, but maybe the problem is with the phone. But I don't like the symptoms. If you can get to running an RUU, I'd try a different one (prob the gingerbread upgrade). Try leaving the battery out for a while. Or see whether you can run it anyway (i.e. despite the screen being off).
 
Well I am pretty sure I had passed 88%, I guess I was a 90 something or maybe it was just final check. The message error I wrote is the excat same I had, I did a printscreen while it was closing, it was starting to be transparent!
I replaced my screen on my working phone about a week ago and obviously this flash leads to a different situation. I have no boot up sign at all, no vibration, no led on when I charge, no usb connection when I connect to computer just the big nothing. I really guess that trying a blind flash like for a slcd balck screen would not work. My understanding is that I have no more working hboot.
I can keep it for parts like the screen, the touchscreen and the battery, try to find a cheap motherboard (only found around $150) or try to bring it to a competent shop.

Anyway I have seen (talking in past before bricking it further) this phone booting once and then going back to boot loop sequence. So I guess, the previous owner did not fail at flashing, to me something is corrupted in the hardware, probably in the rom or somewhere in the memory. If I am right it would mean that it is not possible to do a low level flash (like I have seen on the web some shop soldering stuff to perform some mods).

Do you know any place to find working motherboard at a more decent price?
 
The original bootloop might have been software rather than hardware. But no LED when on charge is an extremely bad sign. It might have had a hardware fault, or it might be that the radio flash failed (which of course could be because it had a hardware fault!), but I think it really is dead.

Unfortunately I don't know where to get a motherboard.
 
You must log in or register to reply here.
Back
Top Bottom