yashsingh1/xdaforums huggingface dataset:
[Motorola Droid 3] ncho2233:
Bob, I was in similar situation as you. Previously rooted with psouza's tool and used Titanium to freeze some apps.

I was notified of the OTA update, so downloaded it on the phone, but before installing it, I unfroze all apps with titanium. I then allowed the update to apply itself on the phone. It installed, then rebooted, and the "M" logo eventually appeared...

... and wouldn't go away.

I thought it was broken, that the update had failed. "M" logo stayed and stayed, but finally after maybe 15 minutes (possibly more), the phone did boot up and it said the update was successful.

I had lost root, although SU was still installed. I used psouza's tool to "unroot" first (not sure if that was neccessary). Then I used zergRush v3 to root again, found here: http://xdaforums.com/showthread.php?p=18805560#post18805560
[Motorola Droid 3] Bob_760:
I think my problem is that I uninstalled the apps after I determined (by freezing them) that they didnt cause any problems... :(

If I use the OTA update it reboots back to home screen and a message saying update failed appears.

If I use the zip I get that error message... Anyone have another backup Quickoffice.apk I could try pushing?
[Motorola Droid 3] danifunker:
My old backup is turning out to be pretty good for everyone... except for restoring me back to Bell :(

Anyways, here you guys go!
[Motorola Droid 3] ddbone:
Hey guys, can anyone post the bell update file here? I tried the previous file that was from rapid share and didn't work. I'm trying to put it to my friends ext SD and flash it from there.

Thanks in advance!
[Motorola Droid 3] Bob_760:
Thanks danifunker!! That was exactly what I needed, I don't know why restoring my backup using titanium backup didn't work, nor why the other backup I downloaded didn't work but that one worked perfectly. I used ADB Push to overwrite mine and the update worked flawlessly first try. I lost root but regained it using DooMLoRD v3 back in business! :D
[Motorola Droid 3] danifunker:
Can someone try updating their phone through MSU and see what happens? Check through your temp files before proceeding!!! I have been poking around with what I believe daywalker figured out... I'm trying to get an SBF here for us bell users...
[Motorola Droid 3] comscier:
finally updated

Got the update notification yesterday~~

failed...

Then tried manual update from SD

Fail...

I then rooted the phone. (I unrooted it before the update)

Browse to \System\app\

I had a bunch of *.apk renamed *.apk.bak

All I have to do is renaming them all... removing the .bak....

Then I retry the update from SD (X+Power, wait for ! logo, volume up down)

Success ^.^
[Motorola Droid 3] Accophox:
Just to help danifunker along (I can't run MSU on my phone cause it's running 2.3.5 BR)

MSU = Motorola Software Update. Download it here:

https://rsddownload.motorola.com/download/Motorola_Software_Update.exe

Install that, connect your phone to computer, run MSU. You'll need to be running 2.3.4 in order for any magic to happen though. After you've run it (your phone may or may not be at 2.3.6 after this process too), go to C:\Program Files (x86)\Motorola\Software Update and look for a MSU.txt. Upload that here so that we might be able to grab a restore package. :)

--- Okay, I actually started tinkering along the lines of what danifunker was thinking of doing. For this to POSSIBLY work (again, NO guarantees, AT all)... I need somebody to run MSU on 2.3.4 or 2.3.6 stock XT860, post the log to this thread (may want to remove your IMEI though), and run the following commands through adb:

getprop gsm.baseband.version
getprop ro.build.id

and run

adb pull /system/build.prop

posting the file and the outputs of those two commands.

I've worked out the request string to be this:

curl -H 'Content-Type: text/xml' -d '<?xml version="1.0" encoding="UTF-8"?>
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body><srpmessage><srpoperation><fungrp>10</fungrp><opcode>01</opcode><parameterlist>
<parameter><name>flex</name><value>USASOLNABELB1B2B5CA025.0R</value></parameter>
<parameter><name>firmware</name><value>5.5.1-112_SLU-54.4U_03.xx.xx</value></parameter>
</parameterlist></srpoperation></srpmessage></soap-env:Body></soap-env:Envelope>' https://rsd.motorola.com/cs/servlets/SRPConsumerServlet

Unfortunately, the gsm.baseband.version is only available through getprop... so I'm effectively stuck when trying to poll the server for the sbf, as the firmware string is incomplete. (The values in the code correspond to 2.3.4 values - if you decide to do it yourself, sub in the 2.3.6)

I know that this has a shot at working because I've tried it with the Brazil flex and pulled up results immediately.
[Motorola Droid 3] SX86:
USB Mode

Just curious, in which USB mode where you when you rooted your phone ? It seems that mine needs to be in "Motorola Phone Portal" for the device to at least show up in adb devices
[Motorola Droid 3] danifunker:
Strange, you usually need to enable Debugging and under applications and set USB mode to "none". Hey can you post your props as well?

adb shell

getprop gsm.baseband.version

getprop ro.build.id

I know you're running 2.3.6, but this might help us out a bit... Thanks!
[Motorola Droid 3] SX86:
I wish I could help you, but first I must get ADB to F***in work !!! Ahah !

Sorry for the use of the F word.
[Motorola Droid 3] danifunker:
Will the screenshot give us the information we're looking for?

I'm not sure, I tried to use

<value>5.5.1-112_SLU-47.6MU_03.3B.01P</value>

those are the new values (for 2.3.6), but unfortunately I got the same error. I'm not sure if we're passing the string exactly as it's looking for...
[Motorola Droid 3] leobg:
I guess you meant [gsm.version.baseband] not [gsm.baseband.version] :)

