Welcome Guest ( Log In | Register )

Bump Topic Topic Closed RSS Feed
126 Pages « < 25 26 27 28 29 > » Bottom

Outline · [ Standard ] · Linear+

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

views
     
KTCY
post Aug 4 2010, 11:38 AM

BumbleBee™
********
All Stars
12,505 posts

Joined: May 2007
From: Triumph in the Skies Status:In LoV3 Again
QUOTE(volcane @ Aug 4 2010, 11:35 AM)
found out how to enable swype.

Long press the "text box",  input method selection dialog pop-up, select Swype.

looks like HTC Keyboard behave differently as compare to nexus one.
*
What you mean by differently ? unsure.gif
skysoblue93
post Aug 4 2010, 11:38 AM

Getting Started
**
Junior Member
211 posts

Joined: May 2010


i cant start my desire! it just stuck at the htc logo.. can somebody help me?
KTCY
post Aug 4 2010, 11:39 AM

BumbleBee™
********
All Stars
12,505 posts

Joined: May 2007
From: Triumph in the Skies Status:In LoV3 Again
QUOTE(skysoblue93 @ Aug 4 2010, 11:38 AM)
i cant start my desire! it just stuck at the htc logo.. can somebody help me?
*
What had you done ? Tell us more.
draco82
post Aug 4 2010, 11:40 AM

On my way
****
Senior Member
584 posts

Joined: Nov 2007


QUOTE(Pennywise @ Aug 4 2010, 11:26 AM)
Guys, thanks for answering my questions.

I'm on LeeDroid 1.6 and am very happy with it since A2SD+ works well and Swype is good too and have access to paid Market. Nothing else I need. I will wait for the official Froyo for Desire for Asia.

Just wondering why ppl keep flashing their Desire with newer and different developers Froyo? Not same? Better performance?
*
I think it is because the release of the official froyo. a lot of mod rom have been made these few days....
As those rom are develop base on the new release, so a lot of bugs need to be fix when root the official froyo...
so you can see the version of those rom is keep upgrading almost everyday v1, v2, v3,.....
so people will keep flashing the latest rom with certain bugs fix until a stable rom is out~~
The more and faster people flash, the easier to find the bugs out, as everyone is giving out comment...
i will join as well to contribute a bit to the developer, haha~~ rclxm9.gif rclxm9.gif
(good reason for flashing~~)
will do my 3rd flashing since the official froyo is out. icon_rolleyes.gif icon_rolleyes.gif
will try out leedroid...
skysoblue93
post Aug 4 2010, 11:47 AM

Getting Started
**
Junior Member
211 posts

Joined: May 2010


QUOTE(KTCY @ Aug 4 2010, 11:39 AM)
What had you done ? Tell us more.
*
i've done nothing actually.. it all started when i was using a sort of wifi app.. then suddenly the phone turned off.. and i cant boot up my phone ever since.. i tried to hard reset it but still not working.. it is like the OS or the rom is corrupted
kairesh
post Aug 4 2010, 11:47 AM

New Member
*
Junior Member
11 posts

Joined: Dec 2008
QUOTE(i_bony @ Aug 4 2010, 10:52 AM)
i think i encountered that problem too T-T
*
It's quite strange as others never complaint on this problem. Moreover, the thread is busy on Froyo discussions sad.gif

Wonder anyone here faces the outgoing call waiting issue? Hoping for some assistance here. icon_question.gif
DecaPix
post Aug 4 2010, 11:52 AM

5 star monkey
*******
Senior Member
3,000 posts

Joined: Aug 2008
From: PeeJay
ok speedtested
getting as high as 2.74 Mbps
is that ok or not? hmm.gif
samurai1337
post Aug 4 2010, 12:01 PM

@_@
Group Icon
VIP
11,594 posts

Joined: Jan 2003
From: Area 51

QUOTE(DecaPix @ Aug 4 2010, 11:52 AM)
ok speedtested
getting as high as 2.74 Mbps
is that ok or not? hmm.gif
*
Wow that's fast... definitely HSDPA (I am getting 1MB max so far from Maxis)
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.
draco82
post Aug 4 2010, 12:08 PM

On my way
****
Senior Member
584 posts

Joined: Nov 2007


QUOTE(skysoblue93 @ Aug 4 2010, 11:47 AM)
i've done nothing actually.. it all started when i was using a sort of wifi app.. then suddenly the phone turned off.. and i cant boot up my phone ever since.. i tried to hard reset it but still not working.. it is like the OS or the rom is corrupted
*
official or custom rom? root?
samurai1337
post Aug 4 2010, 12:10 PM

