yashsingh1/xdaforums huggingface dataset:
[LG Optimus 3D] 314:
You should be able to flash this on any custom gingerbread ROM. (Such as thaiz, acura, etc.) It won't work on stock Optimus 3D roms since those aren't deodexed (can't be themed)

Any base band should work fine since this only changes system menus and the notifications bar
[LG Optimus 3D] levent262:
teşekkürler.
[Motorola Droid 3] emprize:
nice, it works!
[Motorola Droid 3] albatorsk:
I see this mentioned everywhere, and now I just have to ask. What happens if you do let it restore your old settings?
[Motorola Droid 3] emprize:
funny....i got 3G, but i cant make a call nor receive a call......

is that my problem or known problem?
[Motorola Droid 3] Rick#2:
That is strange, I can make and receive calls without any issues. What software/baseband are you using?
[Motorola Droid 3] Rick#2:
The world will explode.

No, to be honest I have never tried. I think the idea is that you don't want any settings from a completely different Android release (ie: Gingerbread vs. ICS) being restored. It will still sync up your contacts and everything, just not any wifi connections, system settings, etc.
[Motorola Droid 3] emprize:
kinda strange, i wipe and try now, sometimes clean install but got phone.apk freeze, my latest try is ok....
[Motorola Droid 3] Willis111:
Very nice man!! I was actually talking to this with Hashcode a while ago and we figured that the best way to get things working for xt860/me863 might be to release small patches to enable data etc. Is it possible to pop your modified files in a smaller patch that can be applied against the current and future cm9 builds? (With a list of what's modded I think most people can do this pretty easily and the patch should be easier to update than the ~175 meg cm9 zip as well when carriers release newer firmwares with updated libs etc).

I have this running against my bell 2.3.6 cwm rom that I flashed non-safe, only problem I have is that I have to boot the phone plugged into the computer with ICS, Hash has fixed and broke that a few times I think, not the most important thing. I notice with your build I don't need to have my phone plugged in to the computer to boot ics.

Edit: For some reason I have data and "Sim card not detected" in the status bar, everything is populated correctly in phone info, phone works for calling and data. Switching out the included libmoto_ril.so with the one from bell 2.3.6 took care of the "Sim card not detected" up top(srsly, maybe it was just the reboot) but when I try to make a call phone fc's lol.
[Motorola Droid 3] goalando:
nice ill try later

Enviado desde mi XT860 usando Tapatalk
[Motorola Droid 3] Willis111:
It's worth trying now, with libertys dl site going down last night I flashed this knowing I wouldn't have data only to wake up and find that it's my every day rom now. Any hacking etc from this point might as well be done while using/on this (although I would still really like to see data working on cm7 as well personally, perhaps if Rick#2 makes this into a smaller patch we can test it on that as well). Only a few things that are holding us back now like camera/some codec/module issues.
[Motorola Droid 3] goalando:
So far so good. Thanks a lot
[Motorola Droid 3] dasilva333:
I'm using the stock Bell 2.3.4 rom and I installed this zip on my safe system enabled mode however it doesnt work. I wish someone could show me how to provide more meaningful logs but this is what I get from dmesg:

http://pastebin.com/jHhTiCC3

a longer dmesg:

http://pastebin.com/k5PMF3r4

and finally heres /proc/kmsg

http://pastebin.com/ygW2Fb4Y

if anyone could look through it and tell me why my xt860 is not booting this build of cm9 that'd be great thanks :)
[Motorola Droid 3] Hashcode:
Hey Congrats on setting this up Rick#2!

Get me a patch of just the changed files and I'll host it under the builds so that people can download both files at the same time as new updates happen.

You've single-handedly brought ICS to the XT860!
[Motorola Droid 3] killster:
works awesome! i had to add some stuff to the ATT apn for data to work

and camera isnt working, but everything else is AWESOME.

THANK YOU to everyone who helped make this possible

From my xt860
[Motorola Droid 3] Endoroid:
Is anyone else finding that touch events take longer to register?
[Motorola Droid 3] LaZiODROID:
Very nice man. Thanks

Has anyone tried to send an MMS picture message (on Rogers?) I double checked my apn's. It didn't seem to send. But data is nice!

Sent from my XT860
[Motorola Droid 3] Rick#2:
Edited the first post with a much smaller patch and some more info on what's going on.
[Motorola Droid 3] Hashcode:
Hi!

I put this patch up on the blog as well:

http://hash-of-codes.blogspot.com/p/android-downloads.html

(See XT860 sub-patch)

Rick#2: I can get that frameworks change into my build via a build.prop setting..

ro.ril.ignore.linkiperror=true

(add this to your build.prop and I'll get it in for the next release)

That you don't need to patch frameworks.jar each release.

And I might build in a prop check for disabling the GlobalNWStats trigger which causes a looping FC for non-VZW Droid 3 users. Not sure what to use tho.

Also in your update-script the mount command references:

mount("ext3", "EMMC", "/dev/block/mmcblk1p23", "/system");

That will only work for Safestrap users.

Let's change it to:

mount("ext3", "EMMC", "/dev/block/system", "/system");
[Motorola Droid 3] Rick#2:
Yeah, I was wondering what to do about that. Didn't think I could just use /dev/block/system, nice for compatibility!

Pretty funny how I spent countless hours sifting the radio logs, trying a billion permutations and combinations of proprietary binaries, libraries and build.prop settings when all that needed to be done was to comment out *one* line of code. I had an itch to try getting rid of that bit regarding the exception a few weeks ago but thought it couldn't possibly be that simple... :)
[Motorola Droid 3] Hashcode:
I sometimes get asked why development takes so long when they take a look at the commit changes and the code hasn't been edited much at all.

*cough* This is a fine example of just such a case.

I'm sure the entire XT860 community appreciates the hard work.
[Motorola Droid 3] Willis111:
I think there have been a few users banging their heads on this one lol. Tyvm for the smaller patch, figure I might give it a shot against cm7 if I can find the build to download somewhere and remember what rom it's built off etc.
[Motorola Droid 3] LaZiODROID:
hear hear

Sent from my XT860
[Motorola Droid 3] Endoroid:
I actually had the same idea. I'm pretty sure I have cm7 on my computer somewhere still. I'll check later on and if you need I'll upload it wherever. As I recall cm7 was pretty close to complete
[Motorola Droid 3] Willis111:
I would appreciate if you could upload, think I erased the d/l'd files. I think cm7 had some problems w/the camera as well but other than that (and data ofc) it seemed pretty good.
[Motorola Droid 3] nikeusfr:
enjoy, and take the result ;-)

http://www.2shared.com/file/SXPP5gcU/CM4D3-nightly-20111110-1700.html

http://www.2shared.com/file/VdrXTael/CM4D3-nightly-20111116-1445.html
[Motorola Droid 3] Endoroid:
3rd party camera apps worked. I may try just dropping in blur camera and see hpw it flies
[Motorola Droid 3] Willis111:
TYVM for the links nikeusfr, appreciated and of course results will be shared.

I remember hearing that 3rd party camera apps work. You might want to try the atrix cam as well. New ICS is up btw, check the blog.
[Motorola Droid 3] Hashcode:
UPDATE: ok, I re-added the XT860 patch to the blog:

http://hash-of-codes.blogspot.com/p/android-downloads.html

This one is only 200k. I removed the framework.jar and added the new build.prop change instead. So it's a lib file + build.prop. And it should be compatible with ANY future ICS update as well.

Let me know if you have any problems with it. I didn't sign it, but I did put up the md5sum.
[Motorola Droid 3] Willis111:
I have a question for you regarding this bit of a post here

and your patch for the xt860. I take it just the build.prop edit is needed and not the modded framework.jar. Would I be able to do this with cm7 as well? the new framework.jar wont boot ofc but a few simple build.prop edits and a matching libmoto_ril.so may do the trick. Giving it a go ofc but wondering what your take is.
[Motorola Droid 3] Hashcode:
I would need to make the same change in CM7's framework (to allow for the build.prop) and then it would work I think.
[Motorola Droid 3] Willis111:
And we'd still have to find a compatible libmoto_ril.so as I think every one I've tried on cm7 has caused a fc loop. Thanks for the reply, flashing your new cm9 now :p
[Motorola Droid 3] emprize:
i flashed the alpha6 and gsm patch, fc happens, but after i deleted the apk called globalnwswitch.apk, and build.prop changed network mode to 3, no more fc, im not sure which one did the trick, maybe both, but can the patch try set the network mode to 3?
[Motorola Droid 3] Willis111:
Removing the globalnwswitch.apk fixed it. Hashcode troubleshot this for me last night.
[Motorola Droid 3] dasilva333:
Still doesn't work

It still doesn't work for me heres what I tried:

-safe system enabled

-wipe cache

-format system

-apply alpha 6

-apply xt860 patch in hashcode's site

-wipe cache

It still gets stuck in a reboot loop. If there's any logs I can provide somehow can someone let me know so I can post them? I'd really like to get CM9 running for me.

Thanks
[Motorola Droid 3] Rick#2:
dasilva,

I had the same problem (bootlooping with the Bell firmware) so I switched over to the iusacell revision. I'll switch back over to Bell and see if I can figure out why it bootloops and post here if I can get it working.
[Motorola Droid 3] dasilva333:
How can you switch back to a true Bell firmware if there isnt any Bell fastboot/sbf files?

I can help you figure out I'm also a programmer and I do Android as I previously said I just need to know where to find the relevant log files that log those events. I tried dmesg but I couldnt find anything useful in there.

Any help would be apreciated thanks Rick.
[Motorola Droid 3] Rick#2:
matdalb conjured up a clean nandroid backup of the latest 2.3.6 Bell firmware, so it's about as close to an .SBF/fastboot as we can get at this point in time, here's the link to Rapidshare where it is hosted:

https://rapidshare.com/files/1705579381/ClockworkMod_v.5.0.2.6_Bell_2.3.6.rar

You have to go back to the old ClockworkMod recovery to use it, I'll make an updated Safestrap-compatible backup that you can flash to your original system partition with my tweaked version of Safestrap. Just away from home right now but I'll try to do it when I get a chance.

I've attached Hashcode's tweaked version of koush's CWM Recovery from a few months ago if you'd like to try it out quicker.
[Motorola Droid 3] Endoroid:
So really its just /system isn't it? Wouldn't that be the same as the bell 2.3.6 rom that willis111 has in the devsection
[Motorola Droid 3] Rick#2:
LOL, yep, that'll do her. I guess I'm a sucker for punishment... hehe.

Take Endoroid's advice and use what Willis111 has set up, it looks pretty cool.
[Motorola Droid 3] Rick#2:
Well, I don't know what changed but I'm booting into CM9 just fine now after flashing Willis111's aforementioned Bell 2.3.6 ROM over top of a fresh fastboot from the iusacell revision. I think it might just be general upstream CM changes that fixed whatever problem the Bell software had an issue with that caused the infinite booting problem I had earlier.

Anyone else as lucky as me?
[Motorola Droid 3] Hashcode:
For those experiencing multiple FCs on the boot up in ICS:

Go to: "Settings" -> "More.." -> "Mobile networks" -> Checkmark "Data roaming" and reboot.

Apparently the default settings for CM have changed and there's a bug I need to fix revolving around the notification telling you that data has ended because you're roaming. It's generating about 10 notifications a second and then Android kills the phone process.

Let me know if that helps stop the FCs for now. it's not a permanent solution as I don't want people to have to allow themselves to data roam.
[Motorola Droid 3] Rick#2:
I should mention that I modified Willis111's update script inside the .zip he created so that it would install on my /systemorig partition instead of the safe system (dev/block/mmcblk1p23), I've attached my modified update-script if anyone else wants to give it a shot.

Just replace the update-script inside Bell-2.3.6_-_Optimized.zip (located at META-INF/com/google/android/updater-script) with this one and in non-safe mode of my tweaked version of Hashcode's Safestrap, go to the Advanced menu and "install .zip from sdcard". Be warned that you are messing with your original system partition, so do a nandroid backup first in case anything goes wrong. So far it's working great.

updater-script:

http://db.tt/2VwlkKi7
[Motorola Droid 3] dasilva333:
Hey Rick are you saying if I do the following:

-flash Willis111's Bell rom on top of my stock Bell rom while im in non-safe mode

-apply your patch so it works in non-safe mode

-flash alpha 6 cm9 in my safe-enabled system

- apply hashcode's xt860 patch found in his site

and it might work?

and of course do a nandroid and if the willis' rom and patch doesnt work i can always restore it back hopefully
[Motorola Droid 3] Calen77:
android 2.3.5 + ICS Rick#2' system is working at 100%

Whoooooow... thirst thancks for the link of your first post !

I made a full install of your big link in my XT860 and it's working at 100% !!!

That link have the last Alpha version or there is a new version now ? The bell's link is better ? Any new fix ?

The hashcode's update to download on your web site is diferent or the same thinck ?

I have used this alpha version and it is stable on many thincks, what bugs has on this version to fix ? For me the "big problem" is the camera; in this version my sim card is ok, i have intenet in 2 and 3g and no problems to make calls or use my Apps...

Motorola will going to launch ICS for XT860 ? I'm asking because In Brasil the Milestone 3 has just 5 months old, and Motorolla always offers 2 years of Android update....
[Motorola Droid 3] Willis111:
Unless you're holding a verizon phone you shouldn't have to patch after flashing the optimized xt860 rom.

My xt860 with no software on it the process would be

-Flash xt860 optimized & switch to/enable safestrap

-Flash Hashcodes most current CM9

-Patch CM9 with Rick or Hashcodes xt860 data patch and done
[Motorola Droid 3] dasilva333:
That sounds great, its just what I wanted to know thanks Willis my only question left would be if I flash your optimized xt860 rom on top of my bell rom would I lose all my data and have to set everything up again?
[Motorola Droid 3] Willis111:
No, the optimized rom I posted is the new bell 2.3.6 so it has all the bell data settings in apn-conf.xml , supports umts out of the box and all that. When I flash it on first boot I usually have to let my phone sit for ~15-30 seconds and then H+ appears in the bar without any patching/meddling etc.
[Motorola Droid 3] dasilva333:
No I meant if I were to flash it with the xt860 on top of the stock Bell rom would I lose my /data folder as in my apps/settings/customizations, like would it be a clean slate or would it just upgrade the stock rom?
[Motorola Droid 3] Endoroid:
It would only flash the /system, so data would be untouched. However you may or may not experience issues from the new rom and old data would im inclined to say you would be fine as the rom itself is very similar, I just don't know if going from an odexed to a deodexed /system would cause problems with the old data. Do a nandroid first
[Motorola Droid 3] dasilva333:
Please help guys :)

Alright so I uninstalled Safestrap, disabled it from the recovery menu. Then I installed the old CWM recovery, did a another backup and followed these exact steps:

-applied zip https://rapidshare.com/files/188972752/Bell-2.3.6_-_Optimized.zip

-cleared cache, cleared dalvik cache

-rebooted and it didnt work, it would just boot back into recovery after a few tries

I restored back to my original backup and everything is back to normal. My goal is to be able to use custom roms alongside my original Bell rom but so far it seems that's only possible after I apply alternative sbfs which doesn't seem to be so bad at this point. Just to make sure I'm clear on what's possible I'm going to outline my plan

-Flash the Fastboot package for UMTS XT860 Iusacell Mexico

-Root it

-Apply Safestrap

-Restore my original Bell stock rom from a nandroid backup to the primary system? (is this possible? and if so will I have any radio/data issues on it?)

-Apply hashcode's CM9 XT860 along with any other patches I might have to include to my secondary system

And hopefully if I follow this procedure I should be able to to achieve my goal right?
[Motorola Droid 3] Endoroid:
Im pretty sure you can run custom roms with stock bell. Install safestrap, switch to safe mode, format system, flash chosen rom, ie ICS, flash the xt860 patch, wipe data, reboot. You may not have to format system and wipe data first time flashing a rom in safe system but better safe than sorry.

And then your stock bell rom remains untouched in non safe mode. Switch between the 2 rims by toggling safemode on or off
[Motorola Droid 3] LaZiODROID:
Dasilva,

I don't think its possible right now to flash a custom rom over your non-safe (stock) system in safestrap. You'll have to install it in safe (correct me if I'm wrong, anyone?)

Sent from my XT860
[Motorola Droid 3] Endoroid:
Unless you have rick#2's tweaked safestrap
[Motorola Droid 3] dasilva333:
I tried that exact procedure and it didnt work. I flashed safestrap and I switched to the second system, format it, flashed every rom available out there including CM9, sd3, Liberty, and cm7 and it didnt work. However I only tried the xt860 patch in hashcode's website for the CM9 rom so maybe that's a factor. I'll try the procedure you outlined again for something like CM9 tommorow give it one more try but I think my best bet is tried Rick#2's solution using the alternative sbf. Can anyone confirm or deny that my outlined plan will work in my previous post?

---------- Post added at 05:08 AM ---------- Previous post was at 05:06 AM ----------

I'm not trying to flash a custom rom over my stock system. I'm trying to flash the mexico sbf and then apply my original Bell stock rom on the stock system so then I can apply CM9 on the second system
[Motorola Droid 3] Endoroid:
The patch from hashcodes site is only for ics I believe. There is a different patch you need to apply to get 3g from other custom roms however they should still boot.
[Motorola Droid 3] dasilva333:
Can you or anyone else confirm or deny my plan on post http://xdaforums.com/showpost.php?p=22219457&postcount=50 ? I'd like to try that idea tonight if its possible
[Motorola Droid 3] Endoroid:
Im confused as to why you can't run custom roms as is, however yes your plan should work, its what I did. Are you running bell 2.3.4 or 2.3.6?
[Motorola Droid 3] dasilva333:
so you also flashed the iusacell sbf and then applied custom roms? im running bell 2.3.4 and everything nd everyrom ive tried just results in a boot loop thtas why
[Motorola Droid 3] Endoroid:
Update to 2.3.6 and it should work. 2.3.4 doesn't work with custom roms.
[Motorola Droid 3] dasilva333:
Wow really? that was it all along? If it was that easy I'm going to thank you so much

I tried applying the OTA update back when it came out but it didnt work and I didnt have safestrap or CWM installed back then. Would it just be a matter of finding the 2.3.6 ota update.zip and applying it to my primary system to fix all my problems?

Edit: Found the link http://xdaforums.com/showthread.php?p=21707652

Which one should I apply the 450 or 200mb one? Also I should use CWM and not safestrap for this right?
[Motorola Droid 3] LaZiODROID:
That's a hot writeup Rick#2. I'm sure many will find that very useful. Thanks to you, hash, willis, endo and everyone in the xt860 community for keeping this going

Sent from my XT860
[Motorola Droid 3] Endoroid:
Rick#2, I recall something about safestrap not working with bell 2.3.4, but I don't recall why. And I know custom roms always bootlooped. Is willis's bell 2.3.6 gonna work? Or would he be better off removing any bootstrap/safestrap files and taking the official OTA via about phone>system updates?
[Motorola Droid 3] Rick#2:
You bet, Willis111's update works great. I've installed it on my original /system partition and used it as a base for CM9 without any problems at all.
[Motorola Droid 3] dasilva333:
I cant seem to be able to get 3G to work on CM9 with the patch provided by hash or rick#2, I tried Data Roaming and I tried various settings on my build.prop I've tried going into the Dialer and making sure its set to Gsm Auto among other settings without any luck. I've managed to get some logcat output while the phone is trying to connect maybe someone can help me with more information:

W/ThrottleService( 308): unable to find stats for iface ppp0

D/dalvikvm( 426): GC_CONCURRENT freed 620K, 7% free 11353K/12167K, paused 5ms+2ms

D/dalvikvm( 426): GC_CONCURRENT freed 657K, 7% free 11382K/12231K, paused 5ms+3ms

E/MetadataRetrieverClient( 220): failed to extract an album art

D/dalvikvm( 426): GC_FOR_ALLOC freed 571K, 8% free 11422K/12359K, paused 62ms

D/dalvikvm( 426): GC_FOR_ALLOC freed 308K, 8% free 11413K/12359K, paused 64ms

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: CONNECTING

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/PhoneApp( 476): mReceiver: ACTION_ANY_DATA_CONNECTION_STATE_CHANGED

D/PhoneApp( 476): - state: DISCONNECTED

D/PhoneApp( 476): - reason: simLoaded

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

D/NotificationMgr( 476): hideDataDisconnectedRoaming()...

I have a XT860

Baseband Version: U_03.3B.00R

Kernel Version: 2.6.35.7-g9f70789

Under Status:

Mobile Network Type: HSPA:11

Service State: In Service

Roaming: Not Roaming

Mobile network state: Disconnected

Thanks for your time your help would be apreciated
[Motorola Droid 3] Rick#2:
Have you set up your APN?
[Motorola Droid 3] dasilva333:
Wow Rick your the man! Alright so what happened was when I originally got there the APN was already there so AT&T wasn't checked so I just checked it without verified the settings inside, as I wrote this response I typed out all the settings realizing the password wasn't preset. Entered the password and viola it works now =D. Thank you so much I wasted so much time trying everything else. I'm currently getting a 3G icon and the following is a speed test screenshot. thanks again.

http://www.speedtest.net/android/138892036.png
[Motorola Droid 3] Rick#2:
Glad you got it working man! Funny how it always comes down to one tiny step.