Develop Bugs

Please help - Desire just wont boot up after flash!

Okay guys, here's the deal:
I decided to go for a new ROM, and now I can't get the phone to boot up after installing any ROM. Even the last ROM that I KNOW worked wont start up. They install fine, bit wont boot. I wanted to repartition my SD card, so I did, which I have now set to a 1GB etx4 partition and all the rest to FAT32.
All I get is that white HTC screen, and it'll stay there infinitely.
Any ideas?

Did you wipe before flashing the ROM? You need to do a full wipe (in. Dalvik cache) before flashing a new ROM otherwise it will hang on the boot screen. Another thing to bare in mind is if you're moving to a ROM using A2SD/D2SD that first boot can take a good few minutes so patience is also needed

I did, yes. Wiped absolutely everything, and it still wont boot. I've left it for at least 20 minutes and still had nothing
Was there a specific way my card should be formatted? I basically followed this guide:
http://forum.xda-developers.com/showthread.php?t=905089&highlight=partition
Except, I did all the work in Ubuntu, and with the memory card plugged into an Xperia X10 (I don't have a card reader.

Your first partition needs to be fat, the second ext. Also if you did it while the xperia was booted it probably messed up the process, best bet is to redo the partitioning while in recovery.

DAE_JA_VOO said:
Okay guys, here's the deal:
I decided to go for a new ROM, and now I can't get the phone to boot up after installing any ROM. Even the last ROM that I KNOW worked wont start up. They install fine, bit wont boot. I wanted to repartition my SD card, so I did, which I have now set to a 1GB etx4 partition and all the rest to FAT32.
All I get is that white HTC screen, and it'll stay there infinitely.
Any ideas?
Click to expand...
Click to collapse
I am experiencing the same thing at the moment. Except I can flash the latest CM7 stable (7.0.2.1) and it works fine. Any other ROM however, just won't boot.
I have tried all Alpharev HBOOT images and several other Sense based ROMs.
My SD has first partition FAT32 and 1GB ext3
I have tried wiping everything with ClockworkMod Recovery 2.0.5.7 and 3.0.2.7 and still no success with loading other ROMs apart from CM7.
The wierd thing is that I have been happily flashing ROMs for months now. The last one I successfully loaded was ][Sense2.1 GingerBread]InsertCoin CM7 v07 and the first one that failed for me was AuraxTremeGinger v8.5-test Gingerbread 2.3.3· (GRI40 |720p|A2SD+|Fast)
It's almost as if the Boot.img is not being correctly written to the boot partition?
Any ideas?

Which recovery do you have ? I had the same issue until I've flashed Ra-Recovery or you have to upgrade your CWM.

paul.c said:
Which recovery do you have ? I had the same issue until I've flashed Ra-Recovery or you have to upgrade your CWM.
Click to expand...
Click to collapse
I currently have ClockworkMod 3.0.2.7 but I tried with 2.0.5.7 as well.
Have not tried RA yet.

hey I too have the same problem of the white HTC screen after bootup.
Background: upgraded the Orange FR 2.1 Desire to the OTA upgrade recommended without thinking. It went through partially and finally wiped out the bootloader or corrupted the bootloader on the phone. There was no backup take nor an gold card made with the phone.
So. even I am struck with a non-booting Orange FR Desire at the moment.
Boot menu shows HBOOT 0.93.001. There is no recovery program either. Can only enter into the system menu for recovery.
Tried the following:
1. Tried update using some orange ROM (update.zip) through the sdcard, but the signature verification failed.
2. Tried a couple of RUUs, but it fails with error 131. I do not have a gold card with me nor do I know the CID.
3. Access through ADB : Does not list the device itself with the 'adb devices' command. Hence no access to the phone memory. So, goldcard ultility wasnt really helpful to get the CID
RUU is able to talk to the phone. This means that the USB port is still functional.
What can I do? suggest please.

It depends on which ROM you intend to install. Desire S ports didn't support ext4 until a today when baadnewz and snq (not necessarily in that order) issued a patch. This can cause bootloops.
I had CWM 2.0.5.7 and tried to install Robocik's RCMixS and it stuck at splash screen until I switched to RaRecovery. Subsequent versions of CWM are reported to work. That is my experience.
If you need further assistance please state which ROM do you intend to install. Good luck !

Recovery affected by rom?

