[Q] Long first Boot on Revolution HD 3.2 - Desire HD Q&A, Help & Troubleshooting

Hi there,
well, today i flashed Revolution HD 3.2, aswell as the recommended radio.
Did a full wipe and installed the rom as usual, no errors.
I know, first boot takes some time as i had to wait about two to five minutes on HD 3.0, but here i'm waiting for like half an hour now.
Allready reinstalled once, formatted the sdcard, same thing happens.
Is this normal behavior?

It probably shouldn't take 30 minutes.
Try to wipe everything manually in recovery.

Did that.
Still nothing.
Funny thing is, Leedroid works just flawless.

Did you check to see that the Md5 checksum matches? Try redownloading the ROM.
edit: Also, you apparently shouldn't flash radios through cwm, in case you hadn't heard.

Checksums match.
I flashed the radio according to mikes readme file.
So, Leedroid works flawless, flashing revolution hd again, same error.
Can't be the radio, switched to the old one already.
Just weird.

That's very strange.. Are you flashing any themes or nosense scripts along with ARHD? Or have you modified the ROM with a cleaner?
So you have a running leedroid, you boot into recovery from clockwork, wipe everything manually from recovery, then flash the ARHD zip? Strange how it's not
booting.
Just try to redownload the ROM to eliminate any problems with your specific file and try again, that's the only thing I can come up with.

It's running now.
Did another wipe and changed the sdcard to a 16 gig one, which seemed to fix it.
Weird, but anyway, it's running.
Thanks for your help guys, much appreciated.

I believe first boots always take longer than normal (up to 60mins) because of building dalvik cache

Related

[Q] Stuck at bootscreen after every single custom ROM flash.

hi
I´ve rooted and flashed my desire several times. rooted with unrevoked3 everytime and tried different roms like leedroid 2.2d, 2.2 f and rcmixhd 0.13. First time i did it i flashed leedroid 2.2d and it worked fine. After 1,5 months running leedroid my phone rebooted due to the overheating problems that 50 % of us suffer from (i rebooted it manually several times during those months and it worked until this day).
It got stuck at the bootupscreen with white background and green HTCtext. couldn´t install RUU via windows, had to grab the PB99IMG.zip onto my SD and boot into bootloader and restore my phone this way. Then i rooted it AGAIN, and flashed rcmixhd 0.13. Success! But only until i rebooted it manually, stuck at bootupscreen again.
I restored the phone from SD with pb99img as earlier. Flashed rcmixhd again and made sure i wiped everything (dalvik, cache, formatted sdcard and created a EXT), success! Until i rebooted my desire...back again.
Now im running stock non-rooted froyo. I´m getting tired of spending the night fixing it but i still want to use senseHD and i like tweaking stuff..
Do any of u guys recognize this problem and what can i do to fix it?
If any of you are from sweden, plz answer in swedish!
Same problem here, the only way i got to install a custom rom was by installing update-cm-6.1.0-Desire-signed.zip. Then installed a custom rom by using the "Rom Manager" tool.
Downloading and flashing through recovery mode, "No, can do!"
Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?
Suddenjr said:
Ok, but "update-cm-6.1.0-Desire-signed.zip" isn´t that a custom ROM? Did you install that through ROM manager?
And did you flash another ROM on top of it?
Click to expand...
Click to collapse
yes this is a custom rom, i did a normal flash first to "update-cm-6.1.0-Desire-signed.zip" (some how that worked???). Then i reflashed through the "ROM manager" tool.
Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.
remmyhi said:
Do you remember to always wipe everything in Recovery before flashing a new rom?
Seems like I always used to have a bootloop or bootfreeze when did not do the proper wipe.
Click to expand...
Click to collapse
i wiped everything even the Dalvik Cache, didn't help a thing.
Could is be that is has something to do with rom's that are not signed?
I have this same problem now, any possible sollutions?
Perdonally i would suggest to reformat your sd cards and try again. Dont forget to wipe everything.
Sent from my LeeDroided Desire HD
Happend to me once or twice.
What to do is, Turn of the phone take out battery do the neccessary wipes and formatting,
root
install clockwork mod from market, go to it and choose install recovery
install rom
install kernel (might affect it somehow)
reboot

