Problems updating to UK 2.1 Official

[Guest YuYeVoN]

Help needed to update my Pulse U8220 to the UK 2.1

I came from FLBMOD 1.3 and tried going to 1.4.1 without any luck errors at ramdisk writing.

Next thing i tried was first doing the UK 2.1 update. but for some reason at the half it stops and gives an update failed.

I've tried different 2.1 updates, even went to the t-mobile uk website to download the 2.1 update. no luck.

It seems like my Pulse only picks the Hungarian update.

So my question is should I go back to 1.5 and then do the UK 2.1?

or does my device can't update using the UK update?

Much help is apreciated as I cannot even use FLBMOD 1.1 zt the moment.

[Guest rjm2k]

Help needed to update my Pulse U8220 to the UK 2.1

I came from FLBMOD 1.3 and tried going to 1.4.1 without any luck errors at ramdisk writing.

Next thing i tried was first doing the UK 2.1 update. but for some reason at the half it stops and gives an update failed.

I've tried different 2.1 updates, even went to the t-mobile uk website to download the 2.1 update. no luck.

It seems like my Pulse only picks the Hungarian update.

So my question is should I go back to 1.5 and then do the UK 2.1?

or does my device can't update using the UK update?

Much help is apreciated as I cannot even use FLBMOD 1.1 zt the moment.

try the "time machine" followed by the uk 2.1?

[Guest YuYeVoN]

try the "time machine" followed by the uk 2.1?

Tried that still get an update failed message.

this basiclly means no more 2.1 custom roms for me, maybe a brick somewhere???

EDIT:And now my first screen is all messed up, i see all colors and black and white lines over my screen (can't be good)

EDIT:I've restored my screen by doing the HU 2.1 update, it worked. but now all the ROMS says

E:Error finishing BOOT:

E:Failure at line 384:

write_raw_image PACKAGE:boot.img BOOT:

installation aborted.

What can I do to fix this problem?

Edited August 31, 2010 by YuYeVoN

[Guest rjm2k]

Tried that still get an update failed message.

this basiclly means no more 2.1 custom roms for me, maybe a brick somewhere???

EDIT:And now my first screen is all messed up, i see all colors and black and white lines over my screen (can't be good)

EDIT:I've restored my screen by doing the HU 2.1 update, it worked. but now all the ROMS says

E:Error finishing BOOT:

E:Failure at line 384:

write_raw_image PACKAGE:boot.img BOOT:

installation aborted.

What can I do to fix this problem?

I think I saw a thread which mentioned quite a few people were getting this issue and it was down to faulty ram.

[Guest YuYeVoN]

Is there any known fix for that or is my phone f*cked :huh: ?

I hope not, else i'll need to go back to my G1 ;):(

The Hungarian update still worked, custom roms none.

only official 1.5 or 2.1 :(

[Guest rjm2k]

Is there any known fix for that or is my phone f*cked :huh: ?

I hope not, else i'll need to go back to my G1 ;):(

The Hungarian update still worked, custom roms none.

only official 1.5 or 2.1 :(

try the new time machine which is mentioned in a recent thread

[Guest johninho]

I was one of the people having the same problem.

Afraid, for me at least, it was a hardware fault.

Hungarian 2.1 or UK Dec 09 1.5 worked fine (as did FLB 1.1 and 1.2)

Anything after that including official UK 2.1 gave same errors that you are getting.

T-Mobile replaced the mainboard under warranty on mine and it's now fine.

If you read the thread from here http://android.modaco.com/index.php?s=&amp...t&p=1369624

I think you'll find it's probably the same problem :huh:

[Guest YuYeVoN]

Well it appears to be the same issue.

Not to worry I rooted and put Aps2SD on the official roms myself :huh:

So basilly it's working. And to add a comment, i overclocked my cpu to run constant on 528 MHz, and the battery already lasted 2 days without charging.

[Guest Fusion0306]

Well it appears to be the same issue.

Not to worry I rooted and put Aps2SD on the official roms myself :huh:

So basilly it's working. And to add a comment, i overclocked my cpu to run constant on 528 MHz, and the battery already lasted 2 days without charging.

the cpu is 528 MHz, so that's not quite overclocked

[Guest meinnit]

the cpu is 528 MHz, so that's not quite overclocked

I think he's referring to the constant bit. I find it hard to believe that the battery lasted that long running at constant 528MHz!

[Guest YuYeVoN]

I can't help it, but i forgot to slow down the frequenzy, after gaming and i looked at the battery and it said that it still had 52%. AFTER 2 DAYS running at 528 MHz.

It also seems that A2SD isn't working at all.

I tried to flash it from my recovey (which is the latest clockwork) but it won't flash the dtapps2sd-2.7.5-rc3c-signed from XDA.

it gave me the following error:

E:Can't chown/mod /system/bin/fixa2sd

(No such file or directory)

Failure at line 6:

set_perm 0 0 0777 SYSTEM:bin/fixa2sd

Does this imply that i don't have full root access, or is there something wrong with my internal working?

or does it mean i need to create the folder myself?

Edited September 2, 2010 by YuYeVoN