Hey mates,
would be cool if you could help me to understand the connection between recovery and flashed rom...
This is why I'm asking: I rooted my desire a couple of weeks ago (by applying the unrevoked method). Since then I flashed a couple of custom roms. I wasnt very happy because the most roms caused my mobile phone to crash. I thought it was because a broken sd card therefore i bought a new one today. Sometimes when my phone crashed I wasnt even able to enter recovery anymore. And sometimes it did just nothing... I couldnt even enter hboot (it just didnt boot - like it was briked - only the charging led was on when i plugged the charger in). In this case I had to remove the battery a couple of times or plug in the charger. Usually I needed to do this many times. This is btw. why I'm fed up with custom roms but maybe its just my mistake. And now finally my question:
Why can I enter recovery sometimes and sometimes not? Does this depend on the rom? Why do I have to remove the battery etc. to make it run?
I know flashed back to the rom I of which I created a backup after root. But it seems that my phone is more unstable since then (even if its just my rooted stock rom)
Thank you for your answers...

What rom are you on? Maybe your recovery is a bit messed, have you tried reflashing it? Btw, s-on right?

If your not able to get to your hboot then there is something wrong with your phone. It will most likely be able to do with your hardware. You can use an ruu to restore everything back to factory default. You could then root again and see if that will help. But it does look like to be a hardware/corruption issue.
Swyped...

Your Desire maybe being one of the new PVT4 new nand would might cause this. I know that the latest version of unrevoked and Clockwork recovery can't be used to root the PVT4 new nand. I had that problem and the fix for me was to use an earlier version of unrevoked and flash Amon Ra recovery instead. There's a thread around the forums regarding this. Check first if your Desire is of the new PVT4 model. Can't post the link but there's a thread that explains how you can check if your Desire is PVT4 new nand. Would post the link but can't yet, but a quick search should take you to it.

hey guys, thank you very much for your fast answers. The desire is s-on. I'll try an official ruu. If I'm brave enough I'll root again . The strange thing is that I can enter recovery but not always. A hardware issue would be awful. I'll let you know how it went. I hope it is ok to just use ruu to update a rooted rom. It flashes a new recovey too, doesnt it?

Ok, i tried to use ruu to unroot my device. It told me that my bootloader was not compatible and canceled flashing. But it also broke my rom. I couldnt boot the system anymore and i couldnt boot into recovery. I dowloaded a ruu image (with my radio) to flash it via hboot. Everything seemed to go fine but after the first restart i'm stucking with an update sign (i guess its the recovery menu) - a mobile with green arrowrs. I think its frozen. Do i need to do anything else?

Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.

Lovebongo said:
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Click to expand...
Click to collapse
Yeah best to send it back, it sounds more like a fault with the device

HTC Desire Boot Loop after Rom Backup - Solved but .....

