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 !

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

[Q] Phone Bricked?

I had a few problems with my HTC Desire he won't start after I did an update of Insertcoin (I did this update, like every other update).
So I thought that I had to re-root my phone.. Bad idea I think.
Now my sd-card is formatted so I don't have my gold-card anymore
and I can't boot my phone.
When I boot it, in the top right and left corner and bottem left and right corner there is the debugging logo (so the triangle with the '!') and in the middle of the screen HTC logo.
EDIT: I also cannot go to the bootloader or fastboot I can only see the screen above nothing else.
EDIT2: I tried and original RUU but I don't know which one I had to use..
I don't know what to do, so please help me!

Sounds like you've flashed the wrong RUU. This happened to me, I've got a Vodafone Desire, flashing the newest HTC Europe RUU restored my HBOOT but still didn't boot (so you could try that I guess), so I used fastboot to flash recovery and then a new ROM. Good luck to you.
Oh yeah also, if you've installed a custom HBOOT and then tried to use a RUU it may be the cause of the problem since it wouldn't have been able to flash the system partition. Although it doesn't appear as to be working, I tried to flash the stock HBOOT through fastboot when my phone was like that, and after the RUU finished installing I did have the stock alpharev one and not my cm7 one.. Just something that might come in useful.

I've tried this solution here but it doesn't work for me.

Yes, it's working again.
This is the solution.
I downloaded this RUU and install it and now it works

Stuck on boot logo and anim., no ROM will work?

Hi guys!
Today, I was messing with my Desire (S-OFF, rooted, stock android 2.3.3) and I had to do a factory reset (I went to settings and wiped all data (including SDcard))...
So after that, the phone DID work, but Superuser had constant crashes and I didn't have root (no matter how many times I flashed the su or su binary .zip).
And I decided to go with a custom ROM, so I put a NAND backup of Aurora v6 (sense 3.0 rom) into sdcard>clockworkmod>backup.
Tried that and it didn't work... I was stuck in a loop:
boot logo>boot animation>power off>repeat
So I took the battery out, went to recovery and mounted my SDcard to my PC and put the ROM's zip file onto it... Tried installing and it didn't work (again, the boot loop). I also tried with a different ROM (runnymede's sense 3.5), but the result was the same...
Does anyone know what I did to pi** my Desire off so much?
And how do I fix it?
I've been at it for hours now, but no matter what I do in recovery (or hboot or fastboot), nothing seems to work!
EDIT1: Downloading a stock RUU, hope this helps...
EDIT2: The stock RUU didn't work... Guess I'd have to have a working Desire for this...
EDIT3: I've noticed that the boot animation isn't HTC's anymore... It's text, saying 'android'... Now I'm really out of ideas...
EDIT4: I pressed the 'clear data' or something similar button in bootloader... Seems that caused the weird boot animation? Trying to flash ROMs now

A few questions first:
1. Which hboot do you have?
2. Which RUU did you use?
3. What error did you get using RUU?
4. Which method for RUU did you use (run from PC or PB99IMG.zip?
5. How you did partition your sd card and did you make sd-ext (all advance roms sense 3.0 and 3.5 require sd-ext)?

Do these ROMs require ext partitions. Check in ROM threads. If nothing works best to downgrade hboot and run ruu 2.3. Thereafter run revolutionary.
Sent from my HTC Desire

A few answers (only correct if RUU is sort of an android installer)
1.I have the stock hboot (unless I broke that somehow with all my button pressing...)
2.The RUU's name is RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
3.Well, since I was only able to try in the bootloader and in the recovery (mount USB storage), both times the error was the same; the installer was unable to detect my Desire...
4.I don't quite understand that (I'm a noob when it comes to 'codenamed' thingies)... What I did was I just downloaded the .exe file and ran it
5.I've tried both with a completely blank SDcard and a partitioned one (256MB size, 0MB swap size)...
Just to point out though that the Aurora ROM didn't need a partitioned SDcard the first time I installed it (when my Desire wasn't in this weird state).
Thanks for your quick reply!
EDIT1:
@handy5876: Yes, they both recommend an ext3 or ext4 SDcard partition. But as said above, the Aurora v6 ROM worked just fine with no partition at all!

someone755 said:
A few answers (only correct if RUU is sort of an android installer)
1.I have the stock hboot (unless I broke that somehow with all my button pressing...)
2.The RUU's name is RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
3.Well, since I was only able to try in the bootloader and in the recovery (mount USB storage), both times the error was the same; the installer was unable to detect my Desire...
4.I don't quite understand that (I'm a noob when it comes to 'codenamed' thingies)... What I did was I just downloaded the .exe file and ran it
5.I've tried both with a completely blank SDcard and a partitioned one (256MB size, 0MB swap size)...
Just to point out though that the Aurora ROM didn't need a partitioned SDcard the first time I installed it (when my Desire wasn't in this weird state).
Thanks for your quick reply!
Click to expand...
Click to collapse
Ok, if you mean stock hboot, which stock Alpharev or HTC? If you have HTC one continue reading. If not reboot phone with power and volume down and see what is written on the top of the screen.
Download 2.3 RUU you have a guide in my signature.
Run RUU from bootloader, not recovery just reboot phone with power-volume down and run it from white screen.

