[Request] Bell Mobolity Lastest Firware (Trying to get 3Gback)

[fogozito]

my current baseband is 76XXC-63805025-SDCBALUM and the current baseband version from Bell mobility is 76XXC-63805030-SDCBALUM, it uses the 850mhz freq for 3G if i can flash my dext with this firmware i maybe be able to get my 3G back.

Acording to the oficial motorola forums dext and cliq uses the same radio image but there is a config file that tells the phone what radio bands to use.

[fedegin]

This radio maybe can help latam users who lost the 2g access!

[GatorV]

Agree, this can help Telcel basebands, because it uses the same radio, let's hope someone can find it

[Citizen86]

http://modmymobile.com/forums/f548/e...52/index4.html

You'll notice post 54, njones has a Bell Mobility Dext. Maybe he can help?

[njones]

Would love to help, but I have no damn idea how to get the bloody thing off my phone...What tools do I need? How do I do it? Please!

[tonymy01]

What you really need to do is "fool" bell into thinking your phone has the old Bell firmware (did they have any old firmware?), by copying the default.prop & build.prop from an old f/w into your current rooted phone. Then do a check for updates, and your phone will tell them the version info that is in your prop files, and their server will say "hey, this needs an update"... and will deliver the update file to your phone /cache directory. Hopefully, like our Aussie 1.2.7 to 1.5.10 update did, it will contain the radio and boot.img and patches for the *original* firmware system files, and bobs-your-uncle, one radio, and one boot.img file to pull apart and study.
Of course, don't apply the update, it will fail miserably as it does checksums on the /system files (and others) it patches. Make sure you copy it out the cache before the phone boots the next time, or else the phone will do a clean-up and remove the file. The filename is actually the current software version.zip, judging by seeing the 2.0.26 one here, and now our Aussie 1.5.10 one.

You don't actually need to copy the prop files out an old version (they are actually readable even for non-root), you can simply mimick some of the firmware version name details more than likely. I would suspect it may just use the build.prop ro.build.version.full=Blur_Version.1.2.7.MB200.Opt us.en.AU in our Aussie case.



Regards

[njones]

Thanks a lot for the reply. However, it appears that you somehow must assume that:

1. I know what I'm doing
2. That I'm not a newbie

What you really need to do is "fool" bell into thinking your phone has the old Bell firmware (did they have any old firmware?)

This I do not know. It's true that it's a Bell Mobility Motorola Dext, but I'm in CA using AT&T.

by copying the default.prop & build.prop from an old f/w into your current rooted phone.

1st problem there is that I don't understand what you just said. I do know that I have not attempted to root the phone out of fear that it will loose 3G. If I am mistaken, and root IS possible, please direct me to the right procedure.

Then do a check for updates, and your phone will tell them the version info that is in your prop files, and their server will say "hey, this needs an update"... and will deliver the update file to your phone /cache directory. Hopefully, like our Aussie 1.2.7 to 1.5.10 update did, it will contain the radio and boot.img and patches for the *original* firmware system files, and bobs-your-uncle, one radio, and one boot.img file to pull apart and study.

This I understand, granted that I'm guided through the other steps.

Of course, don't apply the update, it will fail miserably as it does checksums on the /system files (and others) it patches. Make sure you copy it out the cache before the phone boots the next time, or else the phone will do a clean-up and remove the file. The filename is actually the current software version.zip, judging by seeing the 2.0.26 one here, and now our Aussie 1.5.10 one.

This I understand.

You don't actually need to copy the prop files out an old version (they are actually readable even for non-root), you can simply mimick some of the firmware version name details more than likely. I would suspect it may just use the build.prop ro.build.version.full=Blur_Version.1.2.7.MB200.Opt us.en.AU in our Aussie case.

The above makes as much sense to me as trying to read the bible.

Someone should really make a sticky how-to guide about this thing...But I do appreciate your reply and attempt to educate me. Please don't misunderstand my ignorance as arrogance.

[tonymy01]