gsm.version.baseband: U_03.3B.01P
ro.build.id: 5.5.1-112_SLU-47.6M

build.prop attached.

Note - this is from my now updated 2.3.6 Bell XT860 4G
[Motorola Droid 3] danifunker:
Great, that's exactly what it says in the screenshot. I'm going to walk to a Bell store and take a look at the original baseband version.

Or, does anybody have a screenshot from before they did the update? Doesn't matter if you're rooted.
[Motorola Droid 3] Accophox:
Unfortunately, that looks to be the string we're supposed to pass. Take for instance the UK M2(D2) --

flex="UCASHLSMR2EMEAB1B806D.0R" firmware="SHOLS_U2_02.36.03GSMEPU91A_U_91.07.56I"

SHOLS_U2_02.36.0 = ro.build.id

3GSMEPU91A_U_91.07.56I = gsm.baseband.version

I still need somebody with a 2.3.6 to run MSU to get flex and apflex

Maybe accessible using this: (adb shell)

getprop ro.gsm.flexversion
getprop ro.build.config.version

If not, guess you need to use MSU to try and see if you can get them?

I would have thought the flex wouldn't have changed between versions, but maybe it does.

More experimentation with the RSD server: If you send a request with the associated flex and firmware of one of the phones found in a previous query... it returns no results found? Results may not be one-to-one mapped.

Also - asked daywalker. He's still working on getting us a CA rom too, but I think he's got the same information available to him as we do.
[Motorola Droid 3] lucaspr:
I can make a screenshot of my phone on 2.3.4...

Ohw can't find my camera here is the info:

System version:

5.1.544.XT860.BellMobility.en.CA

BaseBand Version:

U_03.2C.0BP

Build number:

5.5.1-112_SLU-54.4

Kernel version:

2.6.35.7-g6893a41

wfp018@zbr05lnxdroid10 #1

I double checked the codes and I'm installing the update now... So I hope this helps!
[Motorola Droid 3] Accophox:
No dice on the 2.3.4 query. I'm going to give up for now, as I'm still writing exams. :)
[Motorola Droid 3] lucaspr:
Update failed

I tried the updated OTA and by SD card but both fail.

When applied from the sdcard I get the following error:

assert failed: apply_patch_check("/system/build.prop", "45456044c5796124b6f2b6146c62b6301f8b45bb", "bededeaa4976411a1b7a263f7f527e4dfa14")

E:Error in /tmp/sideload/package.zip

(Status 7)

Installation aborted.

Forgive me if I made a typo in the long codes.. But that's it. I downloaded the updates from the link a few pages back and uploaded it to my sd card.

And now both won't install. I already checked my build.prop for changes, but it lookes original to me!

I did change something in build.prop but I deleted that extra code. Well I look further into it.. But any help would be appreciated!

Ohw, I did wipe my phone, just to be sure it would install. Recovery to factory settings, but this didn't alter the extra lines I put in /system/build.prop

---------- Post added at 04:42 PM ---------- Previous post was at 04:37 PM ----------

Could I use your backup, after all it is good for everyone but you! Could I 'borrow' the original build.prop? I realized I didn't backup that before changing. I thought changing it back would be enough!

Never mind all of this!

I got it working! I downloaded the original file from: w ww.droid forums.net/forum/droid-3-hacks/182097-request-build-prop. html

adb push build.prop.bak /system/build.prop

Now it is updating!
[Motorola Droid 3] leobg:
I'll pull them from MSU once I get home. Being quite busy lately @work.
[Motorola Droid 3] danifunker:
Hey Leobg,

