[Q] Help! I think I bricked my brand new Desire! - Desire Q&A, Help & Troubleshooting

First of all I have an unlocked Telus Desire. This is running HBOOT.83 and was rooted using Unrevoked.
The first rom I tried to install was LeeDroid 1.8 and I got a boot loop and never was able to get it running.
After installing this rom I noticed the phone started freezing at the white screen where it said HTC. I was able to go into recovery and flash Pinky just fine. I then decided I wanted to try the cyanogen mod rom so I flashed that and it was really really buggy for me.
I was able to flash back to Pinky but then I started getting Force Quits everytime I opened the market. I went to reflash the rom and now my phone doesn't boot at all.
EDIT: Now when I boot into the Rom I get a few errors popping up and then it restarts. So I can get into Pinky but it crashes and boot loops.

maybe try installing fake flash, clear all your caches and batt stats, install a basic rom just to get it up and running before you install a custom rom of choice. I have found it isn't as easy to brick this phone as say my old omnia i900 which was windows based. It could be that installing roms without clearing all yr caches is causing the glitches. I'm not an expert and don't claim to be but I always have a clear out before installing a new rom and it works for me.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk

Thanks for the advice, I will look into Fake Flash as I am not very familiar with that process.
As an update I managed to get into Recovery, and of course I flashed a rom which gave me nothing but a boot loop. Thankfully I was able to mount the SDCard in recovery mode and I am loading on one of the more vanilla sense roms to see if that works.

A lot of custom roms require you to have an ext3 partition on your SD card. This can cause bootloops if you don't have the card partitioned.
I'd also try booting without the SD and see what results you get.

You will all be happy to know the phone is no longer bricked. Recovery mode seems to be working again and I didn't really do anything to do that.

Related

When I flash roms, my desire wont boot...

Another newbie question sorry... I have successfully rooted my desire as per paul's guide.
I'm now trying to put Pays sparta rom on it but when it has been flashed and i try to boot my phone, it goes to the white HTC screen and then to a black screen with just HTC written on it.... and never gets any further.
If I go back to stock rom or the rooted one, that's fine but I cannot get this or other roms to work.
Am I missing something?
I've wiped to factory defaults, wiped the dalvik stuff etc and then loaded the rom from the SD card.
I'd love to get a custom rom on my phone but am struggling so any help would be massively appreciated.
Thanks!
jaketurbo said:
Another newbie question sorry... I have successfully rooted my desire as per paul's guide.
I'm now trying to put Pays sparta rom on it but when it has been flashed and i try to boot my phone, it goes to the white HTC screen and then to a black screen with just HTC written on it.... and never gets any further.
If I go back to stock rom or the rooted one, that's fine but I cannot get this or other roms to work.
Am I missing something?
I've wiped to factory defaults, wiped the dalvik stuff etc and then loaded the rom from the SD card.
I'd love to get a custom rom on my phone but am struggling so any help would be massively appreciated.
Thanks!
Click to expand...
Click to collapse
Did you partition your SD card while in recovery mode just after flashing the rom? That is probably what was causing it.
Try again but remember to partition your SD card before you reboot.
I had the same problem that you are seeing and it's now all ok.
As the first post in the Pays thread says, use AM desire recovery to wipe the various areas and it should then work fine.
I was just being a divvy....
It was taking ages because of the Apps2SD stuff... transferring files to the SD card.
Done and dusted now and loving Pays Sparta rom.

[Q] Does your phone require multiple battery pulls to boot up?