I am a newbie in this rom flashing land.
I managed to root my Desire this morning using unrevoked 3 method. It was successful. I then installed Rom Manager (free) from Market and tried to make a backup. It ran smoothly until the phone rebooted. The reboot looped at HTC logo.
After searching around, I go to Recovery and restore the newly backup image and the phone went back online. I thought I had bricked my Desire already. .
I have the following questions, please enlighten me:
1) What might cause the shocking loop?
2) In the unrevoked 3 program, I notice that the "Disable Security" was checked when I managed to root the Desire. Does that mean I have S-OFFed the Desire as well in the process? If it is still S-ON, how can I tell and if I download a ROM and try to flash it (I still don't know how), will there be any undoable problems?
Thanks

1. Probably ROM Manager - use the flashed recovery - it works all the time.
2. Unrevoked3 does not S-OFF your phone, you need alpharev for that. To make it sure turn off your phone and reboot to bootlader (Holding VOL- and POWER keys). For the ROM part, check each ROM's thread for requirements to avoid problems.

Hi nqk.
I have only been looking into rooting for a couple of weeks and had the very same experience as yourself. (and the security off bit too). Bricked already!!
Before I had S-Off I tried both CM7 and oxygen, they both worked ok, but if your reason for rooting is the gain memory with the desire I would certainly say go down the alpharev road and use a new HBoot.
The stickies on the development section really do explain it well for us "noobs".
Currently I am running Oxygen 2.1.4, Alpharev oxygen r2 HBoot and S-Off running a 1GB ext4 partition.
Just so giddy with the amount of space available!!

I flashed new custom rom with s-on and stock hboot. Everything is fine so far.
Sent from my HTC Desire using Tapatalk

few times when I have rooted using unrevoked3.21 and run a backup from Clockwork recovery 2.5.0.8 (?) it has stuck on the htc screen... not a great problem as I have usually flashed it straight after - but still annoying

Lothaen said:
few times when I have rooted using unrevoked3.21 and run a backup from Clockwork recovery 2.5.0.8 (?) it has stuck on the htc screen... not a great problem as I have usually flashed it straight after - but still annoying
Click to expand...
Click to collapse
It happened to me when it was still connected with pc via usb cable. You can try removing that.
Sent from my Desire HD using Tapatalk

Stuck in non funtioning RUU Froyo with S-ON

Hello. I'm in a bit of a bind which I cannot get myself out of, so I am posting here. I've been around for over a year lingering, updating, trying new things, etc. I came across a free Incredible, which I attempted to root, and install a ROM onto. I rooted the phone with Unrevoked 3, booted into Clockwork mod recovery, made a nandroid, and installed the ROM. The installation was successful, however, on boot after the HTC splash screen the phone vibrates 5 times and the led flashes green constantly. The same thing happened when I tried to boot into recovery.
I found that the phone booted to the Set Up, which crashed, if it was plugged into a computer. I ADB saw the device but I could not push files or execute commands. Unrevoked S-OFF would not work also.
After Googling, I found a 2.2 RUU, which installed successfully, but I get the same boot problems. If the USB is plugged into a computer before the phone is turned on I actually get to Android and can play around. The phone will not recognize any memory, SD or internal; only phone memory is recognized. I tried ADB again with no luck, most likely has to do with the phone not recognizing memory. So I flashed the RUU from HBOOT which flashed fine, but the same problems still persist.
I am out of ideas, which I hope someone has anything I can try.
S-ON
HBOOT 0.92
MICROP-0417
TOUCH PANEL - ATMELC03_16AC
RADIO 2.15.00.07.28
Edit: I tried to be as detailed as possible, so ask any questions if I did not make since.

Check this out
http://pvillecomp.com/?page_id=33

Thank you, trying it now.

cmlusco said:
Check this out
http://pvillecomp.com/?page_id=33
Click to expand...
Click to collapse
I cannot thank you enough.
Edit: Unrevoked gave me s-off. I want to be clear this time before I install any ROM. Do I need to run unrevoked-forever.zip? I am 99.999% positive I do not since I already have s-off. I want to get a new ROM on tonight.

Unrevoked 3 now contains the forever patch, as previous versions did not. So you are good to go flash away, after making a nandroid of course

No need for unrevoked forever if you are s-off

Thanks! On my way to a new ROM.

[Q] Phone possibly bricked but it might be saveable!

Hi,
My first phone was rooted and I rooted my second too so I am confident rooting them however my second phone which had been rooted for a while had a space issue on SD card so I cleared out a few things which unfourtunatley included all the backup files ....
It worked fine afterwards but didnt let me change rom (using rom manager) so I just left it in working order for a few months until I wanted to reflash a new rom (as I am sure most people do every few months)
When it didnt let me, I tried to unroot and root options using superoneclick and unrevoked3 however, unrevoked 3 just stayed on "running root" and superoneclick got so far and crashed. When I go into the bootloader, it says something about some filed missing (think might be some nbh files).
At the moment, when normally turning the phone on, it stays on the screen with the pink circle, the first boot screen.
I have tried updating it using the RUU but it takes a long time and then says "use the correct rom for your device" which I am, this method just boots my phone and goes to a htc logo.
I can also get into the bootloader but when I apply update.zip, it says it has failed and something about files not existing/step 7 failure.
The thing is, I can get to fast boot and I am sure there is a way via ADB to force a new image (such as a cyanogen recovery image) on to the device.
Can anyone tell me how to push an image to the phone without using the RUU (as this didnt work for me)??
Maybe my phone is just bricked
Thank you very much!!

It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)

Thanks but I do not have another Desire...

Any card reader

yeah, I got a card reader laying around somewhere, if not ill go get one in Tesco, what where you thinking?

bortak said:
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Click to expand...
Click to collapse
Hi Bortak, I am having similair problems with my phone sticking on the pink circle screen. I cant seem to load a recovery file from Bootloader. Will I need to make a Gold Card, my phone is s-off.
thanks mate

if phone is S-OFF go to my guide, look at advanced boot problems S-OFF.

SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!

Mugube said:
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Click to expand...
Click to collapse
#facepalm#
Translation: I flashed another ROM because my other one didn't boot.