no worries. I have an MSU.txt for the original 2.3.4 firmware now. I have access for a bit to a device without the update on it, I'll say I am not planning on updating it soon until we can get an SBF, but I'll going to be headed to the shop to repair my brazillian on my main phone come the new week.
[Motorola Droid 3] :
The only build.prop I can find here is a jumbled text file.

---------- Post added at 10:53 AM ---------- Previous post was at 10:50 AM ----------

I've restored all of the bloatware and factory reset my phone, and the pushed update made it half way through the install and then failed. I'm guessing that it has two do with the two files mentioned earlier -- does anyone have a stock build.prop that is properly formatted?
[Motorola Droid 3] danifunker:
The "jumbled" text file you are referring to is probably because it is a UNIX text file.

Load up notepad++ and try to open the build.prop file in it, the spacing should be fine. Put the build.prop and default.prop into your /system and the update should finish.
[Motorola Droid 3] floored24:
recovery bootstrap

after successfully rooting 236 with doomlord v3, clockwork mod can't get into recovery. I want to nandroid before I install the init d optimization. Anyone know if koush is working on this or should I just use hashcode safestrap to get into recovery and backup. Has anyone nandroided after root on 236?
[Motorola Droid 3] Endoroid:
Im still wondering if anyone got safestrap/custom roms working on bell 2.3.6 yet
[Motorola Droid 3] danifunker:
How are exams?

Anyways, check this out... straight from the MSU. Anyways I don't have the stock phone anymore...

12/20/11 11:05:48 000029c8	Phone.cpp	1909	0	ERROR	GetLanguagePack failed: SendTC failed: ERROR.
12/20/11 11:05:48 IMEI: 3563XXXXXXXXXXXX
12/20/11 11:05:48 Technology: UMTS€è9PPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPt<
12/20/11 11:05:48 Flex File: USASOLNABELB1B2B5CA025.0R
12/20/11 11:05:48 Software: 5.5.1-112_SLU-54.4
12/20/11 11:05:48 PRI:
12/20/11 11:05:48 Kjava:
12/20/11 11:05:48 BootLoader: 0a40
12/20/11 11:05:48 LangPack:
12/20/11 11:05:48 Internal Carrier Name: N / A
12/20/11 11:05:48 Carrier Name: N / A
12/20/11 11:05:48 Model Number: N / A
12/20/11 11:05:48 AP Setup Flex:
12/20/11 11:05:48 AP Resource Flex:
12/20/11 11:05:48 AP Logo Flex:
12/20/11 11:05:48 AP Secure Setup Flex:
12/20/11 11:05:48 AP ROFS:
12/20/11 11:05:48 AP ROFSExtension:
12/20/11 11:05:48 AP Flex: GAS_NA_SOLANABELL_P024
12/20/11 11:05:49 ERROR: Failed to get connection name from registry.
12/20/11 11:05:52 INFO: SRP response with -- OperationStatus<00> Message<Success> FunctionGroup<08> Opcode<48>
12/20/11 11:05:52 Connected device is in warranty and expirydate is <20121030>
12/20/11 11:05:52 WARNNING: No </descendant::fungrp> node
12/20/11 11:05:52 WARNNING: No </descendant::opcode> node
12/20/11 11:05:52 WARNNING: No </descendant::message> node
12/20/11 11:05:52 WARNNING: No </descendant::operationstatus> node
12/20/11 11:05:52 ERROR: Failed to get connection name from registry.
12/20/11 11:05:53 STATUS: Version Verification has been requested.
12/20/11 11:05:53 INFO: SRP response with -- OperationStatus<02> Message<No Phone found with the given phone parameters.> FunctionGroup<06> Opcode<50>
12/20/11 11:05:53 ERROR: SRP Operation failed with code - 02 - No Phone found with the given phone parameters.
12/20/11 11:05:53 ERROR: SRP Operation failed with code <02> <No Phone found with the given phone parameters.> FG<06> OC<50>
12/20/11 11:05:53 ERROR: No Phone is found with the given parameters.
12/20/11 11:05:53 WARNNING: No </descendant::fungrp> node
12/20/11 11:05:53 WARNNING: No </descendant::opcode> node
12/20/11 11:05:53 WARNNING: No </descendant::message> node
12/20/11 11:05:53 WARNNING: No </descendant::operationstatus> node
12/20/11 11:05:54 ERROR: Failed to get connection name from registry.
12/20/11 11:05:55 STATUS: Version Verification has been requested.
12/20/11 11:05:55 INFO: SRP response with -- OperationStatus<02> Message<No Phone found with the given phone parameters.> FunctionGroup<06> Opcode<50>

