[MOD][CWM][Bell][Gobstopper] Stock 2.2.2 for Bell Updated 10/01/2011

Search This thread

NFHimself

Senior Member
Mar 12, 2008
816
469
Mount Pearl
Disclaimer: You may brick your phone. NOT for AT&T

Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.​
Hi,

Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.

What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.

This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.

EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.

It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper. :)

Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.

If you want root after installing this, just install Superuser.apk from the market.

Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)


Cheers!​
Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.

unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
 
Last edited:

akurit

Senior Member
Oct 10, 2007
102
14
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?

So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
 

raybond25

Senior Member
Apr 26, 2008
816
139
Ottawa
Will you eventually be able to compile a zip for Bell gingerbread?
the problem would be hosting it, not sure how he would be able to do that.


When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?

So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?

keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.

NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.

to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline

and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.

hope that clears up your question, if you have any further ask them in here.
 

NFHimself

Senior Member
Mar 12, 2008
816
469
Mount Pearl
Will you eventually be able to compile a zip for Bell gingerbread?

Hi,

I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.

Cheers!
 

akurit

Senior Member
Oct 10, 2007
102
14
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.

tried it again and it work

but seems like i have to fastboot flash it each time i want to use recovery
 
Last edited:

NFHimself

Senior Member
Mar 12, 2008
816
469
Mount Pearl
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.

tried it again and it work

but seems like i have to fastboot flash it each time i want to use recovery

I know what you are talking about, but I got that with a stock bootloader.

If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.

Cheers!

Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.

CWM_INT_Recovery.zip

(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
 
Last edited:
  • Like
Reactions: raybond25

raybond25

Senior Member
Apr 26, 2008
816
139
Ottawa
I know what you are talking about, but I got that with a stock bootloader.

If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.

Cheers!

Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.

CWM_INT_Recovery.zip

(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
 

NFHimself

Senior Member
Mar 12, 2008
816
469
Mount Pearl
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.

Hi,

Sure, it's just replacing the word recovery with boot and having the right boot images in the file.

Cheers!
 
  • Like
Reactions: raybond25

y2whisper

Senior Member
Aug 17, 2006
2,482
274
Toronto
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.

@akurit

I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
 
  • Like
Reactions: akurit

y2whisper

Senior Member
Aug 17, 2006
2,482
274
Toronto
Its installing now!

now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.

ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
 

akurit

Senior Member
Oct 10, 2007
102
14
This is why hehee


......


Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........

now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
 
Last edited:
  • Like
Reactions: miguel.b

raybond25

Senior Member
Apr 26, 2008
816
139
Ottawa
Its installing now!

now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.

ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
 
  • Like
Reactions: y2whisper

NFHimself

Senior Member
Mar 12, 2008
816
469
Mount Pearl
anyone try flashing the bootloader and radio?

Hi,

I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.

Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.

Cheers!
 
  • Like
Reactions: xateeq

y2whisper

Senior Member
Aug 17, 2006
2,482
274
Toronto
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.

I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
 

NFHimself

Senior Member
Mar 12, 2008
816
469
Mount Pearl
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.

I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome

Hi,

What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.

Cheers!
 
  • Like
Reactions: xateeq

y2whisper

Senior Member
Aug 17, 2006
2,482
274
Toronto
ahhhh.

you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.

I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Disclaimer: You may brick your phone. NOT for AT&T

    Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.​
    Hi,

    Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.

    What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.

    This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.

    EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.

    It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper. :)

    Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.

    If you want root after installing this, just install Superuser.apk from the market.

    Bell_FR_2.2.2.zip (Froyo not France)
    (md5 e431b4cc3ba7e3a27b6aad6982a31066)


    Cheers!​
    Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.

    unlocked-fixed-Bell-2.2.2.zip
    Mirror: unlocked-fixed-Bell-2.2.2.zip
    3
    Hi,

    Well, since there is a possible Bell GB OTA in the works "I" would be just flashing the zip and doing the OTA when it is available to avoid any hash checks failing for boot and/or recovery.

    If you want to avoid having to sbf_flash the pudding file again then apply the unlocked cwm zip. It's the same stock boot kernel, just with the cmdline option baked in to work with the unlocked bootloader, not a user compiled kernel in other words.

    Cheers!
    2
    Will you eventually be able to compile a zip for Bell gingerbread?
    the problem would be hosting it, not sure how he would be able to do that.


    When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?

    So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?

    keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.

    NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.

    to find what version you should use, connect to phone via ADB and then
    Code:
    adb shell
    su
    cat /proc/cmdline

    and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.

    hope that clears up your question, if you have any further ask them in here.
    1
    Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this! :cool:
    1
    I would just put on the GobStopper 2.3.4. It's the same as the Bell OTA only better because it's not a mandatory gift from Bell.