Hey guys, been awhile
Finally upgraded from my Stellar (Kaiser) to HTC Desire a couple of months ago but was resisting rooting it as i believed it spoilt my Kaiser (then decided it was just crap.)
Anyway, I hate branding + i wanted Froyo, so i've been playing with my Desire today & I've made a gold card, ive followed the guide via dev forum which was brilliant.
I was expecting a blank slate to install a selected Rom from but to my surprise, found it had a rom after the rooting process, So i figured this was a Stock rom (just what i wanted), tried to Update, downloaded, rebooted, progress bar, few seconds later a red question mark appears & it reboots again.
So i assumed maybe there was something limiting about rom installed, so i downloaded....
"RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684"
and running the exe file i end up going through the standard RCC routine & getting an "Error wrong bootloader version use the correct version" message.
Any suggestions?
I've probably missed something obvious, but ive been searching & trying for a couple of hours now so if anyone can point me in the right direction from here would be great
Thanks
Edit: Just noticed posts saying about using the gold card to do updates, i shall try that & post back.
Edit 2: Tried using gold card + different rom (Stock WWE) seemed to do the trick, don't know if that was the right thing to do but it certainly worked, OTA Froyo downloaded & installed too.
Hey this is my first post, I have scoured the internets for a solution to this problem and I still can't find an answer! I have a rooted HTC Desire, and usually have no problems adding whatever roms I want to my phone. I have found a HTC Desire HD rom that I would like to flash (http://forum.xda-developers.com/showthread.php?t=789830). The thread is over 1000 pages long, and I read about 50 pages in, but no one had came to a solution!
I have partitioned my sd card (16GB) as the video on the page instructs (using Partition Wizard 5) then adding the rom file to the fat32 section of the sd, however when I reboot after flashing it just stays on the htc screen (and I mean indefinately, I know it takes some time to reboot, but it shouldn't take over an hour should it?). When installing the rom clockwork says that it flashed successfully, so I'm a little confused. I just want it to work!
I've been told to use adb logcat to see what error message shows during the flashing process, but I can't get it to acknowledge my phone unless its in normal mode. When in hboot or recovery it just says 'waiting for device'. I take it its not a driver issue because as I said it will acknowledge my phone when in normal mode. It'd be a miracle if I could get that to work first!
Sorry for being a complete n00b about this, I've spent the last 3 days trying to find a solution, but to no end! I'm not sure what other information is relevent, so if you guys could just ask away that would be great. Thanks!
Check out my post at http://forum.xda-developers.com/showthread.php?p=11918633#post11918633
Hope this helps.
Ok let me see if I can explain this in my noobish way. Downloaded and finally got installed the new Express Rom 2.0...Checked it out....worked absolutely great....set it up with my apps and ran it through the paces for a couple of hours....rebooted phone and it would not reload....strated from scratch and this time saved the programming...rebooted and the exact same thing happened....checked the tread and saw no one else with this particular problem....can one of the more learned tell me what i'm doing wrong. used alternative recovery from rom manager to install (green background) instead of my usual (blue) clockwork mod recovery....This is the first rom I've installed using this method
Problem found and solved
Hi I'm new to this, and yes maybe I shouldn't have started messing in the first place, but that's just me I can't help myself.
I was fed up with bloatware and Google so I decided to Root my Desire S using the super one click method.I have Hboot 2.00.0002 so the revolutionary method would n't work, so it worked but I still have S-ON. Everything worked great and I was able to use TiBU to clean my phone of all the junk apps. Unfortunalely I went a bit far, but that wasn't a problem because I'd backed it all up. Not the case when I tried to reinstall apps like HTCcontacts.apk, system apps TiBU just hangs and nothing happens. At a guess Im thinking having S-ON is stopping me from writing to the system folders, although it allows me to uninstal those apps. Hmm I thought OK my phone is wiped anyway I might aswell just flash a new OTA from the HTC website, an official ROM not a custom one, that surely should work. Well to cut a long story short it didn't. It got about a third the way through then failed due to security signatures or something (it flashed up quick so I couldn't read exactly what it said).
Now my phone will only boot to HTC screen and goes no further, I've tried everything but nothings working. I can enter my Bootloader and have managed to flash the ClockworkMod Recovery and have tried to install many different official ROMS from the SD card using the ClockworkMod but it always gets a third through and stops. I've also tried installing from my PC using cmd, which was doing the same but now doesn't even recognise the device.
ITS OK ALL SORTED I WAS JUST DOING THINGS IN THE WRONG ORDER
BIG THANKS TO THIS POST --------> http://forum.xda-developers.com/showthread.php?t=1275632
So having S-ON doesn't seem to matter for flashing new ROMS as there has been some confusion over that in other forums,
Wrong forum mate this is Desire not Desire S
been reported to move to Desire S forum
So I've done some searching, and have yet to find a solution to the issue I'm having. GF's phone is the HTC Incredible as you can probably already guess by what subforum this is posted in. It's been running the CyanogenMod 7.1.0 Rom for quite some time alright. From everything I've seen, most people that have had issues with bootloops is because they have been flashing to a new rom/radio and skipped something/pulled the battery/or something along those lines. This phone has been running fine, and then out of nowhere I guess, started to restart itself continuously yesterday. I can get into HBOOT no problem, but that's about it. When I try to select Recovery, it just kicks right back into the bootloop. Anyone have any suggestions??? Phone isn't under warranty anymore, and her contract ends in a month and a half, so we don't want to have to buy a new phone before then if at all possible.
try reflashing recovery.
first start with a freshly formatted FAT32 sd card, download this file and place it on it
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
this should be the only file on your SD card. now turn off your phone and put the sd card in. now boot into hboot (vol down+power) and it should prompt you to update by pressing vol up. do this and when it boots back into hboot, remove the sd card and delete the file. then try booting into recovery
Tried it and still no change
there was a similar situation (stangely similar ) here
http://forum.xda-developers.com/showthread.php?t=1628585
both cases happened to be running cm 7 too...and randomly started boot looping and stuck with no recovery.
i would read through that thread and see if any of the steps will help you
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
downwardzspiral said:
Just read threw it all, and everything sounds exactly like it does in my case. That one ended up not so well. Do I just assume that this one is done as well???
Click to expand...
Click to collapse
you can try doing the steps in that thread. you may have better luck. Perhaps someone else on this board knows of another method that may help
Just because it didnt work for that guy, dosent mean it wont work for you. Are you s-off? Have you tried reflashing recovery yet?
it's S-Off and I've tried to reflash recovery
How about an ruu?
tried that. tried through the pc and the computer wouldn't recognize it. tried by updating it in HBOOT, and after the update, it would still just bootloop
Sounds like another possible hardware failure. My only other sugestion would be to try the fastboot flash of the misc img, but it probably wont work either. Its very strange, i have seen this 4 or 5 times now in the past couple months, all on cm7, and all unfixable. I dont want to start a war, but mabey something with cm7 or cm7 and a certain program or combination of programs, is causing this. Or mabey its just cause these phones are getting up there in age.
i too find it odd each one is cm7..
Well thanks for all the help anyways. A new phone it is I guess
the basic problem is CM 7 (for the Dinc). it is extremely common. i have seen it happen to so many people now. it drives me insane when i see people suggesting CM 7 "stable" to others (for the Dinc). i have tried to communicate this here and other places too... i have given up hope of people ever accepting this obvious situation. the "stable" version of CM 7 is simply not stable.
however...
a reflash of clockwork recovery has always gotten people out of the CM 7 bootloop. then they are able to get a working rom installed.
i don't understand why you can't get a recovery re-flashed.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A