Notice the last line, "No Phone found with the given phone parameters". I still don't know what the extra parameters are yet though....
[Motorola Droid 3] :
I was using Droid 3 Bootstrap from the market (it's $2.99 but koush does good work and I don't mind supporting him) and it stopped working after the update. I mailed him a bug report but he hasn't replied. I'm not too worried though, there is a reason I've been on Bell stock this long. I actually like the blur interface and I probably won't switch until CM9 comes out, and a foolproof way to return to Bell retail is found. I'm a slow but cautious kind of guy :D
[Motorola Droid 3] Willis111:
I'm pretty sure they do, although like you said I haven't seen anyone post one way or another. Didn't see a kernel in the update and I think that's what was causing problems before, just a slightly different kernel build and it may have had some trouble w/modules etc which would have kept these things from running on our phones prior to now. It may not work for xt860 users who stayed stock, but if you flashed to the brazil retail at any point you should be ready to rock a custom rom.
[Motorola Droid 3] Calen77:
Hi !

I have a XT860, and like bob_760 i used the updated .zip from Bell and don´t Works...look the message:

instaling update...

assert failed: file_getprop ("/system/build.prop","ro.build.fingerprint") == "MOTO/BELCA/umts_solana:2.3.4/5.5.1-112_SLU-54.4/110:users/release-keys" || file_getprop ("/system/build.prop","ro.build.fingerprint") == "MOTO/BELCA/umts_solana:2.3.6/5.5.1-112_SLU-47.6M/111109:user/release-keys"

E:Error in /tmp/sideload/package.zip

(Status 7)

installation aborted.

Then i try to comeback to android 2.3.4 with a backup made with bootstrap and the data is ok, but the android present in the status is 2.3.5. All is there, the pictures, the toys of vivo...

After this, i try made a factory reset and was terrible. All the thinks abou 2.3.4 present in my backup was gone, and the Android version 2.3.5 is there...

I try again, install the bootstrap old and try to make the backup again but the root or the 2.3.5 don´t permit the safestrap comes, after this come the Moto logo and the system boot.

What supost to do ? There is an SBF files to use the RSD Light ?

Please, helpme....
[Motorola Droid 3] danifunker:
We have no SBF for the Bell XT860. Are you using the Bell firmware or are you on Vivo firmware? This update will ONLY work with the Bell firwmware. If you are on 2.3.5 then you cannot apply this patch. If you are on 2.3.4 bell, try to restore your build.prop with the ones that are posted earlier in this thread. Good luck!
[Motorola Droid 3] Calen77:
Oh, thancks Dani...

I am a vivo customer, using a 2.3.5 and i try comeback to 2.3.4 to use the update, now i see that is wast of time...

If there is no SBF for bell, somebody here has a safestrap backup who works for me ? Then i can install the 2.3.4 bell firmware and upgrade to 2.3.6...

I have the solanas retail 2.3.5 SBF, then i always come back and flash my device...

This firmware is good, but there is a bug with the wireless, and every time i change a page on internet, the link is broken, then i have to wait for the device comunicate with my network to procede, every time the link is gone an comeback...

Thancks a lot for the suport...
[Motorola Droid 3] Endoroid:
You can't install 2.3.4 bell firmware. We don't have fastboot files for it(sbf). A safestrap backup doesn't back up your firmware, only /system and /data partitions. If you are on 2.3.5 you are stuck there for the time being
[Motorola Droid 3] danifunker:
Just got my old phone back from the repair shop...

I gotta say, the Bell 2.3.6 is REALLY stable. After using it for about 5 days, I can easily say the battery issues have been solved, and the lag has also been solved. The camera seems to be a fair bit better... Overall, this is a much better improvement over any of the brazillian firmware.
[Motorola Droid 3] eezdva:
So you were able to switch back from the Brazillian firmware??

Thought it wasn't possible??
[Motorola Droid 3] danifunker:
I sent it in for warranty support... Fortunately since I am in Canada I was able to send it in for bell repair after I intentionally killed my partitions.
[Motorola Droid 3] eezdva:
aha. Ok. That's great.

Should have put a note in the box with just SBF pleasssseee or something hahaha.
[Motorola Droid 3] Willis111:
I've added a note a few times asking them to leave the sbf on my internal storage when I've sent my d3 in for repairs but they just ignore it. I had a LOT of trouble with the keyboard for a while, seems the plastic key layover was mis-aligned.
[Motorola Droid 3] eezdva:
Yeah they probably know that when you ask something like this you must be someone who knows more and probably someone from XDA
[Motorola Droid 3] danifunker:
I think we need to know someone who works at FutureTel in Markham... haha :)
[Motorola Droid 3] Willis111:
Just figure its alwys worth a try, you might get someone on the other end who thinjs "why not?". Is there a dump of the new bell build floating around, not the patch files but a dump?
[Motorola Droid 3] matdalb:
Partitions dump