Ever since I flashed LeeDroid 1.8b, I've been having this odd problem. I've wiped the phone since and have flashed Open Desire 3.1.0 and I love it but I'm terrified to reboot my phone.
The phone will boot and freeze at the HTC white screen. This happens even if I try to boot into Recovery, (I can hold down vol+down and power button) but as soon as I select Recovery, it will freeze there at the HTC screen.
The only solution I have is to pull the battery and try again. It will do it around 2 - 3 times before it finally boots into Clockwork Recovery Mod SLCD or boot into Open Desire if I don't boot into recovery. This is the same if I decide to REBOOT the phone or power down and boot up.
This problem never happened when I originally flashed Cyanogen. I'm thinking there's still some files or something left that causes this freezing.. I also did a wipe and delete cache before flashing a new rom.
Does anyone else have this problem or help me sort it out?
Edit: Ah shoot.. wrong forum My bad..
no one?
Although Lee newer acknowledged it, I think it has to do with his ROM. I experienced the same issue while running 1.8b, with 1.8c I haven't rebooted by now, but still I have experienced this only after switching to his ROM and I noticed I am not alone on the ROM thread (other people are complaining too about getting stuck at the bootscreen).
I have changed many ROMs (generic 2.1, generic 2.2, pays, adamg ROM...) and never had such an issue, that is why I think it has to do something with lee's ROM.
If you have OpenDesire I would suggest to reboot it just to see how it will go.
Thanks for your response man! The problem is that I've wiped and everything and flashed Open Desire and I'm still experiencing the issue. Is there another way I can completely delete/format any traces of any previous ROM? I believe there's still some sort of remnants of his files left that are causing this!
THanks,
JD
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
TheLastOne said:
A full wipe can never hurt.
As for freezing at the HTC screen when trying to boot into recovery, I experience this too. What I have found is that if I press no buttons after booting into HBOOT, until HBOOT has tried to load from the SDCard, and THEN selecting Recovery, Recovery boots every time.
However, if I push a button before HBOOT has loaded from the SDCard, I will freeze on the HTC screen regularly.
Click to expand...
Click to collapse
I will definitely try that.. do you ever have problems booting though? I freeze on the HTC screen during boot up as well and have to do 2 - 3 battery pulls before it finally decides to boot!
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
I have, but the only wipe I perform is the one in the Clockwork Recovery. Also deleted the cache, but never have deleted or wiped dalvik cache?
I will try this later today and see what happens.. thanks!
TheLastOne said:
I do not, but hopefully a full wipe (data, cache, dalvik, etc) will solve that. Have you tried wiping everything?
Click to expand...
Click to collapse
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Tawm said:
Just sayin' I've not ever had a boot problem like this with LeeDrOiD. Running 1.8c at the moment.
Click to expand...
Click to collapse
I believe it was an issue with 1.8b..
LeeDroid said:
Ditto.. No issues, its not a rom issue, you may have bad blocks on your nand.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hmm.. anyway to confirm this? It's a brand new device, barely two weeks old and never had this issue until I flashed 1.8b.. I'm going to try to wipe it completely and go from there, hopefully that solves the issue.
What's a nand?
Hi Quazis,
I have had a very similar problem with my Telstra desire after rooting and installing a Lee based rom called NexTSense. After that I installed Open Desire and experienced the same problems.
I am just now re-rooting my phone and going to install Pinky.
Just out of interest are you running on the 850mhz Rogers network? If so have you updated to the latest radios (5.09.20 I think?)? Telstra runs off this frequency also and I think it may have something to do with incompatible radios. -- Can anyone confirm this?
If this is the case maybe try Open Desire without updating the radios?
Hey,
We got the A8182 version of the Desire which has 850/1900 (I believe), so both bands that run on 3G.
Before I flashed LeeDroid, I had updated the radio (.20) and was on Cyanogen nightly build. I had no booting problems with that ROM, but I wanted something a little more stable. I modded it as well and the phone booted up no problem, also into recovery.
Once I flashed LeeDroid, that's when my problems arose. I only wiped/formated data and the cache.. I never formated that dalvik cache. I will wait until Open Desire 3.2.0 releases today and try that a full wipe/format.
Another member said he doesn't touch anything on the phone when he boots into recovery until the phone does the SD card check.. I tried it once and it went into recovery with no issues so maybe pressing buttons before the SD check does something??
I don't, but I did a full flash, and used my separate test sd card.
plasmafire said:
I don't, but I did a full flash, and used my separate test sd card.
Click to expand...
Click to collapse
I'm going to do this.. thankfully I have't customized my phone a lot so I'm going to format both the FAT32 and EXT3 partitions and full wipe.. to do a full wipe.. there's only data/factory, cache, davlik cache and battery stats correct? If I wipe those 4 items in Clockwork, that's considered a full wipe?
JD
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
I don't have this issue with the same ROM as you.
-----------------------------------
- Sent via my HTC Desire -
Yes, not everyone has that problem (in that case we wouldn't need to talk about it - we would KNOW it). Just some people have this issue with that ROM. I would say 5% of the people have the bootloop problem, and 10% of the people have longer-than-average the bootscreen.
Still, it worths taking a look since 3-4 people from 10 participants on this thread say they have this problem with -this- ROM.
My 2 cents.
ljesh said:
Full flash wont help. I know because I did it.
I am to lazy from installing different ROMs, resetting my device, etc... so I will leave it as it is for now (LeeDroid 1.8c), and will try to reboot it as rare as possible (bootscreen takes a while, bootloop is possible too). But when I'll have some more time I will re-root and install another ROM and I am sure the issue will be gone.
Lee, nothing personal (in the end, I am using your ROM right now) but I think you should read more carefully the thread about LeeDroid. You will see many people get stuck at the booscreen and/or their devices keep rebooting with this ROM.
Click to expand...
Click to collapse
Why won't a full flash help? I don't have LeeDroid anymore, I had it for about 10 minutes because I didn't like it. I've since gone to Open Desire and the issue still persisted.. but it never happened when I had Cyanogen installed.
I'm scared to re-root because it requires a reboot and sometimes the HTC screen never goes away.. lol
hey there, its intresting to see that you have the same problem as me,
http://forum.xda-developers.com/showthread.php?t=755835&highlight=Recovery+Issue
the people who are saying they dont have a problem, i'd like to know what recovery you are using?
and what hboot you orignally came from, i.e. do you have a SLCD screen? and how did you root?
because it is now becoming obvious that leedroid rom is causing this issue as a lot of people are having problems.
during the weekend i will try flash the RUU for WWE with the hboot 0.83 included (using gold card)
and start from scratch and flash another.
no disprespect to the developer of leedroid, his work is good. just a lot of people on hboot 0.83 with the SLCD screen have issues.

[Q] Unable to flash stock

Ok, I have good information for you guys. I'm *fairly* noob, but not too bad. Here's exactly what I did:
I got a HTC Desire HD from Vodafone-Australia yesterday. I thought I'd root it, then consider cyanogenmod from there. I followed the instructions here: <cyanogenmod desire hd full upgrade guide from wiki> very closely.
I have never plugged a SIM into this phone. I've been using WiFi. Using my WiFi I downloaded ROMmanager and flash clockwork 3.0.0.5
I then did a backup. I didn't downgrade because the software number was 1.32.178.5.
I followed the instructions to get temporary, and then full SU access. This all seemed to work without a hitch.
I then flashed the engineering HBoot, specifically because it said it could help if I brick the phone.
I then flashed this radio: <radio in the wiki> Seemed to work, but don't know how to confirm.
NOW. This is where it went pear-shaped. I kind of liked the sense UI, but had been using cyanogen 6 on my nexus for ages. I wanted to see if I could flash Cyanogenmod while keeping the sense apps etc. So I told ROMmanager to flash, but NOT wipe the current ROM. I believe this was Cyanogen 6 (stable.) Can't remember full version number.
It rebooted, it flashed. Then went into a boot cycle. The cool Cyanogen loading screen would rotate a bit, then flicker, repeat. I figured "crap." And so went back into the bootloader -> backup and restore -> restored the latest backup.
I then got stuck on a white HTC screen. I figured, still stuck in a boot cycle... so I tried my other backup I'd taken when I first got the phone. White HTC screen again.
So I did a factory reset... still getting a White HTC screen. I start to panic. I tried variations on the theme of "format/wipe/flash" with no luck.
Eventually what I did was download Cyanogen 7 to the sdcard, then flashed that... and it worked!!!! PHEW. Not a brick at least.
Ok, so I figure - well now I have SOMETHING flashed, I can try flashing back my backups. No luck. Everything else leads to a white HTC screen - I've left it for hours at a time. It just won't boot.
So, ok, I have Cyanogenmod 7 running. However, my wifi now doesn't work. I turn it on, it stays on for about 10 seconds, then switches off. It never detects any wifi. In typing this, I figured I might have formated something to do with the radio... ? So I'll try reflashing the radio.
Anyway - can anyone help me? I'd really like to get back to stock if possible. In a pinch I'll settle for Cyanogenmod 7 with working wifi.
Why does only cyanogenmod 7 work? I've tried cyanogenmod 6, and several clockworkmod backups. Also this stock image <link stripped because I haven't posted enough. It was a link modaco.com>
Why does my wifi not work? Can I get stock back?
PS. I flashed the radio and it worked
PSS. I had to strip out all my links because I haven't posted enough on here.
I might have got it. I flashed Cyanogen 7, and as I said above that worked.
Now I have a working radio, I can download ROMmanager. I got ROMmanager to flash the stock ROM I downloaded -- and it worked.
Now all I have to decide is if I want stock ROM or cyanogen with HTC apps restored via titanium backup
dakuth said:
I might have got it. I flashed Cyanogen 7, and as I said above that worked.
Now I have a working radio, I can download ROMmanager. I got ROMmanager to flash the stock ROM I downloaded -- and it worked.
Now all I have to decide is if I want stock ROM or cyanogen with HTC apps restored via titanium backup
Click to expand...
Click to collapse
HTC Sense apps, in the main wont function without the sense framework which is missing from CM, so dont think you'll have much joy running them.
BTW your problem restoring your backups was due to the fact that you need cwm 2.x to flash pre-gingerbread builds and cwm 3.x to flash gingerbread builds

[Q] Please Help! Looping

Ok... here's the deal. I just decided to switch roms finally to see what is new out there. I had been running an old version of Uber Kingdom. Here is the problem I am having. It is boot looping. Relatively simple problem to fix usually. But wait, there's more! It is boot looping in every single rom I install. Sometimes it won't boot to clockwork properly either and I have to pull the battery. Is there someway I can fix this? Or is this a hardware problem (which I kind of doubt)? I just don't understand what the heck is going on. I have been flashing different roms left and right for the past few hours trying to get this thing to stabilize. Sometimes it will boot up into the rom, I will get mostly through the google accounts setup, and then it will restart, and then loop. Other times it won't even get past the white incredible screen, and then sometimes it will make it into the rom splash screen. I have attempted to install CM7 nightly, Uber kingdom, and Synergy so far. I can flash the new rom, I can mount the SD card in clockwork, but then it begins to loop again as soon as I leave clockwork.
Let me know if you need any other information.
Is there a way to just completely redo EVERYTHING, clockwork, rom, everything, just to make sure I have a nice clean slate?
Thanks a ton for reading through this novel. I am extremely frustrated.
~Will
PS, I may not get back to this thread until morning. I have to get to sleep for work. Sorry if I don't respond right away to information requests. Thanks again!
If you can mount the SD card, download the stock RUU from www.dougpiston.com, put it on the root of the SD card named exactly PB31IMG.zip, and boot into hboot to install it. Your phone should be restored to stock, a clean slate.
Tried a different SD?
Sent from my ADR6300 using XDA Premium App
How are you downloading and flashing the ROM? I had this problem when trying to do everything through Rom Manager. Even trying to flash in recovery with a ROM downloaded through ROM Manager would loop.
Update
Well, I was just getting ready to flash the original RUU when I tried one last time to restore my old Uber rom setup and it worked (whereas the last 3 times of doing exactly the same process didn't). It stopped looping at least, even though I am still running the same rom I was before. I think tonight I am still going to attempt to flash the RUU anyway and start over anew.
To answer the questions before, No, I did not try a different SD. I didn't know it could make that much difference. Still on the original one that came with the phone.
As the downloading and flashing process goes, I was downloading direct from the XDA forums on my laptop, then transferring the files via USB. I have never really liked using the Rom Manager. It cuts me out of the XDA loop and I don't get to see all the bleeding edge discussions, etc...
So I will try to flash everything new tonight, and then post my results for anyone who is curious. Thanks for the help guys!

Problem installing a new ROM

Hi Guys, i have searched a few Threads but looks like, im the first one with a problem like that.
Today i installed a new ROM from -> AOKP Milestone 4 to AOSP LIQUIDSMOOTH-v1.2.
But latley i have seen its not Multilanguage Support included. So i tried to go back to my old Milestone 4 ROM via Restore from Recovery Mode.
But its stuck in Bootscreen. So i decided to install it fresh, as i have the last Build still in the internal Storage.
But also i get stuck in Bootscreen and restarts... So back to AOSP and even that is not better, its Booting but then it tries to refresh the Apps and restarts on half way, and i made a full wipe also dalvik cache. I dont know what to do yet... anyone can help?
Silvercn said:
Hi Guys, i have searched a few Threads but looks like, im the first one with a problem like that.
Today i installed a new ROM from -> AOKP Milestone 4 to AOSP LIQUIDSMOOTH-v1.2.
But latley i have seen its not Multilanguage Support included. So i tried to go back to my old Milestone 4 ROM via Restore from Recovery Mode.
But its stuck in Bootscreen. So i decided to install it fresh, as i have the last Build still in the internal Storage.
But also i get stuck in Bootscreen and restarts... So back to AOSP and even that is not better, its Booting but then it tries to refresh the Apps and restarts on half way, and i made a full wipe also dalvik cache. I dont know what to do yet... anyone can help?
Click to expand...
Click to collapse
Can you still get in recovery? I know it is a bit drastic but relocking and unlocking your bootloader , re rooting and reflashinh might be an option. Off course you will loose all your data but you might have your phone back...
Hi, yeah thats what i have done yet!
I thought there is may another way to get on the storage and getting my files. But however, got a fresh Rom now

Categories

Resources