Cyanogenmod Problem wiping

Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
aheavyguy said:
Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
Click to expand...
Click to collapse
If this ONLY happens to you when using cyanogenmod roms, then you are not alone. The exact same issue happens to me also ONLY when using CM 6.1 and CM 6.1.1. I have never had this issue with any other rom, both aosp or sense-based, except with CM 6.x roms.
Sent from my HTC EVO running Myn's Warm TwoPointTwo RLS 4 loaded with all the goodies
Yea for some reason these last 2 releases just wont work right on my phone. Which def sucks because I love Cyanogenmod roms. Anyone have any suggestions as to why this might be happening?
Try the following:
Wipe data+cache twice
Flash sense ROM
boot
wipe data+cache twice
verify MD5's
flash CM
flash gapps
U recommend clockwork or ra
What? This title for a thread and no poop jokes? The Internet makes me sad.
Seriously, though...
I'm partial to Clockwork now because I use ROM Manager Pro. AmonRa was the one I always used on my Hero. Both are good. It's yet another "personal preference" thing.
CM6 Issues
I too have had trouble with CM 6.0 and 6.1. I flashed CM6.0 Stable, and could not get apps to install or uninstall after flashing. I tried restoring an earlier Nandroid backup of my previously working HTC Sense ROM, and still could not install/uninstall any apps. I tried clearing Market cache, fixing permissions, wiping cache, Dalvik cache, numerous reboots, and flashing earlier ND backups with no luck. I finally bit the bullet, flashed Stock RUU, and had to reroot to get phone working properly again.
Think I would have learned from above, but being flashaholic that I am, I flashed CM 6.1 when it came out. Exact same probs, and again had to reflash stock RUU and reroot.
No more Cyanogen mod for me. Nothing against CM, and it may work great on some people's EVOs, but its only caused me headaches.
Good news is I'm getting pretty damn proficient rooting phone using old-school manual adb shell/rageagainstthecage/chmod exploit method, having done it three times now (although I hope I don't find myself in this situation again).
YMMV
Me too. Tried with both clockwork and ra...no dice. Problem is, when I went back to warm, it left pieces and now even warm doesn't run correct. I tried wiping twice and clearing the dalvik too. I know it wasn't erasing everything because there would be apps that were already installed. Like it was installing to a partition, though I have never set that up.
...

[Q] CDMA USCC Desire stuck on white HTC screen! Please help!

I tried to flash the only pre-rooted 2.2
http://forum.xda-developers.com/showthread.php?t=947481
I was s-off before I flashed this and still am after obviously. The first time I flashed it, it worked no problem. I forgot to back a few apps up, so I formated and restored a nandroid back to 2.1 - still no problems.
I get the data I need and format again, then flash the rom from above. It gets stuck at the white HTC screen every time. I have waited for over 25 minutes and it never does anything. I have made sure to format boot,system,data,cache each time and it won't work.
I have clockwork 2.5.0.9 - I am just sick right now that I'm never going to get this working.
I have also tried a second sdcard with no luck.
I have tried both roms on that page (radio included and radio not included)
Please help... anyone???
Ok..............
so maybe all it takes is a post on xda to fix it!
Just to try something different, after a failed attempt to flash the rom, I went into clockwork and only formated data/factory clear, and then flashed the rom. It worked now! Can someone at least explain what I was doing wrong?
I feel like a noob but coming from the EVO (desire is my GFs phone) I format boot,system, etc before I flash any rom.
As per my first post in that thread, a FULL wipe is needed before flashing the ROM
I had been doing a full wipe before each and every time. It seems like manually wiping each partition one by one doesn't really do anything. I'm not used to clockwork as I run a different recovery on my EVO.
I'm still unsure what happened, and why it worked this time. When it did finally work, I didn't wipe the boot and system partitions before flashing the rom. ???
Am I able to flash a newer clockwork on this bravoC ?

[HELP] Bootloop sense roms... (Stock Table)