I have partitions dump made from an upgraded Bell XT860 2.3.6 that I made from my friend phone with dd in adb shell. The partitions are: BOOT (mmcblk1p15), CDROM (mmcblk1p17), PREINSTALL (mmcblk1p23), RECOVERY (mmcblk1p16) and SYSTEM (mmcblk1p21). The only thing that's added in the system partition is root. I did a copy of those partitions before the update too with the original system. If someone can do something with these to help us go original (yeah... I'm on Brazil 2.3.5 because I broke my cell in october trying a rom..., so I whent to the Chinise version too!) it would be apprecieted.

Here's the link. "rapidshare.com/files/2799181111/Bell_XT860_2.3.6_Partition_Images.rar" add the "https://" at the

begining because the forums wont let me put the link "To prevent spam". This is my first post.

PS Sorry for my english, I'm a french new-Brunswicker! heh.

Just for info, the command that I use to copy was: dd if=/dev/block/mmcblk1p15 of=/sdcard/boot.img bs=4096

and so on.
[Motorola Droid 3] matdalb:
Installed Recovered Bell 2.3.6 System Partition

I found a way with an copy of the system.img from an updated Bell XT860 2.3.6 to replace the system partition of an installation from the fastboot package for UMTS XT860 2.3.6 Iusacell Mexico. I used the ClockworkMod v5.0.2.6 for that (not the one with Savestrap). First, I did a backup of my XT860 with the SBF from UMTS XT860 2.3.6 Iusacell Mexico. After that, I replaced the system.ext3.tar from an copy that I made myself from the system.img copy of the updated Bell XT860 2.3.6. I updated the nandroid.md5 file with the new MD5 of the system.ext3.tar that I made and did the recovery. After I rebooted the XT860 and VOILA! It booted! I have all the applications that came with the original Bell XT860 and the "H+" for the data. Since I did it, my cell works great! So if you want to dit it, here the link! I made a clean backup after that to share.

Here's the link. "rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar" add the "https://" at the begining cause I still can't post links.

To install: You have to install the Fastboot package for UMTS XT860 2.3.6 Iusacell Mexico if it's not done yet. Extract the file downloaded. It will make a directory named "2012-01-15.00.00.00". In that directory all the files of the backup is there. Copy that directory in your external sd-card of your phone in "YOUR_EXTERNAL_PHONE_SD-CARD_DRIVE\clockworkmod\backup". Boot in ClockworkMod Recovery and do the restore. The first boot after that could take abit long but after the initial boot, it will be faster.

Note: There's two ways to install the backup, you can do it by keeping your DATA and Cache partitions intact or do the full restore. If you do the full restore, at the initial boot, it will take you at the setup like you just bought you cell. And if you just want to recover the system partition, you will still have all your applications and settings installed and working. So it's up to you. Just go at Advance Restore and chose Restore system if you want to keep your DATA and Cache partition intact.
[Motorola Droid 3] Endoroid:
What kind of speed do you get on speedtest.net. I would think radio.img would be responsible for h+

Although I could totally be wrong. Il try later
[Motorola Droid 3] matdalb:
I did the speed test and for Descendant it's 3.23Mbps and Montant it's 0.76Mbps.

---------- Post added at 10:02 PM ---------- Previous post was at 09:43 PM ----------

Me again... I did 13 test (not on the same server). The fastest was Download: 4.29Mbps with an Upload: 1.33Mbps with the server from Washington, DC. And the lowest Download: 0.80Mbps with an Upload: 1.24Mbps with the server from Bangor,ME
[Motorola Droid 3] Endoroid:
Lol. I like the french. That's pretty similar to what I get I get my best speeds at home. 5 down and 1.5 up. More common results are 2.5 down and 1 up.
[Motorola Droid 3] danifunker:
I'd like to see if there is a future upgrade if he could go back on the standard firmware. Can we know, what is the baseband version it says in the about screen now?
[Motorola Droid 3] matdalb:
It says "U_03_3B.00R"
[Motorola Droid 3] LaZiODROID:
Matdalb: im interested in trying your method to restore the bell system img. I flashed the iusacell mexico SBF to my xt860, rooted it, installed Droid3CWBootstrap.apk, chose Install Bootstrap... it said success... then clicked Reboot Recovery. Phone rebooted but not into recovery.. it bootlooped once and then booted like normal.

How did you get into cwm? Maybe the version im using is old?
[Motorola Droid 3] danifunker:
I'm on U_03.3B.01P

Thats since I've got my phone back from the shop of course :)