[Q] BootManager fail - Desire HD Q&A, Help & Troubleshooting

I wanted to install ICESene over my Icecoldsandwich but then i get the error that the editing of the boot.img has failed what can i do??

Force large boot img
Sent from my HTC Desire HD using xda premium

again error at building new boot.img...

Not sure then, soz...force large boot img did the trick for me
Sent from my HTC Desire HD using xda premium

I have the same issues with boot manager: failing at creating boot.img. And the annoying thing is that the time to discover this is incredible long.

i tried it 5 times yet -_- with wiping etc. but i ever got the same issue..

Try to PM jkoljo, mabe he can help you.
He is DHD guru on this level

Try install the ROM by the NANDroid backup alternate method. But either way, the app just won't work anymore for me.

That happened to me too, but I tried it again and didn't touch my phone till the process was complete. I could boot into ICESense without any problem. Try it again with force large boot image turned on, set your screen timeout to 1 hour and leave the phone alone while it installs. The first time I was doing some other stuff on the phone and got the error, second time left it alone and worked fine.
Sent from my Desire HD using xda premium

Same error from me... Maybe main Rom must be Sense Rom?
Sent from my Desire HD using XDA

I´m using IceColdSandwich at phoneROM and want ICSEnse on SDCard

Bump. I'm having the same issue, but with my OG EVO 4G. So this problem isn't device specific.
I have AOKP installed on phone rom. Have the error reoccurring.

Related

[Q] Cyanogenmod7 Nightlies

Hi,
For some reason in rommanager I can only see up to #13 for the cyanogenmod nightlies?
Does anyone else have this problem?
The reason I bought the paid version was to get access to all of them.
Thanks
Paul
Well you got ripped off because Rom Manager is ****. Seriously, you should NEVER flash anything with Rom Manager or have it installed at that. Just download it from CyanogenMod, put it on your SD and install it via recovery.
Rom manager does what it is supposed to do and does it well.
The reason you do not see anymore nightlies is because there are no more. The nightlies got reset after RC1 was released. There isn't a new njghtly every night because sometimes there is no successful build.
Rom Manager does everything really poorly, seriously. It is useless and causes so many problems.
Meaple said:
Rom Manager does everything really poorly, seriously. It is useless and causes so many problems.
Click to expand...
Click to collapse
Care to elaborate?
Sent from my HTC Desire using Tapatalk
The main issue(s) is when you reboot. Say you flash a rom, when you reboot it tends to just reboot and not flash the rom or anything. It does stuff like that. Rom Manager tries to be the recovery but whilst booted up but fails. Fair enough, it works for some people but so many other people have problems with it. Ok, it has been developed for "noobs" and yes, I did kind of use it at first but then I found out from my own experience it didn't work too well. I think that people should forget about Rom Manager and just boot up into recovery and just use that since the recovery actually works, and only takes a reboot (depending on your rom) to get into it.
Why, do you like it?
I've noticed same issue with the nightly. I've tried manually flashing the newer ones, but get an error on the device check. So rom manager is correct 13 or RC2 are the latest that will install
Sent from my HTC Desire using XDA Premium App
Am a bit of a newbie to the custom rom world. So far rom manager has worked fine.
Am currently on cyanogen rc2 and have flashed my radio without problems. As a Java developer and a phone geek people think I am mad for mucking about with my phone so much.
The question was because I thought I had read there was a nightly 15.
Sent from my Desire HD using XDA App
I have had the same issue with Rom Manager. I had to download directly from the Cyanogenmod site
Just flashed 17 and it seems to be really fast!
http://mirror.kanged.net/nightly/bravo/
or directly to 17
http://mirror.kanged.net/nightly/bravo/cm_bravo_full-17.zip
Cheers
Which desire do you have GSM or cdma?
Sent from my HTC Desire using XDA Premium App
Uk desire HD gsm
Sent from my Desire HD using XDA App
That version worked for me thanks
Sent from my HTC Desire using XDA Premium App
Just realised, that is the bravo version, cyanogen points xemacs desires to bravoc. Still seems to be working fine
Sent from my HTC Desire using XDA Premium App
I don't know if it's related, but I had trouble with CM7 RC2 when installed through ROM Manager, but manually flashing the CM7 Nightly #17 worked just fine. I wiped the caches etc. on both tries (or rather, ROM Manager did on the RC2).