I recently moved to CM7 and S-OFF. I used the alpha-rev method and flashed the CM7 hboot
Seeing the new Leedroid GB rom, I figured I'd give it a try. So I did a full backup, wiped everything, flashed the stock Hboot from Alpha-rev website, then flashed the Leedroid rom and... BOOTLOOP.
I then tried version 2.4, and same thing.
Following this I flashed Redux, which was nice but slow and I was able to confirm that I had 148 Mb of internal memory...
I then redownloaded Leedroid 3.0.5, thinking my file was perhaps corrupt, and still nothing...
I even tried restoring an my old CoolSenseHD 9 nandroid, which passed the splash screen, but looped at the boot screen.
Any ideas??
I had a similar problem. Go into CWM and format system, data and cache.
Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???
i think your recovery is outdated, this can cause bootloops, something to do with your recovery version not able to handle new updater-script.
so update your recovery, you dont have to remove current one, just get the fake-flash.zip of any new recovery (clockworkmod 3.0.2.7) put it on ur sdcard, then in AmonRa select to flash the fake-flash.zip file and it should boot up CWM. then wipe all and flash the ROM.
other than that make sure you have correct partiton layout on ur sd (ext needed ofc) and obviously, correct hboot table.
I tried flashing the latest CWM, then wiping everything and flashing leedroid, but no luck. Then I tried putting AmonRA recovery back, and I tried once more, but still no luck. Then I tried flashing the latest Gingerbread MIUI, and that worked like a charm....
So that rules out my recovery being outdated, and I did flash the latest Radio, so that's good too... I really can't pinpoint the issue, but regardless, I'm really liking MIUI, so that's good I guess.
And as for partitioning, my SD card had a 500MB EXT3 partition for Leedroid, as specified on his page, and my partition table was set to Stock Bravo. I reflashed that Hboot about 4 times just to make sure...
TheSobadef said:
Well I'm on Ra-desire-v2.0.0 recovery, and when I do full wipe, it formats everything... something I've done about 10 times in the past 2 hours...
Any other ideas? Is RA somehow incompatible with sense? Should I switch to CWM with fastboot?
EDIT: I've managed to get a stock rooted rom to work... So why not LeeDroid???
Click to expand...
Click to collapse
As I said, I had this exact problem and solved it by formatting system in CWM. I could flash certain Roms like redux but not leedroid.
AmonRA does not have an option to format system, just wipe which is different.
But even with CWM, I couldn't do it...
I'm guessing it's because the boot.img is too big in the leedroid GB rom, and you have corrupted blocks which limit the allowable size or something. I have that problem with my Desire with certain roms.. which really sucks. Maybe it's because we have Telus branded Desire's lol....
Well I don't believe the Telus Desire is branded (no telus bloatware like other phones, no logo or anything)... I mean I never had to make a gold card, and I haven't been on stock since december...
I just find it wierd that I used to be able to run Froyo leedroid (version 2.3d), but now that I try and flash 2.4 (also froyo) or 3.0 (GB) I have no luck
Have you tried using the RUU to get stock ROM, use Unrevoked and then get the LeeDroid version you wanted?
Are you trying to load htc sense roms on cw7 hboot? Of course it won't work, there is not enough space for the rom.
^If you read my posts, you would know that I have not been using the CM7 HBoot, but the stock Hboot, which is why I was able to load a stock rooted sense rom.
The thing is, I'm afraid to use and RUU because Telus didn't modify their roms in anyway, so carrier RUUs don't exist, yet the phone is locked to Telus... I haven't created a gold-card yet because I haven't had to, yet I feel as though an RUU can jeopardize all of this.

[Q] Help with installing newer ROMS

Hello, I could use some help with my Desire.
A few months ago I rooted my HTC Desire (Bravo, EU version) with Unrevoked3 and then tried a couple ROMS, like CM6 and MIUI. The installations all went fine without any problems and the ROMS worked as advertised.
I decided to go back to the stock 2.2 because of some app compatibility issues, using the backup I made from the recovery tool and have stayed with it since.
Now, whenever I try to install a newer ROM, like Aurora v04 or PyramidMod007, the installation never works, even though I always wipe/factory reset/wipe Dalvik cache before installing. The post-installation booting always freezes on the HTC logo screen for more than 20 minutes and I'm forced to remove the battery and restore my backup image.
The only ROM that I've tried and works is the latest MIUI.
Can anyone tell me what I'm doing wrong?
Are you wiping?
Are you downloading versions that fit in the stock hboot, NOT cm7 hboot?
Are you following ALL the instructions/requirements in the rom threads, including required partitions on SD card?

Categories

Resources