@_@
Group Icon
VIP
11,594 posts

Joined: Jan 2003
From: Area 51

QUOTE(cleave @ Aug 4 2010, 12:07 PM)
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.
*
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?
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.
samurai1337
post Aug 4 2010, 12:44 PM

@_@
Group Icon
VIP
11,594 posts

Joined: Jan 2003
From: Area 51

QUOTE(cleave @ Aug 4 2010, 12:23 PM)
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.
*
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
akachester
post Aug 4 2010, 12:57 PM

Its Life. Live with it!
*******
Senior Member
7,689 posts

Joined: Jul 2005
From: The Land of No Return


For Swype, i had the problem as well previously whereby you had enabled it in settings but you cant find it anywhere. What you should do is, to install Swype, enable it in Settings, then restart your phone. Only then you will see the option by long-pressing the settings key in the messages keyboard.

QUOTE(samurai1337 @ Aug 4 2010, 12:01 PM)
Wow that's fast... definitely HSDPA (I am getting 1MB max so far from Maxis)
*
Speedtest on my Digi showing about 1MB as well but that is on a very good case.

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
*
Aint CWM from the same creator as the ROM Manager? Weird that they will conflict within each other sad.gif

Pennywise
post Aug 4 2010, 01:18 PM

Look at all my stars!!
*******
Senior Member
5,796 posts

Joined: Jan 2003
QUOTE(draco82 @ Aug 4 2010, 11:40 AM)
I think it is because the release of the official froyo. a lot of mod rom have been made these few days....
As those rom are develop base on the new release, so a lot of bugs need to be fix when root the official froyo...
so you can see the version of those rom is keep upgrading almost everyday v1, v2, v3,.....
so people will keep flashing the latest rom with certain bugs fix until a stable rom is out~~
The more and faster people flash, the easier to find the bugs out, as everyone is giving out comment...
i will join as well to contribute a bit to the developer, haha~~ rclxm9.gif  rclxm9.gif
(good reason for flashing~~)
will do my 3rd flashing since the official froyo is out. icon_rolleyes.gif  icon_rolleyes.gif
will try out leedroid...
*
I see. Guess I'll stick with LeeDroid 1.6 (so far I read seems most stable) until the Official Froyo release for Maxis set since all I need is A2SD.
samurai1337
post Aug 4 2010, 01:24 PM

@_@
Group Icon
VIP
11,594 posts

Joined: Jan 2003
From: Area 51

Yeah, I reverted back to Asia stock ROM with 2.1 (unroot) and will wait patiently for 2.2 OTA now sad.gif
volcane
post Aug 4 2010, 01:25 PM

Casual
***
Junior Member
336 posts

Joined: Sep 2004
QUOTE(KTCY @ Aug 4 2010, 11:38 AM)
What you mean by differently ? unsure.gif
*
long press the EN key in the keyboard will bring up the Input Method dialog box.
KTCY
post Aug 4 2010, 02:04 PM

BumbleBee™
********
All Stars
12,505 posts

Joined: May 2007
From: Triumph in the Skies Status:In LoV3 Again
QUOTE(samurai1337 @ Aug 4 2010, 01:24 PM)
Yeah, I reverted back to Asia stock ROM with 2.1 (unroot) and will wait patiently for 2.2 OTA now sad.gif
*
You can always try again tongue.gif
LuffyPSP
post Aug 4 2010, 02:06 PM

Droid, droid droid droid!
*******
Senior Member
3,771 posts

Joined: Apr 2010
From: Kota Bharu


I love my Froyo!! its fast! but dont you guys think the auto-rotate screen is too sensitive. i just hold it horizontal a bit and it changes to landscape, i dont want that. otherwise its a good ROM!
Pennywise
post Aug 4 2010, 02:08 PM

Look at all my stars!!
*******
Senior Member
5,796 posts

Joined: Jan 2003
QUOTE(samurai1337 @ Aug 4 2010, 01:24 PM)
Yeah, I reverted back to Asia stock ROM with 2.1 (unroot) and will wait patiently for 2.2 OTA now sad.gif
*
Someday you probably have to teach me how to do this, when the 2.2 OTA comes closer. So far no announcement from HTC SEA right? I will stick to LeeDroid for a while. smile.gif

126 Pages « < 25 26 27 28 29 > » Top
Topic ClosedOptions
 

Change to:
| Lo-Fi Version
0.0254sec    0.85    6 queries    GZIP Disabled
Time is now: 4th December 2025 - 06:04 PM