UK 2.1 OS won't launch after root/recovery attempt

[Guest Michael Vegfruit]

Started off with a rooted 8220 with Paul's custom rom installed, as described in the guide here

The official 2.1 version came available on T-Mobile UK today. I installed it without problems, restarted OK, etc

Decided I wanted root access back, so I could uninstall telco apps

Went back to that guide, but I think I ran the first and second steps in the wrong order: so, ran the command for flashing the recovery sector first, then ran the command for getting root rights. I'm working in Ubuntu linux, so ran them by typing 'sudo bash install-recovery-linux.sh" and then "sudo bash install-superboot-linux.sh".

(as an aside, looking at that guide, it tells you to run the same script twice for Linux, which may be why I got confused)

Anyway, now, when I try to start the phone, I get the T-mobile logo, the android logo, and then the screen goes black and stays black. I'm occasionally spotting a blinking underscore in the top left corner of the screen (like in terminal, kind of), but it is very irregular. When I say the screen is black, I mean the phone is on, I can see that the backlight for the screen is on, but the display is just showing black and that occasional cursor or whatever it is.

I've tried using the different key combos for fastboot and recovery mode, and even for software upgrade, as there is an upgrade file on there.

Any ideas what I've done wrong?

How can I fix it?

Will T-Mobile be able to see what I've done, or do you think I should be able to get it replaced?

Edited August 6, 2010 by Michael Vegfruit

[Guest Epic-Emodude]

Started off with a rooted 8220 with Paul's custom rom installed, as described in the guide here

The official 2.1 version came available on T-Mobile UK today. I installed it without problems, restarted OK, etc

Decided I wanted root access back, so I could uninstall telco apps

Went back to that guide, but I think I ran the first and second steps in the wrong order: so, ran the command for flashing the recovery sector first, then ran the command for getting root rights. I'm working in Ubuntu linux, so ran them by typing 'sudo bash install-recovery-linux.sh" and then "sudo bash install-superboot-linux.sh".

(as an aside, looking at that guide, it tells you to run the same script twice for Linux, which may be why I got confused)

Anyway, now, when I try to start the phone, I get the T-mobile logo, the android logo, and then the screen goes black and stays black. I'm occasionally spotting a blinking underscore in the top left corner of the screen (like in terminal, kind of), but it is very irregular. When I say the screen is black, I mean the phone is on, I can see that the backlight for the screen is on, but the display is just showing black and that occasional cursor or whatever it is.

I've tried using the different key combos for fastboot and recovery mode, and even for software upgrade, as there is an upgrade file on there.

Any ideas what I've done wrong?

How can I fix it?

Will T-Mobile be able to see what I've done, or do you think I should be able to get it replaced?

I think you have flashed the 1.5 root which changes the boot img. Try the 2.1 root. It can be found on xda.

[Guest Michael Vegfruit]

I think you have flashed the 1.5 root which changes the boot img. Try the 2.1 root. It can be found on xda.

Thanks, that sounds right. I ran the scripts from packs called '1.5-pulse-superboot' and '1.5.2-pulse-amonrarecovery'.

Given that I'm clearly not quite getting this, could you point me to the correct 2.1 root? I have tried googling 'XDA 2.1 root', but only see guides for rooting other bits of hardware.

[Guest TheBrownBottle]

I think you have flashed the 1.5 root which changes the boot img. Try the 2.1 root. It can be found on xda.

The same thing happened to me but the 1.5 root worked with the HU ROM. Somethings changed

Edited August 6, 2010 by TheBrownBottle

[Guest Simon O]

Custom roms for 2.1 are already rooted so they don't need any superboot installed.

[Guest Michael Vegfruit]

Custom roms for 2.1 are already rooted so they don't need any superboot installed.

This was the new (yesterday) official ROM from T-mobile UK, so it wasn't rooted. I'd been using a rooted custom ROM, but installing the official version looks like it removed root permissions. So I tried to install superboot, and, as Epic-Emodude says, I used the 1.5 superboot (at least, that what I understand him to be telling me I've done wrong: it sounds right).

[Guest Epic-Emodude]

Thanks, that sounds right. I ran the scripts from packs called '1.5-pulse-superboot' and '1.5.2-pulse-amonrarecovery'.

Given that I'm clearly not quite getting this, could you point me to the correct 2.1 root? I have tried googling 'XDA 2.1 root', but only see guides for rooting other bits of hardware.

You have to reflash official update then go to the thred for pauls 2.1 rom. It says how it was rooted and a link. Go to the link then download the zip for eclair. To flash it you will need a recovery image. Download rom manager from the market then use that to download and flash the recovery image. It may be easier to get the recovery image (see the thred for more information) then flash a rooted custom rom (i suggest flb mod)

Hope this helps.

[Guest Michael Vegfruit]

You have to reflash official update then go to the thred for pauls 2.1 rom. It says how it was rooted and a link. Go to the link then download the zip for eclair. To flash it you will need a recovery image. Download rom manager from the market then use that to download and flash the recovery image. It may be easier to get the recovery image (see the thred for more information) then flash a rooted custom rom (i suggest flb mod)

Hope this helps.

Thanks, that makes sense. I still had the official /dload image on the phone, so was able to reflash it. I'll check out the other thread and try to do it right.