Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed

Outline · [ Standard ] · Linear+

 HTC Desire Official Thread V4, FAQs on First Page [Froyo 2.2 is Here!]

views
     
cleave
post Aug 3 2010, 06:52 AM

Custom Title goes here...
****
Senior Member
673 posts

Joined: Nov 2007


QUOTE(samurai1337 @ Aug 2 2010, 11:00 PM)
Successfully rooted mine (unrevoked method) and now using the Froyo 2.2 ROM with sense biggrin.gif
*
Congratulations! I guess the FroYo temptation was too strong to resist. laugh.gif

Ok, since the Desire users are in ROM flashing mood, I'll just add a friendly reminder here. While there's a very minimal chance of bricking your set when you flash a ROM, flashing a new radio takes the risk to a new level. If there's anything that can brick your set, it's the radio. You can recover from a corrupted ROM, but if you flash a corrupted radio, the only way to fix it is to send your set to HTC.

Do's
- Make sure your battery is full. The last thing you want is the phone shutting down while radio flashing due to low power.
- Check the MD5 hash of the downloaded radio image (or ROM if it includes a radio). Make sure downloaded copy and the one published on the site matches.

Dont's
- Never pull the battery out while the phone is updating the radio. It'll take some time for the updating process to complete. Be patient and wait. Some impatient people thinks that the phone 'hangs' and pulls the battery out to get it to restart. As a result, bricked phone and hello HTC service center.

I've flashed dozens of ROMs on my Hero and N1 but whenever I need to flash a radio, it still sends shivers down my spine. unsure.gif
cleave
post Aug 4 2010, 11:18 AM

Custom Title goes here...
****
Senior Member
673 posts

Joined: Nov 2007


QUOTE(samurai1337 @ Aug 4 2010, 10:40 AM)
I don't bother to root twice actually, just need to get the Recovery tool working

Maybe I should email ClockworkMod to ask what's their advice
*
Have you tried booting into recovery and try flashing a ROM from there? hmm.gif
Clockworkmod comes in two parts, the recovery image itself and the front-end (ROM Manager). There's a possibility that the ROM manager part is broken while the recovery image is not. One way to determine this is to boot into the recovery console itself (not sure what the key combo for that on Desire, on the N1 it's volume down + power). Or if you have a terminal emulator installed and you have root, start the terminal emulator and type this:
?su
#reboot recovery


cleave
post Aug 4 2010, 12:07 PM

Custom Title goes here...
****
Senior Member
673 posts

Joined: Nov 2007


QUOTE(samurai1337 @ Aug 4 2010, 11:28 AM)
Key combo is volume down + power for Desire too

I think the recovery console itself is broken - I can manually go into recovery mode, but it keeps reading the old settings and the backup is not stored in the clockworkmod directory
*
I see. So we need to find a way to load an uncorrupted recovery image.
If you are familiar with 'fastboot', you can do this:-

1) Download Clockwork image here:-
http://koush.tandtgaming.com/recoveries/re...5.0.1-bravo.img

2) Stash it somewhere where fastboot can locate it.

3) Boot the phone into the bootloader

4) start the command prompt on your PC and type 'fastboot devices' to make sure your phone is recognized by fastboot

5) Now we're gonna load the downloaded recovery image. type:-
fastboot boot recovery-clockwork-2.5.0.1-bravo.img

you should see something like 'downloading boot.img....'

6) If everything went fine the phone should be in recovery mode but not using the suspected corrupted recovery image on the phone. It's using the one you downloaded.

7) Check if the settings and backup folder issue is fixed.

And do this at your own risk. I dont have a Desire to test this method thoroughly. I'm running Amon RA on my N1, sometimes when I want to use some Clockwork functions, I just fastboot the image using the method above. This way, I dont need to flash and re-flash between the two recovery image.
cleave
post Aug 4 2010, 12:23 PM

Custom Title goes here...
****
Senior Member
673 posts

Joined: Nov 2007


QUOTE(samurai1337 @ Aug 4 2010, 12:10 PM)
Unluckily I am not too familiar with fastboot, but I can try

I understand the steps, but how do I do step 2 and step 4?
*
For step 2, the easiest way is to move the downloaded recovery image into the directory where the fastboot binary is located. If you already have fastboot in your system PATH variable, you dont need to do this. Just execute the fastboot command in the directory where the recovery image was placed.

Step 4 is starting a command prompt ('Run.. cmd' on Windows or open a terminal on Linux). Is that DOS box thing where you can type text commands. So you'll have something like this:
C:\androidsdk\fastboot devices

if your device is recognized by fastboot it will reply with 'HTC xxxxxxxx', where 'xxxxxxx' is your device's serial number.
cleave
post Aug 4 2010, 03:59 PM

Custom Title goes here...
****
Senior Member
673 posts

Joined: Nov 2007


QUOTE(samurai1337 @ Aug 4 2010, 12:44 PM)
Too late dude... I already flashed back to stock RUU and re-doing everything again

Thanks for your help though - I think I will avoid ROM Manager for now as I believe it corrupted my CWM recovery
*
What? 13-minutes is too late? I was replying while eating lunch. laugh.gif
Glad you got your issue sorted though. thumbup.gif
cleave
post Aug 4 2010, 06:53 PM

Custom Title goes here...
****
Senior Member
673 posts

Joined: Nov 2007


QUOTE(draco82 @ Aug 4 2010, 06:51 PM)
deodexed rom means you can always change the interface or indication of sense ui
[attachmentid=1709268]
you can notice some indicators looks different like battery....
This is the use of deodexed, but i dont know how to do it~~ tongue.gif
*
Use Metamorph. wink.gif

Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0504sec    0.25    7 queries    GZIP Disabled
Time is now: 3rd December 2025 - 02:09 AM