I tried with the Aurora ROM again... Now it's just stuck at the bootimage!
Time to listen to a pro
My Hboot doesn't say anything about alpharev... But nobody ever changed that, so it must be HTC, right?
So, the *almost* top of the screen should say 'HBOOT USB PLUG' while running the RUU...?
I already tried that with (I think) Android 2.2 but it didn't detect my phone...
Downloading the 2.3 RUU

someone755 said:
I tried with the Aurora ROM again... Now it's just stuck at the bootimage!
Time to listen to a pro
My Hboot doesn't say anything about alpharev... But nobody ever changed that, so it must be HTC, right?
So, the *almost* top of the screen should say 'HBOOT USB PLUG' while running the RUU...?
I already tried that with (I think) Android 2.2 but it didn't detect my phone...
Downloading the 2.3 RUU
Click to expand...
Click to collapse
Then you're ready to go with RUU, just run it from that screen.

Sorry for the slow response, I had to eat meh lunch (while the battery was charging)
I'm getting the 'LOW MAIN BATTERY POWER' error [120]... apparently the battery level is under 30%, even after a 1h charge...
Waiting some more for it to charge, and I have a feeling this 2.3.3 RUU thing just might fix meh problems

Lol the 2.3 upgrade has saved a good few phones this past week
Sent from my HTC Desire

jmcclue said:
Lol the 2.3 upgrade has saved a good few phones this past week
Click to expand...
Click to collapse
Yeah, tell me about it
This is the ultimate HTC Desire un-brick tutorial in this thread

Here is the explanation how all that works.

Okay, so my phone is still not working, as the RUU thinks its battery is under 30%, even though my Desire is fully charged up...
Is wiping battery stats a good idea?
@nlooooo: Thanks! Now I finally! have at least part of the idea how it all works
EDIT: The RUU thinks my battery is less than 30%, even though it has been charging since my last post (and the green LED confirms it's full).
Why?? I just wiped the battery stats, should I do anything else?
EDIT2: Switched from BOOTLOADER USB to FASTBOOT USB, it now seems to work...
As I understand, from here on I can restore NAND backups?
I'm only asking so I wont have to go through this all again -.-'
EDIT3: Just installed Revolutionary CWM (the easiest way to get CWM), flashed su zip... Superuser finally works and my su binary was auto-updated (after many months of manual updates)
Still, can I do NAND restores safely right now?

You'll have to s-off your device and the tool you need to use will flash recovery.
For s-off see this:
revolutionary.io
And read the guide given. Don't worry it will ask you for your IMEI when you start download it's just for the purpose of building your beta license key.
After you flash recovery I think you know what to do...

I already s-off'd the first day I got the thing seems like S-OFF never disappears...?
Just flashed CWM with revolutionary, too (I'll update later) and just flashed su zip.
But is it safe for me to restore NAND backups of other roms? Or must I first install the rom and then restore the NAND?

Now you are on stock hboot with data partition at 147 MB. If your NAND backup data partition is more than 147MB you will get into trouble.

How can my NAND backup partition be different than the one I have now (stock) if I've always had it...? This is sort of confusing... :S

someone755 said:
I already s-off'd the first day I got the thing seems like S-OFF never disappears...?
Just flashed CWM with revolutionary, too (I'll update later) and just flashed su zip.
But is it safe for me to restore NAND backups of other roms? Or must I first install the rom and then restore the NAND?
Click to expand...
Click to collapse
You can restore just backup you don't need to flash rom. But first try to boot with stock 2.3.
So RUU finished with no problems? Now I'm not sure which hboot you have cause if you s-off with revolutionary on the top of the screen pink revolutionary should be written, and it doesn't disappear because RUU can't overwrite custom flashed hboots (alpharev or revolutionary).
---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------
handy5876 said:
Now you are on stock hboot with data partition at 147 MB. If your NAND backup data partition is more than 147MB you will get into trouble.
Click to expand...
Click to collapse
He was on stock before so no problems should occur.

I'd be much happier if you wrote that in your native language (Serbian), since I didn't get any of that... (and yes, I understand Serbian)
I think I have the stock hboot, but I never changed it, so what else could it be?
I S-OFF'd my Desire using Revolutionary, and no RUU, ROM flash or ZIP install could ever make it S-ON'd...
And on top of hboot there is a pink 'Recolutionary' sign...

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.

Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.

I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".

Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.

Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.

Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?

Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?

Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.

Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.

You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!