116 replies to this topic

[rovex]

Rhysd2, on Jun 30 2010, 09:41, said:

Cant be for the desire either. HTC have stated their devices will be getting it later in the year. Q3 or something like that
So is this now on the actual dell site if I go and ask my phone to update?

And do we actually know what 4399 does yet?

Q3 starts tomorrow..  

[Rhysd2]

rovex, on Jun 30 2010, 09:48, said:

Q3 starts tomorrow..  

*facepalm* yes it does lol. I'd be surprised if they had it ready that quick though as HTC seem very slow on their updates.

[PaulOBrien]

4399 kernel MD5 sum is different!

P

[the_didge]

UPDATE REPORT :

From :3889
To : 4399

Status : Successful

After initial update screen a reboot occurred with a 2nd update, the following text was on the screen :
DT: A3.702                 BUILD DATE MAY 19 2010 13:49:07

Then another reboot with :
Restoring(might have been reverting) to factory setting.

Final reboot with long boot time and its back up and running

Method used : Place file on sdcard, rename to update.pkg, switch off device, switch back on while holding both volume buttons, when menue appears use volume buttons to navigate and camera button to select.

[PaulOBrien]

Note 'Update.pkg' is case sensitive, you need the upper case U.

P

[the_didge]

Paul, on Jun 30 2010, 09:02, said:

Note 'Update.pkg' is case sensitive, you need the upper case U.

P

it worked with a lowercase u. what it didnt like was that i had a file called update2.pkg (49XX build) on the sd card. After renaming update2 it was ok again.

Forgot to switch on wifi for data and have just used about 20mb while abroad... Roaming charges are a pain...

[PaulOBrien]

Ah, right, clearly more than one pkg file is the problem!

P

[PaulOBrien]

Hmmm, flashing the custom recovery seems to be having issues for me, getting a black screen...!

P

[the_didge]

Paul, on Jun 30 2010, 09:09, said:

Ah, right, clearly more than one pkg file is the problem!

P

Its ok with 2, but will only allow one that starts with "update" otherwise throws out the same error as a missing file. it was perfectly happy with updgfhfghate2.pkg

[SgtDavePwnage]

Paul, on Jun 30 2010, 10:10, said:

Hmmm, flashing the custom recovery seems to be having issues for me, getting a black screen...!

P

You are using the correct file?  

Remember that the original file uploaded was the wrong one

[the_didge]

Now Confirmed : Cannot update to 49XX from 43XX, must be different hardware models.... but whats the difference?

[marra2]

downloaded mine(4399) straight to me phone with the links off here and phone didn't reset , kept all my stuff as it was. but I'm not rooted yet as no custom roms so can't see the point  

Edited by marra2, 30 June 2010 - 09:18 AM.

[PaulOBrien]

Scratch that, custom recovery is on. Phew.

P

[PaulOBrien]

the_didge, on Jun 30 2010, 10:15, said:

Now Confirmed : Cannot update to 49XX from 43XX, must be different hardware models.... but whats the difference?

You have a 43xx device?

Strange!

P

[PaulOBrien]

I wonder if you have a '21' or a '31' device... any indication in your software info? Have you tried this update?

http://update.zingst...106_4917_31.pkg

P

[the_didge]

Paul, on Jun 30 2010, 09:17, said:

You have a 43xx device?

Strange!

P

Yup 43XX it is now, was 38XX...

[courtlandre]

Any reason to do these updates so far?

[the_didge]

Paul, on Jun 30 2010, 09:19, said:

I wonder if you have a '21' or a '31' device... any indication in your software info? Have you tried this update?

http://update.zingst...106_4917_31.pkg

P

Thats the same as the _31 update (49XX). tried to use that after updating to _21 (43XX). Gave FOTA error before and after upgrading to _21 (43XX)

Edited by the_didge, 30 June 2010 - 09:24 AM.

[PaulOBrien]

Superboot for 4399 now online here.

P

[PaulOBrien]

the_didge, on Jun 30 2010, 10:22, said:

Thats the same as the _31 update (49XX). tried to use that after updating to _21 (43XX). Gave FOTA error before and after upgrading to _21 (43XX)

Ah, my bad, I thought you had a different device to the rest of us. Ignore me.

P