[Q] Sense "stock-lock"

Hi there,
Today i have installed the new 3.2 Revolution ROM with no-Sense.
I tried to restore the stock-lock with flashing the file attached to the post of Revolution, and got the result lock as shown in the screen shot. Tried to install a custom lock after, the result was the same bugged lock. Any solution avaiable for it?
Thanks in advance.
Anyone encountered this error? Really could use some help.
Sent from my Desire HD using XDA App
Bump
Even with custom screen locks, the screwed up "default lock" flashes up sometimes for a sec.
Clueless
Sent from my Desire HD using XDA App
Delete thread please, i have rather re-flashed the 3.2 ROM without no-Sense.

[Q] Virtuous Unity 1.31.3 Bootloops and Freezes

I've liked everything I've read about Virtuous Unity and I want to give it a try. Unfortunately, everything I've tried gets me no where. I have tried installing 1.31.0 followed by the 1.31.3 patch and also the new 2.35.0 followed by the Inc2 patch. I have tried wiping everything I can find. I have done all the wipes in CWM and even started with a fresh SD card. Some have reported success coming directly from the CM nightlies. I tried that and got nothing different.
Here is what happens:
The flash goes great.
If I try to install the radio .zip flash, the install aborts. I can't remember if I successfully did that early on or not.
When booting, the phone may loop between the white HTC screen and the black HTC Quietly brilliant screen.
It may loop between the lock screen and the HTC Quietly Brilliant screen.
It may lock up at the HTC Quietly Brilliant screen where it could stay for an hour before it reboots.
It may lock up at the lock screen where it could stay for an hour before it reboots.
I noticed when it was locked up at the lock screen, my computer was reporting the phone connecting and disconnecting over and over.
Can anyone help?
How are you trying to flash the radio.zip hboot or recovery?
Sent from my ADR6350 using xda premium
If your talking about the pdimg.zip that is flashed in hboot not recovery you may already know that though. If u are flashing through hboot make sure its named exact and not .zip.zip if you renamed on a computer it automatically puts a .zip on it. Also there is a new version of unity out 2.3.5
Sent from my ADR6350 using xda premium
I did not realize the radio update needed to run via HBOOT. It does appear to update properly there. So, I guess that is fully installed.
I have tried the new 2.35 Unity ROM and if I remember correctly, it would only get to the lock screen and then freeze.
Very strange try it after you install the update package in hboot. Also I would advise going to ROM manager and flashing a new recovery because that unity hboot package gives you an older recovery
Sent from my ADR6350 using xda premium
I had already allowed it to update via HBOOT. I have also already installed the latest CWM. I can't get the version number without rebooting but I believe the minor revision number was 8. I'm thinking it was something like 4.0.0.8. This happened early on after seeing the problems start. That was one of my first thoughts.
The newest cwm is 5.0.4 or something like that I know for sure it starts with a 5
Sent from my ADR6350 using xda premium
I would get ROM manager and flash the latest because that hboot zip replaces your recovery and i had issues with it. The newest cwm is blue instead of orange if that helps at all
Sent from my ADR6350 using xda premium
The developer has said it isn't being rolled out to all devices yet. I allowed ROM Manager to download and install the latest.
Nevermind...I just tried it again and I have a newer version. I did it before from another ROM (maybe 3 days ago). I used ROM Manager and it downloaded what I assumed was the latest. I don't know if something changed between now and then or what.
I'm waiting on an email right now so I can't flash but I'll try it a little later.
Thanks for pointing me in that direction.

