Jump to content

Problems flashing custom roms after the Official UK update


Guest elphzwolf
 Share

Recommended Posts

Guest elphzwolf

Here's a brief description of the situtation i'm in:

I updated my pulse with the official UK 2.1 update. When I try to flash any of the 2.2 custom roms (the AntonioPT one, TWRock, basic TomG CM port etc..) + DTa2sd + gapps, following the instructions to the letter, I'm stuck with the following:

1) I do not get the config wizzard (tap the android to begin) when i boot up; instead I'm greeted by ADWlauncher.

2) I have none of the gapps (gmail, youtube, market etc...)

3) I can not (under any rom and circumstance) connect to my WiFi (permanently Obtaining IP adress, network is WPA2/PSK secured)

Previously I had the old 2.1 update (i thnik) with CM AIO ver. 4 and everything worked just fine.

Tried to nand-restore my backup, but I get stuck at the android screen indefinetly (even after wiping data, Dalvik and formatting the sd-ext after restoring the backup).

Tried downgrading to 1.5 then clean upgrading to 1.6->2.1 => the results were the same.

My question being:

1) what should I do now, since I can't bear the T-mobile branded pink rom, and I have grown quite accustomed to the CM 2.2 rom

2) Is there a difference in the partition sizes between the old and new UK 2.1 since half way through the gapps flash it stops abruptly with the message Installation from SD complete

3) does anybody have a working link of the old UK 2.1 update so I can revert back

Thanks in advance for every and any assistance you could provide.

Edited by elphzwolf
Link to comment
Share on other sites

i noticed that issue after i updated to the new german 2.1. maybe these updates make other partition sizes.

so, when i reflashed the older uk2.1, all custom roms are working again.

Edited by msig
Link to comment
Share on other sites

Guest elphzwolf
i noticed that issue after i updated to the new german 2.1. maybe these updates make other partition sizes.

so, when i reflashed the older uk2.1, all custom roms are working again.

Issue fixed by either repacking the rom and gapps to conserve space on /system or by reflashing the old UK update ang gettung a bigger system partition

Thanks for the replies.

Link to comment
Share on other sites

Issue fixed by either repacking the rom and gapps to conserve space on /system or by reflashing the old UK update ang gettung a bigger system partition

thx for the repack tip.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.