I would prefer not to give step by steps, as I don't have your phone, I can't tell what you will and won't do right, I experimented myself to do this, and it may well be different in different regions.
So really, you need to identify if Bell did send any OTA upgrade for your phones. Optus has done 2 now for us, one minor one (no radio change) and one bigger one where the radio was upgraded from 5025 to 5030. They did this second one about a week after I got my phone running smoothly on 2.1 with 2.0.26. So I decided to see if I could manage to get the Optus update, to see what info they put into the phone for 1.5.10, and see if they fixed all the probs that 1.2.7 had, in case I wanted to go back (this 2.0.26 isn't perfect, it does have some networking DNS quirks I worked around with the init.d dns script I wrote and discussed how to install in another thread, the J_r0dd one, and the Aussie thread). I have managed to go back to our orig f/w, and apply the 1.5.10 update, to get the updated system files, by using the orangeFR as the start point, and the backup I took of my (original) firmware with the custom recovery backup when using the "how to root your phone, OLD METHOD" method (i.e. amon boot+recovery). This old method didn't work at all for any phone to network connectivity (i.e. RF dead), but it did root the boot.img, and did put a custom recovery on the phone, which let me backup the untouched system partition of the phone (and the broken boot.img, and the customrecovery and other partitions...except radio).
So this method "broke" the phone RF, but did give me a good copy of the whole system partition. I then rooted using the new OrangeFR method at this point (I think I may have had to put a stock f/w in with rsdlite to get to the point to get to orangeFR into the phone).

I was a newb 5 weeks ago also. I picked up all these tidbits from this forum, and using tools here and xdadevelopers, and, once I worked out the boot+menu bootup method is so low level, the phone is nearly unbrickable (assuming you have rsdlite working properly!!). To fiddle I recommend getting a linux VM or spare machine setup, as some things require the file permissions, links etc to be maintained, something windows can't do.
Regards

[fogozito]

You don't actually need to copy the prop files out an old version (they are actually readable even for non-root), you can simply mimick some of the firmware version name details more than likely. I would suspect it may just use the build.prop ro.build.version.full=Blur_Version.1.2.7.MB200.Opt us.en.AU in our Aussie case.



Regards

how can we obtain the string from bell mobility?


System version Blur_Version.1.5.5.MB200.BellMobility.en.CA
lets see how it goes

[tonymy01]

You get it from your handset with the "about" option, and get it from those files I said by using terminal emulator or even adb shell and cat the files in /system. You don't need root to do that. If you aren't too familiar with typing commands in linux shell, then leave this to someone who is, it isn't a "1 button press" solution by any means.

[fogozito]

You get it from your handset with the "about" option, and get it from those files I said by using terminal emulator or even adb shell and cat the files in /system. You don't need root to do that. If you aren't too familiar with typing commands in linux shell, then leave this to someone who is, it isn't a "1 button press" solution by any means.

i just changed my build from tmobile to Blur_Version.1.2.5.MB200.BellMobility.en.CA and the update didnt shouw up.

Thanks a lot for the reply. However, it appears that you somehow must assume that:
Someone should really make a sticky how-to guide about this thing...But I do appreciate your reply and attempt to educate me. Please don't misunderstand my ignorance as arrogance.

can u pull ur build.prop?
just use this commmand.
ADB pull /system/build.prop C:\build.prop

can u email it to fogozito@gmail.com

**u need to download the google SDK once downloaded navigate to the tools folder
**** dont forget to put ur phone in USB debuggin mode

[tonymy01]

i just changed my build from tmobile to Blur_Version.1.2.5.MB200.BellMobility.en.CA and the update didnt shouw up.

Was that a version that existed in Bell before the current version that Bell phones have? Is that the string format they use? I was only guessing that this was the only thing they use to confirm the f/w revision to see if a patch is avail, perhaps it uses one or two more bits of info, I had saved my original prop files ages ago when I found I could traverse quite a bit of the original phone filesystem non-rooted (but not all), so I used my full prop files to make the phone "pretend" to be a different software version. Remember, updates are made only for specific firmware versions, and so they check the before version of course.
Is your rooted rom altered in any way? Some remove the update checking stuff out of them. I was doing a lot of mucking about (ended up kind of "bricking" trying to flash just a system.img to my system partition... that is not the way you flash systems I found out in hindsight) and ended up going to the Orange.FR f/w, but modding the build for that, to get the firmware update sent to my phone. I then discovered how to flash the phone with my original Optus nandroid I took, so I could apply the update, by mounting the yaffs2 system.img file and copying across to the current system, rather than do a flash of system.img, and that was enough for the phone to have all the orig f/w system in order for me to subsequently tweak the patch on my PC (to root boot.img), and apply it to take another backup of a full working 1.5.10 system. Sorry I am giving a brain dump of my steps here, it is more provided for info so those of you clued up can get hints out of my mucking about to essentially achieve a similar result.

I guess you non- t-mobile american continent users have one more issue though, as I can put any 5025/5030 (and now 5036) onto the phone with no fear of any 3G loss, but you guys *will* have times during experimenting that you will possibly lose 3G and potentially all RF connectivity, to get to a point to get certain things copied/saved/patched/retrieved.

Regards

[mark i]

Good ideas except that:

1. Our software is the first and only version available for the DEXT
   
2. Unlike most carriers, Bell has never (to my knowledge) pushed ANY software out OTA. Any updates for my previous Motorola phones had to be done with the Motorola Software Update program.

[njones]

Blur_Version.0.14.401.MB200 Source Code? - https://opensource.motorola.com/sf/f...latam.0_14_401

Any use to anybody or old news?

[fogozito]

Blur_Version.0.14.401.MB200 Source Code? - https://opensource.motorola.com/sf/f...latam.0_14_401

Any use to anybody or old news?

it doesnt include the radio.img file.