[Q] Flashing new rom, frozen on HTC screen...

I have posted this in the General section, however i think it should be here...
I'm updating a HTC Desire for a family member, the last rom installed was a villain 2.4 rom (it's been a while). I've updated the radio to the latest version ending in .23 and tried to flash the latest RunnymedeMod007, this is where I've encountered the problem. Im stuck on the opening HTC boot screen. And don't understand why, there's no reason for the freeze as far as i know. Should also note I've cleared every cache and wiped.
The second issue is that when there is a rom installed, the camera doesn't load and force closes.
Does anyone out there have any ideas why I've got these problems and could you help me out?
Cheers
have you wiped it a multiple times?
was sorted when I had the same problem
Sent from my HTC Desire using XDA App
I've tried countless wipes and still ended up at the same point with the HTC screen.
I've followed the tutorial here; http://forum.xda-developers.com/showthread.php?t=1275632 for the problem but still nothing.
Any suggestions?
ext partition?
Swyped from my CM7.1 Desire using XDA Premium App
Ext partition,full wipes and flashing rom
Tapatalking
ironjon said:
Ext partition,full wipes and flashing rom
Tapatalking
Click to expand...
Click to collapse
Give details of Device and the method
I'll sum it up quickly for everyone, I'm not a desire user and simply don't understand the system of flashing, could anyone explain what I have to do in noob language? or a tutorial thread that explains it all would do. Thanks for the help by the way.
Try this...
http://forum.xda-developers.com/showthread.php?t=814381
Root guide - post 3 - Flashing a ROM
Hope it helps.
try a different rom too. just might be the rom that u may be using
Sent from my HTC Desire using XDA App

[Q] Camera doesn't work after ROM flashing

Hi everybody,
last Thursday my phone had a boot loop, so I've decided to change the ROM.
I flashed my HTC Desire with Runny ROM 6.1.1 and since that time my camera doesn't work, flash either.
When I try to start camera app there is only black screen and phone restarts in 10 seconds.
I was trying with other ROM and official GB, but camera is simply dead.
Is there anything that I can do with it? Install some fix or update?
I have latest radio and cm7/r2 hboot.
Any ideas?
Do u test it by installing any camera app from play store?
with many apps but still the same effect
Try installing an AOSP build and check your result....what caused your phone boot loop?
Did you do a full wipe?
Sent from my HTC Desire using XDA
What is AOSP?
Yes, I did full wipe and build the partitions on sd-card from scratch.
Sent from my HTC Desire using XDA
AOSP is an original android rom, without HTC Sense or any other interface.(like sandvold's ics)
Sent from my HTC Desire using XDA
twisted_forever said:
Try installing an AOSP build and check your result....what caused your phone boot loop?
Click to expand...
Click to collapse
I don't know what caused boot loop, but I've tried cache and dalvik wipe, without success.
I will try later to flash some AOSP ROM and write here the results. Anyway I've tried already to flash RUU Gingerbread and camera was dead.
There's still no camera on AOSP Sandvolds ICS.
I think that I will disassemble my Desire and check the connections.
Wipe everything.
Boot, system, data, cache, dalvik. Then flash the ROM again. Wiping everything before flashing should be standard procedure for you.
I did it 3 or 4 times in a row. Nothing changed.
Sent from my HTC Desire using XDA
Hardware problem, try with connectors, but I think that you'll need a camera replacement.
Sent from my HTC Desire using XDA
ok, I disassembled my phone and checked all connections. Camera still doesn't work, but phone don't switch off when I try to execute camera app.
I will try one more time to do something with software.
Hi guys, ich disassembled my Desire one more time and guess what. There was one contanc loose. On the lower main board the left board-to-board connector. I put it into the socket and now everything works perfectly!
Anyway thank for your tipps guys!
Sent from my HTC Desire using XDA

Categories

Resources